Best practices for connecting intrusion panels to the network - Honeywell Galaxy Intrusion Panel 3.2.0

Honeywell Galaxy Intrusion Panel Extension Guide 3.2.0

Product
Honeywell Galaxy Intrusion Panel
Content type
Guides > Plugin and extension guides
Version
3.2
Release
3.2.0
ft:locale
en-US
Last updated
2025-03-12

Intrusion detection panels aren’t designed to withstand heavy traffic from the network, especially when broadcast messages occur frequently. Because the panel needs to process incoming packets to check whether it’s the recipient, this might lead to increased demand on processing resources. Under heavy network load conditions, you might notice that the panel drops offline and reconnects repeatedly.

To avoid having the panel reconnect repeatedly, we recommend that you connect the panel to Security Center through an isolated network. This helps in isolating the panel from traffic for which it isn’t the recipient. Many panels can be connected to the same isolated network, as long as the network isn’t also the hub for other traffic which doesn’t involve the panels.

You can build an isolated network by adding a dedicated hardware network node (switch or router), or by creating a dedicated Virtual Local Area Network (VLAN) on a network node that provides network node configuration capabilities.
WARNING: Communication between the plugin and the Honeywell Galaxy system does not protect the integrity and confidentiality of data. As a best practice, deploy the plugin on the same subnet as the third-party Honeywell Galaxy system, within a closed network.