About W_Ratschmeier

In this article we cover the following basic questions: How to Factory Default a NetApp E-Series unit by using BOSCH tools and NetApp WEB GUI? How to download the NetApp Support Bundle of a reachable online NetApp Storage Array   Step-by-step guide   1 How to Factory Default a NetApp E-Series that you bought via BOSCH sales channel? Using the BOSCH Configuration Manager starting with version 6.00, the NetApp models E2600, E2700 and E2800 can be managed. Especially we recommend to use the BOSCH Configuration Manager version above version 06.01 when using a NetApp E2800 to have all models (also former models E2700 and E2600) supported. Also in the BOSCH Configuration Manager, the Basic configuration for the initial setup is helpful as well as the Factory Default option and Clear option is available. Of course the NetApp E2800 offers also a WebGUI by using the IP of the management port of a controller. The following screenshot made from the BOSCH Configuration Manager shows the options available in the tab "Basic Configuration" when a NetApp E-Series (DSA E-Series) is already added to a VRM system in the Configuration Manager. The Button "Defaults" is used to trigger the "Reset Storage Array" mechanism of NetApp. At a E2800 all configuration is eliminated but the Management Port IP still remains to ensure that the WEB GUI of NetApp and the communication of the BOSCH Configuration Manager can still work.   2 How to download the NetApp Support Bundle of a reachable online NetApp Storage Array In the Tab "My Devices" of the Configuration Manager 6.01 and newer versions you can also now download the Support Bundle (collection of logfiles) from a NetApp E2800 storage system. Select the NetApp E2800 in your device tree that is added to a VRM system and right-click on it. There you find "File Download" and "Maintenance Log..." - Choose that to download the NetApp Support Bundle. Another way to download the support bundle file for DSA E-Series E2800 can be found here. Latest version of Configuration Manager is available in Download Area. ... View more

