VMware vCloud Usage Meter 184.108.40.206 | 7 SEP 2017 | Build 6552112
Check for additions and updates to these release notes.
What's in the Release Notes
These release notes cover the following topics:
VMware vCloud Usage Meter 220.127.116.11 delivers new bug fixes described in the Resolved Issues section, enhanced Web browser support described in the Supported Browsers section, and documentation updates described in the Updated Information topic in the vCloud Usage Meter 3.6 User's Guide.
The vCloud Usage Meter 18.104.22.168 Web application is compatible with the following Web browsers:
- Google Chrome
- Mozilla Firefox
- Microsoft Edge
- Microsoft Internet Explorer
vCloud Usage Meter 22.214.171.124 is tested against the following Web browser versions. You can use older versions.
- Microsoft Internet Explorer 11.1480.14393.0
- Microsoft Edge 38.14393.1066.0
- Mozilla Firefox 55.0.3 (64-bit)
- Google Chrome 60.0.3112.113
OS X Yosemite
- Mozilla Firefox 54.0.1
- Google Chrome 60.0.3112.90
- Safari 10.1.2 (12603.3.8)
- Mozilla Firefox 47.0
- Google Chrome 48.0.2564.116
In addition to the current release notes, you can use the documentation set for vCloud Usage Meter 3.6 that includes the following deliverables.
- vCloud Usage Meter 3.6 User's Guide
- Interoperability Pages for vCloud Usage Meter 3.6
- vCloud Usage Meter 3.6 API Reference
- VMware Cloud Provider Program Product Usage Guide in Partner Central at https://www.vmware.com/partners.html (login required)
vCloud Usage Meter 126.96.36.199 is installed as a new appliance. You can migrate data to vCloud Usage Meter 188.8.131.52 from vCloud Usage Meter 184.108.40.206 and 220.127.116.11.
You can migrate configuration and metering data and then use the new vCloud Usage Meter 18.104.22.168 instance to report usage for the month, in which the installation takes place.
migrateum operation exports the
dbdump from the source vCloud Usage Meter and then imports it to the target instance. There are conversion processes for NSX, vSAN and vRealize Operations Manager. Exporting and importing the
dbdump, and conversion processes are time-consuming operations. If your source vCloud Usage Meter instance does not have NSX, vSAN and vRealize Operations Manager added for metering, the time to complete the migration decreases. Other factors that might affect the time to complete the migration are network, virtual environment, and storage. Based on test results, the
migrateum execution time varies from three minutes to ten minutes.
For more information, see Upgrading vCloud Usage Meter chapter in the vCloud Usage Meter 3.6 User's Guide.
The following issues have been fixed in this release.
- Generating Monthly Usage Report fails with an error message due to an integer overflow
This issue is fixed.
The following known issues have been discovered through rigorous testing and will help you understand some behavior you might encounter in this release.
The issues in this section pertain to the vCloud Usage Meter 22.214.171.124 release.
For a list of vCloud Usage Meter 3.6 known issues, see the Known Issues section in the vCloud Usage Meter 3.6 Release Notes.
- When generating а report, you might receive an error message in the vCloud Usage Meter Web application
If the filtered report records cannot be processed within five minutes, you might receive the following error when you attempt to generate a report using the vCloud Usage Meter Web application:
Comet Component did not respond to request
Workaround: To work around this issue, generate the report again.
- If you change the vRealize Operations Manager license, you cannot generate the Monthly Usage Reports for that month
If you change the vRealize Operations Manager license from Standard or Advanced to Enterprise, or vice versa, you cannot generate the Monthly Usage Report for that month.
Workaround: To work around this issue, navigate to the Manage > Reports page in the vCloud Usage Meter Web application, and select Report vRealize Operations Enterprise usage as standalone.
NOTE: If you report vRealize Operations Enterprise usage as standalone, you cannot report the same usage in a bundle.
- For vSAN 6.2, you might observe difference between the used capacity that vCloud Usage Meter 126.96.36.199 and 3.6.1 report
In vCloud Usage Meter 188.8.131.52, vSAN used capacity is calculated based on the capacity values in the Summary tab of the vSphere Web Client. In vCloud Usage Meter 3.6.1, vSAN used capacity is calculated based on the capacity values in the Monitor > Virtual SAN > Capacity tab of the vSphere Web Client. In vSAN 6.2, there is a difference between the used capacity values on the Summary and Capacity tabs and vCloud Usage Meter 184.108.40.206 does not account for that inconsistency. This issue does not affect later vSAN versions.