Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

NSX preparation of a cluster fails but the VIBs install on the ESXi hosts (57304)

Last Updated: 1/23/2019Categories: TroubleshootingTotal Views: 23811Language:
English

17 like this article

Subscribe to get an email
newsletter with new updates

17 people found this helpful Please provide article feedback:

Symptoms

During initial installation of NSX 6.4.1 in a vCenter 6.7 environment, NSX may fail to fully install.  The VIBs install successfully on the ESXi hosts, but the NSX Version shows "Not Ready", VXLAN shows "Not Configured" with no option to install.  ESXi hosts show green check marks under "NSX Installation," "Firewall," and "Communication Channels."

Verification of Symptom:

Using vCenter Web Client, navigate to Home -> Administrator -> vCenter Server Extensions -> vSphere ESX Agent Manager -> Configure -> ESX Agencies

Highlight the Agency with a status of "Alert."   Under the Issue column the message reads: "The software defined by an Agency cannot be staged in VUM."

Navigate to the EAM Mob by opening a web browser and navigating to: https://vcenterserver/eam/mob

In the EAM/Mob navigate to: Agency ID -> Runtime -> issue[x]

Inside the section marked "Description" you see text similar to:

"The software defined by an Agency cannot be staged in VUM. Cause : Could not upload the following VIBs in Integrity server: [https://192.168.110.30/bin/vdn/vibs-6.4.1/6.0-8590012/vxlan.zip, https://192.168.110.30/bin/vdn/vibs-6.4.1/6.7-8590012/vxlan.zip, https://192.168.110.30/bin/vdn/vibs-6.4.1/6.5-8590012/vxlan.zip]"

Purpose

The purpose of this article is to provide a workaround to complete the initial preparation of NSX inside a cluster.

Cause

This is caused by EAM (ESX Agent Manager) being unable to push the NSX VIBs into Update Manager. In many cases, this is because VUM is configured to use a proxy Internet access.

Verify a proxy is in use by navigating to:

Home -> Hosts and Clusters -> Select a Cluster -> Update Manager  -> Go to Admin View

Under "Download Settings" view the "Proxy settings."  If a URL or IP address is configured in the Proxy field, a proxy is in use.

This error "The software defined by an Agency cannot be staged in VUM. Cause : Could not upload the following VIBs in Integrity server:" may also occur if the customer has a Windows vCenter 6.7 with Update Manager installed onto the vCenter.
If such a setup exists, see "Resolution for Windows VC + VUM" in the Resolution section.

Impact / Risks

The NSX cluster will not prepare fully.  VXLAN cannot be configured.

Resolution

Resolution for Proxy Configuration

Remove the proxy configuration.

Click Edit in "Download Settings" section of Update Manager.

Remove the check from "Use Proxy" in the Edit Proxy Settings dialog box

Navigate to Home -> Administration -> vCenter Server Extensions -> Configure -> ESX Agencies

Highlight the Agency with the Alert.

Right Click the Agency

Click "Resolve All Issues."

Resolution for Windows VC + VUM

Verify vCenter is a Windows machine

Verify Update Manager is installed, and on the vCenter itself

Hosts and Clusters -> Select the vCenter from the Navigator -> Manage -> Network Connectivity -> Update Manager settings should include "IP address or host name for the patch store" with a value of the vCenter

Log into the vCenter to check the VUM logs

cd /var/log/vmware/vmware-updatemgr/vum-server/

less vmware-vum-server-log4cpp.log

Verify these error messages in VUM

vmware-vum-server-log4cpp.log.01:[2019-01-14 13:22:17:804 'httpDownload' 2024 INFO]  [httpDownload, 577] Downloading https://VWH01MGM143.csssgatineau.reg07.rtss.qc.ca:443/eam/vib?id=9db70df5-15f1-4e90-b7b5-9ffe3f50ed02 via proxy 10.60.33.96:8080
vmware-vum-server-log4cpp.log.01:[2019-01-14 13:22:17:832 'httpDownload' 2024 ERROR]  [httpDownload, 738] Error 12175 from WinHttpSendRequest for url https://VWH01MGM143.csssgatineau.reg07.rtss.qc.ca:443/eam/vib?id=9db70df5-15f1-4e90-b7b5-9ffe3f50ed02
vmware-vum-server-log4cpp.log.01:[2019-01-14 13:22:17:832 'httpDownload' 2024 INFO]  [httpDownload, 920] Retrying https://VWH01MGM143.csssgatineau.reg07.rtss.qc.ca:443/eam/vib?id=9db70df5-15f1-4e90-b7b5-9ffe3f50ed02 with proxy off
vmware-vum-server-log4cpp.log.01:[2019-01-14 13:22:17:832 'httpDownload' 2024 INFO]  [httpDownload, 562] Downloading https://VWH01MGM143.csssgatineau.reg07.rtss.qc.ca:443/eam/vib?id=9db70df5-15f1-4e90-b7b5-9ffe3f50ed02
vmware-vum-server-log4cpp.log.01:[2019-01-14 13:22:17:836 'httpDownload' 2024 ERROR]  [httpDownload, 738] Error 12175 from WinHttpSendRequest for url https://VWH01MGM143.csssgatineau.reg07.rtss.qc.ca:443/eam/vib?id=9db70df5-15f1-4e90-b7b5-9ffe3f50ed02
vmware-vum-server-log4cpp.log.01:[2019-01-14 13:22:17:836 'httpDownload' 2024 WARN]  [httpDownload, 423] Download https://VWH01MGM143.csssgatineau.reg07.rtss.qc.ca:443/eam/vib?id=9db70df5-15f1-4e90-b7b5-9ffe3f50ed02 failed: Error 12175 from WinHttpSendRequest for url https://VWH01MGM143.csssgatineau.reg07.rtss.qc.ca:443/eam/vib?id=9db70df5-15f1-4e90-b7b5-9ffe3f50ed02
vmware-vum-server-log4cpp.log.01:[2019-01-14 13:22:17:836 'httpDownload' 2024 ERROR]  [httpDownload, 438] Reached retry download limit
vmware-vum-server-log4cpp.log.01:[2019-01-14 13:22:17:836 'DownloadMgr' 2024 ERROR]  [downloadMgr, 629] Executing download job {807237733952} throws error: Reached retry download limit
vmware-vum-server-log4cpp.log.01:[2019-01-14 13:22:17:836 'DownloadMgr' 2024 ERROR]  [downloadMgr, 718] Download failed for url: https://VWH01MGM143.csssgatineau.reg07.rtss.qc.ca:443/eam/vib?id=9db70df5-15f1-4e90-b7b5-9ffe3f50ed02

4. If these error messages are present, then the issue is due to Update Manager being unable to communicate correctly to the Windows vCenter. This is a Windows error, and the fix is a Windows registry change:
https://kb.vmware.com/s/article/2009000

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vCenter Server Appliance

VMware NSX for vSphere

Related Versions:

VMware vCenter Server Appliance 6.7.x

VMware NSX for vSphere 6.4.x

Take Our Survey

Support Assistant