Maintaining uninterrupted network uptime requires verifying that both primary and redundant power supply units (PSUs) are healthy, properly seated, and receiving stable AC or DC input power. Whether you are auditing dual-power redundancy before a maintenance window, calculating rack power draw, or investigating a syslog alarm, Cisco switches provide detailed environmental telemetry through the command-line interface (CLI) and Simple Network Management Protocol (SNMP).
Because command syntax and output fields vary across hardware families—and because engineers frequently confuse chassis power health with Power over Ethernet (PoE) port budgets—knowing the exact commands for your platform is essential. This guide covers the distinction between system and PoE power commands, platform-specific CLI templates for Cisco Catalyst (IOS/IOS-XE) and Cisco Nexus (NX-OS) switches, step-by-step hardware troubleshooting, SNMP monitoring OIDs, and official command reference specifications.
Table of Contents
System Power vs. PoE Power Commands and Status Definitions
When auditing power on a Cisco switch, you must distinguish between chassis hardware power (the physical AC/DC power supply modules feeding the switch backplane) and Power over Ethernet (PoE) allocation (the DC power delivered over RJ-45 ports to endpoints like IP phones, wireless access points, and cameras).
The following comparison outlines which command family to use based on the layer of power delivery you need to inspect:
| Criteria | show env power / show environment power | show power inline | show power detail / show stack-power |
|---|---|---|---|
| Primary Purpose | Verifies the physical health and operational state of internal/replaceable PSUs. | Monitors PoE power allocation and draw on individual switch interfaces. | Displays chassis power budgets, module consumption, and StackPower pooling. |
| Target Component | Power supply bays (1A, 1B, PS1, PS2) and internal PSU fans. | RJ-45 Ethernet ports (Gi1/0/1, Te1/0/1, etc.) and powered devices (PDs). | Switch backplane, supervisor engines, line cards, fan trays, and power stacks. |
| Key Metrics Displayed | PSU Part ID (PID), Serial Number, Status, System Power, PoE Power, Rated Wattage. | Available/Used/Remaining PoE Watts, Port Admin/Oper state, Device Class. | Instantaneous/Peak power, budgeted system power, and PSU redundancy mode. |
| Wattage Meaning | Rated maximum capacity of the PSU (e.g., 715W or 1100W), not live consumption on most Catalyst models. | Live or class-allocated wattage drawn by connected PoE endpoints. | Actual system draw vs. reserved hardware power budgets. |
| Typical Use Case | Confirming dual-PSU redundancy or diagnosing a failed power cord/PSU. | Troubleshooting an access point or IP phone that fails to power on. | Capacity planning for modular chassis or Catalyst StackPower rings. |
When interpreting the output of these commands, the switch reports specific operational states for both physical power supplies and PoE interfaces:
| Command Scope | Status Value | Meaning and Operational Impact |
|---|---|---|
Chassis PSU (show env power) | OK / Good | The power supply is detected, receiving valid input voltage, and delivering healthy output power. |
Chassis PSU (show env power) | Not Present | The power supply slot is empty (either unpopulated by design or the module cannot be read by the backplane). |
Chassis PSU (show env power) | No Input Power | A PSU is physically inserted in the slot, but no AC/DC voltage is detected on its power cord. |
Chassis PSU (show env power) | Disabled | The PSU is present and has input power, but it has been administratively turned off via the CLI. |
Chassis PSU (show env power) | Bad / Faulty | The power supply is unrecognizable or has suffered an internal hardware fault. |
Chassis PSU (show env power) | Fan Faulty | The PSU is generating power, but its internal cooling fan has failed, risking thermal shutdown. |
PoE Port (show power inline) | on / off | on indicates PoE is actively delivered to a connected device; off indicates no PoE device is active. |
PoE Port (show power inline) | fault / power-deny | fault indicates a short circuit or IEEE discovery error; power-deny means the switch lacks sufficient remaining PoE budget to power the port. |
Takeaway: Always use show env power (or show environment power) to validate physical PSU hardware and redundancy, and reserve show power inline for port-level PoE budget checks.
Checking Power Supply Status on Cisco Catalyst Switches (IOS and IOS-XE)
With the distinction between chassis power and PoE established, you can run platform-specific CLI commands to inspect PSU slots on Cisco Catalyst switches. On stackable access switches (such as the Catalyst 2960-X, 3850, 9200, and 9300 series), power supply slots are labeled by switch member number and bay letter (1A for Switch 1 Slot A, 1B for Switch 1 Slot B).
Use the following read-only CLI commands in privileged EXEC mode (Switch#) to check power supply health across fixed, stacked, and modular Catalyst platforms:
! 1. Check PSU status on a standalone Catalyst switch or active stack views
Switch# show env power
SW PID Serial# Status Sys Pwr PoE Pwr Watts
-- ------------------ ---------- --------------- ------- ------- -----
1A PWR-C1-715WAC LIT221010UE OK Good Good 715
1B PWR-C1-715WAC LIT221010UF OK Good Good 715
! 2. Check all PSU slots across every member in a Catalyst 9200/9300 stack
Switch# show environment power all
SW PID Serial# Status Sys Pwr PoE Pwr Watts
-- ------------------ ---------- --------------- ------- ------- -----
1A PWR-C1-1100WAC DCC2401A112 OK Good Good 1100
1B Not Present
2A PWR-C1-1100WAC DCC2401A119 OK Good Good 1100
2B PWR-C1-1100WAC DCC2401A120 No Input Power Bad Bad 1100
! 3. Narrow the output to a specific switch member in a stack (e.g., Member 2)
Switch# show environment power switch 2
! 4. Verify StackPower pooling and redundancy mode on Catalyst 9300/3850
Switch# show stack-power detail
! 5. Check PSU status, fan tray draw, and live wattage on modular/core Catalyst 9400/9500/9600
Switch# show environment status
Switch# show power detail
When reviewing the Catalyst CLI output above:
* Slot Identifiers (1A, 1B): Confirm that both A and B slots show OK and Good if the switch is designed for dual-PSU redundancy. Slot B is physically located closest to the outer edge of the chassis on Catalyst 9300 switches.
* Rated vs. Live Wattage: On Catalyst 9200 and 9300 series switches, the Watts column in show env power displays the rated capacity of the power supply, not live power draw. To view live input/output consumption on supported IOS-XE releases (17.8.1 and later) or Catalyst 9400/9500/9600 switches, use show power detail or show environment all.
Takeaway: Run show environment power all on stackable Catalyst switches to audit every member’s primary and redundant PSU slots in a single view.
Checking Power Supply Status and Wattage on Cisco Nexus Switches (NX-OS)
Unlike fixed Catalyst switches that primarily display rated PSU capacity in their basic environment tables, data center Cisco Nexus switches (such as the Nexus 9000, 7000, and 3000 series running NX-OS) report both Actual Output, Actual Input, and Total Capacity alongside the configured vs. operational power redundancy modes in a single command.
Use the following NX-OS CLI commands to inspect PSU health, live power consumption, and redundancy states:
! 1. View PSU status, live input/output wattage, and redundancy mode on NX-OS
nexus-9300# show environment power
Power Supply:
Voltage: 12 Volts
Power Actual Actual Total
Supply Model Output Input Capacity Status
(Watts ) (Watts ) (Watts )
------- ------------------- ---------- ---------- ---------- --------------
1 NXA-PAC-650W-PE 92 W 104 W 650 W Ok
2 NXA-PAC-650W-PE 94 W 104 W 650 W Ok
Power Usage Summary:
--------------------
Power Supply redundancy mode (configured) PS-Redundant
Power Supply redundancy mode (operational) PS-Redundant
Total Power Capacity (based on configured mode) 650.00 W
Total Power of all Inputs (cumulative) 1300.00 W
Total Power Output (actual draw) 186.00 W
Total Power Input (actual draw) 208.00 W
Total Power Allocated (budget) N/A
Total Power Available for additional modules N/A
! 2. View granular PSU sensor details and hardware thresholds
nexus-9300# show environment power detail
! 3. Configure PSU redundancy mode (if operational mode does not match design)
nexus-9300# configure terminal
nexus-9300(config)# power redundancy-mode ps-redundant
nexus-9300(config)# copy running-config startup-config
Key fields to verify on Nexus switches include:
* Configured vs. Operational Redundancy Mode: Ensure both lines match (e.g., PS-Redundant for N+1 PSU protection, Insrc-Redundant for grid/input source redundancy, or Combined for full non-redundant capacity). If configured is PS-Redundant but operational drops to Non-Redundant, one PSU has failed or total chassis load has exceeded a single PSU’s capacity.
* Actual Input vs. Actual Output: Actual Input reflects the AC/DC power drawn from the rack PDU, while Actual Output reflects the 12V DC power delivered to the switch backplane; the difference represents normal PSU conversion inefficiency (typically 10% to 17%).
Takeaway: On Cisco Nexus switches, always verify that the operational redundancy mode matches the configured mode and that live Total Power Output remains below the single-PSU capacity threshold (Total Power Capacity based on configured mode).
Troubleshooting Faulty, Bad, or No Input Power Supply States
When a CLI check reveals a non-normal state—such as No Input Power, Bad, Disabled, or None—follow this sequential diagnostic workflow to isolate whether the failure lies in the CLI configuration, upstream rack power, thermal sensors, or the PSU hardware itself.
Step 1: Check CLI Administrative State and Syslog History
On Catalyst switches, a power supply slot can be administratively disabled in software even when physically plugged in. Check recent environmental syslog events (%PLATFORM_ENV on IOS-XE or %PLATFORM-4-PFM_PS on NX-OS) and re-enable the slot if it shows Disabled:
* Check logs: show logging | include ENV|POWER|FRU|PFM_PS
* Re-enable an IOS-XE PSU slot: power supply <switch-number> slot {A | B} on (e.g., power supply 1 slot B on).
Step 2: Inspect PSU Fan and Temperature Sensors
A power supply will automatically shut down to protect the chassis if its internal blower fails or ambient intake temperatures exceed critical thresholds.
* Run show env fan and show env temperature (or show environment all on IOS-XE; show environment fan and show environment temperature on NX-OS).
* If the status reads Fan Faulty or a thermal sensor is in a CRITICAL/SHUTDOWN state, clear any airflow obstructions at the rack exhaust/intake and prepare to replace the PSU.
Step 3: Verify Physical PSU LED Indicators
Before pulling any cables, inspect the physical LEDs on the faceplate of the power supply module:
* Solid Green (OK / AC OK): Input power is within valid voltage range and the PSU is operating normally.
* Off: No AC/DC input power is reaching the supply, or the entire switch is unpowered.
* Blinking Amber / Blinking Red: On a dual-PSU switch, this typically indicates that one PSU has lost input power while the second PSU is actively powering the chassis, or the supply is administratively disabled.
* Solid Amber / Solid Red (Fault): The PSU has experienced an internal hardware fault, over-voltage, over-current, or over-temperature shutdown and requires replacement.
Step 4: Isolate Upstream Cords, PDUs, and Brownout Lockups
If the CLI reports No Input Power (or Shutdown/None on NX-OS):
1. Ensure the power cord retention clip is secure and the C13/C15/C19 connector is fully seated in the PSU inlet.
2. Swap the power cord to a known-good outlet on the rack PDU to rule out a tripped circuit breaker or dead PDU receptacle.
3. Reseat the PSU module: On certain Cisco Nexus 9000 (e.g., NXA-PAC-650W under CSCwi62100) and Catalyst platforms, a brief upstream voltage brownout can cause a PSU to report as None or Bad in the CLI even while its physical LED remains green. Unplug the power cable, unlatch and slide the PSU out of the bay for 15 seconds, firmly reseat it until the latch clicks, and reconnect the power cord.
Step 5: Confirm Hardware Detection for RMA (show inventory)
If reseating the unit and verifying AC/DC input voltage does not clear a Bad, Faulty, or unexpected Not Present state, run show inventory. If the PSU’s PID and Serial Number fail to populate in show inventory while seated in a known-good slot, open a Cisco TAC case for an RMA replacement.
Takeaway: Correlate CLI status messages with physical PSU LEDs and power cord checks before replacing hardware, as No Input Power and brownout-induced None states are most often resolved by restoring upstream feed or reseating the module.
Monitoring Cisco Switch Power Supplies via SNMP OIDs and Traps
Rather than relying on manual CLI checks, network engineers should poll PSU status continuously and enable automated SNMP traps in monitoring platforms (such as SolarWinds, PRTG, Zabbix, Nagios, or LibreNMS). Cisco switches expose power supply health primarily through CISCO-ENVMON-MIB (for fixed/stackable switches) and CISCO-ENTITY-FRU-CONTROL-MIB (for modular Catalyst and Nexus switches).
Use the following SNMP OIDs, snmpwalk commands, and switch configuration templates to set up automated alerting:
# 1. Poll CISCO-ENVMON-MIB Power Supply Description & Operational State
# ciscoEnvMonSupplyStatusDescr: .1.3.6.1.4.1.9.9.13.1.5.1.2
snmpwalk -v2c -c <COMMUNITY_STRING> <SWITCH_IP> 1.3.6.1.4.1.9.9.13.1.5.1.2
# ciscoEnvMonSupplyState: .1.3.6.1.4.1.9.9.13.1.5.1.3
# Returns CiscoEnvMonState Integer:
# 1 = normal | 2 = warning | 3 = critical | 4 = shutdown | 5 = notPresent | 6 = notFunctioning
snmpwalk -v2c -c <COMMUNITY_STRING> <SWITCH_IP> 1.3.6.1.4.1.9.9.13.1.5.1.3
# ciscoEnvMonSupplySource: .1.3.6.1.4.1.9.9.13.1.5.1.4
# Returns: 1 = unknown | 2 = ac | 3 = dc | 4 = externalPowerSupply | 5 = internalRedundant
snmpwalk -v2c -c <COMMUNITY_STRING> <SWITCH_IP> 1.3.6.1.4.1.9.9.13.1.5.1.4
# 2. Poll CISCO-ENTITY-FRU-CONTROL-MIB (Modular Catalyst 9400/9600 & Nexus NX-OS)
# cefcFRUPowerOperStatus: .1.3.6.1.4.1.9.9.117.1.1.2.1.2
# Returns PowerOperType Integer (e.g., 1 = offEnvOther, 2 = on, 3 = offAdmin, 4 = offDenied, 5 = offEnvPower)
snmpbulkwalk -v2c -c <COMMUNITY_STRING> <SWITCH_IP> 1.3.6.1.4.1.9.9.117.1.1.2.1.2
To ensure the switch immediately pushes an alert when a redundant PSU fails or loses input power, apply this configuration template on the switch:
! Enable SNMP environmental and FRU power supply traps on Cisco IOS / IOS-XE
Switch(config)# snmp-server enable traps envmon supply fan temperature
Switch(config)# snmp-server enable traps fru-ctrl
Switch(config)# snmp-server host <NMS_SERVER_IP> version 2c <COMMUNITY_STRING> envmon fru-ctrl
Takeaway: Configure your NMS to poll 1.3.6.1.4.1.9.9.13.1.5.1.3 (ciscoEnvMonSupplyState) and trigger a high-priority alert whenever the returned integer deviates from 1 (normal).
Official Cisco Command Reference and Hardware Documentation Specifications
For formal syntax verification, release-specific MIB behavior, and physical chassis specifications, consult the following command reference definitions and official Cisco documentation manuals:
- Command Syntax (Cisco IOS / IOS-XE):
show environment power [all | switch switch-number] - Syntax Description:
all— (Optional) Displays the internal power supply status for all switches in a StackWise or StackWise Virtual ring.switch switch-number— (Optional) Displays the internal power supply status only for the specified stack member. Valid range is1to9(or1to16depending on platform architecture).
- Command Mode: User EXEC (
Switch>) or Privileged EXEC (Switch#). - Command Syntax (Cisco NX-OS):
show environment power [detail] - Syntax Description:
detail— (Optional) Displays extended hardware telemetry, including cord connectivity, voltage/current sensor thresholds, and internal PSU temperature.
- Command Mode: Any command mode (
switch#). - Primary Official Documentation References:
- Cisco Catalyst 9300 Series Switches Hardware Installation Guide — Contains physical PSU installation procedures, AC/DC input voltage requirements, acoustic/thermal specifications, and front/rear PSU LED state tables.
- System Management Configuration Guide, Cisco IOS XE (“Configuring Internal Power Supplies” module) — Details CLI administration of internal PSUs (
power supply switch-number slot {A | B} {on | off}) andshow env powerfield definitions. - Cisco Nexus 9000 Series NX-OS Fundamentals and Environment Command Reference — Defines NX-API and CLI outputs for
show environment power, power usage summary calculations, and redundancy mode configurations.
Takeaway: Match your switch’s exact PID and software train against Cisco’s Hardware Installation Guide and System Management Command Reference to verify model-specific sensor support.
Conclusion
Checking power supply status on a Cisco switch is a straightforward process once you pair the right command with your hardware platform. Use show environment power all on stackable Catalyst switches and show environment power on Nexus switches to audit physical PSU health, input/output wattage, and redundancy modes, while keeping show power inline dedicated to port-level PoE diagnostics. By combining routine CLI verification with physical LED checks and proactive SNMP polling on ciscoEnvMonSupplyState, you can detect single-feed failures early and prevent unexpected network outages.











Comments