Get AI summaries of any video or article — Sign up free
why Power over Ethernet (PoE) is amazing!! // FREE CCNA // EP 12 thumbnail

why Power over Ethernet (PoE) is amazing!! // FREE CCNA // EP 12

NetworkChuck·
5 min read

Based on NetworkChuck's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.

TL;DR

PoE combines network data and electrical power over one Ethernet cable, letting network engineers deploy and relocate powered devices without running separate power wiring.

Briefing

Power over Ethernet (PoE) turns one Ethernet cable into a combined “power + data” link, eliminating the need to run separate electrical wiring for phones, wireless access points, cameras, and even switches. The practical payoff is straightforward: network engineers can deploy and relocate powered devices using the same cabling infrastructure that already carries network traffic—cutting cost, labor, and coordination with electricians.

PoE’s roots trace back to the problem of powering IP phones. Cisco wanted to avoid running two cables—one for power and one for network—so it merged those functions into a single connection. In PoE terminology, the switch is the PSE (power sourcing equipment), while the powered endpoint is the PD (powered device). The mechanism relies on Ethernet cabling pairs that historically weren’t used for data. Early implementations used spare wire pairs in Cat5-era cabling to deliver power alongside the data signal.

Standardization changed PoE from a Cisco-only feature into an industry-wide capability. The IEEE ratified the first PoE standard in 2003 as 802.3af (often written 802.af), delivering roughly 15.4 watts per port—enough for many phones. As device power demands rose, 802.3at (802.at) arrived in 2009, doubling available power to about 30 watts per port (Type 2 PoE / PoE+). Later, higher-power needs pushed further: 802.3bt (802.bt) expanded delivery to about 60 watts (Type 3) by using more wire pairs, and then up to about 90 watts (Type 4) in the highest-power mode. That higher ceiling enables more than just networking gear—lighting systems, and even building HVAC components—while still using the same Ethernet cabling model.

A key operational detail is how switches manage power safely. PoE comes in two broad control modes: active and passive. Active PoE negotiates power requirements with the PD using discovery protocols. Cisco’s Cisco Discovery Protocol (CDP) and the industry-standard Link Layer Discovery Protocol (LLDP) help devices “handshake” so the switch supplies the appropriate power level. Passive PoE is simpler and always-on (often described as 24 volt PoE), which can be risky for devices that don’t expect that power.

On Cisco switches, PoE behavior is visible in the command-line interface. When a PD is connected, syslog messages indicate detection and power grant, followed by interface and line-protocol state changes. Power budgeting matters: switches have finite total wattage, so too many high-draw devices can leave ports unable to power up. Cisco’s “show power inline” output helps track available power, per-port consumption, and device power class ranges. In practice, even when a port is configured for a maximum wattage, the PD may receive less due to cable losses.

The bottom line: PoE is a standardized, power-managed way to deliver network connectivity and electricity over the same cable plant. It reduces installation friction, supports higher-power equipment over time, and—when using active negotiation—keeps power delivery aligned to what connected devices can safely use.

Cornell Notes

Power over Ethernet (PoE) lets a switch deliver both data and electrical power to an endpoint using a single Ethernet cable. The switch acts as the PSE (power sourcing equipment) and the device acts as the PD (powered device), with power delivered over Ethernet pairs that can carry power alongside data. PoE standards progressed from 802.3af (~15.4W) to 802.3at (~30W) and then to 802.3bt, reaching about 60W (Type 3) and up to about 90W (Type 4). Active PoE negotiates required power using discovery protocols such as CDP and LLDP, while passive PoE is always-on and can be risky. PoE also requires power budgeting on the switch; “show power inline” reveals available wattage, per-port draw, and why some devices may fail to power up.

What are the PSE and PD roles in PoE, and why does that matter for troubleshooting?

In PoE, the switch is the PSE (power sourcing equipment) and the endpoint is the PD (powered device). Troubleshooting often starts by checking whether the PSE detected the PD, granted power, and brought the interface up. Cisco CLI output and syslog messages typically show steps like “power device detected,” “power granted,” and then interface/line-protocol state changes. If power is not granted, the PD won’t function even if the data path exists.

