CLI Commands to View Hardware Status
431387
Created On 09/25/18 19:21 PM - Last Modified 07/06/26 11:18 AM
Symptom
This document describes the CLI commands to provide information on the hardware status of a Palo Alto Networks device.
Environment
- Any PA-Firewalls
- Note: For PAN-OS 5.0 and above. The commands do not apply to the Palo Alto Networks VM-Series platforms.
Resolution
To view hardware alarms ("False" indicates "no alarm"):
> show system state | match alarm
chassis.alarm: { }
chassis.leds: { 'alarm': Off, 'fans': Green, 'ha': Off, 'status': Green, 'temp': Green, }
env.s0.fan.0: { 'alarm': False, 'avg': True, 'desc': Fan #1 Operational, 'min': 1, }
env.s0.fan.1: { 'alarm': False, 'avg': True, 'desc': Fan #2 Operational, 'min': 1, }
env.s0.power.0: { 'alarm': False, 'avg': 1.051, 'desc': 1.05V Power Rail, 'hyst': 0.007, 'max': 1.130, 'min': 0.980, 'samples': [ 1.045, 1.055, 1.055, ], }
env.s0.power.1: { 'alarm': False, 'avg': 1.094, 'desc': 1.1V Power Rail, 'hyst': 0.007, 'max': 1.180, 'min': 1.030, 'samples': [ 1.104, 1.084, 1.094, ], }
env.s0.power.2: { 'alarm': False, 'avg': 1.214, 'desc': 1.2V Power Rail, 'hyst': 0.014, 'max': 1.350, 'min': 1.080, 'samples': [ 1.211, 1.221, 1.211, ], }
env.s0.power.3: { 'alarm': False, 'avg': 1.807, 'desc': 1.8V Power Rail, 'hyst': 0.018, 'max': 1.980, 'min': 1.620, 'samples': [ 1.807, 1.807, 1.807, ], }
env.s0.power.4: { 'alarm': False, 'avg': 2.490, 'desc': 2.5V Power Rail, 'hyst': 0.025, 'max': 2.750, 'min': 2.250, 'samples': [ 2.490, 2.490, 2.490, ], }
env.s0.power.5: { 'alarm': False, 'avg': 3.340, 'desc': 3.3V Power Rail, 'hyst': 0.033, 'max': 3.630, 'min': 2.970, 'samples': [ 3.340, 3.340, 3.340, ], }
env.s0.power.6: { 'alarm': False, 'avg': 4.980, 'desc': 5.0V Power Rail, 'hyst': 0.050, 'max': 5.500, 'min': 4.500, 'samples': [ 4.980, 4.980, 4.980, ], }
env.s0.power.7: { 'alarm': False, 'avg': 2.490, 'desc': 3.0V RTC Battery, 'hyst': 0.175, 'max': 3.500, 'samples': [ 2.490, 2.490, 2.490, ], }
env.s0.thermal.0: { 'alarm': False, 'avg': 30.500, 'desc': Temperature at MP [U6], 'hyst': 2.250, 'max': 50.000, 'min': 5.000, 'samples': [ 30.500, 30.500, 30.500, ], }
env.s0.thermal.1: { 'alarm': False, 'avg': 34.500, 'desc': Temperature at DP [U7], 'hyst': 2.250, 'max': 50.000, 'min': 5.000, 'samples': [ 34.500, 34.500, 34.500, ], }
ha.runtime.device.alarm: False
hw.slot0.leds: { 'alarm': Off, 'fans': Green, 'ha': Off, 'status': Green, 'temp': Green, }
Other command samples:
> show system state filter env.* | match alarm > show system state | match fan > show system state | match power
To display the most recent critical hardware alarms (Use the tab key to determine the options for the italicized words: Backward = most recent, forward = oldest)
> show log system severity greater-than-or-equal critical direction equal backward Time Severity Subtype Object EventID ID Description =============================================================================== 01/20 06:51:58 critical ha unknown 0 HA Group 1: commit on local device with running configuration not synchronized; synchronize manually 12/23 14:29:21 critical ha unknown 0 HA Group 1: moved from state Passive to state Active 12/23 14:29:12 critical ha unknown 0 HA Group 1: moved from state Non-Functional to state Passive 12/23 14:27:15 critical general unknown 0 Chassis Master Alarm: HA-event 12/23 14:27:15 critical ha unknown 0 HA Group 1: moved from state Active to state Non-Functional 12/23 14:27:15 critical ha unknown 0 HA Group 1: dataplane is down 12/23 14:27:01 critical general unknown 0 Heartbeat triggering a restart of 'data-plane' from the control-plane 11/09 17:39:44 critical general unknown 0 Chassis Master Alarm: Fans 11/09 17:39:44 critical general unknown 0 Fan #3 Speed: 5778.70 above high-limit 5750.00 09/29 08:52:26 critical ha unknown 0 HA Group 1: commit on local device with running configuration not synchronized; synchronize manually 09/20 09:09:44 critical general unknown 0 Fan #3 Speed: 5778.70 above high-limit 5750.00 09/20 09:09:44 critical general unknown 0 Chassis Master Alarm: Fans 09/20 09:09:04 critical general unknown 0 Chassis Master Alarm: Fans 09/20 09:09:04 critical general unknown 0 Fan #3 Speed: 5776.98 above high-limit 5750.00 06/20 12:37:04 critical general unknown 0 Chassis Master Alarm: Fans 06/20 12:37:04 critical general unknown 0 Fan #1 Speed: 5845.59 above high-limit 5750.00
To display Thermal, Fans and Power status:
> show system environmentals ----Thermal---- Slot Description Alarm Degrees C S0 Temperature at 3830 [U85] False 43.33 S0 Temperature at LION [U86] False 43.83 S0 Temperature at Phy [U87] False 38.33 S0 Temperature at CPLD [U88] False 44.50 ----Fans---- Slot Description Alarm RPMs S0 Fan #1 RPM False 14673 S0 Fan #2 RPM False 14465 S0 Fan #3 RPM False 14261 S0 Fan #4 RPM False 15004 ----Power---- Slot Description Alarm Volts S0 1.0V Power Rail False 0.98 S0 1.2V Power Rail False 1.20 S0 1.5V Power Rail False 1.51 S0 1.8V Power Rail False 1.80 S0 2.5V Power Rail False 2.48 S0 3.3V Power Rail False 3.31 S0 5.0V Power Rail False 5.02 S0 3.3V RTC Battery False 3.22
To check hardware alarm in logs:
> less mp-log ehmon.log * * Ehmon (v3.0) * Jan 07 01:54:26 Start time. Jan 07 01:54:28 Loading: libfans.so... done Jan 07 01:54:28 Loading: libpower.so... done Jan 07 01:54:28 Loading: libthermal.so... done Jan 07 01:55:28 Sensor Alarm [True ]: Fan #1 RPM = 8472 Jan 07 01:55:48 Sensor Alarm [False]: Fan #1 RPM = 8509 Jan 07 01:56:48 Sensor Alarm [True ]: Fan #1 RPM = 8437 Jan 07 01:57:28 Sensor Alarm [False]: Fan #1 RPM = 8544
Note: The alarm LED should clear when the condition that triggered it has cleared.