Issue
When a MPM is replaced on a BACnet IP network, a "Duplicate network identifier" alarm is generated
Product Line
EcoStruxure Building Expert, EcoStruxure Building Operation
Environment
- MPM
- Automation Server
Cause
If the BACnet name and instance number in the new controller is not exactly the same as the original MPM, the Automation Server will consider that an additional device has been installed and an alarm will be triggered stating that the new device has the same BACnet ID as an existing device.
Resolution
Steps to replacing a MPM to prevent the Duplicate ID alarm being triggered:
- When replacing the original MPM, note the BACnet name and Instance ID.
- Install the new MPM and enter the same BACnet name and Instance ID.
Refer to BACnet device can't be discovered due to duplicate name for more information about duplicate BACnet names.
