vCloud Usage Meter 3.6.1 not Detecting the vROPS version says vRealize Operations Not yet discovered
Error : Missing vCenter extension
Steps Performed :
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
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
No comments:
Post a Comment