Information Technology Reference
In-Depth Information
-Bit vs. -Bit
Although the vSphere Client can be installed and is supported on 64-bit Windows operating sys-
tems, the vSphere Client itself remains a 32-bit application and runs in 32-bit compatibility mode.
Reconfi guring the Management Network
During the installation of ESXi, the installer creates a virtual switch—also known as a
vSwitch
—
bound to a physical NIC. The tricky part, depending on your server hardware, is that the
installer might select a different physical NIC than the one you need for correct network connec-
tivity. Consider the scenario depicted in Figure 2.12. If, for whatever reason, the ESXi installer
doesn't link the correct physical NIC to the vSwitch it creates, then you won't have network
connectivity to that host. We'll talk more about why ESXi's network connectivity must be con-
i gured with the correct NIC in Chapter 5, but for now just understand that this is a requirement
for connectivity. Since you need network connectivity to manage the host from the vSphere
Client, how do you i x this?
Figure 2.12
Network con-
nectivity won't be
established if the
ESXi installer links
the wrong NIC to
the management
network.
Correct
Incorrect
esxi-03.lab.local
esxi-04.lab.local
Management
Management
vSwitch0
vSwitch0
vmnic0
vmnic1
vmnic0
vmnic1
Management
network/
VLAN
Production
network/
VLAN
The simplest i x for this problem is to unplug the network cable from the current Ethernet
port in the back of the server and continue trying the remaining ports until the host is accessi-
ble, but that's not always possible or desirable. The better way is to use the DCUI to reconi gure
the management network so that it is converted the way you need it to be coni gured.
