Migrating from vCloud Usage Meter 3.5 to 3.6

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

Pre-requisites:

  1. 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)
  2. Snapshot BOTH UM appliances
  3. SSH turned on both 3.5 and 3.6 appliances.
  4. Timezone is the SAME on both appliances
  5. Under Manage -> Provider, ensure the Contract, Phone, Partner ID, Contract Number, and Site ID MATCH

Steps:

  1. SSH to both appliances as “usgmtr” – NOT root – this is to test to ensure I can log in successfully to both Usage Meter appliances.
  2. Run “migrateum <hostname-of-UM3.5>” on the new Usage Meter appliance.
  3. And if you forgot to SSH as the usgmtr account, you’ll get this!! 🙂
  4. OK, SSH now as usgmtr on the 3.6 appliance – running “migrateum usage35.corp.local”
  5. IF you met the pre-reqs above, you should get a confirmation screen like this:
  6. After confirming, you should see the copy operation start. I didn’t have much data on my UM instance, so this was pretty quick.
  7. Let’s log into the 3.6 instance….
  8. You’ll get the confirmation page again to accept the terms:
  9. Accept the certificate for any product (I had vROps pop up):
  10. vCD was not showing up for me also – I had to check the box “Show inactive” and Activate:
  11. What’s great is all of my Customers and Rules moved over…
  12. 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.

Happy migrating!

vSphere Central – Go-To Bible for core functions!

Hot off the presses here – VMware has released a new content page for go-to information for install, configuration, and management guidance.

https://vspherecentral.vmware.com

Things to point out:

  1. vCenter High Availability Overview – https://vspherecentral.vmware.com/#!/vcenter-server/configuration-and-day-2-operations/vcenter-high-availability-overview
  2. vROps Performance and Health Monitoring Guidance – https://vspherecentral.vmware.com/#!/operations-management/performance-and-health-monitoring
  3. 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!

vROps Management Pack for vCloud Director

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:

  1. Download the PAK file
  2. Toggle to Administration -> Solutions in vROps
  3. Hit the + Button on Solution
  4. Select your PAK file and click Upload
  5.  
  6. Accept the EULA
  7. Let vROps do it’s thing – installing…
  8. Click Finish once it’s complete.
  9. Now find the Management Pack for vCloud Director under Solutions. Go ahead and click on the gear icon to configure your connection.
  10. 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!
  11. Test your connection – if successful, you should start seeing Data Receiving under the Collection Status
  12. Toggle over to Dashboards -> you will see several new vCD dashboard available from All Metrics, vApp Utilization, Alerts, etc.
  13. 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.

vROps 6.6 Upgrade – Easiest. Upgrade. Ever.

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.

  1. 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.
  2. Log into the admin console – so https://<vrops-ui>/admin
  3. Click on Software Update -> Install a Software Update
  4. Upload the PAK file – agree to the terms
  5. 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.