Command to Retrieve Physical Switch Name and Port Numbers to which a particular ESXi host vmnics are connected

vim-cmd hostsvc/net/query_networkhint  | grep -i [Dp][eo][vr][It] |grep -v Capa | grep -v connected

Output format would be:

device = "vmnicX",
         devId = "SwitchName",
         portId = "GigabitEthernetX/Y"

Utility to export ESXi support bundle using web browser

New feature in ESXi5, you can invoke the export log utility via http:

From a web browser browse to https://username:password@ESXHostnameOrIPAddress/cgi-bin/vmsupport.cgi

This will automatically start downloading the support bundle named vm-support.tgz

VMware VirtualCenter Operational Dashboard to view vpxd profiler metrics

We can use VirtualCenter Operational Dashboard to view the metrics data (stored vpxd-profiler-#### file). The dashboard can be accessed by typing the URL https://((hostip or name) or (vcenterip or name)/vod/index.html It will prompt for the credentials provide the details as applicable.

VMware vMotion issue - the virtual machine requires hardware features that are not supported or disbaled on the target host

I recently faced the below issue when trying to migrate a powered on VM (with Hardware Version as 8) from Cisco M3 Blade (Esxi 5.5) to M2 Blade (Esxi 5.5). Whereas when tried to migrate VM (Hardware version 7) between the same set of hosts, it'sworking fine.
The virtual machine requires hardware features that are not supported or disbaled on the target host: General Incompatibilities.

Kill Stuck VM tools installation task in ESXi

While installing VM tools, on one of the virtual machines tools installation task was getting hung. 

Was not able to cancel the task using vCenter or directly connecting to the host. Due to this all the features like Snapshot, Migrate were disabled on the VM.

To kill the VM tools installation task through command line, we need to identify VMID and kill the vm tools insall for the corresponding VM. 

Please follow the below steps. (applicable to ESXi).

1. Enable ssh on the host holding the VM.

2. Login to the host using SSH client. eg., Putty

3. Run the command line /usr/bin/vim-cmd vmsvc/getallvms

This will return list of the VMs with VM ID. Then run the below command to kill the VM tools install process for the VM facing issue.

4. /usr/bin/vim-cmd vmsvc/tools.cancelinstall VMID

Hope this quickly helps in getting the VM back to normal.

--Alternate way of achieving the same using PowerCLI would be:
get-vm "VMname" | Dismount-Tools

Thanks!

Achieved Rackspace CloudU Certification

Recently I was searching for some good course to understand the cloud computing key elements, delivery models etc.,. I came across the article that details about different courses/certifications available to get good idea of Cloud Computing Fundamentals. 

As Rackspace has strong market base in Cloud Computing and also providing vendor-neutral Cloud Computing curriculum 'CloudU' thought will take up the CloudU Training (online). Moreover, the course/exam is free of cost. The course curriculum is good and the author Ben Kepes has excellently presented the key elements of cloud computing in a course that consists 10 lessons.


What is CloudU all about: According to Rackspace, Cloud U is a vendor-neutral curriculum designed for IT professionals and business leaders that covers and certifies knowledge of the fundamentals of Cloud Computing. Cloud U content is available to any professional at any time, but if you want a formal recognition of your knowledge about Cloud Computing, you should complete the courses and requirements for a certificate.

How to prepare: Study each Cloud U lesson whitepaper, and then successfully complete each of 10 Cloud U lesson quizzes based on the whitepaper's content. Successfully complete a 50-question final exam drawn from materials covered in the 10 Cloud U lessons. More details are here

Here's my certificate :)  

vCenter Service not starting after the windows vCenter server restarts

I have experienced this on vCenter Server 5.5.0b. When the windows server is restarted, the vcenter servies does not come up automatically when the service startup type is set to Automatic. When the service is set to Automatic, there are possiblities that the SQL Server/database might not be completely loaded before the vCenter Server service trys to get started. It can be fixed by setting the service startup type to Automatic (Delayed Start).