Issue
EBO 3.2.x SNMP Engine ID seen in EBO 3.2.x is not the one used by the EBO 3.2.x system.
Product Line
EcoStruxure Building Operation
Environment
- Building Operation Workstation (from v3.2)
- Building Operation Automation Server (AS-P and AS-B) (from v3.2)
- SNMP
Cause
EBO 3.2.1 introduced a new SE3Linux operating system for the AS-P and AS-B servers.
The engine ID: seen in Device Administrator or Workstation is the engine ID: contained in Linux, this is not the one used by EBO 3.2.x
Resolution
The SE3Linux engine ID: “0x80001f8803005006042bd7” viewed using the Device administrator:
The SE3Linux engine ID: “0x80001f8803005006042bd7” viewed using the Workstation
The engine ID used by EBO for this example would be:
0x80002a1d03005006042bd7
The difference is always 2a1d compared to 1f88 and the rest of the bytes are the same.
For further information see the attached document SNMP SBO 3.2.x Engine ID Explained.