How did PoE evolve from early implementations to IEEE standards?

Early PoE used unused wire pairs in Cat5-era cabling to send power alongside data. Standardization then moved it into IEEE control: 802.3af (ratified in 2003) provided about 15.4 watts per port (Type 1). 802.3at (2009) increased power to about 30 watts per port (Type 2 / PoE+). 802.3bt expanded power further by using more twisted pairs, reaching about 60 watts (Type 3) and up to about 90 watts (Type 4).

What’s the difference between active PoE and passive PoE, and how does negotiation work?

Active PoE negotiates power with the PD so the switch supplies an appropriate amount of power. Cisco Discovery Protocol (CDP) and Link Layer Discovery Protocol (LLDP) support discovery and negotiation; Cisco devices often default to CDP for phones and access points, while many third-party devices use LLDP. Passive PoE is always-on (commonly described as 24 volt PoE) and does not negotiate; connecting a device that doesn’t expect that power can fry it.

Why can a switch fail to power some devices even if each port is “capable” of high wattage?

Switches have a finite total power budget. Even if each port can output up to the configured maximum, the sum of power draws across all powered ports may exceed the switch’s available wattage. In that case, syslog messages and “show power inline” output can show remaining power dropping to zero and ports failing to power up. The transcript highlights a real-world scenario where too many phones prevented additional phones from powering due to insufficient remaining power.

What does “show power inline” tell you, and why might the PD receive less than the port’s configured maximum?

“show power inline” reports total available PoE power, remaining power, and per-port consumption, including device power class information. Even when a port is configured for a maximum (for example, 15.4W), the PD may receive less—commonly due to cable losses over the Ethernet run and transport overhead.

What happens when a PD tries to draw more power than the interface allocation on a Cisco switch?

When a PD exceeds the configured power limit, the port enters an error disabled state and a syslog/log message is generated. The transcript’s practice question frames this as the best description of the outcome when power draw exceeds allocation.

Review Questions

  1. When a PoE device is connected to a Cisco switch, what sequence of events (detection, power grant, interface/line protocol) would you expect to see in syslog or CLI output?
  2. Compare 802.3af, 802.3at, and 802.3bt in terms of approximate watts per port and which “Type” each corresponds to.
  3. Why might a PD not receive the full wattage that a PoE port is configured to provide, and how would you verify power draw on the switch?

Key Points

  1. 1

    PoE combines network data and electrical power over one Ethernet cable, letting network engineers deploy and relocate powered devices without running separate power wiring.

  2. 2

    Cisco’s PoE model uses a PSE (switch) to supply power and a PD (endpoint) to receive it; detection and power grant are key early steps.

  3. 3

    IEEE standards expanded PoE power over time: 802.3af (~15.4W), 802.3at (~30W), and 802.3bt (about 60W and up to about 90W in higher modes).

  4. 4

    Active PoE negotiates power needs using discovery protocols like CDP and LLDP; passive PoE is always-on and can damage devices that don’t support it.

  5. 5

    PoE requires power budgeting at the switch level; total available wattage can limit how many high-draw ports can power up simultaneously.

  6. 6

    Cisco CLI tools such as “show power inline” reveal available/remaining power, per-port draw, and device power class information.

  7. 7

    If a PD attempts to draw more than the allocated power, the port can enter an error disabled state and generate a log message.

Highlights

PoE turns one cable into both connectivity and power, removing the need for separate electrician-run power lines for phones, cameras, and access points.
Active PoE uses discovery/negotiation (CDP/LLDP) so the switch supplies the right power level—reducing the risk of frying devices.
Higher-power PoE standards (802.3bt) enable powering beyond networking gear, including lighting and potentially HVAC components.
Switch power budgeting is real: “show power inline” can show remaining wattage hitting zero, preventing additional devices from powering up.

Topics

  • Power Over Ethernet
  • PoE Standards
  • Active vs Passive PoE
  • PoE Power Budgeting
  • Cisco PoE CLI

Mentioned