We have successfully upgraded alll our HP DL 380 G6 servers to vSphere 4.1

ESX(i) installations on HP systems require the HP NMI driverESX 4.1 instances on HP systems require the HP NMI driver to ensure proper handling of non-maskable interrupts (NMIs). The NMI driver ensures that NMIs are properly detected and logged. Without this driver, NMIs, which signal hardware faults, are ignored on HP systems with ESX. Workaround: Download and install the NMI driver. The driver is available as an offline bundle from the HP Web site. Also, see KB 1021609.

VMWare hat die Version 4.1 von vSphere veröffentlicht und kann unter folgender URL heruntergeladen werden: http://downloads.vmware.com/d/ ACHTUNG, das vCenter benötigt eine 64Bit Version des Betriebsystems!

They are three different ways to manage the VI with a vma. If you want to run only a single command use: working without sessionfile If you want to run commands withing a timeperiod of 30 minutes use: working with sessionfile If you want to run commands for more than 30 minutes use: vifastpass working without sessionfile (username and password must be entered for each command) e.g. vicfg-nics -l –server server1 –username xxx –vihost xxxx resxtop –server server1  –username xxx –vihost xxx working with sessionfile (session lasts for 30 minutes) Create sessionfile per vcenter server: 1.    type cd /usr/share/doc/vmware-cli/samples/session 2.    for vcenter-p: ./save_session.pl –savesessionfile /tmp/vcenter1 –server xxx –username xxx for vcenter-t: ./save_session.pl –savesessionfile /tmp/vcenter2 –server xxx –username xxx 3.    run commands: e.g. vicfg-nics -l –sessionfile /tmp/vcenter1 –vihost xxx vicfg-nics -l –sessionfile /tmp/vcenter2 –vihost xxx resxtop does not work with sessionfile! working with vifastpass 1.  sudo vifp addserver vcenter1 or/and sudo vifp addserver vcenter2 2.  run vifp listservers to verify that the vcenter server(s) have been added as target. 3.  Inititalize the vcenter server you need to manage (e.g.  vifpinit vcenter1) 4.    run commands e.g. resxtop –vihost xxx (esxhost) vicfg-nics -l –xxx

I recently discovered a problem with a HP EVA 5000 Firmware 3028 which is only able for active/passive, but the driver loaded by esx was: VMW_SATP_DEFAULT_AA This resulted in two dead paths for each attached LUN. To fix this issue run following command: esxcli nmp satp addrule –satp=”VMW_SATP_DEFAULT_AP” –vendor=”COMPAQ” –model=”HSV110 (C)COMPAQ” –description=”active/passive Compaq EVA 5000″ esxcli nmp satp listrules -s VMW_SATP_DEFAULT_AP should now list your new rule. Reboot the host and make sure VMW_SATP_DEFAULT_AP driver is loaded.

When I install new ESX4 Hosts, most of the time I patch them manually, have the patches with me on a USB Stick. This saves me lot of time.

1. Use following cli command on ESX4 to put the host into maintenance mode: vimsh -n -e /hostsvc/maintenance_mode_enter
2. Put the Patch Archive e.g. ESX400-200909001.zip  to the ESX4 Host
3. Run following cli to manually install the Patch Bundle:  esxupdate –bundle ESX400-200909001.zip update
4. Reboot the Host: reboot
5. Exit maintenance mode: vimsh -n -e /hostsvc/maintenance_mode_exit



User following command on the esx console to get the pid of the “running” virtual machine: ps auxfww | grep Name_of_the_VM kill -9 PID (numer of the PID)