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_CMDS in opafastfabric.conf). πŸŽ€
  • Chassis health (as reported by the chassis command specified in FF_CHASSIS_HEALTH in opafastfabric.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. 🧾
  • -d dir β€” specifies the top-level directory for saving baseline and history of failed checks. default is /var/usr/lib/opa/analysis. πŸ—‚οΈ
  • -F chassisfile β€” 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 -F and -H options are not supplied. πŸ‘‘
  • CHASSIS_FILE β€” file containing list of chassis, used if -F and -H options 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 -e option supplied. 🧠
  • FF_CHASSIS_HEALTH β€” single command to issue to check overall health during analysis, unused if -b option 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 of hwCheck command for all selected chassis. πŸ’–

πŸ“Έ Baseline

during a baseline run, the following files are also created in FF_ANALYSIS_DIR/latest.

  • baseline/chassis.fwVersion β€” output of fwVersion command for all selected chassis.
  • baseline/chassis.showChassisIpAddr β€” output of the showChassisIpAddr. command for all selected chassis.
  • baseline/chassis.showDefaultRoute β€” output of the showDefaultRoute command for all selected chassis.
  • baseline/chassis.showNodeDesc β€” output of the showNodeDesc command for all selected chassis.
  • baseline/chassis.showInventory β€” output of the showInventory command for all selected chassis.
  • baseline/chassis.snmpCommunityConf β€” output of the snmpCommunityConf command for all selected chassis.
  • baseline/chassis.snmpTargetAddr β€” output of the snmpTargetAddr command for all selected chassis.
  • baseline/chassis.timeDSTConf β€” output of the timeDSTConf command for all selected chassis.
  • baseline/chassis.timeZoneConf β€” output of the timeZoneConf command 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 the hwCheck command for all selected chassis.
  • latest/chassis.fwVersion β€” output of the fwVersion command for all selected chassis.
  • latest/chassis.fwVersion.diff β€” diff of the baseline and latest fwVersion.
  • latest/chassis.showChassisIpAddr β€” output of the showChassisIpAddr command for all selected chassis.
  • latest/chassis.showChassisIpAddr.diff β€” diff of baseline and latest showChassisIpAddr.
  • latest/chassis.showDefaultRoute β€” output of the showDefaultRoute command for all selected chassis.
  • latest/chassis.showDefaultRoute.diff β€” diff of the baseline and the latest showDefaultRoute.
  • latest/chassis.showNodeDesc β€” output of the showNodeDesc command for all selected chassis.
  • latest/chassis.showNodeDesc.diff β€” diff of the baseline and latest showNodeDesc.
  • latest/chassis.showInventory β€” output of the showInventory command for all selected chassis.
  • latest/chassis.showInventory.diff β€” diff of the baseline and latest showInventory.
  • latest/chassis.snmpCommunityConf β€” output of the snmpCommunityConf command for all selected chassis.
  • latest/chassis.snmpCommunityConf.diff β€” diff of the baseline and latest snmpCommunityConf.
  • latest/chassis.snmpTargetAddr β€” output of the snmpTargetAddr command for all selected chassis.
  • latest/chassis.snmpTargetAddr.diff β€” diff of the baseline and latest snmpTargetAddr.
  • latest/chassis.timeDSTConf β€” output of the timeDSTConf command for all selected chassis.
  • latest/chassis.timeDSTConf.diff β€” diff of the baseline and latest timeDSTConf.
  • latest/chassis.timeZoneConf β€” output of the timeZoneConf command for all selected chassis.
  • latest/chassis.timeZoneConf.diff β€” diff of the baseline and latest timeZonfConf.

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 showInventory displays 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. πŸ’…πŸŒˆβœ¨