When the vRealize 8 products dropped, I was like a kid in a sweet shop, upgrading everything as quick as possible before my customers tried to, so I could encounter any issues first, but also the new features, so I could show them off.
During the upgrade of vROPs, I hit an issue that my Local Admin account in vROPs had expired, but I received no warning when using the vROPs 7.5 instance and logged into the interface using the Admin account.
Before I found the issue;
During the upgrade in vRSLCM, my upgrade task failed with “vROPS upgrade failure”, Error Code: LCMVROPSYSTEM25008, Upgrade.pak_pre_apply_validate_failed.
Continue reading vRSLCM 8.0 – vROPs 7.5 upgrade fails due to Admin password expiry
A customer of mine queried the details of a metric available in vROPs “IsGreenForPlacement”
You can find this by selecting a cluster in vROPs, go to All Metrics, and just search placement.
And here is a screenshot of the Metric in a sparkline.
The customer uses this metric to give a signal (Green/Red Button on a vROPs Dashboard) if a vSphere cluster can be used for on-going deployments.
Unfortunately there’s not much documented information publicly. And we ran into an issue where the metric stayed positive (yes you can deploy), but the Storage datastore had run out of space. So I went off to dig out what this metric actually does.
IsGreenForPlacement – details
After speaking to the internal teams on vROPs I found the answer;
“Regarding IsGreenForPlacement metric, only CPU and Memory participates on calculation of this metric, by default if CPU and MEM workload is less than 80% it is green.”
So storage is not taken into account.
Creating a Dashboard
This one will be really simple. Continue reading vROPs – What is the “IsGreenForPlacement” Metric + Dashboard
I had an interesting question from a customer recently;
Can we track the adoption/upgrades of VMware tools to the latest version in a vROPs dashboard
At first, I thought sure this is easy. But then looking at the various different default options, nothing would give me a graph which shows the increasing uptake or upgrades of VMware Tools to the last version.
I consulted internally, and between myself and my customer we came up with the following solution. Which was quite simple once we thought it out.
- Create a custom group based on the information you want to capture
In the below example, I’ve done this to target VMs with VMware Tools 10.3.10, you could leave it as “10.3” to target any 10.3.X release. Continue reading Using vROPs to track adoption – Such as VMware Tools upgrades