Bosch Building Technologies

    cancel
    Showing results for 
    Search instead for 
    Did you mean: 

    Security: Video

    Sort by:
    Friday
     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.
    View full article
    a week ago
    Keeping an eye on system messages and to collect logging data at a central site just got a whole lot easier General information: Syslog feature is implemented in all IP BOSCH Products for many years. Since latest firmware versions e.g. Firmware version  6.xx and even more enhanced in firmware 7.1x and later a GUI on the WEB-page of the IP cameras was added. The BOSCH IP cameras as network devices can continuously send system messages via Syslog to a Syslog server software. This funciton must be activated and configured before. One aspect is to setup a Syslog server that can receive such information and Inside the IP cameras the IP of such a Syslog server can be configured in order to tell the IP camera to whic hSyslog server the messages should be send to. Enabling this funciton will allow a continous monitoring information even troughout a complete IP camera power cycle (reboot) as the camera starts connecting to the syslog server IP as soon it is getting back online. Network administrators usually monitor these messages and should also be able to offer and inform about Syslog server IPs to use.  Tools as Syslog server: There are many different monitoring tools available and common in the market. Configuration and technical analysis functions of those are in responsibility of those software vendors. Examples of some easy tools to start working with can be e.g.: PRTG NETWORK MONITOR from PAESSLER Kiwi Syslog Server EventLog Analyzer from ManageEngine and many more. When to make use of SYSLOG Especially for incidents that happen unpredictable and do not necessarily trigger an alert message can be analyzed with syslog even throughout reboots of equipment (switch reboot / IP camer reboot etc.) as the syslog reconnects to the destination server. As well in cases were many systems / devices are involved this can be very helpful as the different loginformation can be compared by having the same time bases (Syslog server time when messages arrive).  By using the BOSCH Configuration Manager (stand-alone configuration software) or Bosch Configuration Client software (part of BVMS) can help to quickly setup the syslog function for many cameras in just a few mouseclicks.  💡 Via the device webpage or above mentioned configuration tools it is easy to configure loggings that are also sent out via syslog. There are different levels of logging information that can be sent out:  Event-log data alarm-data debug logging (on advice of a BOSCH expert) In addition there is a chance to download recent history of such data (if enabled before) via the configuration section at the device webpages. Details are described in the product manual. For continous long-term monitoring the syslog function is best choice. Please feel free to get contact with your Level 1 support contact and if needed 2nd Levle support agent to get commands for section (3) debug logging syslog printouts if needed.   
    View full article
    a week ago
    Compared to hardware, in which it is relatively easy to define an end-of-support concept based on the expected lifetime, software behaves totally different. In theory, when the environment does not change, software can still be running ten years after it has been installed. As new versions of the software are released regularly, it is important for customers to know what they can expect from Bosch Building Technologies when the software is purchased. This document describes how Bosch Building Technologies handles the life-cycle of the BVMS, BIS, AMS, and APE, and in which state a specific release can reside. Additionally this document lists the up-to-date situation for all of those software packages.
    View full article
    100% helpful (1/1)
    2 weeks ago
    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.
    View full article
    3 weeks ago
    Collect Video SDK Logs for VSDK based applications:
    View full article
    3 weeks ago
    Symptoms The Activation Key provided from SLMS cannot be activated in BVMS. During the introduction of BVMS 10.0 the BVMS Lite16, 32, and 64 base licenses were not introduced and succeeded by BVMS Lite 10.0 (8 channel base package). Existing BVMS Lite customers might still want to upgrade to BVMS 10.0. Solution The LIF file attached to this article (in the zip archive) can be imported in BVMS Lite 10.0 installations using the license manager (the license manager can be found in the "Tools" menu of the BVMS Configuration Client). Once imported, BVMS Lite 16, 32, 64 systems that are covered under SMA can be upgraded.    
    View full article
    3 weeks ago
    Related Products: BVMS, application crash, memory dump This article lists the scenarios in which technical support normally request dump file from a BVMS system. It contains general guidelines how to create a dump file for BVMS system and provides links to more concrete articles, that correspond to particular issues and exact steps to create a dump. BVMS dumps are needed to troubleshoot the following types of issues: Application crashes – dump is expected to provide more information about the cause of the crash and its origin. Memory or handle leaks – dump is expected to point to their origins Deadlocks, freezes and hangs – dump is expected to point to their origins Recommended tool to create BVMS dumps. The recommended tool is Procdump. It is a command line tool which must be started from the command shell. Development provides couple of .bat files that start Procdump with predefined parameters and cover the most common dump creation cases. The tool as well as the set of .bat files are attached to this article: BVMS_DumpTools_V2.zip The batch file names follow a naming guideline: <Executable>_<Dump use case> , where <Executable> is one of: ConfigClient ConfigWizard OperatorClient ManagementServer ArchivePlayer ExceptionTest and <Dump use case> is one of SingleDump TwoDumps DumpOnException DumpOnHang ActivatePostmortemDebugging There are 3 possible error scenarios and corresponding dump creation methods: Dump creation for reproducible crashes that trigger Windows Error Reporting Run the affected application/service (Operator Client, Configuration Client or Management Server Service) Reproduce the steps that lead to the crash Leave the Windows crash dialog open Run the corresponding batch file for creating a single dump: *_SingleDump.bat. E.g. run OperatorClient_SingleDump.bat to create a single dump of the Operator Client process. Provide support with the resulting .dmp file a description of the steps to reproduce the problem ConfigCollection Note: attached you can find a configured example for this scenario and application Operator Client - BVMS_OC_dump_onException.zip Dump creation for reproducible memory or handle leaks Run the affected application/service (Operator Client, Configuration Client or Management Server Service) Run the corresponding batch file for creating two dumps: *_TwoDumps.bat. E.g. run OperatorClient_TwoDumps.bat to create two dumps of the Operator Client process. Note that by default, the delay between the two dumps is set to one hour (3600 seconds). Depending on the magnitude of the memory leak, you might want to increase/decrease the delay. To do that, edit file *_TwoDumps.bat: replace value "3600" by a value that fits your needs e.g. a value of "7200" will create two dumps with a delay of two hours. Reproduce the steps that lead to the memory leak. Wait until the second dump was created. Provide support with the resulting two .dmp files a description of the steps to reproduce the memory leak a ConfigCollection Dump creation for crashes/hangs/freezes that are hard to reproduce Deactivate the restarting option for Operator Client / Configuration Client: To deactivate the restarting option for Operator Client / Configuration Client: edit ..\Bosch\VMS\bin\ConfigClient.exe.config or ..\Bosch\VMS\bin\OperatorClient.exe.config. Navigate to section <appSettings> add a new entry <add key = "DisableExceptionHandling" value="TRUE" />. Run ActivatePostmortemDebugging.bat Run the affected application/service (Operator Client, Configuration Client or Management Server Service) As soon as the issue appears, check whether the dump was created. Provide support with the resulting .dmp file description of the steps to reproduce the crash ConfigCollection Note: attached you can find a configured example for this scenario and application Operator Client - BVMS_OC_dump_Just-In-Time-Debuger.zip
    View full article
    ‎11-05-2019 03:19 PM
    This article will guide you how to remedy invalid expansion licences on your Bosch Divar IP 5000 all in one.      Error indication Dispite that the registration of your additinal purchased licencens has been completed successfully. The licecens may become invalid  after a  following reboot. This behaivor is caused by switching the MAC address of your teaming interface. Solution In order to prevent such behavior or even to revoke your licences as they are already invalid, please perform the follwing steps:  Step 1 Download the attachment MacAddress.zip (2 KB) and provide it locally to your DIP all in one    Step 2 Unzip the archiv, it should extract two files (setMacAddress.cmd  / setMacAddress.vbs) please do not alter or move the files!   Step 3 Open the command promt (CMD) as adimistrator, e.g.  right-click on the windows button and click on Command Promt (Admin) Step 4 Run the "setMacAddress.cmd",  for this purpose navigate to the location where you have stored the unzipped files  and call   the "setMacAddress.cmd"  file      YOURPATH\setMacAddress.cmd  and hit enter    Step 5 Press the spacebar to continue, after the cursor is blinking again you can close the CMD   Step 6 Reboot your device, in order to complete the task.              
    View full article
    100% helpful (1/1)
    ‎11-05-2019 11:47 AM
    Introduction: Bosch has been providing 2 types of VRM packages: a 32bit and a 64bit version. Since VRM 3.82 we are only offering the 64bit version. As all of our released DIVAP IP units started off as 32bit VRM which includes a Transcoder service. Problem If you do not use the Start.exe included in the VRM Master Installer, you will not be offered the oppertunity to also upgarde the Transcoder. Just running the Setup_VRM_Service_<version>.exe found in the <Install\Bosch> folder, will cause the Transcoder service to stop functioning! This includes if the upgarde is done via BVMS installer. Since BVMS 10.0, VRM 3.82 "64bit" was implemented. Due to the fact that BVMS does not manage the transcoder, it was not installed. Also see Firewall settings: HowTo Configure Windows Firewall Rules, includes PS script to adjust the VRM 64bit and Transcoder rules. Solution Download the appropriate VRM version from our Downloadstore Run the Start.exe Deselect all components and choose only the Transcoder Service   Click on "Install" To confirm that the Transcoder is fully functional, open your browser and navigate to the VRM Monitor: https://<VRM_IP_Address>/ Log in with you Credentials    
    View full article
    100% helpful (3/3)
    ‎11-04-2019 10:06 AM
    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.
    View full article
    ‎10-30-2019 08:07 AM
    Symptoms During the introduction of BVMS 10.0 the BVMS Plus unmanaged site expansion licenses were not introduced, even though this functionality was announced to be available. Solution The LIF file attached to this article (in the zip archive) can be imported in BVMS Plus 10.0 installations using the license manager (the license manager can be found in the "Tools" menu of the BVMS Configuration Client). Once imported, the purchased licenses (MBV-XSITEPLU-100) can be activated.
    View full article
    ‎10-29-2019 02:10 PM
    Do you want to know more about designing a BVMS system?
    View full article
    100% helpful (1/1)
    ‎10-28-2019 08:43 PM
    BVMS Installer - Windows Pending Restart Message Issue:  The pop-up dialog window message: "Setup has detected a pending restart.  Please reboot the system and rerun the installation"  appears when attempting to run the valid BVMS windows installer package. BVMS Installer Pending Restart Message   Cause:  This is a known Windows specific problem when another (non-BVMS) installer does not properly manage its creation and deletion of the “PendingFileRenameOperations” registry key. The most common user created way for this key value to be left resident in the system is when an installation prompts for a restart, yet the system is not expeditiously restarted.     Resolution:  A. Restart the affected workstation B. If the issue still persists, delete the orphaned "PendingFileRenameOperations" registry key value Open a registry editor, such as Regedit.exe or Regedt32.exe.   Navigate to "HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\" In the right navigation pane, right-click the "PendingFileRenameOperations" key value and select delete Close Registry Editor. Run the software Installer again as Administrator   Note:  This message is not a Bosch product failure message. This is a problem within windows and it's registry clean-up handling.  This is a Windows work around. 
    View full article
    100% helpful (1/1)
    ‎10-28-2019 03:38 PM
    BVMS Mobile Video Service - Creating a Self-Signed Certificate to establish a trusted connection Some sites may request or require that the connection to the Mobile Video Service is a trusted connection.  The following procedure will allow you to create a self signed certificate to allow a trusted connection between a web browser and MVS. -Navigate to the Microsoft Management Console Run command mmc.exe Go to File ---> Add/Remove Snap-in… Highlight Certificates and Add for Computer Account You should see certificates listed for Local Computer Save a copy of this console to the Desktop -Run Windows PowerShell ‘as administrator’ on the MVS Server Run the following commands in Windows Power Shell to create the self-signed certificate including the IP address of the MVS and the DNS name so both will work when accessing from a web browser. $todaydt = Get-Date $20years = $todaydt.AddYears(20) New-SelfSignedCertificate -DnsName "mvsIPaddress",”DNSname” -notafter $20years If creation was successful, you will see a thumbprint with a hash as well as the subject CN=ipaddress -Navigate back to your saved MMC console Find the newly created certificate under the Personal  ---> Certificates directory Copy the Certificate to Trusted Root Certification Authorities ---> Certificates directory -Navigate to the IIS Manager Highlight the server machine name on the top-left and then double-click Server Certificates Double-click the created certificate and verify that a private key corresponds to the certificate and that the certificate is OK under the Certification Path Expand the server machine name on the left to reveal the Sites Highlight BoschIVS Select Bindings… on the far right-hand side Edit the Binding for 443 Select the newly created certificate under the SSL certificate dropdown Select OK Click Yes that you want to change the binding Add… new binding Type: https Port: 444 Choose BoschVms in the SSL certificate dropdown Click OK -Navigate to the BVMS Config Client to edit the MVS URL Change the MVS URL to reflect port 444 Example:  https://mvsIPaddress:444/mvs Red X should go away Save/Activate  (BVMS will be bound on the new port and still be able to communicate with the MVS server -Open Internet Explorer (as administrator) and navigate to the MVS URL using the IP address or the DNS Name Continue to the site with the certificate error Click on the certificate error in the navigation bar Click View Certificates and then Install Certificate Install for the Local Machine Place certificate in the Trusted Root Certification Authorities store Click Finish and close out the browser Open IE again and navigate back to the MVS.  There should be no more error.   *The reason behind changing the port to 444 is to make browser access for basic users easier.  This way basic users only have to enter the IP address or DNS name and do not have to enter a special port in the URL.    
    View full article
    100% helpful (3/3)
    ‎10-25-2019 12:48 PM
    Possible Communication Issue between BVMS 8.0 Central Server and Video Recording Manager (VRM) 3.7x 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.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.
    View full article
    ‎10-21-2019 02:05 PM
    Related Products: BVMS, Operator Client This article describes the initial information needed to start troubleshooting Operator Client Crash. Needed information and logs from the customer: 1. Note down the events that lead to crash 2. Classify the crash reproducible crashes that trigger Windows Error Reporting crashes/hangs/freezes that are hard to reproduce, or take long before repeating 3. Provide the following logs: Dump file from the crash – refer to the following article ( https://community.boschsecurity.com/t5/Security-Video/How-To-create-BVMS-memory-dump/ta-p/7326 ) ConfigCollection from the machine where the crashing Operator Client is running.
    View full article
    100% helpful (1/1)
    ‎10-16-2019 11:43 AM
    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 potential non-optimal configuration due, PD commissioned as Emergency Spare error. There is an article as well from hardware partner:  http://www.supermicro.com.tw/support/faqs/faq.cfm?faq=19518   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: https://downloadstore.boschsecurity.com/FILES/KnowledgeBase/MegaRAID_Ctrl_FW_update_DIVAR_IP_BOSCH.zip 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. 
    View full article
    ‎10-11-2019 12:02 PM
    This article provides you with information related to the Windows Firewall, how to access, configure and adjust it.   Firewall A firewall is a program installed on your machine or a piece of hardware in your network, that uses a rule-set to block or allow access to a computer, server or network. It seperatres dedicated network segments, likly your LAN from the Internet. Firewalls can permit traffic to be routed through a specific port to a program or destination, while blocking all other traffic.   Windows Firewall The Windows Firewall interface can be accessed multiple ways. The  way we will look during this TB is via the Windows search function. Click the Windows icon and type in “firewall“.  Then, click on the “Windows  Firewall with Advanced Security” icon.   The GUI provides you a general overview, about the basic function of the software. Displaying the current status of the firewall also which profiles are currently set up. By default the firewall should be enabled. We strongly recommend that the Windows Firewall is enabled on all your Bosch devices featuring a Windows Operating System.   Firewall profiles There are 3 different profiles within your Windows Firewall, which are simply groups of different firewall rule-sets, depending where your machine is currently connected. Public Profile: This profile is used when the computer is connected directly to a public network like a restaurant, library or airport. This profile should be the most restrictive because security is usually not well controlled in public places. Private Profile: This profile is used if your are only connected to  a private network, not directly to the Internet. In these cases, your device is located behind a router or hardware firewall. Which allows to set this profil less restrictive. Domain Profile: This profile is used when the machine is connected to a domain controller, which in turn is controlling a windows domain. This profile should be the least restrictive of the other  profiles because security is usually very well controlled within a domain.   Standdard rule-set by default the Windows Firewall behavior is the following:  Windows Firewall never blocks outgoing traffic. Any requests sent out from the server will not be hindered in any way. Windows Firewall blocks all incoming traffic, except for traffic that is in responses to a request. This means that if you make a request to Google, Google’s inbound reply to your outbound request will not be blocked. Windows Firewall blocks all other traffic. This means that any traffic that is not explicitly allowed is blocked in the firewall. In the Windows Firewall we can filter connection in two different kinds: port exceptions (rule assigned to a dedicated port number)  and program exception (rule assigned to a dedicated program)   In general we need to distinguish between the inbound (frome somewhere to your machine) and outbound (from your machine to somewhere) rule-set.   Open a port in the firewall (inbound rule) In the Windows Firewall with Advanced Security window, right-click "Inbound Rules", and then click "New Rule..." in the action pane. "Rule Type" dialog box, select "Port" depending on your need and then click "Next". In the "Protocol and Ports" dialog box, select "TCP". Then select "Specific local Ports", and then type the port number and then click "Next". In the "Action" dialog box, select "Allow the connection" and then click "Next". In the "Profile" dialog box, select any profiles that apply and then click "Next". (We have allowed all three for demonstration purposes, your selection may vary.) In the "Name" dialog box, type a name and description for this rule, and then click "Finish". At this point, you will now see a new rule in the main firewall rules in the center section, as well as a new listing in the right window panel.   Open a program in the firewall (inbound rule) Click on the "Inbound Rules" option on the top left of the firewall interface. Then, click on the "New rule…" Under "Rule Type" dialog box, select the option "Program" and then click "Next". Select the option "This Program path" browse to the path/location of the program  and click "Next". Next, we select the option “Allow the connection” and then click “Next”. Select the "Profile" the rule will be applied to and click "Next". (We have allowed all three for demonstration purposes, your selection may vary.) Select a "Name" and "Description" for this rule and then Click “Finish”. At this point, you will be dropped back to the main firewall screen. You will now see a new rule in the main firewall rules in the center section, as well as a new listing in the right window pane   Edit a port / program in the firewall Right-click on the rule which will open a context menu. Then click  "Properties" and adjust the rule according your needs .   Close a port / program in the firewall Right-click on the rule which will open a context menu. Then click  " Delete".       Adjust program rule after BVMS upgrade In case you upgraded your current BVMS up to BVMS10, refering to the article TSG-Upgrading-VRM-from-32bit-to-64bit you need to adjust the inbound + outbound rule "Bosch VRM Server" and  "USB Transcoder". Therefore right-click on the rule which will open a context menu. Then click "Properties" and adjust the programs path to: Bosch VRM Server: "C:\Program Files\Bosch\Video Recording Manager\VRM Server\bin\rms.exe" USB Transcoder: "C:\Program Files (x86)\Bosch\Video Recording Manager\VRM Server\bin\usbsvc.exe" Keep in mind, that you need to perform this action on all four rules (inbound and outbound) Alternatively download the attachment set_fw_rules.zip (1 KB) locally to your device, extract the archive and run the PowerShell script "set_fw_rule_trancoder.ps1" as administrator. The script will adjust all necessary rules.
    View full article
    100% helpful (1/1)
    ‎10-09-2019 08:30 AM
    Which Bosch encoders and decoders are compatible with BVMS? Up until some years ago, new released cameras, encoders, domes and decoders that are introduced into market after a BVMS release could not be connected to an existing BVMS version because these cameras where not known to the BVMS. In the BVMS 4.5.1, a new concept was introduced. This concept treats Bosch video encoders and decoders as generic devices, and automatically recognizes specific device functionality (for example the number of streams, relays and inputs). Based on this information the, at that time, unknown device is added to the system and can be used by the operator. The attached document provides a detailed description of this functionality.
    View full article
    100% helpful (3/3)
    ‎10-04-2019 02:20 PM
    Potential for Data Inconsistency Issues on E-Series Storage Systems Status 1/2019: With the new controller firmware 11.50.2 and newer versions 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 11.50R1. This is also announced by NetApp on their support websites (see https://mysupport.netapp.com/). Please follow our BOSCH Knowledge Base and monitor for updates here. 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. Products affected: 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.   Issue Description 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. Workaround 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. status 06/2019: controller firmware version minimum 11.50R1 status 10/2019: controller firmware version to be used 11.50.2 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.
    View full article
    Top Contributors
    Icon--AD-black-48x48Icon--address-consumer-data-black-48x48Icon--appointment-black-48x48Icon--back-left-black-48x48Icon--calendar-black-48x48Icon--center-alignedIcon--Checkbox-checkIcon--clock-black-48x48Icon--close-black-48x48Icon--compare-black-48x48Icon--confirmation-black-48x48Icon--dealer-details-black-48x48Icon--delete-black-48x48Icon--delivery-black-48x48Icon--down-black-48x48Icon--download-black-48x48Ic-OverlayAlertIcon--externallink-black-48x48Icon-Filledforward-right_adjustedIcon--grid-view-black-48x48IC_gd_Check-Circle170821_Icons_Community170823_Bosch_Icons170823_Bosch_Icons170821_Icons_CommunityIC-logout170821_Icons_Community170825_Bosch_Icons170821_Icons_CommunityIC-shopping-cart2170821_Icons_CommunityIC-upIC_UserIcon--imageIcon--info-i-black-48x48Icon--left-alignedIcon--Less-minimize-black-48x48Icon-FilledIcon--List-Check-grennIcon--List-Check-blackIcon--List-Cross-blackIcon--list-view-mobile-black-48x48Icon--list-view-black-48x48Icon--More-Maximize-black-48x48Icon--my-product-black-48x48Icon--newsletter-black-48x48Icon--payment-black-48x48Icon--print-black-48x48Icon--promotion-black-48x48Icon--registration-black-48x48Icon--Reset-black-48x48Icon--right-alignedshare-circle1Icon--share-black-48x48Icon--shopping-bag-black-48x48Icon-shopping-cartIcon--start-play-black-48x48Icon--store-locator-black-48x48Ic-OverlayAlertIcon--summary-black-48x48tumblrIcon-FilledvineIc-OverlayAlertwhishlist