Starting with VxRail version 7.0.130, NIC teaming can be configured on the VxRail non-management networks with both a customer-supplied and VxRail supplied virtual-distributed switch after the cluster initial implementation process is complete. NIC teaming enables the formation of a link aggregation group, which is a logical port that represents a pair of physical ports on a VxRail node. If the ports on the top-of-rack switches connected to these logical ports are also configured into a link aggregation group, peering between the two link aggregation groups will enable an active/active port configuration and support load-balancing for network optimization.
Figure 63. Enabling link aggregation for load-balancing
The following rules are applicable for enabling link aggregation:
- A minimum of four Ethernet ports per VxRail node is required for the VxRail networks.
- Two ports configured to support VxRail management networks (Management/vCenter/VxRail discovery)
- Two ports configured to support vSAN and vMotion.
- Can be all NDC/OCP ports, all PCIe ports, or a mixture of NDC/OCP and PCIe ports
- If all your VxRail networks are on NDC/OCP-based ports, you can migrate the non-management VxRail networks to PCIe-based ports to enable NIC redundancy.
- All VxRail node ports configured for link aggregation must be the same speed.
- Link aggregation can only be configured on the non-management VxRail networks.
- If you want to enable load-balancing only on the vSAN network, you have the option to migrate the vMotion network over to the ports supporting the VxRail management networks.
- The top-of-rack switches support dynamic link aggregation with LACP.
Dynamic link aggregation requires:
- Dynamic port channels are configured on the adjacent top-of-rack switches.
- LACP is enabled on the adjacent top-of-rack switches.
- An LACP policy is configured on the virtual distributed switch.
- The load-balancing setting on the LACP policy is compatible with the supported load-balancing hash algorithms on the adjacent top-of-rack switches.
Figure 64. LACP Policy configuration on virtual-distributed switc