vCenter collection partially fails at SRM collection stage with error: Partial VC collections failure at stage: SRM - Name or service not known.
search cancel

vCenter collection partially fails at SRM collection stage with error: Partial VC collections failure at stage: SRM - Name or service not known.

book

Article ID: 408054

calendar_today

Updated On:

Products

VMware Usage Meter

Issue/Introduction

  • Usage Meter is unable to collect SRM data and collection fails with the error:  Partial VC collections failure at stage: SRM - Name or service not known.
  • Following entries are logged in var/log/vmware-um-platform/collection-vcenter-error.log:
    yyyy-mm-dd hh:mm:ss ERROR --- [collector-main-thread] com.vmware.um.vccollector.VCCollector : SRM stage raised exception com.vmware.um.collector.CollectionError: SRM collection failed on server <product ID> failed due to unknown error: <SRM Appliance FQDN>: Name or service not known
  • nslookup command fails for the SRM appliance's FQDN or IP address.

Environment

VCF Usage Meter 9.0.x

Cause

Due to a DNS resolution issue in the environment, Usage Meter fails to resolve SRM appliance's FQDN/IP and thereby returns Name or service not known error.

Resolution

To resolve this issue, please update the DNS in the environment with suitable entries. This will ensure that the Usage Meter appliance is able to successfully resolve the SRM appliance's Fully Qualified Domain Name (FQDN) and corresponding IP address - forward and reverse DNS lookup.
 
In the interim, the following workaround may be applied to bypass the DNS lookup by manually adding the SRM appliance's entry to the Usage Meter appliance's hosts file:

(i) Take snapshot of Usage Meter appliance.
(ii) Open the hosts file for editing using: vi /etc/hosts
(iii) Press i on the keyboard to enter Insert Mode.
(iv) Make an entry for the concerned SRM appliance in the following format at the end of file:
<IP Address> <FQDN> <Shortname>
(v) Press the Esc key to return to Normal Mode.  
(vi) Save and exit the file by typing: :wq!
(vii) Reboot the Usage Meter appliance to apply the changes: reboot -f

After performing aforementioned actions, the issue should get resolved.