VMware NSX-V end of life is set to January 15, 2024; please refer to the email sent in July/August 2023 to find out how to migrate. For technical complements, please consult our guides.
This guide helps you to analyze your use of NSX-V features and offers you different evolution scenarios: from disabling the NSX-V component to migrating to its successor, NSX-T (named NSX by VMware since version 4.0).
Identifying your NSX-V usage
To identify your usage of the NSX-V feature in your Hosted Private Cloud environment, you have to ask yourself the following questions:
- Am I using VXLAN?
- Am I using a Distributed Firewall rules?
- Am I using a Distributed Logical Router or an Edge Services Gateway?
- Am I using an IPsec VPN?
I do not use any of the NSX-V features
If you do not use any of the above features, you will be able to deactivate NSX-V. You will be notified when the deactivation process is available.
I only use VXLAN
If the only feature you use is VXLAN, you have the following choice:
- Migrating to NSX (see details below), or
- Reconfiguring your network in order to replace VXLAN with VLAN.
If you wish to migrate to VLAN, to help you configure your network, you can use this API call to generate a mapping between VXLAN to VLAN:
serviceName: the reference for your PCC as
To create your VLAN networks, you can follow this documentation: VLAN Creation.
You will then need to disable NSX-V. You will be notified when the deactivation process is available. After the previous operations, you can now migrate your Virtual Machines from the VXLANs to the vRack DVS.
From the Network view in the vSphere UI, right-click on the VXLAN portgroup where your virtual machines are located and select
Migrate VMs to Another Network....
NOTE: In this example, we will migrate the VMs to the VLAN10 portgroup, which is located on the vRack. You must migrate all VMs to portgroups in order to disable NSX-V (or if OVHcloud detects that NSX-V is not in use).
Complete your operation and reproduce this for each used vxlan portgroup.
VMs will only experience a very brief reconnection. In some cases, this may only be the loss of a single ping request.
You will then have to deactivate NSX-V. You will be notified when the deactivation process is available.
I use some of the NSX-V features
We recommend migrating to NSX (see details below) to benefit from all its included features.
Alternatively, you can decide to deploy alternative components (Load-balancer, Firewall appliance, VPN, etc.) and then disable NSX-V (you will be notified when the deactivation process is available).
Migrating to NSX
The NSX software is enabled at the Virtual Datacenter (vDC) level. In order to migrate from NSX-V to NSX, you can order a new vDC for your existing Hosted Private Cloud service (feature will be available soon), add new Hosts, and then migrate from your current vDC to the new vDC using VMware vMotion.
The documentation to migrate to NSX is not yet available.
Our support teams and Sales Engineers can provide you with assistance when the migration is available.