There are empty sockets in the network cabinet, so adding a camera looks straightforward. Then a device starts restarting after the expansion. Those empty sockets told you there was room for a cable. They did not tell you there was enough power.
To check a Power over Ethernet, or PoE, installation, compare three things: what each device needs, what its port can provide, and what all the devices need together. PoE lets compatible equipment receive power over a network cable, but the port count and power budget are separate limits.
Start with model numbers, not equipment families
A network switch is the box connecting wired devices. Two switches with the same number of sockets can have different powered ports, power standards and total budgets. Some models also change their available power depending on the installed supply. Read the label and exact specification before approving additions.
Do the same for each camera, wireless access point and other powered device. An access point is the device providing WiFi in an area. Record the full model and any accessory that draws power through it. A broad description such as outdoor camera is not enough to check compatibility.
Use the manufacturer's maximum requirement and any conditions attached to it. A current power reading can help diagnose the working installation, but it is a snapshot. It may not represent startup, additional radios, night illumination, a heater or another supported feature when enabled.
Check individual ports before adding the total
PoE has several standardized power modes. Labels such as PoE, PoE+ and PoE++ describe different capabilities, not interchangeable promises. The device and the power source need to support a compatible mode, and the usable power at the device can differ from the power supplied at the port.
A large total budget cannot compensate for a port that does not support the device's requirement. Conversely, a powerful individual port does not prove that every powered port can run at that level simultaneously. Both checks need to pass.
Be especially careful with older or passive power equipment, which may not negotiate power in the same way as standardized equipment. Have the installer verify compatibility from the specifications. Do not try an adapter merely because its connector fits.
Do not mix a device's received-power requirement with a switch's supplied-power figure without accounting for the manufacturer's definitions and cable losses. Ask for a consistent calculation, not just a column of watts with incompatible assumptions.
Build a power worksheet for the planned installation
List existing devices as well as additions. For each one, record the model, required power mode, specified maximum, intended port and cable route. Add any documented allowance needed to compare the device requirements with the switch budget on the same basis.
Then compare the aggregate requirement with the exact switch's available budget. Keep spare capacity for the approved expansion plan and operating conditions. There is no single spare percentage that proves every installation is adequate; the designer should explain the margin and what it covers.
If the plan exceeds either a port limit or the total budget, revise it before connecting equipment. A compatible injector, which adds power to one cable connection, or another suitably powered switch may be an option. Those choices add outlets, cabling and support considerations, so document them rather than hiding the problem behind the cabinet.
- Exact switch model, supply configuration and total available PoE budget.
- Device model, required power mode and maximum requirement.
- Assigned port and that port's supported power mode.
- Existing load, planned additions and documented spare capacity.
- Backup power requirements and the equipment that must remain online.
Do not confuse distributed power with backup power
A PoE switch still needs an electrical supply. If that supply stops, its powered devices can stop too. An uninterruptible power supply, or UPS, is a battery backed supply intended to keep selected equipment running for a limited period. Its capacity and runtime need their own assessment.
Decide what the business needs during an outage. Keeping a camera powered is not enough if its recorder is off. Keeping an access point online does not restore an internet connection whose upstream equipment has lost power. Ask for the whole required path to be listed and tested.
Avoid treating door equipment as just another spare load. Access control can involve lock supplies, safe exit and other requirements that need qualified design. A network power calculation is not approval to change door or life safety wiring.
Count the watts as carefully as the ports, and state which limit each number describes.Verify the completed system, then keep the record
At commissioning, check that each device negotiated the expected power and remains stable during the agreed test conditions. Include features likely to change demand and record any power warnings or restarts. A daytime dashboard screenshot alone cannot demonstrate every night mode or outage requirement.
If devices restart, investigate rather than assigning every failure to the power budget. The technician should also consider cable quality, termination, power supply condition and logs. Make one justified change at a time so the result can be attributed to it.
Keep the final port and power worksheet with the handover documents. When someone later asks for another camera, the office can identify the real remaining capacity instead of starting with the reassuring but incomplete fact that there is an empty socket.
Plan the next step with NeuroDesk
NeuroDesk's network infrastructure planning reviews equipment capacity, cable routes and room for expansion. Bring the exact switch model and the proposed camera or access point models. We can check the power plan before spare ports turn into another equipment order.
See our business network infrastructure planning for the relevant scope.
Sources and technical scope
The technical references below describe particular equipment and software. Features and limits must be checked against the installed model and configuration; they are not promises for every system.