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:

1. Using vCenter Web Client, navigate to Home -> Administrator -> vCenter Server Extensions -> vSphere ESX Agent Manager -> Configure -> ESX Agencies
2. 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."
3. Navigate to the EAM Mob by opening a web browser and navigating to: https://vcenterserver/eam/mob
4. In the EAM/Mob navigate to: Agency ID -> Runtime -> issue[x]
5. 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]"

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.

1. Home -> Hosts and Clusters -> Select a Cluster -> Update Manager  -> Go to Admin View
2. 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.

1. Remove the proxy configuration.
   1. Click Edit in "Download Settings" section of Update Manager.
   2. Remove the check from "Use Proxy" in the Edit Proxy Settings dialog box

​​​​

2. Navigate to Home -> Administration -> vCenter Server Extensions -> Configure -> ESX Agencies
3. Highlight the Agency with the Alert.
4. Right Click the Agency
5. Click "Resolve All Issues."

​​​
 

1. Verify vCenter is a Windows machine
2. Verify Update Manager is installed, and on the vCenter itself
   1. 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
3. Log into the vCenter to check the VUM logs
   1. cd /var/log/vmware/vmware-updatemgr/vum-server/
   2. less vmware-vum-server-log4cpp.log
   3. Verify these error messages in VUM