HIK PoE Switch & Network Planning Guide (2026)

An IP camera system has three physical layers: cameras, cabling and the network that connects them to the recorder. The switch sits at the centre of the last layer. It supplies power, carries the video streams and, on larger sites, separates camera traffic from everything else.

This guide covers HIK PoE switch and network planning: PoE standards and budgets, uplink capacity, switch selection, VLAN and QoS design, multicast, cabling and redundancy. It is written for installers, integrators and buyers who need the network to be as deliberate as the camera list.

Most network problems in surveillance are predictable. The switch runs out of power budget, the uplink saturates, or video competes with business traffic and loses. Each of these is avoidable with a short planning exercise before the purchase order.

A good network plan is boring in the best way: the cameras stay online, the recordings are complete, and nothing needs attention until the next planned change. Start with the numbers, then choose the hardware.

1. Why the switch decides system reliability

Cameras get the attention, but the switch determines whether they stay online. A camera that reboots at night is often not faulty; it is drawing more power than the port can supply when IR or a heater turns on. A recorder that drops channels at the busiest hour is often not faulty either; the uplink is congested.

The switch also determines how the system behaves when something changes. Adding four cameras, enabling a higher bitrate or connecting a second recorder all put more load on the switch. A design with headroom absorbs those changes; a design at the limit does not.

Finally, the switch is the natural place to separate camera traffic from business traffic. A managed switch with VLANs and QoS can keep video stable while the office network does backups, video calls and file transfers.

A well-planned switch also makes fault-finding easier. Managed switches expose port status, PoE draw and error counters. When a camera goes offline, the switch tells you whether the port lost power, lost link or is receiving errors, which narrows the problem immediately.

On a multi-building site, the switch plan becomes a topology plan. Where the switches sit, how they are linked and which recorder each group feeds determine

The switch is also where the system's security posture begins. Default passwords, open management pages and unused ports are common weaknesses. Change defaults, disable unused ports and restrict management access before the system goes live.

2. PoE standards and power classes

Power over Ethernet carries power and data on the same cable. The three common standards are 802.3af, 802.3at and 802.3bt. Each raises the maximum power available at the source, which allows more capable cameras and peripherals.

802.3af provides up to about 15.4 W at the source. It suits fixed domes, bullets and small cameras with modest IR. 802.3at provides up to about 30 W and suits PTZ cameras, cameras with heaters and devices with higher IR power. 802.3bt provides up to about 60 W or 90 W depending on type, and suits high-power PTZ, multi-sensor cameras and heated housings.

The camera's power class is a ceiling, not a guarantee. A camera may be class 4 (802.3at) but draw only 9 W in normal operation. The number to design for is the maximum draw in the datasheet, including IR and heater, not the class maximum and not the typical value.

Check that the switch supports the standard the camera needs, and that the port can deliver the required class. A switch that supports 802.3at on paper may have a total budget that cannot power every port at 30 W.

Passive PoE is different. It applies a fixed voltage without negotiation and can damage devices that do not expect it.

Power classes are negotiated at connection time. The switch and camera agree on a class before power is applied, and the switch refuses to power a device that requests more than the port can supply. A camera that works on one switch but not another is often a class mismatch, not a faulty camera.

Some cameras support multiple classes or use LLDP for finer power negotiation. Check whether the switch supports the same negotiation method,

The power class is not the same as the power draw. A class 4 camera may draw 9 W most of the time and 25 W when the heater runs. Design for the higher number, and check the switch's per-port limit against it.

Some switches reserve power per port by class rather than by actual draw. A 30 W class may reserve 30 W even if the camera draws 9 W, which reduces the number of cameras the switch can support.

Class negotiation also affects startup time. A camera may take a few seconds to negotiate and boot; a switch that powers all ports at once can create an inrush current that trips the budget. Some switches stagger power-on; check if this matters on a large installation.

3. PoE budget math

The PoE budget is simple arithmetic with a safety margin. Add the maximum draw of every powered device on the switch. Add any non-camera PoE devices. Compare the total with the switch's PoE budget. Then check each port against its per-port limit.

Example: eight fixed 4 MP cameras at 8 W each draw 64 W. A switch with a 120 W budget leaves 56 W, about 47% headroom. That is comfortable. If four cameras are replaced by PTZ units at 25 W, the total becomes 4 × 8 + 4 × 25 = 132 W, which exceeds a 120 W budget. The design needs a larger switch or a second switch.

