opachassisanalysis(8)
π opachassisanalysis(8) β chassis detective era πβ¨
ok bestie, quick vibe check before we dive in: this is opachassisanalysis, and it lives in the IFSFFCLIRG man page collection, section 8. it is highkey iconic and it is here to look at your chassis and tell you the truth. π
β¨ NAME β¨
opachassisanalysis
(Switch) Performs analysis of the chassis.
the opachassisanalysis tool checks the following for the Intel(R) Omni-Path Fabric Chassis:
- Chassis configuration (as reported by the chassis commands specified in
FF_CHASSIS_CMDSinopafastfabric.conf). π - Chassis health (as reported by the chassis command specified in
FF_CHASSIS_HEALTHinopafastfabric.conf). π©Ί
so yeah, it's checking your config and your health. it's giving doctor who does spreadsheets. π
π¦ SYNTAX π¦
opachassisanalysis [-b|-e] [-s] [-d dir] [-F chassisfile]
[-H 'chassis']
no cap, that's the whole shape of it. πΈ
π OPTIONS π
--helpβ produces the full help text. your little "what does this do again" bestie. π«Ά-bβ specifies the baseline mode. default is the compare/check mode. this is the "take the photo we compare against later" era. πΈ-eβ evaluates health only. default is the compare/check mode. (yes, only the health part. don't be greedy.) π-sβ saves history of failures (errors/differences). receipts, kept. π§Ύ-ddirβ specifies the top-level directory for saving baseline and history of failed checks. default is/var/usr/lib/opa/analysis. ποΈ-Fchassisfileβ specifies the file with the chassis in the cluster. default is/etc/opa/chassis. π-H 'chassis'β specifies the list of chassis on which to execute the command. (mind the quotes, bestie.) π
πΈ EXAMPLE πΈ
opachassisanalysis
literally just that. main character energy, zero arguments. β¨
π ENVIRONMENT VARIABLES π
the following environment variables are also used by this command:
CHASSISβ list of chassis, used if-Fand-Hoptions are not supplied. πCHASSIS_FILEβ file containing list of chassis, used if-Fand-Hoptions are not supplied. πFF_ANALYSIS_DIRβ top-level directory for baselines and failed health checks. ποΈFF_CHASSIS_CMDSβ list of commands to issue during analysis, unused if-eoption supplied. π§FF_CHASSIS_HEALTHβ single command to issue to check overall health during analysis, unused if-boption supplied. π
π DETAILS π
Intel recommends that you set up SSH keys for chassis (see opasetupssh). if SSH keys are not set up, all chassis must be configured with the same admin password and the password must be kept in the /etc/opa/opafastfabric.conf configuration file. π like, do the keys thing. please. your future self is begging.
the default set of FF_CHASSIS_CMDS is:
showInventory fwVersion showNodeDesc timeZoneConf timeDSTConf
snmpCommunityConf snmpTargetAddr showChassisIpAddr showDefaultRoute
the commands specified in FF_CHASSIS_CMDS must be simple commands with no arguments. the output of these commands are compared to the baseline using FF_DIFF_CMD. therefore, commands that include dynamically changing values, such as port packet counters, should not be included in this list. π«π (dynamic stuff in a diff = chaos, and not the cute kind.)
FF_CHASSIS_HEALTH can specify one command (with arguments) to be used to check the chassis health. for chassis with newer firmware, the hwCheck command is recommended. for chassis with older firmware, a benign command, such as fruInfo, should be used. the default is hwCheck. note that only the exit status of the FF_CHASSIS_HEALTH command is checked. the output is not captured and compared in a snapshot. however, on failure its output is saved to aid diagnosis. π©» so like β exit status is the whole tea, but if it goes wrong you still get the receipts.
the opachassisanalysis tool performs its analysis against one or more chassis in the fabric. as such, it permits the chassis to be specified using the -H, -F, CHASSIS, chassis_file or opafastfabric.conf. the handling of these options and settings is comparable to opacmdall -C and similar FastFabric Toolset commands against a chassis. π§
all files generated by opafabricanalysis start with chassis. in the file name. π·οΈ
the opachassisanalysis tool generates files such as the following within FF_ANALYSIS_DIR. the actual file names reflect the individual chassis commands that have been configured through the FF_CHASSIS_HEALTH and FF_CHASSIS_CMDS parameters:
π©Ί Health Check
latest/chassis.hwCheckβ output ofhwCheckcommand for all selected chassis. π
πΈ Baseline
during a baseline run, the following files are also created in FF_ANALYSIS_DIR/latest.
baseline/chassis.fwVersionβ output offwVersioncommand for all selected chassis.baseline/chassis.showChassisIpAddrβ output of theshowChassisIpAddr.command for all selected chassis.baseline/chassis.showDefaultRouteβ output of theshowDefaultRoutecommand for all selected chassis.baseline/chassis.showNodeDescβ output of theshowNodeDesccommand for all selected chassis.baseline/chassis.showInventoryβ output of theshowInventorycommand for all selected chassis.baseline/chassis.snmpCommunityConfβ output of thesnmpCommunityConfcommand for all selected chassis.baseline/chassis.snmpTargetAddrβ output of thesnmpTargetAddrcommand for all selected chassis.baseline/chassis.timeDSTConfβ output of thetimeDSTConfcommand for all selected chassis.baseline/chassis.timeZoneConfβ output of thetimeZoneConfcommand for all selected chassis.
π Full Analysis
the following .diff files are only created if differences are detected. (no differences, no diff. periodt.)
latest/chassis.hwCheckβ output of thehwCheckcommand for all selected chassis.latest/chassis.fwVersionβ output of thefwVersioncommand for all selected chassis.latest/chassis.fwVersion.diffβ diff of the baseline and latestfwVersion.latest/chassis.showChassisIpAddrβ output of theshowChassisIpAddrcommand for all selected chassis.latest/chassis.showChassisIpAddr.diffβ diff of baseline and latestshowChassisIpAddr.latest/chassis.showDefaultRouteβ output of theshowDefaultRoutecommand for all selected chassis.latest/chassis.showDefaultRoute.diffβ diff of the baseline and the latestshowDefaultRoute.latest/chassis.showNodeDescβ output of theshowNodeDesccommand for all selected chassis.latest/chassis.showNodeDesc.diffβ diff of the baseline and latestshowNodeDesc.latest/chassis.showInventoryβ output of theshowInventorycommand for all selected chassis.latest/chassis.showInventory.diffβ diff of the baseline and latestshowInventory.latest/chassis.snmpCommunityConfβ output of thesnmpCommunityConfcommand for all selected chassis.latest/chassis.snmpCommunityConf.diffβ diff of the baseline and latestsnmpCommunityConf.latest/chassis.snmpTargetAddrβ output of thesnmpTargetAddrcommand for all selected chassis.latest/chassis.snmpTargetAddr.diffβ diff of the baseline and latestsnmpTargetAddr.latest/chassis.timeDSTConfβ output of thetimeDSTConfcommand for all selected chassis.latest/chassis.timeDSTConf.diffβ diff of the baseline and latesttimeDSTConf.latest/chassis.timeZoneConfβ output of thetimeZoneConfcommand for all selected chassis.latest/chassis.timeZoneConf.diffβ diff of the baseline and latesttimeZonfConf.
if the -s option is used and failures are detected, files related to the checks that failed are also copied to a time-stamped directory name under FF_ANALYSIS_DIR. π°οΈβ¨
π CHASSIS ITEMS CHECKED AGAINST THE BASELINE π
based upon showInventory:
- Addition/removal of Chassis FRUsReplacement is only checked for FRUs that
showInventorydisplays the serial number. π - Removal of redundant FRUs (spines, power supply, fan). π¨
based upon fwVersion:
- Changes to primary or alternate FW versions installed in cards in chassis. π₯
based upon showNodeDesc:
- Changes to configured node description for chassis. note changes detected here would also be detected in fabric level analysis. π
based upon timeZoneConf and timeDSTConf:
- Changes to the chassis time zone and daylight savings time configuration. π
based upon snmpCommunityConf and snmpTargetAddr:
- Changes to SNMP persistent configuration within the chassis. π‘
the following Chassis items are not checked against baseline:
- Changes to the chassis configuration on the management LAN (for example,
showChassisIpAddr,showDefaultRoute). such changes typically result in the chassis not responding on the LAN at the expected address that is detected by failures that perform other chassis checks. π
π§ CHASSIS ITEMS ALSO CHECKED DURING HEALTH CHECK π§
based upon hwCheck:
- Overall health of FRUs in chassis:
- Status of Fans in chassis π¬οΈ
- Status of Power Supplies in chassis β‘
- Temp/Voltage for each card π‘οΈ
- Presence of adequate power/cooling of FRUs π
- Presence of N+1 power/cooling of FRUs π
- Presence of Redundant AC input π
that's the whole page, bestie. you're officially fluent. π¦
Copyright(C) 2015-2019 Intel Corporation β and that's the source, version and date wrapped up in a little bow, from the IFSFFCLIRG man page set, section 8, opachassisanalysis(8). go forth and analyze. slay. π
πβ¨
π¦ where this page comes from
- centos-stream 9: opa-fastfabric 1:10.12.1.0.6-1.el9 Β· BSD or GPLv2
- debian bookworm: opa-fastfabric 10.10.3.0.11-1+b1 Β· BSD-3-clause-top
- debian trixie: opa-fastfabric 10.10.3.0.11-1+b2 Β· BSD-3-clause-top
- opensuse-leap 16.0: opa-fastfabric 10.14.4.0.20-160000.3.2 Β· BSD-3-Clause OR GPL-2.0-only
- ubuntu jammy: opa-fastfabric 10.10.3.0.11-1ubuntu1 Β· BSD-3-clause-top
- ubuntu noble: opa-fastfabric 10.10.3.0.11-1ubuntu3 Β· BSD-3-clause-top
- ubuntu questing: opa-fastfabric 10.10.3.0.11-1ubuntu3
- ubuntu resolute: opa-fastfabric 10.10.3.0.11-1ubuntu4 Β· BSD-3-clause-top
- ubuntu stonking: opa-fastfabric 10.10.3.0.11-1ubuntu5 Β· BSD-3-clause-top
- Copyright 2015-2019, Intel Corporation
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms