The problem PoE had to solve
Ethernet cabling was designed for data, and devices at the end of it — phones, then cameras, then access points — needed power from somewhere. Running separate power to each meant an adapter, an outlet and an electrician at every device. Power over Ethernet's insight was that the cable already reaches the device; the engineering problem was delivering meaningful DC power over data pairs without endangering the decades of non-PoE equipment already plugged into the world's networks. The solution is a negotiation, and it happens in milliseconds, every time a device is plugged in.
A PoE switch port is therefore not 'live' in the way a wall socket is. It begins each connection at a whisper — low-voltage probes — and only escalates when the device at the other end proves, electrically, that it is a PoE device asking for power.
The three-act handshake
Detection. The switch applies a small probe voltage and measures the resistance signature presented by the device. A standards-compliant powered device (PD) presents a precise 25 kΩ signature. Anything else — a laptop, a printer, a wet cable — fails the test, and the port stays a plain data port, forever harmless. This is the mechanism behind the guarantee that PoE cannot damage non-PoE equipment.
Classification. The device then signals its power class — how much it may draw (classes run from a few watts in 802.3af to 71W at the device in 802.3bt Type 4). The switch grants the class if its per-port limit and remaining total budget allow; in finer-grained systems, LLDP negotiation can trim the grant to the device's stated need. Delivery. Only now does the port rise to full voltage (nominally 48V DC, delivered on the data pairs — and on all four pairs for bt). The switch keeps supervising: overload, short-circuit or disconnect, and the port shuts down or returns to probing. That supervision is also what lets watchdog-equipped switches notice a silent device and restart it.
From the port to the system
Scale the handshake by 24 ports and the switch's real jobs appear: it is simultaneously a data fabric (switching capacity, forwarding rate, MAC table — the numbers every datasheet leads with) and a power plant with a fixed total output, allocating class grants against a shared budget. This dual nature explains every PoE design rule on this site: budget by the sum (the power plant is shared), class by the hungriest device (each port negotiates alone), and never fear the mixed estate (every port negotiates for itself).
It also explains the ecosystem around the switch: injectors give a non-PoE port the same three-act ability for one link; splitters perform the reverse separation for a device that cannot negotiate; extenders re-drive both data and granted power down the next span. All of it is the same diplomacy, conducted at 48 volts, in milliseconds, billions of times a day.
Where the negotiation can go wrong
Understanding the handshake explains its failure modes, which are the field faults in our troubleshooting guide wearing their true names. A device that presents a dirty signature (corroded contacts, water in a junction) may negotiate intermittently — power that comes and goes with the weather. A device that classifies honestly but draws beyond its class in a heater-on surge can trip a strict port while working on a lenient one — which is why 'it worked on the old switch' proves less than it seems. And a switch whose total budget is exhausted does not fail loudly; it simply refuses the next negotiation, leaving the last device dark and the installer blaming the camera.
Each failure is the diplomacy breaking at a different act — detection, classification, or the budget ledger behind delivery. Diagnosing in that order, with a known-good device to conduct a clean negotiation on a suspect port, resolves most of them in minutes. The protocol was designed to be safe and legible; the systems built on it reward people who read it the same way.
The pairs themselves: how power rides the cable
A detail the handshake story skips: where, physically, the power travels. In 10/100M Ethernet only two of the cable's four pairs carry data, so early PoE could use the spare pairs (Mode B) or share the data pairs through centre-tapped transformers (Mode A) — both are standardised, and datasheets still disclose pin assignments (1/2 and 3/6 in the models quoted on this site). Gigabit uses all four pairs for data, so power always shares the data pairs via the transformers' centre taps — the phantom power technique, invisible to the data signal. 802.3bt extends delivery across all four pairs, which is both how it reaches 90W and why cable heating enters its design rules.
For the practitioner, pair mechanics matter at exactly two moments: when a datasheet's pinout must match a legacy device's expectation (the standards-compliant devices negotiate either mode; some legacy gear does not), and when non-standard patch panels or two-pair cabling — installed by optimists for 'data only' — silently amputate a bt link to at speeds or refuse it power entirely. Four good pairs, certified: the whole cathedral of negotiation rests on that unglamorous foundation.
The idea, compressed
A PoE port is a careful power supply wearing a network interface: it probes before it powers, grants by class, supervises while it delivers, and never energises a device that has not identified itself as a power consumer. That caution is why a single cable can safely carry a building's cameras, radios and phones — and why the design rules built on top of it (budgets by sum, classes by device, distances by physics) work at all. Understand the negotiation and the rest of PoE is bookkeeping; skip it, and every fault looks like magic until someone explains the handshake.
One last practical note for the buyer who skipped to the end: the handshake's elegance is why you should demand standards compliance and published figures from every element of a PoE system — switch, injector, splitter, device. Equipment that implements the negotiation honestly interoperates with strangers' equipment for a decade; equipment that approximates it creates the folklore of 'that camera only works with that switch'. There is no such folklore in a standards-true estate — there is arithmetic, and it either closes or it does not. Buy the arithmetic, and the little 48-volt diplomats at every port will do the rest, silently, for years.
It is worth pausing on how unusual this is in the history of infrastructure. Power distribution and data networking grew up as separate trades, with separate codes, separate contractors and separate ideas of safety. PoE merged them at the exact point where the modern building needed them merged — the device edge — and it did so not by decree but by a negotiation protocol conservative enough that two industries could both sign it. Every camera that lights up on a single cable is that treaty being honoured one more time.