VMware Networking Community
rajeevsrikant
Expert
Expert
Jump to solution

NSX Controller - CDO Mode

I was going through the below document regarding the CDO mode.

In the document figure 12 & 13 is similar but it says that ping is successful in figure 12 & in figure 13 the ping has failed.

The diagram is the same for both figure 12 & 13 but why ping fails in figure 13.

VMware NSX-V: Control Plane Resiliency with CDO Mode

Tags (1)
0 Kudos
1 Solution

Accepted Solutions
bayupw
Leadership
Leadership
Jump to solution

In figure 12, there are 2 Hosts (Host1 and Host2) and 3 VMs (VM1, VM2 and VM3)

Initially, two VMs VM1 and VM2 were communicating in Host1 and there is another VM (VM3) on Host2.

Because of VM3, Host2 already part of the logical switch VNI 900002 prior NSX Controller Cluster failure (control plane loss).

Therefore, when VM2 vMotions to Host2 the communication continues to work (sucessful ping)

pastedImage_0.png

Now in the other picture figure 13, there is no VM3 on Host2 so initially Host2 was not part of the logical switch VNI 900002

When VM2 vMotions to Host2, NSX Controller cannot be notified that Host2 are now the new member of logical switch VNI 900002 and this is why Ping Fails.

pastedImage_2.png

This scenario can be handled by enabling CDO mode

Bayu Wibowo | VCIX6-DCV/NV
Author of VMware NSX Cookbook http://bit.ly/NSXCookbook
https://github.com/bayupw/PowerNSX-Scripts
https://nz.linkedin.com/in/bayupw | twitter @bayupw

View solution in original post

0 Kudos
1 Reply
bayupw
Leadership
Leadership
Jump to solution

In figure 12, there are 2 Hosts (Host1 and Host2) and 3 VMs (VM1, VM2 and VM3)

Initially, two VMs VM1 and VM2 were communicating in Host1 and there is another VM (VM3) on Host2.

Because of VM3, Host2 already part of the logical switch VNI 900002 prior NSX Controller Cluster failure (control plane loss).

Therefore, when VM2 vMotions to Host2 the communication continues to work (sucessful ping)

pastedImage_0.png

Now in the other picture figure 13, there is no VM3 on Host2 so initially Host2 was not part of the logical switch VNI 900002

When VM2 vMotions to Host2, NSX Controller cannot be notified that Host2 are now the new member of logical switch VNI 900002 and this is why Ping Fails.

pastedImage_2.png

This scenario can be handled by enabling CDO mode

Bayu Wibowo | VCIX6-DCV/NV
Author of VMware NSX Cookbook http://bit.ly/NSXCookbook
https://github.com/bayupw/PowerNSX-Scripts
https://nz.linkedin.com/in/bayupw | twitter @bayupw
0 Kudos