IP address and port planning during batch deployment: avoiding conflicts and later rework
Why do we need to plan first
Dozens of projects can be run by relying on "automatic acquisition + random allocation", but later expansion, equipment replacement, Troubleshooting can be very painful: you cannot find the address corresponding to a certain camera, and you have to add it to the NVR again after replacing it. Spending half an hour making an address list in the early stage can save a lot of time in the later stage.
Recommendations for network segmentation
| Purpose | Example network segment | Description |
|---|---|---|
| Camera | 10.10.0.0/22 | Segmented by floor or area |
| NVR/Storage | 10.10.10.0/24 | Fixed address for easy cascading |
| Management platform/server | 10.10.20.0/24 | Isolated from the front end |
| Access control/alarm and other subsystems | 10.10.30.0/24 | Independent network segments facilitate authority control |
Address allocation table template
It is recommended to include at least: point number, installation location, device model, MAC address, IP address, Gateway, associated switch port, access NVR number, and remarks. Among them, the MAC address is the most easily ignored, but it is the only reliable identifier for later locating the device.
Port planning
- It is recommended to plan the HTTP management port, RTSP port, and ONVIF port in a unified manner and record them in the document. Avoid interworking failure caused by mixing different batches of equipment.
- Always disable the default port for external mapping ports, and do not directly expose the device port to the public network.
- The RTSP streaming port must be open on the firewall, otherwise the platform can search for the device but cannot get the stream.
Quick location of address conflicts
The symptoms are usually "some cameras are intermittent" or "newly installed cameras cause the original ones to go offline". Troubleshooting sequence: First use a scanning tool to list all online addresses and MACs on this network segment. Compare with the address table to find duplicates; then check whether there are unregistered devices (such as laptops for temporary debugging, Equipment from other departments) occupy the monitoring network segment address.