check-circle-line exclamation-circle-line close-line

VMware vCloud Usage Meter 3.5 Release Notes

VMware vCloud Usage Meter 3.5 | 15 SEP 2016 | Build 4359663

Last updated: 25 OCT 2017

Check for additions and updates to these release notes.

What's in the Release Notes

These release notes cover the following topics:

Interoperability Notice

vCloud Director 8.20 and vCloud Usage Meter 3.5 Interoperability Requirements

Before deploying vCloud Director 8.20 in production, you must ensure that it is configured correctly with vCloud Usage Meter. For more information, see vCloud Director 8.20 and vCloud Usage Meter 3.5.0 TLS compatibility (2149204)

What's New

  • Support for both old and new vCloud Air Network bundles. For the bundle details, see the vCAN Product Usage Guide in Partner Central at (login required).
  • VMware vSAN metering is now supported. vSAN metering is cluster-based and it is averaged over the reporting month.
  • Improved Horizon DaaS reporting. The maximum allocated quota of VDI sessions and RDSH sessions is now metered and reported. The VDI desktops used for RDSH as well as the utility and management virtual machines are excluded from metering.
  • NSX metering is now supported. For more information about the configuration options, see the Add NSX Manager topic in vCloud Usage Meter 3.5 User’s Guide.
  • The Usage Meter virtual appliance’s size is increased to support larger inventories.
  • While logging in to the vCloud Usage Meter Web Application, unless you are using LDAP, use the user name ‘admin’ instead of ‘usgmtr’.
  • Expanded interoperability support. For more information, see Interoperability Pages for vCloud Usage Meter 3.5.
  • You can receive email notifications of collection errors. For more information, see Configuring Email Settings topics in vCloud Usage Meter 3.5 User’s Guide.
  • For added security, only TLSv1.2 is enabled in Usage Meter 3.5. By default, earlier TLS versions are disabled. You cannot enable any other TLS versions. When interfacing with Usage Meter, ensure that your Web Browser supports TLSv1.2 to be able to communicate with Usage Meter.

Product Documentation

In addition to the current release notes, you can use the documentation set for vCloud Usage Meter 3.5 that includes the following deliverables.

Supported Browsers

  • Microsoft Edge 25.10586.0.0
  • Mozilla Firefox 47.0.1
  • Google Chrome 52.0.2743.116 m
  • Safari 9.0.1

If you are working with Microsoft Internet Explorer, turn off the "Compatibility view" mode, to improve the look and feel of the vCloud Usage Meter 3.5 Web Application.


vCloud Usage Meter 3.5 is installed as a new appliance. You can import configuration only (all information displayed on the Manage page only) but not measurements, from Usage Meter 3.4.0 and 3.3.3. No other configuration information is migrated. In order to migrate customer rules, first export from the existing vCloud Usage Meter and import into the vCloud Usage Meter 3.5 appliance. For more information, see Upgrading vCloud Usage Meter topic in the vCloud Usage Meter User’s Guide.

Note: The log file might contain the following error messages during the migration process, which you can ignore.

ERROR: must be owner of extension plpgsql
WARNING: no privileges could be revoked for "public”

Open Source Components

The copyright statements and licenses applicable to the open source software components distributed in vCloud Usage Meter 3.5 are available at vCloud Usage Meter Open Source Disclosure page.

Issues Fixed

  • The vRealize Operations Manager monitoring issue occurring in Usage Meter 3.4.0 due to which monitoring of more than 100 virtual machines was not supported is fixed.
  • The issue causing duplicate virtual machines to be seen in the Virtual Machine History report, when virtual machines were moved in to a new host is fixed.
  • The mismatch between data in the automatically generated email report and data in the manually generated report is corrected.
  • The problem creating the events.EventMonitor: log messages (which are, in fact, harmless) is fixed.
  • The SSL security issue is fixed.
  • The issue causing customer rules to mismatch is fixed.

Known Issues

The following known issues have been discovered through rigorous testing and will help you understand some behavior you might encounter in this release.

The known issues are grouped as follows.

