EAM VIB URL points to incorrect vCenter Server name or IP

Products

• VMware NSX

Issue/Introduction

Symptoms:

• Installing NSX components or deploying Guest introspection fails with this error:
  please check if ovf/vibs are accessible.
   
• URL points to incorrect IP address or FQDN of vCenter server.
   
• In the esxupdate.log file, you see entries similar to:
  
  2016-12-06T00:39:38Z esxupdate: esxupdate: ERROR: MetadataDownloadError: ('https://10.3.1.51:443/eam/vib?id=0b7c9ebc-be83-4053-ba4f-255abb02787c', None, "('https://10.3.1.51:443/eam/vib?id=0b7c9ebc-be83-4053-ba4f-255abb02787c', '/tmp/tmpZh1_RO', '[Errno 12] Timeout: <urlopen error timed out>')")
  2016-12-06T00:39:38Z esxupdate: esxupdate: DEBUG: <<<
  
  Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Environment

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

Cause

This issue occurs if the runtime settings in the vCenter Server points to an old or incorrect vCenter FQDN or IP of vCenter Server.

Resolution

To resolve this issue, update the runtime settings in the vSphere Web Client:

1. Log in to vSphere Web Client.
2. Navigate to vCenter Server instance > Manage.
3. Under Settings, select General.
4. In the Edit vCenter Server Settings dialog box, select Runtime Settings.
5. In the vCenter Server managed address field, enter the correct vCenter Server IP Address.
6. In the vCenter Server name field, enter the correct FQDN of the vCenter Server system.
7. Click OK.