health command
This command displays the current health status of the command target. It can also be used to display the alerts that are active for the command target.
You can only specify one command target each time you run the health command.
- Flex System Enterpise chassis command target: For the Flex System Enterpise chassis command target, one of the following health states is returned. This state will reflect the highest health state reported by any other component installed in the chassis, unless the state reported by the chassis itself is higher.
- OK - All monitored parameters are within normal their operating ranges.
- System level - There are currently active minor warnings or system events, but no critical or major events are active.
- Non-critical - There are currently active major warnings or system events, but no critical events are active.
- Critical - One or more critical events are currently active.
- Lenovo Flex System Carrier-Grade chassis command target: For the Lenovo Flex System Carrier-Grade chassis command target, one of the following health states is returned. This state will reflect the highest health state reported by any other component installed in the chassis, unless the state reported by the chassis itself is higher.
- OK - All monitored parameters are within normal their operating ranges.
- Minor - There are currently active minor warnings or system events, but no critical or major events are active.
- Major - There are currently active major warnings or system events, but no critical events are active.
- Critical - One or more critical events are currently active.
- Compute node command target: For the compute node command target, one of the following health states is returned for all chassis types. This state will reflect the highest health state reported by any other component installed in the compute node, unless the state reported by the compute node itself is higher.
- OK - All monitored parameters in the chassis are within normal their operating ranges.
- Non-critical - There are currently active warnings or system events, but no critical events are active.
- Critical - One or more critical events are currently active.
- Command targets other than a chassis or compute node: For command targets other than a compute node, one of the following health states is returned for all chassis types.
- OK - All monitored parameters are within normal their operating ranges.
- System level - There are currently active minor warnings or system events, but no critical or major events are active.
- Non-critical - There are currently active major warnings or system events, but no critical events are active.
- Critical - One or more critical events are currently active.
- Web interface: Critical , Attention (Telco major/minor event), Normal (Telco OK event)
- SNMP: Critical/Bad, Warning (Telco major/minor event), Good (Telco OK event)
- CLI: Critical, Non-critical (Telco major/minor event), OK
If command syntax is not correctly entered, or if a command fails to run, an error message is returned. See Common errors for a list of error messages that apply to all commands or health command errors for a list of error messages that are specific to the health command.
Function | What it does | Command | Target (see paths in Command targets) |
---|---|---|---|
Display health status | Displays the current health status of the command target.
| health | Lenovo Flex System chassis:
Primary CMM:
Compute node:
I/O module:
Power supply:
Fan module:
|
Display health status for tree | Displays the current health status of the tree structure of devices present in the Lenovo Flex System chassis, starting at the command target level. If CMM bays are part of the tree, they will be identified as primary or standby (redundant).
| health -l depth where depth
| Lenovo Flex System chassis:
Primary CMM:
Compute node:
I/O module:
Power supply:
Fan module:
|
Display health status and alerts Note This command option applies only to | Displays the current health status and active alerts for the command target.
The total amount of information returned from the health -f command is limited to 1024 bytes. | health -f | Lenovo Flex System chassis:
Primary CMM:
Compute node:
I/O module:
Power supply:
Fan module:
|
Display health status and active events (Telco) Note This command option applies only to | Displays the current health status and active events for the command target. Note In a Lenovo Flex System Carrier-Grade chassis, the -f option must be used exclusive of the -k option.
The total amount of information returned from the health -f command is limited to 1024 bytes. | health -f | Lenovo Flex System chassis:
Primary CMM:
Compute node:
I/O module:
Power supply:
Fan module:
|
Display health status and acknowledged events (Telco) Note This command option applies only to | Displays the current health status and acknowledged events for the command target. Note In a Lenovo Flex System Carrier-Grade chassis, the -k option must be used exclusive of the -f option.
The total amount of information returned from the health -f command is limited to 1024 bytes. | health -k | Lenovo Flex System chassis:
Primary CMM:
Compute node:
I/O module:
Power supply:
Fan module:
|
Display results with timestamp | Adds display of timestamp information to status command output. | health -t Note The -t option must be used with the -f option. | Lenovo Flex System chassis:
Primary CMM:
Compute node:
I/O module:
Power supply:
Fan module:
|
health -l a -f -t
The following example shows the information that is returned from these commands:
system> health -l a -f -t
system : Critical
blade[1] : Critical
(03/25/15, 16:29:58) (0000BB5C) Node Node 01 message: processor 2 has a Configuration Mismatch.
blade[3] : Critical
(03/25/15, 16:29:45) (0000BB58) Node Node 03 message: Front panel board 1, interconnect
(LightPath) configuration error.
(03/25/15, 16:29:45) (0000BB59) Node Node 03 message: Expansion card 1, (Mezz Exp 1 Fault)
critical.
(03/25/15, 16:30:11) (0000BB62) Node Node 03 incompatible with the I/O-module configuration.
(03/25/15, 16:29:13) (0000BB47) Security policy is in Pending state at system-management
processor on Node 03.
blade[5] : Non-Critical
(03/25/15, 16:29:08) (0000BB46) Security policy is in Pending state at system-management
processor on Node 05.
blade[6] : Non-Critical
(03/25/15, 16:29:18) (0000BB4C) Security policy is in Pending state at system-management
processor on Node 06.
blade[7] : Non-Critical
(03/25/15, 16:29:30) (0000BB50) Node Node 07 device Storage back plane[01] VPD is not valid.
(03/25/15, 16:29:35) (0000BB52) Node Node 07 device Storage back plane[02] VPD is not valid.
blade[11] : Critical
(03/25/15, 16:48:33) (0000BB6F) Node Node 11 failed initial provisioning.
blade[13] : Non-Critical
(03/25/15, 16:28:55) (0000BB43) Security policy is in Pending state at system-management
processor on Node 13.
blade[14] : Non-Critical
(03/25/15, 16:28:51) (0000BB42) Security policy is in Pending state at system-management
processor on Node 14.
(03/25/15, 16:29:05) (0000BB45) Node Node 14 device Expansion card[01] VPD is not valid.
blower[1] : OK
blower[2] : OK
blower[3] : Critical
(03/25/15, 16:28:48) (0000BB40) Fan module Fan 03 has failed.
blower[4] : OK
blower[5] : OK
blower[6] : OK
blower[7] : OK
blower[8] : Critical
(03/25/15, 16:29:01) (0000BB44) Fan module Fan 08 has failed.
blower[9] : OK
blower[10]: OK
power[1] : Non-Critical
(03/25/15, 16:29:15) (0000BB48) Power supply Power Supply 01 is off. Input fault.
blower[1] : OK
power[2] : Non-Critical
(03/25/15, 16:29:15) (0000BB49) Power supply Power Supply 02 is off. Input fault.
blower[1] : OK
power[3] : Non-Critical
(03/25/15, 16:29:15) (0000BB4A) Power supply Power Supply 03 is off. Input fault.
blower[1] : OK
power[4] : OK
blower[1] : OK
power[5] : OK
blower[1] : OK
power[6] : Non-Critical
(03/25/15, 16:29:16) (0000BB4B) Power supply Power Supply 06 is off. Input fault.
blower[1] : OK
mm[1] : Non-Critical
(03/25/15, 16:28:48) (0000BB41) Cooling zone zone01 might not have adequate cooling.
mm[2] : OK
switch[3] : Non-Critical
(03/25/15, 16:30:11) (0000BB61) I/O module IO Module 03 is incompatible with the node
configuration.
mt[1] : OK
fanmux[1] : Non-Critical
(03/25/15, 16:29:19) (0000BB4D) Fan logic module Fan Logic 01 is an older revision card (FRU
81Y2912) and needs to be replaced.
fanmux[2] : Non-Critical
(03/25/15, 16:29:19) (0000BB4E) Fan logic module Fan Logic 02 is an older revision card (FRU
81Y2912) and needs to be replaced.
system>