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:
| VLAN | Purpose |
| 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 |
| vMotion | User-specified VLAN for Virtual machine (VM) migration traffic |
| vSAN | User-specified VLAN for distributed storage traffic |
| VM networks | One or more user-specified VLANs as required for VM data traffic |
Note: All VLANs in VLANs used by VxRail share the physical connections shown in Production network connection details in this deployment.
VLAN IDs and network addresses that are planned for this deployment example are shown in the following table.
| VLAN ID | Description | Network |
| 4091 | SFS Client Management/VxRail cluster build | 192.168.10.0/241 |
| 3939 | SFS Client Control/VxRail Internal Management | IPv6 multicast |
| 1811 | External Management | 172.18.11.0/24 |
| 1812 | vMotion, first cluster | 172.18.12.0/24 |
| 1813 | vSAN, first cluster | 172.18.13.0/24 |
| 1814 | VM Network A, first cluster guest network (optional) | 172.18.14.0/24 |
| 1815 | VM Network B, first cluster guest network (optional) | 172.18.15.0/24 |
| 1822 | vMotion, second cluster | 172.18.22.0/24 |
| 1823 | vSAN, second cluster | 172.18.23.0/24 |
| 1824 | VM Network C, second cluster guest network (optional) | 172.18.24.0/24 |
| 1825 | VM Network D, second cluster guest network (optional) | 172.18.25.0/24 |
Note: SFS automatically creates VLANs 4091 and 3939. VLANs 1811 through 1825 and their network IP addresses are user-defined and are examples only. In SmartFabric mode, VLANs 1 through 3999, excluding 3939, are available for use. VLANs 4091 and 3939 may be changed from their defaults in the SFS UI under Global Settings > Fabric Settings. VLAN 3939 is also a VxRail default VLAN. If VLAN 3939 is changed in the SFS UI, you must also change it to match in VxRail per the VxRail documentation for VxRail node discovery.
Note: VLANs 4000 through 4094 are reserved for SFS. For more information about the reserved VLANs, see the SmartFabric Services User Guide.
Note: SFS uses the 172.16.0.0/16, and 172.30.0.0/16 IP address blocks internally for the leaf-spine network configuration. If these networks conflict with your environment, these default IP addresses blocks may be changed in the SFS UI under Global Settings > Fabric Settings. OMNI uses the 172.16.0.0/25 IP address block by default for the docker private network. If this block conflicts with your environment, it may be changed as shown in the OpenManage Network Integration User Guide, Release 3.2.
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.
The 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.
1 The default VxRail Manager IP address is on this network.