Hello,
We are trying to migrate (as compute and storage) all NSX components (NSX manager, ESG with HA, DLR control VM with HA and control cluster with 3 nodes) to a new cluster within the same vCenter Instance.
Our questions are as below:
- Which components can we move them using a normal vMotion/svMotion ?
- Which components need a redeploy to new cluster ? and How ?
Appreciated,
- NSX Manager can be moved via vMotion to the new cluster without problems.
- NSX Controller must be redeployed. If you have at least 2 controllers that can happen without downtime. Just delete the first one and create a new one in the new cluster. If it's successful deployed and connected, you can delete the second one and so on.
- NSX Edge Gateways and DLR must also be redeployed. This will require a minimal downtime because of a failover in a HA configuration. Just change the appliance configuration for each edge/dlr appliance under Manage > Settings > Configuration:
I would recommend that you first change the Standby appliance settings and if this edge node is redeployed, do the same for the active component. That way you only have 1 failover per edge/dlr.
For the sake of completeness I can tell you that a vMotion of Controller, Edges and DLR is basically possible. vSphere lets you do that. But it's only supported by NSX within a cluster. And if you do a vMotion in another cluster, the next time you upgrade or re-deploy these components, they will be deployed back in the original cluster, because this cluster configuration is defined in the settings.
For this reason, the only clean way is to reconfigure them, which will result in a re-deployment of the Edges and DLR and a short interruption.
- NSX Manager can be moved via vMotion to the new cluster without problems.
- NSX Controller must be redeployed. If you have at least 2 controllers that can happen without downtime. Just delete the first one and create a new one in the new cluster. If it's successful deployed and connected, you can delete the second one and so on.
- NSX Edge Gateways and DLR must also be redeployed. This will require a minimal downtime because of a failover in a HA configuration. Just change the appliance configuration for each edge/dlr appliance under Manage > Settings > Configuration:
I would recommend that you first change the Standby appliance settings and if this edge node is redeployed, do the same for the active component. That way you only have 1 failover per edge/dlr.
For the sake of completeness I can tell you that a vMotion of Controller, Edges and DLR is basically possible. vSphere lets you do that. But it's only supported by NSX within a cluster. And if you do a vMotion in another cluster, the next time you upgrade or re-deploy these components, they will be deployed back in the original cluster, because this cluster configuration is defined in the settings.
For this reason, the only clean way is to reconfigure them, which will result in a re-deployment of the Edges and DLR and a short interruption.
Thanks a lot, we will try these steps and get back to you.
Wonderful post !!
I applied these steps today, and it was perfect and successfully redeployed all components as mentioned.
There is a VMware KB on this Procedure to migrate NSX component VMs between vSphere clusters (2148350)
Thanks Bayu,
Also a helpful KB.