This site will be decommissioned on December 31st 2024. After that date content will be available at techdocs.broadcom.com.

 

vCloud Usage Meter 4.5.0.1 | 23 MAY 2022 | Build 19821071

Check for additions and updates to these release notes.

What's New

The VMware vCloud Usage Meter 4.5.0.1 release introduces changes in the permissions of the umscheduler local user account that are necessary for automated maintenance and cleanup operations.

Configuration Maximums

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

Upgrade

You can install vCloud Usage Meter 4.5.0.1 as an in-place upgrade on top of vCloud Usage Meter 4.x. For information, see Upgrading and Migrating the vCloud Usage Meter Appliance.

If you are upgrading from vCloud Usage Meter 4.1.x to version 4.5.0.1, 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.4 or earlier to version 4.5.0.1, VMware recommends that you do not revert to the snapshot of the source vCloud Usage Meter appliance.

Resolved Issues

  • After deploying or upgrading to vCloud Usage Meter 4.5, the system stops creating the umhealth_<date>.log log files

    After deploying a new vCloud Usage Meter 4.5 appliance or upgrading to vCloud Usage Meter 4.5, the system stops running the umhealth cron jobs. As a result, the daily umhealth_<date>.log log files are missing from the opt/vmware/cloudusagemetering/var/logs/ directory.

    In vCloud Usage Meter 4.5, the local user account umscheduler runs the umhealth cron jobs. The system stops running the umhealth cron jobs, because the umscheduler account does not have sufficient privileges.

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 How do I delete product servers in vCloud Usage Meter.

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

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

  • 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: vCloud Usage Meter is unable to collect NSX Service Insertion usage.

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

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

    Workaround: None. Upgrade to vCloud Usage Meter 4.6.

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

    For vCenter Server/vSAN versions 7.0 Update 1 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 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.

    Workaround: None. Use the Partner Connect Program Product Usage Guide to calculate the usage data manually or upgrade to vCloud Usage Meter 4.6.

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

    Workaround: None. Upgrade to vCloud Usage Meter 4.6.

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

  • 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) ::

    Workaround: To workaround this issue, follow the steps in the https://kb.vmware.com/s/article/87221 KB article.

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

  • After upgrading from vCloud Usage Meter 4.1.x to version 4.5, the status for a product consumption server becomes blank

    In vCloud Usage Meter 4.1.x, if a product consumption server cannot be metered due to invalid credentials or certificate, after upgrading to vCloud Usage Meter 4.5, the status for this product consumption server becomes blank.

    Workaround: Delete the product consumption server and re-register it with vCloud Usage Meter 4.5.

  • 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.5, SSH to the vCloud Usage Meter console results in a WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! error message

    After upgrade 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