[ad_1]
In at the moment’s quickly evolving IT panorama, Cloud Service Providers want to make sure that their prospects have entry to the most recent and most superior networking and safety features. VMware Cloud Director (VCD) permits prospects to construct safe personal clouds, dramatically growing knowledge middle effectivity and enterprise agility.
Combined with VMware NSX (beforehand NSX-T Data Center or NSX-T), VMware’s software-defined networking platform, the result’s a strong answer for service suppliers and enterprises to assist the rising variety of distributed purposes being run on heterogenous endpoints, VMs, containers, and naked metallic throughout DC, Cloud, and Edge.
Why ought to we migrate VMware Cloud Director to VMware NSX (NSX-T)?
As per the present newest model (10.4.2), VCD nonetheless helps two choices for community virtualization: NSX Data Center for vSphere (NSX-V) and VMware NSX (formally referred to as NSX-T Data Center or NSX-T). However, NSX-V reached its End of General Support (EoGS) is January 16, 2022, and technical steerage on January 16, 2023. Therefore organizations should take proactive steps to mitigate safety dangers, preserve compliance, and proceed to leverage the advantages of community virtualization.
The migration course of might be complicated and must be deliberate and executed fastidiously to attenuate disruption and guarantee a profitable transition. Recently, VMware has launched model 1.4.2 of the VMware NSX Migration for VMware Cloud Director software, enhancing the assist of VCD networking options and permitting V2T migrations with minimal downtime.
VCD V2T Features and Migration Matrix
To assist Cloud Service Providers plan for a easy transition, this quick weblog supplies data on the present VCD NSX Features Support Matrix and people that may be auto-migrated utilizing the most recent NSX Migration for VCD software (1.4.2).
| Feature | NSX Data Center for vSphere (NSX-V) | VMware NSX (NSX-T) | NSX Migration for VCD software |
|---|---|---|---|
| Overlay community backing | VXLAN | GENEVE | Yes |
| Distributed Routing | Yes | Yes | Yes |
| Non-Distributed Routing | Yes | Yes (10.3.2) | Yes |
| External Network | Port teams; Logical Switches (digital wires) | Port teams; NSX Segments; Connection to exterior networks from Edge GW (10.4.1) | Yes |
| Provider Gateway | Not Applicable (N/A) | T0/VRF for Edge GW egress | Yes |
| Routed Network with NAT | Yes | Yes | Yes |
| Routed Network no NAT | Yes | Advertisement of routed community requires devoted Provider GW or IP Spaces. | Yes |
| Isolated Network | Yes | Yes | Yes |
| Direct Network | Yes | Yes | Yes |
| Imported Network | Unsupported | Yes | N/A |
| Shared Network | Yes | With Data Center Groups for non-directly linked Org VDC networks | Yes |
| IPv6 Network | Yes | Yes | Yes |
| Dual Stack (IPv4/IPv6 on similar vNIC) | Yes | Yes | Yes |
| Org VDC Edge GW | ESG | Tier-1 Gateway | Yes |
| IP handle sub-allocation | Provider managed | Provider managed or self-service with IP Spaces | Yes |
| Edge Firewall | Yes | Yes | Yes |
| NAT (NAT44) | Yes | Yes | Yes |
| NAT64 | Yes | Unsupported | N/A |
| DHCP | Yes | Yes | Yes |
| DHCPv6 | Unsupported | Yes | N/A |
| DNS Forwarding | Yes | Yes | Yes |
| BGP IPv4 | Yes | The Provider GW should be personal to a company or devoted to Tenant’s Edge GW. | Yes |
| BGP IPv6 | Unsupported | Yes | N/A |
| OSPF | Yes | Unsupported | N/A |
| VRF Lite | Unsupported | Yes | Yes |
| Static Routes | Yes | Static routes solely on Tier-1 GW, however not on Tier-0/VRF (10.4) | Yes |
| Policy-Based IPsec VPN | Yes | Yes | Yes |
| Route-Based IPsec VPN | Yes | Unsupported | N/A |
| L2 VPN | Yes | Yes (10.3) | NSX-T L2VPN isn’t backwards suitable with NSX-V L2VPN. The configuration of all L2VPN endpoints should be migrated manually. |
| SSL VPN | Yes | Unsupported by NSX-T. SSL VPN alternate options might be deployed, and the configuration migrated manually. Please test the VMware Cloud Director Remote Access VPN Integration Guide. | N/A |
| Load Balancing | Yes | Requires NSX Advanced Loadbalancer (Avi) | Yes |
| IPv6 Load Balancing | Yes | Requires NSX Advanced Loadbalancer (Avi) (10.4) | Yes |
| Edge logging and CLI | Yes | NSX-T Edge node is shared. CLI isn’t out there. Centralized logging with potential filtering. No tenant-dedicated logging. | N/A |
| Edge HA | Yes (Optional Active/Standby) | Yes | Yes |
| vApp Edge (routing, NAT, firewall) | Yes | Yes (10.3) Routed vApps can’t be linked to VLAN-backed Org VDC community |
Yes |
| vApp Edge Fencing | Yes | Unsupported | N/A |
| Distributed Firewall (L3/L4 and L7) | Yes | Requires VCD Data Center Group | Yes |
| Distributed Firewall (L2) | Yes | Unsupported | N/A |
| Cross VDC Networking (similar VCD) | Yes | Requires VCD Data Center Group; single egress solely | Unsupported |
| Cross VDC Network (totally different VCDs) | Yes | Unsupported | N/A |
| Edge placement | Yes (by way of API) | Edge Cluster granularity and by way of failure domains in NSX-T | Yes |
| Edge gateway charge limiting | Yes (exterior community granularity) | At the Edge GW stage (10.3.2). NSX-T Gateway Ingress/Egress QoC Profiles |
Yes |
| External community metering | Yes | Yes with Aria Operations | N/A |
| Segment Profile | Unsupported | Yes | N/A |
Are you curious about studying extra about NSX Migration for VCD software and course of? Do you could carry out a VCD NSX migration? Beneath are some reference sources that will help you all through the transition.
Docs and Blogs
Webinar Series
- Close the Technical NSX V to NSX T Skills Gap
- Part 1 Series: Modernize Your NSX Environment (3 Episodes, Level 100-300) Watch now on-demand
- Part 2 Series: Migrating Complex NSX-v Architectures (4 Episodes Level 300-400). Register for July 11-19 Series AMER/EMEA or APJ
Demos:
Conclusion
While VMware NSX Data Center for vSphere (6.4.x) continues to perform previous its EoGS date, bug fixes and safety patches for the particular model are discontinued. This can expose the infrastructure to vulnerabilities, making it essential for organizations to plan and execute an NSX-V to NSX-T transition for VMware Cloud Director environments.
In addition, migrating to NSX-T will preserve a robust integration to your VMware Cloud Director platform whereas enabling higher enterprise agility, cloud scalability, and community efficiency by supporting trendy distributed apps with a whole networking and safety stack.
Use the vcd-v2t-assist channel within the VMware Cloud Provider Slack workspace for additional questions or to supply your V2T migration expertise and suggestions. Additionally, the next FAQ solutions frequent questions regarding the VMware NSX Migration for VMware Cloud Director.