VMware Cloud Community
goppi
Enthusiast
Enthusiast
Jump to solution

NICs gone after applying patch

Just tried to install the lastes patch for ESXi 5.1 (ESXi510-201210001) on a running ProLiant DL380 gen. 8 via "esxcli software vib install".

The command says everything is ok, however after rebooting console screen shows the following message "No compatible network adpaters found ...." and the box is no longer reachable.

Any idea how to repair the server and what has happened?

Is this normal behavour that a patch removes network drivers and renders a server unusable?

Thanks for any help.

Cheers

0 Kudos
1 Solution

Accepted Solutions
MKguy
Virtuoso
Virtuoso
Jump to solution

IIRC in this release the DL380 gen. NICs are not supported.

You are remembering correctly:

http://www.vmware.com/resources/compatibility/detail.php?deviceCategory=io&productid=21446&deviceCat...

So what is the recommended method when applying patches?
Using update instead?

Yes. As the name implies, you use esxcli with the update command when applying updates Smiley Wink. That way it would not have replaced your tg3 driver with an older version.

Oh the good ol esxupdate, rip. But I have few complaints about what esxcli provides by now.

-- http://alpacapowered.wordpress.com

View solution in original post

0 Kudos
4 Replies
MKguy
Virtuoso
Virtuoso
Jump to solution

So you ran esxcli software vib install? The "install" option can completely remove certain VIBs not present in the update file. This is also outputted to the console. You should run the update command to update the VIBs.

It sounds like the install command could have removed your NIC driver - the tg3 driver for the default HP gen8 331FLR NICs. Confirm this with esxcli software vib list | grep tg3

If you use other NICs check the respective driver is still there.

The same issue with storage is documented here:

http://vninja.net/vmware-2/hp-bl460c-g8-lose-its-datastore/

If you reinstall the VIB, grab an updated driver since gen8 systems have some problems with the default driver:

http://communities.vmware.com/message/2103651#2103651

https://my.vmware.com/group/vmware/details?downloadGroup=DT-ESXI50-Broadcom-tg3-3124cv501&productId=...

-- http://alpacapowered.wordpress.com
goppi
Enthusiast
Enthusiast
Jump to solution

Hi MKguy.

Thanks for you reply.

The net-tg3 is still there but it is version 3.11h so it has been downgraded by the patch. IIRC in this release the DL380 gen. NICs are not supported. This was the reason I built my own install media with the tg3-3.124c version (beside the fact that there were connection problems with the older releases).

So what is the recommended method when applying patches?

Using update instead?

I'm new to 5.1 so esxupdate was my friend till now which no longer exists.

Cheers.

0 Kudos
MKguy
Virtuoso
Virtuoso
Jump to solution

IIRC in this release the DL380 gen. NICs are not supported.

You are remembering correctly:

http://www.vmware.com/resources/compatibility/detail.php?deviceCategory=io&productid=21446&deviceCat...

So what is the recommended method when applying patches?
Using update instead?

Yes. As the name implies, you use esxcli with the update command when applying updates Smiley Wink. That way it would not have replaced your tg3 driver with an older version.

Oh the good ol esxupdate, rip. But I have few complaints about what esxcli provides by now.

-- http://alpacapowered.wordpress.com
0 Kudos
goppi
Enthusiast
Enthusiast
Jump to solution

Yes. As the name implies, you use esxcli with the update command when applying updates Smiley Wink.

Yea. Seems that I have to learn it the hard way.

Oh the good ol esxupdate, rip. But I have few complaints about what esxcli provides by now.

When you got used to it I see no reason why esxcli should be bad.

Thanks again for helping.

Cheers.

0 Kudos