This is a known issue affecting NSX for vSphere 6.x
This issue is resolved in vSphere 6.0 Update 3
To work around this issue, install the VXLAN module directly on the ESXi host.
Note: Before proceeding, ensure that the bypassVumEnabled flag is set to true. This setting configures the EAM to install the vibs directly to the ESXi hosts even when the VUM is installed and/or not available.
To modify the flag and to ensure that the installation completes:
- Open a browser to the MOB at:
https://<vCenter_Server_IP>/eam/mob/
Note: If this is a new installation of vCenter Server, log in to https://vCenter_Server_IP/eam using a web browser to deploy the EAM.
- Log in with Administrator privileges.
- Select an agency from the agency list. This is usually agency-0. If not, select the appropriate agency.
Note: In VMware vCenter Server 6.0, the agencies have changed to GUID.
- Click Config. This should be a URL where agency-0 is replaced by your local agency ID.
For example:
https://<vCenter_Server_IP>/eam/mob/?moid=agency-0&doPath=config
- Verify if the bypassVumEnabled flag is set to true.
- If the value is set to true, proceed with installing the VXLAN modules and preparing the host.
- If the flag is set to false:
- Using the agency ID identified in Step 3, change the browser URL:
https://<vCenter_Server_IP>/eam/mob/?moid=agency-<0>&method=Update
- In the config field, change the existing configuration options to match this:
<config>
<bypassVumEnabled>true</bypassVumEnabled>
</config>
- Click Invoke Method. Result should match: Method Invocation Result: void
Note: Click Resolve on the Host Preparation tab in the NSX Manager UI if the agency is in a Red State.
Note: In all other cases, leave the setting as
true to allow newly installed hosts that join the cluster to work seamlessly.