times

VMware vCloud Usage Meter 4.4 | 4 MAY 2021 | Build 17956418

Check for additions and updates to these release notes.

What's in the Release Notes

The release notes cover the following topics:

What's New
Configuration Maximums
Caveats and Limitations
Supported Browsers
Upgrade
Known Issues

What's New

The VMware vCloud Usage Meter 4.4 release introduces the following new features:

Authentication against an LDAP server
Customer Labels and Rules for generating Customer Monthly Reports on vCloud Usage Insight
Offline Mode Configuration enhancements
Edition selection for Tanzu
VMware Cloud Director Availability enhancements
New in-place upgrade mode using an ISO image

For information about the compatibility of vCloud Usage Meter 4.4 and optional VMware products, see the VMware Product Interoperability Matrix.

Configuration Maximums

To view the tested scale and the VMware-recommended concurrency limits, see VMware Configuration Maximums.

Caveats and Limitations

Customer Rules

If you have configured customer rules in vCloud Usage Meter 3.6.x, after migrating to this release, the customer rules from version 3.6 cannot be migrated to version 4.4. You must manually create new customer rules in vCloud Usage Meter 4.4.

License Keys

If you have configured license keys in vCloud Usage Meter 3.6.x, after migrating to this release, the license keys from version 3.6 cannot be migrated to version 4.4. You must manually configure the license keys in vCloud Usage Meter 4.4.

Supported Browsers

The vCloud Usage Meter 4.4 Web application is compatible with the following Web browsers:

Google Chrome
Mozilla Firefox
Microsoft Edge

vCloud Usage Meter 4.4 is tested against the following Web browser versions.

Windows

Windows 10

Google Chrome 90.0.4430.72
Microsoft Edge 89.0.774.77
Mozilla Firefox 88.0

macOS

macOS Catalina 10.15.7

Google Chrome 89.0.4389.128
Mozilla Firefox 87.0
Apple Safari 14.0.3

macOS Big Sur 11.2.3

Google Chrome 90.0.4430.72
Mozilla Firefox 87.0
Apple Safari 14.0.3

Linux

Ubuntu 20.10

Google Chrome 90.0.4430.72
Mozilla Firefox 87.0

Upgrade

You can install vCloud Usage Meter 4.4 as an in-place upgrade on top of vCloud Usage Meter 4.x. For information, see In-Place upgrade of vCloud Usage Meter.
If you are upgrading from vCloud Usage Meter 4.1.x, in the vCloud Usage Meter Web interface, you must manually accept the certificates for all metered product servers.

Resolved Issues

Adding a new instance for metering in vCloud Usage Meter fails with an error message
When you add a new instance for metering in vCloud Usage Meter, the operation fails with an error message.
Certificate error for [hostname or IP address]: can not verify certificate chain

vCloud Usage Meter validates the certificate chain for each product and expects that the first certificate in the chain is issued and signed by the entity represented by the second certificate. If the certificates of the instance you are adding for metering are not in a correct order, vCloud Usage Meter cannot verify them.

Known Issues

vCloud Usage Meter fails to collect vSAN data when all ESXi hosts for a vSAN cluster are disconnected
If all ESXi hosts, which are part of a vSAN cluster, are disconnected, vCloud Usage Meter fails to collect the vSAN data in the following circumstances:
- when the vSAN cluster uses the Duplication feature
- when the vSAN cluster does not use the Duplication feature, but the version of the registered vCenter Server instance associated with the cluster is below 7.0 Update 3.
As a result, you receive a Partial collection failure: VSAN notification in the Notifications window of vCloud Usage Meter Web interface.

