Possible causes and solution(s)
Symptoms
When upgrading to BVMS 13.0 or 13.1, the Windows Server SNMP Service is automatically stopped and removed.
This also occurs whenever the BVMS 13.x installer is started again and changes are made to installed components.
Causes
This behavior is intentional and was introduced together with new SNMP library to support SNMPv3 in the next release. The Windows SNMP Service does not support SNMPv3.
Since both, the Windows Server SNMP Service and the BVMS SNMP Server use the same default SNMP Trap port (UDP 162), running both services simultaneously would create a port conflict.
-
Note: By default, BVMS SNMP Server is running on port 162 to maintain the system working as before and disable the Windows SNMP Service to avoid conflicts.
Solution
If the Windows SNMP Service is required for other purposes, such as third-party SNMP-based server supervision applications, additional reconfiguration is necessary.
In this case, to allow both services to operate simultaneously, the BVMS SNMP Server must be configured to use a different SNMP Trap port, other than 162 (for example, UDP 163).
How to change the BVMS SNMP Trap port:
-
Open the following configuration file:
-
C:\Program Files\Bosch\VMS\bin\BvmsSnmpServer.exe.config
-
If you cannot open the file, run Notepad as an administrator, then go to File → Open and search by BvmsSnmpServer.exe.config
-
-
Locate the following parameter:
-
<add key="SNMPTrapPort" value="" />
-
Change the value to another available port, for example, 163:
-
<add key="SNMPTrapPort" value="163" />
-
After changing the value, restart Windows service 'BVMS SNMP Server'
Important notes:
-
After changing the BVMS SNMP Trap port, all devices communicating with the BVMS SNMP Server must also be updated to use the new port.
-
When changing the SNMP Trap port, it is also necessary to reconfigure the corresponding firewall rule for SNMP TRAP IN. By default, the firewall rule created by BVMS Setup is allowed only for port 162.