Launching soon: The world's first vendor agnostic bug scrubLearn more & join waitlist
OPERATIONAL DEFECT DATABASE
...
...
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 AgenciesHighlight 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/mobIn 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]"
The purpose of this article is to provide a workaround to complete the initial preparation of NSX inside a cluster.
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 ViewUnder "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.
The NSX cluster will not prepare fully. VXLAN cannot be configured.
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 AgenciesHighlight the Agency with the Alert.Right Click the AgencyClick "Resolve All Issues." Resolution for Windows VC + VUM Verify vCenter is a Windows machineVerify 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.logVerify 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:8080vmware-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-9ffe3f50ed02vmware-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 offvmware-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-9ffe3f50ed02vmware-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-9ffe3f50ed02vmware-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-9ffe3f50ed02vmware-vum-server-log4cpp.log.01:[2019-01-14 13:22:17:836 'httpDownload' 2024 ERROR] [httpDownload, 438] Reached retry download limitvmware-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 limitvmware-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-9ffe3f50ed024. 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