baronne
Contributor
Contributor

NIC order changed after host update via Update Manager

Hi,

I started updating our small cluster of ESX 5.5 hosts this afternoon - and as an acid test I attempted the update on one host and after the successful update the server came back up with the NICs in the wrong order.  I've found articles about how to go about modifying this in the esx.conf file - however, surely this shouldn't be happening. It has obviously caused an issue for this host as it now now longer has a connection to the SAN. Is there a way to prevent this from happening or is it going to be a painful experience every time I come around to patching?

btw. using a vDS switch with host profiles.

Any advice/help much appreciated.

cheers,

ennorab

0 Kudos
5 Replies
bspagna89
Hot Shot
Hot Shot

Do you know if the host profile was compliant after booting?

New blog - https://virtualizeme.org/
0 Kudos
baronne
Contributor
Contributor

hi, the host became non-compliant after the update and reboot.

0 Kudos
bspagna89
Hot Shot
Hot Shot

Do you know what the reasons were? I think if we can get that host profile to apply properly you may be in good shape.

New blog - https://virtualizeme.org/
0 Kudos
baronne
Contributor
Contributor

ok, I'm going to try get it to apply the host profile and see how that goes...

0 Kudos
baronne
Contributor
Contributor

hi .. no joy unfortunately. I'm applying the host profile and the host appears to be compliant but the it appears something screwy has gone wrong with the NICs. The two interfaces I have for the storage appear disconnected:

deadnics.png

0 Kudos