Friday, March 23, 2012

vCenter Operation Manager 5: No data reading

Credit to Edward Chew

For anyone who have used vCenter Operations Manager 5, in short vCOps most called it.  But the right abbreviation is vC Ops.

You might realize after deployment, some but not everyone will encounter this issue, the data for certain variable becomes unknown.  Slowly you have more of such no data returns.  You can reboot the vApp however this does not resolve any thing.

As seen below this is what happen to one of the environment we have.  Luckily thanks to one of my fellow colleague, Edward Chew, he raise a support to seek for a hotfix.  And yes the build version 5.0.0 build 554150 is patched with the hotfix to 5.0.0 Build 635818

After the hotfix is applied the data collection is resumed.

One of the reason this was caused:
"it has to do with how vC Ops handle an unexpected situation during collection.  Prior to the patch, if it threw an exception, it wouldn’t recover and its believe it stopped the collection process.  The patch should fix that and allow it to continue past the exception and get the rest of the data."

Update 1: vC OPs Manager 5.0.1 Build 677931 has been release today 27 Apr 2012.  I believe the no data issue should be resolved as it has a higher build level than the hotfix.

vSphere client remote console: vim.fault.invalidticket

Someone actually encountered this on their vSphere client remote screen. 

Did a check in the VMware community and found this thread.

It seems the SSL token that has an expired session still in your browser cached.

To clear the SSL cache using IE:
- Select Tools/Gear Icon (in IE 7/8/9) -> Internet Options
- Select the Content tab
- Select the Clear SSL State button

vCenter Operations Manager 5: Videos

VMware has release a series of 4 videos regarding vCenter Operations Manager (vC Ops).  It really save me lots of time understanding it on my own.  Wish this was published earlier and I won't have to go through it the tough way myself :(

However now with this video, my friends and fellow VMware practicetioner can have a good look at how well vC Ops look and feel and what information can it really deliver.

To save trying to look through all the videos and figure out which is whic, I have posted all the 4 in order here.

VMware vCenter Operations Capacity Planning & Management: Dashboard Overview

VMware vCenter Operations Capacity Planning & Management: Drilldown & Alerts

VMware vCenter Operations Capacity Planning & Management: Heatmaps & Event Management
VMware vCenter Operations Capacity Planning & Management: What-if Scenarios

Tuesday, March 13, 2012

Upgrade from vSphere 4.x to vSphere 5

Have visited several customers and everyone is on different version of vSphere 4.x update and some on vSphere 5 (that is good) and some are still in VI3.5.

Many are not considering to do further upgrade but intend to migrated directly to vSphere 5.  The good news is the upgrade can be in place upgrade by using the CD or simply use the vCenter Update Manager.

However there are some issues arised for specific versions of vSphere 4.x which need to be take care of  before doing the upgrade/migration to vSphere 5 else you might just lose the environment.

Users who are on

vSphere 4.0 Update 2:
 vSphere 4.1:

Take care if you environment contains any of the two mentioned build of vSphere 4.x, do upgrade to the next build before upgrading/migrating to vSphere 5.

Update 23 Mar 2012
For vSphere 4.0 Update 2 issues with vCenter 5.0 is been resolved in vSphere 5.0. Update 1.  This can be found in the release note on 15 Mar 2012 (3 days after my post above).

ESX 4.0 hosts with certain build numbers cannot be managed by vCenter 5.0
A purple screen of death (PSOD) may occur on hosts running ESXi 4.0 releases between Patch03 (build 219382) and Patch09 (build 360236).This occurs when the host is being managed by vCenter 5.0 in a cluster with HA enabled and VPXA agent gets reinstalled on the host e.g. if the host was removed and re-added into the vCenter inventory. With this fix, hosts are allowed to be managed by vCenter and the ESX 4.0 hosts does not PSOD.
This issue is resolved in this release.

Wednesday, March 7, 2012

vCenter Operations Manager (vC Ops) required of DRS cluster

For those who have been deploying vC Ops and have been using it in their environment, you may not have face any problem deploying the ovf vApp.

However there are some who have acquire vC Ops but facing error deploying the vApp.  This applies to mostly customer on Essential, Essential Plus or customer with a cluster without DRS enabled.  vSphere Essential and Essential Plus does not contain DRS features.

There is a KB stating this issue and the work around for those customer affected however the caveat is to lose the vApp container.  For those no aware, vC Ops manager consist of two VMs groups together in a vApp container.

VMware Odyssey™ at vForum 2019 Singapore

This year, from the success of vWarrior last year, VMware Singapore is hosting VMware Odyssey™ at #vFORUMSG Singapore. VMware Odyssey (reb...