Question   Can I receive / retrieve more than 4 live video streams with BOSCH Video Security Client on my Windows PC?   Answer   All VRM versions newer than version 3.0 running on a DIVAR IP (e.g. DIVAR IP 6000 R2) do offer automated live video forwarding via the VRM running on the DIVAR IP. For example the VRM version 3.71.0029 or VRM 03.81.0032 can offer 4 transcoded live videos and on top normal non-transcoded video depending on available performance and bandwidth. As the Video Security Client do not offer connections to devices of DIVAR IP Family through HTTP(S) proxies, the VSC cannot correctly determine if a DIVAR IP is local or connected via public internet. The Release letter of the Video Security Client (VSC) informs in section "4. Restrictions, known issues". Release Letter Video Security Client v3.5.0 DIVAR IP Family devices coming with VRM 3.6x and later are reachable via non transcoded tunneled way as well in case the Video Security Client can detect the DIVAR IP as local available device. There is a mechanism in the Video Security Client (VSC) to detect if the DIVAR IP is in the same local network as the Windows workstation running the VSC. As soon the VSC cannot reach the DIVAR IP locally but via a public IP the VSC tries to use a transcoded live video. A DIVAR IP offers up to 4 transcoded video connection in total. Note: There is one sentence in the release letter that is only valid for the VRM version 3.0 but not for any later/(newer VRM version: "•   Connections to devices of the DIVAR IP Family with VRM Version 3.0 support only transcoded connections" Please be aware that of course newer VRM versions offer non-transcoded live video via the VRM live video forwarding in the local network. ... View more

MTU stands for "Maximum Transmission Unit." MTU is a networking term that defines the largest packet size that can be sent over a network connection. The MTU is typically limited by the type of connection, but may sometimes be adjusted IT network settings. The typical value of the Network MTU is 1514 Byte. If a system sends packets over an Ethernet network that are larger than this size, the data will be fragmented into smaller packets. When referring to Ethernet MTU this includes 4 Byte checksum. The  1514 Byte is the interface MTU without the Ethernet Checksum. In cae there are limitations by the type of connection, the packets will then need to be reassembled on the receiving side (e.g. Bosch video management software or Bosch hardware decoder). However, it can be beneficial to optimize the packet size on the sender side (e.g. IP camera) to the exisitng network infrastructure. As MTU maximum packet size is layer 1 related, the IP MTU that you can be adjusted at the BOSCH device configuration (Configuration Webpages or with the help fo BOSCH configuraiton software like "Configuraiton Manager"). The BOSCH GUI refers to this as “Network MTU”. BOSCH products can manage fragmented data. MSS stands for "Maximum Segment Size" The MSS value is calculated from the MTU. MSS = MTU – (layer 3 TCP header [20 Byte] + Layer 2 IP header [20 Byte]+ Layer Ethernet 1 [6+6+2 = 14 Byte]) For example looking at CPP 6 Platform – like FLEXIDOME IP panoramic 7000 MP in Firmware version 6.50.0128 you can adjust and find the following values: Network MSS (in Byte) - default value = 1460 iSCSI MSS (in Byte) – default = 1460 Network MTU (in Byte) – default = 1514   MTU and MSS can be adjusted at all released firmware versions 4.x and later. CPP-ENC CPP3 CPP4 CPP5 CPP6 CPP7 CPP7.3 yes x x x x x x x No                   Step-by-step guide Here some screenshots as example based on Firmware 06.50.0128   ... View more

CPP: Combined firmware package – applicable to all platforms   The Release Letter for CPP FW 7.89.1221 provides information about the dependencies between firmware versions for a better understanding of the upgrade process of devices with older firmware.   To obtain a combined firmware file, you have to get in contact with the Central Technical Support.   Step-by-step guide   CCP4 and CPP6 devices: Due to an internal file system being introduced to CPP4 and CPP6 since firmware 6.10 and architectural changes thereof, a direct upgrade from firmware below version 6.10 to latest firmware is only possible via intermediate firmware 6.1x. CPP4 cameras upgrade from FW < 6.10 to intermediate FW 6.11 upgrade from FW < 6.50 to intermediate FW 6.50 upgrade EXTEGRA from FW 6.10 or newer to latest FW 6.32 upgrade from FW 6.50 (<6.51) to latest FW 7.10   CPP6 cameras  upgrade from FW < 6.50 to intermediate FW 6.50 upgrade from FW 6.50 (<6.51) to latest FW 7.89    CPP5 devices: This combined firmware cannot be applied to CPP5 products with firmware version older than 5.91. It is required to upgrade to intermediate firmware 5.91 first This means that intermediate firmware version 5.91 for CPP5 needs to be requested from Bosch Central Technical Support team. Only after receiving and uploading firmware 5.91, you can upload the latest version CPP5 specific firmware available on the Download Store (currently 6.31.0010).   Note: Upgrading from versions lower than 5.5x To upgrade to a newer firmware version using this combined firmware package, firmware versions before 5.5x require an intermediate update cycle using the respective platform firmware version mentioned above.   Restrictions: This firmware and its included platform firmware builds are not applicable to MPEG-4 products. The final firmware version for VIP-X1600-XFM4 modules is FW 5.54. No newer firmware will be provided for these modules. Configuration Manager cannot upload this Combined Firmware file to VIP-X1600-XFM4 modules. Use the module’s web page instead for uploading; or use the separate firmware file. The final firmware version for CPP3 devices is FW 5.75. No newer firmware will be provided for these products. The Combined Firmware file does not load onto VG4 AUTODOME or AUTODOME Easy II via the browser when running a firmware version before 5.52.0017. The specific platform file should be used instead. (Note: In case any link might not work to the current DownloadStore, see attached a copy PDF of the Release Letter.)   How to get and request a BOSCH Legacy Firmware:   The procedure to request and get an legacy firmware that is no longer online in the web is as follows: Customers are kindly requested to reach out to the Bosch Central Technical Support team Bosch Central Technical Support team will ask for the exact BOSCH Commercial Type Number (CTN). The Bosch Central Technical Support team can check the Global End of service date. The project background (How many of these devices/cameras) need to be collected.  The Bosch Central Technical Support team can explain and check if there is the chance to update the project and included management software in order to be able to use the latest BOSCH device firmware as the goal is to have a non-vulnerable product in productive environments. In case there is no newer firmware available (hardware was discontinued), a commercial hardware upsell can be recommended. In general, all firmware that is not available on the product catalog, and for all firmware files that are ranked to have vulnerabilities, this need to be documented in a Technical Support case. In case legacy firmware is anyhow needed and requested by our customers, the Bosch Central Technical Support team will start an approval flow. One form/ document that must be signed by the installer/ customer. See an example PDF (empty) "Legacy Platform (FW SW) Release Form (Version 1.08).pdf" attached to this article. Such a form will be prepared by the Bosch Central Technical Support team and provided to our customer/ installer in order to confirm that legacy firmware is then used on the risk of the installer and customer (See text and legal note in the PDF).  See also: Bosch Video support - Firmware and Software requests ___________________________________________________________________________ The above mentioned combined firmware 6.50 supports: CPP7.3 HD and UHD cameras update from FW 6.40 or newer to latest FW 6.50 CPP7 UHD cameras update from FW 6.30 or newer to latest FW 6.50 CPP6 UHD cameras update from FW 6.10 or newer to latest FW 6.50 CPP5 encoders update from FW 5.91 or newer to latest FW 6.30 CPP4 HD cameras update from FW < 6.10 to intermediate FW 6.11 update from FW 6.10 or newer to latest FW 6.50 CPP3 cameras and encoders update from FW 4.54.0026 or newer to latest FW 5.74 CPP-ENC VIP-X1600-XFM4 encoders: update from FW 4.2x or newer to latest FW 5.53 VJT XF and VJD-3000 update to latest FW 5.97 The combined firmware package includes the following build versions: CPP7.3 FW 6.50.0128 CPP7 H.264 6.50.0128 CPP6 H.264 6.50.0128 CPP5 H.264 6.30.0059 CPP4 H.264 6.50.0128 CPP4 H.264 6.11.0021 CPP3 H.264 5.74.0010 CPP-ENC H.264 5.97.0005 for VJT XF family, VJD-3000 and VJC-7000 CPP-ENC H.264 5.53.0004 for VIP X1600 XFM4 For detailed description please refer to the separate release letters. Customers can upload such combined firmware packages by using multi-select in the Configuration tool "BOSCH Configuration Manager" (download the latest version available on the BOSCH DownloadStore or Product catalog > Video Software > Video Management Systems > Configuration Manager) When using the multi-select option in Configuration Manager, please make sure this combined firmware package for all platforms can be uploaded to all the devices selected and there are no additional requirements or intermediate steps needed for any of the devices in question. ⚠️ Note that new changes in this procedure might be introduced. When changes are done, then this article will be updated. Therefore check this article from time to time. ___________________________________________________________________________   Upgrade to the latest FW available:   To upgrade to a newer firmware version using this combined firmware package, products may require to have this firmware file uploaded multiple times until the intended firmware version is installed, depending on the CPP version of the camera you have.  As per Release Letter of CPP FW v.7.89.1221, this FW version must be applied as described below: • CPP7.3 HD and UHD cameras o upgrade from FW < 6.50 to intermediate FW 6.50 o upgrade from FW 6.50 (<6.51) to latest FW 7.89   • CPP7 HD cameras o upgrade from FW < 6.50 to intermediate FW 6.50 o upgrade from FW 6.50 (<6.51) to latest FW 7.89 • CPP6 UHD cameras o upgrade from FW < 6.50 to intermediate FW 6.50 o upgrade from FW 6.50 (<6.51) to latest FW 7.89 • CPP5 encoders o upgrade from FW 5.91 or newer to latest FW 6.31 • CPP4 HD cameras o upgrade from FW < 6.10 to intermediate FW 6.11 o upgrade from FW < 6.50 to intermediate FW 6.50 o upgrade from FW 6.50 (<6.51) to latest FW 7.10 • CPP3 cameras and encoders o upgrade from FW 4.54.0026 or newer to latest FW 5.75 • CPP-ENC encoders and decoders o VIP-X1600-XFM4 encoders: upgrade from FW 4.2x or newer to latest FW 5.54 o VJT XF, VJD-3000 and VJC-7000 upgrade to latest FW 5.97 The combined firmware package includes the following build versions: • CPP7.3 FW 7.89.0030 • CPP7.3 FW 6.50.0133 • CPP7 H.264 7.89.0030 • CPP7 H.264 6.50.0133 • CPP6 H.264 7.89.0030 • CPP6 H.264 6.50.0133 • CPP5 H.264 6.31.0010 • CPP4 H.264 7.10.0096 • CPP4 H.264 6.50.0133 • CPP4 H.264 6.11.0026 • CPP3 H.264 5.75.0011 • CPP-ENC H.264 5.97.0013 for VJT XF family, VJD-3000 and VJC-7000 • CPP-ENC H.264 5.54.0012 for VIP X1600 XFM4   Nice to know: How to upgrade the Autodome IP 5000 IR (CPP4) camera firmware from 6.32 to the latest available? ... View more

Possible causes and solution(s)   Causes This article informs about improvements in firmware handling and new security mechanisms that help our customers to increase security related to firmware updates and IP camera protection. BOSCH introduces authenticated firmware signature Firmware security with IP cameras and IP video encoders is enhanced by introducing signed firmware. The signature of the firmware file has been strengthened by using a two-factor authentication process for signing any firmware file within BOSCH that is published as "RELEASED FIRMWARE". This new process has been prepared with firmware 6.50 already and comes into effect with firmware versions 6.51 and newer. Non-released firmware cannot be installed on products in the field. The new signature protects from non-released versions being installed in productive systems. As a result any integrator-specific firmware e.g. for Field Acceptance Test or project assistance from BOSCH R&D need to have a special license installed prior to the firmware update (loading a project-specific firmware) to allow a "Development Build" of a firmware. The BOSCH Integration Partner Program Program (IPP) Team and the BOSCH support teams are happy to assist our customers / integration partners where needed. For all projects where such a "Allow Development Build" license is required, a technical support case must be created with BOSCH technical support and those cases will be tracked and documented. Solution Introducing a "minimum required version" For specific projects with implementation into 3rd party management software, a firmware downgrade to an older firmware version than 6.51 can be required. All customers and partners in the need to downgrade are requested to contact their local BOSCH Support. Partners with special Support regulation should contact their known IPP support contact in the region in order to get in touch with the Global IPP support.  Right now a simple downgrade to a less secure firmware, which might also lack other improvements, is no longer possible in each case. The dependencies and the minimum required version is documented and listed in the Release Letter of any firmware version 6.51 or newer. NOTE: All Firmware requests to downgrade to less secure firmware (status 2018-10-16 e.g. 6.44.x). Any downgrade to a firmware version which is not ranked as secure enough must be requested via the BOSCH technical support in your region. See details published in Security Advisories of BOSCH: https://www.boschsecurity.com/xc/en/support/product-security/security-advisories.html Such a waiver form must be handed out by BOSCH support and signed by Integrator, Installer and/or BOSCH Partner. Note: Please also be aware that depending on Hardware there is a minimum Firmware version mentioned at the section "Device Overview" at the WEB GUI of all BOSCH IP cameras. Especially in case of the need to "downgrade" to previous/older Firmware, this Firmware version information must be checked before and taken into consideration. In case a downgrade to a firmware version above the displayed "Minimum required Firmware is planned or needed, it is recommend to check the downgrade process with the local Technical Support of BOSCH. A downgrade is not recommended in general, as fixes and security improvements added to new firmware is missing in older firmware. (example screenshot here below) For other firmware releases, newer than 6.51 (status 03/2019) additional dependencies might be introduced. Please make use of the search feature to find additional news on future firmware releases in our Knowledge Base and read through the Release Letter of such newer Firmware. Firmware file encryption Update to 6.51 Firmware: In order to upload version 6.51 to a device running a firmware version below 6.50, you need to upgrade first to version 6.50, since older firmware versions do not support firmware file decryption. ... View more