Headroom matters for two reasons. First, cameras draw more in cold weather when heaters activate. Second, a replacement camera may draw more than the original. A design at 100% of budget has no room for either.

Voltage drop is the hidden variable. PoE loses voltage over distance, so a camera at the end of a 100 m run receives less than the switch supplies. If the camera is near its limit, a long run can cause resets when IR turns on.

The diagram below shows the relationship between camera load, switch budget, uplink bandwidth and the recorder.

Keep the budget table in the handover document: camera model, quantity, maximum draw, port, switch total and headroom. When a camera is added later, the table answers the question immediately.

Do not forget non-camera PoE devices. Access points, intercoms, access-control readers and PoE clocks also draw from the same budget.

Budget planning should include the recorder if it is PoE-powered, and any PoE injectors or mid-spans. Each device on the power path consumes budget somewhere; the goal is to account for all of it in one table.

Consider the cost of a second switch. If the camera count is close to the budget limit, a second switch may be cheaper than a larger chassis, and it adds redundancy:

A power budget should be reviewed when the camera list changes. Adding four cameras or replacing fixed cameras with PTZ units can push a comfortable design over the limit.

The switch budget should also be checked against the switch's PoE allocation method, not just the total. Some switches reserve power by class, which can reduce the number of ports available at full power. Read the datasheet carefully before committing to a count.

Also consider the switch's PoE budget at the model level, not just the series.

Power budget tools from switch vendors can help, but check the assumptions. Some tools use typical rather than maximum draw, which understates the requirement. Use the datasheet maximum and your own table.

4. Uplink bandwidth

The uplink carries the aggregate camera bitrate from the switch to the recorder and, if needed, to remote viewers. For a 32-camera system at 6 Mbps, the aggregate is about 192 Mbps; with 20% headroom, plan for roughly 230 Mbps. A 1 Gbps uplink is comfortable for that load.

For 64 cameras at 8 MP and 10 Mbps, the aggregate is about 640 Mbps; with headroom, it approaches 770 Mbps. A single 1 Gbps uplink is tight, especially with other traffic. Use two uplinks, a 10 Gbps uplink, or distribute recorders closer to camera groups.

Estimate from the configured bitrate, not the datasheet maximum. A camera set to 4 Mbps uses 4 Mbps; one left at 12 Mbps uses 12 Mbps. Multiply by the camera count, add headroom, and compare with the uplink.

Remote viewing is a separate calculation. Six sub-streams at 1 Mbps each need about 6 Mbps outbound plus overhead. The risk is the peak when several users open playback at once, not the average.

Quality of service helps here. Put video on a dedicated VLAN and prioritise it,

The uplink is also shared with management traffic, firmware updates and recorder playback. A firmware update to 32 cameras can briefly consume significant bandwidth. Plan the uplink for normal operation plus a margin for maintenance.

If the recorder is on the same switch as the cameras, camera-to-recorder traffic stays local and does not cross the uplink. That is

If remote viewing is required, plan it explicitly. Sub-stream viewing at 0.5–1 Mbps per viewer is manageable; full-resolution playback from many clients is not. Document the expected number of concurrent viewers.

5. Choosing the switch

Start with port count, but do not stop there. Count the cameras, add spare ports for future cameras and for the recorder or uplink, and choose a switch with more ports than the immediate requirement. A 16-port switch for 12 cameras leaves room for growth; a 16-port switch for 16 cameras does not.

Check the PoE budget against the total draw, not the port count. A 24-port switch with a 190 W budget may not power 24 cameras at 8 W each (192 W), let alone PTZ units. Match the budget to the actual device list.

Decide between managed and unmanaged. Unmanaged switches are simple and cheap, and they suit small isolated systems. Managed switches cost more but support VLANs, QoS, link aggregation, loop protection and monitoring. On any site where video shares the business network, managed is the better choice.

Check the uplink type and speed. Some switches have fixed 1 Gbps uplinks; others have SFP or SFP+ cages for fibre or 10 Gbps. For multi-building sites, fibre uplinks avoid distance limits and ground potential differences.

Finally, check the physical form: rack-mount or desktop, fanless or fan-cooled, operating temperature and power input.

Check the switch's switching capacity and packet forwarding rate, not just the port speed. A switch with many ports but a weak backplane can become a bottleneck when all cameras stream at once.

Consider the management interface. A switch with a clear web UI, SNMP and logging is easier to support than one with a minimal interface.