You might observe the following error messages vccol_main.log/vccol_error.log file.
- When the vSAN cluster uses the Duplication feature
```
ERROR --- [vCenter collector thread] com.vmware.um.vccollector.VCCollector: VSAN stage raised exception java.lang.NullPointerException java.lang.NullPointerException: null
```
- When the vSAN cluster does not use the Duplication feature, but the version of the registered vCenter Server instance associated with the cluster is below 7.0 Update 3.
```
ERROR --- [vCenter collector thread] com.vmware.um.vccollector.VCCollector    : VSAN stage raised exception com.sun.xml.ws.fault.ServerSOAPFaultException: Client received SOAP Fault from server: ‘>’ not supported between instances of ‘NoneType’ and ‘int’ Please see the server log to find more detail regarding exact cause of the failure. com.sun.xml.ws.fault.ServerSOAPFaultException: Client received SOAP Fault from server: ‘>’ not supported between instances of ‘NoneType’ and ‘int’ Please see the server log to find more detail regarding exact cause of the failure.
```
The inaccurately collected vSAN usage data affects the units in the reports.

Workaround: None. Check why all the ESXi hosts, which are part of the vSAN cluster, are disconnected.
vCloud Usage Meter does not send email notifications in case of partial collection failure for vSAN and SRM
vCloud Usage Meter does not send email notifications in case of partial collection failure for vSAN and SRM. Partial collection failure issues are displayed as error messages in the Notifications window of the vCloud Usage Meter Web interface.

Workaround: None.
The status of the metered NSX-T instance is Incomplete collection after NSX Service Insertion feature collection failure
For NSX-T versions 4.0.x, collection of the data for the NSX Service Insertion feature fails with the following error observed in /opt/vmware/cloudusagemetering/var/logs/nsxt_error.log.
```
Feature detector PacketInspectionDetector raised exception com.vmware.um.collector.UnexpectedResponseCode: API endpoint api/v1/serviceinsertion/sections on server 25 returned HTTP status 404
```
As a result, the status of the metered NSX-T instance is Incomplete collection.

Workaround: None. For more information, see the following KB: https://kb.vmware.com/s/article/89145.
New vCloud Usage Meter reports twice the product consumption for a re-registered Horizon DaaS instance
If you remove a Horizon DaaS instance from vCloud Usage Meter and re-register it again in the same month, vCloud Usage Meter reports twice the product consumption for this instance.

This happens because Horizon DaaS does not have unique ID and after every registration, the instance is assigned a new ID. As a result, vCloud Usage Meter considers the re-registered Horizon DaaS instance as a new instance.

Workaround: None. After removing a Horizon DaaS instance, if you want to re-register it in the same month, contact VMware Global Support.
New Configuring vCloud Usage Meter to use a proxy server to connect to the Internet fails with an error message
In the initial vCloud Usage Meter Web interface, if you configure the appliance to connect to the Internet by using a network proxy server that requires an authentication, the configuration fails with an error message.
Failed to connect to the proxy server: Failed to authenticate with proxy

Workaround: There is no workaround at this time.
vCloud Usage Meter cannot collect product consumption data from a registered VMware Cloud Director instance associated with a disconnected or deactivated vCenter Server instance
The product consumption data metering for a VMware Cloud Director associated with one or multiple vCenter Server instances fails if one or more of the vCenter Server instances are in a disconnected or deactivated state.

Workaround: To fix this issue, in VMware Cloud Director, you must either activate and reconnect the vCenter Server instances, or remove from VMware Cloud Director the vCenter Server instances that are in deactivated and disconnected state.
vCloud Usage Meter reports the product consumption data for a vCenter Server instance running on a Demo or Perpetual host
If you register a vCenter Server instance that is managed by VMware Cloud Foundation and running on a Demo or Perpetual host, vCloud Usage Meter reports its product consumption data for the month of the registration. vCloud Usage Meter should not report the product consumption data for Demo and Perpetual hosts.

Workaround: There is no workaround at this time.
vCloud Usage Meter cannot detect vSAN
If a vSAN enabled cluster is listed with different names in the vCenter Server inventory and the Licensing Service, vCloud Usage Meter cannot detect the vSAN and does not meter the product consumption report to VMware.

Workaround: Follow the instructions in the Usage Meter doesn't detect vSAN KB article.