IP CCTV INFRASTRUCTURE
IP Camera, PoE Switch and NVR Network Design Playbook
How to design the network around cameras, calculate traffic and storage from real bitrates, and avoid PoE and uplink bottlenecks.
Start with camera requirements
For each camera record resolution, codec options, configured frame rate, expected bitrate or bitrate range, PoE requirement, environment, mounting position and retention requirement. Do not calculate storage from megapixels alone.
Calculate aggregate traffic
If 20 cameras are configured for 6 Mbps average each, the arithmetic average video load is 120 Mbps before protocol overhead and variation. That number is a planning input for switch uplinks and NVR inbound bandwidth. Use the actual configured/expected bitrate for the camera scene and codec.
Storage
Storage depends on bitrate x recording time x retention period. Variable bitrate cameras can change substantially with scene motion and complexity. Treat the calculator result as a planning value unless it uses measured bitrate from the final configuration.
PoE
IR illuminators, heaters, PTZ motors and accessories can raise power demand. Size the switch from the actual camera power data and verify the total switch budget. Commission the system at night or under the power state that produces the highest expected camera load when practical.
Network segmentation
A dedicated camera VLAN can simplify addressing, firewall policy and troubleshooting. The correct policy depends on the customer's architecture. At minimum, know which systems need access to cameras, which need access to the NVR/VMS and which management stations are authorised.
NVR limits
Check the recorder's published inbound bandwidth, camera count, codec support, storage bays and drive compatibility. A recorder can have enough physical ports or licences but still have an inbound bitrate limit.
What works well
- One camera ID tied to switch port, IP address and physical location.
- UPS backing for the entire recording path, not only the NVR.
- Measured bitrate after final camera settings are applied.
- Separate recording, management and client-access requirements in the design.
Client benefit
Correct design prevents the common failure where cameras look fine individually but the uplink, PoE budget or recorder cannot handle the full system at peak load.
Security, NVR and KVM Guide | PoE Playbook | Camera Storage Calculator
Training manual: design from bitrate, not megapixels
Bandwidth example
If 24 cameras are configured for an observed average of 5 Mbps each, the simple average aggregate is 120 Mbps. That is not yet the complete switch-uplink design because bitrate can vary and other traffic exists, but it is far more useful than saying "24 x 4K cameras".
Storage arithmetic
For a constant 5 Mbps stream:
5 megabits/s x 3600 x 24 / 8 = 54,000 megabytes per day before unit conversion and overhead assumptions.
For 24 such streams, the raw arithmetic is 1,296,000 MB/day. Real deployments should use the camera's configured or measured average bitrate and the desired retention schedule. Variable bitrate can move significantly with motion, lighting and scene complexity.
Switch design
- Enough physical access ports.
- Enough PoE per port.
- Enough total PoE budget.
- Enough uplink capacity for aggregate camera traffic.
- Enough UPS capacity for the switch and NVR if recording must continue during outage.
Commissioning at the camera
- Confirm final field of view and focus.
- Set resolution, codec, frame rate and bitrate mode.
- Confirm time/NTP.
- Confirm IP/VLAN and recorder registration.
- Check night mode or IR behaviour.
- Record switch port and camera ID.
- Check live and recorded playback.
Failure mode: cameras freeze at busy times
Check NVR inbound bandwidth, switch uplink utilisation, packet loss, interface errors and camera bitrate changes. Do not assume a storage disk problem because the symptom is visible on recorded video.