vCloud Usage Meter 4.6 | 04 OCT 2022 | Build 20554128

Check for additions and updates to these release notes.

What's New

The VMware vCloud Usage Meter 4.6 release introduces the following:

Configuration Maximums

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

Supported Browsers

The vCloud Usage Meter 4.6 Web application is compatible with the following Web browsers.

  • Google Chrome

  • Mozilla Firefox

  • Microsoft Edge

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

Windows 11

  • Google Chrome 104.0.5112.102

  • Microsoft Edge (64-bit) 104.0.1293.70

  • Mozilla Firefox 91.13.0esr

macOS Monterey 12.4

  • Google Chrome 105.0.5195.102

  • Apple Safari 15.5 (17613.2.7.1.8)

  • Mozilla Firefox (64-bit) 104.0.1

centOS 7

  • Google Chrome 105.0.5195.125

centOS 8

  • Mozilla Firefox 104.0.2

Upgrading from Previous Releases

You can install vCloud Usage Meter 4.6 as an in-place upgrade on top of vCloud Usage Meter 4.3 and later. For information, see Upgrading the vCloud Usage Meter Appliance.

If you are upgrading from vCloud Usage Meter 4.x to version 4.6, in the vCloud Usage Meter Web interface, you must manually accept the certificates for all metered product servers.

To ensure the automatic aggregation and reporting of the monthly product consumption data, after a successful upgrade from version 4.3 or later to version 4.6, VMware recommends that you do not revert to the snapshot of the source vCloud Usage Meter appliance.

Resolved Issues

  • The displayed DNS server in the vCloud Usage VAMI is wrong

    The DNS server dispayed in the vCloud Usage VAMI is wrong. The issue persists even after editing the DNS settings.

  • The Monthly Usage report contains metered data for vSAN license editions that are different from the expected ones

    For vCenter Server/vSAN versions 7.0 and above, if the vSAN cluster in a registered vCenter Server instance uses one of the Shared Witness or the Stretched Cluster features, the Monthly Usage report contains metered data for vSAN license editions that are different from the expected ones.

    Also, the number of the features associated with the cluster in the vsanFInt column of the Cluster History report is incorrect.

  • The Cluster History report does not contain the metered product consumption data for vSAN Cloud Native Storage

    If the vSAN Cloud Native Storage feature for a registered vCenter Server instance is not in a vSphere with Kubernetes/ Tanzu environment, the Cluster History report does not contain the product consumption data for the respective vSAN Cloud Native Storage.

  • After upgrading to vCloud Usage Meter 4.5, vCloud Usage Meter stops metering Site Recovery Manager

    After upgrading to vCloud Usage Meter 4.5, the metering of the registered Site Recovery Manager instance fails. The vCloud Usage Meter log files displays the following error message.

    Unknown Failure HTTP transport error: org.bouncycastle.tls.TlsFatalAlert: certificate_unknown(46) ::

