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

VMware vCloud Usage Meter 3.6.1 Release Notes

VMware vCloud Usage Meter 3.6.1 | 18 DEC 2017 | Build 7359407

Check for additions and updates to these release notes.

What's in the Release Notes

These release notes cover the following topics:

What's New

VMware vCloud Usage Meter 3.6.1 patch release introduces improved vSAN and vRealize Operations Manager metering, improved email notifications, extended Web browser support for the vCloud Usage Meter Web application, bug fixes described in the Resolved Issues section of the current page, and documentation updates described in the Updated Information topic of the vCloud Usage Meter User's Guide.

Product Documentation

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

Supported Browsers

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

  • Google Chrome
  • Mozilla Firefox
  • Microsoft Edge
  • Microsoft Internet Explorer
  • Safari

vCloud Usage Meter 3.6.1 is tested against the following Web browser versions. You can use older versions.

Windows 10

  • Microsoft Internet Explorer 11.674.15063.0
  • Microsoft Edge 40.15063.674.0
  • Google Chrome 62.0.3202.94
  • Mozilla Firefox 56.0b3 (64-bit)

OS X Yosemite

  • Mozilla Firefox57
  • Google Chrome 62.0.3202.94
  • Safari 11.0.1 (12604.3.5.1.1)

Ubuntu 14.04.5

  • Google Chrome 48.0.2564.116
  • Mozilla Firefox 47

Upgrade 

vCloud Usage Meter 3.6.1 is installed as a new appliance. You can migrate data to vCloud Usage Meter 3.6.1 from vCloud Usage Meter 3.5.0.0, 3.6.0.0, and 3.6.0.1.

You can migrate configuration - products added for metering, customers, and rules - and metering data, and then use the new vCloud Usage Meter 3.6.1 instance to report usage for the month, in which the installation takes place.

If you are migrating from vCloud Usage Meter 3.5.0.0, you must accept the legal agreement that is displayed when you first log in to the vCloud Usage Meter Web application.

If you are migrating from vCloud Usage Meter 3.6.0.0 or 3.6.0.1 and have already accepted the legal agreement, you do not need to accept it again after you complete the migration to vCloud Usage Meter 3.6.1.

The migrateum operation exports the dbdump from the source vCloud Usage Meter and then imports it to the target instance. There are conversion processes for NSX, vSAN and vRealize Operations Manager. Exporting and importing the dbdump, and conversion processes are time-consuming operations. If your source vCloud Usage Meter instance does not have NSX, vSAN and vRealize Operations Manager added for metering, the time to complete the migration decreases. Other factors that might affect the time to complete the migration are network, virtual environment, and storage. Based on test results, the migrateum execution time varies from three minutes to ten minutes.

For more information, see Upgrading vCloud Usage Meter chapter in the vCloud Usage Meter 3.6 User's Guide.

Resolved Issues

  • If the vSAN Deduplication feature is turned on, you will see a difference between the Total Used Capacity in the vCloud Usage Meter reports and the vSAN Used - Total values in your vCenter Server Cluster

    This issue only affects vSAN versions 6.6 and 6.6.1, if the vSAN deduplication feature is turned on. For vSAN versions 6.2 and 6.5, metering is accurate even if the deduplication feature is turned on.

    This issue is fixed.

  • If you change the vRealize Operations Manager license, you cannot generate the Monthly Usage Reports for that month

    If you change the vRealize Operations Manager license from Standard or Advanced to Enterprise, or vice versa, you cannot generate the Monthly Usage Report for that month.

    This issue is fixed.

  • For vSAN 6.2, you might observe difference between the used capacity that vCloud Usage Meter 3.6.0.1 and 3.6.1 report

    In vCloud Usage Meter 3.6.0.1, vSAN used capacity is calculated based on the capacity values in the Summary tab of the vSphere Web Client. In vCloud Usage Meter 3.6.1, vSAN used capacity is calculated based on the capacity values in the Monitor > Virtual SAN > Capacity tab of the vSphere Web Client. In vSAN 6.2, there is a difference between the used capacity values on the Summary and Capacity tabs and vCloud Usage Meter 3.6.0.1 does not account for that inconsistency. This issue does not affect later vSAN versions.

    This issue is fixed.

  • vRealize Operations usage of managed vCenter Server may be reported as unmanaged

    Due to a bug in the vRealize Operations data processing, vRealize Operations usage of managed vCenter Server may be reported as unmanaged.

    This issue is fixed.

  • vCloud Usage Meter does not meter vSAN

    vCloud Usage Meter collects information for the enabled vSAN features from the associated vCenter Server and stores this information in vCloud Usage Meter. In certain occasions vCloud Usage Meter fails to read the information about used vSAN features. As a result, vCloud Usage Meter reports do not contain vSAN usage information. 

    This issue is fixed.

Known Issues

See the vCloud Usage Meter 3.6 Release Notes and vCloud Usage Meter 3.6.0.1 Release Notes for Known Issues.
  • New NSX consumption data collection fails

    vCloud Usage Meter 3.6.1 fails to collect consumption data from the NSX Manager instance with the error message:
    vCenter Server 0.0.0.0 Collection didn't finish successfully. Please check the log.

    The collector log shows timing out during NSX Manager collection.
    This can happen when in your vCloud Usage Meter 3.6.1 environment you have an NSX Manager instance with more than 1000 IP sets.

    Workaround: You must upgrade to vCloud Usage Meter Hot Patch 2.

  • New vCenter Server consumption data collection fails

    vCloud Usage Meter 3.6.1 fails to collect consumption data from vCenter Server with the error message:
    Client received SOAP Fault from server: A general system error occurred: Operation timed out Please see the server log to find more detail regarding exact cause of the failure.

    This can happen if your vCenter Server instances are in linked mode. During the consumption data collection, vCloud Usage Meter makes calls to vCenter Server and vCenter Server makes calls to the License service. As a result, the License service fails with a timeout exception.

    Workaround: You must upgrade to vCloud Usage Meter Hot Patch 2.

  • New Auto reporting or manual generation of reports in vCloud Usage Meter fails

    Generating auto reports or manual reports fails with one of the following behaviors:

    • You receive an e-mail with the subject Usage Meter at your_IP restart.
    • You receive an error message Fatal: the database system is shutting down.
    • You receive a Tomcat error log OutOfMemoryError.
    • Your vCloud Usage Meter appliance restarts on its own.
    • You might observe high memory usage or high CPU usage.

    Workaround: To work around this issue, you must upgrade to vCloud Usage Meter Hot Patch 2 or you can:

    • Increase the CPU allocation from 2 to 4
    • Increase the RAM allocation from 3 GB to 12 GB
    • Increase the Java Heap size from 256 MB to 10 GB
  • New TLS 1.0 is enabled in vCloud Usage Meter 3.6.x

    After you reboot your vCloud Usage Meter 3.6.x appliance, TLS 1.0 is automatically enabled.

    Workaround: To disable TLS 1.0, you must upgrade to vCloud Usage Meter Hot Patch 2 or you can disable VAMI by running the commands:

    1. systemctl stop vami-lighttp
    2. systemctl disable vami-lighttp
    3. systemctl mask vami-lighttp
    4. systemctl stop vami-sfcb
    5. systemctl disable vami-sfcb
    6. systemctl mask vami-sfcb​
  • You might observe incorrect high usage reports after configuring the vCloud Usage Meter 3.6.x appliance in specific time zones

    The vCloud Usage Meter reports are showing unexpected high usage values. The VM History report, the Monthly Usage report and the Customer Monthly Usage report contain duplicated usage entries for the reported period. The duplicated entries are caused by configuring the vCloud Usage Meter appliance in a time zone, which rule for Daylight-Saving Time (DST) was changed after 17th April, 2014.

    Workaround: To work around this issue, follow the resolution steps here:

    https://kb.vmware.com/s/article/55119