About Central_Support

Question   What the “Storage state failure” alarm message means in Operator Client?   Answer   A video surveillance system uses two different types of communication:   Control traffic is used for sending controls and events between two components of the system. This includes, for example, system events ("storage state failure") and security events ("IVA alarm 1 triggered"), but also pan-tilt zoom controls. Media traffic contains the actual video. This is mainly used for live viewing and recording.   Some events, for example the "storage state failure" does not seem to impact the system's capability to record, but it does indicate that the specific camera is struggling to continuously record. To ensure a stable and reliable system, it is highly recommended to investigate all events that are enabled by default. A sign-off on the system's delivery should only be done without any active system events.   The "storage state failure" alarm doesn't always mean a recording error unless there is a gap at the time of the error for that camera that reported it. It is an error of the iSCSI protocol; it means that when the camera releases the connection for a certain block it has not received a response back from the iSCSI target in a certain time.   Good to know: The Central Technical Support Team would suggest you verifying the physical connection between the camera and the storage. If you have multiple cameras in the system and this happens on all cameras, we suggest checking to see if the server has any network issues. Please check the windows system event logs to see if issues with the network connection appear. When contacting the Central Technical Support team, please ensure first that you have prepared the following: cameras maintenance log files (How to collect logs from your Bosch IP Camera or Encoder?) VRM logs retrieved from the VRM monitor as shown in picture below (1) please set the date and time so that all relevant info gets exported. (How to collect VRM logs with VRM (v3.82/ v3.83/ v4.00)?) together with the block info of the cameras (picture point 2 and 3)   ... View more

Question   Which are the RCP commands to disable or enable IVA on Bosch cameras?   Answer   First recommendation would be to configure the mode for IVA as a trigger, setting IVA as Profile 1 for “trigger off” and IVA as silent for “trigger on”. Then use the following CGI commands to switch the virtual trigger input on/off:   // Virtual input off http://192.168.0.105/rcp.xml?command=0x0a8b&type=F_FLAG&direction=WRITE&num=1&payload=0 //Virtual input on http://192.168.0.105/rcp.xml?command=0x0a8b&type=F_FLAG&direction=WRITE&num=1&payload=1 ... View more

Question   Where are the DIVAR IP 2000 EZ reset options ?   Answer   To access the "Reset" options of a DIVAR IP 2000 Recording Appliance, you have to open the Appliance's "Dashboard". From the Dashboard select the "Configuration" tab in the top right hand portion of your browser > System menu > Service submenu From the "Service" submenu select the "Reset" menu on the right portion of the page. Once you have selected the "Reset" menu you will have two basic options: Format disks only: This option will only format the video disks of the appliance. Selecting this option leaves the appliances database and video devices untouched Reset all to factory defaults: This option not only formats all video disks but resets the appliances database to factory default as well. Video devices will no longer be associated with the appliance and any passwords that you set in the Wizard will no longer apply to the VRM database Additional reset option:  Selecting the "Also reset connected devices" will default all video devices associated with the appliance back to their factory default state, to include: Device passwords Encoder profiles (FPS and Resolution) Motion Detection Areas IP information ... View more

Thanks to its integrated, long-lasting wiper, the MIC IP starlight 7000 camera captures images of the highest quality all year long, regardless of the weather. This article is meant to provide you with the step-by-step guide to activating the wiper and the white lights illuminator option, if your camera is equipped with both of them. Article requirements: MIC IP starlight 7000 HD Bosch Video Management System  Workstation   Step-by-step guide   A. First, you need to set up the relevant Aux Command/ s of the camera inside BVMS. According to the Operation Manual (page 82), the AUX commands for the wiper and the white lights are as follows: 1.In Configuration Client, go to Cameras and Recording tab > select the camera for which you want to set the AUX commands and click the PTZ Settings button:   2. Select "Aux Commands" tab and add the AUX commands for Wiper and White light illumination > click OK:   3. Once this is done, you can use the user event Event Button Pressed in Events tab > System Devices > Operator Client Event Buttons > Event Button Pressed There are 4 user events that you can choose: Set the trigger alarm to "Always" Leave the Log as "Always" Don't forget to save your changes!   4. Then, under Alarms tab > System Devices  Here you can set the title and the color of the Alarm you will see in the Operator Client You can specify the workflow for this alarm by clicking the  More - “Alarm Options> select ”Workflow tab. You can choose to set auto-clear the alarm after configured time. Therefore, please tick the second option (‘Alarm Settings” dialog box)   5. Make sure that the users have the access to the Operator Event Button pressed.  In User groups tab > select the relevant Group and tick the options that the users are allowed to use in the Operator Client.     6. Make sure that your camera is in the Logical Tree from Maps and Structure tab and press Save and Activate the changes.   B) Then, under the Operator Client, you can right click on the server: at the top “Logical Tree”. You will get a menu where you can select the correct User Event button.   This will activate trigger the event.   The wiper and the White light illumination of the MIC IP starlight 7000 HD camera can now be activated by clicking on the arrow near the AUX Commands. One drop-down list will be displayed. Click the desired Aux command you created before. In this example, we chose "Wiper wipes 5 times":   White light ON/ OFF:     ... View more

