VxRail host networks
Networks and IP addresses used for the VxRail vSAN stretched cluster should be planned before starting deployment. The following table shows the VLAN IDs and network IP addresses used in this example.
|VLAN ID||Description||SFS network name||Network||Gateway|
|4091||VxRail cluster build||SFS Client Management|| |
|3939||VxRail node discovery||SFS Client Control|| |
|20||VM Data (optional)||192.168.20.0/24||192.168.20.254|
With SFS, each VLAN in the table above is automatically placed in a VXLAN virtual network with a Virtual Network Identifier (VNI) that matches the VLAN ID. VLAN 11 is in virtual network 11, VLAN 12 is in virtual network 12, and so on. In this deployment, all VxRail node-connected ports are untagged in VLAN 4091 and tagged in the remaining VLANs in the table above.
The VxRail cluster build VLAN, 4091, is used for initial access to the VxRail Manager for deployment using a jump host. VxRail Manager uses VLAN 3939 to discover VxRail nodes. The External Management VLAN is used for VxRail Manager, VxRail host management, vCenter Server, DNS, and NTP traffic. The vMotion VLAN is for VM migration, and the vSAN VLAN is for distributed storage traffic. The VM Data VLAN shown in the table is optional and is included to demonstrate how additional VLANs can be configured.
A gateway is required for External Management and vSAN traffic for communication with the witness host in Site 3. The vMotion VLAN does not use a gateway. In this deployment, vMotion is only done between Site 1 and Site 2, and this traffic is Layer 2. For additional VLANs such as VM Data, a gateway is only required if the VMs need to communicate outside of their existing network. Gateways are not used for traffic on the same virtual network between Site 1 and Site 2.
Witness host networks
In a vSAN stretched cluster, the witness host has one VLAN for Management traffic, and one VLAN for vSAN traffic. The witness host does not participate in vMotion. The VLAN IDs and network addresses used for the witness host are shown in the following table. These VLANs are configured on the DCI-Site-3 switch that the witness host is connected to. The networks differ from the SmartFabric networks because all traffic is routed from the SmartFabric to the witness host.