Are you designing a BVMS or DIVAR IP based video surveillance system? Do you need to calculate the storage consumption of a Bosch video surveillance system? The BVMS Project Checklist is an Excel-based tool which makes it easier to design a BVMS system. There are two files attached to this article:
The project checklist (Excel) itself.
Connectivity problems after DIVAR Mobile Viewer APP upgrade from v3.0.0 to the new v3.1.0
As result of a software bug in the APP problems in the connectivity can occur in case the DIVAR hybrid/network is running firmware v3.0.0 or below. Running firmware v3.1.0 does not show the problem.
This problem exists for both Android and IOS app platfoms
DIVAR Mobile Viewer app 3.1.1 for both Android and iOS have been released and are available on the stores. This version is compatible with previous DIVAR hybrid/network firmware v3.0.0 and 3.1.0
Additional info for DIVAR AN 3000/5000
For the DIVAR AN 3000/5000 we just learned that the DIVAR Mobile Viewer app v3.1.1. can consume more than one session per device. This typically happens when in the Live Preview the "Device List" (top right icon) is used to open all cameras simultaneously. This seems only to happen as a first action when you open the app. This can result is a failing connection showing the message “System is busy”.
For the moment please apply these workarounds avoiding this connection problem: - Change the number of remote sessions allowed (default=4) in the DIVAR AN 3000/5000 configuration to 64 (Menu, Settings, Network, Max. connection) OR - Avoid the use of "Start Live Preview (16)" in "Device List" as an first action. By viewing one camera only as first action showed that new session consumption was prevented.
In case of occurring connection problem: close and restart the DIVAR Mobile Viewer app. This problem seems not to occur when using Android or for accessing DIVAR network/hybrid.
How can I protect my security system, from an IT security perspective?
The attached document explains how the security system can be hardened. Additionally the BVMS - Network Design Guide includes best practices for desgning a secure network.
BVMS customers can download camera updates free of charge, in order to integrate approved, third-party cameras. BVMS scans for third-party cameras, automatically configuring motion and other key events; it also enables installers to configure the most important settings for third-party cameras from a single user interface, without the hassle of having to access the websites of other camera manufacturers.
The attached files include a list of compatible cameras and the ONVIF mapping files for each specific BVMS version.
The attached documents should help you to make the upgrade process as smooth as possible. The upgrade itself is not restricted to BVMS software only. The supported software and firmware versions can be found in the release notes of the related BVMS version.
An attachment is added to this article for each BVMS version. Currently the upgrade guides for BVMS 8.0 and 9.0 are attached to this article. From BVMS 10.0 onwards a description on how to migrate systems has been included as well.
Related Products: Configuration Manager 7.00 and above.
This article shows how to use recorded video in Configuration Manager in order to calibrate a camera and to configure a task.
Camera Calibration using Recorded Video
It is possible to calibrate camera using already recorded video in Configuration Manager 7.0. This feature is independent of the camera firmware version.
Configure a Video Analytics Task using Recorded Video
It is possible to configure a Video Analytics Task, using already recorded video in Configuration Manger 7.00 and above. This includes initial Task configuration, verification and then further performance analysis over the time and fine-tuning of the task parameters.
Note: There are multiple video analytics how-to videos in the following lists:
Calibration playlist: https://www.youtube.com/playlist?list=PLz97rFi-OzLfI2F4sP-ocX3BhX0rtJvgt
Video Analytic how-to playlist: https://www.youtube.com/playlist?list=PLz97rFi-OzLdPrzs-SR-g1oo4RkV9mvf5
Related Products: BVMS Operator Client
This article describes the initial steps one can take for troubleshooting BVMS display issues (during live view or playback). It also summarizes what initial information and logs are needed for support in order to start the issue investigation.
Check and eventually update the version of your Graphic Card driver.
During BVMS system tests there were documented cases of display issues related with out of date Graphic card divers. It is important that the Graphic Card driver of the client is up to date. Find the supported version of the Graphic Card driver in the corresponding to your BVMS version Release Notes (https://downloadstore.boschsecurity.com), in the section Hardware drivers.
Please prove the following information to support.
Is the issue camera type / FW dependent
Are all the devices in the system affected
Is the issue existent for all BVMS Operator Clients in the system
Is the issue existent for hardware decoders, for camera Web Interface or other display Clients
Is the recording, the playback or are both affected
Please provide Log files
BVMS ConfigCollector logs keeping the following conditions:
From the machine that shows the issue
Including VSDK logging – please follow the steps from the article How to collect Video SDK log files
Movie showing the display artefacts can be helpful
Status February 25, 2017
BOSCH offers and confirms that since February 2017 the firmware version 3.180.05-1562 can be used with the LSI MegaRAID Controller. In case there are newer versions supported and recommended with BOSCH DIVAR IP this will be announced in cooperation with the Product Management.
For DIVAR IP units (e.g. DIVAR IP 6000) BOSCH BT Security & Safety Systems offers an firmware update for the internal MegaRADI Controller.
It could happen that in the Megaraid Software the user can see the following: potential non-optimal configuration due, PD commissioned as Emergency Spare error.
Here we provide the steps to update a DIVAR IP system:
Using MegaRAID Storage Manager utility under OS
1) Open MSM, Right click on Supermicro MegaRAID controller to be updated and click Update Controller Firmware
2) Click Browse to search for new firmware
3) Select the new MegaRAID controller firmware
4) Click OK to continue
5) Check the “Confirm” box and click OK to continue
*** Wait for around 1~2 minutes to complete
6) Click OK once firmware update completed
7) Reboot the system and check firmware version in controller OPROM banner during boot. At the section Revision you can see version 3.180.05-1562
😎 Check firmware version using MSM in OS When selecting the "Supermicro SMC 2208 (Bus1, Dev 0) device you can see on the right the "Firmware Version" = 3.180.05-1562
The firmware *.rom filw is available via the following link - inside the ZIP file:
This Firmware Version is subject of change. Any new version must be announce by BOSCH PRM responsible for DIVAR IP via the BT-ST/ETP-MKP2 organisation and BOSCH support at BT-ASA here in the BOSCH Knowledge Base.
The RAID combines two or more physical drives into a logical unit presented as a single hard drive to the operating system. There are currently six basic RAID levels: RAID 0, RAID 1, RAID 0+1, RAID 1+0, RAID 3, RAID 4, RAID 5 and RAID 6.
The scope of this article is to provide basic information for the levels RAID 5 and RAID 6 and to compare them from point of view of performance and security.
Hot spare is a drive that acts as a stand by drive in RAID 1, RAID 5 or RAID 6 volume. It is fully functional drive that contains no data and is not used during normal operation. If a drive from the volume fails, the controller reconstructs the data from the failed drive to the hot spare drive.
A RAID 5 array is designed to protect against the failure of a single disk within the array. Because of the way that RAID 5 works, the total capacity of one disk is lost to overhead. If, for example, a RAID 5 array contained five 10TB disks, then the array’s usable capacity would be 40TB.
A RAID 5 (with Hot Spare disk) array can be configured to treat one of the disks as a hot spare. Then one of the disks is reserved as a replacement in the event that a disk fails. For the above example with five 10TB disks, this would decrease the example array’s usable capacity to 30TB.
A RAID 6 array is designed to protect against two simultaneous disk failures. However, the price for this extra protection is that two disks' worth of capacity is lost to overhead. As such, a RAID 6 array made up of five 10TB disks would have a usable capacity of 30TB because 20 TB is lost to overhead.
The performance during Normal Operation is measured in IOPS (Input/output operations per second) and as a sum for all the disks (excluding the Hot Spares and decreased for writing parity data) in the array. As a rule of the thumb, the higher the overhead associated with writing parity data (in the above example RAID 5 with Hot Spare causes the same overhead like RAID 6) the lower the IOPS.
The reason for implementing RAID arrays is to secure the data. The level of protection does not directly correlate with the overhead. From the above example both RAID 5 with Hot Spare and RAID 6 have same capacity, but offer different level of protection. In case of failure of RAID 5 array with Hot Spare, the Hot Spare is activated and the rebuild process start immediately. The system can recover from a single disk failure and during the recovery, process is vulnerable to second disk failure. Therefore, RAID 5 and RAID 5 with Hot Spare disk offer the same level of protection – single disk failure. In contrast, if a disk fails at RAID 6 array, the recovery will start only after the faulty disk is replaced manually. However, if during the recovery process second disk fails, the RAID 6 array will stay functional.
The password for the local admin and diagnostic port is set to the same starting with E2800 controller firmware 11.40.2 or later.
In case a user does not know his password any longer, it is not possible to reset and re-configure this password by using the diagnostic port (serial port on the rear side near the uplink ports of the controller). With controller firmware older than 11.40.2 it was possible to reset the Administrator Password needed for configuration. But older NetApp controller firmware cannot and must not be used any longer due to other technical reasons. When accessing the Management Port IP to enter the WEB GUI of the NetApp E2800 system for configuraiton or support data collection, the Administrator Password is required. For the time being this is reported to NetApp to work out a solution for all NetApp customers and BOSCH.
Solution and Procedure:
Right now, BOSCH and our customers have no documented instruciton or procedure to remove / reset the password. We are working ont hat with high preassure and awareness. We kindly ask all customers requiring access to the configuraiton but having not the Administrator Password on hand for configuraiton, to reach out to BOSCH support and ask to sent the requewst immediately up to a Levle 3 Ticket to the Gatekeeper team at BOSCH BT-SC/ETP-MKP2 or BT-VS Support in the BU.