Use this procedure if "Applied To" is configured in any of the DFW rules (this means that "Applied To" is not set to "DFW").
Note: For
NSX-v to
NSX-T migration, see the KB article
https://kb.vmware.com/s/article/56991 for more information.
For NSX-T to NSX-v migration, migrating a workload VM back to NSX-v might not work because the distributed firewall filter in NSX-T is always higher than in NSX-v. The workaround is to place the workload VM in the NSX-T exclusion list prior to vMotion.
Prerequisites
- Switch the Default Gateway to NSX-T Data Center.
- Ensure that:
- vSphere vMotion is enabled on the VMkernel adapter of each host in the cluster that is involved in this migration. For detailed steps about enabling vMotion on the VMkernel adapter, see the vSphere product documentation.
- The destination host in NSX-T Data Center has sufficient resources to receive the migrated VMs.
- The source and destination hosts are in an operational state. Resolve any problems with hosts including disconnected states.
For more information about vMotion, see Migration with vMotion in the vSphere product documentation.
Procedure
What to do next
After the migration of workload VMs and the DFW-only configuration is successful and thoroughly verified, remove the Layer 2 bridge to release the NSX-T Edge that you used for bridging.