VLANs and IP addresses used for VxRail node traffic must be planned before switch configuration and VxRail deployment can begin.
VxRail node traffic is divided into five or more VLANs, as shown in the following table.
VLAN | Purpose |
External Management | VxRail Manager, ESXi, vCenter Server, NTP, DNS, and vRealize Log Insight traffic |
vMotion | Virtual machine (VM) migration |
vSAN | Distributed storage traffic |
VM networks | One or more VLANs for VM data traffic |
Internal Management | VxRail node discovery |
VLAN configuration and IP network addresses planned for the deployment in this configuration guide are shown in the table below.
VLAN ID | Description | Network | Gateway | VLAN ports |
1811 | External Management | 172.18.11.0/24 | 172.18.11.254 | Untagged |
1812 | vMotion | 172.18.12.0/24 | NA | Tagged |
1813 | vSAN | 172.18.13.0/24 | NA | Tagged |
1814 | VM Network A | 172.18.14.0/24 | Optional, not used | Tagged |
1815 | VM Network B | 172.18.15.0/24 | Optional, not used | Tagged |
3939 | Internal Management | IPv6 multicast | not used | Tagged |
This example uses two networks for VM data traffic, VM Network A and VM Network B, with each on a separate VLAN. The actual number of VM data networks used is based on customer requirements.
The Internal Management VLAN, 3939, is used exclusively for VxRail node discovery.
When deploying the VxRail IPv6, multicast is required for node discovery. Multicast Listener Discovery (MLD) snooping and queries must be enabled on this VLAN for node discovery to succeed.