Logs are definitely important. We would even say they are the most important thing for a system to function properly. At some point, the Central Support Team may ask you to provide them with the BVMS Configuration Collection. This article explains you how and where you can get the BVMS Configuration Collection of your system.   Step-by-step guide   You need administrative rights to use Bosch VMS Configuration Collector. Bosch VMS Configuration Collector is used to collect Bosch VMS relevant items and pack them in a single .zip file. This .zip file contains a configuration report with all relevant diagnostic information to help Bosch Support to understand, reproduce and resolve customer issues.   The software is automatically installed during installation of Bosch VMS. You can start the software on each computer where at least one Bosch VMS software module (Central Server, NVR, VRM, Operator Cllient) is installed.   1.Starting Bosch Configuration Collector: From the Start menu, select Programs > Bosch VMS > Configuration Collector or From Computer > Local Disk (C:) > Program Data > Microsoft > Windows > Start Menu > Programs > BOSCH VMS:   2. Open Config Collector > enter a title for your configuration report and click the “Generate configuration report” button and wait until the process is done and the .zip file is created on your Desktop as per default.   Notes: A) To change the point in time for that the report is valid: Click the Description tab. In the Date and Time fields, enter the desired values. To change the output directory for the .zip file B) To view the content of the .zip file before it is created: Click the Configuration tab. In the left pane you see the categories and their content of the information that will be stored in the .zip file. C) To add an attachment: Click the Attachments tab. Use the icons for inserting attachments of your choice. or Drag files or directories from Windows Explorer into this window. or Click Insert to insert screen shots from clipboard.   ❗ A complete Config collector contains the following folders: BVMS DiBos DirectX MVS (if the MVS is on the same machine. In this exaample it is a DIP 7000 R2) Registry System Video Streaming Gateway Vidos VRMServer   The most important folders used at the start of the troubleshooting are the following: BVMS Folder System folder VRM Log Folder   1.BVMS Folder   In the bellow snip, you can see the folders of a BVMS Config collector export In a Standalone System, the MVS folder should not be present (because it is not allowed to have the MVS server to be on the same server as the BVMS server nor the VRM Server) and the VRMServer folder might be missing as well because it might be on a different machine. In that case, config collector needs to be run on those machines.   Configuration log and Call sequencer log need to be consulted at the start of the troubleshoot. They can be found in the Bvms folder from BVMS Config Collection In the Configuration log, a short system overview can be seen In the Call sequencer log, information about camera Firmware can be collected (applicable for BVMS 8.0 and above)   2. System folder   Here, we have the System Info file:   From the SystemInfo file, we can extract the following: Operating System CPU RAM GPU System manufacturer and model (if it is an OEM device, e.g Divar IP, HP Workstation) BIOS version GPU Driver versions   3. VRM Log Folder   Before making any changes, collect logging from all the affected systems/components Including VRM, Camera, iSCSI etc. (please do not reboot the camera before the Maintenance_log has bee extracted) Enable higher level logging: Debug & RCP+ (these 2 are the most common logs needed for further investigation) via Web browser go to https:// <VRM IP Address> /debugSettings.htm   or from BVMS Configuration Client     Bellow you can find the path to the VRM logs collected by Config Collector:   VRM logs - Tips and Tricks: In a normal operation, the VRM logs should have roughly the same size / day. If an event occurred, the VRM logs from a day are increasing in size, these logs need to be checked first. If the problem occurred for longer than 30 days, then this is not applicable because probably the size will fluctuate daily.  First thing that needs to be checked is the VRM version, which is the first line in a VRM log. If this line is also present further down in the log, it means that the VRM restarted for whatever reason. This needs to be corelated with the Windows logs to see if it was a scheduled restart of the machine, or an improper shutdown due to bad operation or power failure. Second line is the HW info of that machine. You can conclude from here if it is a DIVAR IP or a 3rd party server. Key words that can be searched in the VRM log: "device disconnected" - can hint to a network issue or a problem with a camera. This can be corelated to "connection established to device". If multiple devices are having this issue and all seem to disconnect at the same time, the first hint might be a network issue. If only one device has this behavior, depending on the time it took for the VRM to reconnect to the device it can be  "different time" - time synchronization between the cameras and the VRM server is off and needs to be checked. Recording issues might occur.  "device runs out of storage" - can hint to either a misconfiguration of the retention time or if multiple iSCSI targets are configured in the system one or more are offline "target offline" - iSCSI target offline. Depending on the model, there are different ways to troubleshoot. If Netapp units are involved, the support bundle file is needed to check the status of the unit. Check the following articles and find out: How to download the support bundle file for DSA E-Series E2800? How to download the support bundle file for DSA E-Series E2700? If DIVAR IP's are involved, the first step is to check if the iSCSI service is running and if there are errors in the MegaRAID. ... View more