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
Potential for Data Inconsistency Issues on E-Series Storage Systems
With the controller firmware 11.50.1 and newer version like NetApp controller firmware 11.50.2 an issues are fixed by NetApp, which enforce an immediate update of all E2800 iSCSI Storage Systems (their controllers). In July 2019 BOSCH announced the need to update from all former NetApp controller firmware 08.30.40.00 to newer versions. At that time the Firmware for NetApp E2800 controller recommended was version NetApp Firmware 11.50R1. This is also announced by NetApp on their support websites (see https://mysupport.netapp.com/).
Bosch approval 31st of January 2018
Bosch approval 7th of May 2019
Bosch approval 20th of September 2019
NetApp Firmware 08.30.40.00 no longer allowed for usage
NetApp Firmware: 11.50.R1 no longer allowed for usage
NetApp Firmware: 11.50.2 currently shipped by Netapp via BOSCH
NetApp Firmware: 11.50.2P1 11.50.3 11.60
Please follow our BOSCH Knowledge Base and monitor for updates at this article for important news. Eventhough NetApp inbuild functions for BOSCH video optimized recording 24/7 and generic firmware is used at E2800 iSCSI storage systems, BOSCH is evaluating new firmware versions provided by NetApp on a regular bases. The BOSCH submodel ID 356 ensures that the NetApp system is optimized for 24/7 video recording.
All DSA E-Series (E2800 12-bay) and DSA E-Series (E2800 60-bay)
Example product variants:
DSA-N2E8X4-12AT Base unit 12x4TB High-performance and high-capacity storage system base unit with iSCSI disk arrays, single controller. DSA E2800, 12 x 4 TB HDD, Order number DSA-N2E8X4-12A
DSA-N2C8X4-12AT Dual controller unit 12x4TB High-performance and high-capacity storage system base unit with iSCSI disk arrays, dual controller. DSA E2800, 12 x 4 TB HDD, Order number DSA-N2C8X4-12AT
Note: There are other models with various HDD capacity (e.g. 8TB harddrives and larger) available For more details visit the BOSCH product website
Summary of issue
NetApp® has become aware of issues that could occur when an E-Series controller reboots at certain points during the evacuation of data from a drive that is performed as part of the sequence when a drive is being failed by the controller. As a result, there is a small possibility of data inconsistency on controllers running certain versions of E-Series SANtricity® OS controller software.
First announced in 06/2019: The issues are possible on E-Series controllers running 8.30, 8.40, 11.30, 11.40, and 11.50 versions of E-Series SANtricity OS controller software. The overall probability of these issues occurring is very low, but RAID 1 volumes have a higher probability of encountering the issues than other RAID levels or NetApp Dynamic Disk Pools. These issues do not affect traditional RAID volume groups that have no global hot spare drives because drive evacuation does not occur in this configuration. For information about fixes in these releases, view the readme notes for each revision release.
No workaround available. Controller Firmware update is needed. HDD Firmware update is not in relation to the descdribed issue here, but it is in general recommended to install the latest offered HDD firmware that is recommended by BOSCH and NetApp. The same applies for HDD firmware.
Solution: Update the NetApp Controller Firmware
Upgrade E-Series SANtricity OS controller software to the latest applicable revision release for each platform as soon as possible. Please reach out to your local BOSCH technical team and BOSCH BT-SC/ETP-MKP team to ensure that the relevant NetApp Firmware has been approved to be usable for 24/7 video recording and replay use case. Even the global NetApp Firmware can be installed on BOSCH submodel ID 356
Where to get the Controller Firmware
All customers with a full NetApp NOW support account can download the controller firmware by using the own NetApp user account.
All other customers are requested to contact the BOSCH Support organisation. The controller firmware package can be downloaded fro mthe NetApp website directly. Revisions can be found at https://mysupport.netapp.com/NOW/cgi-bin/software/ See also: https://mysupport.netapp.com/products/web/ECMLP2854621.html
Additional information is available at NetApp and accessible after user registration. First go to https://mysupport.netapp.com/ to register. Product Release Notes from NetApp: https://mysupport.netapp.com/ecm/ecm_download_file/ECMLP2842060
NetApp Support Bulletin, please view the following URL: https://kb.netapp.com/app/answers/answer_view/a_id/1086731 (As the URL can change any time by NetApp, search for the KB id 1086731)
Steps to update
The E-Series SANtricity ® OS package includes data for simplex controller and duplex controller systems and the firmware file itself.
NVSRAM File for for duplex.
NVSRAM file for simplex
and the controller firmware
Download the latest SANtricity OS software files from the NetApp Support Site to your management client.
From SANtricity System Manager, select Support > Upgrade Center .
In the area labeled “SANtricity OS Software upgrade,” click NetApp Support .
On the NetApp Support Site, click the Downloads tab, and then select Software .
Locate E-Series/EF-Series SANtricity OS (Controller Firmware) .
For the platform, select E2800 , and click Go!
Select the version of SANtricity OS (Controller Firmware) you want to install, and click View & Download .
Follow the online instructions to complete the file download.
Attention: Risk of data loss or risk of damage to the storage array — Do not make changes to the storage array while the upgrade is occurring. Maintain power to the storage array.
Possible Communication Issue between BVMS 8.0 Central Server and Video Recording Manager (VRM) 3.7x with BVMS 8.0 installed on different Servers.
Communication can get interrupted and configuraiton might fail if the below desribed actions are not performed. If your system is affected or not is described here as follows:
There can be authentication issues between the BVMS Central Server and the Video Recording Manager in case they are installed on different Servers.
It is possible to see reports at the BVMS 8.x system alarms that VRM reports wrong version
Please check in the VRM debug logging if the following logline indications can be found
CONFIG;DEBUG;SENDING XPATH /SYSTEM/DEVICES/DEVICE as well as HAS NO CONFIGURED NODE, SET TO CONFIGURED
CONFIG;INTERNAL;/SYSTEM/DEVICES CHANGED IN CONFIG. DEVICEID= [DEVICE IP]\0;SYSINFO;INTERNAL;LINE 1 HAS NO CONFIGURED NODE, SET TO CONFIGURED
In general please keep in mind, that it is strongly recommended to use VRM 3.71.00xx with BVMS 8.0. Do not use any older VRM version like 03.71.0022. The 03.71.0029 and Releaseletter is available at the BOSCH DownloadStore (status update 2018-10-26). https://downloadstore.boschsecurity.com/FILES/Setup_VRM_03.71.0029_win32.zip Release Letter: https://downloadstore.boschsecurity.com/FILES/Bosch_Releaseletter_VRM_3.71.0029.pdf
At the VRM system / server, please check and ensure that the following Microsoft software packages are pre-installed:
.NET framework 4.6.2 or higher
Redistributables for Visual Studio 2015
In case one component is missing, please perform the following steps:
Download the missing Microsoft components. Note: When using BVMS 8.0 the VRM is typically a 32-Bit VRM software. Therefore the 32-Bit Microsoft packages are needed. Component that was seen as missing is the >> “Visual C++ Redistributable for Visual Studio 2015” https://www.microsoft.com/en-US/download/details.aspx?id=4814 Please choose the 32-Bit version of that when using with 32-Bit VRM and the >> .NET framework 4.6.2 or higher (NDP462-KB3151800-x86-x64-AllOS-ENU.exe) https://www.microsoft.com/en-US/download/details.aspx?id=53344
Stop the VRM (rms.exe) service in Windows services
Install those components with Administrator rights at the VRM server Reboot the server after installation of the Microsoft components
Check if the VRM service is running and if needed Re-Start the VRM (rms.exe) service
Check that the combination of messages are not longer seen in the VRM debug logging
The VRM package is enhanced and useres should no longer run into this issue with VRM 3.81 and newer versions. Please be aware that BVMS releases are tested with certain VRM verions. This still can offer to install a newer VRM than originally rolled-out in the BVMS overall installer. For all VRM versions 3.7x and below 3.81 it is needed to add this packages.
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.
When using Configuration Manager, each device has a status icon.
The method below shows you how to generate an updated certificate for Bosch IP Camera's and VRM Servers
Here we are talking about Certificates, the Icon is colored Yellow with an exclamation mark.
Using the mouse over Tooltip, the device is saying exactly what is wrong with the certificate connection.
VRM on a DIVAR IP 5000:
Right click on the device to Show Certificates, if you wish to view them.
We can see that there are multiple things wrong.
The Cert is not Trusted
Cert Name mismatch.
First is inconsistent date:
All IP devices and PC’s must be synchronized on Date time page (group General)
Second is invalid certificate
First quick look on certificate requirement level, navigate to Preferences -> Configuration Manager -> Access -> Security:
The certificate must just be valid - self signed certificate matching host name/IP address will be sufficient.
We need to generate a new certificate on Certificate page.
Clicking "Generate certificate" button:
should open a certificate creation dialog - most important options are matching common name and matching validity time.
After the certificate is created correct usage must be set as shown below:
IP Camera Certificate
To apply changes VRM must be restarted.
If certificate requirement is higher, then a validatable chain of certification must be used (This would be setup by a System Integrator or IT Administrator):
Trusted - the signing entity CA (e.g. VeriSign) must be trusted on target PC
Issued by this CA - There is a Micro CA setup on this PC.
The attached manual provides information for Mobile Video Service (MVS) within Bosch Video Management System. You can find:
- how to configure the router and Internet Information Service (IIS)
- how to add MVS to BVMS
- user guide
- some troubleshooting tips
+++ Update: new Excel template file with detailed explanations of all parameters +++
Intro: The Project Assistant offers two ways of importing existing project data:
Option 1) Importing a .bpassist file, which was exported from the app at some point and which contains all information and data ever created/entered inside the app for that specific project. Simply select the "Project Assistant" mode >> click "continue" >> and press "import".
Option 2) Importing from a tab-separated text file. This option may be useful, if you have existing project data, e.g. in an Excel spreadsheet, which you want to transfer into the Project Assistant for further use.
This article deals with option 2 and explains the steps potentially needed before you can refer to the steps explained in the following Youtube video ("Import from file").
Let's assume you already have existing project data prepared in an Excel spreadsheet and you want to transfer that data into a format that can be imported to the Project Assistant
Go to the Bosch Security Systems DownloadStore and download the provided template file "example_project_import_report_template.txt" or the NEW Excel file " 2019_02_20_example_project_IMPORT_template.xlsx" , which also includes detailed instructions and explanations on each parameter.
Import the .txt template file into Excel by opening the template file with Excel and following these steps:
Select "delimited" as well as "My data has headers."
Select "Tab" in the Delimiters section and finish up the Excel import by pressing "Finish".
INSTEAD, you can also use the NEW Excel file, where you can avoid the above described initial import step of the .txt file.
[Option A] According to the provided data columns, copy and paste your existing data from your initial spreadsheet file into the template file (you do not need to populate every column of the template) [Option B] This option works the other way around. Use the Project Assistant header tags, e.g. [ip], [mac], etc., which you can find in the template file and add these tags to the column headers in your initial Excel spreadsheet (cf. screenshot below). The Project Assistant is capable of searching the .txt import file for these tags and of filtering out the corresponding columns (no matter the order of the columns).
Go to "Save As" in Excel and save the newly populated template file as a "Unicode Text (*.txt")" file
Transfer the file to where you can find it with the Project Assistant and start the app
Create a new project
Set a password for the project itself as well as default passwords for the cameras that you would like to assign
That's it - Now it is time to refer to the Youtube video mentioned above
Enjoy using the Project Assistant and feel free to share your feedback with us!
This troubleshooting guide, will guide you through the recovery steps of an DIP, without video data loss
General note: Using a Bosch DIP system without video data disks is a non supported use case, its mandatory to equip the system with data disks to recover the system.
Step 1 - Preperation
Download the attachment repair.zip and unzip the content
Prepare an USB-stick, rename it to SCRIPT
Copy the repair.txt extracted of the attachment on the USB-stick
Insert the USB-stick into an USB-slot of your machine
Insert the BOSCH r ecovery DVD into the DVD-drive
Step 2 - Create RAiD1
Boot the machine and enter the Intel RAiD MENU pressing CTRL + I
Navigate to CREATE RAiD VOLUME and hit enter
Set RAiD level to RAiD1(Mirror), navigate to CREATE VOLUME and hit enter
Exit the RAiD controller, navigate to EXIT and hit enter
Reboot the machine (e.g. press CTRL + ALT + DEL)
Step 3 - System Recovery
During the reboot, boot from DVD, press ENTER as the line will displayed
In the System Management Utility, click on CONSOLE
Type into command line "diskpart.exe" hit enter
Type into command line "list volume" hit enter and search for your USB-stick called SCRIPT, note down the assigned drive letter (LTR)
End diskpart.exe by typing on the command line "exit" hit enter
Type into the command line "diskpart.exe /s [YOUR_USB_DRIVE_LETTER]:\repair.txt" hit enter
Wait until the script has been finished and CLOSE the console
Step 4 - System Recovery
On the System Management Utililty click on SYSTEM RECOVERY (back to factory default)
NOTE: Do not select Initial Factory Setup, this will wipe all existing data!
As the recovery has been completed, click on OK to confirm and reboot
Do not eject the DVD and follow the instructions on your screen to initialize the system.
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 attached document will provide a basic explanation and simple examples of the interfacing (scripting, calling functions by external applications) functionality in Bosch Video Management System. The interfacing functionality is based on Bosch VMS SDKs. The Bosch VMS SDKs contain all interfaces, object types and methods that are needed for automation and integration to and of Bosch VMS.
The document can be found in the attachments section on the bottom of the page or at the right side of the page. Please look for the attachment icon.
The attached document describes the settings you must perform after having installed BIS and BVMS on the different computers. Ensure that the installations of BIS Server and BVMS Management Server were performed successfully on separate computers. Additionally you must have purchased and activated an OPC Server License for BVMS.
The document can be found in the attachments section on the bottom of the page or the right side of the page. Please look for the attachment icon.
In rare situations it might happen that the mirrored SSD drives used for the Operating system need to be set-up from scratch when not only one, but both SSD drives used in the RAID-1 mirrored setup need to be exchanged with two new drives (e.g. Both SSD have been removed or were missing during first install attempt or imaging process from the recovery DVD. It is strongly recommended to always open a Technical Support Case at the local BOSCH Security Systems Level 1 Support team / help desk. Report the the following details to the support: Is the system registered at BOSCH? What is the System Serial-No.? What is the storage capcity of the new inserted two SSD drives at the rear side of the used DIVAR IP 70000 R2 system?
Firmware The table below lists the firmware versions which are used in the BVMS 8.0 system test. Bosch Video Stitcher 18.104.22.168 VideoSDK 6.12.0078 Firmware MPEG-4 4.15.0002 Firmware CPP3 5.74.0004 Firmware CPP4 6.41.0037 Firmware CPP5 6.30.0047 Firmware CPP6 6.41.0037 Firmware CPP7 6.41.0037 Firmware CPP7.3 6.41.0037 Firmware CPP-ENC 5.53.0004 (for VIP X1600 XFM4) Firmware CPP-ENC 5.97.0005 (for VJT XF E family, VIDEOJETdecoder 3000) Firmware X1/X2 2.53.0005 VIP XD HD 1.8 VJD 7000 54.8.2 VJD 8000 9.00.0134 VRM 3.70.0056 VSG 6.42.0010 iOS 9.0.2 / 9.3.5 / 10.3.1 Web Client 11.0.96 Software The table below lists the software versions which are used in the BVMS 8.0 system test. BIS 4.3, 4.4, 4.5 DiBos 8.7 BRS 8.10/8.11 Allegiant MCS 2.94 / 2.95 Intuikey Keyboard 1.96 DVR FW Version 2.3.2 (DVR400 / 600) 3.61 (DIVAR 700) 2.5.0 (Divar AN 3000/5000) 1.2.1 (Divar Network/Hybrid) SQL Server 2014 Operating systems Operator Client Windows 8.1 64-bit; Windows 10 64-bit creators update (1703) Config Client Windows 8.1 64-bit; Windows 10 64-bit; Windows Server2012 R2 64-bit; Windows Server 2016 64-bit. Management Server, Mobile Video Service Windows Server 2008 R2 SP1 64-bit; Windows Server2012 R2 64-bit; Windows Server 2016 64-bit. Cameo SDK 22.214.171.124 BVMS SDK 126.96.36.199 RCPP 188.8.131.52 Hardware drivers NVIDIA Quadro Quadro Pro Driver for Microsoft Windows 7/8.1 (64-Bit) 385.08 (28.June 2017) Quadro Pro Driver for Microsoft Windows 10 (64-Bit) 385.69 (21.September 2017) AMD FirePro Unified Graphics Driver for Windows 8.1/10 (64- bit) 17.Q3 (27.July 2017) Bosch strongly urges customers to use the driver and software versions mentioned above. This ensures that the software can perform its task reliably.