NSX Uninstall Process: Troubleshooting and Removal Steps
search cancel

NSX Uninstall Process: Troubleshooting and Removal Steps

book

Article ID: 375111

calendar_today

Updated On:

Products

VMware NSX

Issue/Introduction

VMware NSX components must be uninstalled in a particular order and each component may experience interruptions of the uninstall process.  Each component’s uninstall will have to be verified individually. 

  • The process to remove NSX

  • Procedure to troubleshoot the issue step by step.

  • List of information and logs to be collected to opening a case with Broadcom Support.

Environment

VMware NSX

VMware NSX-T Data Center

Resolution

  • During a standard Networking and Security Installation, NSX is installed on ESXi hosts and the vCenter Server (Extension)

  • To uninstall NSX fully, it needs to be removed from all installed components, and all NSX objects need to be removed from the environment.

  • Official documentation to Uninstall NSX from a Managed Host in a vSphere Cluster.

Uninstalling NSX from an ESXi host

  1. Remove all workload virtual machines from all NSX related networks. These VMs can be moved to non-NSX port groups.

    1. Edit the configuration of the VMs using vCenter to change NSX segment to a regular portgroup with downtime approval.

    2. Evacuate the VM's from the host.

    3. Place the host in Maintenance Mode.

  2. Prepare the host for VIB removal:

    • If only removing NSX from a Single ESXi Host:

      1. Via vCenter, put the host into Maintenance Mode
      2. Once the host is in Maintenance Mode, move the host to the Datacenter level of the vCenter Inventory


      3. Once the host is at the Datacenter level of the vCenter, return to the NSX interface and go to System → Fabric → Hosts → Other Nodes.

        • If a Transport Node Profile is in use, once the host has been removed from the cluster it should begin uninstalling NSX from the host automatically.  

        • If a Transport Node Profile is not in use, or if the uninstall doesn’t begin automatically, click the checkbox beside the ESXi host’s name and click Remove NSX.


          • If this is the first attempt to remove the ESXi host from NSX, click Delete without checking the “Force Delete” checkbox. This will attempt to uninstall the NSX VIBs from the ESXi host and properly remove the host from the NSX Manager database. If this fails for any reason, perform the next step try with the “Force Delete” option before attempting to use cli commands to remove NSX from the host.


      4. If multiple attempts have been made to uninstall NSX from this host and in case failed, check the “Force Delete” checkbox and then click Delete.
                         


    • If removing NSX from all hosts in a cluster

      *NOTE: Removing a Transport Node Profile (TNP) from a cluster will NOT initiate a VIB uninstall from all hosts in the cluster.

      1. Click the Checkbox beside the cluster name and then click "Remove NSX"

      2. Click "REMOVE" on the popup dialog box that appears.


      3. The uninstall process will begin on all hosts in the cluster.


      4. Any errors or uninstall failures will be reported in the NSX GUI and will need to be addressed individually. Use the "For Individual Hosts" section of this document to start troubleshooting and attempting to work around single host uninstall failures.


  3. After ALL hosts have successfully been removed from NSX and All NSX VIBs are uninstalled, no NSX port groups should appear in the vCenter interface.

    • NSX Segments as seen in the NSX GUI


    • vCenter Networks with NSX Segments available (some hosts fully installed with NSX)


    • vCenter Networks with no NSX Segments available (all hosts uninstalled)

 

