There was a complain from our custmer that the NVR6128 is uploading some data which choke the network of the customer which is on the public IP. And when they restart the NVR or disconnect it from the NATing i.e. from publich IP, then the network again get able to start browsing again.
On their network maintinance tool they saw that some data started uploading on the publich network.
No alarm was coming as NVR6128 was running properly.
On inquiring the customer it got clear that somebody from one of them tried to access many camera's via B/S client at the same time.
But as their bandwidth was limited so whenever they tried to see many cameras via B/S client then due to low bandwidth network used to get hang each time. Actually they were getting issue as according to the given formula they were accessing more cameras then the allowed number at the same time.
As it is recommended that use 60% bandwidth out of the total so
Total Bandwidth * 0.6 = x MB
x / bit rate (which we set for each camera) = Total number cameras which can be seen at one time.
i.e if total available bandwidth is 2MB and the set bit rate for cameras is 200K the according to the formula
2M * 0.6 = 1.2M
1.2M / 200K = 6 cameras
so with these specification we can see 6 cameras at one time and if we shall try to access more then it will cause problem in the network.
Cutomer is having one central NVR6128 and on remote site NVR6008 are installed which are connected with the central NVR6128 on customers internal network i.e. Private IP. The other port of the NVR is connected to the Public IP via NATing as customer wanted to use the B/S client to access the Central NVR6128 and to see the camera videos on it as well. So we got the complain that the NVR6128 is uploading some data on Public IP through NATing device.
We tried to find out from logs that which data and from which IP is getting upload from the NVR6128 but did not find anything and NVR6128 was working properly including all processes.
There was not any other server or device connected with the NVR6128 as well, so everything was ok from the equipment side.
It is suggested that before troubleshooting ask the detail about the problem which occured, this thing will help to find out the problem quickly.