CCNA 200-301

CCNP Enterprise

CCNP Security

CCIE Enterprise Lab

CCIE Security Lab

CCNP Service Provider

CCNP Data Center

CCNP Collaboration

CCIE DC Lab

Verifying whether a Cisco switch port is actively delivering Power over Ethernet (PoE)—and how much wattage remains in the switch’s overall power budget—is a routine task when deploying or troubleshooting IP phones, wireless access points, and security cameras. Whether you manage enterprise Catalyst switches via the command-line interface (CLI) or monitor Cisco Business and Meraki switches through a web browser, Cisco provides detailed telemetry down to the milliwatt level. Before inspecting individual port metrics, however, it helps to confirm that your switch hardware supports inline power and that its PoE standard matches your connected devices’ requirements.

How to Tell If a Cisco Switch Supports PoE

Before running diagnostic commands on an unresponsive port, confirm that the switch chassis and installed power supplies are physically capable of delivering inline power.

How can I tell if my Cisco switch model supports PoE from the part number?
Cisco encodes PoE capability directly into the switch Stock Keeping Unit (SKU) or Product ID (PID), typically using a letter suffix immediately following the port count:
* Data-Only (Non-PoE): Suffixes such as T (Catalyst 9000/1000 series, e.g., C9300-24T or C1000-24T-4G-L) or TS / S (legacy Catalyst 2960-X/3850 series, e.g., WS-C2960X-24TS-L) indicate data-only ports with no PoE hardware.
* PoE+ (Up to 30W per port): Suffixes containing P, LP, or FP indicate IEEE 802.3at PoE+ support. Examples include C9300-24P, C9200L-48P-4G, CBS350-24P-4G, and Meraki MS225-48FP (LP and FP denote Lite/Partial PoE vs. Full PoE budget across all ports).
* Cisco UPOE (Up to 60W per port): A U or UP suffix indicates universal power over Ethernet across all four twisted pairs (e.g., C9300-24U, WS-C3850-48U, or Meraki MS390-24UX).
* Cisco UPOE+ (Up to 90W per port): An H suffix on modular and fixed Catalyst 9000 switches (such as C9300-48H) denotes IEEE 802.3bt Type 4 high-power capability.

How do I verify PoE capability on the physical switch front panel?
Inspect the LED cluster near the Mode button on the left side of the switch faceplate. PoE-capable Catalyst switches feature a dedicated PoE status indicator alongside STAT, DUPLX, SPEED, and STACK. Pressing the Mode button until the PoE LED illuminates changes the behavior of the individual RJ-45 port LEDs:
* Solid Green: PoE is active and delivering power to a connected Powered Device (PD).
* Off: No PD is detected, or PoE is administratively disabled on the port.
* Alternating Green and Amber: PoE is denied because the switch’s total inline power budget has been exhausted.
* Blinking Amber: PoE has been shut down on the port due to a fault, short circuit, or overcurrent condition.

How can I check if a switch has PoE hardware via the CLI without checking the physical chassis?
Run show version or show inventory in EXEC mode to retrieve the exact chassis PID and installed power supply modules. Additionally, attempting to run show power inline on a data-only switch will either return an % Invalid input detected at '^' marker syntax error or display an empty output with 0.0 Available Watts.


Cisco PoE Standards, Classes, and Per-Port Wattage Limits

Once you confirm your switch supports PoE, you must ensure the port’s PoE tier can supply enough power for the connected endpoint. High-draw devices like pan-tilt-zoom (PTZ) cameras or tri-band Wi-Fi 6E/7 access points will fail to boot if connected to a standard 15.4W PoE port.

Cisco PoE TierIEEE StandardPoE ClassMax Power at Switch Port (PSE)Assured Power at Device (PD)Active Wire PairsTypical Powered Devices
Cisco Legacy Inline PowerPre-standard (Cisco Proprietary)N/A7.0 W~6.3 W2 pairsLegacy Cisco 7900 series IP phones, early Aironet APs
PoE (Type 1)IEEE 802.3afClass 0 (Default)15.4 W12.95 W2 pairsStandard VoIP phones, fixed indoor IP cameras
PoE (Type 1)IEEE 802.3afClass 14.0 W3.84 W2 pairsLow-power IoT sensors, basic wall phones
PoE (Type 1)IEEE 802.3afClass 27.0 W6.49 W2 pairsEntry-level IP phones, simple badge readers
PoE (Type 1)IEEE 802.3afClass 315.4 W12.95 W2 pairsDual-band 802.11ac APs, standard VoIP desk phones
PoE+ (Type 2)IEEE 802.3atClass 430.0 W25.5 W2 pairsVideo IP phones, Wi-Fi 6 APs, indoor PTZ cameras
Cisco UPOE (Type 3)IEEE 802.3bt / Cisco UPOEClass 545.0 W40.0 W4 pairsHigh-density Wi-Fi 6E APs, outdoor cameras with blowers
Cisco UPOE (Type 3)IEEE 802.3bt / Cisco UPOEClass 660.0 W51.0 W4 pairsCompact PoE-powered switches, VDI thin clients, multi-radio APs
Cisco UPOE+ (Type 4)IEEE 802.3btClass 775.0 W62.0 W4 pairsEnterprise Wi-Fi 7 APs, smart building PoE lighting controllers
Cisco UPOE+ (Type 4)IEEE 802.3btClass 890.0 W71.3 W4 pairsDaisy-chained PoE passthrough switches, digital signage displays

