I have confirmed that vRealize Operations Manager 6.5 is compatible with Usage Meter 3.5. I am trying to add any user to the Usage Meter, but am failing.
Adding the user as username@domain I receive the following
org.springframework.http.converter.HttpMessageNotReadableException: Could not read JSON: Unable to unmarshal (to type [simple type, class java.lang.String]): Could not map [NOT_EXISTING] to ResourceState (through reference chain: com.vmware.ops.api.model.resource.ResourceDtoList["resourceList"]->com.vmware.ops.api.model.resource.ResourceDto["resourceStatusStates"]->com.vmware.ops.api.model.resource.ResourceStatusState["resourceState"]); nested exception is org.codehaus.jackson.map.JsonMappingException: Unable to unmarshal (to type [simple type, class java.lang.String]): Could not map [NOT_EXISTING] to ResourceState (through reference chain: com.vmware.ops.api.model.resource.ResourceDtoList["resourceList"]->com.vmware.ops.api.model.resource.ResourceDto["resourceStatusStates"]->com.vmware.ops.api.model.resource.ResourceStatusState["resourceState"])
Adding the user as a local user of vROps or domain\username I receive the following:
com.vmware.ops.api.client.exceptions.AuthException: API call failed, reason = 401
I've tried different permission levels, but am not getting any improvement.
I noticed that the vCenter references vROPs still as 6.4 and the Usage meter shows the below. Is this contributing to the problem?
|6.4.0.000000||VMware vRealize Operations Not yet discovered|
Thanks in advance,
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.
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.
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,
I've downloaded and installed now the vCloud Usage Meter 3.6 applicance. But we have the exact same error as before regarding to the vRealize Operations Mangager.
The Usage Meter does not recognizes the vROPS 6.5. Instead there is written "6.4.0.000000 VMware vRealize Operations Not yet discovered". And in the logs we receive regularly the error "java.util.concurrent.ExecutionException: dispatch.StatusCode: Unexpected response status: 401". So, nothing has changed.
Thanks for posting in the Usage Meter (UM) community.
Response status 401 means Unauthorized or bad authentication.
Could you please check and provide the correct vRealize Operations Manager credentials in Usage meter.
thank you for your fast response. The Usage Meter was indeed not autenticated with the vRealize Operations Manger, as we were using an Active Directory account.
Now we have changed the user to a vRealize local account and we received immediately the message "Credentials for <IP Address> are correct".
But we have still the same problem: The Usage Meter won't detect our vrops server correctly. As I've written, we are using the vRealize Operations Manager in the version 6.5. But the vCloud Usage Meter 3.6 still says "6.4.0.000000 VMware vRealize Operations Not yet discovered "
Please wait for Usage meter collection to happen (max 1 hour).
Then vRealize Operations Manager version 6.5 will get automatically updated in the Usage meter 3.6.
I changed the collection Start at minute, instead of waiting an hour. Now the Version is detected correctly.
I really appreciate your help. Sorry for my impatience.