[ad_1]
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 continually enhance your potential 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:
- Help for routed vApp community migration (together with vApp edge networking companies)
- UTF-8 characters assist emigrate VMware Cloud Director objects having names and descriptions with particular characters or non-Latin-based languages
- Help for Edge Gateway Price Limits migration
- Non-Distributed Routing assist with NSX-T Information Heart
- Enhanced Direct Community Migration
- Normal enhancements and value (see beneath for extra particulars)
- Up to date evaluation mode
Please examine the VMware NSX Migration for VMware Cloud Director 1.3.2 launch notes for an in depth listing.
Routed vApp Networks Migration
vApps are a core characteristic in VMware Cloud Director and helpful for grouping VMs for software wants. vApps networks can both be constructed with or with out companies. Networks with out companies are both easy remoted vApp networks or direct vApp networks (i.e., a logical extension of a company VDC community). Nevertheless, vApp networks will also be configured with firewall, NAT, static routing, and DHCP companies. These companies are used to created vApps with community safety and isolation, successfully encapsulating its members.
Networks configured with companies are usually known as routed vApp networks; a typical use case for routed vApp networks is for dev/check environments. Remoted networks will also be configured with DHCP companies.
VMware Cloud Director 10.3 launched the assist for routed vApp networks (a.okay.a. vApp Edge companies) for NSX-T backed group digital information heart: vApp edges are deployed as standalone Tier-1 gateways linked to an overlay group VDC community by way of 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 issues:
- This characteristic requires VMware Cloud Director 10.3.2.1 or newer
- vApp edges can solely be linked to overlay-backed group VDC networks (thus, routed vApp mum or dad community can’t be a immediately linked org VDC community)
- Routed vApp community isn’t supported with different kinds of networks in the identical vApp
Normal Enhancements & Usability
This 1.3.2 launch consists of many different new options, however the objective is to not undergo all objects on this weblog publish. Whereas some could seem minor, their quantity and advantages carry higher flexibility and migration expertise.
- Non-Distributed Routing with NSX-T Information Heart: now you can allow non-distributed routing on routed group VDC networks (such networks are linked by way of service interface on to service router of Tier-1 gateway). Non-distributed routing can be enabled on group VDC networks routed by way of an inside interface in one of many following two instances.
- Explicitly by way of setting enter parameter NonDistributedNetworks within the YAML file.
- Implicitly if DNS relay is enabled and DNS IP is identical as Default Gateway IP. This along with auto-configured DNAT of Default Gateway IP to DNS Forwarder IP will obtain the supply of DNS companies on the identical IP for migrated VMs.
- Enhanced Direct Community Migration: you are actually capable of drive migration of immediately linked group VDC networks to a unique exterior community with -v2t suffix for service community use case.
- A number of Tier-0 Gateways Help: you’ve got an choice to specify particular person Tier-0 Gateways for every Edge Gateway in Org VDC. It’s now not necessary to attach all goal Edge Gateways to a single Tier-0 Gateway.
- Renamed ExternalNetwork toTier0Gateways: ExternalNetwork subject within the consumer enter YAML file which specifies the NSX-T Tier-0 Gateway is renamed to Tier0Gateways to match the title within the VMware Cloud Director consumer interface.
- Optionally available Tier0Gateways and DummyExternalNetwork: these two fields in consumer enter YAML may be skipped if edge gateways should not current on the NSX for vSphere backed Org VDC.
- Visitor VLAN migration: routed Org VDC networks and routed vApp networks may be migrated with the Visitor VLAN possibility enabled.
- Disk Stage 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/unbiased disks connected to powered-on VMs with out powering off these VMs. Named disks with totally different storage insurance policies may even be migrated
- Replace evaluation mode to take into accounts options that are actually 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 additionally many further options.
We proceed to enhance the situations 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 unique launch cycle than VMware Cloud Director, and we’ve got 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 by way of your VMware consultant.
Further assets:
[ad_2]