Key Takeaway: Always account for cable power loss over Cat5e/Cat6 runs (up to 100 meters). While a Class 4 PoE+ switch port allocates up to 30.0W at the switch (Power Sourcing Equipment, or PSE), only 25.5W is guaranteed to reach the Powered Device (PD).


How to Check PoE Port Status and Power Budget via Cisco CLI

Knowing the hardware capabilities and wattage tiers sets the stage for live diagnostics. On Cisco Catalyst switches running Cisco IOS or IOS XE, the show power inline command family provides real-time visibility into global power budgets and per-interface consumption.

Step 1: Check the Switch-Wide PoE Summary and Port Table

Log in to the switch CLI and run show power inline from User EXEC or Privileged EXEC mode to view both the chassis power budget and the status of every PoE-capable port:

Switch# show power inline
Available: 715.0(w)  Used: 68.2(w)  Remaining: 646.8(w)

Interface Admin  Oper       Power   Device              Class Max
                            (Watts)                            
--------- ------ ---------- ------- ------------------- ----- ----
Gi1/0/1   auto   on         15.4    AIR-AP2802I-B-K9    3     30.0
Gi1/0/2   auto   on         26.8    C9130AXI-B          4     30.0
Gi1/0/3   auto   off        0.0     n/a                 n/a   30.0
Gi1/0/4   static on         30.0    IP Camera           4     30.0
Gi1/0/5   off    off        0.0     n/a                 n/a   30.0
Gi1/0/6   auto   power-deny 0.0     n/a                 n/a   30.0

Understand each field in the output:
* Top Summary (Available / Used / Remaining): Shows the total inline wattage supplied by the switch’s power supplies, the sum of power currently allocated to active ports, and the remaining wattage available for new devices.
* Admin: The configured PoE mode on the interface:
* auto: Automatically detects a PD and allocates power up to the negotiated class limit.
* static: Pre-allocates the maximum configured wattage to the port from the switch budget, even if no device is plugged in.
* off: Inline power is administratively disabled (power inline never).
* Oper: The real-time operational state of the port:
* on: Power is actively flowing to the connected device.
* off: No PoE device is connected, or PoE is disabled.
* power-deny: A valid PD was detected, but the switch lacks sufficient Remaining wattage in its budget (or the device requested more than the port’s Max limit).
* faulty or err-disable: The port shut down due to an overcurrent draw or hardware short circuit.
* Power (Watts): The power currently allocated to or measured on the port. (Depending on your switch platform and CDP/LLDP state, this shows either the class cutoff allocation or real-time consumption).
* Device: The hardware model string reported via CDP or LLDP (Ieee PD appears if the device does not advertise a Layer 2 discovery name).
* Class: The IEEE 802.3 PoE class (0 through 8) negotiated during physical layer detection (as covered in the comparison table above).
* Max: The maximum wattage ceiling permitted on the port.

Step 2: Inspect Detailed PoE Metrics on a Single Port

To diagnose why a specific port is drawing unexpected wattage or failing negotiation, append the interface ID and the detail keyword:

Switch# show power inline gigabitethernet 1/0/2 detail
 Interface: Gi1/0/2
 Inline Power Mode: auto
 Operational status: on
 Device Detected: yes
 Device Type: C9130AXI-B
 IEEE Class: 4
 Discovery mechanism used/configured: Ieee and Cisco
 Police: on

 Power Allocated 
 Admin Value: 30.0
 Power drawn from the source: 26.8
 Power available to the device: 25.5

 Actual consumption
 Measured at the port: 14.2
 Maximum Power drawn by the device since powered on: 24.9

 Absent Counter: 0
 Over Current Counter: 0
 Short Current Counter: 0
 Invalid Signature Counter: 0
 Power Denied Counter: 0

Pay close attention to the difference between Power drawn from the source (26.8W, which is reserved against your switch’s PoE budget via IEEE Class or CDP/LLDP negotiation) and Measured at the port (14.2W, the actual electrical load at that exact second). Reviewing the Maximum Power drawn by the device since powered on and the fault counters (Over Current, Short Current, Invalid Signature) helps pinpoint intermittent cabling or hardware problems.

