After deploying NSX I have noticed the IP pool for the VXLAN VMKernel port didn't get applied to the same nic as the rest of the cluster. There does not appear to be a way of "unpreparing" an individual host. If anyone knows a way please do tell.
Hello and Welcome to NSX VMTN,
In NSX we have 3 different VIB
vib names are:
esx-dvfilter-switch-security
esx-vsip
esx-vxlan
VXLAN VIB verification
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
we can verify vib exist by this command:
esxcli software vib get --vibname esx-vxlan
VMware_bootbank_esx-vxlan_5.5.0-0.0.1641394
Name: esx-vxlan
Version: 5.5.0-0.0.1641394
Type: bootbank
Vendor: VMware
Acceptance Level: VMwareCertified
Summary: Vxlan and host tool
Description: This package loads module and configures firewall for vxlan networking.
ReferenceURLs:
Creation Date: 2014-03-02
Depends: esx-base >= 5.5, esx-base << 5.6, nsx-api <= 1, vmkapi_2_2_0_0
Conflicts:
Replaces:
Provides: vxlan = 2.0.0.0-nsx, vdr = 1.0.0.0
Maintenance Mode Required: False
Hardware Platforms Required:
Live Install Allowed: True
Live Remove Allowed: False
Stateless Ready: True
Overlay: True
Tags:
Payloads: esx-vxla
Remove VXLAN VIB
esxcli software vib remove -n esx-vxlan
Removal Result
Message: The update completed successfully, but the system needs to be reboot ed for the changes to be effective.
Reboot Required: true
VIBs Installed:
VIBs Removed: VMware_bootbank_esx-vxlan_5.5.0-0.0.1641394
VIBs Skipped:
you can remove all 3 VIB this way.
The best option would be to remove the ESXi host from the prepared cluster which will uninstall any NSX components automatically. Then once the VMkernel interfaces are aligned, you can re-add the host to the cluster which will re-install the NSX components & create the VXLAN VTEP.
