Search the VMware Knowledge Base (KB)
View by Article ID

"Not Ready" Installation Status in NSX (2075600)

  • 3 Ratings
Language Editions


  • Under Networking and Security, Installation Status appears as Not Ready on the Clusters and Hosts. Clicking on Resolve does not fix the issue
  • vSphere ESX Agent Manager showing Error VIB module for agent is not installed on host
  • ESXi host fails to access VIBs from the vCenter Server.
  • While changing from vShield Endpoint to NSX Manager, you may see Failed status for one or more hosts in a cluster.
Note: For additional symptoms and log entries, see the Additional Information section.


Validate that each troubleshooting step is true for your environment. The steps are ordered in the most appropriate sequence to isolate the issue and identify the proper resolution. Do not skip a step.
  1. Verify that DNS is configured correctly on the vCenter Server, the ESXi hosts and NSX Manager. Ensure that forward and reverse DNS resolution from vCenter Server, ESXi hosts, NSX Manager and Update Manager are working.

  2. VMware recommends to have Network Time Protocol (NTP) configured on the environment. Verify that NTP is configured correctly.

  3. Verify that all ports required for NSX for vSphere 6.x are not blocked by a firewall.  For related information, see Network Port Requirements for VMware NSX for vSphere (2079386)

  4. Verify that the vCenter Server Managed IP Address is configured correctly.

  5. Verify that the VMware Update Manager is working correctly. Ensure that the Update Manager service is running.

    For related information, see:
  6. If non-default ports are specified during a vCenter Server deployment, ensure that these ports are not being blocked by the ESXi host firewall.

  7. Verify that vCenter server vpxd process is listening on TCP port 8089. NSX Manager only support the default port 8089.

    Note: When vCenter is installed, vpxd selects a TCP port (8089, by default) for the ESX Agent Manager. If that port is in use at the time of installation, it will select the next free port (8090 or higher port).

If the issue persists even after trying the preceding steps, collect the VMware Support Script Data and file a support request with VMware Support and note this Knowledge Base article ID (2075600) in the problem description.

See Also

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.


  • 3 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)

Please enter the Captcha code before clicking Submit.
  • 3 Ratings