Known Issues

  • New - vCloud Usage Meter still reports a deleted customer rule mapped to a VMware Cloud Director instance

    A configured and then deleted customer rule mapped to a registered VMware Cloud Director instance is is still part of the reported data by vCloud Usage Meter.

    Workaround: Execute the following steps.

    1. Add a new customer rule.

      1. On the Customer Label page, enter the same name as the name of the deleted rule.

      2. From the Product drop-down menu, select the same VMware Cloud Director endpoint as the endpoint for the deleted rule.

      3. From the Object Type drop-down menu, select Organization.

      4. From Available Objects table, select only System.

    2. Wait until the data collection for the VMware Cloud Director instance finishes successfully.

    3. Delete the newly added customer rule.

  • vCloud Usage Meter reports data for the virtual machines of a registered vCenter Server instance after migrating all the virtual machines associated with the instance

    If you migrate all the virtual machines associated with a registered vCenter Server instance to another vCenter Server instance, vCloud Usage Meter might still collect and report data for the virtual machines no longer associated with the instance.

    Workaround: After you migrate the virtual machines, delete the registered vCenter Server instance from the vCloud Usage Meter Web interface. For more information, see Delete Product Servers in vCloud Usage Meter.

  • When editing or auditing a customer rule, all objects that are part of the rule appear as Not Found

    If you delete an object from an inventory of a registered vCenter Server instance and that object is part of a customer rule, when editing or auditing the rule, all objects that are part of the rule appear as Not Found. vCloud Usage Meter displays all the selected objects with their MoRef IDs. Moreover, when auditing the rule, all the objects appear in the Missing Target Objects tab even though not all of them are deleted.

    Workaround: Edit the customer rule by manually deselecting the deleted objects from the Selected objects list.

  • vCloud Usage Meter does not send test messages to syslog servers over TCP ports despite a success message in the VAMI

    If you send a test message to a syslog host that listens to the TCP port through the vCloud Usage Meter VAMI, you receive the following success message.

    Successfully sent the test message to all syslog servers.

    However, the syslog servers do not actually receive the test message.

    Workaround: None.

  • 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 in the 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 displays vRealize Network Insight instead of VMware Aria Operations for Networks

    As a result of a rebranding, vRealize Network Insight is now VMware Aria Operations for Networks. However, in the vCloud Usage Meter Web interface, the Virtual Machine History, and the Monthly Usage reports, the name is still vRealize Network Insight. The discrepancy in the naming does not affect the metering of the registered VMware Aria Operations for Networks instances.

    Workaround: None.

  • vCloud Usage Meter displays vRealize Operations instead of VMware Aria Operations

    As a result of a rebranding, vRealize Operations is now VMware Aria Operations. However, in the vCloud Usage Meter Web interface, the Virtual Machine History, and the Monthly Usage reports, the name is still vRealize Operations.

    Workaround: None.

  • vCloud Usage Meter fails to collect the vSAN data for vCenter Server versions below 6.7 Upgrade 3

    vCloud Usage Meter fails to collect the vSAN product consumption data for vCenter Server versions below 6.7 Upgrade 3. As a result, you receive a Partial collection failure: VSAN notification in the Notifications window of vCloud Usage Meter Web interface. You also observe the following errors in the vccol_main.log/vccol_error.log file.

    ERROR --- [vCenter collector thread] c.v.u.v.vsan.VsanServiceSession : Failed to query cluster domain-xx for 
CNS volumes.
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: Unknown type (CnsVolumeManager) 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: Upgrade to vCenter Server version 6.7 Upgrade 3 or above. If you use read-only user for the vCloud Usage Meter data collection, assign the Cns Searchable permission to the user. For more information, see the following KB: vCloud Usage Meter reports vSAN partial collection error.

  • Collection of vSAN data fails when using a vCenter Server read-only user assigned only with Profile Driven storage view permissions

    vCloud Usage Meter fails to collect vSAN product consumption data when you use a vCenter Server read-only user assigned only with Profile Driven storage view permissions.

    As a result, you receive a Partial collection failure: VSAN notification in the Notifications window of vCloud Usage Meter Web interface. You also observe the following error in the vccol_main.log/vccol_error.log file.

    ERROR --- [vCenter collector thread] c.v.u.v.vsan.VsanServiceSession : Failed to query cluster domain-xx for 
CNS volumes.
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: null 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: Assign the Cns Searchable permission to the vCenter Server read-only user. For more information, see the following KB: vCloud Usage Meter reports vSAN partial collection error.

  • Collection of data for vSAN that uses the Stretched Cluster feature fails for vCenter Server versions below 7.0

    For vCenter Server versions below 7.0, if the vSAN cluster in a registered vCenter Server instance uses the Stretched Cluster feature, the vSAN collection fails.

    As a result, you receive a Partial collection failure: VSAN notification in the Notifications window of vCloud Usage Meter Web interface. You also observe the following error in the vccol_main.log/vccol_error.log file.

    [vCenter collector thread] com.vmware.um.vccollector.VCCollector : VSAN stage raised exception com.sun.xml.ws.fault.ServerSOAPFaultException: Client received SOAP Fault from server: Unable to resolve WSDL method name 
