When connect to an active/active array, esxcfg-mpath will not show you which HBA is currently in use for I/O operation. You can check this out in ESX 4.0 by using
esxcli nmp device list | grep "Working Paths"
You can also find out how many LUNs are connecting through a specific HBA
esxcli nmp device list | grep "Working Paths" | grep -c vmhba#
Note: (Tip was provided by a BCS customer)
VMkernel has it's own error code. When looking at vmkernel log files, some times you need help to understand some of the error codes. You can print them out by using:
vmkerrcode -l | less
esxtop is a great tool to monitor your host resource. What about if you want more information on the VM itself?
Connect to ESX server via ssh --> "esxtop" --> "c" (to switch to the CPU screen) Now you will see somthing like this:
Now what about if I want to see the VM named "bs-bcs-vc01"?
I can type "e" --> now it will ask me about the GID which is 20 in this case. so I type in "20" hit enter.
You now can see the CPU usage on all virtual CPU and the monitor processes (VMM), remote connections (MKS)
You can also find out how many LUNs are connecting through a specific HBA
