About Central_Support

Possible causes and solution(s)   Causes   When camera is set to auto track (by web interface) to "auto"-> IVA is detecting an object but camera is not following. Auto tracking works and metadata is displayed only on a stored preposition.   Solution   There was a change introduced starting with FW v.7.70. The new feature is: i-Track only starts on VCA-Alarm.   You can either program this on presets, e.g a detection field or if you want to have Itrack active regardless of its position, you need to activate "global VCA" and assign task detection area "whole screen" now only activate iTrack "AUXON78" so the eye is in the corner, and your iTrack will always be on sharp   Note: IVA must be active for at least one preset scene in the VCA page on the Settings tab. If IVA is configured for one scene, then all other scenes have Intelligent Tracking enabled by default. If a scene, however, has Motion+ or IVA 5.5 Flow activated, then Intelligent Tracker is disabled for these scenes. Please refer also to the attached document.   See more KB articles related to video analytics here. ... View more

Simple Network Management Protocol (SNMP) is a common protocol to monitor the health status of a system. Such a monitoring system typically has a central management server that collect all the data from the system’s compatible components and devices. A network management server can poll the health status of a device via SNMP requests. This article shows how to configure Bosch cameras in order to be able to answer to such requests. For more information on SNMP and supported SNMP versions please check - What should you know about SNMP and Bosch cameras SNMP support?   Step-by-step guide   Step 1 - Enable SNMP. Click on SET Step 2 - Select the SNMP v3, set up the authentication protocol and password and privacy protocol and password. Click on Set and Reboot button. Note: Please keep in mind that for SNMP v3 only the the Standard MIB II file is supported. This means that only general network device performance monitoring parameters can be requested. There is no Bosch Private MIB II extension for SNMP v3. For exact support details check - What should you know about SNMP and Bosch cameras SNMP support?   How to activate the SNMP and configure sending SNMP traps from Bosch cameras? ... View more

Simple Network Management Protocol (SNMP) is a common protocol to monitor the health status of a system. Such a monitoring system typically has a central management server that collect all the data from the system’s compatible components and devices. A network management server can poll the health status of a device via SNMP requests. This article shows how to configure Bosch cameras in order to be able to answer to such requests. For more information on SNMP and supported SNMP versions please check - What should you know about SNMP and Bosch cameras SNMP support?   Step-by-step guide:   Step 1 - Enable SNMP. Click on SET Step 2 - Select the SNMP v1 legacy. Click on Set and Reboot button. Step 3 - Community Strings In case the set up does not use the default Community Strings ("public"), please check this article in order to change the community strings - How to change SNMP Community string for Bosch cameras?    How to activate the SNMP and configure sending SNMP traps from Bosch cameras? ... View more

The default Community Strings for Bosch cameras is - public. To change it, please follow the steps below.   Step-by-step guide   1. Enable SNMP 2. Set the SNMP Community Name The read and write Community names are configured in the camera separately using Bosch RCP+ commands. These are: 0x0b16 for SNMP read access and 0x0b17 for SNMP write access.   Refer to the RCP+ documentation for more details. This is easily done using the following CGI commands. Substitute the IP address of the camera and the desired change the Payload from the default of "public" to a name required for your set up.   The CGI to change the community string for SNMP read access is: http://<ip address>/rcp.xml?command=0x0b16&type=P_STRING&direction=WRITE&num=1&payload=customisedString The CGI to change the community string for SNMP write access is: http://<ip address>/rcp.xml?command=0x0b17&type=P_STRING&direction=WRITE&num=1&payload=customisedString ... View more

This article describes all the steps that will help you to create iSCSI Virtual Disk/LUNs after replacing an HDD on a DIVAR IP 5000 AIO. Article requirements: Disk Management BVMS Configuration Client which is included with BVMS Server Manager DIVAR IP 5000 AIO   Step-by-step guide   Add New Simple Volume: 1. Search for "Disk Management" and open it   The new HDD will be displayed as "Unallocated"   2. Right click on the new HDD (in this example Disk 4) and select "New Simple Volume" > Next > Next > Next > Next > Finish 3. The new volume will become "Healthy (Primary Partition)" and it will be displayed in Disk Management (in this example "Test (H:)") and in This PC folder (Test (H:) folder will be empty)   Create LUNs 1. If you check in Configuration Manager, under "Basic Configuration" menu, you will see the number of LUNs already configured (from the other HDDs - in this example 12 LUNs): 2. Open Server Manager Important! Go to "File and Storage Services".  Please check first in iSCSI menu if the Virtual Disk Status of the new path created before is "Error" instead of "Connected". If so, please right click on all of them and remove them from iSCSI Virtual Disks window. In this example "H:\VHDxx.vhdx"   a) Go to Volumes menu > select H: > right click on it the and select "New iSCSI Virtual Disk" b) Now, select the storage location (in this example H:) > click Next **You can also select a custom path if you want. c) Type in the iSCSI virtual disk name > click Next d) Please always select "Fixed size" and add the size of the iSCSI virtual disk. To calculate the number of LUNs for the detected capacity you need to follow the below procedure: If the size is calculated in TB, the capacity will be divided with :1.82 in TB If the size is calculated in Gb, the capacity will be divided with :1900 in Gb You need to divide the physical capacity which is detected by the Configuration client as in the below picture with a number which is near the maximum size of 2000 Gb For example in Gb: 19557/ 1900 = 10.29 => Number of LUNs = 11 As the result is above 10 we will select 11 in order for the luns to have a size near 2000Gb. In this example, the free space is 7.28 TB: 7.28 TB/ 1.82 TB =  4 =>Number of LUNs = 4 e) Once you filled in the Size > click Next f) Select "Existing iSCSI target (TG0)" > click Next and Create: g) The iSCSI virtual disk will be created > click Close: Because in this example we have 7.28 TB(Free space)/ 1.82 TB =  4 =>Number of LUNs = 4 => We added 4 New iSCSI Virtual Disks for H: volume Therefore, steps a); b); c); d)....g) should be done 4 times. The Initialization process could  take quite a long time. This time depends on the physical capacity of the HDD.   Once the paths are initialized, they should display their status column empty and Virtual Disk status as "Connected". Note: In case the status shows "Error", please restart the iSCSI service or restart the unit. 3. Now go to Configuration Client and right click on the DIP 500 AIO > select Scan Target and check if the LUNs are formatted. Note: If they are "unknown" > tick all the boxes next to the LUNs > c) Hit Format LUN button > OK Recommended  select 4 LUNs at the time Important: If some of the LUNs were not formatted, tick all the remaining boxes with status “unknown” or “HD_FORMAT….” and hit again the Format LUN button Wait until all the LUNs are formatted and click the Activate Configuration button  > OK ... View more