Archive for the ‘ESX’ Category

Bug in HP Agents 8.70 causes HP DL580 G7 running ESX to reboot on PSU failure [SOLVED]

January 10, 2012 2 comments

We discovered a bug in HP Agents 8.70 installed on ESX 4.1 running on HP ProLiant DL580 G7 servers.


Those machines come equipped with 4 PSUs.  When the power is lost of 2 PSUs at the same time, a reboot is triggered by the HP Agents.  This causes all VMs on that host to crash (HA will restart them on another host if configured properly).  This reboot makes no sense as the system is perfectly capable of running on 2 PSUs.

Read more…

Categories: ESX, Hardware, vSphere

Get all VMs with Fixed MAC Addresses using PowerCLI

July 29, 2011 6 comments

I needed a list of all VMs with a Fixed MAC Address running on vSphere (it works for ESX 3.5 as well).

Let’s build up this command from the beginning.  We start with Get-VM to get a hold of all VMs.


This of course will list just any VM.  So we need some filtering.

Read more…

Categories: ESX, PowerCLI, vSphere

Reorder NICs on ESX 3.5

September 27, 2010 Leave a comment

When you have an ESX host with different brands of NICs, the order may not always be the same across hosts.

In this example, we want the NIC numbering to be sorted by Brand.  Right now, the Intel NICs (vmnic2 and vmnic3) fall in between the Broadcom NICs.  This makes things complicated.

We are going to swap vmnic2 <-> vmnic6 and vmnic3 <-> vmnic7.

Read more…

Categories: ESX

Get ESX version numbers

August 31, 2010 1 comment

Log in to your ESX and run the following command:

cat /proc/vmware/version

It will give you a nice overview of the version of ESX and its components/drivers.


Categories: ESX, VMware, vSphere

Enable Serial-Line Logging on ESX 3.5 through HP iLO

August 16, 2010 Leave a comment

First we need to configure the Virtual COM port.

Reboot your server and get into the BIOS by pressing F9.  Get into the System Options screen and select the Virtual Serial Port.  Take a note of the COM port used (COM 2 in this example).


Go back to the main menu and select BIOS Serial Console & EMS.  Under BIOS Serial Console Port, select the COM port you noted above.  Set the BIOS Serial Console Baub Rate to 115200.

Read more…

Categories: ESX, VMware

Get the trend of VM CPU Usage over a 1 year period

July 1, 2010 Leave a comment

Ever wondered what the trend is of all your VM’s CPU Usage?  You might see surprising things 🙂


The following script calculates the following things:

Perf1yAgo The average VM CPU usage over a 10 days timespan exactly 1 year ago
PerfNow The average VM CPU usage over the last 10 days
Trend 0 % = No change in CPU usage
100 % = CPU Usage doubled in a 1 year timespan
-50 % = CPU Usage is half of what it used to be 1 year ago

VM’s with no statistics available from 1 year ago are skipped.  PoweredOff VM’s are skipped as well.



Fire up PowerCLI and connect to one or more vCenter servers with Connect-VIServer.

Read more…

Categories: ESX, VMware, vSphere

Set verbose logging on Emulex Driver in ESX 3.5

July 1, 2010 Leave a comment

If you’re troobleshooting SAN/HBA issues, it might come in handy to enable verbose logging on your Emulex HBA driver.

Run the following command to list the drivername

vmkload_mod -l | grep lpfc


The HBA driver is our case is lpfc_740 (lpfc stands for LightPulse Fibre Channel and 740 is the version number)

List the current options for the driver by entering

esxcfg-module -g lpfc_740


Run the following command to set the verbose logging option:

esxcfg-module -s lpfc_log_verbose=0xffff lpfc_740

You can run the esxcfg-module –g lpfc_740 command again to verify the settings:


Make the change (re)boot persistent

esxcfg-boot -b

Reboot your host (make sure no VM’s are running)


If you now check your vmkernel logfile (/var/log/vmkernel), you will see a LOT of entries from your HBA driver.


After you have done your stuff, make sure to disable to logging by running (basically, you will remove the lpfc_log_verbose option from the driver loading module)

esxcfg-module –s ‘’ lpfc_740

esxcfg-boot -b


After the reboot, open up your vmkernel logfile and verify the HBA driver entries no longer appear.

Categories: ESX, Storage, VMware