Planning an isolated Metasys BACnet/IP network - Metasys - LIT-12012458 - Field Device - 13.0

Metasys IP Networks for BACnet/IP Controllers Technical Bulletin

Document type
Technical Bulletin
Document number
Revision date
Product status

The Isolated Metasys BACnet/IP network architecture is used to create a standalone BAS IP network due to the lack of an available IT network, or because the BAS IP devices are not allowed to connect to the existing IT network. In the case of new construction, an Isolated network may be set up as a provisional network before the availability of the IT network , and then be converted to a connected Metasys BACnet/IP Network once the IT network is available. Whether the Isolated network will be converted to a connected network at some time in the future must be considered when planning the Isolated network to simplify the conversion of the Isolated Network to a Connected network.

If the Isolated network will be converted to a Connected network, the Isolated network must be deployed using the same IT subnets and VLANs which will be used when the network is ultimately connected to the IT network. Likewise, if the network engine s need to communicate with other BACnet devices in the IT network once the BAS network is connected to the IT network, the network engine s must be placed in the future IT subnet and VLAN rather than in the subnets with the IP controllers they supervise. This allows the Isolated network to convert to a Connected network with little to no configuration changes on the BAS switches.