After vCenter discovery in ESM, objects like VMs and Hypervisor are missing
search cancel

After vCenter discovery in ESM, objects like VMs and Hypervisor are missing

book

Article ID: 315762

calendar_today

Updated On:

Products

VMware Smart Assurance

Issue/Introduction

  • vCenter is discovered as host, children objects of vCenter are not discovered.
  • Credentials of vCenter is passed yet after discovery Relationship Objects are empty.

Environment

VMware Smart Assurance - SMARTS

Cause

In the debug enabled ESM domain log, below functions show failed to fetch information(empty details in {}), hence all the relationships are not created. 

It is due to user permissions issue in vCenter.

FINER: [ESMVCenterDiscovery-<Vcenter Name>] ESMDataCenter::ProcessObject hostsToClusters: {}
FINER: [ESMVCenterDiscovery-<Vcenter Name>] ESMDataCenter::ProcessObject netVDSsToDC: {}
FINER: [ESMVCenterDiscovery-<Vcenter Name>] ESMDataCenter::ProcessObject dvSwitchToName: {}
FINER: [ESMVCenterDiscovery-<Vcenter Name>] ESMDataCenter::ProcessObject hostsToCluster {}

Resolution

Read permissions for the user account should be propagated to the children (sub folders/VMs) in vCenter.