Container Servers create same Instance ID for BACnet interface

[David_Purser]

Issue

When the BACnet Interface is created in Container Servers, the automatically generated Device Object ID aka Instance ID can be the same as another Container Server on the same container host.

Product Line

EcoStruxure Building Operation

Environment

• Building Operation Edge Server
• Building Operation Enterprise Server for Linux

Cause

The algorithm used to pick BACnet Interface Device IDs in individual Automation Servers does not work for Container Servers since they share the same ethernet connection,.

Resolution

Perform tasks to ensure Instance IDs are unique.

1. One can prevent the issue by ensuring uniqueness when adding the BACnet Interface 
   1. When adding Interface -> BACnet Interface, do NOT click Create or Create and Edit, but click Edit in Wizard. 
   2. Enter the following data
      1. BACnet Name
      2. Instance ID (ensuring unique ID to the entire BACnet system)
      3. Leave Network Type = IP network
      4. Network ID (this should be the same network ID as the IP network is attaching) 
2. One can repair the issue and ensure uniqueness after creating the BACnet Interface.
   1. Changing the BACnet Device ID in an Automation Server to configure unique ID
   2. Repair Hosting a BACnet controller and IO Module 
   3. Fixing References in BACnet/IP Controllers