| Scroll ignore |
|---|
| Scroll ignore |
|---|
Link to be provided outside of Bosch Internal document. This article cannot be provided outside of Bosch. |
Possible causes and solution(s)
Scenario:
- VSG version 7.1
- BVMS 10.1 build 10.1.1.12
- VRM is on 2 separate machines as Primary and Failover
- Failover VRM is also used as iSCSI and there is another dedicated iSCSI machine.
Cameras do not record and when going to VSG and recording, it stands that:
- Camera 1 - ANR not configured
- Camera 1 - [Recording 1] Error: No more blocks available
It’s the same on 2 VSG and cameras added to VSG don’t record.
Causes
There is no communication happening between the VRM and the VSG, and the VSG does not contain any information from the VRM where to record.
Potential causes of this issue may be lack of basic network communication, switch or router blocking the ports, hardware or software firewalls limiting the communication, Domain Security Policies applied to the domain, users or computers.
Some of these machines could be located on separate domains which could lead to a potential issue due to the security policies at the domain level that could apply and block communication.
Solution
- First, please see this document and check the compatibility on page 8. If the VSG and VRM don’t match the required version as per Release Note, please perform the upgrade for them
- VRM 3.83.0021 (64-bit)
- VSG 7.2.0.44
Note: After the upgrade we recommended to refresh and update the States and capabilities in BVMS, so the Configuration Client can read the new configuration.
- The firewalls should be checked to allow communication
| Warning | ||
|---|---|---|
| ||
Check your Network Setup There might be many wrong network setups scenarios, such as: wrong subnet, wrong IP range, wrong Inter VLANrouting, Domain restrictions, ISP restrictions, other software firewalls, Physical Firewalls, logical ports, physical ports. Networks with certificate authentication. For example you might be in the scenario of a wrong subnet. → Therefore, for this case, you should check whether the VSG servers you want to use are on another subnet than the Clients and the Central Server, so they could not find them by scanning. If so, please setup them correctly on the same subnet and setup the system from scratch following the normal install/config procedures → Afterwards, add manually the VSG with the correct IP and Port configuration for both VSG servers. Then, all cameras should be connected and should work as intended. |
If the issue persists, please do the following:
- Check live stream - provide the information if there are issues also with the live stream
- Enable: VSG Debug, RTP logging:
- The following article will help you to find out: Where can you find the "VSG debug logging" option in Configuration Client to enable/ disable it?
- Reproduce the issue and provide Video Streaming Gateway logs: Collect Config collector logs from the sever (article here)
- Collect the VSG logs using the BVIP tool à Central Technical Support team can provide you with this tool
- Screenshot of the Dashboard of the VRM.
- VSDK loggings from VSG sever — Idea please note that when you need VSDK logging from a service like (VSG, MVS, VRM etc.) you need to restart the service in order to get the data written in to the VSDK folders.
- The following article will help you to find out: How to enable and collect Video SDK log files?
- Wireshark captures on the VSG server & VRM server simultaneously if possible.
advancedINLINEgreenINLINE
Please contact CTS / SG or GK team to view this section from draft space, if necessaryadINLINE
Information below is for CTS, SG, GK reference and must be kept internal only.
If you are part of CTS, SG or GK team, please hide this section when you have finished using this article!