Sample Cluster Control Connections

The GigaVUE‑OS provides a flexible approach to cluster control traffic, allowing you to route it over cluster management or Mgmt ports. The ports available and their ethx designations vary by control card version and node type, as summarized in the following table:

Control Card/Node Type	Possible Cluster Control Ports	Deployment Models
HCCv2 Control Card	Mgmt (eth0)	■   Mgmt (eth0) and L2 switch
GigaVUE‑HC3 Node	Mgmt (eth0)	■   Mgmt (eth0) and L2 switch
GigaVUE‑HC2 Node	Mgmt (eth0)	■   Mgmt (eth0) and L2 switch
GigaVUE‑HC1 Node	Mgmt (eth0)	■   Mgmt (eth0) and L2 switch
GigaVUE TA Series Nodes	Mgmt (eth0)	■   Mgmt (eth0) and L2 switch

Sample Cluster Control Configurations

Nodes in the same cluster must use the same cluster interface. For example, if there is a GigaVUE-TA10 in the cluster, all nodes in the cluster must use eth0.

Zeroconf for Cluster Management Ports

By default, cluster management ports use zero configuration networking (zeroconf) to establish networking settings. This eases configuration when establishing clusters using the cluster management port(s).

Keep Cluster Management Ports Connected!

Important: Clusters implemented using the cluster management ports for cluster control traffic must ensure that the cluster management ports of all nodes in the cluster are connected at all times. This prevents a situation where multiple leaders claim the management VIP address, resulting in the inability to connect to it at all.