Fanless switches are preferable in offices and quiet areas; fan-cooled switches are common in racks. Check the operating temperature if the switch will sit in a cabinet or an outdoor enclosure.

Warranty and support matter on larger sites. A switch that fails after two years with no replacement path can leave the site without video.

Port count should include the uplink and the recorder. A 16-port switch with 15 cameras has one port for the uplink and no room for a local recorder or a spare. Leave at least two spare ports for growth and service.

Check whether the switch supports jumbo frames, IGMP snooping and VLAN tagging. These features matter for video and multicast; a switch without them may limit the design later.

6. VLANs and QoS

A VLAN separates camera traffic from business traffic on the same physical switch. Cameras and the recorder go on one VLAN; office computers, phones and servers stay on another. Broadcast traffic and large file transfers then stay out of the video path.

QoS prioritises video traffic when the network is busy. Video is tolerant of some delay but not of sustained loss; a congested uplink produces mosaic artefacts and dropped recordings. Prioritising video keeps the camera streams stable while other traffic waits.

Keep the design simple. One camera VLAN and one business VLAN is usually enough for a small site. Larger sites may separate camera groups, recorders and management. Document the VLAN IDs, the port assignments and the inter-VLAN rules in the handover document.

Do not expose cameras to the internet by default. If remote access is required, use a VPN or a secured remote-access service.

Document the VLAN plan before configuration. Record which ports are camera ports, which are uplinks and which are management. A port patched to the wrong VLAN is a common cause of "camera not found".

If a firewall or router sits between VLANs, allow only the required traffic. Cameras need to reach the recorder;

QoS is not a substitute for adequate bandwidth. If the uplink is overloaded, prioritisation can protect video at the expense of other traffic, but it cannot create capacity. Size the uplink first, then prioritise.

Keep management access on a separate VLAN or a restricted address range. A camera network with open management access is an easy target;

A camera VLAN is not a substitute for camera hardening. Change default credentials, disable unused services and keep firmware current. The network can isolate traffic, but it cannot fix weak device configuration.

7. Multicast and IGMP snooping

When several viewers watch the same camera, unicast sends a separate copy to each viewer, multiplying bandwidth. Multicast sends one copy that multiple viewers can join. On a control room with several monitors, multicast can reduce load on the recorder and the uplink.

Multicast requires switch support, usually IGMP snooping, and careful configuration. Without snooping, multicast traffic can flood every port and make the problem worse. Enable IGMP snooping, define the multicast group range and test with the actual viewers.

For small systems, unicast is simpler and usually sufficient.

Multicast also affects the recorder. A recorder that receives multicast can serve multiple viewers without duplicating the stream, which reduces load on the camera and the network.

Test multicast with the real viewer software. Some clients join groups differently, and a misconfigured group

Multicast is most useful when many viewers watch the same few cameras, such as a control room wall. It is less useful when viewers watch different cameras,

Multicast configuration should be documented: group range, snooping settings and which ports are multicast routers. Without documentation, the next technician may disable snooping and flood the network.

8. Cabling and distance

Use twisted-pair cable rated for the environment. Cat5e supports 1 Gbps over 100 m and is adequate for most 4 MP cameras. Cat6 gives more margin for 8 MP and longer runs. Avoid copper-clad aluminium cable; it has higher resistance and is a poor choice for PoE.

Keep each run within 100 m from switch to camera, including patch leads. For longer runs, use fibre or a mid-span extender. A run that is slightly too long may work at first and fail intermittently later.

Terminate carefully and test every run. Poor terminations cause more faults than cable itself. Label both ends and record the camera, switch port and VLAN in the handover document.

Separate video cable from mains where possible, cross at right angles if you must cross, and use conduit outdoors.

PoE cable quality matters more than many installers expect. Thin or copper-clad cable increases resistance and voltage drop, which shows up as camera resets at night or at the end of long runs.

Surge protection is worth planning on outdoor runs.

Test the PoE voltage at the far end, not just continuity. A cable that passes data may still drop too much voltage for a camera at the end of a long run.

Commissioning should include a PoE draw check. Compare the actual draw on each port with the budget table. A camera drawing more than expected may indicate a fault or a higher-power model than planned.

Keep camera cables away from mains and from high-current equipment. Induced noise can appear as intermittent packet loss, which is difficult to diagnose after installation.

9. Redundancy and UPS

