The EAM MOB is inaccessible when EAM loses track of the VC IP as a result of an upgrade from Windows vCenter to VCSA appliance
search cancel

The EAM MOB is inaccessible when EAM loses track of the VC IP as a result of an upgrade from Windows vCenter to VCSA appliance

book

Article ID: 330150

calendar_today

Updated On:

Products

VMware vCenter Server

Issue/Introduction

Symptoms:
  • While upgrading from Windows based 6.0 Update 2, Express Patch 7 (Build 4510822) to VCSA v6.5.0, build=8024368 = vCenter Server 6.5 Update 1g the following symptoms are noticed.
  • The EAM service seems to be locked up
  • The EAM service is not scanning and logging as expected
  • The EAM MOB is inaccessible, access to https://vCenter_Server_IP/eam/mob/ results in an HTTP Error 404
  • vCenter eam.log reports errors related to an empty vCenter Server address, like the following:
2018-09-12T13:26:20.040-07:00 | INFO | vim-monitor | MonitorImpl.java | 109 | Start polling updates ...
2018-09-12T13:26:23.006-07:00 | WARN | vim-inv-update | EamAddress.java | 234 | Ignores an empty VC address option with key VirtualCenter.AutoManagedIPV6
2018-09-12T13:26:23.007-07:00 | WARN | vim-inv-update | EamAddress.java | 234 | Ignores an empty VC address option with key VirtualCenter.ManagedIP
2018-09-12T13:26:23.008-07:00 | WARN | vim-inv-update | EamAddress.java | 234 | Ignores an empty VC address option with key VirtualCenter.AutoManagedIPV6
2018-09-12T13:26:23.008-07:00 | WARN | vim-inv-update | EamAddress.java | 234 | Ignores an empty VC address option with key VirtualCenter.ManagedIP
2018-09-12T13:26:24.745-07:00 | INFO | compute-res-domain-c2868 | ClusterVibJob.java | 219 | No hosts needs maintenance mode in compute resource: domain-c2868


Cause

An issue may occur post upgrade where the EAM thread that scan all the hosts in every NSX prepared cluster and update the status, is only serviced after the thread that is responsible for telling the EAM service the information about the vCenter Server IP address, resulting in EAM loses track of the vCenter Server IP address.

Resolution

To solve the issue upgrade to VMware vCenter Server 6.7 or update to VMware vCenter Server 6.5 Update 2d and above.

Additional Information

Impact/Risks:
Without an operational vCenter EAM service, it won't be possible to prepare or unprepare Clusters or ESXi hosts for VMware NSX.

Powered by Wolken Software