Known Issues
  • Discrepancy between the total allocated quota for VDI connections in the Monthly Usage report and the Customer Monthly Usage report in Horizon DaaS

    You will see a larger value by summing up the VDI connections by all tenants than the total VDI connections in the Monthly Usage Report. This issue is caused because Horizon DaaS does not provide a way of extracting the number of desktop models that are used for RDSH session connections.

    Workaround: Enter this value manually in the ‘number of VDI Session Model’ field of the Manage > Product page. Since this is the total value and the breakdown of this value among tenants is not available, the VDI usage by tenants is reported without excluding the session models.

  • Customer Monthly Usage Report does not display deleted customer for the month

    Usage Meter does not maintain history of deleted customers.

    Workaround: If you want to customers displayed in the Virtual Machine History report, do not delete customers until the end of their last month.

  • vRealize Operations Manager issues

    • License key for version 6.0.0 is not detected by Usage Meter and displays Unexpected response status: 404 error.
    • License key number for versions 6.1 and 6.2 is displayed as 000000 on the Usage Meter Manage and Reports pages.
    • The express installation license is displayed as "NOT_LICENCED" even when the standard license is applied.

    Workaround: None.

  • DNS entries need to be added in Usage Meter appliances while adding products using Hostname

    While adding products in Usage Meter using Hostname instead of IP addresses, the DNS entries need to be added in the Usage Meter appliances. If you do not add the DNS entry, a 'UnknownHostException' is displayed when you try to add the vCenter Hostname.

    Workaround: None.

  • Site Recovery Manager collection fails after upgrading to Usage Meter 3.5

    After upgrading to vCloud Usage Meter 3.5.0 by migrating configurations from vCloud Usage Meter 3.3.3 and 3.4.0 versions, an error message may be displayed during collection.

    Workaround: To work around this issue, do the following:

    1. Go Manager > Products tab.
    2. Click Edit and Save the server(s) with the Site Recovery Manager peer.
  • Newly created virtual machine count does not increase with respect to the vRealize Automation in the vCloud Usage Meter Monthly Usage Report

    After updating vRealize Automation (version 6.2.4) self-signed certificates, the newly added virtual machines are not included.

    Workaround: Reboot the vRealize Automation in the following order:

    1. vRealize Automation Cafe Appliance
    2. vRealize Automation IAAS Server
  • NSX Manager Server gets deleted on entering incorrect Password

    After successfully adding NSX Manager server, if you enter an incorrect Password while editing it, the NSX Manager gets deleted.

    Workaround: To reactivate the server, provide the correct credentials.

  • When executing exit command in the console in single user mode to reboot the vCloud Usage Meter appliance you might receive “Kernel panic – Not syncing : Attempted to kill init!” Error

    Workaround: Reset the vCloud Usage Meter appliance by going to the console menu VM > Power > Reset.

  • Site Recovery Manager issues:
    • Site Recovery Manager collections fail with fault.drextapi.fault.NoPermission.summary error.
    • Site Recovery Manager does not appear correctly on the Manage > Products page.

    Both issues indicate Site Recovery Manager login is not properly configured.

    Workaround: If you are using SSO, see for more information about resolving SSO pairing issues.

    If you are affected by the issue without using SSO, verify that the Site Recovery Manager is configured properly. For more information, see Site Recovery Manager Installation and Configuration in the VMware vCenter Site Recovery Manager Documentation Center.

  • Usage Meter 3.5 does not meter VMware products that are out of general support.

    Workaround: Use UM 3.3.3 to meter all products that are out of general support and work to move to supported products.

  • Usage Meter 3.5 reports Starter Bundle.

    Workaround: If you see Starter Bundle on your monthly usage report, report as Standard Bundle.

  • After upgrading products that vCloud Usage Meter 3.5 is metering, if the upgrade includes a certificate update, the upgraded products disappear from the Manage > Products page and go into inactive state in the Web Application.

    Workaround: To work around this issue, do the following:

    1. In the vCloud Usage Meter Web application, go to the Products page.
    2. Select Show Inactive in the product section for the affected product.
    3. Click Edit for the inactive product.
    4. Activate the product by clicking Save.
    5. Click Accept to accept the new license.

  • vCenter Server with a non-billable license gets metered

    Workaround: When adding a vCenter Server that is using demo or perpetual license in the vCloud Usage Meter Web Application, make sure that you update the license information accordingly within an hour of adding the product, to avoid this vCenter Server to get metered and charged. By default, vCenter Servers are added with VCAN (charging) license and the grace period to update the license to the correct type is one hour.

  • vCloud Usage Meter 3.5 cannot connect to products that have TLS 1.0 disabled by default

    Workaround: To work around this issue, upgrade to the latest version of vCloud Usage Meter or enable TLS 1.0 on the product that you want to meter with vCloud Usage Meter 3.5. For more information about product versions that have TLS 1.0 disabled by default, see Status of TLSv1.1/1.2 Enablement and TLSv1.0 Disablement across VMware products (2145796). For more information about enabling TLS 1.0, see the product documentation for the affected product version.