UM 3.6.1 with VCSA 6.5U1 and VROPS 6.7 complaining about "Missing vCenter extension"

[thakala]

Hello,

We recently deployed VROPS 6.7 with VCSA 6.5U1 and we'v have beeing flooeded by error messages from UM 3.6.1 ever since.

Errors we are getting are

Usage Meter: (x.x.x.x)

Start time: 2018-06-07 09:36:00

Duration:    44 seconds

Time: 2018-06-07 09:36:20, Product: vCenter Server, Hostname: scsvcsa.smn.prod, Message:

Time: 2018-06-07 09:36:20, Product: vRealize Operations Manager, Hostname: x.x.x.x, Message: Missing vCenter extension

VCS and VROPS are both visible in UM Manage tab, both have working credentials and VROPS SSL certificate has been accepted. I have tried syncing vCenter inventory and Rebuilding VROPS list, no help, UM keeps on complaining about missing extension and VROPS status in UM Manage tab is "VMware vRealize Operations Not yet discovered".

VROPS 6.7 is to my understanding supported by UM 3.6.1.

Any pointers where to look next? I already filed an SR, still waiting to hear back.

[bsnvmw]

VCSA 6.5 U1 and vrops 6.7  is compatible with UM 3.6.1 however vrops 6.7 extension or plugin registration works only with vcenter 6.7 not less than that is what my understanding is.

If any one experienced the same can you give your inputs

[thakala]

Yep, that looks to be the case. We have vCenter Server 6.7 and VROPS 6.7 running in lab in there I can see VROPS extension on vSphere Client. But I have no idea if this is only a cosmetic issue with UM or is it really impacting usage collection.

[thakala · Accepted solution]

This problem was caused by insufficient privileges on Usage Meter vCenter Server account, it seems that Read Only role is not enough for UM when VROPS is deployed. I granted usagemeter account an Administrator role and now UM collection is finishing without warnings.

[paluszekd]

Please note that it must be a LOCAL read-only account on the vROps environment, not an Active Directory/LDAP based account. Global read only does work, but it has to be specified at the root level. If this is not the case, please do log an SR for our team to review it further. Thanks!