Delete NSX Edge Appliances

    • Before NSX can be removed from vCenter, all objects inside vCenter need to be deleted from the vCenter Inventory. This is particularly important when Edges and NSX Managers have been deployed using the NSX GUI into the vCenter Inventory

  1. Edge nodes need to be shut down and deleted, make sure there are no T0 and T1 gateways mapped.

    1. From Networking -> Segments -> Disconnect all Segments from Any T1s or T0s.  This can be done by setting the "Connected Gateway" to "None."


    2. Click Save -> Close Editing.

  2. If a Segment has any features supported on Service Routers (i.e. services inside Edge Nodes), those services will need to be removed before the segment can be disconnected from the T1/T0. However, a segment can be deleted if services are associated with it.

    1. If a segment is still referenced by a T1/T0, it will not be allowed to be deleted and the T1/T0 have to be edited to remove the uplinks associated with these segments.


    2. In this instance, the T0 has multiple interfaces and being used to peer with several BGP neighbors.


      1. Delete all BGP neighbors.

      2. Delete all Interfaces.

      3. Close Editing.

  3. Return to Networking → Segments and delete the remaining segments.
  4. Delete any remaining T1 and T0 gateways.

  5. Delete the Edge Clusters:

    1. Navigate to System → Nodes → Edge Clusters.

    2. Select the Edge Cluster by clicking the checkbox, then click Edit.

    3. In the Edit Edge Cluster dialog box, check the edges on the right and click the blue arrow to move them to the Available box on the left.





    4. Click Save.

    5. Click Edge Transport Nodes

    6. Select all Edges by clicking the checkbox beside the Edge header


    7. Click Delete. All Edges will be deleted from the NSX inventory.

      • If the Edges were deployed via the NSX GUI, the virtual machines will be powered down and deleted from the vCenter inventory automatically.

      • If the Edges were deployed manually (via OVA), they will not be deleted from the vCenter inventory. They will need to be powered down and deleted manually via the vCenter user interface.

Delete NSX Managers

  • NSX Managers deployed via the NSX UI must first be deleted before removing the "Compute Manager" (same applies to the Edge Transport nodes). This means the NSX Managers will have to be deleted which are deployed through NSX UI and by leaving the initial NSX manager node that was deployed via OVA on vCenter.

  • To identify which compute manager was used to deploy NSX manager nodes via the vc_id value returned from the    GET https://<nsx-mgr-IP/FQDN>/api/v1/cluster/nodes/deployments  API call.

    • Sample (truncated) output:
                  "deployment_config": {
                      "vc_id": "2fd34a13-####-####-####-fcc5d41f7db4",
                      "compute_id": "<domain-id>",
                      "storage_id": "<datastore-id>",
                      "host_id": "<host-id>",
                      "management_network_id": "<dvportgroup-id>",
      • In this sample output, the vc_id value is noted as 2fd34a13-####-####-####-fcc5d41f7db4. This can be checked against the NSX manager UUID value on the System > Configuration > Appliances page, under the View Details link for each of the NSX manager nodes.

  • The NSX UI will show this message/alert when attempting to delete the Compute Manager is an NSX component has been deployed using the GUI


  • To delete any NSX Managers still associated with this Compute Manager:

    1. Navigate to System -> Appliances

    2. Select the NSX Manager to be deleted via the NSX UI

    3. Click Actions → Delete


      • NOTE: Only Managers that were deployed using the NSX UI will have the Delete command as a selection option.


Delete the Compute Manager (i.e. Uninstall NSX from a vCenter Server)

  1. Once the only NSX Manager remaining is the OVA deployed node, vCenter can be removed from NSX via the System → Fabric → Compute Managers page.

  2. Select the Compute Manager by clicking the checkbox beside the Compute Manager name.


  3. Click Delete.

  4. Click Delete in the popup dialog box.


  5. If no components, such as Edges or NSX Manager nodes exist inside the vCenter, the Compute Manager will be removed.


  6. Once the removal of "Compute Manager" is successful without errors, this will also remove the "NSX Extension" from the vCenter Server.  if in case of any error, follow the documentation to Remove NSX-T Data Center Extension from vCenter Server" and validate the uninstall is complete.

  7. The remaining NSX Manager node can now be safely shut down and deleted from vCenter Inventory.

Additional Information

Known Issues when attempting to uninstall NSX from an ESXi host:

Known Issues when attempting to install NSX on an ESXi host:

Known Issues when attempting to NSX edge node:

Known issue when attempting to uninstall NSX from vCenter:



If you are contacting Broadcom support about this issue: provide the information below.

Powered by Wolken Software