Information Technology Reference
In-Depth Information
Figure 5.13
Use the Network
Restore Options
screen to manage
network connectiv-
ity to an ESXi host.
Let's move our discussion of VMkernel networking away from just management trafi c and
take a closer look at the other types of VMkernel trafi c, as well as how to create and coni gure
VMkernel ports.
Confi guring VMkernel Networking
VMkernel networking carries management trafi c, but it also carries all other forms of trafi c
that originate with the ESXi host itself (i.e., any trafi c that isn't generated by VMs running on
that ESXi host). As shown in Figure 5.14 and Figure 5.15, VMkernel ports are used for manage-
ment, vMotion, iSCSI, NAS/NFS access, and vSphere FT—basically, all types of trafi c that are
generated by the hypervisor itself. In Chapter 6, “Creating and Coni guring Storage Devices.”
we detail the iSCSI and NAS/NFS coni gurations; in Chapter 12, we provide details of the vMo-
tion process and how vSphere FT works. These discussions provide insight into the trafi c l ow
between VMkernel and storage devices (iSCSI/NFS) or other ESXi hosts (for vMotion or vSphere
FT). At this point, you should be concerned only with coni guring VMkernel networking.
A VMkernel port actually comprises two different components: a port group on a vSwitch
and a VMkernel network interface, also known as a
vmknic
. Creating a VMkernel port using the
vSphere Web Client combines the task of creating the port group and the VMkernel NIC.
Perform the following steps to add a VMkernel port to an existing vSwitch using the vSphere
Web Client:
1.
If not already connected, open a supported web browser and log in to a vCenter Server
instance. For example, if your vCenter Server instance is called “vcenter,” then you'll
connect to
https://vcenter.domain.name:9443/vsphere-client an
d then log in with
appropriate credentials.
2.
From the vSphere Web Client home page, select vCenter from the navigation list on
the left.