Step 3: Check Per-Switch PoE Budgets in a Stack

In a Cisco StackWise deployment, check the power budget for a specific stack member or inspect how power supplies are pooled using:

Switch# show power inline module 2
Switch# show env power all

show env power all verifies that all installed power supplies are operational (OK) and displays how much wattage is reserved for the switch system versus the PoE pool.


How to Check PoE Port Status via the Cisco Web GUI

If you prefer visual dashboards over the CLI—or if you manage cloud-native or small-business switches—you can check PoE consumption and port states through Cisco’s graphical interfaces.

1. Cisco Catalyst IOS XE WebUI (Catalyst 9000 & 1000 Series)

  1. Open a browser and log in to the switch’s management IP address via https://<switch-ip>.
  2. On the main Dashboard, locate the PoE summary widget to view a gauge of Total, Used, and Remaining wattage.
  3. For per-port telemetry, navigate to Monitoring > System > PoE in the left-hand menu.
  4. Review the interface table, which lists each port’s Admin State, Oper Status, Allocated Power (W), Device Type, and PoE Class.
  5. To modify a port’s inline power settings, go to Configuration > Interface > Ethernet, click the target port, and select the PoE tab.

2. Cisco Business (CBS250/CBS350) & Catalyst 1200/1300 Web GUI

  1. Log in to the switch web administration page. In the top-right corner, change the Display Mode dropdown from Basic to Advanced (if applicable).
  2. In the left navigation pane, go to Port Management > PoE > Properties (or Status and Statistics > PoE on newer firmware).
  3. At the top of the page, check the System Power Status table to see Nominal Power (total budget), Consumed Power (real-time draw), and Allocated Power.
  4. Scroll down to the Port Power Table to inspect individual interfaces. Here you can view whether PoE is Enabled, the Operational Status (Delivering Power, Searching, Disabled, or Fault), the Power Allocation (mW), and real-time Power Consumption (mW).

3. Cisco Meraki Cloud Dashboard (MS & Cloud-Managed Catalyst Switches)

  1. Sign in to dashboard.meraki.com and navigate to Switching > Monitor > Switches.
  2. Click the target switch from your inventory list.
  3. Near the top of the switch status page, check the Power bar (for example, 182W / 740W) to verify total PoE draw over the past 24 hours.
  4. Click the Ports tab (or click the port directly on the virtual switch faceplate graphic).
  5. Inside the port detail view, check the PoE line under the Status section to see if it reports Active along with the exact real-time wattage draw (e.g., 11.4 W). To see all ports at once, return to the multi-port list view, click the + (column configuration) icon on the right, and enable the PoE and Power draw columns.

Troubleshooting a Cisco PoE Port Not Providing Power

When the CLI or Web GUI reveals that a port is stuck in off, power-deny, or err-disabled despite a connected device, follow this sequential workflow to restore power.

Step 1: Verify PoE Is Administratively Enabled on the Port

If show power inline lists Admin as off, someone previously disabled inline power on that port. Re-enable automatic PoE detection:

Switch# configure terminal
Switch(config)# interface gigabitethernet 1/0/5
Switch(config-if)# power inline auto
Switch(config-if)# end

Step 2: Reset (Bounce) PoE Power on a Hung Device

If an IP camera or wireless access point is frozen (Oper shows on, but the device is unresponsive on the network), you can remotely power-cycle the physical port without unplugging the patch cable:

Switch# configure terminal
Switch(config)# interface gigabitethernet 1/0/1
Switch(config-if)# power inline never
! Wait 5 to 10 seconds for the device's internal capacitors to fully discharge
Switch(config-if)# power inline auto
Switch(config-if)# end

(Note: On newer IOS XE releases, you can also run hw-module beacon slot <number> port <number> to identify the port or bounce the interface directly with shutdown / no shutdown, though toggling power inline specifically forces the PoE controller to drop and renegotiate voltage).

Step 3: Clear ilpower Err-Disabled States and Check Logs

When a connected device draws more power than its negotiated cutoff limit—or if a damaged Ethernet cable causes a pin short—the switch’s PoE policing engine shuts down the port and places it into an ilpower error-disabled state.
1. Check for error-disabled ports and inspect the system log:
text
Switch# show interfaces status err-disabled
Switch# show logging | include ILPOWER

Look for messages such as %ILPOWER-3-CONTROLLER_PORT_ERR (often caused by bad cabling or a faulty PD) or %ILPOWER-5-ILPOWER_POWER_DENY.
2. After replacing a suspect patch cord or verifying the device’s wattage requirements, reset the port out of err-disabled by cycling the interface:
text
Switch# configure terminal
Switch(config)# interface gigabitethernet 1/0/6
Switch(config-if)# shutdown
Switch(config-if)# no shutdown
Switch(config-if)# end

