Why can’t I select certain network interfaces when creating an HA cluster?
Last modified date:
2025-05-09
Applicable Products
- QuTS hero h5.3.0 or later
- High Availability Manager 1.0 or later
Scenario
When creating a high-availability (HA) cluster, you have to select network interfaces for the cluster connection and the heartbeat connection. However, when you click the dropdown menus to select a network interface, certain network interfaces do not appear on the list.
Cause and Solution
Due to limitations in the HA environment, certain configurations on a network interface make the interface incompatible for use in an HA cluster.
To make your network interface available for selection, perform one or more of the following actions depending on the connection type:
- Cluster connection
- Remove any vSwitch adapter bindings from the network interface.
This prevents conflicts with virtual switch management and isolation. - If port trunking is configured, change the port trunking mode from "Balance-alb" or "Balance-tlb" to another option.
- Remove any vSwitch adapter bindings from the network interface.
- Heartbeat connection
- Remove any VLAN configuration from the network interface.
This ensures a stable and direct communication channel between the two nodes. - Remove any vSwitch adapter bindings from the network interface.
This prevents conflicts with virtual switch management and isolation. - If port trunking is configured, change the port trunking mode from "Balance-alb" or "Balance-tlb" to another option.
- Remove any VLAN configuration from the network interface.
Further Reading
- What is a cluster connection and how do I select an appropriate network interface for it?
- What is a heartbeat connection and how do I select an appropriate network interface for it?
- How do I create a high-availability cluster?
- Which QuTS hero features are currently not supported in High Availability Mode?
