NSX Agent fails to start after ESXi host upgrade to ESX 7.0U2 using HP custom ISO: VMware-ESXi-7.0.2-17867351-HPE-702.0.0.10.7.5.14-May2021-Synergy.iso

Products

• VMware NSX

Issue/Introduction

After upgrading the ESXi host from version 6.7 to 7.0, the ESXi host is unable to establish communication with the NSX Manager.

Environment

VMware NSX

Cause

HP custom VIBs HPE_bootbank_amsd_701.11.7.1.3-1OEM.701.0.0.16555998 and HPE_bootbank_amshelpr_701.11.7.0.14-1OEM.701.0.0.16555998 cause issues with NSX VIBs, breaking communication with NSX Manager.

Resolution

1. Confirm that the amsd and amshelpr VIBs exist on the host: esxcli software vib list
2. Validate if the VIB amsd, amshelpr are used by the customer
3. Remove the HP VIBs amsd and amshelpr
   1. esxcli software vib remove --vibname=amsd
      Removal Result
        Message: The update completed successfully, but the system needs to be rebooted for the changes to be effective.
        Reboot Required: true
        VIBs Installed:
        VIBs Removed: HPE_bootbank_amsd_701.11.7.1.3-1OEM.701.0.0.16555998
        VIBs Skipped:
   2. esxcli software vib remove --vibname=amshelpr
      Removal Result
        Message: The update completed successfully, but the system needs to be rebooted for the changes to be effective.
        Reboot Required: true
        VIBs Installed:
        VIBs Removed: HPE_bootbank_amshelpr_701.11.7.0.14-1OEM.701.0.0.16555998
        VIBs Skipped:
4. Reboot the ESXi host after removing the VIBs
5. Re-sync the ESXi host using the below API (Note: transport_node_id is the ID of transport nodes):
   1. POST https://<nsx-mgr>/api/v1/transport-nodes/transport_node_id?action=resync_host_config