In vCenter 6.5 / 6.7 EAM service is unable push any VIB's due to URL to download vibs from is missing the VC FQDN or IP

Products

• VMware NSX
• VMware vCenter Server

Issue/Introduction

• NSX host prep, firewall and communication channels down and/or guest introspection in a not ready status.
• ESX Agency reports the following alert:

Unable to access agent offline bundle at https://#.#.#.#/bin/epsec/6.4.4.11051444/vibs/6.7/offlinebundle/vShield-Endpoint-Mux-6.5.0esx65-11038418.zip. Cause : <esxupdate-response> <version>1.50</version> <error errorClass="MetadataDownloadError"> <errorCode>4</errorCode> <errorDesc>Failed to download metadata.</errorDesc> <url>https://:443/eam/vib?id=<UUID></url> <localfile>None</localfile> <msg>('https://:443/eam/vib?id=<UUID>', '/tmp/tmp9om0gli3', '&lt;urlopen error [Errno -2] Name or service not known&gt;')</msg> </error> </esxupdate-response>

Cause

• Prior to vCenter Server 6.5, vCenter kept all EAM configurations in a single file called /etc/vmware-eam/eam.properties. 
• Beginning in vCenter 6.5, EAM configurations are broken into two files called /etc/vmware-eam/eam.properties and /etc/vmware-eam/eam-vim.properties.  Most of the configurations are now located in the /etc/vmware-eam/eam-vim.properties file, however with the older versions /etc/vmware-eam/eam.properties files contains all the information.
• If both files contain the same information, or if either file contains incorrect data, VUM will report duplicate information and will not populate the download URL with the correct VC host information.  This results in the cluster reporting that NSX was not properly installed.

Resolution

Workaround:

1. Log onto vCenter CLI
2. cd to /etc/vmware-eam folder
3. Confirm there is an eam-vim.properties file.
4. Make a backup of the eam.properties file.
   • cp eam.properties eam.properties_bkup
5. vi to eam.properties and clear out current file.
6. dd on each line
7. Copy the following syntax to the empty eam.properties file
   • eam.properties correct the syntax:

#########################################################################
# Copyright 2013-2017,2021 VMware, Inc. All rights reserved. VMware Confidential
#########################################################################

eam.support_linked_clone=true
eam.debug_ref_count=false
eam.mm.policy.one.by.one=false

7. Save the file
   • 'Esc' key then ':wq!' enter
8. Restart eam services
   • service-control --restart vmware-eam

Additional Information

Impact/Risks:

• This affects EAM which communicates between vCenter and NSX to install vibs for NSX-V and Guest Introspection.