VMware vCloud Usage Meter 4.1 | 19 SEP 2019 | Build 14668000
Check for additions and updates to these release notes.
What's in the Release NotesThe release notes cover the following topics:
- What's New
- Operational Limits
- License Keys
- Supported Browsers
- Supported Bundles
- Operating System Updates
- Known Issues
VMware vCloud Usage Meter 4.1 introduces an automated metering and reporting solution only for:
- vCenter Server
- vRealize Operations Manager
- NSX Data Center for vSphere
This solution is only available to members of VMware Cloud Provider Program. Тhe monthly usage consumption data reporting from vCloud Usage Meter 4.1 to the VMware Cloud Provider Business Portal is available only after you register your vCloud Usage Meter 4.1 instances with vCloud Usage Insight, and after you configure outbound HTTPS connection from your data center to vCloud Usage Insight. You retain full control to manage the aggregated consumption data in the VMware Cloud Provider Business Portal prior to submission. vCloud Usage Meter 4.1 does not require to be configured with an e-mail server. Your configuration data is stored with vCloud Usage Meter 4.1, and the archive with metering data is stored on vCloud Usage Insight. For more information about vCloud Usage Insight, see vCloud Usage Insight Documentation.
The following operational limits are discovered through rigorous testing of different metering operations.
- vCloud Usage Meter 4.1 can scale up to 50 vCenter Servers appliances.
- vCloud Usage Meter 4.1 supports up to 7 vCenter Server appliances in linked mode.
NSX Data Center for vSphere
vCloud Usage Meter 4.1 can scale up to 50 NSX Manager instances.
Virtual Machines per vRealize Operations Manager
vCloud Usage Meter 4.1 can scale up a single vRealize Operations Manager instance with up to 15 000 virtual machines.
Virtual Machine power events
A single vCloud Usage Meter 4.1 instance can tolerate up to 4500 changes of the power state every hour for all registered vCenter Servers.
If the total number of changes of the power events per hour is greater than 4500, you must distribute the work load by installing and configuring one or more additional vCloud Usage Meter 4.1 appliances.
vCloud Usage Meter 4.1 considers all license keys as billable. Therefore all virtual machines running on the vCenter Server you add in vCloud Usage Meter 4.1 are metered and their usage consumption data is reported to the VMware Cloud Provider Business Portal.
The vCloud Usage Meter 4.1 Web application is compatible with the following Web browsers:
- Google Chrome
- Mozilla Firefox
- Microsoft Edge
vCloud Usage Meter 4.1 is tested against the following Web browser versions. You can also use older versions.
- Google Chrome 75.0.3770.142
- Microsoft Edge 44.17763.1.0
- Mozilla Firefox 68.0.1
macOS High Sierra
- Google Chrome 76.0.3809.87
- Mozilla Firefox 68.0.2
- Safari 12.1.12
- Google Chrome 76.0.3809.100
- Mozilla Firefox 68.0.1
vCloud Usage Meter 4.1 does not support the Advanced with Networking and Advanced with Management bundles. If you are using any of these bundles with vCloud Director, do not upgrade to vCloud Usage Meter 4.1 unless instructed otherwise by VMware.
vCloud Usage Meter 4.1 is installed as a new appliance. After you install and configure the vCloud Usage Meter 4.1 appliance, you can migrate vCenter Server, NSX Manager and vRealize Operations Manager product configuration data from vCloud Usage Meter 3.6.x to vCloud Usage Meter 4.1. No other configuration information is migrated. For more information about migration of product configuration data and transfer of production workloads from vCloud Usage Meter 3.6.x to vCloud Usage Meter 4.1, see Upgrading vCloud Usage Meter in Installing and Configuring vCloud Usage Meter.
Operating System Updates
To upgrade the vCloud Usage Meter 4.1 appliance, you must install only the official vCloud Usage Meter updates provided by VMware.
- Cannot assign static address to vCloud Usage Meter 4.1 after deployment of vCloud Usage Meter 4.1 VM
After you deploy vCloud Usage Meter 4.1 with static IP on vCenter Server 6.7 Update 1 or earlier through the vSphere HTML5 Client, vCloud Usage Meter 4.1 cannot assign a static IP address.
Workaround: Deploy vCloud Usage Meter 4.1 with static IP address using Flex on vCenter Server 6.7 Update 1 or earlier, and with static IP address using HTML5 on vCenter Server 6.7 Update 2 or later.
- Deploying vCloud Usage Meter 4.1 on vCenter Server 6.5 fails when using the vSphere Client
During deployment of vCloud Usage Meter 4.1 through the vSphere Client on vCenter Server 6.5, you receive the following error messages when setting the password for the root and usagemeter accounts:
2 properties have invalid values
Password must be at most 256 characters
Workaround: Deploy the vCloud Usage Meter 4.1 appliance through the vSphere Web Client or the OVF tool.
- Cannot open de- anonymized Virtual Machine History Report
When you try to open de- anonymized Virtual Machine History Report from the same virtual machine on which the report was downloaded and de-anonymized, the process hangs.
This can happen when the size of the report causes a swap memory issue on the vCloud Usage Meter 4.1 appliance.
Workaround: To view the de-anonymized Virtual Machine History Report, follow the steps.
1. Transfer the de-anonymized report file to a secondary virtual machine.
2. Open the de-anonymized report file from the secondary virtual machine.
- Automatic discovery of vRealize Operations Manager may be delayed
Sometimes vCloud Usage Meter 4.1 fails to automatically discover vRealize Operations servers immediately, and they do not show up in vRealize Operations Manager.
Workaround: vRealize Operations servers will be automatically discovered on the next collection run, in approximately 60 minutes.
- The vCloud Usage Meter 4.1 Web interface does not display a vRealize Operations Manager that is associated with a registered vCenter Server
In vCloud Usage Meter 4.1, you add for metering a vCenter Server that is associated with a vRealize Operations Manager. When you log in to the vCloud Usage Meter 4.1 Web interface and navigate to Products > vRealize Operations Manager, the vRealize Operations Manager server that is associated with the registered vCenter Server does not appear in the list of vRealize Operations Manager instances.
Workaround: Follow the steps in the KB https://kb.vmware.com/s/article/2150394.