-
vCloud Usage Meter 3.6.1 not Detecting the vROPS version says vRealize Operations Not yet discovered 

 Error : Missing vCenter extension







Steps Performed : 

  • un-register the vCenter registration from the vROPS
  • Removed the com.vmware.vcops/com.vmware.vrops from the vCenter mob
  • Synchronized vCenter and rebuild- vROPS from the Usage Meter but the issue still persist 
  • Even tried to make the vROPS inactive on the UM database still no go
Verified the UM logs found that customer changed password for the vCenter service account used to connect to the UM missing permissions 


collector.log

ERROR [Collector xxxx-serv.com] vc.VCenterCollector: 
com.vmware.pbm.RuntimeFaultFaultMsg: 
ERROR [Collector xxxx-serv.com] vc.VCenterCollector:
com.vmware.pbm.RuntimeFaultFaultMsg:
ERROR [Collector 4] vrops.Vrops: Time:  Product: vRealize Operations Manager,
Hostname: 10.x.x.x, Message: Missing vCenter extension

 Resolution :

 Login in to the vSphere Web Client ,Navigate to Administration > Roles.
Click the Create role button,Type a name for the new role.
Select the following permission: Profile-driven storage > Profile-driven storage view

Assign the new role to the user which is used for vCloud Usage Meter collection.
Re-initiated the collection on the Usage Meter detected the vROPS version on the UM

Observation: Usually the vROPS is detected on the Usage Meter by the referencing vCenter plugin com.vmware.vcops/com.vmware.vrops. So if removing the plugin doesn't works its worth to check on the permissions for the vCenter user account used for the UM collection


Comments

Post a Comment

Popular posts from this blog

VAPI Endpoint service failure

-
VAPI Endpoint service failure  ERROR | state-manager1            | StsBuilder                     | Failed to acquire token for the solution user 2018-11-15T21:50:42.647Z | ERROR | state-manager1            | DefaultStateManager            | Could not initialize endpoint runtime state. com.vmware.vapi.endpoint.config.ConfigurationException: com.vmware.vim.sso.client.exception.AuthenticationFailedException: Provided credentials are not valid.         at com.vmware.vapi.endpoint.cis.StsBuilder.createToken(StsBuilder.java:182)         at com.vmware.vapi.endpoint.cis.StsBuilder.rebuild(StsBuilder.java:77)      ...
Read more

Replacing vROPS Certificates

-
Image
Issue:  When using default certificates in vROPS  Due to security requirements it was necessary to replace the default self-signed certificates with a trusted certificate signed by an internal CA. Unlike vCenter, vROPS uses a common name vc-ops-slice-1 followed by slice-2 for data and other node, where vCenter has SAN names in the default certificate so when you add the root of the local machine trusted store then the vCenter url shows secured. In order to make the secure SSL we have to generate the CSR and get it signed by any third party SSL vendors or our own Microsoft CA.  I will be generating a CSR and getting signed by internal Microsoft CA .We can refer this below article from VMware as reference.  https://kb.vmware.com/s/article/2046591?lang=en_us Steps:  1.The first step is to create a new private key from taking a SSH session to master node vROPS. openssl genrsa -out vrops.key 2048 2. Using the configuration file below make sure to provide de...
Read more

vPostgres service fails to start with Fatal error : bogus postmaster.pid

-
I came across this issue today where vPostgres service was failing on VCSA with error Fatal Error. # service-control --start vmware-vpostgres Perform start operation. vmon_profile=None, svc_names=['vmware-vpostgres'], include_coreossvcs=False, include_leafossvcs=False 2019-11-06T21:38:14.283Z   Service vmware-vpostgres state STOPPED Error executing start on service vmware-vpostgres. Details {     "resolution": null,     "detail": [         {             "args": [                 "vmware-vpostgres"             ],             "id": "install.ciscommon.service.failstart",             "localized": " A...
Read more