PoE Not Working? A Six-Step Fault-Finding Path for CCTV Switches

"The camera has no power" describes a symptom, not a fault. In practice there are six distinct causes, and they are best eliminated in a fixed order, because each step narrows what the next one can be. Doing it in this order usually takes ten minutes; doing it at random can take a day.

1. Confirm the port is really a PoE port

It sounds trivial and it is the most common mistake on mixed switches. Ports are often grouped — for example 8 PoE ports plus 2 uplinks — and the uplink ports will never supply power. Check the port numbering on the front panel, not the marketing headline ("8-port PoE switch" may mean 4 PoE + 4 uplink).

2. Watch what the port reports during negotiation

A working PoE port runs a short detection-and-classification sequence before it applies power. Managed switches show this in the port status: detecting, class X, power good, or denied. If the port reports "denied" or "class 0" for a camera that should be class 4, the answer is usually the camera or the cable, not the switch.

Port statusWhat it meansNext step
No linkpair / cable / connector faulttest the cable, then the camera on another port
Link, no powerdetection failed — PD signature not seencamera fault, or non-standard PD
Power denied / class mismatchrequested class exceeds port capabilitymatch port standard to PD class
Power applied, camera rebootsovercurrent or budget exhaustedmeasure draw, check total budget

3. Check the total budget, not just the port

PoE budget is shared. A 120 W switch with eight 15 W cameras is at its ceiling before any headroom, and the ninth camera gets refused even though its own port has capacity. Add the switch's own consumption, then keep 25–30% headroom for night draw.

4. Test the cable properly

PoE is sensitive to resistance in a way data-only Ethernet is not: the camera may link fine and still brown out under load. Copper-clad aluminium (CCA) cable, long runs, poor crimps and water in a connector all show up as voltage drop rather than as a dead link.

5. Isolate the PD

Put the suspect camera on a known-good port with a short patch lead. If it powers up there, the camera is fine and the fault is in the run, the port or the budget. If it fails on a good port, check whether the camera needs more than the port offers — a heated PTZ on an af port will not run, however good the cable.

6. Then look at configuration

Only after the electrical path is proven should you touch software. The usual culprits: PoE disabled per port, a per-port power limit set too low, a scheduled port shutdown, or a storm of spanning-tree / loop events that bounced the port.

Managed units with per-port class reporting make steps 2 and 3 fast, which is the practical argument for the L2/3 managed PoE range on larger sites. For small cabinets the unmanaged PoE switches are enough — you just diagnose with a meter instead of a UI.

Send the camera model, the run length and the switch model, and we will tell you whether the port can carry it. Ask for a quote.

FAQ

The camera works on a short cable but not on the installed run. Why?

Voltage drop. PoE loses power over distance, and CCA cable or a poor termination can push the camera below its minimum input. Measure voltage at the camera under load and replace CCA cable with solid copper.

Can I power a 30 W camera from an 802.3af port?

No. The port will refuse or the camera will brown out. Use an 802.3at port for class-4 devices.

Why does the camera drop only at night?

IR illuminators add several watts. The site is running without headroom, so the extra night draw pushes total consumption past the budget.

Is a PoE injector a valid test tool?

Yes, for a single camera — a known-good injector isolates the switch from the camera quickly. It is not a permanent fix for a multi-camera cabinet.

Detaillierte technische Daten werden auf Englisch bereitgestellt.

← Wissen
WhatsApp