NSX Controllers becoming a one node NSX Controller cluster resulting in undefined datapath connectivity issues
Article ID: 321140
Updated On:
Products
VMware NSX
Issue/Introduction
Symptoms:
After running the initialize-control cluster command on all the NSX-T Controllers, you see this symptom:
Undefined datapath connectivity issues.
After running the initialize-control cluster command on all the NSX-T Controllers, you see this symptom:
Undefined datapath connectivity issues.
Environment
VMware NSX-T Data Center 2.x
VMware NSX-T Data Center
VMware NSX-T Data Center
Cause
This issue occurs when the initialize-control cluster command is run on all NSX-T Controllers, each of the Controller becomes a 1-node cluster which can cause undefined datapath connectivity issues.
VMware recommends when creating a controller cluster, you should run the initialize control-cluster command on only the first Controller, and then join the other Controllers to the cluster by running the join control-cluster command on the first Controller. For more information, see the NSX Controller Installation and Clustering section of the NSX-T Installation Guide.
VMware recommends when creating a controller cluster, you should run the initialize control-cluster command on only the first Controller, and then join the other Controllers to the cluster by running the join control-cluster command on the first Controller. For more information, see the NSX Controller Installation and Clustering section of the NSX-T Installation Guide.
Resolution
To resolve this issue, reconfigure your controller cluster as described in the NSX Controller Installation and Clustering section of the NSX-T Installation Guide.
Feedback
Yes
No
Powered by
