Launching soon: The world's first vendor agnostic bug scrubLearn more & join waitlist
OPERATIONAL DEFECT DATABASE
...
...
Due to a bug in the vRealize Operations Manager data processing, vRealize Operations Manager usage of managed vCenter Server may be reported as un-managed (or standalone) instead of being included in the bundle report.
This article provides steps to correctly report vROps with Usage Meter 3.6, 3.6.0.1, 3.6.1.
The issue occurs because of one of the following: In the vRealize Operations Manager User Interface, you configure a vCenter Server by using an FQDN. Then, in the vCloud Usage Meter Web App, you register the same vCenter Server instance with the same FQDN, but the letter cases in vCloud Usage Meter Web App do not match the letter cases you used in the vRealize Operations Manager User Interface. As a result, vRealize Operations Manager usage of managed vCenter Server may be reported as unmanaged. In the vRealize Operations Manager User Interface, you configure a vCenter Server by using an FQDN. Then, in the vCloud Usage Meter Web App, you register the same vCenter Server with an IP address. Or you configure a vCenter Server using an IP address in the vRealize Operations Manager User Interface. Then, in the vCloud Usage Meter Web App, you register the same vCenter Server with an FQDN. As a result, vRealize Operations Manager usage of managed vCenter Server may be reported as unmanaged.
Accurate reporting of vROps consumption.
This issue is resolved in vCloud Usage Meter 3.6.1 and a work around is provided for existing vCloud Usage Meter 3.6 and 3.6.0.1 installations.Notes: vCloud Usage Meter 3.6.1 is GA and replaces versions 3.6 and 3.6.0.1.vCloud Usage Meter versions 3.6 and 3.6.0.1 are removed from the download site.For partners and providers that are using vRealize Operations Manager, it is recommended to either migrate to vCloud Usage Meter 3.6.1 or follow the workaround.
To work around this issue:Important: The workaround is not retroactive. vROps is correctly reported only after the workaround. If you registered a vCenter Server in vCloud Usage Meter by using an IP address, update the configuration for the same vCenter Server instance in the vRealize Operations Manager User interface with the same IP address that you used in the vCloud Usage Meter Web App. Wait for the next successful collection. vCloud Usage Meter collects consumption data from vCenter Server instances on hourly basis. If you registered a vCenter Server in vCloud Usage Meter by using an FQDN, update the configuration for the same vCenter Server instance in the vRealize Operations Manager User interface with the same FQDN that you used in the vCloud Usage Meter Web App. Make sure that the letter case is one and the same in both interfaces. Wait for the next successful collection. vCloud Usage Meter collects consumption data from vCenter Server instances on hourly basis. See the following two screenshots for further reference.In the vCloud Usage Meter Web application:In the vRealize Operations Manager User Interface: Log in to vROps.Click Administration.Click Solution.Configure vSphere Adapters.