Dell VxRail Architecture Overview

PDF

Network

Although VMware supports using a VLAN other than VMware vSAN VLAN for Witness Traffic Separation (WTS), VxRail requires the WTS network to use its own VLAN. This layout is specific to the VxRail 2-node cluster with VMware vSAN.

VxRail 8.0.320 and later versions support VxRail-managed VMware VDS and customer-managed VMware VDS with 2 port minimum and several LAG options.

The following table outlines the network layout that VxRail uses in the configuration of a 2-node cluster:

Table 1. Network layout for VxRail 2-node clusters with VMware vSAN (4 uplinks)Network layout for VMware vSAN 2-node clusters
Traffic	Members	NIOC shares	UPLINK1	UPLINK2	UPLINK3	UPLINK4
Traffic	Members	NIOC shares	VMNIC0	VMNIC1	VMNIC2	VMNIC3
Management network	ESXi vmk2	40	Standby	Active	Unused	Unused
VMware vCenter Server network	VMware vCenter Server, VxRail Manage, eth0,	N/A	Standby	Active	Unused	Unused
VxRail Management	ESXi vmk0 (IPv6 discovery), VxRail Manager (eth1)	N/A	Standby	Active	Unused	Unused
Witness traffic	ESXi vmk5		Active	Standby
VMware vSAN	ESXi vmk3	100	Unused	Unused	Active	Standby
VMware vSphere vMotion	ESXi vmk4	50	Unused	Unused	Standby	Active
VMs	VMs	60	Active	Standby	Unused	Unused

Table 2. Network layout for VxRail 2-node clusters with VMware vSAN (2 uplinks)Network layout for VMware vSAN 2-node clusters
Traffic	Members	NIOC shares	UPLINK1	UPLINK2
Traffic	Members	NIOC shares	VMNIC0	VMNIC1
Management network	ESXi vmk2	20	Active	Standby
VMware vCenter Server network	VMware vCenter Server, VxRail Manager (eth0)	N/A	Active	Standby
VxRail Management	VMware ESXi vmk0 (IPv6 discovery), VxRail Manager (eth1)	N/A	Active	Standby
Witness traffic	ESXi vmk5		Active	Standby
VMware vSAN	ESXi vmk3	100	Standby	Active
VMware vSphere vMotion	ESXi vmk4	50	Active	Standby
VMs	VMs	30	Active	Standby