VLANs and IP addresses used for VxRail node traffic must be planned before VxRail deployment can begin. VxRail node traffic is divided into six or more VLANs, as shown in the following table:
|VxRail Cluster Build
|Used to build the VxRail cluster. SFS automatically creates this VLAN and names it SFS Client Management.
|VxRail Internal Management
|Used for VxRail node discovery. SFS automatically creates this VLAN and names it SFS Client Control.
|VxRail External Management
|User-specified VLAN for VxRail Manager, ESXi, vCenter Server, NTP, DNS, and vRealize Log Insight traffic
|User-specified VLAN for Virtual machine (VM) migration traffic
|User-specified VLAN for distributed storage traffic
|One or more user-specified VLANs as required for VM data traffic
VLAN IDs and network addresses that are planned for this deployment example are shown in the following table.
|SFS Client Management/VxRail cluster build
|SFS Client Control/VxRail Internal Management
|vMotion, first cluster
|vSAN, first cluster
|VM Network A, first cluster guest network (optional)
|VM Network B, first cluster guest network (optional)
|vMotion, second cluster
|vSAN, second cluster
|VM Network C, second cluster guest network (optional)
|VM Network D, second cluster guest network (optional)
In SmartFabric mode, each VLAN in VLAN IDs and network addresses is automatically placed in a VXLAN virtual network with a Virtual Network Identifier (VNI) that matches the VLAN ID. VLAN 4091 is in virtual network 4091, VLAN 1811 is in virtual network 1811, and so on.
show virtual network command is used to view virtual networks, VLANs, and port-VLAN assignments. This command is covered in more detail later in this guide.