BACnet BDT on a BACnet BBMD becomes corrupted after upgrade

Issue

BACnet Broadcast Device Table (BDT) on a BACnet Broadcast Management Device (BBMD) becomes corrupted after a server version upgrade, only if the BACnet BDT was taught from another BBMD

The following upgrades have this issue v1.5 to v1.6, v1.6 to v1.7, v1.7 to v1.8

Product Line

SmartStruxure Solution

Environment

BACnet Broadcast Device Table BBDT BDT Management BBMD

Cause

1. When a BDT is manually built (or BBMD first created), BDTE00001 is always it's own IP address. In the example this is 192.168.1.15

2. When the BDT is taught from another BBMD, the BDT is changed and BDTE00001 is modified.

3. When a Server (Enterprise or Automation) is upgraded (V1.5-1.6, 1.6-1.7, 1.7-1.8), then BDT entry BDTE00001 is changed to it's own IP address.

4. Thus the Servers BBMD BDT can be corrupted with the Server IP address apearing twice in the BDT

Resolution

The taught BDT can either be set manually, before the upgrade, so it does not get corrupted by the upgrade process or be corrected following the upgrade.

Option 1: Change the BDT before the upgrade
The BDT Entry BDTE00001 should be set to the IP address the Server that contains it. The BDT Entry (BDTE00002 in the simple example above) that held the IP address of the Server should be set to the value that was in BDTE00001.

 

Option 2: Correct the BDT after the upgrade
For the first Server being upgraded

  1. Upgrade the Server
  2. Log into the Server and view the BDT from WorkStation
  3. Multi-select and delete all entries,
  4. Then manually reenter in all the BDT entries. 

 

For all remaining servers being upgraded

  1. Upgrade the Server
  2. Log into the Server and view the BDT from WorkStation
  3. Multi-select and delete all entries
  4. From the First Server BBMD do a teach
  5. Verify the BDT table is in the Server

 

Below would be the first upgraded Server as option 2 or a corrected as option 1

 

NOTES
1. Versions 1.8 and beyond include a fix so that the "BDT Teach" Mechanism does not allow the BDTE00001 to be changed.
2. A hotfix will be available in V1.7
3. Upgrading to a fixed version will not correct the issue, one of the two resolutions above will still need to be completed.