Remediation of hosts in single image cluster failed with the error "vSphere ESX Agent Manager' service, running on 'cluster 'ClusterName" reported issue Agency ### required solutions [EMC-###] are not properly configured"
search cancel

Remediation of hosts in single image cluster failed with the error "vSphere ESX Agent Manager' service, running on 'cluster 'ClusterName" reported issue Agency ### required solutions [EMC-###] are not properly configured"

book

Article ID: 428175

calendar_today

Updated On:

Products

VMware vSphere ESXi

Issue/Introduction

  • In single image cluster remediation of hosts fails with the error "vSphere ESX Agent Manager' service, running on 'cluster 'ClusterName" reported issue Agency ### required solutions [EMC-###] are not properly configured" "Health Check for 'clusterName' failed"
  • We see below error in eam.log
    YYYY-MM-DDThh:mm:ss.863Z |  INFO | vim-inv-update | IssueHandlerBase.java | 116 | Updating issues:
    New issues:
     []
    Removed issues: [
    eam.issue.HostNotReachable {
       description = <unset>,
       time = YYYY-MM-DDThh:mm:ss,623,
       key = 49,
       agency = 'Agency:#######:null',
       agencyName = 'IoFilter-EMC_bootbank_emcsplitter',
       solutionId = 'VirtualCenter',
       solutionName = 'VirtualCenter',
       agent = 'Agent:##########:null',
       agentName = '#########',
       host = 'HostSystem:host-####:883f290e-8394-4d77-b90c-0b3e1d85cf79',
       hostName = 'hostName',
    }
    ]
    YYYY-MM-DDThh:mm:ss.863Z |  INFO | vim-inv-update | HostAgent.java | 1081 | [checkGoal:HostAgent(ID: 0e9acd9b-ac6b-47a0-a5d9-4bf1bf303e43)] has issues.
    YYYY-MM-DDThh:mm:ss.864Z |  INFO | vim-inv-update | VcEventManager.java | 792 | [EventIndex: 470] Posting event.
    YYYY-MM-DDThh:mm:ss.864Z |  INFO | vim-inv-update | IssueHandlerBase.java | 200 | Issues removed: HostAgentIssueHandler:HostAgent(ID: 0e9acd9b-ac6b-47a0-a5d9-4bf1bf303e43)
    [
    eam.issue.HostNotReachable {
       description = <unset>,
       time = 2026-02-03 06:57:33,623,
       key = 49,
       agency = 'Agency:#########:null',
       agencyName = 'IoFilter-EMC_bootbank_emcsplitter',
       solutionId = 'VirtualCenter',
       solutionName = 'VirtualCenter',
       agent = 'Agent:#######:null',
       agentName = '0e9acd9b-ac6b-47a0-a5d9-4bf1bf303e43',
       host = 'HostSystem:host-####:883f290e-8394-4d77-b90c-0b3e1d85cf79',
       hostName = 'hostName',
    }
    ]
    Location: IssueHandlerBase.java:removeIssuesByType:152
    YYYY-MM-DDThh:mm:ss.867Z |  INFO | vim-inv-update | HostAgent.java | 1081 | [checkGoal:HostAgent(ID: 0e9acd9b-ac6b-47a0-a5d9-4bf1bf303e43)] has issues.

Environment

vCenter 8.x

Cause

There is EMC_bootbank_emcsplitter present on the cluster which caused the issue as it is not part of the single image for the cluster 

Resolution

Note : Before you begin take a non memory snapshot of vCenter VM (or offline snapshot if part of ELM)

Remove the "IoFilter-EMC_bootbank_emcsplitter" using vCenter mob :

  1. Log in to the Managed Object Browser (MOB) using the URL format: https://<VC_IP>/mob.
  2. Click Content > groud-d1 (Datacenter) > datacenter-3 (<Datastore-name>) > group-h5 (host).
  3. Copy the required cluster name MOID from childEntity.
    For example: domain-c8
  4. Click Home > Content > IoFilterManager > QueryIoFilterInfo.
  5. Paste the MOID of cluster ex: domain-c8 in place of MOID and click Invoke Method, to view the installed IO Filters:
  6. Copy the id value of splitter without double quotations.
    Example: Splitter id: EMC_bootbank_emcsplitter_5330.m.169-1OEM.700.1.0.15843807
  7. Run UninstallIOFilter_Task, Home > Content > IoFilterManager > UninstallIOFilter_Task .
  8. Paste the ID of splitter or jiraf and give the MOID and click Invoke Method to run uninstallation of splitter.

Once EMC_bootbank_emcsplitter has been removed, attempt the remediation.