90% of them. They just drop in and out randomly but are down more often than not.
The previous setup had NVRs in each building that the cameras connected to directly. The NVRs were then all connected to the main admin data network for clients to access.
Issue started when the cameras were setup on the main admin data network as the NVRs were removed for the upgrade to the new VMS.
This is part of a university network with various VLANs for different device types. I had wanted to isolate the CCTV network anyway but it's still odd that they're not playing nice on the main admin data network.
This is why...
when cameras were connected to NVR internal switch (or separate switch connected to second port on NVR), cameras were MANAGED by NVR..
NVR worked as router / firewall / NAT / DHCP server / time server for them... All network configuration on cameras were managed by NVR..
On your network You had only NVR visible - cameras were hidden behind NVR firewall...
When You connected cameras to main VLAN - this probably was disaster at first.
You must manually set ip / network parameters on each camera using dahua config tool..
If there was any DHCP server for normal clients on this network segment / VLAN - You must use static IP's from outside DHCP scope/range (but inside network routing range).. No duplicates of static IP and DHCP IP range..
I don't known how big IP segment network was - it was enough for all normal clients and cameras.. DHCP range and static IP's...
You need separate & isolated VLAN..
only second port of NVR and cameras there...
On all switch ports where cameras (or NVR) are connected, You must setup Native VLAN for this ethernet port to CCTV VLAN number.. And disable tagged VLANs...
The best solution is allow back NVR to fully manage the cams (IP's etc)..
Allow NVR works as router / firewall / NAT / DHCP server for cameras..
But first You must have separate isolated VLAN.. and revert configuration on cameras to no static IP (use DHCP)..
Yes, this new one is completely isolated. I had initially tested with the default 1 VLAN (as it wasn't in use) and saw the same behaviour so had a new VLAN created to try rule it out.
Never use VLAN 1 on multi VLAN / switch networks
No, and no, not from what I can see. The VLAN was automatically created when specifying it on the access ports, and automatically included in the allowed VLANs on the trunk ports.
ask Cisco admin is everything ok there..
One building is setup this way due to limited free ports. Those cameras are affected too. EDIT: Sorry re-read and that's something we haven't tested. All the cameras are installed so would have to be removed to try this. The vendor/installer has also recommended going a step further by setting the cameras up on their own fibre links between the buildings.
Yes - but between local POE switch and NVR there is campus network. Which can create problems (we don't known why at this moment)..
Get smaller POE switch and put in building where You have NVR (or move NVR to the building where You have local POE switch)..
connect to that POE switch second port NVR and some cameras from the building...
no campus network connected to this local POE switch...
primary NVR port connect to main VLAN in campus network, where should work...
before connecting cams reset them to use DHCP (no static IP)..
allow NVR to manage them using camera list interface on NVR...
This local installation (NVR + totally separate POE switch and some cams managed by NVR) SHOULD WORK...
If You need you can connect second NIC of VMS computer (or some netbook with
tools) to this local POE switch - to check network, pings etc..
if this will work then you known that NVR is ok and those cams (and settings) are ok..
then You can try connect more cameras...
first all direct..
second the rest using campus network (on ethernet port setup for CCTV VLAN)...
remember about reseting camera settings to DHCP (no static IP)..
if this will fail You will known that something is not OK in campus network configuration..