Best practices for connecting intrusion panels to the network - Honeywell Galaxy intrusion panel 3.1

Honeywell Galaxy Intrusion Panel Extension Guide 3.1

Applies to
Honeywell Galaxy intrusion panel 3.1
Last updated
Content type
Guides > Plugin and extension guides
Honeywell Galaxy intrusion panel
Plugin and extension guides

Intrusion detection panels are not 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 is 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 to isolate the panel from traffic for which it is not the recipient. Many panels can be connected to the same isolated network, as long as the network is not also the hub for other traffic which does not 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.