Security: Video

  Related Products: DIVAR IP 7000R2 and DIVAR IP 6000R2   CTN Description   DIP-6180-00N  DIVAR IP 6000 2U W/O HDD  DIP-6183-4HD  DIVAR IP 6000 2U 4X3TB  DIP-6183-8HD  DIVAR IP 6000 2U 8X3TB  DIP-6184-4HD  DIVAR IP 6000 2U 4X4TB  DIP-6184-8HD  DIVAR IP 6000 2U 8X4TB  DIP-61F0-00N  DIVAR IP 6000 3U W/O HDD  DIP-61F3-16HD  DIVAR IP 6000 3U 16X3TB  DIP-61F4-16HD  DIVAR IP 6000 3U 16X4TB  DIP-7180-00N  DIVAR IP 7000 2U W/O HDD (R2)  DIP-7183-4HD  DIVAR IP 7000 2U 4X3TB (R2)  DIP-7183-8HD  DIVAR IP 7000 2U 8X3TB (R2)  DIP-7184-4HD  DIVAR IP 7000 2U 8X3TB (R2)  DIP-7184-8HD  DIVAR IP 7000 2U 8X4TB (R2)  DIP-71F0-00N  DIVAR IP 7000 3U W/O HDD (R2)  DIP-71F3-16HD  DIVAR IP 7000 3U 16X3TB (R2)  DIP-6704-HD 4000GB HDD DIVAR IP 6000/7000      Overview: For recovery of DIVAR IP 6000 R2 or DIVAR IP 7000 R2 one should use only the DVD provided with the particular device. Do not use the DVD for recovery if you are not sure that it is the one delivered with the system. In case the DVD is lost or damaged request the respective ISO image from Bosch Technical Support.  Solution:  Request the ISO image from Bosch Technical Support:   Provide the Serial Number of the device Issue description: What is the reason for the recovery Why it is not possible to use the recovery DVD

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. 

  How to identify Hardware errors based on beep codes Relates to: IP Storage/PC HW - DIVAR IP 6000 R2 and DIVAR IP 7000 R2 Both DIVAR IP units running the BIOS from American Megatrends Inc. (A.M.I) There are PRE BOOT or POST BOOT beeps. Please see the following Acoustic Error Codes. Short Beeps Beeps BOOT Description Possible Root Cause 1x short PRE Ready to Start No error   2x short PRE + POST Can´t restore Parity RAM 3x short PRE Errors in the lower memory block (first 64 Kbytes) RAM 4x short PRE System-Timer error Motherboard 5x short PRE Processor malfunction CPU 6x short PRE No RAM installed RAM 7x short PRE Exception interrupt error CPU 8x short PRE Display memory error Graphic card 9x short PRE CMOS/ROM checksum error CMOS battery, CMOS 10x short PRE CMOS read error Motherboard, CMOS-Clear-Jumper 11x short PRE L2 Cache malfunction Cache, CPU or Motherboard Repeated short PRE + POST Problem with the power supply to the motherboard Motherboard Long Beeps Beeps   Description Possible Root Cause 1x long PRE + POST Power Supply error Power Supply or Motherboard 3x long PRE Error in keyboard interface Motherboard Repeated long PRE + POST Power Supply Malfunction: To high or low voltage Power Supply or Motherboard Beep Combinations Beeps   Description Possible Root Cause 1x long + 1x short PRE Fatal Error on the Mainboard Motherboard 1x long + 2x short PRE + POST Video Problem Graphic card malfunction or wrong installed 1x long + 3x short PRE + POST Video Error Broken RAM-DAC (Digital Analogue Converter) 1x long + 6x short PRE Keyboard-Controller malfunction Keyboard 1x long + 8x short PRE Video Memory malfunction RAM on the graphic card 1x long + 9x short PRE ROM-BIOS-Checksum error ROM-BIOS (Battery or Motherboard error) 2x long + 2x short PRE + POST Video error Video-ROM error or video graphic malfunction 3x long PRE Keyboard-Interface or RAM malfunction Motherboard or RAM 3x l + 3x s + 3x l PRE + POST RAM malfunction RAM

Possible Communication Issue between BVMS 8.0 Central Server and Video Recording Manager (VRM) 3.70 and 3.71 with BVMS 8.0 installed on different Servers. Problem Identification 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 Solution In general please keep in mind, that it is strongly recommended to use VRM 3.71.0029 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.

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?