While utilizing vCloud Use Meter as a provider, you might deal with a circumstance when the metering of a VMware item that you utilize varies from what you have actually prepared for. One such case might be the metering of vRealize Operations High Schedule that makes up numerous nodes– a main, reproduction, and information node.
Although Use Meter presently offers just precise metering of vRealize Operations with one node, in this article, we will cover the possible metering situations of vRealize Operations High Schedule (vROps HA) and how to fix them.
vROps HA Metering Circumstances
Circumstance 1: In this case, if you are running vROps with several nodes and 2 of the nodes (a main and reproduction) are keeping an eye on the exact same vCenter, which vCenter is included for metering in vCloud Use Meter, then this will lead to excess metering. If the vCenter Extension Supervisor has the vROps main node signed up, then the VMs of the vCenter that are kept an eye on by the main node will be found as handled. While the VMs kept an eye on by the reproduction node will be found as unmanaged.
Let’s take a look at the copying.
Example 1: Let’s utilize a vCenter Server that hosts 40 VMs. This vCenter will be kept an eye on by vROps with 2 nodes– a main and reproduction. As there is synchronization in between the nodes, they will both see the exact same variety of VMs.
Use Meter identifies VMs kept an eye on by the signed up vROps node in the vCenter Extension Supervisor, as handled. In this example, the main node will be signed up in the vCenter Extension Supervisor. As an outcome, Use Meter will report 40 VMs kept an eye on by the main node as handled, and the rest 40 VMs that are translucented the vROps reproduction node will be reported as unmanaged.
In summary, we have:
- vCenter hosts 40 VMs
- vCenter Extension Supervisor has the vROps Main Node signed up
- vROps Main Node screens 40 VMs; vROps Reproduction Node keeps track of 40 VMs
- Use Meter 4.X reports– 40 handled and 40 unmanaged VMs
Circumstance 2: Another case is vROps node tracking vCenter 1 and another vROps node tracking vCenter 2. In vCenter 1 Extension Supervisor, just the vROps Main Node will be signed up. While in vCenter 2 Extension Supervisor, it will be just the vROps Reproduction Node that is signed up. If vCenter 1 is contributed to Use Meter, then its VMs will be reported as handled, and the VMs of vCenter 2 will be reported as unmanaged. If just vCenter 2 will be included for metering in Use Meter, just its VMs will be reported as handled, while the VMs of vCenter 1 will be reported as unmanaged. If vCenter 1 and vCenter 2 are included for metering, then Use Meter will report their VMs as handled.
Let’s see an example with 2 vCenter Servers kept an eye on by vROps HA.
Example 2: For this example, we will utilize vCenter 1 with 50 VMs and vCenter 2 with 30 VMs. In vCenter 1 Extension Supervisor, we will have the vROps Main Node signed up. While in vCenter 2 Extension Supervisor, we will have the vROps Reproduction Node signed up. Use Meter identifies as handled those VMs that are kept an eye on by the vROps node signed up in the vCenter Extension Supervisor. If we include vCenter 1 to Use Meter, then 50 VMs will be reported as handled, and the 30 VMs of vCenter 2 will be reported as unmanaged. If we just include vCenter 2 to Use Meter, then 30 VMs will be reported as handled, and the 50 VMs of vCenter 1 will be reported as unmanaged. And lastly, if we include both vCenter 1 and vCenter 2, Use Meter will report as handled 80 VMs.
In summary, we have:
- vCenter 1 hosts 50 VMs; vCenter 2 hosts 30 VMs
- vCenter 1 Extension Supervisor has vROps Main Node signed up; While vCenter 2 Extension Supervisor has vROps Reproduction Node signed up
- When just vCenter 1 is contributed to Use Meter– 50 VMs reported as handled and 30 VMs as unmanaged
- If just vCenter 2 is contributed to Use Meter– 30 VMs reported as handled and 50 VMs as unmanaged
- When both vCenter 1 and vCenter 2 are contributed to Use Meter– 80 VMs reported as handled
Essential
When vROPs HA is utilized, and there is failover, the reproduction node ends up being the vROps main node. In this case, Use Meter will not find it instantly. This will trigger inaccurate metering. To resolve this, you require to include the vCenter Server once again to upgrade the vROps Main node with which it is linked. This will activate the vROPs auto-detect in Use Meter, and you will have the ideal vROps node being metered.
How D oes Use Meter Detect and Meter vROps?
Use Meter auto-discovers vRealize Operations Servers that are keeping an eye on vCenter Servers signed up with it. When a vCenter server is signed up with Use Meter, the latter inquiries the vCenter Extension Supervisor for the existence of signed up vRealize Operations servers. Each found vRealize Operations server is noted on the Item page of the Use Meter web application.
After discovery, the Use Meter administrator need to get in the qualifications needed to login to each vRealize Operations Server to finish the server registration and start metering. When Use Meter links to a vRealize Operations server, it queries a list of vCenter servers kept an eye on by vRealize Operations and the Virtual Makers kept an eye on.
vCenter servers kept an eye on by a vRealize Operations server, which are likewise signed up with Use Meter, are called handled, while vCenter servers kept an eye on by vRealize Operations however not signed up in Use Meter are called unmanaged. Both handled and unmanaged vCenter servers are noted as different lines in the regular monthly use reports.
vCloud Use Meter links to a vRealize Operations server utilizing the account supplied by the Use Meter administrator after it was instantly found. Use Meter will meter all VMs that show up through the supplied account.
How to Prevent Excess vROps HA Metering?
To prevent excess metering of vROps HA, you can do any of the following:
1. Modification your vROps to utilize a single node for keeping an eye on a single vCenter.
2. If seeing this concern prior to your regular monthly use report is sent, then on the 2 nd day of the next month, by hand report your VMs count handled by vROps in the VMware Commerce Website.
Note: You require to have an Operations function appointed to your account to send MBOs.
a. Select your MBO from your Job Inbox in VMware Commerce Website.
b. Get in the Order variety of your MBO.
c. Get in the vROPs systems utilized for the month under Use Data of your MBO.
d. Supply the factor for by hand sending your vROps systems.
e. Send the MBO.
For more in-depth details on how to send your MBO report, go to:
https://docs.vmware.com/en/VMware-Cloud-Provider-Commerce-Portal/services/Using-Commerce-Platform-Provider/GUID-4B2E382C-01C6-45A5-8D53-E030B624C00E.html
3. If your MBO is currently provided and the variety of VMs kept an eye on by vROPs in Use Meter is not fix due to having vROps HA, then you can send a removal PR by calling the VMware Global Providers Assistance Group.
Have more concerns?
Contact us at usagemeter@vmware.com.