PoE Standards

Power over Ethernet (PoE) is a technology that enables Ethernet cables to carry both data and electrical power simultaneously. It was developed to simplify the deployment of network devices that require power, such as IP phones, wireless access points, and IP cameras, by eliminating the need for separate power cables and outlets. PoE is standardized by the IEEE under 802.3af (original PoE), 802.3at (PoE+), and 802.3bt (PoE++ or 4PPoE). Cisco also has proprietary implementations like Cisco Inline Power, but modern networks use IEEE standards.

PoE operates at the physical layer but involves a negotiation process before power is delivered. The process consists of four stages: Detection, Classification, Startup, and Operation.

#### Detection When a device is connected to a PoE-enabled port, the Power Sourcing Equipment (PSE) – typically a switch – sends a low-voltage signal (2.8V to 10V) to detect a valid Powered Device (PD). The PD must present a 25kΩ signature resistor (with a tolerance of ±5%) between the pairs. If the PSE detects this resistance, it proceeds; otherwise, it does not apply power, protecting non-PoE devices.

#### Classification After detection, the PSE applies a voltage between 15.5V and 20.5V to classify the PD's power requirements. The PD responds by drawing a specific current, which maps to a power class:

The classification is used by the PSE to allocate power budget. If the PD does not support classification, it defaults to Class 0.

#### Startup Once classification is complete, the PSE ramps up voltage to the nominal 48V DC (range 44-57V) within 400ms. The PD must present a load within 500ms to avoid power removal.

#### Operation During normal operation, the PSE continuously monitors the current draw. If the current drops below a minimum threshold (e.g., 5mA for 350ms), the PSE removes power (disconnect detection). This ensures safe disconnection when the PD is unplugged.

Cisco switches have a total PoE power budget (e.g., 370W for a Catalyst 2960X-24PD-L). The switch allocates power per port based on classification or configured maximum. If the total requested power exceeds the budget, the switch may deny power to new devices or use a priority scheme (low, high, critical) to shed power from lower-priority ports.

To verify PoE status on a Cisco switch, use the following commands:

Switch# show power inline

Sample output:

Available:370.0(w)  Used:52.0(w)  Remaining:318.0(w)
Interface Admin  Oper       Power   Device              Class Max
---------------------------------------------------------------------
Gi0/1    auto   on         15.4    IP Phone 7960        3     30.0
Gi0/2    auto   on         4.0     Cisco AIR-AP1131     1     30.0
Gi0/3    auto   off        0.0     n/a                  n/a   30.0

Switch# show power inline gigabitEthernet 0/1 detail

Provides detailed information including measured current, voltage, and power.

Switch# show power inline police

Displays power policing status (action when PD draws more than allocated).

PoE interacts with EtherChannel, VLANs, and QoS. For example, if a port is part of an EtherChannel, PoE configuration must be consistent across member ports. PoE also affects PoE devices that use LLDP-MED for advanced power negotiation (LLDP-MED can advertise power requirements up to 100W). Cisco switches support both legacy classification and LLDP-MED.

In enterprise networks, PoE is almost ubiquitous for IP telephony, wireless, and surveillance. Consider a medium-sized office with 200 IP phones and 50 wireless access points (APs). Each IP phone consumes about 6.3W (Class 2) and each AP about 15.4W (Class 3). Total PoE requirement: (200*6.3) + (50*15.4) = 1260 + 770 = 2030W. A single Catalyst 9300-48P switch has a PoE budget of 1440W, so you would need two such switches to power all devices, or use PoE injectors for some APs. The network engineer must calculate the power budget carefully and possibly use power management features like power policing or priority to ensure critical devices (e.g., phones for emergency calls) stay powered.

Another scenario: deploying PoE++ for high-power devices like pan-tilt-zoom (PTZ) cameras or digital signage. These require up to 60W (Type 3) or 100W (Type 4). Not all switches support PoE++; you may need a dedicated PoE++ switch or use midspan injectors. Misconfiguration here can lead to insufficient power, causing devices to reboot or fail to operate. For example, if you connect a 60W camera to a switch that only provides 30W per port, the camera may not power up or may operate erratically.

A common real-world problem: when a switch's power budget is exceeded, it may shut down lower-priority ports. This can cause unexpected outages. Engineers configure priority using the power inline priority command (critical, high, low) to ensure essential devices remain powered. Also, monitoring with SNMP and syslog alerts on PoE status is standard practice. In large deployments, power budgeting is integrated into network management tools that track per-switch and per-port power consumption.

Finally, consider the impact of cable length. While PoE can theoretically work up to 100 meters, voltage drop increases with distance. For high-power PoE++ (100W), shorter cables or higher-gauge wires (e.g., Cat6a) are recommended to minimize loss. In practice, most enterprise cabling runs are under 90 meters, so this is rarely an issue, but it's a consideration for outdoor cameras or long runs.