NSX Migration for Cloud Director 1.3.2 with Routed vApp Community Migration

Developed by the Cloud Infrastructure Enterprise Group (CIBG), the VMware NSX Migration for VMware Cloud Director is THE answer you’re in search of emigrate NSX for vSphere to NSX-T in case you are working a VMware Cloud Director setting: it’s an exterior automation instrument that initiates and full the migration course of with minimal downtime.

We’re thrilled to announce that the VMware NSX Migration for VMware Cloud Director 1.3.2 model is now typically accessible!

To always enhance your means emigrate from NSX for vSphere to NSX-T, this seventh iteration of the NSX Migration for Cloud Director brings a number of key migration capabilities:

• Assist for routed vApp community migration (together with vApp edge networking providers)
• UTF-8 characters assist emigrate VMware Cloud Director objects having names and descriptions with particular characters or non-Latin-based languages
• Assist for Edge Gateway Charge Limits migration
• Non-Distributed Routing assist with NSX-T Knowledge Middle
• Enhanced Direct Community Migration
• Normal enhancements and value (see beneath for extra particulars)
• Up to date evaluation mode

Please verify the VMware NSX Migration for VMware Cloud Director 1.3.2 launch notes for an in depth checklist.

Routed vApp Networks Migration

vApps are a core function in VMware Cloud Director and helpful for grouping VMs for utility wants. vApps networks can both be constructed with or with out providers. Networks with out providers are both easy remoted vApp networks or direct vApp networks (i.e., a logical extension of a corporation VDC community). Nonetheless, vApp networks can be configured with firewall, NAT, static routing, and DHCP providers. These providers are used to created vApps with community safety and isolation, successfully encapsulating its members.

Networks configured with providers are sometimes known as routed vApp networks; a typical use case for routed vApp networks is for dev/take a look at environments. Remoted networks can be configured with DHCP providers.

VMware Cloud Director 10.3 launched the assist for routed vApp networks (a.ok.a. vApp Edge providers) for NSX-T backed group digital information middle: vApp edges are deployed as standalone Tier-1 gateways related to an overlay group VDC community through a service interface.

Beginning with model 1.3.2, the NSX migration for Cloud Director helps the migration of routed vApp networks with the next concerns:

• This function requires VMware Cloud Director 10.3.2.1 or newer
• vApp edges can solely be related to overlay-backed group VDC networks (thus, routed vApp mum or dad community can’t be a immediately related org VDC community)
• Routed vApp community shouldn’t be supported with different sorts of networks in the identical vApp

Normal Enhancements & Usability

This 1.3.2 launch consists of many different new options, however the aim is to not undergo all gadgets on this weblog put up. Whereas some could appear minor, their quantity and advantages carry higher flexibility and migration expertise.

• Non-Distributed Routing with NSX-T Knowledge Middle: now you can allow non-distributed routing on routed group VDC networks (such networks are related through service interface on to service router of Tier-1 gateway). Non-distributed routing shall be enabled on group VDC networks routed through an inside interface in one of many following two instances.
  • Explicitly through setting enter parameter NonDistributedNetworks within the YAML file.
  • Implicitly if DNS relay is enabled and DNS IP is similar as Default Gateway IP. This along with auto-configured DNAT of Default Gateway IP to DNS Forwarder IP will obtain the supply of DNS providers on the identical IP for migrated VMs.
• Enhanced Direct Community Migration: you at the moment are capable of pressure migration of immediately related group VDC networks to a distinct exterior community with -v2t suffix for service community use case.
• A number of Tier-0 Gateways Assist: you will have an choice to specify particular person Tier-0 Gateways for every Edge Gateway in Org VDC. It’s now not obligatory to attach all goal Edge Gateways to a single Tier-0 Gateway.
• Renamed ExternalNetwork toTier0Gateways: ExternalNetwork subject within the person enter YAML file which specifies the NSX-T Tier-0 Gateway is renamed to Tier0Gateways to match the identify within the VMware Cloud Director person interface.
• Elective Tier0Gateways and DummyExternalNetwork: these two fields in person enter YAML might be skipped if edge gateways usually are not current on the NSX for vSphere backed Org VDC.
• Visitor VLAN migration: routed Org VDC networks and routed vApp networks might be migrated with the Visitor VLAN possibility enabled.
• Disk Degree Storage Coverage assist: you’ll be able to migrate VMs with disks having totally different storage insurance policies.
• Enhanced Named Disk Migration: you’ll be able to migrate named/impartial disks connected to powered-on VMs with out powering off these VMs. Named disks with totally different storage insurance policies may also be migrated
• Replace evaluation mode to take into accounts options that at the moment are supported.

Abstract

The VMware NSX Migration for Cloud Director 1.3.2 is now typically accessible and brings the assist to routed vApp networks migration but in addition many further options.

We proceed to enhance the eventualities and the tooling to assist our VMware Cloud Suppliers Companions emigrate VMware Cloud Director from NSX for vSphere to NSX-T. Please don’t wait and take the benefit to redo an automated evaluation utilizing this newest model to see the way it improves your functionality emigrate. 😉

This migration instrument has a distinct launch cycle than VMware Cloud Director, and we have now already began growing the following model.

You might be inspired to proceed offering suggestions to assist us resolve how the instrument ought to evolve. We might love to listen to about you, both within the feedback part beneath, in social media (@woueb), within the #vcd-v2t-assist channel on the VMware Cloud Supplier Slack workspace, or through your VMware consultant.

Extra assets: