"Not Ready" Installation Status in NSX for vSphere
search cancel

"Not Ready" Installation Status in NSX for vSphere

book

Article ID: 318902

calendar_today

Updated On:

Products

VMware NSX

Issue/Introduction

This article provides steps to resolve the cluster not ready issue in the NSX environment.

Symptoms:

  • 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.

Environment

VMware NSX for vSphere 6.3.x
VMware NSX for vSphere 6.1.x
VMware NSX for vSphere 6.4.x
VMware NSX for vSphere 6.0.x
VMware NSX for vSphere 6.2.x

Resolution

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. Recommendation is 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 port change is identified , update the port number in the following files to remediate, 

    1. C:\ProgramData\VMware\vCenterServer\cfg\appliance\firewall\vmware-vpxd (1 hit)
      Line 19: "port": 8089
       
    2. C:\ProgramData\VMware\vCenterServer\cfg\install-defaults\vpxd.int.sdk-tunnel-port (1 hit)
      Line 1: 8089
       
    3. C:\ProgramData\VMware\vCenterServer\cfg\rereg\4a84ebc6-####-####-####-f9006e946d1e_spec (6 hits)
      Line 55: rhttpproxy.endpoint1.address=8089
      Line 58: rhttpproxy.endpoint2.namespace=sdkTunnel:8089
      Line 60: rhttpproxy.endpoint2.address=8089
      Line 63: rhttpproxy.endpoint3.namespace=${system.urlhostname}:8089
      Line 65: rhttpproxy.endpoint3.address=8089
       
    4. C:\ProgramData\VMware\vCenterServer\cfg\vmware-eam\eam.properties (3 hits)
      Line 58: vc.tunnelSdkUri.template=https://##{VC_HOST_NAME}##:8089/sdk/vimService
      Line 59: vc.tunnelSdkUri=##{VC_HOST_NAME}##::8089/sdk/vimService
       
    5. C:\ProgramData\VMware\vCenterServer\cfg\vmware-rhttpproxy\endpoints.conf.d\vpxd-proxy.conf (2 hits)
      Line 1: VC-####:8089 localtunnel 8089 allow reject
      Line 1: VC-####:8089 localtunnel 8089 allow reject
       
    6. C:\ProgramData\VMware\vCenterServer\cfg\vmware-rhttpproxy\endpoints.conf.d\vpxd-rhttpproxy-endpoint.conf (5 hits)
      Line 5: /sdkTunnel localtunnel 8089 allow reject
      Line 6: sdkTunnel:8090 localtunnel 8089 allow reject
      Line 6: sdkTunnel:8090 localtunnel 8089 allow reject
      Line 7: ##{VC_HOST_NAME}##:8089 localtunnel 8089 allow reject
      Line 7: ##{VC_HOST_NAME}##:8089 localtunnel 8089 allow reject
       
    7. C:\ProgramData\VMware\vCenterServer\cfg\vmware-vpx\proxy.xml (9 hits)
      Line 39: <port>8089</port>
      Line 71: <serverNamespace>VC-DSN:8089</serverNamespace>
      Line 73: <port>8089</port>
      Line 77: <serverNamespace>VC-IP:8089</serverNamespace>
      Line 79: <port>8089</port>
      Line 83: <serverNamespace>[VC-IPV6]:8089</serverNamespace>
      Line 85: <port>8089</port>
      Line 90: <port>8089</port>
      Line 91: <serverNamespace>sdkTunnel:8089</serverNamespace>
       
    8. C:\ProgramData\VMware\vCenterServer\cfg\vmware-vpx\vpxd.cfg (1 hit)
      Line 110: <secureSoapPort>8089</secureSoapPort>
       
    9. C:\ProgramData\VMware\vCenterServer\cfg\vmware-vpx-workflow\conf\component-manager.properties (1 hit)
      Line 4: com.vmware.vim.vcenter.extension = https://localhost:8089
       
    10. C:\Program Files\VMware\vCenter Server\vsm\conf\vsm.properties (1 hit)
      Line 21: vpxd.int.sdk-tunnel-port=8089
       
    11. Reboot vCenter Server.         

If the issue persists even after trying the preceding steps, collect the VMware Support Script Data and open a case with Broadcom Support and note this Knowledge Base article ID (318902) in the problem description.

 

Additional Information

You experience these additional symptoms:
  • In the VC system events table, you see the error:

    Event Message:'Installation of deployment unit failed, please check if ovf/vib urls are accessible, in correct format and all the properties in ovf environment have been configured in service attributes. Please check logs for details.', Module:'Security Fabric'
     
  • In the /var/log/esxupdate.log file of the affected ESXi host, you see entries similar to:

    YYYY-MM-DD TIME 30Z esxupdate: BootBankInstaller.pyc: INFO: Unrecognized value "title=Loading VMware ESXi" in boot.cfg
    YYYY-MM-DD TIME 30Z esxupdate: vmware.runcommand: INFO: runcommand called with: args = '['/sbin/bootOption', '-rp']', outfile = 'None', returnoutput = 'True', timeout = '0.0'.

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

Configuring VMware ESXi Management Network from the direct console
Verifying the VMware vCenter Server Managed IP Address
Collecting diagnostic information for VMware products
TCP and UDP Ports required to access VMware vCenter Server, VMware ESXi and ESX hosts, and other network components
Stopping, starting, or restarting the vSphere Update Manager service
ESX and ESXi host time keeping Best Practices
Required ports for VMware vCenter Server 5.5
“Agent VIB module not installed” when installing EAM/VXLAN Agent using VUM
Network port requirements for VMware NSX for vSphere 6.x
Configuring the NSX SSO Lookup Service fails

Powered by Wolken Software