Category Archives: Products

Articles covering specific products, such as VMware vSphere, vCloud Suite, NSX, vRealize, Horizon Suite.

OYW 7.0 Lite Edition

19 April 2019 update: I received questions from customers on what happens to the Full Edition. If you are using it, then it’s forward compatible with the Lite Edition. I have not updated the Full Edition as a huge portion of customers are simply not operationally ready for Performance SLA.

The 7.0 Lite edition replaces the earlier version. You don’t need the old one anymore.

I’ve updated Operationalize Your World based on lesson learned & requirements from customers. You can find the updated here.

It also sports a simplified import steps. You can get it done in minutes. Download the files from here.

Use Admin account. The reason is we’re overwriting the default dashboards and summary pages. Since dashboards are personalized, if you do not use Admin account, it will create new dashboards instead.

  • Import the super metrics.
  • Go to you Default Policy, and enable them. Do not enable them on All Objects as you end up having super metrics for every single types of objects.
  • Import the views. Choose overwrite existing.
  • Import the dashboards. Choose overwrite existing.
  • Import the Summary Pages. Do not change your default pages yet.

Take a coffee break! Let the super metrics be calculated. To validate if they are calculated, go to Troubleshoot a Cluster dashboard.

If the dashboards are filled with data, then it’s time change your default Summary Page. To do it, follow the following screenshot:

Select Manage Summary Dashboards to bring up dialog box below
Choose the Object summary page that you want to customize. I’ve selected vSphere Cluster
Choose the replacement Summary Page. I’ve named them Summary Page for ease of identification

If you are using vSAN, then there are additional steps

  • If you are only using Hybrid or All Flash, but not both types, then simply enable the correct vSAN KPI super metrics. They are named “Ops. Hybrid vSAN KPI” and “Ops. All Flash vSAN KPI”
  • If you are using both Hybrid and All Flash, then you need to create 1 policy for each. Then enable the correct super metric for each policy.

For your convenience, I’ve disabled the Summary Pages. Reason is they are not used as dashboard.

BTW, if you notice an hour glass icon, just wait a while. I notice this can take up to 1 hour in large environment.

If you want to share the dashboards to other users, then do the dashboard sharing:

That’s all you need! In future, I will share how the Multi-Tier Application dashboard is done. This needs Group Types and Groups.

How to upgrade to vRealize Operations 7.0

This post was contributed by someone I respect for his dedication to vR Ops. Varghese Philipose, Staff TAM, Dubai, has done many upgrades. He is part of the awesome TAM team in Middle East, and they have successfully done >100 upgrades. I’ve been to Dubai several times and meet their customers. The enthusiasm from the customers on how vR Ops have helped them is the proof of the TAM team dedication.

Phase 1 : Running Pre-upgrade Assessment tool
Only for 6.6.1 or older. 6.7 does not need this.

  • Download upgrade assessment tool: vRealize Operations 7.0 – Upgrade Assessment Tool (File Type: pak, File size: 5.97 MB)
  • Launch a browser. Go to
    https://master-node-FQDN-or-IP-address/admin, where the address is the master node Administrator interface.
  • Click Software Update in the left panel.
  • Click Install a Software Update in the main panel.
  • Follow the steps in the wizard to locate and install your PAK file. Check Install the PAK file even if it is already installed.
  • Install the Upgrade Assessment Tool.
  • Wait for the software update to complete.

Note: If a cluster fails and the status changes to offline during the installation process of a PAK file update then some nodes become unavailable. To fix this, go to the Administrator interface and manually take the cluster offline and click Finish Installation to continue the installation process.

Next step is the Pre-upgrade assessment report. Follow these:

  • Navigate to the Support > Support Bundles tab.
  • Download the light support bundle that was generated from the installation of the Upgrade Assessment Tool.
  • In the downloaded support bundle, open the cluster_timestamp_nodeaddress/nodeaddress_timestamp_nodeaddress/apuat-data/report/index.html file.
  • A list of all potentially impacted user content is displayed in the Impacted Components Summary page.
  • Make the recommended changes. In most cases, you just need to replace metrics with the recommended ones.
  • If you have Management Pack that you do not use, remove it

Phase 2 : Upgrading to vRops 7.0 

Download the following upgrade files by using the download link from myvmware portal

File NameBuild#
vRealize Operations – Virtual Appliance OS upgrade10098133
vRealize Operations – Virtual Appliance upgrade10098133

  1. Make sure the root logins to all the vRops nodes are available.
  2. Make sure all the vRops nodes have sufficient disk space for upgrade ( Minimum 5% free disk space required) : Check with command “df -h” from SSH session to each node.
  3. Optional step: If you have a large vRops cluster with more than 4 nodes , the upgrade process can be made faster by pre-copying upgrade files to all nodes. Pre-copy the upgrade files to all nodes except Master Node – follow steps as in KB 2127895
  4. Take the vR Ops cluster offline from Admin UI and shut down all the nodes.
  5. Optional but highly recommended. Take the snapshot of all the nodes.
  6. Power on vR Ops nodes in the sequence starting Master Node, Replica Node, Data Nodes and Remote Collectors.
  7. Take the cluster offline, if it comes online after powering ON. This step reduces the time taken for upgrade.
  8. Initiate vR Ops Virtual Appliance OS upgrade from Admin UI. This upgrades the base SuSE Linux OS
  9. Once OS upgrade is completed , take the cluster Offline and start the Virtual Appliance upgrade.
  10. Once the upgrade is completed, verify functionality. If all functionality is reported correctly, take the cluster offline, shutdown nodes and delete the snapshots. Once snapshots are removed, power on the nodes in sequence (follow same steps in Step #6 above ).
  11. Once all nodes are powered on , bring the vRops cluster Online.

VMC Migration: Before vs After comparison

When you are migrating your customers workload to another infrastructure, the onus is on you to prove that you’re not causing problems to the VMs or Applications. This is especially true if it’s your idea to migrate, and you’re not giving them a choice.

There are many examples of migration. Popular ones are:

  • From old DC to new DC.
  • From on-prem to VMC.
  • From on-prem to Cloud. This is typically vSphere as you can simply move without changing VM.

In the above, you typically change all infrastructure. New server, new network, new storage, new vSphere. You may virtualize network by adding NSX. You may also virtualize storage by going vSAN.

Regardless, your Application Team do not and should not care. It’s transparent to them. In fact, it should be better as you’re using faster & bigger hardware. You have more CPU cores, faster RAM, faster storage, bigger network, less network hops, etc.

And that’s exactly where the problem might start 😉

A VM that takes 8 hours to complete the batch job may now take 2 hours. So it completes the same amount of work, doing as many Disk, Network, CPU, RAM in 4x shorter duration.

So what happens to the VM IOPS? Yes, it went up by 400%.

What happens to VM CPU Usage? It also went up by 400%. It has to, as it completes the same amount of logic. Suddenly, a VM that runs relatively idle at 20% becomes highly utilization 80%.

All the above is fine, if not for the next factor. Can you guess what is it?

Hint: it’s how you justify the budget to your management.

Yes, you promise higher consolidation. You have more CPU cores, more RAM, so logically you use higher over-commit ratio. As Mark said, use it carefully.

Since you have to increase overcommit ratio, how do you then prove that performance will not be affected as you drive utilization higher?

The answer is to look at what KPI can impact a VM performance. The article here provides the answer. A VM Owner looks at her VM performance, not your IaaS utilization.

The above is for a VM. It does not answer how the IaaS platform cope. This is where the Cluster KPI comes in.

With the above 2 dashboards, you can monitor and prove both the consumer layer (VM) and provider layer (Infra).