Monthly Archives: February 2015

Who powered off/on what VM and when in vSphere

The answer to the above question can be answered easily with Log Insight. I used the 2 built-in variables, which will ensure the log entry has user name and VM name. To filter all non power activity, I specify the string “power”. This will include both power on and power off.

Apparently, the log entry included irrelevant entry. That was easy to filter. Just click on the entry and filter the text out, like what I did below.

The result is a table showing who powered on or powered off which VM and when. You get the host, cluster, data center, vCenter also. I hide the time stamp. You can easily bring it back by clicking the Columns link. Notice I hide 11 columns, so there are other info that Log Insight can show.


I grouped the above chart by the VM Name. You can easily change it. Below is how to do it. Notice I’ve grouped it by user name. This is just a lab, as I used root a lot (not a good discipline!). I should have used proper AD name.


For more Log Insight tips, I highly recommend Steven Flander’s blog.

vRealize Operations 6.0.1 upgrade

To upgrade, click on Software Update menu on the left.The upgrade process from VMware vRealize Operations 6.0 is quite straightforward, as you can see from the Release Notes.

The first is you login to the admin console. Do this by appending /admin in the URL. You will get the screenshot below. From there, I found it relatively straight forward since I only have 1 node. This is another reason why I prefer to keep only 1 node.


To upgrade, click on Software Update menu on the left. The result is the screenshot below. From here, click on the Install a Software Update button.


This brings up the wizard below. The first step is certainly uploading the .pak file. The file size is around 1 GB, so it took a few minutes in my case. From here, it is a matter of following the wizard.


The progress reminds me of the management pack installation. Here is the update process. The State “Staged” was fast, but the second state can take a while. It took me <10 minutes in my case.


When installation finishes, the administrator interface logs me out, so I’m back to the login screen of /admin URL.

The Release Notes states that “On the main Status and Troubleshooting page of the administrator interface, the Bring Online button appears, but do not click the button. The cluster will go online automatically.”

I logged back in. In my case, it’s already starting to bring it on-line, as you can see below. The cluster status is “Going Online“. Nice! Notice the version number is already 6.0.1


The above process took several minutes. You may see the cluster is already online, but the installation showing it’s in progress. Just wait for a few minutes, and the message will disappear.


You can verify that it’s done by clicking the Software Update again. You should see something like this:


That’s it!

Migrating your WordPress blog to GoDaddy – part 2


After the migration, what you need to do is to change the nameserver. As can you see below, it’s still pointing to the old hosting provider. Mine was hosted at I was not aware of this manual change. So for months I was working on the old site!


Changing is it pretty easy. This is another example of great UI by GoDaddy. Since my domain is with GoDaddy, as I have to do is to choose Standard. No need to key in anything.


Within a few minutes, the nameserver is updated. So now this is pointing to the migrated site.


How do I know the IP address given by GoDaddy. Click on the Settings, then go to the DNS tab. Please note that this is a shared IP. You can use it for ftp purpose if you need to upload/download files.

4 This is the IP given to me by GoDaddy - it is shared

You should also verify that the Zone File has been updated. Notice the IP Address matches.

5 zone file A record

One way to test for sure is to upload an image file via WordPress editor. WordPress puts all images in a specific directory. GoDaddy provides you with the ftp userID and password. You can find it under the SSH and SFTP tab.


GoDaddy would tell you it takes up to 48 hours for DNS propagation. In general it takes much faster. In my experience it’s done within 1 hour.

7 global DNS propagation test

When you are browsing, make sure your browser and your OS do not cache the old IP. I cleared mine, and found out that my laptop still pointing to the old IP. Notice the IP address is, which is the address I have at I tried with different laptop. Same result. I bypass my homerouter and use mobile 3G, and I got it right. As you can see in the subsequent ping, it got the right address. So my home router was caching it.