1
2opachassisanalysis(8) Master map: IFSFFCLIRG (Man Page) opachassisanalysis(8)
3
4
5
7 opachassisanalysis
8
9
10
11 (Switch) Performs analysis of the chassis.
12
13 The opachassisanalysis tool checks the following for the Intel(R) Omni-
14 Path Fabric Chassis:
15
16 · Chassis configuration (as reported by the chassis commands spec‐
17 ified in FF_CHASSIS_CMDS in opafastfabric.conf).
18
19 · Chassis health (as reported by the chassis command specified in
20 FF_CHASSIS_HEALTH in opafastfabric.conf).
21
23 opachassisanalysis [-b|-e] [-s] [-d dir] [-F chassisfile]
24 [-H 'chassis']
25
27 --help Produces full help text.
28
29 -b Specifies the baseline mode. Default is the compare/check
30 mode.
31
32 -e Evaluates health only. Default is the compare/check mode.
33
34 -s Saves history of failures (errors/differences).
35
36 -d dir Specifies the top-level directory for saving baseline and
37 history of failed checks. Default = /var/usr/lib/opa/analysis
38
39 -F chassisfile
40 Specifies the file with the chassis in the cluster. Default =
41 /etc/opa/chassis
42
43 -H 'chassis'
44 Specifies the list of chassis on which to execute the com‐
45 mand.
46
48 opachassisanalysis
49
51 The following environment variables are also used by this command:
52
53 CHASSIS List of chassis, used if -F and -H options are not supplied.
54
55 CHASSIS_FILE
56 File containing list of chassis, used if -F and -H options
57 are not supplied.
58
59 FF_ANALYSIS_DIR
60 Top-level directory for baselines and failed health checks.
61
62 FF_CHASSIS_CMDS
63 List of commands to issue during analysis, unused if -e
64 option supplied.
65
66
67 FF_CHASSIS_HEALTH
68 Single command to issue to check overall health during analy‐
69 sis, unused if -b option supplied.
70
71
73 Intel recommends that you set up SSH keys for chassis (see opasetupssh
74 ). If SSH keys are not set up, all chassis must be configured with the
75 same admin password and the password must be kept in the
76 /etc/opa/opafastfabric.conf configuration file.
77
78 The default set of FF_CHASSIS_CMDS is:showInventory fwVersion showNod‐
79 eDesc timeZoneConf timeDSTConf
80 snmpCommunityConf snmpTargetAddr showChassisIpAddr showDefaultRoute
81
82 The commands specified in FF_CHASSIS_CMDS must be simple commands with
83 no arguments. The output of these commands are compared to the baseline
84 using FF_DIFF_CMD. Therefore, commands that include dynamically chang‐
85 ing values, such as port packet counters, should not be included in
86 this list.
87
88 FF_CHASSIS_HEALTH can specify one command (with arguments) to be used
89 to check the chassis health. For chassis with newer firmware, the
90 hwCheck command is recommended. For chassis with older firmware, a
91 benign command, such as fruInfo, should be used. The default is
92 hwCheck. Note that only the exit status of the FF_CHASSIS_HEALTH com‐
93 mand is checked. The output is not captured and compared in a snapshot.
94 However, on failure its output is saved to aid diagnosis.
95
96 The opachassisanalysis tool performs its analysis against one or more
97 chassis in the fabric. As such, it permits the chassis to be specified
98 using the -H, -F, CHASSIS, chassis_file or opafastfabric.conf. The han‐
99 dling of these options and settings is comparable to opacmdall -C and
100 similar FastFabric Toolset commands against a chassis.
101
102 All files generated by opafabricanalysis start with chassis. in the
103 file name.
104
105 The opachassisanalysis tool generates files such as the following
106 within FF_ANALYSIS_DIR. The actual file names reflect the individual
107 chassis commands that have been configured through the FF_CHAS‐
108 SIS_HEALTH and FF_CHASSIS_CMDS parameters:
109
110 Health Check
111
112
113 · latest/chassis.hwCheck Output of hwCheck command for all
114 selected chassis
115
116
117 Baseline: During a baseline run, the following files are also created
118 in FF_ANALYSIS_DIR /latest.
119
120 · baseline/chassis.fwVersion Output of fwVersion command for all
121 selected chassis.
122
123
124 · baseline/chassis.showChassisIpAddr Output of the showChassisI‐
125 pAddr. command for all selected chassis.
126
127
128 · baseline/chassis.showDefaultRoute Output of the showDefaultRoute
129 command for all selected chassis.
130
131
132 · baseline/chassis.showNodeDesc Output of the showNodeDesc command
133 for all selected chassis.
134
135
136 · baseline/chassis.showInventory Output of the showInventory com‐
137 mand for all selected chassis.
138
139
140 · baseline/chassis.snmpCommunityConf Output of the snmpCommunity‐
141 Conf command for all selected chassis.
142
143
144 · baseline/chassis.snmpTargetAddr Output of the snmpTargetAddr
145 command for all selected chassis.
146
147
148 · baseline/chassis.timeDSTConf Output of the timeDSTConf command
149 for all selected chassis.
150
151
152 · baseline/chassis.timeZoneConf Output of the timeZoneConf command
153 for all selected chassis.
154
155
156 Full Analysis: The following .diff files are only created if differ‐
157 ences are detected.
158
159 · latest/chassis.hwCheck Output of the hwCheck command for all
160 selected chassis.
161
162
163 · latest/chassis.fwVersion Output of the fwVersion command for all
164 selected chassis.
165
166
167 · latest/chassis.fwVersion.diff diff of the baseline and latest
168 fwVersion.
169
170
171 · latest/chassis.showChassisIpAddr Output of the showChassisIpAddr
172 command for all selected chassis.
173
174
175 · latest/chassis.showChassisIpAddr.diff diff of baseline and lat‐
176 est showChassisIpAddr.
177
178
179 · latest/chassis.showDefaultRoute Output of the showDefaultRoute
180 command for all selected chassis.
181
182
183 · latest/chassis.showDefaultRoute.diff diff of the baseline and
184 the latest showDefaultRoute.
185
186
187 · latest/chassis.showNodeDesc Output of the showNodeDesc command
188 for all selected chassis.
189
190
191 · latest/chassis.showNodeDesc.diff diff of the baseline and latest
192 showNodeDesc.
193
194
195 · latest/chassis.showInventory Output of the showInventory command
196 for all selected chassis.
197
198
199 · latest/chassis.showInventory.diff diff of the baseline and lat‐
200 est showInventory.
201
202
203 · latest/chassis.snmpCommunityConf Output of the snmpCommunityConf
204 command for all selected chassis.
205
206
207 · latest/chassis.snmpCommunityConf.diff diff of the baseline and
208 latest snmpCommunityConf.
209
210
211 · latest/chassis.snmpTargetAddr Output of the snmpTargetAddr com‐
212 mand for all selected chassis.
213
214
215 · latest/chassis.snmpTargetAddr.diff diff of the baseline and lat‐
216 est snmpTargetAddr.
217
218
219 · latest/chassis.timeDSTConf Output of the timeDSTConf command for
220 all selected chassis.
221
222
223 · latest/chassis.timeDSTConf.diff diff of the baseline and latest
224 timeDSTConf.
225
226
227 · latest/chassis.timeZoneConf Output of the timeZoneConf command
228 for all selected chassis.
229
230
231 · latest/chassis.timeZoneConf.diff diff of the baseline and latest
232 timeZonfConf.
233
234
235 If the -s option is used and failures are detected, files related to
236 the checks that failed are also copied to a time-stamped directory name
237 under FF_ANALYSIS_DIR.
238
240 Based upon showInventory :
241
242 · Addition/removal of Chassis FRUsReplacement is only checked for
243 FRUs that showInventory displays the serial number.
244
245
246 · Removal of redundant FRUs (spines, power supply, fan)
247
248 Based upon fwVersion:
249
250 · Changes to primary or alternate FW versions installed in cards
251 in chassis.
252
253 Based upon showNodeDesc:
254
255 · Changes to configured node description for chassis. Note changes
256 detected here would also be detected in fabric level analysis.
257
258 Based upon timeZoneConf and timeDSTConf:
259
260 · Changes to the chassis time zone and daylight savings time con‐
261 figuration.
262
263 Based upon snmpCommunityConf and snmpTargetAddr:
264
265 · Changes to SNMP persistent configuration within the chassis.
266
267 The following Chassis items are not checked against baseline:
268
269 · Changes to the chassis configuration on the management LAN (for
270 example, showChassisIpAddr, showDefaultRoute). Such changes typ‐
271 ically result in the chassis not responding on the LAN at the
272 expected address that is detected by failures that perform other
273 chassis checks.
274
276 Based upon hwCheck:
277
278 · Overall health of FRUs in chassis:
279
280 · Status of Fans in chassis
281
282 · Status of Power Supplies in chassis
283
284 · Temp/Voltage for each card
285
286 · Presence of adequate power/cooling of FRUs
287
288 · Presence of N+1 power/cooling of FRUs
289
290 · Presence of Redundant AC input
291
292
293
294Copyright(C) 2015-2018 Intel Corporation opachassisanalysis(8)