ESXi host disconnected after upgrade
Article ID: 411811
Updated On:
Products
Issue/Introduction
- After upgrading an ESXi host the vCenter reports that the host is disconnected.
- After upgrade the network is not working and host can only be accessed via KVM console.
Environment
VMware ESXi
Cause
This occurs because the PCI bus ordering from the physical network is changed after either rebooting the server or adding additional vNICs, and this causes the order of the NICs presented to the ESXi host to be different. then what was previously used.
This issue can also be seen after an upgrade is applied to an ESXi host and the driver/firmware data for the NICs is updated as well.
Resolution
Re-alias the NICs so they are in the correct order via the ESXi host SSH/DCUI and reboot the effected ESXi host for the changes to take place.
- To confirm which NIC or vNIC is supposed to be associated with which specific vmnic on the ESXi side, please review the physical network for the MAC or PCI identifying addresses.
- Work with the hardware vendor to determine if there is a configuration for the physical NICs to maintain their device names, so if the host is rebooted or upgraded the PCI identifying data won't change.
- If the hosts is using a host profile the changes can also be manually made via the profile under Device Alias Configuration (normally located under General System Settings) and then remediate the affected host.
- If no host profiles are in use, then the aliases will need to be manually changed with CLI commands.
- To manually edit the aliases please refer to the section titled Changing the names assigned by the ESXi host in How VMware ESXi determines the order in which names are assigned to devices for the specific commands and further details.
Additional Information
Please note this is a known occurrence with Cisco UCS vNICS. Please refer to Cisco Bug: CSCuv34051 for further details from Cisco. This site may require log in for more details and is not monitored or updated by VMware by Broadcom.
Feedback
