I assumed you have tried, can you login vrops UI directly using the same username/pwd?
Thanks for the response. Yes I can log in without issue.
I had tried the usage meter with known functioning admin credentials without success.
I think this may be an issue with vRealize Operations 6.5. Regardless of LDAP or local account, if I run the following:
curl https://vrops-host/suite-api/api/adapters -u ‘username:password’ -H ‘Content-Type: application/json’ -H ‘Accept: application/json’ –insecure
It returns this:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><ops:error xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:ops="http://webservice.vmware.com/vRealizeOpsMgr/1.0/" httpStatusCode="401" apiErrorCode="401"><ops:message>The provided username/password or token is not valid. Please try again.</ops:message></ops:error>curl: (6)
I may need to raise a vROps support ticket for them to investigate.
I can confirm I get the same error message (API call failed, reason = 401) when using vROps 6.5 with Usage Meter 3.5. Usage Meter still shows vROps Version 6.4.0.000000 and 'not yet discovered'.
It's really difficult for us to stay secure with all the new vulnerabilities because of the dependency to Usage Meter which lacks support for newer releases of the whole SDDC stack.
Usage Meter support for other VMware products always lags behind but this is not what we as a service provider expect from you. We expect that Usage Meter always supports the newest releases in the whole VMware ecosystem. Usage Meter should never be a reason to not upgrade the whole stack.
I've been reassured by a very large CSP distributor that there is an imminent fix coming out to resolve the issues with 3.5. I'll post an update when I receive it.
that sounds good. I hope this fix is coming sooner than later!
Same here, update should be in day's not weeks...
( We have explain the issue that we have with vROps and UM. They will be waiting for a new release for UM and if this version is supported with vROps 6.5 they will use it. )
The vROps versions UM 3.5 can meter are listed in section Metering Capabilities at -
The capability to meter vROps 6.5 is on the Usage Meter roadmap.
According to the Interoperability matrix, vC Usage Meter 3.4 is compatible with vROPS 6.5, but vC Usage Meter 3.5 is unsupported with any version of vROPS!
We'd been running vC Usage Meter 3.5 for quite some time now with vROPS 6.4, no problem at all. I updated to vROPS 6.5 today and am now seeing the same error.
Guess I'll be reverting to the pre-6.5 snapshot.
Please use vROPS 6.4 . We are investigating vROPS 6.5 issues and will update soon.
Any update on this? It is now 4 months since I posted this issue.
it's unbelievable how VMware treats their Service Providers with this crappy tool! We are locked down with our upgrade planning just because of Usage Meter! Where is vCenter 6.5 support?
Are you kidding me? almost five months and still no update! In the meantime vROps 6.6 is out and it is not even mentioned on the Interoperability matrix?
I hope I can meet the product manager at VMworld, this situation is not acceptable anymore!
Thanks for posting in the Usage Meter (UM) community.
UM 3.6 can be deployed on and can meter vCenter 6.5.
The installation instructions are in topic Installing vCloud Usage Meter at -
The configuration instructions are in topic Add vCenter Server at
The vROps versions that UM 3.6 can meter are published to -
vROps 6.6 is on the list and correctly marked as incompatible.
Have a nice day,