ADVERTISE HERE

esxcfg-scsidevs–a output changed in vSphere 4.1

Title: esxcfg-scsidevs–a output changed in vSphere 4.1
Author(s): (ICT-Freak.nl) Arne Fokkema
Target Audience: Technical - Intermediate
Current Revision:
First Published: 11 January 2011
Products: VMware, vSphere
UID: XD10370

Why did VMware change the output of esxcfg-scsidevs –a?

Punchy Text: 

Why did VMware change the output of esxcfg-scsidevs –a?

By Arne Fokkema - ICT-Freak.nl


Last week I was busy converting one of my ks.cfg scripts which I use to install vSphere 4.0 update 2 to vSphere 4.1 and I found something, which I didn’t expect from VMware..

To find the iSCSI vmhba I use the following one-liner to save it into a variable VMHBA:

VMHBA=$(/usr/sbin/esxcfg-scsidevs -a |grep “Software iSCSI” |awk ‘{print $1}’)

But this one-liner didn’t work anymore in vSphere 4.1. So I tried to run the script part by part and started with a vSphere 4.1 host:

/usr/sbin/esxcfg-scsidevs -a

The following output was generated:

iSCSI Software Adapterif you run the same command on a vSphere 4.0 update 2 host, you’ll see the difference:

Software iSCSISo to fix this part of my ks.cfg I had to change the VMHBA one-liner and change the grep phrase to “iSCSI Software Adapter” instead of “Software iSCSI”:

VMHBA=$(/usr/sbin/esxcfg-scsidevs -a |grep “iSCSI Software Adapter” |awk ‘{print $1}’)

After changing this line, my ks.cfg script runs fine again. But the question remains unanswered; why did VMware change the output of esxcfg-scsidevs –a Winking smile.

Spotlight:

VMware Documentation Downloader v11.08.30

Updated for vSphere 5 - A free tool for those on the move who need information FAST

vSphere 5 License Entitlement Changes

See what has changed in the license entitlement in vSphere 5?

Thin Client vs Zero Client

The differences between Thin and Zero desktop clients for VDI

Technology Exchange: