vCloud Usage Meter is not uploading product usage data
search cancel

vCloud Usage Meter is not uploading product usage data

book

Article ID: 322769

calendar_today

Updated On:

Products

VMware Aria Suite

Issue/Introduction

Symptoms:
vCloud Usage Meter appliance is not uploading any data to vCloud Usage Insight.

Environment

VMware vCloud Usage Meter 4.x

Cause

This issue occurs if vCloud Usage Meter is not registered in the Commerce Portal

Additionally, there might be a connectivity issue with vCloud Usage Insight.

Resolution

To resolve this issue:

  1. Ensure the vCloud Usage Meter appliance is correctly registered in the VMware Commerce Portal.
  • Log in to the VMware Commerce Portal and verify if vCloud Usage Meter is present under the contact with which it has been registered.
  1. Check your vCloud Usage Meter connectivity to vCloud Usage Insight:
    1. vCloud Usage Meter must be connected to the Internet, and all supported VMware products that can be metered must have their ports open so that the appliance can connect to them. See for reference the ports of the VMware products that need to be open for vCloud Usage Meter: VMware Ports and Protocols.
    2. Enable SSH access to the vCloud Usage Meter by entering the following command  in the vCloud Usage Meter (Web or Remote) Console as root: service sshd start
    3. Log in to vCloud Usage Meter via SSH as usagemeter.
ssh usagemeter@<usage-meter-address>
 
The vCloud Usage Meter address could be its IP address or Fully Qualified Domain Name (FQDN).
  1. Test connectivity to vCloud Usage Insight by using the curl command depending on the proxy usage:
  • curl command when using a direct connection to vCloud Usage Insight:
                  curl -v https://ums.cloud.vmware.com/um/api/v1/ping
  • curl command when using proxy to connect to vCloud Usage Insight:
curl -v https://ums.cloud.vmware.com/um/api/v1/ping --proxy <proxy-address>:<proxy-port>

The proxy server address could be its IP address or Fully Qualified Domain Name (FQDN).
For every curl request, the response should be HTTP status code 200.

You should receive the following response:

"Connected to ums.cloud.vmware.com (xxx.xxx.xxx.xxx) port 443 (#0)".


In case another HTTP status code is returned, contact VMware support to investigate the issue.

Example:

curl -v https://ums.cloud.vmware.com/um/api/v1/ping --proxy app-proxy.com:80
  1. Check the vCloud Usage Meter registration status in vCloud Usage Insight by using the curl command depending on the proxy usage:
  • curl command when using a direct connection to vCloud Usage Insight:
curl -v https://ums.cloud.vmware.com/um/api/v1/upload/registration?um=<UM UUID>
  • curl command when using proxy to connect to vCloud Usage Insight:
curl -v https://ums.cloud.vmware.com/um/api/v1/upload/registration?um=<UM UUID> --proxy <proxy-address>:<proxy-port>

The proxy server address could be its IP address or Fully Qualified Domain Name (FQDN).
For every curl request, the response should be HTTP status code 200. In case another HTTP status code is returned, contact VMware support to investigate the issue.
 
Example:
 
curl -v https://ums.cloud.vmware.com/um/api/v1/upload/registration?um=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx --proxy app-proxy.com:80
  1. Log in to vCloud Usage Insight and check the vCloud Usage Meter upload status. Next to the vCloud Usage Meter name, under Status, you will also find information for the latest successful upload made from the appliance to vCloud Usage Insight.
  2. Check the Notifications tab in the vCloud Usage Meter web interface for specific details related to the detected missing uploads.
  3. Manually verify if usage data can be uploaded to vCloud Usage Insight:
    • Log in to the web interface of your vCloud Usage Meter and navigate to the Settings tab. Click SEND UPDATE TO VUI. The returned notification should be "All Data Sent Successfully".
  4. Check if archive data is uploaded or not. Go to the vCloud Usage Meter archive folder and check if .info & .zip folders are present in the archive folders like collection/notification. In case those folders are not present, contact VMware support to investigate the issue.
Examples for vCloud Usage Meter 4.2:
  • Notification folder
ls -l /opt/vmware/cloudusagemetering/var/archive/notification/0/0/2/
  • Collection folder
ls -l /opt/vmware/cloudusagemetering/var/archive/collection/0/0/1/
 
Examples for vCloud Usage Meter 4.3:
  • Notification folder
ls -l /opt/vmware/umdata/Notification/2020/11/02/
  • Collection folder
 ls -l /opt/vmware/umdata/Collection/2020/11/02/
 
Examples for vCloud Usage Meter 4.4:
  • Notification folder
ls -l /opt/vmware/umdata/Notification/2021/11/02/
  • Collection folder
 ls -l /opt/vmware/umdata/Collection/2021/11/02/



Powered by Wolken Software