5 Switch Problems Killing Your CCTV Projects — And How to Fix Them

Your customer's cameras freeze. Cameras go offline. The whole site goes down and nobody can say why. In most of these cases the cameras are fine — the switch underneath them is the problem. Here are the five faults we see most often on surveillance sites, what each one looks like from the customer's side, and the specification that prevents it.

Problem 1 — Bandwidth bottleneck

Cameras look fine individually and stutter together. Frames drop when several people watch at once, and playback crawls. The cause is usually an uplink sized by port count instead of by bitrate: an eight-camera cabinet on a 100 Mbps path, or a trunk shared with office traffic.

• Add up camera bitrates (a 4MP H.265 camera is typically 4–6 Mbps) and compare with the uplink, not with the port count.
• Keep gigabit uplinks on every cabinet, and move to 2.5G or 10G when several cabinets converge on one core port.
• Separate camera traffic from office traffic so a backup job cannot starve the recorders.

Problem 2 — PoE budget shortfall

Cameras reboot at dusk, or two or three drop off the network every evening. That is the signature of a PoE budget that was sized for daytime draw: as IR turns on, the total climbs past what the switch can deliver and the weakest ports get cut.

• Compare total PoE budget, not "PoE on all ports"; a 16-port switch can share as little as 120 W.
• Use night draw for every camera, then add 25–30% headroom.
• Keep runs under 100 m and avoid thin CCA cable; voltage drop wastes budget before the camera sees it.

Our PoE switch range is specified by total budget and per-port class, so the number on the datasheet is the number the site gets.

Problem 3 — Network loops

Someone patches a wall port into another wall port, broadcast traffic multiplies, and the entire site stops — cameras, POS, door access, everything. An unmanaged switch has no defence against this.

• Use managed switches with STP/RSTP and storm control on any site with more than one cabinet.
• Enable loop detection on access ports used by staff or cleaners.
• Label and document the patch panel; most loops come from undocumented ports.

Problem 4 — No remote management

One camera freezes on a Friday night and the only fix is a two-hour drive to power-cycle a port. Without management, every minor fault becomes a paid callout, and the customer remembers the invoice, not the cause.

• Per-port PoE control lets you reboot a single camera from a desk.
• Port statistics and error counters turn "the cameras are slow" into a measurable diagnosis.
• SNMP or syslog lets the site report itself before the customer calls.

Managed and managed PoE models are listed under L2/3 managed switches and managed PoE switches.

Problem 5 — Wrong cable, connectors and installation

The switch is right and the site still fails, because the physical layer was treated as an afterthought: CCA patch leads, RJ45 plugs crimped on site, cameras at 130 m, or a cabinet with no surge protection and no earth reference.

• Use Cat5e minimum, Cat6 for new runs; never copper-clad aluminium for PoE.
• Buy factory-made patch leads, and test every run before the cameras go up.
• Plan the 100 m limit before the cable is pulled; beyond it, use fibre or an extender.
• Earth and surge-protect outdoor cabinets, especially where cameras sit on masts.

The five problems in one table

What we recommend

Specify the switch last, after the camera list, the cabinet layout and the cable plan — then check four numbers: total PoE budget, uplink bandwidth, management features, and spare ports. If all four are covered, the five problems above mostly stop happening.

Send the camera list and cabinet plan and we will return a port / PoE / uplink table with the matching models — usually within one working day. Get a quote.

FAQ

المواصفات الفنية التفصيلية متوفرة باللغة الإنجليزية.