Wiped out HBA config with firmware update

[billcmurphy]

Hi All,

I just recently updated the firmware on an Emulex fiber card in an HP dl380 G6  running esx 5.5.

Not only are my paths to the SAN gone, but I can't see the card in vsphere to re-configure.

Is there some way to initialize the device to get it to show up?

The drivers, etc are installed.

Thanks,

-Bill

[LucianoPatrão]

Hi

Could you provide more information?? Emulex model?? Firmware version?? What ESXi driver version are installed??

Check here how to check this information: VMware KB: Identifying the firmware of a Qlogic or Emulex FC HBA

Thanks

[billcmurphy]

Hi Luciano,

Thank you for the feedback!!

I have 4 identical hosts, all using EMC branded Emulex LPe11000 4GB fiber adapters.

The KB article you referenced has the location of the drivers under /proc/scsi .

On each host the contents of the /proc/scsi directory consists of bnx2i and hpsa.

Could the Emulex drivers be located somewhere else on the file system?

  Thanks,

-Bill

[billcmurphy]

Just some more info:

when running ~# esxcfg-scsidevs -a on a normal host I can see the Emulex info:

# esxcfg-scsidevs -a

vmhba38 bnx2i             unbound   iscsi.vmhba38                           Broadcom iSCSI Adapter

vmhba39 bnx2i             unbound   iscsi.vmhba39                           Broadcom iSCSI Adapter

vmhba0  ata_piix          link-n/a  sata.vmhba0                             (0:0:31.2) Intel Corporation ICH10 4 port SATA IDE Controller

vmhba1  hpsa              link-n/a  sas.50123456789abcde                    (0:4:0.0) Hewlett-Packard Company Smart Array P410i

vmhba2  lpfc              link-up   fc.20000000c97ab48e:10000000c97ab48e    (0:7:0.0) Emulex Corporation LPe11000 4Gb Fibre Channel Host Adapter

vmhba3  lpfc              link-up   fc.20000000c97ab48f:10000000c97ab48f    (0:7:0.1) Emulex Corporation LPe11000 4Gb Fibre Channel Host Adapter

vmhba40 ata_piix          link-n/a  sata.vmhba40                            (0:0:31.2) Intel Corporation ICH10 4 port SATA IDE Controller

vmhba32 bnx2i             unbound   iscsi.vmhba32                           Broadcom iSCSI Adapter

vmhba33 bnx2i             unbound   iscsi.vmhba33                           Broadcom iSCSI Adapter

vmhba34 bnx2i             unbound   iscsi.vmhba34                           Broadcom iSCSI Adapter

vmhba35 bnx2i             unbound   iscsi.vmhba35                           Broadcom iSCSI Adapter

vmhba36 bnx2i             unbound   iscsi.vmhba36                           Broadcom iSCSI Adapter

vmhba37 bnx2i             unbound   iscsi.vmhba37                           Broadcom iSCSI Adapter

BUT, on the problem host I only see:

~ # esxcfg-scsidevs -a

vmhba38 bnx2i             unbound   iscsi.vmhba38                           Broadcom iSCSI Adapter

vmhba39 bnx2i             unbound   iscsi.vmhba39                           Broadcom iSCSI Adapter

vmhba0  ata_piix          link-n/a  sata.vmhba0                             (0:0:31.2) Intel Corporation ICH10 4 port SATA IDE Controller

vmhba1  hpsa              link-n/a  sas.50123456789abcde                    (0:4:0.0) Hewlett-Packard Company Smart Array P410i

vmhba40 ata_piix          link-n/a  sata.vmhba40                            (0:0:31.2) Intel Corporation ICH10 4 port SATA IDE Controller

vmhba32 bnx2i             unbound   iscsi.vmhba32                           Broadcom iSCSI Adapter

vmhba33 bnx2i             unbound   iscsi.vmhba33                           Broadcom iSCSI Adapter

vmhba34 bnx2i             unbound   iscsi.vmhba34                           Broadcom iSCSI Adapter

vmhba35 bnx2i             unbound   iscsi.vmhba35                           Broadcom iSCSI Adapter

vmhba36 bnx2i             unbound   iscsi.vmhba36                           Broadcom iSCSI Adapter

vmhba37 bnx2i             unbound   iscsi.vmhba37                           Broadcom iSCSI Adapter

So the question is:

Is my card dead or is there some way to initialize before the system will recognize it?

Nothing has changed on the system except a firmware update on the fiber card.  All the other fiber cards in other hosts have already been updated.

Thanks again,

-Bill

[billcmurphy]

So looks like the card is dead.

If I replace it, how do I get my SAN to recognize the new card?

There doesn't seem to be any options to add connection within vsphere...

Thanks,

-Bill

[LucianoPatrão]

Hi Bill,

Sorry been very busy and did not return to this post.

If both host have the same ESXi version, Hosts are same model(same BIOS, Firmware etc.) and the Cards also, then yes you could have a broken one.

Have you try to install to install the recent VIB drivers into that host that you upgraded the card?

Last drivers:

Index of /hpe/apr2016/esxi-550-drv-vibs/lpfc

Try to run this in a working host and on that host, and check the results

for a in $(esxcfg-scsidevs -a |awk '{print $2}') ;do vmkload_mod -s $a |grep -i version ;done

I have my homelab with emulex, but unfortunately I move house last week, and still have my homelab disconnected. If not I could try to check some of my configurations to help more.

Here you can also check and get some information about your Cards/NICs

https://kb.vmware.com/kb/1027206

Hope this can help

[billcmurphy]

Hi Luciano,

Thank you for the reply!

I have replaced the card and re-zoned the storage to see the new one.

I will test the old card in another system with the updated VIB drivers as soon as I can.

Thank you for all the feedback.

-Bill

[LucianoPatrão]

Hi,

Try also to update the device drivers

http://vibsdepot.hpe.com/hpe/apr2016/esxi-550-devicedrivers/VMW-ESX-5.5.0-lpfc-10.7.110.4-3162103.zi...

[continuum]

> I have replaced the card
Hopefully you created dd-copies of each single disk in case you used raid 5 or similar.
Crossing fingers ....