Supported Features and Edge Gateway Services

This section lists the features and edge gateway services supported by NSX Migration for VMware Cloud Director.

Supported Features

The NSX Migration for VMware Cloud Director supports several features.

• Compute policies including VM placement and VM sizing policy

• Storage policies

• Catalog migration from organization VDC backed by NSX Data Center for vSphere to organization VDC backed by NSX-T Data Center. The catalog migration also includes the migration of vApp templates and media.

  Note

  • The published catalogs will be migrated as unpublished and publishing of catalogs has to be done manually after cleanup.
  • The subscribed catalogs will not be migrated, the provider has to remove the subscribed catalogs before cleanup.
  • Input YAML flag TimeoutForVappMigration can also be used to regulate catalog migration.
  • Migrates the vApp templates whose storage policy is not present in the NSX-T Data Center. Before catalog migration, the storage policy of those templates which are not present in the NSX-T Data Center is updated with the default storage policy of the NSX-T Data Center.
  • Catalog Owner details will be migrated during cleanup.
  • Catalog Share Permission details will be migrated during the cleanup.

• Standalone VMs

• VM with connected media

• VMs with snapshots

• Affinity and anti-affinity rules

• Direct (connected to external networks backed by a VLAN port group), routed (including distributed), and isolated organization VDC networks

• Shared organization VDC networks

• Independent (named) disks

• Disk Level Storage Policy

• Fast provisioned VMs and vApps

• DHCP services support on isolated vApp networks

• DHCP services support the organization VDC networks (direct, isolated, and routed) and Dual stack (IPv4/IPv6 on the same vNIC) routed organization VDC networks

• Distributed firewall including static and dynamic group

  • Routed (including distributed), and isolated organization VDC networks
  • Organization VDC network directly connected to an external network which is migrated as imported networks (VLAN segment backed) to target Data Center Group

• Multiple ports on DFW services

• Distributed firewall rules with exclusion/negate enabled at the Source/Destination

• Routed vApp networks

• Non-Latin characters in the component’s name or description

Supported Edge Gateway Services

The NSX Migration for VMware Cloud Director tool supports the following edge gateway services:

• Following source and destination user-defined firewall rules objects are supported:
  • IP
  • IPSET
  • Routed organization VDC networks
• NAT44 rules
• BGP routing via a dedicated external network (Tier-0 or VRF gateway)

  Note BGP is not supported if Edge Gateway is not connected to a dedicated Tier-0/VRF.

• Policy-based IPSEC VPN with supported parameters for IPSEC with Pre-shared key or certificate based authentication
• IPSET in grouping objects
• DNS forwarding

  Note The DNS listener IP address will change after the migration. The new IP address will be updated in the organization VDC network's configuration but will not be applied in the guest operating system of already deployed VMs.

• Load balancing:
  • Supported Algorithms: round-robin and least connection
  • Supported Persistences: cookie and source IP
  • Supported IP types in virtual services : IPv4, IPv6
  • Transparent Mode:
    • Supported IP types in virtual services : IPv4
    • Supported IP types in pool members : IPv4
  • SSL Passthrough
• DHCP relay
• DHCP static binding
• Edge Gateway Rate Limits
• Org VDC networks that are not distributed but routed via SR

  Note If DNAT rule with translated IP from non distributed routed Org VDC network subnet is configured and there is also a firewall rule using the original destination IP, starting with version 1.4 the firewall rule is duplicated during the migration with the translated destination address. This ensures proper external connectivity as the service port on the Tier-1 gateway which is used the non distributed Org VDC network has its own firewall instance and the packets passing through have the translated destination IP.

• Static route migration where the next hop is either on the Org VDC network or an external network connected directly to Edge Gateway and not via Tier-0/VRF
• Advertise IPv6 subnets of Org VDC network