Many VCSPs have faced operational issues while Reporting consumption using VMware Usage Meter
VMware Usage Meter 4.8 or above
VMware vCenter Server 7.x or above
VMware vSphere 7. x or above
VCSPs are facing key operational issues with VMware UsageMeter, impacting reporting of the right infrastructure consumption to Broadcom Systems.
Problem: UsageMeter hourly reports show #####-######-##### instead of proper license keys.
Solution: Validate vCenter Server user permissions for UsageMeter access. Ensure the user has all minimum permissions outlined in the Usage Meter documentation, including:
1. Global Licenses assigned to the credentials used with Usage Meter
2. Proper license swap permissions
Failure to set these permissions correctly can result in license swap failures and improper key display.
Problem: Billing shows unexpectedly high core consumption or overall billing amount.
Solution: Power down secondary White Label older Usage Meters. Partners participating in the White Label program should:
1. Deploy new Usage Meter appliances
2. Ensure old meters are powered down
Failure to deactivate old meters can lead to overage and inflated billing.
Problem: Unexpected invoicing or billing discrepancies.
Solution: If issues persist after addressing the above problems:
1. Raise a support ticket via support.broadcom.com
2. Share the ticket information with your Broadcom Sales team
This approach ensures that complex billing issues receive proper attention and resolution from the support team.
By addressing these common UsageMeter issues, VCSPs can improve the accuracy of their reporting and billing processes, leading to more predictable and correct invoicing.
** vCenter Permissions steps