IP address assignment for IP cameras

[engr.humayun 0]

Dear experts,

 

I am relatively new in the field of CCTV. Kindly let me know, what is the preferred method to assign IP addresses to the IP cameras, i.e., static or dynamic. Please let me know the answer with possible reasons.

 

Thanks

[StanLee2066 0]

Dear experts,

 

I am relatively new in the field of CCTV. Kindly let me know, what is the preferred method to assign IP addresses to the IP cameras, i.e., static or dynamic. Please let me know the answer with possible reasons.

 

Thanks

 

 

static. you need to be able to assign a permanent, known address to the camera. otherwise how will you be able to guarantee contact? e.g. would you rather your girlfriend always keep the same phone number or that she change it whenever she likes without telling you what it is?

[mkkoskin 0]

static. you need to be able to assign a permanent, known address to the camera. otherwise how will you be able to guarantee contact? e.g. would you rather your girlfriend always keep the same phone number or that she change it whenever she likes without telling you what it is?

 

This is true when question is asked static or dynamic, but since its usually static vs. DHCP, it's a bit more complicated.

If the camera network is installed as standalone, "offline" installation, then it's either zero-config system or manually set to static.

 

If the system is being installed into a corporate network, don't EVER install static devices, worst case scenario you'll 'crash' the whole network. In corporate cases always ask the system administrator which ip's to use, or if admin wants you to use DHCP. In which case they probably have their network set up by DHCP and assign IP addresses according to device MAC addresses, then you tell the MAC addresses to admin, admin configures them to network and tells you which IPs the devices will have when you plug them in.

 

If the system is for home security, most of the routers can work with dhcp and static IPs, but make sure you don't assign IPs that are already in use for other devices.

[engr.humayun 0]

Thank you StanLee2066 and mkkoskin for the prompt response.

 

The IP CCTV environment at my side will be a university campus where the Ethernet network is taken care by ITC department.

So, how about that we define a separate Video VLAN for each building and program the DHCP server to assign a dynamic IP address from a specific Video VLAN. As soon as we connect the camera and put it in the proper Video VLAN for that building, the camera will get an IP address from DHCP.

What do you guys think about this possibility. Kindly negate it with reasons if you think it is not feasible.

[Numb-nuts 1]

.

.

GOODNESS, how many girlfriends have you got?

 

[buellwinkle 0]

By virtue that you will have to have PoE switches for the cameras and your corporate computer network does not likely have it may negate the reason for a VLAN but most of the higher capacity management PoE switches have VLAN capability if needed. But it may pay to have a separate subnet via VLAN just for the cameras and then have a second ethernet connection to the campus lan for the NVR PC. Make sure the PoE switches have GigE uplinks at least, if not all gigabit (cameras are pretty much all 100Mbps).

[ssmith10pn 0]

The coolest setup I have seen is Different VLAN for each building.

Example:

10.1.208.x building A

10.2.208.x building b

10.3.208.x building c

 

Then DHCP was port specific. Port 1 Building A got 10.1.208.2

Anytime a camera got replaced it picked up the same IP as the previous one.

This was in a 3000 camera University environment.

[mgb 0]

On most of the jobs I do, the cameras are their own network with their own switches. I static ip all of them and my server has 2 nics. One to the cameras, one to the facilities LAN.

I have a couple of jobs where the cameras are on the facilities LAN on a vlan. and these are plenty beefy lans so its not like the cameras are bogging things down but it makes it harder to work and troubleshoot sometimes.

Cameras have ended up on different vlans due to mistakes by the administrators and it holds me up from getting things done.

Edited August 9, 2014 by Guest

[mkkoskin 0]

Thank you StanLee2066 and mkkoskin for the prompt response.

 

The IP CCTV environment at my side will be a university campus where the Ethernet network is taken care by ITC department.

So, how about that we define a separate Video VLAN for each building and program the DHCP server to assign a dynamic IP address from a specific Video VLAN. As soon as we connect the camera and put it in the proper Video VLAN for that building, the camera will get an IP address from DHCP.

What do you guys think about this possibility. Kindly negate it with reasons if you think it is not feasible.

 

In any case you'll want a static IP, either manually set or coming from DHCP according to MAC address. The NVR/VMS you'll be using will need to know the IP, and if it's dynamic for some reason, you'll end up spending a lot of time at the NVR/VMS changing the IPs.

 

We have big customers with hundreds/thousands of cameras around the country, this network is countrywide managed with VLANs, it's a nice way to keep track of which site the devices are on, and incase you need to connect to say mall 1 camera 194, you instantly know that it is for example 10.10.1.194. This network is managed by customers IT. If the security system was on a completely separated network, connecting to it and managing it remotely would be pain.

 

So in your University case, i'd have a chat with the people that manage the current network and ask what they think fits in their system. If they're willing to take the video surveillance system in their network, that makes your job a LOT easier, when all you do is provide them with device MAC address and install the device in place with DHCP.

[StanLee2066 0]

In any case you'll want a static IP, either manually set or coming from DHCP according to MAC address

 

Yes, also called "DHCP device reservation". I use this for some of my equipment - mostly PCs. The idea is to maintain the same address for the device at all times. If there is a major advantage to using DHCP device reservation to accomplish this for very large networks is beyond the scope of my knowledge. However I recently installed a few hundred network capable SSR radios in the network of a mayor city. The IT system specialist simply provided me with an IP address to set for each radio. That being said, I was just the installer with no familiarity of their network setup so can't comment on why this was the best way to go for this particular setup.

[engr.humayun 0]

Thank you StanLee2066 and mkkoskin for the prompt response.

 

The IP CCTV environment at my side will be a university campus where the Ethernet network is taken care by ITC department.

So, how about that we define a separate Video VLAN for each building and program the DHCP server to assign a dynamic IP address from a specific Video VLAN. As soon as we connect the camera and put it in the proper Video VLAN for that building, the camera will get an IP address from DHCP.

What do you guys think about this possibility. Kindly negate it with reasons if you think it is not feasible.

 

In any case you'll want a static IP, either manually set or coming from DHCP according to MAC address. The NVR/VMS you'll be using will need to know the IP, and if it's dynamic for some reason, you'll end up spending a lot of time at the NVR/VMS changing the IPs.

 

We have big customers with hundreds/thousands of cameras around the country, this network is countrywide managed with VLANs, it's a nice way to keep track of which site the devices are on, and incase you need to connect to say mall 1 camera 194, you instantly know that it is for example 10.10.1.194. This network is managed by customers IT. If the security system was on a completely separated network, connecting to it and managing it remotely would be pain.

 

So in your University case, i'd have a chat with the people that manage the current network and ask what they think fits in their system. If they're willing to take the video surveillance system in their network, that makes your job a LOT easier, when all you do is provide them with device MAC address and install the device in place with DHCP.

 

Dear mkkoskin, thank you for the detailed response again. Our university wide implementation comprises of 2,500 IP cameras, and our ITC department (who manages the university network) has agreed to take the video surveillance system in their network. However, we will use separate Video VLAN for each building.

Based on this discussion, I will put forward the suggestion of assigning IP addresses to the cameras using the device MAC address with the help of DHCP.

[Numb-nuts 1]

The coolest setup I have seen is Different VLAN for each building.

Example:

10.1.208.x building A

10.2.208.x building b

10.3.208.x building c

 

Then DHCP was port specific. Port 1 Building A got 10.1.208.2

Anytime a camera got replaced it picked up the same IP as the previous one.

This was in a 3000 camera University environment.

 

Now that is what I call awsome use of the technology. Very Impressive.

[ssmith10pn 0]

One of the 5 aggregation points around campus.