A UPS on the switch and recorder keeps the system running through short outages. Size the UPS for the equipment that must ride through: the recorder, the core switch and the cameras on critical channels. A small UPS that keeps the switch alive but not the recorder is only half a solution.

On larger sites, consider redundant uplinks or link aggregation. If one uplink fails, the other carries the load. Configure it deliberately and test the failover before handover.

Enable loop protection on managed switches. A loop in a camera network can bring down the whole segment.

Label the UPS outlets. Put the recorder and core switch on battery-backed outlets, and keep non-critical loads off them so the runtime is preserved for the equipment that matters.

Test the failover. A redundant uplink that has never been tested may not work when needed. Disconnect one link during commissioning and

Document the recovery procedure. After an outage, the order in which devices restart can matter. Bring up the core switch first, then the recorder, then the cameras, and

Check the UPS runtime with the actual load. A UPS rated for 10 minutes at half load may give 5 minutes at full load. Measure or calculate the runtime for the equipment you plan to protect.

10. Worked examples

Small retail, 8 cameras. Eight 4 MP cameras at 8 W each draw 64 W. A 16-port switch with a 120 W budget leaves 56 W headroom. Aggregate bitrate is 48 Mbps, well within a 1 Gbps uplink. A single unmanaged switch is sufficient if the site has no business network sharing.

Warehouse, 32 cameras. Thirty-two cameras at 8 W draw 256 W. Choose a 24-port or 48-port switch with at least a 370 W budget, or two switches. Aggregate bitrate at 6 Mbps is 192 Mbps, so a 1 Gbps uplink is comfortable. Use a managed switch with a camera VLAN and QoS.

Campus, 64 cameras. Sixty-four cameras at 10 Mbps aggregate to 640 Mbps. Use two 1 Gbps uplinks or a 10 Gbps uplink, and distribute recorders to keep traffic local. PoE budget depends on camera type; PTZ units at 25 W would require multiple switches or higher-power models.

Remote site, 4 cameras. Four cameras at 8 W draw 32 W. A small 8-port switch with a 60–120 W budget is enough.

Medium office, 16 cameras. Sixteen cameras at 8 W draw 128 W. A 24-port switch with a 240 W budget leaves 112 W headroom. Aggregate bitrate at 6 Mbps is 96 Mbps; a 1 Gbps uplink is ample. Use a managed switch if the office network shares the same hardware.

Mixed site, 24 cameras including 4 PTZ. Twenty fixed cameras at 8 W plus four PTZ at 25 W draw 260 W. Choose a switch with at least a 370 W budget,

Multi-building site, two switches. Two 24-port switches, one per building, linked by fibre. Each switch powers its local cameras; the recorder sits with the core switch. Aggregate traffic on the fibre link is only the remote building's camera load, not the whole site,

Small warehouse, 12 cameras. Twelve cameras at 8 W draw 96 W. A 16-port switch with a 120 W budget leaves 24 W, which is only 20% headroom. If PTZ units may be added, choose a 240 W model instead.

11. Common mistakes

Choosing a switch by port count alone is the most common mistake. A switch with enough ports but too little PoE budget will fail when the cameras are connected.

Ignoring peak draw is the second. Heaters and IR increase consumption in cold weather or at night. Design for the maximum, not the average.

Using a 1 Gbps uplink for 64 high-bitrate cameras is the third. The aggregate may exceed the uplink, causing dropped frames and mosaic artefacts.

Sharing an unmanaged switch with business traffic is the fourth. Video competes with backups and file transfers and loses. Use a managed switch with VLANs and QoS.

Forgetting the UPS is the fifth.

Ignoring voltage drop is another common mistake. A camera at the end of a long run may reset even though the switch budget looks fine. Measure or calculate the drop and use better cable or a shorter run.

Choosing a switch without IGMP snooping for a multicast design is the eighth. Multicast without snooping floods the network and can make performance worse than unicast.

Assuming a 1 Gbps uplink is enough for every camera is the ninth. At 64 cameras and 10 Mbps, the aggregate is close to the limit before headroom; plan the uplink from the numbers.

12. Procurement checklist

• List every camera with maximum power draw and configured bitrate.
• Sum the draws and choose a switch budget with 20–30% headroom.
• Check per-port PoE class against each camera.
• Sum the bitrates and size the uplink with 20% headroom.
• Choose managed if video shares the business network.
• Plan VLANs and QoS, and document port assignments.
• Confirm cable type, distance and surge protection.
• Size the UPS for the recorder and core switch.
• Plan loop protection and redundant uplinks on larger sites.
• Record the final design in the handover document.
• Confirm the switch's per-port and total PoE allocation method.
• Check the uplink type and speed against the aggregate bitrate.
• Record the VLAN IDs and port map.

