Knowledge Base

The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
 
Search the VMware Knowledge Base (KB)   View by Article ID
 

Applying host profiles on ESX/ESXi 4.x and 5.x can swap vmk# order (1037576)

Symptoms

  • When applying Host Profiles to an ESX/ESXi host, the network configuration of the ESX/ESXi hosts changes.
  • For example, the network configuration for an ESX/ESXi host from which the Host Profile is created looks like:

    vSwitch0:
    vmk0: Management
    vmk1: vMotion

    After applying the host profile, the network configuration of the ESX/ESXi host looks like:

    vSwitch0:
    vmk0:  vMotion
    vmk1: Management

  • IP address of the host as displayed on the DCUI will change to whatever IP is associated with vmk0 (e.g. the vmotion IP address) so the host will appear to have the wrong IP address after applying the host profile. 
  • If you have three or four vmkernel interfaces, when you capture or update the host profile from a reference host, you see that the vmkernel interfaces are reversed.
  • Applying a host profile attempts to remove a kernel port.

Cause

This issue occurs because the Host Port Profile in the Host Profile list has vMotion before Management and it gets applied in that  order.

Resolution

This is a known issue.

To work around this issue, edit the host profiles:

Note: When editing the host profile manually, you will be removing any networks listed before the management network.
  1. Log into the vCenter Server using the vSphere Client.
  2. Click Home
  3. Under the Management section, click Host Profiles
    1. If using legacy networking, choose  Edit Profile, then expand Networking configuration > Host port group
    2. If using DVS networking, choose Edit Profile > Networking configuration > Host virtual NIC

  4. Find the port-group's which are using management service and re-create their profiles

    To re-create identical new port-group profiles:
  • Right-click the Host port group folder and click Add Profile
  • Name the profile and click OK
  • Expand the Host port group, right-click on the newly created profile and re-name it to match the old profile which will be deleted later.
  • Go through each policy option on the new profile and make sure it matches exactly as the old one
  • Save the profiles by clicking OK
  • Delete the old profiles

Notes:

  • You will not be recreating  portgroup profile which has management service enabled
  • Applying this profile to other ESX/ESXi hosts will ensure that vmk0 is assigned to management service portgroup.    

Additional Information

To be alerted when this article is updated, click Subscribe to Document in the Actions box.

Tags

host-profiles-swap-vmk

This Article Replaces

2005470

Update History

12/05/2011 - Added additional symptom 02/1/2012 - Changed resolution based on Engineering Notes. 03/28/2012 - Added 5.x to the title 04/12/2013 - Added 5.1 to Product Versions. Added Symptom.

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 7 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.
What can we do to improve this information? (4000 or fewer characters)
  • 7 Ratings
Actions
KB: