A subset of NSX-V features is supported for migration.
Most features have some limitations. When you import your NSX-V configuration for migration, you will get detailed feedback about what features and configurations in your environment are supported or not supported.
NSX-V Feature | Supported | Notes |
---|---|---|
VLAN-backed logical switches | Yes | |
Overlay-backed logical switches | Yes | |
L2 Bridges | No | |
Transport Zones | Yes | |
Routing | Yes | |
East-West Micro-Segmentation | Yes | |
Edge Firewall | Yes | |
NAT | Yes | |
L2 VPN | Yes | |
L3 VPN | Yes | |
Load Balancer | Yes | Supported for end-to-end migration. (NSX 4.0.0.1) Not supported for lift-and-shift migration. (NSX 4.0.1.1 and later) Supported for lift-and-shift migration. |
DHCP and DNS | Yes | |
Distributed Firewall | Yes | |
Service Composer | Yes | |
Grouping objects | Yes | Limitations include number of items, and dynamic expressions making up security groups. |
Guest Introspection | Yes | Supported for end-to-end migration only. Only Guest Introspection service configuration is migrated. Partner service registration, partner service VMs, and vendor templates are not migrated. Before migration, the partner service must be registered with NSX to create the respective service and vendor templates in NSX. Consult the VMware partner before proceeding with migration. |
Network Introspection | Yes | Supported for end-to-end migration only. Only Network Introspection service configuration is migrated. Partner service registration, partner service VMs, and vendor templates are not migrated. Before migration, the partner service, vendor templates, and Partner Management Console/Partner Service Manager must be registered with NSX. Consult the VMware partner before proceeding with migration. |
Cross-vCenter NSX | Yes |
Only supported if you choose the Migrate NSX for vSphere mode and User Defined Topology. |
NSX-V with a Cloud Management Platform, Integrated Stack Solution, or PaaS Solution. | Yes | Migration of NSX-V with vRealize Automation is supported. Contact your VMware representative before proceeding with migration. Scripts and integrations might break if you migrate the integrated environments:
For example:
|