VMware vCloud Usage Meter 4.2 | 21 MAY 2020 | Build 16222545
Check for additions and updates to these release notes.
What's in the Release NotesThe release notes cover the following topics:
- What's New
- Configuration Maximums
- License Keys
- Billing Model Support
- Supported Browsers
- Known Issues
UPDATED VMware vCloud Usage Meter 4.2 provides ability to designate the billable from the non-billable license keys by defining the billing category. This release introduces also additional metering capabilities for:
- VMware Cloud Foundation
- NSX-T Data Center
- vRealize Network Insight
- vCloud Availability 3.0, vCloud Availability 3.5, and VMware Cloud Director Availability 4.0
- vCloud Director 9.5.x, vCloud Director 9.7.x, vCloud Director 10.0.x, and VMware Cloud Director 10.1
- Horizon Desktop as a Service 9.0
For more information about the compatibility of vCloud Usage Meter 4.2 and optional VMware products, see the VMware Product Interoperability Matrix.
Тhe automatic monthly usage consumption data reporting from vCloud Usage Meter 4.2 to the VMware Cloud Provider Commerce Portal is available only after you register your vCloud Usage Meter 4.2 instances with Commerce Portal, and after you configure outbound HTTPS connection from your data center to vCloud Usage Insight. See Ports and Protocols required by vCloud Usage Meter.
You retain full control to manage the aggregated consumption data in the Commerce Portal prior to submission. vCloud Usage Meter 4.2 does not require to be configured with an e-mail server. Your configuration data is stored with vCloud Usage Meter 4.2, and the archive with metering data is stored on vCloud Usage Insight. For more information about vCloud Usage Insight, see vCloud Usage Insight Documentation.
To view the tested scale and the VMware-recommended concurrency limits, see VMware Configuration Maximums.
In vCloud Usage Meter 4.2 you can distinguish the billable from the non-billable license keys. The virtual machines running on hosts with billable license keys are metered and their usage consumption data is reported to the VMware Cloud Provider Commerce Portal.
Billing Model Support
vCloud Usage Meter 4.2 supports only the Flex Pricing model. The Flex Pricing model simplifies licensing with a single, core bundle and the flexibility to choose individual add-on products as needed.
The vCloud Usage Meter 4.2 Web application is compatible with the following Web browsers:
- Google Chrome
- Mozilla Firefox
- Microsoft Edge
vCloud Usage Meter 4.2 is tested against the following Web browser versions.
- Google Chrome 80.0.3987.149
- Microsoft Edge 80.0.361.69
- Mozilla Firefox 74.0
macOS High Sierra 10.13.6
- Google Chrome 80.0.3987.149
- Mozilla Firefox 69.0.2
- Safari 13.0.4
- Google Chrome 79.0.3945.130
- Mozilla Firefox 68.6.0esr
You can migrate the product configuration data from vCloud Usage Meter 3.6.x to vCloud Usage Meter 4.2. 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.2, see Upgrading vCloud Usage Meter in Installing and Configuring vCloud Usage Meter.
You can initiate the collecting of the product consumption data for the new vCenter Server instances while still retaining the metering of your existing vCenter Server instances with vCloud Usage meter 3.6.x or 4.1.x.
vCloud Usage Meter 4.2 supports an in-place upgrade from vCloud Usage Meter 4.1.x. For information, see In-Place upgrade of vCloud Usage Meter.
- You cannot deploy vCloud Usage Meter 4.2 with static IP allocation
Using vSphere Client, if you configure a static IP address during the deployment of a vCloud Usage Meter appliance on a vCenter Server 6.7 Update 1 or a later version, the vCloud Usage Meter appliance is deployed without a static IP address.
Workaround: Deploy the vCloud Usage Meter 4.2 appliance by using vSphere Web Client (a Flex-based GUI).
- vCloud Usage Meter reports a product consumption data for a vCenter Server instance running on a Demo or Perpetual host
In vCloud Usage Meter, if you add a vCenter Server instance managed by VMware Cloud Foundation, and you configure the license key for this vCenter Server as Demo or Perpetual, for the first month after the registration vCloud Usage Meter reports the vCenter Server product consumption data.
Workaround: There is no workaround at this time.
- Migration of product configuration data to vCloud Usage Meter 4.2 fails
If you migrate product configuration data from vCloud Usage Meter 3.6.1 Hot Patch 1 or Hot Patch 2 release to vCloud Usage Meter 4.2, the operation fails with an error message:
java.io.FileNotFoundException: resources/VcavServer.csv (No such file or directory”)
Workaround: To work around this issue, follow the steps.
- Log in to the source vCloud Usage Meter console as root.
- Start the SSHD service in the source vCloud Usage Meter appliance by running the following command.
service sshd start
- Log in to the target vCloud Usage Meter console as usagemeter.
- Start the SSHD service in the target vCloud Usage Meter appliance by running the following command.
su root service sshd start
- From the source vCloud Usage Meter console, execute the command.
echo "host" > /opt/vmware/cloudusagemetering/resources/VcavServer.csv
- To migrate the source product configuration data to the target vCloud Usage Meter 4.2 appliance, run the command.
Here, hostname is the TCP host name or IP address of the source vCloud Usage Meter appliance from which you are migrating the vCenter Server configuration data. The migrateum command uses SSH and Secure copy protocol to export the database and keystore files from the source system and copy it to vCloud Usage Meter 4.2.
6.1. Confirm that you want to migrate vCloud Usage Meter data.
You must enter the usgmtr password of the source vCloud Usage Meter appliance and confirm that you want to proceed with the data migration.
- In the source vCloud Usage Meter console, stop the sshd service by running the following command.
service sshd stop
- In the target vCloud Usage Meter console, disable the sshd service by running the following command.
service sshd stop