NSX V2T Post-Migration Cleanup: Removing Unused Components After V2T Migration
book
Article ID: 409035
calendar_today
Updated On:
Products
VMware NSX
Issue/Introduction
This KB provides step-by-step instructions to clean up Unused components on NSX-T that were created or left behind as a byproduct of a V2T migration.
These components, while functional during the migration, are no longer used post-migration and can be removed to standardize the NSX-T environment.
These components must be removed in a specific order to avoid dependency errors.
Below are the unused components which you may see post V2T migration : Transport Node Profile (TNP) Transport Zone (TZ) Segments Segment profile DHCP profile IP pools Uplink profiles NIOC profiles
Environment
VMware NSX
Resolution
Pre-cleanup Checks: Before proceeding with any cleanup steps, ensure the following critical checks are performed:
Backup: Make sure you have the latest backup and passphrase. Host Maintenance: Please make sure there are no rigid affinity rules that can hinder putting the host into Maintenance mode Segment Usage: Verify no VMs or logical ports are attached to segments before attempting to delete them. Segment Profile Usage: Ensure no segments are attached to a segment profile before deletion. DHCP Profile Usage: Validate that the DHCP profile is not in use by any Tier-1 gateways or segments before deletion. IP Pool Allocation:Confirm that the IP pool has 0 allocated IPs before attempting to delete it.
Cleanup Steps:
Detach a Transport Node Profile (TNP) This step removes the automated configuration link between the cluster and the Hosts. It does not affect data plane traffic on existing hosts but is required before you can re-prepare the hosts.
Log in to the NSX Manager UI.
Navigate to System > Fabric > Hosts and select the Clusters tab.
Select the target cluster, click the Actions menu, and select Detach Transport Node Profile.
Confirm the detachment and wait for the process to complete.
Prepare manually the ESXi host Following the detachment, you must remove the old NSX configuration (Dummy TZ, Uplink-Profile, VDS Uplinks) from each ESXi host, preparing it for the new TNP as per the standard.
Warning: This process is disruptive. Always migrate or shut down all VMs from the host before putting it into maintenance mode.
In vCenter, migrate or power off all VMs from a host.
Put the host into maintenance mode.
In the NSX Manager UI, navigate to System > Fabric > Hosts and select the Host Transport Nodes tab.
Select the ESXi host, click Actions, and change the respective configuration as per standard.
Once NSX preparation is complete, take the host out of maintenance mode and validate VM communication.
Repeat this process for every host in the cluster.
Attach the new TNP After all ESXi hosts have been prepared, you can apply the new, standardized TNP.
Navigate to System > Fabric > Hosts and select the Clusters tab.
Select the cluster, click Actions, and choose Apply Transport Node Profile.
Select the new TNP that meets your standards and apply it.
Make sure that there are no mismatch alarms between TNP and TNs.
Validate the ESXi details in the Transport Zone (TZ) Verify that the hosts were successfully configured and have joined the correct Transport Zones.
Navigate to System > Fabric > Hosts and select the Host Transport Nodes tab.
Confirm that all hosts in the cluster show a Success status for their NSX configuration.
Click on individual hosts and check the Transport Zones section to ensure they are members of the correct TZs.
Delete the segment (make sure no VM on port) You can only delete a segment if no VMs or logical ports are attached to it.
Navigate to Networking > Segments and select the target segment.
In the details pane, check the Attached Ports column. If the count is greater than zero, investigate and migrate the VMs off this segment.
Once the port count is zero, you can delete the segment.
Delete the segment profile (make sure no segment on it) A segment profile can only be deleted if no segments are using it.
Navigate to Networking > Segments > Segment Profiles.
Select the profile you want to delete.
Use the "Used By" feature (if available) or check dependent segments manually to ensure no segments are referencing it.
Once confirmed, delete the profile.
Delete the DHCP profile (validate "where used") To delete a DHCP profile, first ensure it is not being used by any Tier-1 gateways or segments.
Navigate to Networking > DHCP.
Select the DHCP server or profile you want to delete.
Check the "Used By" or equivalent option to see which gateways or segments are referencing it.
Remove the DHCP configuration from all dependent objects.
Once the profile is no longer in use, you can delete it.
Delete IP Pool (validate 0 allocated IPs) An IP pool can only be deleted when all IPs have been released.
Navigate to Networking > IP Management > IP Address Pools.
Select the IP pool and check the Allocated column. It must be zero.
Once confirmed, delete the IP pool.
Delete unused uplink profiles Remove the uplink profiles that are not actively in use by your transport nodes.
Navigate to System > Fabric > Profiles > Uplink Profiles.
Examine each profile and cross-reference its usage against your transport nodes and TNPs.
Delete the profiles that are confirmed to be unused.
Delete the dummy TZ from all Edge Nodes If a dummy Transport Zone is configured on your NSX Edge nodes after the migration, you must remove them manually.
Navigate to System > Fabric > Nodes > Edge Clusters and select the Edge cluster.
For each Edge node, edit its configuration to remove the dummy Transport Zone in the overlay switch.
Apply the changes
Delete dummy TZ Once the Transport Zone is no longer in use by any transport nodes, you can delete it.
Navigate to System > Fabric > Profiles > Transport Zones.
Select the dummy Transport Zone and delete it.
Delete NIOC profile if migrated as N-VDS Once you have completed an N-VDS migration, you may have an outdated NIOC profile that can be safely removed.
Navigate to System > Fabric > Profiles > NIOC Profiles.
Check for profiles associated with the old N-VDS configuration.
Ensure the profile is not referenced by any host switches or TNPs before deleting.