The purpose of this article is to provide a workaround to complete the initial preparation of NSX inside a cluster.
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:
"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]"
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:
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.
Resolution for Proxy Configuration