About Central_Support

Question   What should you know about SNMP and Bosch cameras SNMP support?   Answer   This article explains briefly the basics of SNMP. Declares the basic terms of the protocol. It also explains what part of the protocol is supported by Bosch cameras. Basics of SNMP and terms. Simple Network Management Protocol (SNMP) is a common protocol to monitor the health status of a system. Such a monitoring system typically has a central management server that collect all the data from the system’s compatible components and devices. SNMP provides two methods to gain the system health status: The network management server can poll the health status of a device via SNMP requests. Devices can actively notify the network management server about their system health status in case of error or alarm conditions through sending SNMP traps to the SNMP server. Such traps must be configured inside the device. Basic terms: MIB Management Information Base, is an ASCII text file that describes SNMP network elements. It is the dictionary of the SNMP language — every object referred to in an SNMP message must be listed in the MIB. Each element in the MIB is given an object identifier, or OID.   An OID is a number that uniquely identifies an element in the SNMP universe. Each OID is associated with a human-readable text label. When your SNMP device sends a Trap or a GetResponse, it transmits a series of OIDs, paired with their current values. Example (from bvip_snmp.mib) – OID -- 1.3.6.1.4.1.3967.1.5.1.1       mac-address SNMP manager collects and organizes SNMP information from managed devices (agents). It uses the MIB as a codebook for translating the OID numbers into a human-readable display.   PDU (Protocol Data Units): In the second section of this article, there are examples of PDU types Trap and GetRequest. For more information on the existing PDUs (that are different in different SNMP versions), please refer to SNMP documentation.   SNMP also allows configuration of some variables inside devices and components. The information, which messages a device supports and which traps it can send, is derived from the Management Information Base, the so-called MIB file, a file that is delivered with a product for easy integration into a network monitoring system. There are three different version of the SNMP protocol: –SNMP version 1 SNMP version 1 (SNMPv1) is the initial implementation of the SNMP protocol. It is widely used and has become the de facto standard protocol for network management and monitoring. But SNMPv1 has become under threat due to its lack of security features. It only uses ‘community strings’ as a kind of passwords, which are transmitted in clear text.Thus, SNMPv1 shall only be used when it can be assured that the network is physically protected against unauthorized access. –SNMP version 2 SNMP version 2 (SNMPv2) included improvements in security and confidentiality, amongst others, and introduced a bulk request to retrieve large amounts of data in a single request. However, its security approach was considered way too complex,hindering its acceptance. Thus, it was soon pushed out by version SNMPv2c, which equals SNMPv2 but without its controversial security model, reverting to the community-based method from SNMPv1instead, similarly lacking security. –SNMP version 3 SNMP version 3 (SNMPv3) mainly adds security and remote configuration enhancements. These include improvements on confidentiality by encryption of packets, message integrity and authentication. It also addresses large-scale deployment of SNMP.   -MIB and MIB II A management information base (MIB) is a formal description of a set of network objects that can be managed using the Simple Network Management Protocol (SNMP). MIB-I refers to the initial MIB definition and MIB-II refers to the current definition. -Standard MIB Standard MIB objects are designed for a wide variety of technologies and network devices. These MIB objects cover a large range of performance monitoring parameters that are valid for any network device in general. -Private MIB Private MIB extentions are created in order to cover vendor-specific performance monitoring parameters.   Bosch cameras SNMP and MIB To check what SNMP version does a particular camera support, check the data sheet of the device. (Find it under your device in the product catalogue - https://www.boschsecurity.com/xc/en/product-catalog/) since FW 6.40 onwards Bosch devices support: SNMP v1 legacy with MIB II (The term legacy is used in some documents to note that this is SNMP v1 and there is Bosch private MIB II extention ) and SNMP v3 basic integration. This means that there is no Bosch private MIB file and  only the standard system MIB file can be used. There is no trap support for SNMP v3 implementation. up to FW 6.40 Bosch devices support SNMP v1 with Bosch MIB II extention. Recent platforms CPP13 and CPP14 provide a full private MIB integration for both SNMP v1 and v3, including trap support. Structure of the MIB (bvip_snmp.mib) The file starts with description in form of comments (comment starts with --) List of the traps    All Commands – Object Types, data you can read and sometimes write. To read and write the SNMP manager sends to the agent commands (ex. GetRequest and SetRequest) encapsulated in PDUs. The body of the MIB file is a tree of all MIB Object - all characteristics of the device that are controlable via SNMP    Fig. Object Type structure   Access - the most important entry in an object-type description. This controls whether you can read and write the data described in the object-type. There are three access settings: read-only - request the data in with GetRequest, GetNext, Walk, etc read-write- retrieve the data in a GetRequest and write new data for the object-type in a SetRequest. not-accessible - you can’t request the data or write new data   Details how to configure Bosch camera to send SNMP traps: How to activate the SNMP and configure sending SNMP traps from Bosch cameras? ... View more

Question   Where you can find the connection state events for Camera/ Encoder?   Answer   This guide is meant to explain how you can find the connection state events of a camera in Operator Client - Bosch Video Management System. Open Operator Client > Tools > Find in logbook Filter only for the specific cameras you are interested in, and only for the following events and click on "Search" button: - Connection state (Encoder) - Connection state (Camera) - Video loss (Camera)  Logbook Results should be displayed: ... View more

Question   Which is the mandatory information requested by Bosch Central Technical Support for a faulty hard drive (HDD) on a DIP AIO or DIP 6000/ 7000 R2?   Answer   Don't skip the Warning Signs that suggest an HDD Failure. If you suspect that your hard drive has failed and you are contacting the Central Technical Support team, please first consider the mandatory information listed below, which must be provided to them:   1. Has your unit been registered? If not,  please access the online registration form, fill in all the mandatory fields and press Submit.  Note: In order to enable the IT supplier of the product to fulfill the service and support agreements, it is necessary to register each system. Without proper registration, efficient support for IT products bought from Bosch cannot be guaranteed and the available Service Level will be best effort only. Useful information about the registration process: Where and why should 3rd party devices be registered?   2. Picture of the HDD label   3. For an HDD Failure, the SERIAL NUMBER of the unit is mandatory. Based on the SN, the Central Technical Support team will also check if your unit is still under warranty. Please check the Supermicro Limited Warranty conditions.   4. Picture with the HDD LED on the front of the unit   5. Logs MegaRAID logs: How to collect MegaRAID logs for DIVAR IP 6000/7000 R2? IPMI information/logs: please refer to the following article: How to remotely view and collect the system's event log through IPMI? Super Doctor logs and print screens: please refer to the following article: How to Collect Support Data of DIP 6000 R2/ 7000 R2 with SuperDoctor 5 (SD5)   6. Print screen from the MegaRAID tabs where the status of the HDD is visible: 1 picture with Dashboard tab 1 picture with Physical tab 1 picture with Logical tab Example:   7. Delivery details Contact name (person) delivery : Contact number (tel.) delivery : Contact e-mail delivery : Delivery location company name (co location) : Street name : House number : Zip code : City : Country : Specific directions for delivery (Reception, Warehouse… etc. ) : Notes or other specifications :   Note: Only DIP units using Bosch bought drives are supported by SMC (Supermicro) and Bosch. Therefore, if a unit is equipped with hard drives bought anywhere else and the fault occurs because of the hard drives, the case is not supported.   ... View more

A transfer of the license from the Bosch Software License Manager System (SLMS) to the Bosch Remote Portal is required for every BVMS system to be upgraded from 10.1 to 11.0 Starting with BVMS 11.0 the license activation is done via Bosch Remote Portal. To upgrade an existing system, the BVMS licenses need to be migrated from the old licensing system, Bosch Software License Manager System (SLMS), to the new licensing system available in Bosch Remote Portal. This article describes the steps that need to be followed when upgrading a system to BVMS 11.0. Prerequisites for upgrading a system to BVMS 11.0: Existing license activated in SLMS Valid Software Assurance (SMA) Valid account on Bosch Remote Portal   ❗❗❗ IMPORTANT In BVMS 10.x the computer signature is the link to the license in the SLMS When upgrading to 11.x the computer signature becomes obsolete and the new Remote Portal tool no longer takes it into consideration The software Order ID is transferred in the background from SLMS to the Remote Portal This allows the activation of BVMS 11.x in the Remote Portal using the new identifiers for the Management Server Hardware called System Fingerprint, contained in the System Info file.   Step-by-step guide   1. Check the license status in Bosch Software License Manager System   Access Bosch Security Systems Software License Manager (SLMS) website and login using your credentials. Click My Activations and select BVMS from the Select a Product Family drop down list The list with all the BVMS activations for the account is going to appear If a system is entitled to upgrade to the next BVMS version, the Upgrade button will be available   2. Upgrade the license in Bosch Software License Manager System (SLMS)   Click Upgrade and OK The upgrade process is going to take around 1 minute Once the upgrade is finished, the system displays the successfully upgraded message By clicking the + next to the System Identifier, the software ID is going to be displayed To activate the BVMS 11.0 license, copy the software ID and/or send an email containing the information. The email sent looks like below: Using this information, the activation process in Bosch Remote Portal can be started   3. Create an account on Bosch Remote Portal or login using your existing account   if you already have an account, access Bosch Remote Portal and login using your credentials    4. Upgrade the BVMS software on your server and save the system info file   Run the BVMS 11.0 installation package before performing the next steps Note: while performing the license upgrade, the Operator Client will not be able to login anymore until the licensing process is finished   5. Go to Bosch Remote Portal and generate the activation file   6. License the system by uploading the generated activation file   ⚠️ This step is described in the article below. Follow the license activation process steps: How to activate a new BVMS 11.0 license?    Useful: For more details, please refer also to the BVMS 11.0 - Upgrade and Migration document or to the following YouTube video:   How to upgrade a BVMS license to BVMS 11.0 ... View more

In terms of license activation process and compared to other versions of BVMS (<v11.0), the Bosch Remote Portal replaces the Bosch Software License Manager System (SLMS), starting with BVMS v11.0. A new user registration is required in Bosch Remote Portal and the mandatory information for license activation is the System Info file (generated in the Configuration Client) and the Software order ID (received from the Bosch order desk by e-mail → ordering remains unchanged: still utilizes the Bosch Order Desk) The remote portal will then provide a "Activation file" which includes all activation details. It needs to be uploaded to the newly installed BVMS system. The activation process defines the start date of the software maintenance agreement (SMA - software assurance) period. The end date is shown on the License manager of the BVMS Configuration Client after activation NEW: Software version-less ordering process: Ordering a BVMS Base or Expansion licenses is not software dependent anymore starting with BVMS 11.0 upwards. During license activation only "non End of Life" (EOL) versions are assigned to the license.   Follow this article and find out the steps that need to be performed when activating a new BVMS 11.0 license. 🚩 Keep in mind that the SMA license must be activated both on the unit and in the Remote Portal.   Step-by-step guide   1. Install the BVMS 11.0 software on your server and save the system info file   Once the BVMS 11.0 is installed, access BVMS Configuration Client After you successfully logged in, the system will display the message that it is currently running in an unregistered mode > Click OK The License Manager dialog window will appear > Click Add near the Licenses option In the next window, under the STEP 1 click Save in order to save the system information file and select the location where the file should be saved The status of the saving process will be displayed > click Close   2. Login to Bosch Remote Portal and generate the activation file   Access Bosch Remote Portal, Login using your credentials and select Software Licensing Click Claim Software Order and paste the Software Order ID in the window displayed Note: The Software Order ID can be found in the email from the Order Desk department. Copy and paste it in the corresponding section and click Claim All the licenses available on the Software Order ID are going to be displayed Click the Activate License button > upload the system info file that you saved earlier and fill in the required information > click Next You should complete an Installation Site name that corresponds to the actual site where the system is installed for easy identification.  Select the base product and the licenses that you wish to claim for the current system and click Next The expansion channels contained in the software order can be assigned to different systems if necessary > click Activate After you successfully added your license, you will see the following license dashboard in the Remote Portal: Download your activation file and make it accessible to the BVMS computer   3. License the system by uploading the generated activation file   In BVMS Configuration Client access Tools > License Manager  Then, in the License Manager dialog box select Add near the Licenses option and under Step 5 click Open Navigate to the location where the Activation file was saved and upload it After successfully uploading your activation file, the license status changes to Activated and the license information is displayed The details about the licenses installed on the system can be found under the License Inspector menu Useful: For more details, please refer also to the following YouTube video:  How to activate the license for a new BVMS 11.0 system BVMS 11.1.1 - Upgrade and Migration ... View more