VMware vCloud Usage Meter 3.6.1 – End to End Deployment and Configuration (2 of 3)

Note (August 7th, 2019) – while these posts were written for, the same steps apply for 3.6.1. 

This is a continuation of the VMware vCloud Usage Meter 3.6.1 – End to End Deployment and Configuration (1 of 3)

Post 1 of 3 here 

vCloud Usage Meter Web Configuration

  1. Now we are ready to log into the Usage Meter from your browser. Google Chrome is the best choice for Usage Meter.
  2. Point your browser to https://<UM-FQDN>:8433/um 
  3. 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. 
  4. Accept the Terms and Conditions. 
  5. Before we start doing any product configuration, we need to set up the Provider and Email information.
  6. 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.
  7. 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. 
  8. 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. 
  9. Now press the Save button – from here, it will immediately bring you to the Products page. 

vCenter and vRealize Operations Setup

  1. 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
  2. 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.
  3. Great – we can now see a message requesting us to accept the certificates. Press Accept All. 
  4. 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. 
  5. 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.
  6. 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. 
  7. 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

  1. 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. 
  2. A similar message we saw from vCenter additions – accept the certificate and hit Accept All. 
  3. 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

  1. Again, very similiar steps for vCD integration – the key difference is you do need sysadmin privileges to access vCD from UM.
  2. Click Add under the vCloud Director section and input the FQDN/IP along with the credentials. 
  3. 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! 

Now, we will go ahead and set up and review Usage Meter Reporting.

VMware vCloud Usage Meter 3.6.1 – End to End Deployment and Configuration (1 of 3)

Note (August 7th, 2019) – while these posts were written for, the same steps apply for 3.6.1. 

At VMware, I get a lot of questions regarding the best way to install vCloud Usage Meter for a successful setup. This post will highlight the key points I’ve learned in my time working with the product. In a future post, I will detail how to use Usage Meter for estimating vRAM / points usage.

This Usage Meter review will be broken out into the following sections – I have split this into three posts.

  1. Key Requirements for Usage Meter
  2. vCloud Usage Meter Initial Configuration
  3. vCloud Usage Meter Web Configuration – Starts on Part 2
    1. vCenter and vROps Setup
    2. NSX Manager Setup
    3. vCloud Director Setup
  4. Verifying and Configuring vCloud Usage Meter Data Collection – Starts on Part 3
    1. Customer/Rules Setup and Walkthrough
    2. Monthly Report Walkthrough
    3. Monthly Report Collection 

Key Requirements for Usage Meter

  1. Ensure the network ports are open! Network/firewall rules are the #1 item that goes awry with a Usage Meter setup.
    1. Key Port: 443 TCP – this is used for Usage Meter -> vCenter/NSX/vCD/vROps – ensure this is open!
    2. 8443 TCP is needed inbound to access Usage Meter
    3. 443 and/or 25 outbound for SMTP emailing is required from Usage Meter
    4. All ports are in more detail here – vCloud Usage Meter TCP Port Configuration
  2. Appliance Size: 2vCPU / 3.6GB Memory / 60GB VMDK
  3. Create a fully qualified domain name and register the IP with your DNS server – just makes things easier.
  4. Have your service accounts created for the products that need to be monitored.
    1. vCenter – global read-only access (created at the top level)
    2. NSX Manager – read-only administrative privileges
    3. vCloud Director – system admin privileges
    4. vRealize Automation – read-only administrative privileges
    5. vROps – automatically discovered
  5. Create a Network Protocol Profile for the OVF deployment. This is a commonly missed step and barks about no network pools available.
    1. To set this up, browse to your Data Center -> Manage -> Network Protocol Profiles
    2. Create a new profile (or reuse one) and name it while setting what network(s) Usage Meter will sit on
    3. Under Configure IPv4 – set your subnet/CIDR, default gateway, and DNS server. I know this sounds counterintuitive, but you do not need to enable the IP Pool for manual/static configurations. I typically do not bother with IPv6. 
    4. Under Set other network configurations, I usually set the DNS domain and search path. 
  6. Deploy Usage Meter where it’s readily accessible to the monitored environments. For Providers, it usually makes sense to deploy this a management cluster that has access to resource vCenters.

vCloud Usage Meter Deployment Steps

  1. Download vCloud Usage Meter – https://my.vmware.com/en/web/vmware/info/slug/datacenter_cloud_infrastructure/vmware_vcloud_usage_meter/3_6 
  2. OK – before we start to deploy the OVA file, did you remember to establish your Network Protocol Profile??? 
  3. Let’s go ahead and deploy it to my Management Cluster – 
  4. Click Next and ensure we see vCloud Usage Meter – 
  5. Accept the EULA
  6. Provide the VM name and folder location 
  7. Select your datastore 
  8. Network setup – select the network you put in the Network Protocol Profile and select your IP Allocation method. I typically do static since I have a DNS entry established. 
  9. The final step for initial deployment – now we need to provide the root and usgmtr passwords along with the IP address of the Usage Meter appliance. Make sure you remember these passwords! 
  10. Verify everything looks good and press that Finish button…

