VMkernel NIC Not Correctly Configured

Products

• VMware vCenter Server
• VMware vSphere ESXi

Issue/Introduction

Summary

The reported event indicates that the VMkernel NIC (vmk#) is not configured correctly in the ESX advanced configuration option /Migrate/Vmknic for the ESX host on which the virtual machine is running.

/Migrate/Vmknic can be used to specify a particular VMkernel NIC (vmknic) for VMotion to bind to when attempting to connect to the remote host. Generally, it is not needed, and if multiple vmknics are configured, VMotion binds to the correct vmknic based on its IP address.

Example

If vmk0 is not a valid VMkernel NIC and is specified in /Migrate/Vmknic, then you see the following:

The ESX advanced config option /Migrate/Vmknic is set to an invalid vmknic: vmk0. /Migrate/Vmknic specifies a vmknic that VMotion binds to for improved performance. Please update the config option with a valid vmknic or, if you don't want VMotion to bind to a specific vmknic, remove the invalid vmknic and leave the option blank.

Impact

New virtual machine migrations with VMotion on the affected hosts fail to correctly initiate.

Environment

VMware vCenter Server 4.0.x
VMware ESXi 4.0.x Embedded
VMware ESXi 4.0.x Installable
VMware ESX 4.0.x

Resolution

Use one of the following options to resolve this issue.

Using the vSphere Client to Configure the VMkernel NIC

1. Connect to the ESX/ESXi host by using the vSphere client.
2. Select Configuration > Advanced Settings.
3. From the list of advanced options, select Migrate.
4. Check if the vmknic information is accurate for Migrate. Vmknic and configure the appropriate VMkernel NIC port.

Using the Service Console to Configure the VMkernel NIC

Connect to the ESX/ESXi host's service console and run the following command:

# esxcfg-advcfg –s vmk# /Migrate/Vmknic

where vmk# refers to given vmkernel interface.