Configuration overview—Customer-managed virtual distributed switch

You can skip this section if your VxRail version is not 7.0.010 or later, or if you do not plan to deploy VxRail against one or more customer-managed virtual distributed switches.

Before VxRail version 7.0.010, if you deployed the VxRail cluster on an external, customer-managed vCenter, a virtual distributed switch was configured on the vCenter instance as part of the initial cluster build process. The automated initial build process deployed the virtual distributed switch adhering to VxRail requirements in the vCenter instance, and then attached the VxRail networks to the port groups on the virtual distributed switch. Depending on the target version planned for your VxRail cluster, you can preconfigure one or two virtual distributed switches on your external vCenter instance to support VxRail networking.

• Starting with VxRail version 7.0.010, you have the choice of configuring a single virtual distributed switch to the external vCenter before the initial cluster build process.
• Starting with VxRail version 7.0.130, you have the choice of configuring one or two virtual distributed-switches to the external vCenter instance before the initial cluster build process.

If you choose to manually configure the virtual switches and configure the network before initial cluster build, you must perform the following prerequisites:

• Unless your data center already has a vCenter instance compatible with VxRail, deploy a vCenter instance that will serve as the target for the VxRail cluster.
• You can deploy the VxRail cluster to an existing virtual distributed switch or a pair of virtual distributed switches on the target vCenter instance.
• Configure a port group for each of the required VxRail networks. Dell recommends using naming standards that clearly identify the VxRail network traffic type. 
• Configure the VLAN assigned to each required VxRail network on the respective port group. The VLANs for each VxRail network traffic type are in the VxRail Networks section in Appendix A: VxRail Network Configuration Table.
• Configure at least two uplinks on the virtual distributed switch to support the VxRail cluster.
• Configure the teaming and failover policies for the distributed port groups. Each port group is assigned a teaming and failover policy. You can choose a simple strategy and configure a single policy that is applied to all port groups, or configure a set of policies to address requirements at the port group level.
• If you plan to enable load balancing with LACP against any nonmanagement VxRail networks, configure the LACP policy on the virtual distributed switch, and apply the policy to the appropriate port group or port groups. 

Figure 61.    Sample port groups on customer-managed virtual distributed switch

Dell recommends referencing the configuration settings applied to the virtual distributed switch by the automated VxRail initial build process as a baseline. This ensures a successful deployment of a VxRail cluster against the customer-managed virtual distributed switch. The settings that are used by the automated initial build process can be found in Appendix E: Virtual Distributed Switch Port Group Default Settings.

If your plan is to have more than one VxRail cluster deployed against a single customer-managed virtual distributed switch, Dell recommends establishing a distinctive naming standard for the distributed port groups. This will ease network management and help distinguish the individual VxRail networks among multiple VxRail clusters.

Configuring port groups on the virtual distributed switch for any guest networks you want is not required for the VxRail initial build process. These port groups can be configured after the VxRail initial build process is complete. Dell also recommends establishing a distinctive naming standard for these distributed port groups.

Prepare link aggregation on customer-managed virtual distributed switch

You can skip this section if your VxRail version is not 7.0.130 or later, and you do not plan to enable link aggregation against one or more VxRail networks on the customer-managed virtual distributed switch.

Starting with VxRail version 7.0.130, you can configure link aggregation against the VxRail nonmanagement networks, which include the vSAN network and vMotion network. The following prerequisites must be met to enable link aggregation on the VxRail nonmanagement networks:

• Four ports from each VxRail node must be configured to support VxRail networking.

• Two ports will be configured to support VxRail management networks. Link aggregation is not supported on these networks.
• Two ports will be configured to support VxRail nonmanagement networks. Link aggregation is supported on these networks.

• Link aggregation can be configured on the vSAN network, vMotion network, or both.

• If link aggregation is not to be configured on the vMotion network, this network must be assigned to the same uplinks supporting the VxRail management networks.

• The adjacent top-of-rack switches must be configured to support link aggregation. See the guides provided by your switch vendor to perform this task.

The following tasks must be completed on the virtual distributed switch on your customer-managed vCenter instance to support link aggregation:

• Configure an LACP policy on the virtual distributed switch

Figure 62.    Sample LACP policy configured on virtual distributed switch.

• Configure the teaming and failover policy on the port groups that are targeted for link aggregation.

Figure 63.    Sample LACP Policy configured as active uplink in teaming and failover policy