3. Optionally, configure the switch to automatically recover from PoE faults after a timeout interval:
text
Switch(config)# errdisable recovery cause ilpower
Switch(config)# errdisable recovery interval 300

Step 4: Resolve power-deny and High-Wattage Negotiation Failures

If a port displays power-deny or a Wi-Fi 6/7 access point boots in low-power degraded mode (disabling its 5 GHz or 6 GHz radios), check three common configuration limits:
* Port Max Wattage Cap: Check if a manual cap was configured on the interface (power inline auto max <milliwatts>). Remove any restrictive cap by running default power inline under the interface configuration.
* Layer 2 Power Negotiation (CDP/LLDP): Many Class 4 (30W) and Class 6/8 (60W–90W) devices initially classify at a lower IEEE physical tier and rely on CDP or LLDP to request their full operational power. Ensure both protocols are active on the port:
text
Switch(config-if)# cdp enable
Switch(config-if)# lldp transmit
Switch(config-if)# lldp receive

* Four-Pair / UPOE Activation: On UPOE-capable switches powering 60W+ devices, verify that four-pair power delivery is enabled on the interface (power inline four-pair forced on older IOS XE releases, or verify IEEE 802.3bt negotiation on newer releases) and ensure the switch’s global power budget has enough Remaining watts. For mission-critical endpoints on a heavily loaded switch, assign high PoE priority (power inline port priority high) so those ports retain power if a power supply fails.


Cisco Catalyst PoE Command Reference and Official Documentation

For platform-specific syntax nuances, MIB definitions, and hardware release notes, consult the command reference summary and official Cisco documentation hierarchy below.

Core Cisco IOS / IOS XE PoE Command Summary

Command SyntaxCommand ModeFunction and Usage
show power inline [interface-id] [detail]User EXEC (>) or Privileged EXEC (#)Displays global inline power budget (Available, Used, Remaining) and per-port PoE operational states, classes, and measured wattage.
show power inline police [interface-id]Privileged EXEC (#)Displays real-time power policing thresholds, cutoff values, and overcurrent action configurations (errdisable vs. log).
show power inline priority [interface-id]Privileged EXEC (#)Displays port power priority assignments (low, high, critical) used during power supply budget brownouts.
power inline {auto [max max-wattage] \| never \| static [max max-wattage]}Interface Configuration (config-if#)Sets the administrative PoE mode on an interface. max-wattage is specified in milliwatts (e.g., 4000 to 30000 for PoE+, up to 60000 or 90000 on UPOE/UPOE+ ports).
power inline consumption default milli-wattsGlobal (config#) or Interface (config-if#)Overrides class-based power reservation and allocates a fixed milliwatt value from the switch budget (use with caution to avoid oversubscribing the PSU).
power inline police [action {errdisable \| log}]Interface Configuration (config-if#)Enables real-time hardware monitoring of actual port power draw against the cutoff threshold and defines the violation action.
power inline port priority {high \| low}Interface Configuration (config-if#)Prioritizes specific interfaces so they continue receiving power if a redundant PSU fails and total chassis capacity drops below demand.

Locating Official Cisco Platform Documentation

Cisco structures its PoE configuration manuals by switch family and IOS XE release train on cisco.com:
* Catalyst 9000 Series (9200, 9300, 9400): Navigate to Cisco Support > Switches > Catalyst 9300 Series Switches > Configuration Guides, select your installed Cisco IOS XE Release (e.g., IOS XE Dublin 17.12.x or IOS XE 17.15.x), and open the Interface and Hardware Components Configuration Guide > Configuring Power over Ethernet. This document covers Fast PoE, Perpetual PoE (which maintains inline power across switch warm reloads), and IEEE 802.3bt Type 4 UPOE+ behavior.
* Catalyst 1000 and Classic IOS (2960-X/XR): Refer to the Interface and Hardware Components Configuration Guide for Cisco IOS Release 15.2(7)E, specifically the chapter titled Configuring PoE and the EnergyWise / PoE Command Reference.
* Cisco Business (CBS250/350) and Catalyst 1200/1300: Consult the Administration Guide and CLI Guide for your specific model series under Small Business Support, which details the simplified OS syntax (show power inline and power inline {auto | never | limit}).


Conclusion

Checking a PoE port on a Cisco switch begins with confirming your hardware SKU and PoE class limits, followed by running show power inline and show power inline <interface> detail (or inspecting the PoE dashboard in the WebUI) to compare allocated versus actual wattage draw. By combining real-time port telemetry with targeted troubleshooting—such as enabling CDP/LLDP negotiation, clearing ilpower error-disabled states, and monitoring your chassis power budget—you can quickly isolate cabling faults and keep all powered endpoints running reliably.

Please follow and like us:
Last modified: November 17, 2026

Author

Comments

Write a Reply or Comment

Your email address will not be published.