Category Archives: Virtualization

Obtaining ILO ip and mac on esxi host

In Vcenter, for configuring Esxi Host Power management (configure tab, power management) I needed an easy way to get both ip and mac address. A quick search got me a powershell script for use under powercli. I didn’t have powercli installed on my newer workstation so.. here’s the process.

Continue reading Obtaining ILO ip and mac on esxi host


3Par and ESXi configuration

As part of optimization, guides call for setting RoundRobin and iops=1. This allows for better balancing/distribution of data flow. After installing ESXi6, open up putty, connect, and run:

esxcli storage nmp satp rule add -s “VMW_SATP_ALUA” -P “VMW_PSP_RR” -O iops=1 -c “tpgs_on” -V “3PARdata” -M “VV” -e “HP 3PAR Custom iSCSI/FC/FCoE ALUA Rule”

You’ll need to reboot afterward so the quick way to reboot: # reboot
If you don’t have access to ssh or the system in in lockdown mode or if you want to issue the reboot programatically, try the ‘safe’ way: # vicfg-hostops –operation reboot -force

Reference: Pg 36 – HP 3PAR VMware ESX/ESXi Implementation Guide (

VMware Workstation: DOS 6.22 with Networking, Sharing, and Remote Control

I ended up not getting this to work perfectly but thought I’d post the draft as some of it may provide a little guidance..



Create a folder to hold the contents of a mountable iso image (ie, c:\build\)

Extract (unzip) the two network disks into a single folder (c:\build\netsetup\)

Extract the AMD PCnet driver into the same folder (c:\build\netsetup\) via unzip, then run or extract the wfw31.exe to get the files needed.

Extract Tinyhg_f.exe from into the same folder also. this version includes support for VGA modes.  If you don’t need VGA, then use the Tinyh_f.exe as it’ll use less memory)

Copy the netshar.exe into the same folder as well.

Run Folder2ISO and create an image of the netsetup folder.

Create a New VM (Install the OS later; type=Other, MS-Dos; Max HD Size=2G, store as a single file).  Do not start the VM just yet, finish the new vm wizard.  Set the Network type to be Bridged instead of NAT. Attach the Dos bootable ISO then manually EDIT your new vm’s vmx file using notepad++ or similar and ADD

bios.bootDelay = “nnnn”

I chose 5000 (in place of nnnn) for an approximate 5 second bios boot screen delay which will allow you time to hit the appropriate key to manually select a boot device.

NOW you can start up the VM, and it should automatically boot to the loaded ISO (dos6.22). When it’s up, run Fdisk to partition the HD. It will ask for a reboot.

When you restart, this time you’ll need to hit the appropriate key to bring up your bootmenu (on HP or Dell systems, it’s often ESC or F12.) and boot to the dos cd. Now format it and transfer the system files (/s), msdos files, and copy a barebones config that will load the cdrom driver.

format c: /s

xcopy r:\*.* c:\msdos\ /s /y

copy autoexec.bat c:\

copy config.sys c:\

copy himem.sys c:\

copy cd1.sys c:\

Power off the vm then change the attached ISO to the NetSetup.iso you created earlier and start up the vm again.

Change to the R: drive (cd rom) and run setup.exe to start the network client installation.

Accept default of c:\net

Select *Network adapter not shown on list below …

[ ]

Accept Default location of R:\ then select the Advanced Micro Devices PCNET Family adaptor.

[ ]

When entering your username, it will also be used as the PC name

[ ]

Change network configuration

[ ]

Tab to the upper box and highlight “NWLink IPX Compatible Transport”. Tab to the the lower box, select Remove, and then select the Microsoft TCP/IP for the protocol used.

[ ]

Network setup is done.  Press F3 to exit without rebooting.

[ ]

Copy the file that allows for sharing folders and also copy and add the Tiny host; and set it to start at bootup

copy r:\netshar.exe c:\msdos

copy r:\tiny*.exe c:\msdos – Copies the Tiny remote control TSR from the network setup disc.

c:\msdos\edit c:\autoexec.bat

c:\msdos\tinyhg_f.exe password password

…or tinyh_f.exe for non-vga purposes

While your editing the autoexec.bat file, you’ll probably wish to verify a path statement exists and that c:\msdos, c:\, and c:\net are included. You can change the prompt also..

set path=c:\,c:\msdos,c:\net

Prompt $p$g

after saving and exiting, you can reboot the vm via Ctrl-Alt-Insert

misc references:

Updating to ESXi 5.5 update2

ssh/sftp the update zip to a datastore of your choice. I usually use CoreFTP LE as my client and push the update to /vmfs/volumes/1A-LabsESXiDataStore-Thick/ISO-Bits-Drivers/

Put the host into maintenance mode using vcenter/vsphere web interface or use Kitty/Putty to do it via the cmdline.

# vim-cmd hostsvc/maintenance_mode_enter

Change to the location where you uploaded the update and start the update.

# esxcli software vib update -d “/vmfs/volumes/1A-LabsESXiDataStore-Thick/ISO-Bits-Drivers/”

Optionally, you can view the installed files. check the dates for the particular update being applied.

#esxcli software vib list

It will require a reboot to complete the update.


Finally, exit mainenace mode and you’re back in business.

# vim-cmd hostsvc/maintenance_mode_exit

A full list of vCenter updates is maintained here: