NSX install failure of ESXI and stuck in partial success status
search cancel

NSX install failure of ESXI and stuck in partial success status

book

Article ID: 416113

calendar_today

Updated On:

Products

VMware NSX

Issue/Introduction

  • You have an ESXi which has failed installation of NSX and stuck in partial success state when viewed from NSX UI, following an ESXi upgrade from 7.x to 8.x 

  • You tried re-preparing the Host for NSX and it fails with error indicating the TEP already exists and the gateway is unreachable as in below screenshot



  • Validation of ESXi kernels from the command 'esxcfg-vmknic -l' reveals there are already pre-existing NSX TEP's (vmk's)

Environment

VMware NSX

Cause

Since the ESXi contains pre-existing NSX TEP's (vmk's) from a previous installation which is treated as stale vmkernels by NSX preventing the new installation

Resolution

Remove the conflicting NSX TEP's vmkernel interfaces on the problem ESXi using the below command and retry the NSX installation

esxcli network ip interface remove -i vmkX

NOTE : If the issue persists even after following the above steps, feel free to open a support case with Broadcom Support Team

Additional Information

The NSX VIBs are different for ESXi 7.0 and ESXi 8.0, due to which there may be a need to re-prepare the ESXi if NSX kernel module was not part of the image or upgrade baseline.

Below is the KB talking about the above issue : 
NSX Host Install Failed After ESXi 7.0 to 8.0 Upgrade: Node has invalid version of software