White Papers

Mapping volumes to an ESXi server
26 Dell EMC SC Series: Best Practices with VMware vSphere | 2060-M-BP-V
For example, with subnet 192.168.0.x and subnet mask 255.255.255.0, the vSwitch would look like Figure 13.
iSCSI ports and NICs on a single vSwitch/single subnet (VMkernel port binding allowed)
Note: Using port binding is not recommended when the VMkernel ports are on different networks as shown in
Figure 14, because it may cause long rescan times and other problems. See Considerations for using
software iSCSI port binding in ESX/ESXi in the VMware Knowledge Base.
In configurations using multiple fault domains, with the iSCSI front-end ports configured in a multiple subnet
and multiple fault domain configurations, ensure either:
• VMkernel ports and vmnics reside in separate vSwitches (see Figure 14)
OR
• Failover order ensures one VMkernel per physical NIC in a single vSwitch
Due to the network separation, VMkernel port binding must not be used.
iSCSI VMkernel ports and NICs on multiple vSwitches/multiple subnets (port binding must not
be used).