QuerySharedWitnessCompatibility for namespace name urn:vsan

    The inaccurately collected vSAN usage data affects the units in the reports.

    Workaround: None. Upgrade to vCenter Server version 7.0 or above.

  • Adding a Tanzu Kubernetes Grid management cluster deployed through Container Service Extension for metering results in a Collection Error: APIError status and notification alert

    Adding a Tanzu Kubernetes Grid management cluster deployed through Container Service Extension for metering results in a Collection Error: APIError status. You also recieve a Collection Error: APIError alert in the Notifications tab of the vCloud Usage Meter Web interface. The collection data failure occurs because vCloud Usage Meter does not support the metering of Tanzu Kubernetes Grid management clusters deployed through Container Service Extension.

    You might observe the following error in the tkgm_main.log.

    ERROR --- [TKGM collector thread] c.v.um.tkgmcollector.api.TkgmClient : GET https://ip-address/apis/infrastructure.cluster.x-k8s.io/v1beta1/vspheremachines failed for endpoint '16' with 404

    Workaround: None.

  • vCloud Usage Meter reports both the deployed and the discovered virtual machines associated with vRealize Automation 8.x

    vCloud Usage Meter reports product consumption data for both the deployed and the discovered virtual machines associated with the vRealize Automation 8.x instance which is registered through the vRealize Suite Lifecycle Manager.

    Workaround: None. Report the product consumption data only for the number of virtual machines deployed in the vRealize Automation 8.x inventory.

  • In the Virtual Machine History report, the license edition for the metered vRealize Operations instance is different than the expected one

    If the version of the metered vRealize Operations instance is 8.10 or later, vCloud Usage Meter reports the detected virtual machines against the highest vRealize Operations edition associated with the product and does not take licence groups into consideration. That might result in a different than the expected license edition for the metered vRealize Operations instance in the Virtual Machine History report.

    Workaround: If only one license is active in vRealize Operations, delete the other licenses so that vCloud Usage Meter can report the detected virtual machines against the active license. If many licenses are active, there is no workaround.

  • 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.

  • When installing vCloud Usage Meter 4.6 as an in-place upgrade, the vCloud Usage Meter VM becomes unresponsive

    When you attempt to install vCloud Usage Meter 4.6 as an in-place upgrade, the VM on which you install the new appliance, becomes unresponsive. The process might fail with an error message.

    The guest operating system has locked the CD-ROM door and is probably using the CD-ROM, which can prevent the guest from recognizing media changes.

    Workaround: Follow the steps in the https://kb.vmware.com/s/article/2144053?lang=en_us KB

  • Upgrading to vCloud Usage Meter 4.6 can result in a Failed to process journal=>read error message in the vCloud Usage Meter Web interface

    If the host name is incorrectly set when generating the self-signed certificate, upgrading to vCloud Usage Meter 4.6 results in an error message in the vCloud Usage Meter Web interface.

    Failed to process journal=>read. Error:com.vmware.um.common.err.UmException: Hostname localhost not verified: certificate: sha256/t0k44cGiczDyGyzA/xuXcP6arPXzCiYjKeLM0pNG8LU= DN: CN=photon-machine,ST=Some-State,C=US subjectAltNames: []. Check the appliance logs for more details

    Also, the Notifications page does not load.

    Workaround: Ensure that you set the correct host name. Then you can either generate a new self-signed certificate or import an internal Certification Authority (CA) - Signed Certificate. The certificate CN must match the hostname of the vCloud Usage Meter appliance. For information, see vCloud Usage Meter Certificate Management.

  • Downloading the product consumption data for a vCloud Usage Meter appliance that runs in an offline mode returns an Alert: No usage data to download error message

    If a vCloud Usage Meter appliance runs in an offline mode and contains registered product server instances, an attempt to download the product consumption report results in an error message:

    Alert: No usage data to download.

    The issue occurs when the collected product consumption data is not ready for download yet.

    Workaround: Wait for several minutes and then download the product consumption report.

  • The status of the registered NSX-V Manager instance is Credentials verified

    The Credentials verified message appears in the Status column of the registered NSX-V Manager instance.

    Workaround: None. The status changes to OK in an hour.

  • Creating a customer rule for a registered VMware Cloud Director or a vCenter Server instance before accepting the product certificates results in an Unable to process requests error message

    If the status for a registered VMware Cloud Director or a vCenter Server instance is displaying a Please Accept Certificate message and you attempt to create a customer rule for an object on the instance, you receive an error message such as:

    Unable to process requests. Error: Failed to get VCD searched objects for VMware Cloud Director.Unable to process requests. Error: Failed to get VC searched objects for vCenter Server.

    Workaround: First accept the product certificate and then create the customer rule.

  • 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.

  • Site Recovery Manager consumption data is missing from the product consumption report

    If you configure Storage Profile Protection Groups (SPPG) on a Site Revovery Manager instance, vCloud Usage Meter cannot collect product consumption data from the virtual machines associated with the SPPG. 

    Workaround: There is no workaround at this time.

  • After upgrade to vCloud Usage Meter 4.6, SSH to the vCloud Usage Meter console results in a WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! error message

    After upgrading from vCloud Usage Meter versions 4.3 or 4.4 to this release, when you SSH for the first time to the vCloud Usage Meter console, you receive an error message.

    WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! This happens because after upgrading, the vCloud Usage Meter host ID is changed in the library.

    Workaround: To delete the old host ID, run the following command.

    ssh-keygen -R <IP-of-the-UM>

check-circle-line exclamation-circle-line close-line
Scroll to top icon