IP CCTV on the Corporate Network: Bandwidth, PoE, and Storage Without Killing Office Traffic

IP cameras are endpoints with appetites. Dump them on the user access layer and you get frozen video and slow file shares.

Calculate before you buy lenses

Rough planning inputs:

• Resolution and FPS per camera
• Compression (H.265 vs H.264) and scene motion
• Continuous vs motion recording
• Retention days required by policy

Sum bitrate × camera count for the uplink to the NVR/VMS. Add headroom for firmware nights and multi-view spikes.

Network patterns that scale

Dedicated camera VLAN / VRF

Isolate camera traffic from office PCs. Apply ACLs so cameras cannot browse the internet freely — many botnets start from exposed DVRs/NVRs.

Right-sized switching

Prefer PoE+/PoE++ budgets matched to IR and PTZ draw. Separate uplinks to recording servers when camera density is high.

Time and identity

NTP everywhere. Change default passwords. Put the VMS management UI behind VPN or jump host — never raw on the public internet.

Storage path

Keep recording storage off the general file server volume when possible. Test restore of a random hour of footage quarterly.

Integration with the rest of the stack

CCTV works best when cabling, switching, and security policy were designed together:

• Structured cabling certified for PoE distance
• Firewall rules that allow VMS clients without opening the world
• Monitoring for offline cameras as an ops signal, not a surprise audit finding

Go-live checklist

1. Spot-check night IR image quality on critical doors.
2. Confirm retention actually matches the legal/ops requirement.
3. Verify failover if the primary NVR disk or NIC fails.
4. Document camera map with switch port and patch label.

Treat video like a production workload: measured bandwidth, segmented, and owned.

Raasano designs CCTV onto the enterprise network — PoE, switching, and recording paths that do not starve telephony or office traffic.