13. FAQ

How much PoE budget do I need? Add the maximum draw of all cameras and leave 20–30% headroom. Do not size to the average.

Can I power a PTZ from an 802.3af port? Usually not. PTZ cameras with IR and heaters often need 802.3at or 802.3bt. Check the datasheet.

Is a 1 Gbps uplink enough? For many 32-camera systems, yes. For 64 cameras at 8–10 Mbps, plan for two uplinks or 10 Gbps.

Do I need a managed switch? Not for a small isolated system. Use one when video shares the business network or when VLANs, QoS and monitoring are required.

What is IGMP snooping? A switch feature that limits multicast traffic to the ports that requested it. It prevents multicast from flooding the network.

How do I protect against a cable loop? Enable spanning tree or the switch's loop-detection feature, and document the topology.

Should cameras have internet access? Usually no. Block outbound access unless a specific feature requires it, and use a VPN for remote access.

How long should PoE cables be? Keep each run within 100 m, including patch leads. Use fibre or an extender for longer runs.

Can I mix PoE and non-PoE devices on one switch? Yes. Non-PoE devices use the data ports and draw no power; just keep the PoE budget for the devices that need it.

Do I need a separate switch for cameras? Not necessarily. A managed switch with a camera VLAN can share hardware safely. A separate switch is simpler but adds cost and rack space.

How much headroom should I leave on the uplink? 20% is a practical minimum. More is better if the site may add cameras or raise bitrates.

Should the recorder be on the camera VLAN? Usually yes. Keeping camera and recorder traffic on the same VLAN avoids routing video through the firewall and keeps the path simple.

Can PoE power a camera over 150 m? Not over standard copper Ethernet. Use fibre with local power or a mid-span extender designed for the distance.

How do I choose between 8-port and 16-port switches? Count the cameras, add spare ports and the uplink, and choose the next size up. Two smaller switches can also add redundancy.

Does PoE affect image quality? No, if the camera receives stable power. Unstable power can cause reboots and gaps in recording, which look like quality problems.

How do I monitor PoE usage? Managed switches usually show per-port power draw. Check it after commissioning and compare with the budget table.

Can I use a PoE injector instead of a PoE switch? Yes for a few cameras, but injectors add cabling and points of failure. A PoE switch is cleaner for more than a handful of devices.

What if the switch budget is slightly short? Reduce the camera count on that switch, choose lower-power models, or add a second switch. Do not run at the limit.

14. Glossary

• PoE: Power over Ethernet; power and data on one cable.
• 802.3af / at / bt: PoE standards with increasing power budgets.
• PSE: power sourcing equipment; the switch or injector that supplies PoE.
• PD: powered device; the camera or other device that receives PoE.
• VLAN: a logically separated network segment.
• QoS: quality of service; prioritises latency-sensitive traffic.
• IGMP snooping: a switch feature that manages multicast group membership.
• Uplink: the connection from an access switch to the rest of the network.
• Link aggregation: combining multiple links into one logical link.
• UPS: uninterruptible power supply.
• LLDP: link layer discovery protocol; can be used for power negotiation and topology discovery.
• Spanning tree: a protocol that prevents network loops.
• SFP / SFP+: hot-swappable transceiver slots for fibre or high-speed copper uplinks.
• Backplane: the internal switching capacity of the switch.
• Port isolation: a feature that prevents clients on the same switch from communicating directly.
• Jumbo frames: Ethernet frames larger than the standard 1500 bytes, used in some video networks.
• PoE injector: a device that adds PoE to a non-PoE switch port.

15. Sources

• IEEE 802 — Ethernet and PoE standards, including 802.3af/at/bt.
• ONVIF — interoperability profiles for IP video products.
• TIA — structured cabling standards and guidance.

Shop HIK PoE recorders

In-stock and priced models for this topic. Confirm the exact suffix and quantity before ordering.

DS-7608NXI-K2/8P 8-ch PoE NVR

$330.00

View product →

DS-7616NI-M2/16P 16-ch PoE NVR

$611.00

View product →

DS-7732NI-I4-24P 32-ch PoE NVR

$655.00

View product →