On new deployments of VMware vCloud Usage Meter, sometimes the wrong vRealize Operations Instance (vROps) is propagated to Usage Meter on initial connection. Today, you cannot change or modify this vROps instance. This is frustrating for new users of Usage Meter.
Well, Usage Meter relies on the Managed Object Browser (MOB) to correlate to the connected vROps instance. In some cases, a VM Administrator may have a stale or older vROps instance still registered to the vCenter environment. For correct reporting and to remove any errors from Usage Meter, this needs to be resolved.
How do I resolve this?
Three steps to solving this:
If applicable, remove the vCenter extension/registration from vRealize Operations.
Remove the incorrect vROps instance from the vCenter MOB.
Register the correct vROps instance and synchronize the inventory in Usage Meter.
Before, any of this is done, I suggest snapshotting your vCenter and Usage Meter appliance. Don’t forget to remove the snaps post-completion!
Step 1 – If applicable, remove the vCenter extension/registration from vRealize Operations
If you have an operating vROps instance that needs to be removed/modified, let’s remove this registration from the vCenter(s).
In the vROps UI, navigate to Administration -> Solutions -> Select VMware vSphere -> click Configure (the gear wheel) and click Manage Registrations –
From there, we need to put in the credentials and click the Unregister button to complete this request.
Again, if your vROps instance is not available, skip ahead.
Step 2 – Remove the incorrect vROps instance from the vCenter MOB.
Open your browser to “https://<vCenter-FQDN>/mob/?moid=ExtensionManager” – this is the direct link to the Extension Manager section. Type in administrative credentials to log in.
Verify you see the extensionList[“com.vmware.vcops”] extension in the list. Click on it. We are going to verify that we see the incorrect vROps instance before we remove it.
From here, click on “server.” We are going to verify that the incorrect vROps instance is showing up in the extension.
Verify you see the incorrect vROps instance.
OK, press the back button twice and back to the original URL. Now we will unregister the incorrect vROps instance.
Click on the UnregisterExtension Method at the bottom –
Now you’ll get a popup requesting the extension name that we will unregister. Type in “com.vmware.vcops” in the box and press the Invoke Method button.
This may take a few seconds to run. However, you will see a void message. Close the popup and refresh the main browser tab that has the MOB information. We should see that the vcops extension has been successfully removed.
Step 3 – Register the correct vROps instance and synchronize the inventory in Usage Meter.
We are now ready to register the right vROps instance to vCenter.
Log into the vROps web console and navigate to Administration -> Solutions -> select the VMware vSphere name. You might see it collecting, but we need to register the plugin into vCenter.
Click on the wheel icon right under Solutions to open up the Configuration section. We will now click on Manage Registrations to re-register it to vCenter.
Check the box to “Use collection credentials” and click the Register button.
This might take a moment to register the plugin inside of vCenter, but a successful message will look like the following –
Going back to my vCenter MOB tab, I can now see vcops under the ExtensionManager section.
Almost complete! Hop over to the Usage Meter console and click “Synchronize All vCenter Inventories” button right under the vCenter Server section. Then, click the Rebuild button under vRealize Operations Manager.
There we go! We now see our vROps instance. Click on Edit to put in the correct credentials. Remember, you need to utilize a LOCAL vROps read-only or administrator account. AD/LDAP accounts do NOT work!
Once you put in the credentials, you will see a message stating the credentials are correct. Complete! On the next hourly run, we should see it fully activated and the “Not yet discovered” message will be removed.
Complete! Now, you’ll be able to monitor your vROps instance and bill based on the usage.
Verifying and Configuring vCloud Usage Meter Data Collection
Alright, home stretch!
Click Licenses at the top right corner – let’s verify the connected vCenter licenses are shown as VCPP. By default, they will be imported as VCPP. If you have any Perpetual licenses connected to the monitored vCenter, it is important you classify it as such. Any VCPP MUST be classified as VCPP under the licenses.
Let’s go to the Monitor tab – this shows how many collections have happened – you want to see 24 on a daily basis (1 an hour). If there’s not, there’s an issue. (Ignore my Day 10 – that’s when I changed my time from UTC to EST 🙂 ).
Now we are going to create two new Customers (think tenants) that will be part of my itemized billing. What’s great about Usage Meter is we can provide granular reporting based on tenant usage – a roll-up of how many points a Customer uses on a monthly basis. Usage Meter is not intended for customer-facing chargeback, but more for compliance between the Provider and VMware – this is a nice addition that definitely helps out the provider.
Note – if you are setting up Usage Meter for entire data center collection, Customer setup is optional. By default, Usage Meter will pull the entire environment into the Monthly Reports. The following steps can be skipped.
Customer/Rules Setup and Walkthrough
Click on the Customers link at the top right corner. By default, no customers are added by vCenter connections – however, vCloud Director will import any Orgs and assign them based on their respective org VDC (think Resource Pool) – very nice option!
I’m going to go ahead and establish a new customer called “Tenant” – click on the Add button and provide the name, Country (note to my fellow US citizens – US is fifteen down from the top, not in alphabetical order), and zip code. If you want to anonymize this customer data, click the box Restricted.
We can now see Tenant in the Customer list, but no rules or VM’s attached to it. Do you also see how now we have Active VM’s attached to the Public, T1, and T2 Customers? This is because UM detected those Org, assigned the rule, and is collecting data – slick!
OK – let’s click on Rules now on the top right corner.
Before we create a rule for Tenant, let’s check out the existing vCD rules that were automatically created. Click on Rules List –
From here, we can see how the Rule was applied – there’s an exact string applied for each Org/Customer.
Now let’s check out which VM’s are under Public – click the Customer list at the top and select Public
You can also see the list has changed – I see the only Public rule applied. From here, I can click Display Mapped Virtual Machines
Now we can see the mapped VM’s to Public – this is a great way of verifying if you rule is setup the way you want it.
Okay, back to setting up Tenant for collection. Press Back or Click on Rules at the top and select the Customer drop-down – Tenant. From here, we will be creating a rule that maps to my Management cluster for this demonstration. Remember, you can create rules that are associated with an entire Data Center, Cluster, Resource Pool, Folder, prefix, etc – many options are available.
Note – if you look at my screenshot below, I deployed Usage Meter to my Management Cluster. Where is it? 🙂 We automatically remove Usage Meter from any data collection – you do not pay for any resource usage for the UM appliance.
I selected the RegionA01-MGMT01 object and we can see the Rule Creator it automatically changed the Object Type Cluster and has a specific value. This value matches to how vCenter sees the cluster in the MOB browser. In my example, I have “domain-c71”
When you’re ready to create the rule – click Create on the Rule Creator section. Once it’s created, the Rules List sublink will blink Yellow, and let’s go ahead and click that.
Excellent, we see our new rule populated. Note – Active VM’s will not show until the next monitoring interval. By default, it runs 5 minutes past the hour.
Automatic Reporting Tab
Here’s where you can set up automatic monthly reporting to a specific email address outside of your point of contact. Currently, this DOES NOT send your usage results to VMware or the iAsset portal. You still need to input your monthly usage by the 5th of every month.
I configured where I wanted to send this when to send this – pretty straightforward.
Monthly Report Walkthrough
Let’s go ahead and click on Reports in the top right corner.
By default, the monthly reports will be emailed to the point of contact identified in the setup. There are five different reports:
Customer Monthly Usage
Horizon DaaS Tenants
Virtual Machine History
Basic functions – you can either Browse or Export the reports. Browse will show on the screen while Export will turn the report into a TSV file for you to download. The latter is the required item for compliance.
This report shows the entire aggregate of what Usage Meter sees. How many points on each bundle Usage Meter has collected, vSAN usage, VM’s by Product Server, and vCD Summary. If we had Horizon DaaS, it would show up here.
Customer Monthly Usage
This shows what each Customer uses on a monthly basis along with the respective bundle. Since we just started the collection, I don’t have any data here but we can see the Customers inside of the Monthly Usage section.
Virtual Machine History
This is a great report for getting initial estimates of what an environment could utilize in the VCPP program – this is the report that I use to provide estimates.
The VM History report shows the VM state, allocated vRAM, and then Billed vRAM – that’s where sizing estimates come into play.
This report is used for vSAN – shows usage based on vSAN storage on disk along with any features that may be applied. For example, my COMP01 cluster has DeDuplication turned on. This requires an Enterprise licensed so we see it applied.
Monthly Report Collection
Okay, let’s go ahead and export all of the reports – this is a good example of what you would send to your aggregator for monthly billing.
Click on Reports at the top and then hit the Export button for each report.
From here, we will see the reports under the Download Completed Reports
They are TSV files – so can be opened with Excel or a notepad editor. As you can see, they are all tab separated, so the data can be reviewed as such.
Note – any changes to this file will change the MD5 hash – DO NOT make any modifications!
That’s it! I realize this series was lengthy, but it’s good for our existing and up and coming providers to understand Usage Meter setup and what I’ve learned in my time working with it. More to come!
Now we are ready to log into the Usage Meter from your browser. Google Chrome is the best choice for Usage Meter.
Point your browser to https://<UM-FQDN>:8433/um
Accept the self-signed cert and continue to the login page. Type admin as your username and the password you set when we set the webpass password.
Accept the Terms and Conditions.
Before we start doing any product configuration, we need to set up the Provider and Email information.
Under the Provider tab, put in the Company/SP Name, contact email address (I usually put in the person who is responsible for UM collection), and your Partner ID and Customer Number. Site ID is for you at this time – we may use for this for future versions on multiple UM instances. Press Save when complete and it should bring you to the Email tab. Note: If you are installing Usage Meter for initial data collection and/or proposal purposes, you can put in “1234567” or “99999” for the Partner ID/Contract Number.
On the Email tab, put in your SMTP server FQDN or IP address. If it’s an open relay, it will not need a username/password. Authentication options are available.
Now press the Send email button – this will send a test email to VMware along with the individual email address you supplied on the Provider tab. If it is successful, you will receive a successful message along with an email to the specified address. As shown in the 2nd screenshot below, I can see that I received a successful test email.
Now press the Save button – from here, it will immediately bring you to the Products page.
vCenter and vRealize Operations Setup
Now we are ready to add our VMware management systems. First, let’s add our vCenter. Click the Add button right below the vCenter Server category. Do you have an external Platform Services Controller? If so, make sure you check the box and input the required info! If you are using SRM, this dropdown will be available once the secondary vCenter site is connected. When finished, press Save
OK, we can now see a message showing UM attempting to log into vCenter. If you get errors on this part, there are two possibilities: 1) wrong credentials or 2) ports are not open.
Great – we can now see a message requesting us to accept the certificates. Press Accept All.
Alright, vCenter is now showing on our list and now we see vROps was automatically detected. This is done by the MOB extension list inside of vCenter. Press Accept All to accept the certificate. The wrong vROps instance showing here? Here’s how to fix it.
Now we can see vROps in the list, but we need to update the credentials for it to activate. My vROps instance is not connected to the SSO domain, so I am going to use local admin credentials. Press the Edit button by the vROps instance and put in the credentials.
Now we can see a message stating vROps credentials are correct. Excellent. It will still show Not Yet Discovered until the next hourly collection interval – do not worry. Do check it in an hour to verify the message has been removed.
We are now complete for vCenter and vROps! If you have any other instances of vCenter, please repeat these steps. vROps cannot be added independently – it must be tied to a vCenter instance.
NSX Manager Setup
Now let’s add the NSX Manager instance. Very straightforward – hit the Add button under the NSX Manager section. Now we need to input our NSX Manager FQDN or IP, username and password (remember, NSX Manager instance credentials!) along with the connected vCenter server.
A similar message we saw from vCenter additions – accept the certificate and hit Accept All.
We will see a testing credentials message and once that disappears, NSX Manager will populate in the list. Done! Repeat these steps for any additional NSX Managers.
vCloud Director Setup
Again, very similiar steps for vCD integration – the key difference is you do need sysadmin privileges to access vCD from UM.
Click Add under the vCloud Director section and input the FQDN/IP along with the credentials.
We will see the message to accept the certificate again – hit Accept All. Once that happens, it will test the credentials and populate into the list. Done!