PoE Switch Basics: Powering IP Cameras and Wireless Access Points

Power over Ethernet (PoE) has become the standard method for deploying IP cameras, wireless access points, VoIP phones, and other networked devices in commercial and industrial settings. Instead of running separate power cables, PoE delivers both data and electrical power over a single Cat5e or Cat6 cable — simplifying installation and reducing cost. But buying the wrong PoE switch or misconfiguring it can lead to devices that brown out under load, cameras that randomly reboot, or access points that can’t operate at full speed.

This guide covers what you need to know before you buy and after you unbox.

PoE Standards: 802.3af, 802.3at, 802.3bt

Not all PoE is equal. The IEEE standards define maximum power delivery per port:

Standard	Also Called	Max Power Per Port	Typical Use
802.3af	PoE	15.4W (12.95W at device)	Basic IP cameras, VoIP phones, small APs
802.3at	PoE+	30W (25.5W at device)	PTZ cameras, dual-band APs, video intercoms
802.3bt Type 3	PoE++	60W	Wi-Fi 6/6E APs, pan-tilt cameras with heaters
802.3bt Type 4	PoE++	100W	Thin clients, LED panels, high-performance APs

The power values drop slightly from the switch port to the device because of cable resistance — this is called “cable loss” and is why a 30W PoE+ port delivers only 25.5W to the device. For long cable runs (over 200 feet), that loss increases, so use the highest available standard when in doubt.

Match the switch to your devices. Check the maximum PoE draw listed on each device’s spec sheet, not just the label. A Wi-Fi 6E access point might be listed as PoE+, but its maximum draw under load might be 22W — well within a PoE+ port’s budget. An outdoor PTZ camera with built-in heater coils might draw the full 25.5W.

Calculating Your PoE Budget

Every PoE switch has two power constraints: per-port wattage (covered above) and total switch PoE budget.

The PoE budget is the total watts the switch can deliver across all PoE ports simultaneously. A typical 8-port PoE+ switch might have a 65W or 120W budget, even though 8 ports × 30W = 240W theoretical maximum. Manufacturers assume not every port runs at full load.

How to calculate your real load:

1. List every PoE device and its maximum wattage draw
2. Add those figures together
3. Add 20% headroom for startup inrush current and future additions
4. Make sure the switch’s total PoE budget exceeds that number

Example: 4 cameras at 12W + 2 access points at 20W = 88W. Add 20% headroom = 106W minimum budget. A switch with a 65W budget would be undersized here.

Some budget switches “share” the PoE budget across ports in ways that cause devices to drop power when multiple high-draw devices run simultaneously. This is the cause of mysterious camera reboots during business hours. Name-brand switches (Cisco, Ubiquiti, Netgear ProAV, TP-Link Omada) publish their PoE budget clearly and enforce it at the hardware level.

Managed vs. Unmanaged PoE Switches

For a simple 4-camera setup on an isolated network, an unmanaged PoE switch works fine. For anything more complex, you’ll want a managed switch for several reasons:

Per-port PoE control. Managed switches let you enable or disable PoE per port via the web interface. This is invaluable for remotely rebooting a frozen camera or AP without physically pulling its cable.

PoE scheduling. Some deployments benefit from powering down cameras or APs during off-hours to save energy and extend device lifespans. Managed switches support time-based PoE schedules.

VLAN support. Separating camera traffic from corporate LAN traffic is a security best practice. A managed switch handles the VLAN configuration that makes this possible.

Port monitoring and alerts. Managed switches can alert you when a device draws anomalous power or when a port goes down — useful for catching failing cameras before a security incident.

Cable and Distance Considerations

PoE works over standard Cat5e, Cat6, or Cat6A cabling. A few practical notes:

Maximum run length is 328 feet (100 meters). This is a hard Ethernet limit, not a PoE limitation. Beyond 100m, you need an intermediate switch or a PoE extender. PoE extenders inject power into the cable mid-span and pass data through — they’re useful for cameras at the far end of a large warehouse or parking lot.

Use Cat6 or better. Cat5e technically supports PoE, but Cat6 has lower resistance per foot, which means less voltage drop over long runs. For runs longer than 150 feet supplying high-wattage devices, Cat6 meaningfully increases delivered power.

Avoid patch cable adapters for long runs. Inline adapters and couplers introduce resistance and poor contact quality that worsens PoE performance. Run a single uninterrupted cable from switch to device wherever possible.

Check your conduit fill. Bundled Cat6 cables in a conduit generate heat from PoE current flow. Exceeding conduit fill ratings or bundling dozens of cables without derating increases temperature and can degrade performance or trigger thermal shutdowns in the switch.

Physical Installation Best Practices

Rack-mount vs. desktop switches. For an IDF or server closet, use rack-mounted switches. For a small retrofit job — say, adding 4 cameras to a retail space without a proper rack — a DIN-rail-mounted switch or a small desktop-form switch is practical.

Cooling matters. PoE switches run hot because they’re converting power. Don’t mount them in sealed enclosures without ventilation. Leave at least two inches of clearance on all sides, and verify the ambient temperature stays within spec. Outdoor enclosures need active cooling or shade.

Label every port. Before you seal the ceiling tiles or push cables through walls, label both ends of every cable with the device location (e.g., “CAM-NW-CORNER”, “AP-2F-HALL”). Tying port numbers to a simple spreadsheet or network diagram saves hours on future troubleshooting.

Initial Configuration Checklist

Once hardware is installed, work through these steps before considering the deployment live:

1. Update switch firmware. Managed switches ship with factory firmware that may be months out of date. Update via the admin interface before configuring anything else.

2. Change default credentials. Every network device ships with a default username and password. Change both immediately. Use a password manager to store the credentials.

3. Set a static IP for the switch itself. Managed switches need a predictable address for administration. Assign a static IP outside your DHCP pool or create a DHCP reservation by MAC address.

4. Configure VLANs. Put cameras on an isolated VLAN with no internet access unless they need cloud features. Put access points on a separate VLAN if your deployment separates corporate and guest traffic.

5. Enable STP (Spanning Tree Protocol). If you have any redundant links or the potential for a loop, STP prevents broadcast storms from taking down your network.

6. Test each device’s power draw. After all devices are connected, log into the managed switch and check the actual PoE draw per port. Verify it’s within expected range and that total draw stays well below the switch’s budget.

7. Verify uplink capacity. A PoE switch aggregates traffic from all connected devices to a single uplink. If you have 8 cameras streaming at 4Mbps each, your uplink needs to handle at least 32Mbps. A single-gigabit uplink is rarely a bottleneck for cameras, but high-density AP deployments with heavy client load can push that limit.

Common Problems and Quick Fixes

Device powers on but not at full speed. The switch and device may have negotiated a lower PoE standard. Check if both sides support the same standard. Some 802.3at devices fall back to 802.3af with non-standard switches.

Devices randomly reboot. Usually a PoE budget problem. Check total power draw on the switch dashboard. If total draw approaches the budget limit, devices will cycle as the switch tries to protect itself.

Camera works but shows in the switch as “not powered.” The device may have its own power supply connected — PoE switches detect this and don’t inject power. Verify the device is actually receiving power via PoE by disconnecting any secondary power source.

New device won’t power on. Verify cable continuity end-to-end with a cable tester. A miswired cable will pass data but fail PoE because PoE uses all four pairs (on 802.3at and 802.3bt). Check that the port isn’t administratively disabled.