Excellent! Now we should see vCenter deploying and creating the new Usage Meter appliance.

It will take about five minutes for it to fully initialize and start to be available on the network.

vCloud Usage Meter Initial Configuration

  1. Open up the console and ensure the FQDN/IP is available from your workspace. 
  2. Now let’s hop into the console – we are going to do two things: 1) Set the timezone and 2) set the admin account to log into the web console – this is COMPLETELY separate from the root and usgmtr accounts.
  3. Setting timezone – click into the console and press the arrow down button to select Set Timezone 
  4. Select your appropriate continent, country, and timezone. Then confirm the changes. 
  5. You will then see a message stating timezone settings have been changed and now back to the blue screen. Let’s now login – 
  6. Press enter and type in root and the password that you set at deployment. 
  7. Now type in “webpass” without the quotations. Now type in the password you would like to set for the admin account when we log into the web interface.
  8. OK! One last thing – for some reason, my hostname did not set correctly when deploying. I see localhost when it should be usage361. Let’s use this as a teachable moment when something goes awry on the network side.
  9. Type in “/opt/vmware/share/vami/vami_config_net” – this is a script we use for Usage Meter network changes to this appliance. From here, you can update the IP address, hostname, DNS, etc. DO NOT use traditional Linux commands to update network values – use this script as this updates both the system and Tomcat configurations.
  10. Alright, selecting choice 3 and typing in the correct FQDN. For a hostname change, this does require a reboot – so I’m going to press 1 to exit and reboot Usage Meter.
  11. After the reboot, my hostname is correct. 

Next, we will go over the vCloud Usage Meter Web Configuration.

vCD Extender – Warm Migration Video

This will be my last post on vCD Extender – an exciting addition to vCloud Director and wanted to provide a comprehensive look at Extender’s functionality.

Link to vCD Extender Warm Migration Setup – Part 1 of 2

Link to vCD Extender Warm Migration Setup – Part 1 of 2

Link to vCD Extender Warm Migration Demo Walkthrough

With this video, I created a new VM called WebApp3 and plan to migrate it over to the vCD Cloud environment. I’ve updated my logical demo diagram to the following:

Here’s the video I recorded – enjoy!

vCD Extender – Warm Migration Demonstration

Continuation of vCD Extender Setup – Part 1 and Part 2

Now you’re ready for your first migration. Going back to my high-level diagram, I will be migrating WebApp2 to the Provider vCD environment and ensuring connectivity is available over the VPN tunnel.

Before we start, we can see WebApp1 can ping WebApp2:

Let’s go to Migrations – Warm Migration:

Let’s select WebApp2 – remember, it must be running for a warm migration:

Selecting the defaults – I only have one network here, so it defaulted to our L2VPN network of “company-network”

Changing the Target RPO to 5 minutes (this is the fastest RPO currently) and naming the migration job “WebApp2-Migration” – this will start immediately.

Okay, now we see the job running! Depending on your network connectivity, this will take some time to replicate over the WAN.

So let’s see what happens behind the scenes.

On my provider side, I see my cloud replication instance accepting the incoming replication:

We can also see on the provider vCenter, a shell VM is substantiated and then removed from inventory. I also see some kind of SSL update to one of the hosts (I presume this is to allow direct replication):

On the tenant side, I can also see a task in here to enable and start replication of WebApp2:

While the On-Prem replication instance shows an outbound replication ID:

OK, initial replication is complete! We are now ready to cut WebApp2 over.

Back to Workloads subtab -> hit the Start Cutover button

It will prompt you for the target and you can also choose to power it on after cutover. This is handy if you had multiple VM’s that were ready for cutover, but perhaps not ready to cut them over at the same time.

Hitting the start button, you are asked one last time if you’re ready to cut over…

Alright, we are cutting over…

We can see the pings stop…

We can see WebApp2 was shut down –

I start seeing some new tasks on the provider vCenter side…

Now we also see WebApp2 pop up in vCD –

Looks like we have power on!

And now waiting a few moments for the VM to fully boot…and we have connectivity! Note that I am double nested here, so this duplicate packet behavior is something I’ve seen with VPN tunnels. 

WebApp1 can see WebApp2, let’s see if it’s the reverse! Yes, we do.

By my count, this took about 4 minutes from me pushing the button, final synchronization and having network connectivity between my two WebApp servers.

I hope to have a demo video next – enjoy setting up vCD Extender and migrating your customers to your vCD Cloud! #longlivevCD