December 20th Update – this procedure works for upgrades to the newest version of Usage Meter 3.6.1. The migration process remains the same.
With our new release of vCloud Usage Meter 3.6, I have several SP’s requesting the work effort for migrating from 3.5 to 3.6 Usage Meter. I am doing this in my lab environment and showing the steps required for the data migration.
Official Instructions: https://docs.vmware.com/en/vCloud-Usage-Meter/3.6/com.vmware.vcum.usersguide.doc/GUID-88DD4D6B-B357-46D5-A6B7-AC1EDB7F423E.html
- Usage Meter 3.6 appliance stood up and IP’d – you do not need to point it to your Products (migration tool will take care of that)
- Snapshot BOTH UM appliances
- SSH turned on both 3.5 and 3.6 appliances.
- Timezone is the SAME on both appliances
- Under Manage -> Provider, ensure the Contract, Phone, Partner ID, Contract Number, and Site ID MATCH
- SSH to both appliances as “usgmtr” – NOT root – this is to test to ensure I can log in successfully to both Usage Meter appliances.
- Run “migrateum <hostname-of-UM3.5>” on the new Usage Meter appliance.
- And if you forgot to SSH as the usgmtr account, you’ll get this!! 🙂
- OK, SSH now as usgmtr on the 3.6 appliance – running “migrateum usage35.corp.local”
- IF you met the pre-reqs above, you should get a confirmation screen like this:
- After confirming, you should see the copy operation start. I didn’t have much data on my UM instance, so this was pretty quick.
- Let’s log into the 3.6 instance….
- You’ll get the confirmation page again to accept the terms:
- Accept the certificate for any product (I had vROps pop up):
- vCD was not showing up for me also – I had to check the box “Show inactive” and Activate:
- What’s great is all of my Customers and Rules moved over…
- And previous Report data is there!
Once you verify everything looks good, DON’T FORGET TO REMOVE YOUR SNAPSHOTS!!!
Not a very tough migration – just ensure your 3.6 UM is configured exactly the same way as the 3.5 instance or the migration tool will error out.
Hot off the presses here – VMware has released a new content page for go-to information for install, configuration, and management guidance.
Things to point out:
- vCenter High Availability Overview – https://vspherecentral.vmware.com/#!/vcenter-server/configuration-and-day-2-operations/vcenter-high-availability-overview
- vROps Performance and Health Monitoring Guidance – https://vspherecentral.vmware.com/#!/operations-management/performance-and-health-monitoring
- Command-Line Interfaces – https://vspherecentral.vmware.com/#!/developer-and-automation-interfaces/command-line-interfaces
This is a GREAT go-to page for core functions from a lifecycle perspective. Get this out to your teams!
This is a nice little jewel available in the VMware Solution Exchange – ability to monitor vCD objects and provide potential tenant integration for monitoring their org.
More info here: https://marketplace.vmware.com/vsx/solutions/management-pack-for-vcloud-director
To install it – it’s pretty easy:
- Download the PAK file
- Toggle to Administration -> Solutions in vROps
- Hit the + Button on Solution
- Select your PAK file and click Upload
- Accept the EULA
- Let vROps do it’s thing – installing…
- Click Finish once it’s complete.
- Now find the Management Pack for vCloud Director under Solutions. Go ahead and click on the gear icon to configure your connection.
- Add your instance along with the Display Name, org you want to connect to, and credentials. Pretty similar to other connections. Note – ensure Auto Discovery is set to “True” if you want new objects to propagate to vROps!
- Test your connection – if successful, you should start seeing Data Receiving under the Collection Status
- Toggle over to Dashboards -> you will see several new vCD dashboard available from All Metrics, vApp Utilization, Alerts, etc.
- From here, one could provide tenant access to a specific dashboard and/or org from vROps that provides a vCD view.
Yet another great addition for vROps 6.6 – definitely check it out if you are a vCD user!
Installation Guide is here.
I just upgraded my current vROps 6.4 instance to 6.6 – didn’t really know what it would take to do this.
Well, I can say this was one of the easiest updates I’ve ever done. I can summarize this in five steps.
- Download the appropriate PAK update file from vmware.com – there’s a few versions you can download. I’m running the vApp, so downloaded that.
- Log into the admin console – so https://<vrops-ui>/admin
- Click on Software Update -> Install a Software Update
- Upload the PAK file – agree to the terms
- Sit back and let it do its thing.
There’s 9 steps during the upgrade process. The admin page will time out during the appliance reboot. Once it comes up, the new GUI is evident.
Once it hits 9 of 9 – click on System Status on the left. You’ll see your applicable nodes and the current state.
I love the new interface, but also the immediate usability of 6.6. On the left side, I can see immediate recommended actions and workload balance.
Just incredible for a “minor” release.