un preparing the vds_edge( edge cluster ) from the vxlan and preparing again the edge cluster for the vxlan with the vds in the production cluster. Tenants are deployed through the VCD 9.7 and cross NSX 6.4.3 is used.

[malihafayyaz]

In our environment we have ESXI version 6.5.0 update 13635690 , NSX 6.4.3 and VCD 9.7.0.13634630. We have tenants that are deployed through the VCD. In our production data centre we have two cluster IAASEMEDGE101 and IAASEMPRD101 both have their separate VDS and prepared for the VXLAN traffic respectively. Now the requirement is to have one vDS across both the cluster. As the NSX environment is cross so we are using the UDLR feature from the VCD. The ESG’s are deployed through the VCD and using the external vxlan network that is created on vDS in edge cluster. So in the change the vDS in edge cluster will be unprepared for vxlan, the host uplinks will be connected to the vDS in the payload cluster and then the edge cluster will be again prepared for the vxlan.
Now the questions related to this change are
1- As it is a cross NSX environment with VCD which site to do first the Primary or the secondary. Keeping in mind that the tenants are deployed through VCD and we are also using the UDLR from the VCD
2- As the VCD is using the external networks which are basically logical switches created on the vds_edge. Can we edit the properties of the external network and change the logical switch that is on the vds_edge to the logical switch which is on the vds_payload. Note: as there is a transport zone that is spanning both the clusters, so when a logical switch is created it is created on both the vDS. ( what will be downtime if the external network is change or impact)
3- Is there any other dependency on the VCD that needs to be looked upon other than the external network and what will be the proper steps to remove the external network dependency in VCD
4- The NSX Edges that are using the vxlan interfaces. What is the proper step to remove the VXLAN dependency either by starting all the configuration from the scratch, or by vmotion to the production cluster, do the change and then vmotion it to the old cluster or by redeploying? Which is the safest method.
5- what will be the effect on the UDLR that is deployed through the VCD how can we vmotion or redeploy to another cluster and what will be the effect on the VCD
6- what will be the effect on the UDLR that is deployed through the VCD how can we vmotion or redeploy to another cluster and what will be the effect on the VCD. The HA status of all the UDLR that are deployed from the down. The UDLR is not active at the secondary site. If we vmotion it to the other cluster what will be the effect and vice versa.
7- Any effect on the transport zone.?

We did this change in our other cloud last year but at that time there were no UDLR configured at that time and no ESG’s were deployed through the VCD. Now this time we have tenants that are deployed through VCD and using UDLR ( which is also configured through the VCD).

[Sreec]

1- As it is a cross NSX environment with VCD which site to do first the Primary or the secondary. Keeping in mind that the tenants are deployed through VCD and we are also using the UDLR from the VCD

    Do you have similar cluster architecture for both the sites ie Edge and payload cluster design ? 

2- As the VCD is using the external networks which are basically logical switches created on the vds_edge. Can we edit the properties of the external network and change the logical switch that is on the vds_edge to the logical switch which is on the vds_payload. Note: as there is a transport zone that is spanning both the clusters, so when a logical switch is created it is created on both the vDS. ( what will

be downtime if the external network is change or impact)

During the phase of external network change , there will be a downtime for VM traffic based on the traffic type (External/Internal or backup traffic) Another option would be to create Edges on payload cluster and ensure accurate VLAN mapping is done End-End , and simply migrate the VCD networks to new edges which are in payload . Take care of your static/dynamic routes along with firewall changes at physical/virtual network for seamless migration.

3- Is there any other dependency on the VCD that needs to be looked upon other than the external network and what will be the proper steps to remove the external network dependency in VCD

      External network movement should be fine as long as there are no connected entities from VCD perspective.

4- The NSX Edges that are using the vxlan interfaces. What is the proper step to remove the VXLAN dependency either by starting all the configuration from the scratch, or by vmotion to the production cluster, do the change and then vmotion it to the old cluster or by redeploying? Which is the safest method.

Like i said in the earlier comment, either you can create new edges and simply disconnect/reconnect the networks to new edges . Or you can migrate the edges to payload .  Do check VCD storage profiles and payload cluster storage mappings , this will decide if vmotion or SVMOTION is possible.

5- what will be the effect on the UDLR that is deployed through the VCD how can we vmotion or redeploy to another cluster and what will be the effect on the VCD

6- what will be the effect on the UDLR that is deployed through the VCD how can we vmotion or redeploy to another cluster and what will be the effect on the VCD. The HA status of all the UDLR that are deployed from the down. The UDLR is not active at the secondary site. If we vmotion it to the other cluster what will be the effect and vice versa.

UDLR/Edges have same dependency from NSX perspective , ensure payload cluster is in same transport zone as edge cluster . From VCD perspective ensure Edge transit VLANs are working for new clusters. 

7- Any effect on the transport zone.?

I don't think you need to change any transport zone settings as long as both the clusters are part of same transport zone.

[malihafayyaz]

Thanks for the reply. I appreciate the time that you have put in answering the question.

1-  Yes we have similar cluster architecture for both the sites ie Edge and payload cluster design.

2- yes that is one option to configure all the NSX on the EDge cluster but it will require a lot of configuration. i was looking at the Redeploy or the Vmotion option ?

3- Regarding the External network, some of the ESG are using the logical switches as the external network ( and these external network are on the vds_edge). so before un preparing the vds_edge for the vxlan, can we edit the external network setting and assign the logical switch that is created on the vds_production and the same case to be applied to the ORG VDC network as they will also based on logical switch.

7- From the transport zone i have to exclude the edge cluster after the change.

Thanks

Maliha Fayyaz

[Sreec]

1-  Yes we have similar cluster architecture for both the sites ie Edge and payload cluster design.

In that case I would recommend doing the cluster remapping on secondary NSX site , followed by primary.

2- yes that is one option to configure all the NSX on the EDge cluster but it will require a lot of configuration. i was looking at the Redeploy or the Vmotion option ?

Yes, you can certainly migrate the machines. Remember that , payload cluster is visible to same VCD tenant , simply migrating the objects from vSphere will break VCD managed objects functionality.

3- Regarding the External network, some of the ESG are using the logical switches as the external network ( and these external network are on the vds_edge). so before un preparing the vds_edge for the vxlan, can we edit the external network setting and assign the logical switch that is created on the vds_production and the same case to be applied to the ORG VDC network as they will also based on logical switch.

Yes , there is a move to option in VCD . Either you can use that functionally to migrate the networks between edges or just create new logical switch and map to migrated edges.

7- From the transport zone i have to exclude the edge cluster after the change.

Yes, after the change you can certainly exclude the same.