Technical Guide | HelixNet IP Network Guidance Page 9
- Configuration and control of any device is possible through any other unit in the
group
- Configuration information is both distributed and persisted within every node of
the group
- The Link-Group significantly reduces loss of service within the set group
HelixNet
Pairing by
Name
HKB-2X, HRM-4X, and HXII-BP on the same subnet can pair to a system by name. The
system uses mDNS to propagate HMS and HRM (when configured as an expansion host)
presence in a network. As a device populates it’s mDNS entry, it specifies an ID, an IP
address, a name and a list of services.
When configuration changes, the mDNS entry is updated and all devices connected “by
name” will update and re-pair/link/expand as required.
NETWORK INSTALLATION
Managed
Ethernet
Switch
When connecting HelixNet to a
managed network switch, ensure that the connection performs
at a minimum of 100Mb full duplex.
If the system is using more than one switch, ensure that the bridge between the switches also
operates at a minimum of 1Gb full duplex. When using a managed switch, the port connected
to the HelixNet Main Station and endpoints should be set at 100Mb versus letting the port auto-
negotiate.
Note: You do not need to set all ports to 100Mb, only the ones connected to the HMS-4X, HRM-
4X, HKB-2X & HXII-BP.
We recommend the following specifications when selecting a managed switch to use with
HelixNet:
- 100/1000Base-T Layer 3 Managed Switch
- QoS support with the audio traffic prioritized over other data
- If Energy Efficient Ethernet is supported, ensure it is disabled
- SPF/Mini-GBIC support
If connecting two or more switches together, we recommend the bridge / link
ports between the switches supports at least 1GB.
To Next Page
Loading...
Need help?
General
