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.
- From VxRail 7.0.010 and later, you have the choice of configuring a single virtual distributed switch to the external VMware vCenter Server before the initial cluster build process.
- From VxRail 7.0.130 and later, you have the choice of configuring one or two virtual-distributed switches to the external VMware vCenter Server instance before the initial cluster build process.
- Unless your data center already has a VMware vCenter Server instance compatible with VxRail, deploy a VMware vCenter Server instance that serves 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 VMware vCenter Server instance.
- Configure a port group for each of the required VxRail networks. Use 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 VxRail networks, configure the LACP policy on the virtual-distributed switch, and apply the policy to the appropriate port group or port groups.
Refer the configuration settings that are 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 Portgroup Default Settings.
|Network configuration table||Action|
|Row 41||Enter the name of the virtual-distributed switch that will support the VxRail cluster networking.|
|Row 42||If a decision is made to configure two virtual-distributed switches, enter the name of the second virtual-distributed switch.|
|Row 43||Enter the name of the port group that will enable connectivity for the VxRail external management network.|
|Row 44||Enter the name of the port group that will enable connectivity for the VxRail-managed VMware vCenter Server network.|
|Row 45||Enter the name of the port group that will enable connectivity for the VxRail internal management network.|
|Row 46||Enter the name of the port group that will enable connectivity for the VMware vSphere vMotion network.|
|Row 47||Enter the name of the port group that will enable connectivity for the vSAN network.|
If your plan is to have more than one VxRail cluster deployed against a single customer-managed virtual-distributed switch, Follow a distinctive naming standard for the distributed port groups. This eases 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. Follow a distinctive naming standard for these distributed port groups.