VMware NSX Migration for VMware Cloud Director 1.3.1 | 30 NOV 2021

Check for additions and updates to these release notes.

What's New

The NSX Migration for VMware Cloud Director tool version 1.3.1 supports several new features:

  • DHCP static binding (if the bound IP does not overlap existing DHCP pool addresses)
  • DHCP relay on the Edge Gateway
  • Cross vCenter migration (migration to a target NSX-T provider VDC managed by a different vCenter Server instance)
  • Clone overlay ID (VNI) from the source VXLAN logical switch backed organization VDC network to the target Org VDC network Geneve backed NSX-T segment
  • Enhanced network pool support
    • Port group backed network pool
    • Network pool backed by multiple VDS (vSphere Distributed Switches)
    • Migration of organization VDC without network pool
  • IPsec VPN enhancement: certificate based authentication, SHA-256 digest algorithm
  • Route advertisement enhancements for fully routed network topology
  • VMs using automated IP Pool address assignment will retain their IP address after the migration
  • Updated assessment mode for unsupported Edge Gateway features: SSH, Syslog, and GRE tunnel
  • Option to choose target network pool if multiple Geneve network pools exist
  • DHCP lease time value of more than 7200 seconds for isolated organization VDC networks

Known Issues

  • Rollback Fails at ‘Reset the target external network’

Step:

[vcdOperations]:[resetTargetExternalNetwork]:3911 [INFO] [VDC-demo]| Rollback:Reset the target external network

Exception:

Failed to reset the target external network 'external-network-name' to its initial state: [ xx-xx-xx-xx-xx] The provided list 'ipRanges.values' should have at least one item in it.

Reason: During rollback the migration tool removes the IP address/s used by the target edge gateway from the target external network. If the target external network has no spare IP in its static IP Pool apart from the ones used by target edge gateway/s, then the migration tool won’t be able to remove the IPs as a minimum of one IP should be present in every subnet of an external network.

Workaround: Add additional IP(s) to the static IP pool of the target external network and run the rollback.

  • Cleanup Fails at ‘Updating the source External network’

Step:

[vcdNSXMigratorCleanup]:[run]:3542 [INFO] [VDC-demo]| Updating the source External network.

Exception:

Failed to update source external network ‘external-network-name' : [ xx-xx-xx-xx-xx] The provided list 'ipRanges.values' should have at least one item in it.

Reason: During cleanup, the migration tool removes the IP address/s used by the source edge gateway from the source external network. If the source external network has no spare IP in its static IP Pool apart from the ones used by source edge gateway/s, then the migration tool won’t be able to remove the IPs as a minimum of one IP should be present in every subnet of an external network.

Workaround: Will need to clean IP/s manually from static IP Pool of source external network in case of failure.

  • vApp network directly connected to Org VDC network scoped to DC group renaming failure

vApp network directly connected to Org VDC network scoped to DC group is not renamed when the parent network is renamed during cleanup.

Affected VMware Cloud Director version: 10.3.0

Fixed in: VMware Cloud Director 10.3.1

  • VM loses N-S traffic after rollback

After rollback is completed, VMs may lose N-S connectivity. VM loses N-S traffic following vMotion to an NSX for vSphere host after NSX-v to NSX-T Edge migration cutover was done.

Fixed in NSX-T 3.1.3.3 (for more details, see NSX-T Release Notes).

  • Migration of VM having multiple disks with different storage policies fails

Step:

[vcdOperations]:[moveVappApiCall]:3714 [INFO] [Disk-Test]| Moving vApp – vApp-test to target Org VDC - Disk-Test-v2t

Exception:

Failed to move vApp – vApp-test with errors [ 5d7588d9-a62c-4308-9c86-8dbbf5f35564 ] Cannot find VDC storage policy "ef057b95-8e06-4320-a9a2-409fc86d2a7d" in VDC "88594b4a-ca19-478c- af88-9734b485458d"

Workaround: None

  • After migration to NSX-T, NAT rules are not editable through VMware Cloud Director UI

After the migration is completed, the NAT rules created at target are not editable using VMware Cloud Director UI. A lock symbol can be seen while selecting NAT rules.

Workaround: Use VMware Cloud Director API to edit the NAT rules. Issue fixed in VMware Cloud Director 10.3.2.

  • VMs connected to distributed Org VDC networks lose network connectivity after N-S network switchover

VMs connected to distributed Org VDC networks lose network connectivity after N-S network switchover and bridging does not work.

Workaround: Ensure that the MAC Address of the NSX-T Virtual Distributed Router is using a different MAC address than the NSX-V distributed logical router. For more details, see NSX-T documentation.

check-circle-line exclamation-circle-line close-line
Scroll to top icon