NSX Installation on an ESXi Host fails with an error "Host configuration: NSXA Vim not ready;"
search cancel

NSX Installation on an ESXi Host fails with an error "Host configuration: NSXA Vim not ready;"

book

Article ID: 406822

calendar_today

Updated On:

Products

VMware NSX

Issue/Introduction

  • When attempting to install NSX on an ESXi host, it fails with error: "Host configuration: NSXA Vim not ready;":
  • The following error is observed on the NSX Manager /var/log/syslog

    NSX ####### FABRIC [nsx@#### comp="nsx-manager" level="INFO" subcomp="manager"] TransportNodeStateAutoRectifier: Syncing TransportNode TransportNode/########-####-####-####-############ [Current config status = PARTIAL_SUCCESS, Failure code = 8804].
    NSX  ####### - [nsx@#### comp="nsx-controller" level="WARNING" subcomp="l2AppUfo"] Failed to find or create logical entry LogicalSwitchId:[id=########-####-####-####-############, vni=-1]

    <...>

    CONFIG_STATUS_IN_PROGRESS#012failure_code: 8804#012failure_message {#012  value: " Host configuration: host switch apply operation failed: [Error; ######_######|50 ## ## ## ## ## ## ##-## ## ## ## ## ## ## ##|VDS|ApplyDvs(50 ## ## ## ## ## ## ##-## ## ## ## ## ## ## ##) failed: {\'fault1\': {\'objectId\': \'50 ## ## ## ## ## ## ##-## ## ## ## ## ## ## ##\', \'fault\': \'PlatformConfigFault\', \'msg\': \'An error occurred during host configuration: .\', \'faultMessage\': [\'Operation failed, diagnostics report: Unable to Set: Failure\']}}; 

  • After installing NSX on the ESXi host, the vmkernel adapter disappears from the vSphere UI on the affected host:
  • From vSphere UI -> Networking tab, the DVS displays the error: "The vSphere Distributed Switch configuration on some hosts differed from that of the vCenter Server."
  • Following errors can be seen in the ESXi host logs /var/log/vmkernel.log

    In(182) vmkernel: cpu40:2098516)NetDVS: 9918: Failed to clear host property com.vmware.vswitch.uplinkMirrorSessions on DVS 50 ## ## ## ## ## ## ##-## ## ## ## ## ## ## ## as it is not set yet.
    In(182) vmkernel: cpu40:2098516)NetDVS: 9918: Failed to clear host property com.vmware.vswitch.LLSPAN.rxDispatcher on DVS 50 ## ## ## ## ## ## ##-## ## ## ## ## ## ## ## as it is not set yet.
    In(182) vmkernel: cpu40:2098516)NetDVS: 9918: Failed to clear host property com.vmware.vswitch.macLearning.learnStatic on DVS 50 ## ## ## ## ## ## ##-## ## ## ## ## ## ## ## as it is not set yet.
    In(182) vmkernel: cpu40:2098516)NetDVS: 9918: Failed to clear host property com.vmware.vswitch.uplinkMirrorSessions on DVS 50 ## ## ## ## ## ## ##-## ## ## ## ## ## ## ## as it is not set yet.
    In(182) vmkernel: cpu40:2098516)NetDVS: 9918: Failed to clear host property com.vmware.vswitch.LLSPAN.rxDispatcher on DVS 50 ## ## ## ## ## ## ##-## ## ## ## ## ## ## ## as it is not set yet.
    In(182) vmkernel: cpu40:2098516)NetDVS: 9918: Failed to clear host property com.vmware.vswitch.macLearning.learnStatic on DVS 50 ## ## ## ## ## ## ##-## ## ## ## ## ## ## ## as it is not set yet.
    In(182) vmkernel: cpu40:2098516)NetDVS: 9918: Failed to clear host property com.vmware.vswitch.uplinkMirrorSessions on DVS 50 ## ## ## ## ## ## ##-## ## ## ## ## ## ## ## as it is not set yet.
    In(182) vmkernel: cpu40:2098516)NetDVS: 9918: Failed to clear host property com.vmware.vswitch.LLSPAN.rxDispatcher on DVS 50 ## ## ## ## ## ## ##-## ## ## ## ## ## ## ## as it is not set yet.
    In(182) vmkernel: cpu40:2098516)NetDVS: 9918: Failed to clear host property com.vmware.vswitch.macLearning.learnStatic on DVS 50 ## ## ## ## ## ## ##-## ## ## ## ## ## ## ## as it is not set yet.
    In(182) vmkernel: cpu126:2099616 opID=d7136aed)NetDVS: 9918: Failed to clear host property com.vmware.etherswitch.ipfixbehavior on DVS 50 ## ## ## ## ## ## ##-## ## ## ## ## ## ## ## as it is not set yet.
    In(182) vmkernel: cpu126:2099616 opID=d7136aed)NetDVS: 9918: Failed to clear global property com.vmware.etherswitch.ipfixbehavior on DVS 50 ## ## ## ## ## ## ##-## ## ## ## ## ## ## ## as it is not set yet.
    Wa(180) vmkwarning: cpu126:2099616 opID=d7136aed)WARNING: kcp: KCP_DvpgPropDeactivate:163: [nsx@6876 comp="nsx-esx" subcomp="kcp"]Failed to unregister property: com.vmware.nsx.kcp.enable for DvsPortset-4 : Busy
    Wa(180) vmkwarning: cpu126:2099616 opID=d7136aed)WARNING: kcp: KCP_VdsPropActivate:283: [nsx@6876 comp="nsx-esx" subcomp="kcp"]Failed to register property: com.vmware.nsx.kcp.enable for DvsPortset-4 : Already exists
    In(182) vmkernel: cpu126:2099616 opID=d7136aed)vswitch: VSwitchActivate:9891: [nsx@6876 comp="nsx-esx" subcomp="vswitch"]Failed to post netevent com.vmware.nsx.vswitch.activate.23382415 on ps DvsPortset-4: Failure
    Wa(180) vmkwarning: cpu126:2099616 opID=d7136aed)WARNING: kcp: KCP_DvpgPropActivate:134: [nsx@6876 comp="nsx-esx" subcomp="kcp"]Failed to register property: com.vmware.nsx.kcp.enable for DvsPortset-4 : Already exists
    In(182) vmkernel: cpu126:2099616 opID=d7136aed)NetDVS: 9918: Failed to clear host property com.vmware.common.host.volatile.upgrade70OrLater on DVS 50 ## ## ## ## ## ## ##-## ## ## ## ## ## ## ## as it is not set yet.
    In(182) vmkernel: cpu92:2099620 opID=c948cb09)NetDVS: 9918: Failed to clear host property com.vmware.common.host.volatile.upgrade70OrLater on DVS 50 ## ## ## ## ## ## ##-## ## ## ## ## ## ## ## as it is not set yet.
    In(182) vmkernel: cpu66:2101786)NetDVS: 9918: Failed to clear host property com.vmware.nsx.pendingUserActions on DVS 50 ## ## ## ## ## ## ##-## ## ## ## ## ## ## ## as it is not set yet.

    Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Cause

The cause of this issue is the presence of stale properties on the ESXi host. These were left on the host during a previous unsuccessful uninstall of NSX and when an attempt was made to install NSX again, the process failed due to the stale properties.

Resolution

This issue is resolved in VMware NSX 4.2, available at Broadcom downloads.
If you are having difficulty finding and downloading software, please review the Download Broadcom products and software KB.

Note: If you are still observing this issue in NSX 4.2 or later, please open a support case with Broadcom Support and refer to this KB article.
For more information, see Creating and managing Broadcom support cases.

Workaround:

  1. A workaround is to run the "del nsx" command on the affected host. Please see step 8 in this doc:
    Uninstall NSX from a Managed Host in a vSphere Cluster

    Note: Please ensure the host is in maintenance mode and out of the cluster you are trying to add/install.

  2. If the option 1 does not resolve this issue:
    1. Place the affected host in Maintenance mode.
    2. Remove the host from the NSX cluster and confirm NSX is uninstalled from the host
    3. Move all host networking to a standard switch
    4. Remove the host from the VDS
    5. Add the host back to the VDS, migrating all required networking to the VDS.
    6. Add the host back to the NSX cluster.
Powered by Wolken Software