3-8 ESX Operation and Configuration
DUPLEX LAN CONFIGURATION
The operable network configuration is described here..
Functional Overview
Duplicating a LAN is achieved by binding multiple adapters to the same virtual switch (NIC
teaming). If an uplink adapter fails, it switches to another adapter to continue the operation.
Operable Network Configuration
For NEC Express5800/ft series, network interface names are based on the naming convention as
described in the table below. Network duplication is achieved by pairing network interfaces of PCI
slots in CPU/IO module 0 and network interfaces in the same PCI slots in CPU/IO module 1 (i.e.
Two network interfaces are bound to a switch). You can configure the setting of and check the
network interfaces from Vsphere client.
For more specific setting method, see VMware Vsphere document "ESX Configuration Guide".
If NIC Teaming configuration is set Route based on ip hash, it may cause disconnected network
for 30 seconds in the maximum when the failover occurs due to failure so on.
It is necessary to be used after carefully examining the setting of application and client.
And if Load Balancing is set Route based on source MAC hash or Route based on the
originating port ID, it may cause temporarily disconnected network for VMware specific when the
failover occurs.
It is necessary to be used after setting Beacon Probing from Failover Detection.
PCI slot and network interface name
PCI slot
On Board
PCI-e slot 1
PCI-e slot 2
PCI-e slot 3
PCI-e slot 4
Port
CPU/IO module 0
#1
vmnic 100600
#2
vmnic 100601
#1
vmnic 100100
#2
vmnic 100101
#1
vmnic 100200
#2
vmnic 100201
#1
vmnic 100300
#2
vmnic 100301
#1
vmnic 100400
#2
vmnic 100401
CPU/IO module 1
vmnic 110600
vmnic 110601
vmnic 110100
vmnic 110101
vmnic 110200
vmnic 110201
vmnic 110300
vmnic 110301
vmnic 110400
vmnic 110401