View source for Lab: NSX Manager deployment (Single site)

<div class="page-body">

'''Lab: NSX Manager deployment''' (Single site)

In this lab I am working with the following software and versions:

{| class="wikitable simple-table"
|-
! Software
! Version
! Filename
|-
| VMware vCenter Server Appliance
| 7.00U3G
| VMware-VCSA-all-7.0.3-20150588.iso
|-
| VMware ESXi Server
| 7.00U3F
| VMware-VMvisor-Installer-7.0U3f-20036589.x86_64.iso
|-
| VMware NSX
| 4.0.0.1
| nsx-unified-appliance-4.0.0.1.0.20159694.ova
|}

<ol style="list-style-type: decimal;">
<li>Deploy three NSX Manager Nodes and make sure they operate in a cluster.
<ol style="list-style-type: lower-alpha;">
<li>Do not use any external load balancers.</li></ol>
</li></ol>

<ol start="2" style="list-style-type: decimal;">
<li>Add a valid license to NSX.</li></ol>

<div id="341efff9-004f-4af1-8bcf-69597126cbcc" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/12/Untitled.png

</div>
<span id="76e3cdda-4936-4d9a-8170-ee3a6dc77ba2"></span>
= The Steps =

*<span class="far fa-regular fa-square"> STEP 0: Make sure a DNS server [[Lab:Install and configure a DNS Server using BIND]] and an vSphere SDDC infrastructure [[Lab:Install and configure a (nested) vSphere SDDC]] is deployed</span>
*<span class="far fa-regular fa-square"> STEP 1: Deploy the first NSX Manager</span>
*<span class="far fa-regular fa-square"> STEP 2: Add the NSX License</span>
*<span class="far fa-regular fa-square"> STEP 3: Add a Compute Manager</span>
*<span class="far fa-regular fa-square"> STEP 4: Deploy the second and third NSX Manager to form an NSX Manager Cluster</span>
*<span class="far fa-regular fa-square"> STEP 5: Configure the NSX VIP IP Address</span>


<span id="748e78f6-e87a-4bf0-8015-6edeaad12baf"></span>
= STEP 1: Deploy the first NSX Manager =

The NSX Manager can be deployed using the vCenter Server or an ESXi host. I will describe both.

For the deployment the following configuration parameters are required:

<div id="d0bacc6c-47f3-4408-8ff7-02458d26e247" class="collection-content">

<span id="section"></span>
====  ====

{| class="wikitable collection-content"
|-
! Parameter Name
! Input
|-
| vSphere Cluster
| Management
|-
| VM Name
| Pod-120-NSXT-LM-1
|-
| Storage
| Management_vSAN
|-
| Network (Port Group)
| Management
|-
| System Root User Password
| VMware1!VMware1!
|-
| CLI "admin" User Password
| VMware1!VMware1!
|-
| CLI "audit" User Password
| VMware1!VMware1!
|-
| Hostname
| Pod-120-NSXT-LM-1
|-
| Rolename
| NSX Manager
|-
| Management Network IPv4 Address
| 10.203.120.12
|-
| Management Network Netmask
| 255.255.255.0
|-
| Default IPv4 Gateway
| 10.203.120.1
|-
| DNS Server list
| 10.203.0.5
|-
| Domain Search List
| sddc.lab
|-
| NTP Server List
| 10.203.0.5
|-
| Enable SSH
| yes
|-
| Allow root SSH logins
| yes
|}

</div>
<span id="bee5fb39-c9ab-47a9-b1c7-e435155ea086"></span>
== Deploying the first NSX Manager using vCenter Server ==

Let’s start with the vCenter Server.

Right-click the vSphere cluster where I want to deploy the NSX Manager to and select “'''Deploy OVF Template'''”.

<div id="477b5313-e346-4c6d-be7c-d8d5f7f9076f" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/12/Untitled%201.png

</div>
Select “Local File” and select the NSX OVA file that I downloaded from the VMware website.

<div id="1c1b9b1e-86b5-4b77-8b86-e2707cc36b71" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/12/Untitled%202.png

</div>
Specify a Virtual Machine Name.

<div id="ca4d35c4-9304-456f-abf8-57ac425d741b" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/12/Untitled%203.png

</div>
Specify the compute resource.

<div id="fd071f6a-3781-4b0f-9a50-65e4758640f2" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/12/Untitled%204.png

</div>
Review the details.

<div id="59d68a66-663b-4125-825a-d281c8d0d2c6" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/12/Untitled%205.png

</div>
Specify a deployment size.

<div id="a0687f73-7ca5-4e90-bbff-87474d35f79a" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/12/Untitled%206.png

</div>
Specify the storage.

<div id="206afbec-c2a6-4c88-a0d0-980e1d2ef8de" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/12/Untitled%207.png

</div>
Specify the network.

<div id="f70929d3-8cf8-4c81-841a-b07c380f7e5a" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/12/Untitled%208.png

</div>
Specify the parameters as per this table.

<div id="5fa899c4-8f1e-472f-bd11-243c6cf3b6f5" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/12/Untitled%209.png

</div>
⚠️ In the customise template section there are some parameters that are not used for this deployment, I can just leave those blank and only use the parameters I specified above as these are required for a successful deployment.

Review the details and click on “'''Finish'''” to start the deployment.

<div id="5b30d170-724e-4f3f-8985-9cb117f953f6" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/12/Untitled%2010.png

</div>
In the “Recent Tasks” section in the vCenter Server I can track the deployment status.

<div id="05d511e4-80ae-4473-932e-8c7e971cc1de" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/12/Untitled%2011.png

</div>
When the deployment is finished I need to turn on the NSX Manager VM by right-clicking on the VM and select '''Power → Power On.'''

<div id="6df730a0-a99c-4976-b739-40a31ee8593b" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/12/Untitled%2012.png

</div>
The NSX Manager VM is now powered on.

<div id="664aa213-8c3c-48b3-8569-b6fb713e590d" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/12/Untitled%2013.png

</div>
<span id="bc1e2f3f-7d64-4e15-a6be-220336c36b3f"></span>
== Deploying the first NSX Manager using ESXi Server ==

Another way to deploy the fist NSX Manager Node is to do the deployment on an ESXi host. Click on “'''Create/Register VM'''”

<div id="d79f32ac-9fbc-4fed-8d58-0dafaefff766" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/12/Untitled%2014.png

</div>
Select “'''Deploy a virtual machine from an OVF file'''”.

<div id="6c6dc8ac-93a6-43de-ad5d-db625e924575" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/12/Untitled%2015.png

</div>
Specify a Virtual Machine Name and select the NSX OVA file that I downloaded from the VMware website.

<div id="308b84d4-1826-4052-a152-a2a3e94a2e51" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/12/Untitled%2016.png

</div>
Specify the storage.

<div id="fe570938-3441-4318-aabc-0d45f55bc20a" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/12/Untitled%2017.png

</div>
Specify the network and specify a deployment size. Make sure the VM is powered on automatically.

<div id="d2be43b8-91fe-4dc2-9aa7-503a43002962" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/12/Untitled%2018.png

</div>
Specify the parameters as per this table:

<div id="e09bc1fc-c10b-4381-a108-29ae34e88646" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/12/Untitled%2019.png

</div>
Review the details and click on “'''Finish'''” to start the deployment.

<div id="132a0976-688a-471b-aaf3-92b1d8cf5fc7" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/12/Untitled%2020.png

</div>
In the “Recent Tasks” section in the ESXi Server I can track the deployment status.

<div id="1978f1cf-270c-4245-8429-141bc9549f59" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/12/Untitled%2021.png

</div>
Verify if the VM is powered on.

<div id="6addfc26-6ce3-4fb8-9f55-374126feda21" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/12/Untitled%2022.png

</div>
<span id="908df3eb-88aa-4478-86dd-a021491b1178"></span>
== Log in for the first time ==

Now that the first NSX Manager Node is deployed I can log in to the GUI.

<div id="63e74306-c9ba-4953-a023-eca364e67594" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/12/Untitled%2023.png

</div>
Accept the End User Licence Agreement.

<div id="7cca44fe-2e69-4afe-bf9c-aba1d9b75a55" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/12/Untitled%2024.png

</div>
Specify if I want to join the “Customer Experience Improvement Program”.

<div id="fd887fb7-af97-4184-bd28-da818a4c38c5" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/12/Untitled%2025.png

</div>
NSX 4.0.0.1 has a “Welcome wizard” to point out where I can find what. Click on “'''Next'''”.

<div id="2e4ec440-fe30-4309-a6b2-e643f7b2300d" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/12/Untitled%2026.png

</div>
The wizard point out “Networking”.

<div id="a6d208fa-1152-44fa-bf5a-8b9386a78346" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/12/Untitled%2027.png

</div>
The wizard point out “Security”.

<div id="330f35e3-0fc2-4b93-977b-dbce3bf2c00c" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/12/Untitled%2028.png

</div>
The wizard point out “Plan &amp; Troubleshoot”.

<div id="136793c8-bc68-4c03-9fa3-f8942656ed63" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/12/Untitled%2029.png

</div>
The wizard point out “System”. Click the box “'''Don’t show this again'''” and “'''Got it'''”.

<div id="ae177d8f-6be5-438f-91a2-7479516203ad" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/12/Untitled%2030.png

</div>
Now that the first NSX Manager Node is deployed and I am logged in I will see a blue bar at the top to inform that a license needs to be added.

<div id="79ca1dd2-ddcd-4988-aba8-f277c4b08e1d" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/12/Untitled%2031.png

</div>
<span id="0076e9cf-fc6f-4b5c-84b4-bf94ae3ad6e4"></span>
= STEP 2: Add the NSX License =

<div id="7dea3293-fde9-44c4-b5a5-889ff876b9a7" class="collection-content">

<span id="section-1"></span>
====  ====

{| class="wikitable collection-content"
|-
! Product
! License key
|-
| VMware NSX
| <code>3M2U7-XXXXX-XXXXX-XXXXX-XXXXX</code>
|}

</div>
I can either click on the “Manage Licences” button in the blue top bar.

<div id="e8f21be4-086c-4b84-ae09-90e828af2728" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/12/Untitled%2032.png

</div>
Or I can go to '''System → Settings → Licences''' and click on “Add License”.

<div id="c259c703-73ac-4ad8-8e8c-75776c2bbe76" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/12/Untitled%2033.png

</div>
Add the license.

<div id="6611cdc2-f26a-45d0-aca6-4c0b999bd19c" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/12/Untitled%2034.png

</div>
Verify if the license is added.

<div id="817e2621-730d-464e-959a-cadf90a381f5" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/12/Untitled%2035.png

</div>
<span id="4c48d165-71fe-41c4-bd21-f109192dfadf"></span>

= STEP 3: Add a Compute Manager =

To prepare ESXi hosts to be an NSX Host Transport Node I need to add a Compute Manager. This is also needed if I want to deploy NSX Edge Transport Nodes and additional NSX Manager Nodes (to form an NSX Manager Cluster” using the NSX GUI.

I add a compute manager by going to '''System → Configuration → Fabric → Compute Managers''' → and click on “Add Compute Manager”.

<div id="b8aef4e5-6732-40e5-a4f8-eecabeadb762" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/12/Untitled%2036.png

</div>
Use the following parameters to add the Compute Manager and click on “'''Add'''” when I am finished.

<div id="a8274a9d-b467-4b74-868d-29233221f542" class="collection-content">

<span id="section-2"></span>
====  ====

{| class="wikitable collection-content"
|-
! Parameter Name
! Input
|-
| Name
| pod-120-vcenter.sddc.lab
|-
| FQDN or IP Address
| pod-120-vcenter.sddc.lab
|-
| Username
| administrator@vsphere.local
|-
| Password
| VMware1!
|-
| Enable Trust
| Yes
|-
| Access Level
| Full Access
|}

</div>
<div id="0c6b7d39-0725-4fae-ad61-5e6a20a1eb26" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/12/Untitled%2037.png

</div>
When I click “'''Save'''” I get a message to add the missing Fingerprint of the vCenter server. Click on “'''Add'''”.

<div id="d9fde9f3-6260-4723-8021-944cbf784a37" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/12/Untitled%2038.png

</div>
After I clicked on add I will see that the add is “In Progress”.

<div id="20312724-d0ae-4b0a-9a8a-6e2f48865294" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/12/Untitled%2039.png

</div>
Look for the “Registered” and “Up” status when the Compute Manager is added successfully.

<div id="21c5d1da-4b66-4d1a-89d7-e3ed3346cd7f" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/12/Untitled%2040.png

</div>
<div id="0eb4ac22-0b9a-49c6-9681-4f9165302e75" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/12/Untitled%2041.png

</div>
<span id="09d9bb41-6593-4141-b42f-ab631af03273"></span>

= STEP 4: Deploy the second and third NSX Manager to form an NSX Manager Cluster =

To form an NSX Manager Cluster I need two additional NSX Manager Nodes. These Manager Nodes can be deployed manually and added to the cluster using some CLI commands, or I can deploy the NSX Manager Nodes from the first NSX Manager Node’s GUI (Compute Manager configuration is required for this).

<span id="86db1ded-8d42-410f-8cf2-ac9560f09ed9"></span>
== Deploy the second and third NSX Manager to form an NSX Manager Cluster 〈using the CLI〉 | Using the NSX Manager standalone deployments ==

Let’s start with the manual deployment of the second and third NSX Manager Nodes. Just for demonstration purposes I will also deploy these new NSX Manager Nodes in a different IP range (network) then the first one.

<div id="4e7cd56f-2fff-4f67-8a23-cf2f9d105c33" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/12/Untitled%2042.png

</div>
The table below will contain all the configuration parameters that I will need to deploy the second and third NSX Manager Node manually.

<div id="56d5deb2-0774-4d1a-a19e-56e30f2df933" class="collection-content">

<span id="section-3"></span>
====  ====

{| class="wikitable collection-content"
|-
! Parameter Name
! Input Second Node
! Input Third Node
|-
| vSphere Cluster
| N/A
| N/A
|-
| VM Name
| Pod-120-NSXT-LM-2
| Pod-120-NSXT-LM-3
|-
| Storage
| ESX-02-DS-01
| ESX-02-DS-01
|-
| Network (Port Group)
| Lab-Routers
| Lab-Routers
|-
| System Root User Password
| VMware1!VMware1!
| VMware1!VMware1!
|-
| CLI "admin" User Password
| VMware1!VMware1!
| VMware1!VMware1!
|-
| CLI "audit" User Password
| VMware1!VMware1!
| VMware1!VMware1!
|-
| Hostname
| Pod-120-NSXT-LM-2
| Pod-120-NSXT-LM-3
|-
| Rolename
| NSX Manager
| NSX Manager
|-
| Management Network IPv4 Address
| 10.203.0.11
| 10.203.0.12
|-
| Management Network Netmask
| 255.255.255.0
| 255.255.255.0
|-
| Default IPv4 Gateway
| 10.203.0.1
| 10.203.0.1
|-
| DNS Server list
| 10.203.0.5
| 10.203.0.5
|-
| Domain Search List
| sddc.lab
| sddc.lab
|-
| NTP Server List
| 10.203.0.5
| 10.203.0.5
|-
| Enable SSH
| yes
| yes
|-
| Allow root SSH logins
| yes
| yes
|}

</div>
When I look at the NSX Home screen I will see the warning “'''3 node cluster recommended'''”.

When I click on “Deploy Nodes” it will take me to the Appliances screen.

<div id="da459b3c-d3bb-4d46-91f1-c5eeea111ade" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/12/Untitled%2043.png

</div>
I can also manually browse to the Appliances screen by browsing to '''System → Configuration → Appliances'''.

<div id="d467367e-b7bc-414c-896a-985402ccfdf3" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/12/Untitled%2044.png

</div>
Notice that only one Node is listed.

<span id="efca2b3b-e7a2-4de8-85cb-c7373a50e299"></span>
=== Get information from the first NSX Manager Node ===

Make note of the IP address of the first NSX Manager Node.

<pre class="code">Pod-120-NSXT-LM-1&gt; get interface eth0
Wed Aug 24 2022 UTC 13:28:29.070
Interface: eth0
  IPv4 Address:
    Address: 10.203.120.12/24
    MAC address: 00:0c:29:75:b4:14
    MTU: 1500
    Default gateway: 10.203.120.1
    Broadcast address: 10.203.120.255
  Link status: up
  Admin status: up
  RX packets: 104708
  RX bytes: 13665374
  RX errors: 0
  RX dropped: 0
  TX packets: 16258
  TX bytes: 26292049
  TX errors: 0
  TX dropped: 0
  TX collisions: 0

Pod-120-NSXT-LM-1&gt;</pre>
Make note of the certificate thumbprint of the first NSX Manager Node.

<pre class="code">Pod-120-NSXT-LM-1&gt; get certificate api thumbprint
Wed Aug 24 2022 UTC 13:31:23.839
bb0e0933b21052d8a29fac65d6a250877ed2cefb913033ccb962bd79bcae0a46

Pod-120-NSXT-LM-1&gt;</pre>
Make note of the Cluster ID.

<pre class="code">Pod-120-NSXT-LM-1&gt; get cluster config
Wed Aug 24 2022 UTC 13:31:38.069
Cluster Id: 7262902c-d10a-4c40-a1d4-d24f737ccfaa
Cluster Configuration Version: 0
Number of nodes in the cluster: 1

Node UUID: fd0e4d56-4c33-0e61-8bff-9d8a1375b414
Node Status: JOINED
    ENTITY                               UUID                                       IP ADDRESS        IPV6 ADDRESS
              PORT     FQDN
    HTTPS                                9834c769-e08c-48de-beb9-d2d2509e1d0d       10.203.120.12     -
              443      Pod-120-NSXT-LM-1.SDDC.Lab
    ASYNC_REPLICATOR                     f8da85a9-66dd-4566-ac32-bd9f99644b9c       10.203.120.12     -
              -        Pod-120-NSXT-LM-1.SDDC.Lab
    CONTROLLER                           2b97a266-fa0d-4c38-b857-e88552aa5c13       10.203.120.12     -
              -        Pod-120-NSXT-LM-1.SDDC.Lab
    CLUSTER_BOOT_MANAGER                 fbca4c2f-28c3-4ce3-8452-9dfe04a91272       10.203.120.12     -
              -        Pod-120-NSXT-LM-1.SDDC.Lab
    CM-INVENTORY                         a18a55d1-8889-4352-912d-c340eb00a03d       10.203.120.12     -
              -        Pod-120-NSXT-LM-1.SDDC.Lab
    DATASTORE                            7de9e729-c7ea-482c-8014-7a613fe13e8b       10.203.120.12     -
              9000     Pod-120-NSXT-LM-1.SDDC.Lab
    CORFU_NONCONFIG                      26c912bd-0fb4-4067-961d-737e34521744       10.203.120.12     -
              9040     Pod-120-NSXT-LM-1.SDDC.Lab
    IDPS_REPORTING                       a1a10066-1508-4923-a197-fff5fc3b759b       10.203.120.12     -
              -        Pod-120-NSXT-LM-1.SDDC.Lab
    MESSAGING-MANAGER                    e6be3d88-5ebf-435e-8609-700929a427b6       10.203.120.12     -
              -        Pod-120-NSXT-LM-1.SDDC.Lab
    MONITORING                           f9dd4b01-2581-4d12-b4b2-4b09938657c3       10.203.120.12     -
              -        Pod-120-NSXT-LM-1.SDDC.Lab
    MANAGER                              4360cb53-c2b4-467a-8e24-e96b44a846ea       10.203.120.12     -
              -        Pod-120-NSXT-LM-1.SDDC.Lab
    SITE_MANAGER                         f9373036-1629-452b-b9e9-6470f06243ce       10.203.120.12     -
              -        Pod-120-NSXT-LM-1.SDDC.Lab
    UPGRADE_COORDINATOR                  c75bb26e-7151-46a9-a3e0-9235fccd05ac       10.203.120.12     -
              -        Pod-120-NSXT-LM-1.SDDC.Lab

Pod-120-NSXT-LM-1&gt;</pre>
All the items I just made a note of are listed in the configuration parameters in the table below, and are required to join the new Nodes to the first Node.

<div id="d705cdbe-b1d9-4fee-80ea-1dbab791f173" class="collection-content">

<span id="section-4"></span>
====  ====

{| class="wikitable collection-content"
|-
! Parameter Name
! Input
|-
| IP address
| 10.203.120.12
|-
| Cluster ID
| <span class="mark highlight-yellow_background">'''7262902c-d10a-4c40-a1d4-d24f737ccfaa'''</span>
|-
| User name
| admin
|-
| Password
| VMware1!VMware1!
|-
| Certificate thumbprint
| <span class="mark highlight-yellow_background">'''bb0e0933b21052d8a29fac65d6a250877ed2cefb913033ccb962bd79bcae0a46'''</span>
|}

</div>
<span id="4f33d9f1-b003-454a-aa6e-5d8a2927c7a0"></span>

=== Add the second NSX Manager Node ===

The deployment of the second / third NSX Manager Node can be done using the [https://www.iwanhoogendoorn.nl/index.php/Lab:_NSX_Manager_deployment_(Single_site) vCenter Server] or [https://www.iwanhoogendoorn.nl/index.php/Lab:_NSX_Manager_deployment_(Single_site) ESXi Server] deployments described earlier.

Join the second NSX Manager Node to the first Node (cluster).

<pre class="code">Pod-120-NSXT-LM-2&gt; join 10.203.120.12 cluster-id 7262902c-d10a-4c40-a1d4-d24f737ccfaa username admin password VMware1!VMware1! thumbprint bb0e0933b21052d8a29fac65d6a250877ed2cefb913033ccb962bd79bcae0a46
Data on this node will be lost. Are you sure? (yes/no): yes
Join operation successful. Services are being restarted. Cluster may take some time to stabilize.

Pod-120-NSXT-LM-2&gt;</pre>
After I have issued the join command I can look at the Appliances screen to track the progress. During the join I might see some strange outputs like the one, but patience is key.

<div id="939eb981-8ad1-49bb-ae6c-7750432a5a7f" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/12/Untitled%2045.png

</div>
Joining and cluster stabilising will take around 15 minutes to finish.

<div id="80679e26-6f0b-4675-99cb-c8bddd7251bb" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/12/Untitled%2046.png

</div>
When the join is completed I will now have an NSX Manager Cluster with two NSX Manager Nodes.

I can issue the following CLI commands to verify is the status is “UP” for all the services.

<div class="collapsible">
    <div class="collapsible-alone-header">Pod-120-NSXT-LM-1&gt; <code>get cluster status</code></div>
   <div class="collapsible-content">
<pre class="code">Pod-120-NSXT-LM-1&gt; get cluster status
Wed Aug 24 2022 UTC 13:51:50.382
Cluster Id: 7262902c-d10a-4c40-a1d4-d24f737ccfaa
Overall Status: STABLE

Group Type: DATASTORE
Group Status: STABLE

Members:
    UUID                                       FQDN                                       IP               STATUS
    fd0e4d56-4c33-0e61-8bff-9d8a1375b414       Pod-120-NSXT-LM-1.SDDC.Lab                 10.203.120.12    UP
    18cd2242-02f0-c2b9-68b8-0d70ff3d2aaf       Pod-120-NSXT-LM-2                          10.203.0.11      UP

Group Type: CLUSTER_BOOT_MANAGER
Group Status: STABLE

Members:
    UUID                                       FQDN                                       IP               STATUS
    fd0e4d56-4c33-0e61-8bff-9d8a1375b414       Pod-120-NSXT-LM-1.SDDC.Lab                 10.203.120.12    UP
    18cd2242-02f0-c2b9-68b8-0d70ff3d2aaf       Pod-120-NSXT-LM-2                          10.203.0.11      UP

Group Type: CONTROLLER
Group Status: STABLE

Members:
    UUID                                       FQDN                                       IP               STATUS
    2b97a266-fa0d-4c38-b857-e88552aa5c13       Pod-120-NSXT-LM-1.SDDC.Lab                 10.203.120.12    UP
    d0b3e07c-7d41-452c-9adf-2ae794797551       Pod-120-NSXT-LM-2                          10.203.0.11      UP

Group Type: MANAGER
Group Status: STABLE

Members:
    UUID                                       FQDN                                       IP               STATUS
    fd0e4d56-4c33-0e61-8bff-9d8a1375b414       Pod-120-NSXT-LM-1.SDDC.Lab                 10.203.120.12    UP
    18cd2242-02f0-c2b9-68b8-0d70ff3d2aaf       Pod-120-NSXT-LM-2                          10.203.0.11      UP

Group Type: HTTPS
Group Status: STABLE

Members:
    UUID                                       FQDN                                       IP               STATUS
    fd0e4d56-4c33-0e61-8bff-9d8a1375b414       Pod-120-NSXT-LM-1.SDDC.Lab                 10.203.120.12    UP
    18cd2242-02f0-c2b9-68b8-0d70ff3d2aaf       Pod-120-NSXT-LM-2                          10.203.0.11      UP

Group Type: MONITORING
Group Status: STABLE

Members:
    UUID                                       FQDN                                       IP               STATUS
    fd0e4d56-4c33-0e61-8bff-9d8a1375b414       Pod-120-NSXT-LM-1.SDDC.Lab                 10.203.120.12    UP
    18cd2242-02f0-c2b9-68b8-0d70ff3d2aaf       Pod-120-NSXT-LM-2                          10.203.0.11      UP

Group Type: MESSAGING-MANAGER
Group Status: STABLE

Members:
    UUID                                       FQDN                                       IP               STATUS
    fd0e4d56-4c33-0e61-8bff-9d8a1375b414       Pod-120-NSXT-LM-1.SDDC.Lab                 10.203.120.12    UP
    18cd2242-02f0-c2b9-68b8-0d70ff3d2aaf       Pod-120-NSXT-LM-2                          10.203.0.11      UP

Group Type: SITE_MANAGER
Group Status: STABLE

Members:
    UUID                                       FQDN                                       IP               STATUS
    fd0e4d56-4c33-0e61-8bff-9d8a1375b414       Pod-120-NSXT-LM-1.SDDC.Lab                 10.203.120.12    UP
    18cd2242-02f0-c2b9-68b8-0d70ff3d2aaf       Pod-120-NSXT-LM-2                          10.203.0.11      UP

Group Type: CM-INVENTORY
Group Status: STABLE

Members:
    UUID                                       FQDN                                       IP               STATUS
    fd0e4d56-4c33-0e61-8bff-9d8a1375b414       Pod-120-NSXT-LM-1.SDDC.Lab                 10.203.120.12    UP
    18cd2242-02f0-c2b9-68b8-0d70ff3d2aaf       Pod-120-NSXT-LM-2                          10.203.0.11      UP

Group Type: IDPS_REPORTING
Group Status: STABLE

Members:
    UUID                                       FQDN                                       IP               STATUS
    fd0e4d56-4c33-0e61-8bff-9d8a1375b414       Pod-120-NSXT-LM-1.SDDC.Lab                 10.203.120.12    UP
    18cd2242-02f0-c2b9-68b8-0d70ff3d2aaf       Pod-120-NSXT-LM-2                          10.203.0.11      UP

Group Type: CORFU_NONCONFIG
Group Status: STABLE

Members:
    UUID                                       FQDN                                       IP               STATUS
    fd0e4d56-4c33-0e61-8bff-9d8a1375b414       Pod-120-NSXT-LM-1.SDDC.Lab                 10.203.120.12    UP
    18cd2242-02f0-c2b9-68b8-0d70ff3d2aaf       Pod-120-NSXT-LM-2                          10.203.0.11      UP

Pod-120-NSXT-LM-1&gt;</pre></div></div>

<div class="collapsible">
    <div class="collapsible-alone-header">Pod-120-NSXT-LM-2&gt; <code>get cluster status</code></div>
   <div class="collapsible-content">
<pre class="code">Pod-120-NSXT-LM-2&gt; get cluster status
Wed Aug 24 2022 UTC 13:51:10.907
Cluster Id: 7262902c-d10a-4c40-a1d4-d24f737ccfaa
Overall Status: STABLE

Group Type: DATASTORE
Group Status: STABLE

Members:
    UUID                                       FQDN                                       IP               STATUS
    fd0e4d56-4c33-0e61-8bff-9d8a1375b414       Pod-120-NSXT-LM-1.SDDC.Lab                 10.203.120.12    UP
    18cd2242-02f0-c2b9-68b8-0d70ff3d2aaf       Pod-120-NSXT-LM-2                          10.203.0.11      UP

Group Type: CLUSTER_BOOT_MANAGER
Group Status: STABLE

Members:
    UUID                                       FQDN                                       IP               STATUS
    fd0e4d56-4c33-0e61-8bff-9d8a1375b414       Pod-120-NSXT-LM-1.SDDC.Lab                 10.203.120.12    UP
    18cd2242-02f0-c2b9-68b8-0d70ff3d2aaf       Pod-120-NSXT-LM-2                          10.203.0.11      UP

Group Type: CONTROLLER
Group Status: STABLE

Members:
    UUID                                       FQDN                                       IP               STATUS
    2b97a266-fa0d-4c38-b857-e88552aa5c13       Pod-120-NSXT-LM-1.SDDC.Lab                 10.203.120.12    UP
    d0b3e07c-7d41-452c-9adf-2ae794797551       Pod-120-NSXT-LM-2                          10.203.0.11      UP

Group Type: MANAGER
Group Status: STABLE

Members:
    UUID                                       FQDN                                       IP               STATUS
    fd0e4d56-4c33-0e61-8bff-9d8a1375b414       Pod-120-NSXT-LM-1.SDDC.Lab                 10.203.120.12    UP
    18cd2242-02f0-c2b9-68b8-0d70ff3d2aaf       Pod-120-NSXT-LM-2                          10.203.0.11      UP

Group Type: HTTPS
Group Status: STABLE

Members:
    UUID                                       FQDN                                       IP               STATUS
    fd0e4d56-4c33-0e61-8bff-9d8a1375b414       Pod-120-NSXT-LM-1.SDDC.Lab                 10.203.120.12    UP
    18cd2242-02f0-c2b9-68b8-0d70ff3d2aaf       Pod-120-NSXT-LM-2                          10.203.0.11      UP

Group Type: SITE_MANAGER
Group Status: STABLE

Members:
    UUID                                       FQDN                                       IP               STATUS
    fd0e4d56-4c33-0e61-8bff-9d8a1375b414       Pod-120-NSXT-LM-1.SDDC.Lab                 10.203.120.12    UP
    18cd2242-02f0-c2b9-68b8-0d70ff3d2aaf       Pod-120-NSXT-LM-2                          10.203.0.11      UP

Group Type: CM-INVENTORY
Group Status: STABLE

Members:
    UUID                                       FQDN                                       IP               STATUS
    fd0e4d56-4c33-0e61-8bff-9d8a1375b414       Pod-120-NSXT-LM-1.SDDC.Lab                 10.203.120.12    UP
    18cd2242-02f0-c2b9-68b8-0d70ff3d2aaf       Pod-120-NSXT-LM-2                          10.203.0.11      UP

Group Type: IDPS_REPORTING
Group Status: STABLE

Members:
    UUID                                       FQDN                                       IP               STATUS
    fd0e4d56-4c33-0e61-8bff-9d8a1375b414       Pod-120-NSXT-LM-1.SDDC.Lab                 10.203.120.12    UP
    18cd2242-02f0-c2b9-68b8-0d70ff3d2aaf       Pod-120-NSXT-LM-2                          10.203.0.11      UP

Group Type: MONITORING
Group Status: STABLE

Members:
    UUID                                       FQDN                                       IP               STATUS
    fd0e4d56-4c33-0e61-8bff-9d8a1375b414       Pod-120-NSXT-LM-1.SDDC.Lab                 10.203.120.12    UP
    18cd2242-02f0-c2b9-68b8-0d70ff3d2aaf       Pod-120-NSXT-LM-2                          10.203.0.11      UP

Group Type: MESSAGING-MANAGER
Group Status: STABLE

Members:
    UUID                                       FQDN                                       IP               STATUS
    fd0e4d56-4c33-0e61-8bff-9d8a1375b414       Pod-120-NSXT-LM-1.SDDC.Lab                 10.203.120.12    UP
    18cd2242-02f0-c2b9-68b8-0d70ff3d2aaf       Pod-120-NSXT-LM-2                          10.203.0.11      UP

Group Type: CORFU_NONCONFIG
Group Status: STABLE

Members:
    UUID                                       FQDN                                       IP               STATUS
    fd0e4d56-4c33-0e61-8bff-9d8a1375b414       Pod-120-NSXT-LM-1.SDDC.Lab                 10.203.120.12    UP
    18cd2242-02f0-c2b9-68b8-0d70ff3d2aaf       Pod-120-NSXT-LM-2                          10.203.0.11      UP

Pod-120-NSXT-LM-2&gt;</pre></div></div>

<span id="7a5275e8-e8e6-411a-9b63-682e751b6c87"></span>

=== Add the third NSX Manager Node ===

When the join is completed I will now have an NSX Manager Cluster with two NSX Manager Nodes.

<div id="062aff30-eca6-4719-80aa-7ee24d074fb2" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/12/Untitled%2046.png

</div>
Join the third NSX Manager Node to the first and second Nodes (cluster).

<pre class="code">Pod-120-NSXT-LM-3&gt; join 10.203.120.12 cluster-id 7262902c-d10a-4c40-a1d4-d24f737ccfaa username admin password VMware1!VMware1! thumbprint bb0e0933b21052d8a29fac65d6a250877ed2cefb913033ccb962bd79bcae0a46
Data on this node will be lost. Are you sure? (yes/no): yes
Join operation successful. Services are being restarted. Cluster may take some time to stabilize.

Pod-120-NSXT-LM-3&gt;</pre>
After I have issued the join command I can look at the Appliances screen to track the progress. During the join I might see some strange outputs like the one, but patience is key.

<div id="7bf3e148-faa6-4ba7-9381-096283bbbee9" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/12/Untitled%2047.png

</div>
Joining and cluster stabilising will take around 15 minutes to finish.

<div id="1a94cb77-54db-4582-afa6-a078b83742fd" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/12/Untitled%2048.png

</div>
When the join is completed I will now have an NSX Manager Cluster with three NSX Manager Nodes.

I can issue the following CLI commands to verify is the status is “UP” for all the services.

<div class="collapsible">
    <div class="collapsible-alone-header">Pod-120-NSXT-LM-1&gt; <code>get cluster config</code></div>
   <div class="collapsible-content">
<pre class="code">Pod-120-NSXT-LM-1&gt; get cluster config
Wed Aug 24 2022 UTC 16:30:36.385
Cluster Id: 7262902c-d10a-4c40-a1d4-d24f737ccfaa
Cluster Configuration Version: 2
Number of nodes in the cluster: 3

Node UUID: fd0e4d56-4c33-0e61-8bff-9d8a1375b414
Node Status: JOINED
    ENTITY                               UUID                                       IP ADDRESS        IPV6 ADDRESS
              PORT     FQDN
    HTTPS                                9834c769-e08c-48de-beb9-d2d2509e1d0d       10.203.120.12     -
              443      Pod-120-NSXT-LM-1.SDDC.Lab
    ASYNC_REPLICATOR                     f8da85a9-66dd-4566-ac32-bd9f99644b9c       10.203.120.12     -
              -        Pod-120-NSXT-LM-1.SDDC.Lab
    CONTROLLER                           2b97a266-fa0d-4c38-b857-e88552aa5c13       10.203.120.12     -
              -        Pod-120-NSXT-LM-1.SDDC.Lab
    CLUSTER_BOOT_MANAGER                 fbca4c2f-28c3-4ce3-8452-9dfe04a91272       10.203.120.12     -
              -        Pod-120-NSXT-LM-1.SDDC.Lab
    CM-INVENTORY                         a18a55d1-8889-4352-912d-c340eb00a03d       10.203.120.12     -
              -        Pod-120-NSXT-LM-1.SDDC.Lab
    DATASTORE                            7de9e729-c7ea-482c-8014-7a613fe13e8b       10.203.120.12     -
              9000     Pod-120-NSXT-LM-1.SDDC.Lab
    CORFU_NONCONFIG                      26c912bd-0fb4-4067-961d-737e34521744       10.203.120.12     -
              9040     Pod-120-NSXT-LM-1.SDDC.Lab
    IDPS_REPORTING                       a1a10066-1508-4923-a197-fff5fc3b759b       10.203.120.12     -
              -        Pod-120-NSXT-LM-1.SDDC.Lab
    MESSAGING-MANAGER                    e6be3d88-5ebf-435e-8609-700929a427b6       10.203.120.12     -
              -        Pod-120-NSXT-LM-1.SDDC.Lab
    MONITORING                           f9dd4b01-2581-4d12-b4b2-4b09938657c3       10.203.120.12     -
              -        Pod-120-NSXT-LM-1.SDDC.Lab
    MANAGER                              4360cb53-c2b4-467a-8e24-e96b44a846ea       10.203.120.12     -
              -        Pod-120-NSXT-LM-1.SDDC.Lab
    SITE_MANAGER                         f9373036-1629-452b-b9e9-6470f06243ce       10.203.120.12     -
              -        Pod-120-NSXT-LM-1.SDDC.Lab
    UPGRADE_COORDINATOR                  c75bb26e-7151-46a9-a3e0-9235fccd05ac       10.203.120.12     -
              -        Pod-120-NSXT-LM-1.SDDC.Lab

Node UUID: 18cd2242-02f0-c2b9-68b8-0d70ff3d2aaf
Node Status: JOINED
    ENTITY                               UUID                                       IP ADDRESS        IPV6 ADDRESS
              PORT     FQDN
    HTTPS                                6bd094ec-9407-4495-9cd0-b03c155ade9a       10.203.0.11       -
              443      Pod-120-NSXT-LM-2
    ASYNC_REPLICATOR                     b783c086-2da7-4289-a4c4-da8123b9d736       10.203.0.11       -
              -        Pod-120-NSXT-LM-2
    CONTROLLER                           d0b3e07c-7d41-452c-9adf-2ae794797551       10.203.0.11       -
              -        Pod-120-NSXT-LM-2
    CLUSTER_BOOT_MANAGER                 f2e77537-ad26-4595-b4ff-8ecccd03888b       10.203.0.11       -
              -        Pod-120-NSXT-LM-2
    CM-INVENTORY                         1ed1f723-dfdc-4ab5-8840-c55cfc3a59e0       10.203.0.11       -
              -        Pod-120-NSXT-LM-2
    DATASTORE                            c20a9bba-425f-425e-a703-089e77717763       10.203.0.11       -
              9000     Pod-120-NSXT-LM-2
    CORFU_NONCONFIG                      9e3be29c-8bb4-484c-aa6a-65fc45f21587       10.203.0.11       -
              9040     Pod-120-NSXT-LM-2
    IDPS_REPORTING                       f9cc923e-824f-4624-b838-26e0c56b2c6b       10.203.0.11       -
              -        Pod-120-NSXT-LM-2
    MESSAGING-MANAGER                    17c8b927-b9cc-4028-a3cf-56ba1774dfb7       10.203.0.11       -
              -        Pod-120-NSXT-LM-2
    MONITORING                           b7772420-d816-4e93-b644-f264c4d00b30       10.203.0.11       -
              -        Pod-120-NSXT-LM-2
    MANAGER                              ea97278a-08ba-48a0-a722-59647d84bdd8       10.203.0.11       -
              -        Pod-120-NSXT-LM-2
    SITE_MANAGER                         07d56dd4-d38f-4952-b60b-69bd8991a9b1       10.203.0.11       -
              -        Pod-120-NSXT-LM-2
    UPGRADE_COORDINATOR                  fd59bb19-10f2-462e-90fe-b35353ef31ec       10.203.0.11       -
              -        Pod-120-NSXT-LM-2

Node UUID: eeda2242-6b5d-cf12-64bf-e825bf9128ab
Node Status: JOINED
    ENTITY                               UUID                                       IP ADDRESS        IPV6 ADDRESS
              PORT     FQDN
    HTTPS                                24a5c202-305c-45ca-bb7a-c3a6a5fc8e7b       10.203.0.12       -
              443      Pod-120-NSXT-LM-3
    ASYNC_REPLICATOR                     689b1f67-7858-4f29-8e28-dbfaf4840b14       10.203.0.12       -
              -        Pod-120-NSXT-LM-3
    CONTROLLER                           52f97c28-411a-4d59-8783-5b85247e1f94       10.203.0.12       -
              -        Pod-120-NSXT-LM-3
    CLUSTER_BOOT_MANAGER                 076b18e7-6f30-4918-baea-024c0c7c1edd       10.203.0.12       -
              -        Pod-120-NSXT-LM-3
    CM-INVENTORY                         7556c130-b0b3-4918-89ca-f242bdaf6514       10.203.0.12       -
              -        Pod-120-NSXT-LM-3
    DATASTORE                            4ea6a3d0-1db0-49ed-9214-db4f63b928e6       10.203.0.12       -
              9000     Pod-120-NSXT-LM-3
    CORFU_NONCONFIG                      fb9dfa79-4aee-4d3a-84c5-3daa300ff4ab       10.203.0.12       -
              9040     Pod-120-NSXT-LM-3
    IDPS_REPORTING                       31342a00-c53d-482e-ae97-792eb9cae196       10.203.0.12       -
              -        Pod-120-NSXT-LM-3
    MESSAGING-MANAGER                    1b74454e-da8a-432a-a71f-02af8838849a       10.203.0.12       -
              -        Pod-120-NSXT-LM-3
    MONITORING                           83993414-3aa3-4fca-99ff-cedb368ad9bc       10.203.0.12       -
              -        Pod-120-NSXT-LM-3
    MANAGER                              66d3718f-405d-4e7d-8909-7daccbd2a856       10.203.0.12       -
              -        Pod-120-NSXT-LM-3
    SITE_MANAGER                         ddbe38a3-908d-4795-adeb-0f526ff8802b       10.203.0.12       -
              -        Pod-120-NSXT-LM-3
    UPGRADE_COORDINATOR                  80cc3089-ed2c-49eb-8324-2a47771fd0f7       10.203.0.12       -
              -        Pod-120-NSXT-LM-3

Pod-120-NSXT-LM-1&gt;</pre></div></div>

<div class="collapsible">
    <div class="collapsible-alone-header">Pod-120-NSXT-LM-1&gt; <code>get cluster status</code></div>
   <div class="collapsible-content">
<pre class="code">Pod-120-NSXT-LM-1&gt; get cluster status
Wed Aug 24 2022 UTC 16:30:37.295
Cluster Id: e0681397-166e-4b49-9a3c-74fc1df3e9d1
Overall Status: STABLE

Group Type: DATASTORE
Group Status: STABLE

Members:
    UUID                                       FQDN                                       IP               STATUS
    a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       Pod-120-NSXT-LM-1.SDDC.Lab                 10.203.120.12    UP
    09d4df47-f293-4ea7-8173-92a320fed685       Pod-120-NSXT-LM-2                          10.203.120.13    UP
    f77633c9-69f2-41a2-b3f8-b14c96a7bec5       Pod-120-NSXT-LM-3                          10.203.120.14    UP

Group Type: CLUSTER_BOOT_MANAGER
Group Status: STABLE

Members:
    UUID                                       FQDN                                       IP               STATUS
    a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       Pod-120-NSXT-LM-1.SDDC.Lab                 10.203.120.12    UP
    09d4df47-f293-4ea7-8173-92a320fed685       Pod-120-NSXT-LM-2                          10.203.120.13    UP
    f77633c9-69f2-41a2-b3f8-b14c96a7bec5       Pod-120-NSXT-LM-3                          10.203.120.14    UP

Group Type: CONTROLLER
Group Status: STABLE

Members:
    UUID                                       FQDN                                       IP               STATUS
    81e59552-30ba-4cff-9540-1eda464c0072       Pod-120-NSXT-LM-1.SDDC.Lab                 10.203.120.12    UP
    537c5d50-a89e-4f93-933f-d94c75e1b5cd       Pod-120-NSXT-LM-2                          10.203.120.13    UP
    1826609d-288d-4b21-87da-1a9aeb3a07a4       Pod-120-NSXT-LM-3                          10.203.120.14    UP

Group Type: MANAGER
Group Status: STABLE

Members:
    UUID                                       FQDN                                       IP               STATUS
    a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       Pod-120-NSXT-LM-1.SDDC.Lab                 10.203.120.12    UP
    09d4df47-f293-4ea7-8173-92a320fed685       Pod-120-NSXT-LM-2                          10.203.120.13    UP
    f77633c9-69f2-41a2-b3f8-b14c96a7bec5       Pod-120-NSXT-LM-3                          10.203.120.14    UP

Group Type: HTTPS
Group Status: STABLE

Members:
    UUID                                       FQDN                                       IP               STATUS
    a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       Pod-120-NSXT-LM-1.SDDC.Lab                 10.203.120.12    UP
    09d4df47-f293-4ea7-8173-92a320fed685       Pod-120-NSXT-LM-2                          10.203.120.13    UP
    f77633c9-69f2-41a2-b3f8-b14c96a7bec5       Pod-120-NSXT-LM-3                          10.203.120.14    UP

Group Type: IDPS_REPORTING
Group Status: STABLE

Members:
    UUID                                       FQDN                                       IP               STATUS
    a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       Pod-120-NSXT-LM-1.SDDC.Lab                 10.203.120.12    UP
    09d4df47-f293-4ea7-8173-92a320fed685       Pod-120-NSXT-LM-2                          10.203.120.13    UP
    f77633c9-69f2-41a2-b3f8-b14c96a7bec5       Pod-120-NSXT-LM-3                          10.203.120.14    UP

Group Type: MONITORING
Group Status: STABLE

Members:
    UUID                                       FQDN                                       IP               STATUS
    a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       Pod-120-NSXT-LM-1.SDDC.Lab                 10.203.120.12    UP
    09d4df47-f293-4ea7-8173-92a320fed685       Pod-120-NSXT-LM-2                          10.203.120.13    UP
    f77633c9-69f2-41a2-b3f8-b14c96a7bec5       Pod-120-NSXT-LM-3                          10.203.120.14    UP

Group Type: CM-INVENTORY
Group Status: STABLE

Members:
    UUID                                       FQDN                                       IP               STATUS
    a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       Pod-120-NSXT-LM-1.SDDC.Lab                 10.203.120.12    UP
    09d4df47-f293-4ea7-8173-92a320fed685       Pod-120-NSXT-LM-2                          10.203.120.13    UP
    f77633c9-69f2-41a2-b3f8-b14c96a7bec5       Pod-120-NSXT-LM-3                          10.203.120.14    UP

Group Type: MESSAGING-MANAGER
Group Status: STABLE

Members:
    UUID                                       FQDN                                       IP               STATUS
    a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       Pod-120-NSXT-LM-1.SDDC.Lab                 10.203.120.12    UP
    09d4df47-f293-4ea7-8173-92a320fed685       Pod-120-NSXT-LM-2                          10.203.120.13    UP
    f77633c9-69f2-41a2-b3f8-b14c96a7bec5       Pod-120-NSXT-LM-3                          10.203.120.14    UP

Group Type: SITE_MANAGER
Group Status: STABLE

Members:
    UUID                                       FQDN                                       IP               STATUS
    a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       Pod-120-NSXT-LM-1.SDDC.Lab                 10.203.120.12    UP
    09d4df47-f293-4ea7-8173-92a320fed685       Pod-120-NSXT-LM-2                          10.203.120.13    UP
    f77633c9-69f2-41a2-b3f8-b14c96a7bec5       Pod-120-NSXT-LM-3                          10.203.120.14    UP

Group Type: CORFU_NONCONFIG
Group Status: STABLE

Members:
    UUID                                       FQDN                                       IP               STATUS
    a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       Pod-120-NSXT-LM-1.SDDC.Lab                 10.203.120.12    UP
    09d4df47-f293-4ea7-8173-92a320fed685       Pod-120-NSXT-LM-2                          10.203.120.13    UP
    f77633c9-69f2-41a2-b3f8-b14c96a7bec5       Pod-120-NSXT-LM-3                          10.203.120.14    UP

Pod-120-NSXT-LM-1&gt;</pre></div></div>

<div class="collapsible">
    <div class="collapsible-alone-header">Pod-120-NSXT-LM-2&gt; <code>get cluster config</code></div>
   <div class="collapsible-content">
<pre class="code">Pod-120-NSXT-LM-2&gt; get cluster config
Wed Aug 24 2022 UTC 16:30:59.819
Cluster Id: 7262902c-d10a-4c40-a1d4-d24f737ccfaa
Cluster Configuration Version: 2
Number of nodes in the cluster: 3

Node UUID: fd0e4d56-4c33-0e61-8bff-9d8a1375b414
Node Status: JOINED
    ENTITY                               UUID                                       IP ADDRESS        IPV6 ADDRESS
              PORT     FQDN
    HTTPS                                9834c769-e08c-48de-beb9-d2d2509e1d0d       10.203.120.12     -
              443      Pod-120-NSXT-LM-1.SDDC.Lab
    ASYNC_REPLICATOR                     f8da85a9-66dd-4566-ac32-bd9f99644b9c       10.203.120.12     -
              -        Pod-120-NSXT-LM-1.SDDC.Lab
    CONTROLLER                           2b97a266-fa0d-4c38-b857-e88552aa5c13       10.203.120.12     -
              -        Pod-120-NSXT-LM-1.SDDC.Lab
    CLUSTER_BOOT_MANAGER                 fbca4c2f-28c3-4ce3-8452-9dfe04a91272       10.203.120.12     -
              -        Pod-120-NSXT-LM-1.SDDC.Lab
    CM-INVENTORY                         a18a55d1-8889-4352-912d-c340eb00a03d       10.203.120.12     -
              -        Pod-120-NSXT-LM-1.SDDC.Lab
    DATASTORE                            7de9e729-c7ea-482c-8014-7a613fe13e8b       10.203.120.12     -
              9000     Pod-120-NSXT-LM-1.SDDC.Lab
    CORFU_NONCONFIG                      26c912bd-0fb4-4067-961d-737e34521744       10.203.120.12     -
              9040     Pod-120-NSXT-LM-1.SDDC.Lab
    IDPS_REPORTING                       a1a10066-1508-4923-a197-fff5fc3b759b       10.203.120.12     -
              -        Pod-120-NSXT-LM-1.SDDC.Lab
    MESSAGING-MANAGER                    e6be3d88-5ebf-435e-8609-700929a427b6       10.203.120.12     -
              -        Pod-120-NSXT-LM-1.SDDC.Lab
    MONITORING                           f9dd4b01-2581-4d12-b4b2-4b09938657c3       10.203.120.12     -
              -        Pod-120-NSXT-LM-1.SDDC.Lab
    MANAGER                              4360cb53-c2b4-467a-8e24-e96b44a846ea       10.203.120.12     -
              -        Pod-120-NSXT-LM-1.SDDC.Lab
    SITE_MANAGER                         f9373036-1629-452b-b9e9-6470f06243ce       10.203.120.12     -
              -        Pod-120-NSXT-LM-1.SDDC.Lab
    UPGRADE_COORDINATOR                  c75bb26e-7151-46a9-a3e0-9235fccd05ac       10.203.120.12     -
              -        Pod-120-NSXT-LM-1.SDDC.Lab

Node UUID: 18cd2242-02f0-c2b9-68b8-0d70ff3d2aaf
Node Status: JOINED
    ENTITY                               UUID                                       IP ADDRESS        IPV6 ADDRESS
              PORT     FQDN
    HTTPS                                6bd094ec-9407-4495-9cd0-b03c155ade9a       10.203.0.11       -
              443      Pod-120-NSXT-LM-2
    ASYNC_REPLICATOR                     b783c086-2da7-4289-a4c4-da8123b9d736       10.203.0.11       -
              -        Pod-120-NSXT-LM-2
    CONTROLLER                           d0b3e07c-7d41-452c-9adf-2ae794797551       10.203.0.11       -
              -        Pod-120-NSXT-LM-2
    CLUSTER_BOOT_MANAGER                 f2e77537-ad26-4595-b4ff-8ecccd03888b       10.203.0.11       -
              -        Pod-120-NSXT-LM-2
    CM-INVENTORY                         1ed1f723-dfdc-4ab5-8840-c55cfc3a59e0       10.203.0.11       -
              -        Pod-120-NSXT-LM-2
    DATASTORE                            c20a9bba-425f-425e-a703-089e77717763       10.203.0.11       -
              9000     Pod-120-NSXT-LM-2
    CORFU_NONCONFIG                      9e3be29c-8bb4-484c-aa6a-65fc45f21587       10.203.0.11       -
              9040     Pod-120-NSXT-LM-2
    IDPS_REPORTING                       f9cc923e-824f-4624-b838-26e0c56b2c6b       10.203.0.11       -
              -        Pod-120-NSXT-LM-2
    MESSAGING-MANAGER                    17c8b927-b9cc-4028-a3cf-56ba1774dfb7       10.203.0.11       -
              -        Pod-120-NSXT-LM-2
    MONITORING                           b7772420-d816-4e93-b644-f264c4d00b30       10.203.0.11       -
              -        Pod-120-NSXT-LM-2
    MANAGER                              ea97278a-08ba-48a0-a722-59647d84bdd8       10.203.0.11       -
              -        Pod-120-NSXT-LM-2
    SITE_MANAGER                         07d56dd4-d38f-4952-b60b-69bd8991a9b1       10.203.0.11       -
              -        Pod-120-NSXT-LM-2
    UPGRADE_COORDINATOR                  fd59bb19-10f2-462e-90fe-b35353ef31ec       10.203.0.11       -
              -        Pod-120-NSXT-LM-2

Node UUID: eeda2242-6b5d-cf12-64bf-e825bf9128ab
Node Status: JOINED
    ENTITY                               UUID                                       IP ADDRESS        IPV6 ADDRESS
              PORT     FQDN
    HTTPS                                24a5c202-305c-45ca-bb7a-c3a6a5fc8e7b       10.203.0.12       -
              443      Pod-120-NSXT-LM-3
    ASYNC_REPLICATOR                     689b1f67-7858-4f29-8e28-dbfaf4840b14       10.203.0.12       -
              -        Pod-120-NSXT-LM-3
    CONTROLLER                           52f97c28-411a-4d59-8783-5b85247e1f94       10.203.0.12       -
              -        Pod-120-NSXT-LM-3
    CLUSTER_BOOT_MANAGER                 076b18e7-6f30-4918-baea-024c0c7c1edd       10.203.0.12       -
              -        Pod-120-NSXT-LM-3
    CM-INVENTORY                         7556c130-b0b3-4918-89ca-f242bdaf6514       10.203.0.12       -
              -        Pod-120-NSXT-LM-3
    DATASTORE                            4ea6a3d0-1db0-49ed-9214-db4f63b928e6       10.203.0.12       -
              9000     Pod-120-NSXT-LM-3
    CORFU_NONCONFIG                      fb9dfa79-4aee-4d3a-84c5-3daa300ff4ab       10.203.0.12       -
              9040     Pod-120-NSXT-LM-3
    IDPS_REPORTING                       31342a00-c53d-482e-ae97-792eb9cae196       10.203.0.12       -
              -        Pod-120-NSXT-LM-3
    MESSAGING-MANAGER                    1b74454e-da8a-432a-a71f-02af8838849a       10.203.0.12       -
              -        Pod-120-NSXT-LM-3
    MONITORING                           83993414-3aa3-4fca-99ff-cedb368ad9bc       10.203.0.12       -
              -        Pod-120-NSXT-LM-3
    MANAGER                              66d3718f-405d-4e7d-8909-7daccbd2a856       10.203.0.12       -
              -        Pod-120-NSXT-LM-3
    SITE_MANAGER                         ddbe38a3-908d-4795-adeb-0f526ff8802b       10.203.0.12       -
              -        Pod-120-NSXT-LM-3
    UPGRADE_COORDINATOR                  80cc3089-ed2c-49eb-8324-2a47771fd0f7       10.203.0.12       -
              -        Pod-120-NSXT-LM-3

Pod-120-NSXT-LM-2&gt;</pre></div></div>

<div class="collapsible">
    <div class="collapsible-alone-header">Pod-120-NSXT-LM-2&gt; <code>get cluster status</code></div>
   <div class="collapsible-content">
<pre class="code">Pod-120-NSXT-LM-2&gt; get cluster status
Wed Aug 24 2022 UTC 14:03:42.263
Cluster Id: 7262902c-d10a-4c40-a1d4-d24f737ccfaa
Overall Status: STABLE

Group Type: DATASTORE
Group Status: STABLE

Members:
    UUID                                       FQDN                                       IP               STATUS
    fd0e4d56-4c33-0e61-8bff-9d8a1375b414       Pod-120-NSXT-LM-1.SDDC.Lab                 10.203.120.12    UP
    18cd2242-02f0-c2b9-68b8-0d70ff3d2aaf       Pod-120-NSXT-LM-2                          10.203.0.11      UP
    eeda2242-6b5d-cf12-64bf-e825bf9128ab       Pod-120-NSXT-LM-3                          10.203.0.12      UP

Group Type: CLUSTER_BOOT_MANAGER
Group Status: STABLE

Members:
    UUID                                       FQDN                                       IP               STATUS
    fd0e4d56-4c33-0e61-8bff-9d8a1375b414       Pod-120-NSXT-LM-1.SDDC.Lab                 10.203.120.12    UP
    18cd2242-02f0-c2b9-68b8-0d70ff3d2aaf       Pod-120-NSXT-LM-2                          10.203.0.11      UP
    eeda2242-6b5d-cf12-64bf-e825bf9128ab       Pod-120-NSXT-LM-3                          10.203.0.12      UP

Group Type: CONTROLLER
Group Status: STABLE

Members:
    UUID                                       FQDN                                       IP               STATUS
    2b97a266-fa0d-4c38-b857-e88552aa5c13       Pod-120-NSXT-LM-1.SDDC.Lab                 10.203.120.12    UP
    d0b3e07c-7d41-452c-9adf-2ae794797551       Pod-120-NSXT-LM-2                          10.203.0.11      UP
    52f97c28-411a-4d59-8783-5b85247e1f94       Pod-120-NSXT-LM-3                          10.203.0.12      UP

Group Type: MANAGER
Group Status: STABLE

Members:
    UUID                                       FQDN                                       IP               STATUS
    fd0e4d56-4c33-0e61-8bff-9d8a1375b414       Pod-120-NSXT-LM-1.SDDC.Lab                 10.203.120.12    UP
    18cd2242-02f0-c2b9-68b8-0d70ff3d2aaf       Pod-120-NSXT-LM-2                          10.203.0.11      UP
    eeda2242-6b5d-cf12-64bf-e825bf9128ab       Pod-120-NSXT-LM-3                          10.203.0.12      UP

Group Type: HTTPS
Group Status: STABLE

Members:
    UUID                                       FQDN                                       IP               STATUS
    fd0e4d56-4c33-0e61-8bff-9d8a1375b414       Pod-120-NSXT-LM-1.SDDC.Lab                 10.203.120.12    UP
    18cd2242-02f0-c2b9-68b8-0d70ff3d2aaf       Pod-120-NSXT-LM-2                          10.203.0.11      UP
    eeda2242-6b5d-cf12-64bf-e825bf9128ab       Pod-120-NSXT-LM-3                          10.203.0.12      UP

Group Type: SITE_MANAGER
Group Status: STABLE

Members:
    UUID                                       FQDN                                       IP               STATUS
    fd0e4d56-4c33-0e61-8bff-9d8a1375b414       Pod-120-NSXT-LM-1.SDDC.Lab                 10.203.120.12    UP
    18cd2242-02f0-c2b9-68b8-0d70ff3d2aaf       Pod-120-NSXT-LM-2                          10.203.0.11      UP
    eeda2242-6b5d-cf12-64bf-e825bf9128ab       Pod-120-NSXT-LM-3                          10.203.0.12      UP

Group Type: CM-INVENTORY
Group Status: STABLE

Members:
    UUID                                       FQDN                                       IP               STATUS
    fd0e4d56-4c33-0e61-8bff-9d8a1375b414       Pod-120-NSXT-LM-1.SDDC.Lab                 10.203.120.12    UP
    18cd2242-02f0-c2b9-68b8-0d70ff3d2aaf       Pod-120-NSXT-LM-2                          10.203.0.11      UP
    eeda2242-6b5d-cf12-64bf-e825bf9128ab       Pod-120-NSXT-LM-3                          10.203.0.12      UP

Group Type: IDPS_REPORTING
Group Status: STABLE

Members:
    UUID                                       FQDN                                       IP               STATUS
    fd0e4d56-4c33-0e61-8bff-9d8a1375b414       Pod-120-NSXT-LM-1.SDDC.Lab                 10.203.120.12    UP
    18cd2242-02f0-c2b9-68b8-0d70ff3d2aaf       Pod-120-NSXT-LM-2                          10.203.0.11      UP
    eeda2242-6b5d-cf12-64bf-e825bf9128ab       Pod-120-NSXT-LM-3                          10.203.0.12      UP

Group Type: MONITORING
Group Status: STABLE

Members:
    UUID                                       FQDN                                       IP               STATUS
    fd0e4d56-4c33-0e61-8bff-9d8a1375b414       Pod-120-NSXT-LM-1.SDDC.Lab                 10.203.120.12    UP
    18cd2242-02f0-c2b9-68b8-0d70ff3d2aaf       Pod-120-NSXT-LM-2                          10.203.0.11      UP
    eeda2242-6b5d-cf12-64bf-e825bf9128ab       Pod-120-NSXT-LM-3                          10.203.0.12      UP

Group Type: MESSAGING-MANAGER
Group Status: STABLE

Members:
    UUID                                       FQDN                                       IP               STATUS
    fd0e4d56-4c33-0e61-8bff-9d8a1375b414       Pod-120-NSXT-LM-1.SDDC.Lab                 10.203.120.12    UP
    18cd2242-02f0-c2b9-68b8-0d70ff3d2aaf       Pod-120-NSXT-LM-2                          10.203.0.11      UP
    eeda2242-6b5d-cf12-64bf-e825bf9128ab       Pod-120-NSXT-LM-3                          10.203.0.12      UP

Group Type: CORFU_NONCONFIG
Group Status: STABLE

Members:
    UUID                                       FQDN                                       IP               STATUS
    fd0e4d56-4c33-0e61-8bff-9d8a1375b414       Pod-120-NSXT-LM-1.SDDC.Lab                 10.203.120.12    UP
    18cd2242-02f0-c2b9-68b8-0d70ff3d2aaf       Pod-120-NSXT-LM-2                          10.203.0.11      UP
    eeda2242-6b5d-cf12-64bf-e825bf9128ab       Pod-120-NSXT-LM-3                          10.203.0.12      UP

Pod-120-NSXT-LM-2&gt;</pre></div></div>

<div class="collapsible">
    <div class="collapsible-alone-header">Pod-120-NSXT-LM-3&gt; <code>get cluster config</code></div>
   <div class="collapsible-content">
<pre class="code">Pod-120-NSXT-LM-3&gt; get cluster config
Wed Aug 24 2022 UTC 16:31:02.827
Cluster Id: 7262902c-d10a-4c40-a1d4-d24f737ccfaa
Cluster Configuration Version: 2
Number of nodes in the cluster: 3

Node UUID: fd0e4d56-4c33-0e61-8bff-9d8a1375b414
Node Status: JOINED
    ENTITY                               UUID                                       IP ADDRESS        IPV6 ADDRESS
              PORT     FQDN
    HTTPS                                9834c769-e08c-48de-beb9-d2d2509e1d0d       10.203.120.12     -
              443      Pod-120-NSXT-LM-1.SDDC.Lab
    ASYNC_REPLICATOR                     f8da85a9-66dd-4566-ac32-bd9f99644b9c       10.203.120.12     -
              -        Pod-120-NSXT-LM-1.SDDC.Lab
    CONTROLLER                           2b97a266-fa0d-4c38-b857-e88552aa5c13       10.203.120.12     -
              -        Pod-120-NSXT-LM-1.SDDC.Lab
    CLUSTER_BOOT_MANAGER                 fbca4c2f-28c3-4ce3-8452-9dfe04a91272       10.203.120.12     -
              -        Pod-120-NSXT-LM-1.SDDC.Lab
    CM-INVENTORY                         a18a55d1-8889-4352-912d-c340eb00a03d       10.203.120.12     -
              -        Pod-120-NSXT-LM-1.SDDC.Lab
    DATASTORE                            7de9e729-c7ea-482c-8014-7a613fe13e8b       10.203.120.12     -
              9000     Pod-120-NSXT-LM-1.SDDC.Lab
    CORFU_NONCONFIG                      26c912bd-0fb4-4067-961d-737e34521744       10.203.120.12     -
              9040     Pod-120-NSXT-LM-1.SDDC.Lab
    IDPS_REPORTING                       a1a10066-1508-4923-a197-fff5fc3b759b       10.203.120.12     -
              -        Pod-120-NSXT-LM-1.SDDC.Lab
    MESSAGING-MANAGER                    e6be3d88-5ebf-435e-8609-700929a427b6       10.203.120.12     -
              -        Pod-120-NSXT-LM-1.SDDC.Lab
    MONITORING                           f9dd4b01-2581-4d12-b4b2-4b09938657c3       10.203.120.12     -
              -        Pod-120-NSXT-LM-1.SDDC.Lab
    MANAGER                              4360cb53-c2b4-467a-8e24-e96b44a846ea       10.203.120.12     -
              -        Pod-120-NSXT-LM-1.SDDC.Lab
    SITE_MANAGER                         f9373036-1629-452b-b9e9-6470f06243ce       10.203.120.12     -
              -        Pod-120-NSXT-LM-1.SDDC.Lab
    UPGRADE_COORDINATOR                  c75bb26e-7151-46a9-a3e0-9235fccd05ac       10.203.120.12     -
              -        Pod-120-NSXT-LM-1.SDDC.Lab

Node UUID: 18cd2242-02f0-c2b9-68b8-0d70ff3d2aaf
Node Status: JOINED
    ENTITY                               UUID                                       IP ADDRESS        IPV6 ADDRESS
              PORT     FQDN
    HTTPS                                6bd094ec-9407-4495-9cd0-b03c155ade9a       10.203.0.11       -
              443      Pod-120-NSXT-LM-2
    ASYNC_REPLICATOR                     b783c086-2da7-4289-a4c4-da8123b9d736       10.203.0.11       -
              -        Pod-120-NSXT-LM-2
    CONTROLLER                           d0b3e07c-7d41-452c-9adf-2ae794797551       10.203.0.11       -
              -        Pod-120-NSXT-LM-2
    CLUSTER_BOOT_MANAGER                 f2e77537-ad26-4595-b4ff-8ecccd03888b       10.203.0.11       -
              -        Pod-120-NSXT-LM-2
    CM-INVENTORY                         1ed1f723-dfdc-4ab5-8840-c55cfc3a59e0       10.203.0.11       -
              -        Pod-120-NSXT-LM-2
    DATASTORE                            c20a9bba-425f-425e-a703-089e77717763       10.203.0.11       -
              9000     Pod-120-NSXT-LM-2
    CORFU_NONCONFIG                      9e3be29c-8bb4-484c-aa6a-65fc45f21587       10.203.0.11       -
              9040     Pod-120-NSXT-LM-2
    IDPS_REPORTING                       f9cc923e-824f-4624-b838-26e0c56b2c6b       10.203.0.11       -
              -        Pod-120-NSXT-LM-2
    MESSAGING-MANAGER                    17c8b927-b9cc-4028-a3cf-56ba1774dfb7       10.203.0.11       -
              -        Pod-120-NSXT-LM-2
    MONITORING                           b7772420-d816-4e93-b644-f264c4d00b30       10.203.0.11       -
              -        Pod-120-NSXT-LM-2
    MANAGER                              ea97278a-08ba-48a0-a722-59647d84bdd8       10.203.0.11       -
              -        Pod-120-NSXT-LM-2
    SITE_MANAGER                         07d56dd4-d38f-4952-b60b-69bd8991a9b1       10.203.0.11       -
              -        Pod-120-NSXT-LM-2
    UPGRADE_COORDINATOR                  fd59bb19-10f2-462e-90fe-b35353ef31ec       10.203.0.11       -
              -        Pod-120-NSXT-LM-2

Node UUID: eeda2242-6b5d-cf12-64bf-e825bf9128ab
Node Status: JOINED
    ENTITY                               UUID                                       IP ADDRESS        IPV6 ADDRESS
              PORT     FQDN
    HTTPS                                24a5c202-305c-45ca-bb7a-c3a6a5fc8e7b       10.203.0.12       -
              443      Pod-120-NSXT-LM-3
    ASYNC_REPLICATOR                     689b1f67-7858-4f29-8e28-dbfaf4840b14       10.203.0.12       -
              -        Pod-120-NSXT-LM-3
    CONTROLLER                           52f97c28-411a-4d59-8783-5b85247e1f94       10.203.0.12       -
              -        Pod-120-NSXT-LM-3
    CLUSTER_BOOT_MANAGER                 076b18e7-6f30-4918-baea-024c0c7c1edd       10.203.0.12       -
              -        Pod-120-NSXT-LM-3
    CM-INVENTORY                         7556c130-b0b3-4918-89ca-f242bdaf6514       10.203.0.12       -
              -        Pod-120-NSXT-LM-3
    DATASTORE                            4ea6a3d0-1db0-49ed-9214-db4f63b928e6       10.203.0.12       -
              9000     Pod-120-NSXT-LM-3
    CORFU_NONCONFIG                      fb9dfa79-4aee-4d3a-84c5-3daa300ff4ab       10.203.0.12       -
              9040     Pod-120-NSXT-LM-3
    IDPS_REPORTING                       31342a00-c53d-482e-ae97-792eb9cae196       10.203.0.12       -
              -        Pod-120-NSXT-LM-3
    MESSAGING-MANAGER                    1b74454e-da8a-432a-a71f-02af8838849a       10.203.0.12       -
              -        Pod-120-NSXT-LM-3
    MONITORING                           83993414-3aa3-4fca-99ff-cedb368ad9bc       10.203.0.12       -
              -        Pod-120-NSXT-LM-3
    MANAGER                              66d3718f-405d-4e7d-8909-7daccbd2a856       10.203.0.12       -
              -        Pod-120-NSXT-LM-3
    SITE_MANAGER                         ddbe38a3-908d-4795-adeb-0f526ff8802b       10.203.0.12       -
              -        Pod-120-NSXT-LM-3
    UPGRADE_COORDINATOR                  80cc3089-ed2c-49eb-8324-2a47771fd0f7       10.203.0.12       -
              -        Pod-120-NSXT-LM-3

Pod-120-NSXT-LM-3&gt;</pre></div></div>

<div class="collapsible">
    <div class="collapsible-alone-header">Pod-120-NSXT-LM-3&gt; <code>get cluster status</code></div>
   <div class="collapsible-content">
<pre class="code">Pod-120-NSXT-LM-3&gt; get cluster status
Wed Aug 24 2022 UTC 14:03:45.388
Cluster Id: 7262902c-d10a-4c40-a1d4-d24f737ccfaa
Overall Status: STABLE

Group Type: DATASTORE
Group Status: STABLE

Members:
    UUID                                       FQDN                                       IP               STATUS
    fd0e4d56-4c33-0e61-8bff-9d8a1375b414       Pod-120-NSXT-LM-1.SDDC.Lab                 10.203.120.12    UP
    18cd2242-02f0-c2b9-68b8-0d70ff3d2aaf       Pod-120-NSXT-LM-2                          10.203.0.11      UP
    eeda2242-6b5d-cf12-64bf-e825bf9128ab       Pod-120-NSXT-LM-3                          10.203.0.12      UP

Group Type: CLUSTER_BOOT_MANAGER
Group Status: STABLE

Members:
    UUID                                       FQDN                                       IP               STATUS
    fd0e4d56-4c33-0e61-8bff-9d8a1375b414       Pod-120-NSXT-LM-1.SDDC.Lab                 10.203.120.12    UP
    18cd2242-02f0-c2b9-68b8-0d70ff3d2aaf       Pod-120-NSXT-LM-2                          10.203.0.11      UP
    eeda2242-6b5d-cf12-64bf-e825bf9128ab       Pod-120-NSXT-LM-3                          10.203.0.12      UP

Group Type: CONTROLLER
Group Status: STABLE

Members:
    UUID                                       FQDN                                       IP               STATUS
    2b97a266-fa0d-4c38-b857-e88552aa5c13       Pod-120-NSXT-LM-1.SDDC.Lab                 10.203.120.12    UP
    d0b3e07c-7d41-452c-9adf-2ae794797551       Pod-120-NSXT-LM-2                          10.203.0.11      UP
    52f97c28-411a-4d59-8783-5b85247e1f94       Pod-120-NSXT-LM-3                          10.203.0.12      UP

Group Type: MANAGER
Group Status: STABLE

Members:
    UUID                                       FQDN                                       IP               STATUS
    fd0e4d56-4c33-0e61-8bff-9d8a1375b414       Pod-120-NSXT-LM-1.SDDC.Lab                 10.203.120.12    UP
    18cd2242-02f0-c2b9-68b8-0d70ff3d2aaf       Pod-120-NSXT-LM-2                          10.203.0.11      UP
    eeda2242-6b5d-cf12-64bf-e825bf9128ab       Pod-120-NSXT-LM-3                          10.203.0.12      UP

Group Type: HTTPS
Group Status: STABLE

Members:
    UUID                                       FQDN                                       IP               STATUS
    fd0e4d56-4c33-0e61-8bff-9d8a1375b414       Pod-120-NSXT-LM-1.SDDC.Lab                 10.203.120.12    UP
    18cd2242-02f0-c2b9-68b8-0d70ff3d2aaf       Pod-120-NSXT-LM-2                          10.203.0.11      UP
    eeda2242-6b5d-cf12-64bf-e825bf9128ab       Pod-120-NSXT-LM-3                          10.203.0.12      UP

Group Type: MONITORING
Group Status: STABLE

Members:
    UUID                                       FQDN                                       IP               STATUS
    fd0e4d56-4c33-0e61-8bff-9d8a1375b414       Pod-120-NSXT-LM-1.SDDC.Lab                 10.203.120.12    UP
    18cd2242-02f0-c2b9-68b8-0d70ff3d2aaf       Pod-120-NSXT-LM-2                          10.203.0.11      UP
    eeda2242-6b5d-cf12-64bf-e825bf9128ab       Pod-120-NSXT-LM-3                          10.203.0.12      UP

Group Type: IDPS_REPORTING
Group Status: STABLE

Members:
    UUID                                       FQDN                                       IP               STATUS
    fd0e4d56-4c33-0e61-8bff-9d8a1375b414       Pod-120-NSXT-LM-1.SDDC.Lab                 10.203.120.12    UP
    18cd2242-02f0-c2b9-68b8-0d70ff3d2aaf       Pod-120-NSXT-LM-2                          10.203.0.11      UP
    eeda2242-6b5d-cf12-64bf-e825bf9128ab       Pod-120-NSXT-LM-3                          10.203.0.12      UP

Group Type: MESSAGING-MANAGER
Group Status: STABLE

Members:
    UUID                                       FQDN                                       IP               STATUS
    fd0e4d56-4c33-0e61-8bff-9d8a1375b414       Pod-120-NSXT-LM-1.SDDC.Lab                 10.203.120.12    UP
    18cd2242-02f0-c2b9-68b8-0d70ff3d2aaf       Pod-120-NSXT-LM-2                          10.203.0.11      UP
    eeda2242-6b5d-cf12-64bf-e825bf9128ab       Pod-120-NSXT-LM-3                          10.203.0.12      UP

Group Type: CM-INVENTORY
Group Status: STABLE

Members:
    UUID                                       FQDN                                       IP               STATUS
    fd0e4d56-4c33-0e61-8bff-9d8a1375b414       Pod-120-NSXT-LM-1.SDDC.Lab                 10.203.120.12    UP
    18cd2242-02f0-c2b9-68b8-0d70ff3d2aaf       Pod-120-NSXT-LM-2                          10.203.0.11      UP
    eeda2242-6b5d-cf12-64bf-e825bf9128ab       Pod-120-NSXT-LM-3                          10.203.0.12      UP

Group Type: SITE_MANAGER
Group Status: STABLE

Members:
    UUID                                       FQDN                                       IP               STATUS
    fd0e4d56-4c33-0e61-8bff-9d8a1375b414       Pod-120-NSXT-LM-1.SDDC.Lab                 10.203.120.12    UP
    18cd2242-02f0-c2b9-68b8-0d70ff3d2aaf       Pod-120-NSXT-LM-2                          10.203.0.11      UP
    eeda2242-6b5d-cf12-64bf-e825bf9128ab       Pod-120-NSXT-LM-3                          10.203.0.12      UP

Group Type: CORFU_NONCONFIG
Group Status: STABLE

Members:
    UUID                                       FQDN                                       IP               STATUS
    fd0e4d56-4c33-0e61-8bff-9d8a1375b414       Pod-120-NSXT-LM-1.SDDC.Lab                 10.203.120.12    UP
    18cd2242-02f0-c2b9-68b8-0d70ff3d2aaf       Pod-120-NSXT-LM-2                          10.203.0.11      UP
    eeda2242-6b5d-cf12-64bf-e825bf9128ab       Pod-120-NSXT-LM-3                          10.203.0.12      UP

Pod-120-NSXT-LM-3&gt;</pre></div></div>

<span id="2eb4a75c-a848-4b20-bf9c-34b94a616a47"></span>

== Deploy the second and third NSX Manager to form an NSX Manager Cluster | Using the NSX Manager GUI ==

When I do not want to deploy the NSX Manager Nodes manually I can deploy the NSX Manager Nodes from the first NSX Manager Node using the GUI (Compute Manager configuration is required for this).

When I look at the NSX Home screen I will see the warning “'''3 node cluster recommended'''”.

When I click on “Deploy Nodes” it will take me to the Appliances screen.

<div id="32c0bb40-618c-45ea-b24c-293fe8bb8029" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/12/Untitled%2043.png

</div>
I can also manually browse to the Appliances screen by browsing to '''System → Configuration → Appliances'''.

<div id="5c2cb3ad-6e3c-44d8-8e7a-2c80722dd745" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/12/Untitled%2049.png

</div>
Notice that only one Node is listed.

Again for demonstration purposes I will now deploy these new NSX Manager Nodes in the same IP range (network) then the first one. I will need this later when I want to [https://www.iwanhoogendoorn.nl/index.php/Lab:_NSX_Manager_deployment_(Single_site) configure a Virtual IP address] on the NSX Manager Cluster.

<div id="dd7b2915-db04-4a14-b78e-e819f6182737" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/12/Untitled%2050.png

</div>
The table below will contain all the configuration parameters that I will need to deploy the second and third NSX Manager Node using the GUI.

<div id="f56b215d-6eb6-4a34-9d1f-5eaa92d564b7" class="collection-content">

<span id="section-5"></span>
====  ====

{| class="wikitable collection-content"
|-
! Parameter Name
! Input Second Node
! Input Third Node
|-
| vSphere Cluster
| N/A
| N/A
|-
| VM Name
| Pod-120-NSXT-LM-2
| Pod-120-NSXT-LM-3
|-
| Storage
| ESX-03-DS-01
| ESX-03-DS-01
|-
| Network (Port Group)
| Pod-120-Mgmt
| Pod-120-Mgmt
|-
| System Root User Password
| VMware1!VMware1!
| VMware1!VMware1!
|-
| CLI "admin" User Password
| VMware1!VMware1!
| VMware1!VMware1!
|-
| CLI "audit" User Password
| VMware1!VMware1!
| VMware1!VMware1!
|-
| Hostname
| Pod-120-NSXT-LM-2
| Pod-120-NSXT-LM-3
|-
| Rolename
| NSX Manager
| NSX Manager
|-
| Management Network IPv4 Address
| 10.203.120.13
| 10.203.120.14
|-
| Management Network Netmask
| 255.255.255.0
| 255.255.255.0
|-
| Default IPv4 Gateway
| 10.203.120.1
| 10.203.120.1
|-
| DNS Server list
| 10.203.0.5
| 10.203.0.5
|-
| Domain Search List
| sddc.lab
| sddc.lab
|-
| NTP Server List
| 10.203.0.5
| 10.203.0.5
|-
| Enable SSH
| yes
| yes
|-
| Allow root SSH logins
| yes
| yes
|}

</div>
<span id="8dc7793b-f69a-4558-ab0e-5b0476f68119"></span>
=== Add the second NSX Manager Node ===

After I clicked “Add NSX Appliance” I can start with the deployment of the second NSX Manager Node. Use the Configuration Parameters from the table above to specify the Appliance Information.

<div id="7553f7e0-780e-43d2-b1ae-e9615e8da6fe" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/12/Untitled%2051.png

</div>
Use the Configuration Parameters from the table above to specify the Configuration.

<div id="930e7a20-d8b7-42fb-afc2-2e1ab1243424" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/12/Untitled%2052.png

</div>
Use the Configuration Parameters from the table above to specify the Access & Credentials.

<div id="7520a699-cc4e-4e78-b81f-dde7e56f986d" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/12/Untitled%2053.png

</div>
After I have clicked “'''Install Appliance'''” I can look at the Appliances screen to track the progress.

<div id="01d2f8b6-a96e-4252-a754-40c6f08a2db4" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/12/Untitled%2054.png

</div>
After I have clicked “'''Install Appliance'''” I can look at the Appliances screen to track the progress.

<div id="b35244f2-6738-4849-8388-fdb5f77f8fcd" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/12/Untitled%2055.png

</div>
When the deployment is completed I will now have an NSX Manager Cluster with two NSX Manager Nodes.

<div id="e78bfd1d-0d13-4c18-a993-7bf97427b38f" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/12/Untitled%2056.png

</div>
<span id="a2d968c9-85d3-46d0-a53c-546085c51d52"></span>
=== Add the third NSX Manager Node ===

Click on “Add NSX Appliance” again to start with the deployment of the third NSX Manager Node. Use the Configuration Parameters from the table above to specify the Appliance Information.

<div id="b376f286-f9df-49c8-bbf8-142618b96852" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/12/Untitled%2057.png

</div>
Use the Configuration Parameters from the table above to specify the Configuration.

<div id="25cc1d5a-3092-4eed-9631-db03ae01af03" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/12/Untitled%2058.png

</div>
Use the Configuration Parameters from the table above to specify the Access & Credentials.

<div id="fbb3cf8f-e80e-4ccc-8eb0-c0b49c2e41bc" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/12/Untitled%2059.png

</div>
After I have clicked “'''Install Appliance'''” I can look at the Appliances screen to track the progress.

<div id="471cd0e7-d1f7-460f-af16-02566f5a78b9" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/12/Untitled%2060.png

</div>
After I have clicked “'''Install Appliance'''” I can look at the Appliances screen to track the progress.

<div id="0c1fdf88-f9f6-4647-9b2c-878b9b8ebd0f" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/12/Untitled%2061.png

</div>
When the deployment is completed I will now have an NSX Manager Cluster with three NSX Manager Nodes.

<div id="cf04ef4c-03ea-429b-bee3-cf19de3ee35e" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/12/Untitled%2062.png

</div>
One thing that I want to point out is that if I have manually deployed an NSX Manager Node I will not be able to delete it from the GUI. Look as the button that is greyed out.

<div id="8b0db68c-0937-4cf0-a3d8-e6f412dcd53c" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/12/Untitled%2063.png

</div>
When I have deployed an NSX Manager Node using the GUI I will be able to delete it from the GUI. Look as the button that can now be used.

<div id="a04353b5-80b1-46ce-a73e-6da82efbf4ca" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/12/Untitled%2064.png

</div>
Also pay attention to the NSX Home screen that the W warning “'''3 node cluster recommended'''” is now gone.

<div id="7a0a8fdd-8f18-4e0b-ba44-f7f3bc7c74df" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/12/Untitled%2065.png

</div>
<span id="4af7c626-ea42-4188-a801-1a8bd78cd02d"></span>

= STEP 5: Configure the NSX Virtual IP Address (VIP) =

Now that I have an NSX Manager Cluster consisting out of three Nodes I can configure the NSX Manager Cluster Virtual IP Address.

<div id="93bc7b6f-2f97-49c6-ab5a-1640ad6e223f" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/12/Untitled%2066.png

</div>
<div id="a7ed75eb-5c01-40fe-ba79-1c32ea0f71e0" class="collection-content">

<span id="section-6"></span>
====  ====

{| class="wikitable collection-content"
|-
! Parameter Name
! Input
|-
| Virtual IP
| 10.203.120.11
|}

</div>
<span id="f541ea3a-daac-481e-b060-f469dd310958"></span>
== NSX Manager Nodes not in the same network ==

One of the constraints of configuring an NSX Manager Cluster Virtual IP Address is that all the Nodes needs to be part of the same network.

For demonstration purpose I have three NSX Manager Nodes that are NOT in the same network. Click on “'''Set Virtual IP'''”.

<div id="c60204c2-bdc3-4117-8829-07c1b2e9328e" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/12/Untitled%2067.png

</div>
Specify the IP address.

<div id="866a976b-fe6e-41d3-94e4-95f33505436a" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/12/Untitled%2068.png

</div>
Make note of the error, as I am trying to do something that is not allowed.

<div id="e870e5f9-4166-4538-8e28-585bca385090" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/12/Untitled%2069.png

</div>
<span id="4c90f52f-fe79-4b41-8f3d-27ae5dda6f4f"></span>
== NSX Manager Nodes in the same network ==

Let’s now try it with three NSX Manager Nodes that ARE in the same network. Click on “'''Set Virtual IP'''”.

<div id="dbf20bfb-afd7-4354-b470-4259b233731b" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/12/Untitled%2070.png

</div>
Specify the IP address.

<div id="e51c8f51-f49b-413d-8e8c-02758e16dd4d" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/12/Untitled%2071.png
</div>
Look at the status.

<div id="5e476088-4787-4bef-91db-c2cd089c77a1" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/12/Untitled%2072.png

</div>
Verify if the Virtual IP is correctly configured below the “Virtual IP” label.

<div id="f30bd726-b71b-4ae6-93eb-26d87c2acc65" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/12/Untitled%2073.png

</div>
I can now browse to the FQDN that translates to the Virtual IP address to connect to the NSX Manager Cluster using this new Virtual IP address.

<div id="e7786916-88c9-40e2-8d01-6a58051eaae2" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/12/Untitled%2074.png

</div>
When I have the Virtual IP address (VIP) configured one of the NSX Manager Nodes will always be the leader, and this VIP is bound to the leader. To find out which NSX Manager Node is the leader issue the following command:

<div class="collapsible">
    <div class="collapsible-alone-header">Pod-120-NSXT-LM-1&gt; '''<code>get cluster status verbose</code>'''</div>
   <div class="collapsible-content">
<pre class="code">Pod-120-NSXT-LM-1&gt; get cluster status verbose
Thu Aug 25 2022 UTC 11:24:19.964
Cluster Id: e0681397-166e-4b49-9a3c-74fc1df3e9d1
Overall Status: STABLE

Group Type: DATASTORE
Group Status: STABLE

Members:
    UUID                                       FQDN                                       IP               STATUS
    a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       Pod-120-NSXT-LM-1.SDDC.Lab                 10.203.120.12    UP
    09d4df47-f293-4ea7-8173-92a320fed685       Pod-120-NSXT-LM-2                          10.203.120.13    UP
    f77633c9-69f2-41a2-b3f8-b14c96a7bec5       Pod-120-NSXT-LM-3                          10.203.120.14    UP


Group Type: CLUSTER_BOOT_MANAGER
Group Status: STABLE

Members:
    UUID                                       FQDN                                       IP               STATUS
    a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       Pod-120-NSXT-LM-1.SDDC.Lab                 10.203.120.12    UP
    09d4df47-f293-4ea7-8173-92a320fed685       Pod-120-NSXT-LM-2                          10.203.120.13    UP
    f77633c9-69f2-41a2-b3f8-b14c96a7bec5       Pod-120-NSXT-LM-3                          10.203.120.14    UP

Leaders:
    SERVICE                                    LEADER                                     LEASE VERSION
    cluster-manager                            a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       767

Group Type: CONTROLLER
Group Status: STABLE

Members:
    UUID                                       FQDN                                       IP               STATUS
    81e59552-30ba-4cff-9540-1eda464c0072       Pod-120-NSXT-LM-1.SDDC.Lab                 10.203.120.12    UP
    537c5d50-a89e-4f93-933f-d94c75e1b5cd       Pod-120-NSXT-LM-2                          10.203.120.13    UP
    1826609d-288d-4b21-87da-1a9aeb3a07a4       Pod-120-NSXT-LM-3                          10.203.120.14    UP

Leaders:
    SERVICE                                    LEADER                                     LEASE VERSION
    ShardingService                            81e59552-30ba-4cff-9540-1eda464c0072       726

Group Type: MANAGER
Group Status: STABLE

Members:
    UUID                                       FQDN                                       IP               STATUS
    a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       Pod-120-NSXT-LM-1.SDDC.Lab                 10.203.120.12    UP
    09d4df47-f293-4ea7-8173-92a320fed685       Pod-120-NSXT-LM-2                          10.203.120.13    UP
    f77633c9-69f2-41a2-b3f8-b14c96a7bec5       Pod-120-NSXT-LM-3                          10.203.120.14    UP

Leaders:
    SERVICE                                    LEADER                                     LEASE VERSION
    ServiceConfigChangeWorker-GiServiceProfile a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       739
    POLICY_SVC_IDS_GATEWAY_POLICY_PROVIDER     a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       739
    SHA_APPLIANCE_SERVICE                      a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       737
    POLICY_SVC_POLICY_TRANSPORT_ZONE           a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       739
    POLICY_SVC_EDGE_TRANSPORT_NODE             a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       737
    UnderlayRouteWorker-UnderlayRouteRefreshTrigger a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       737
    POLICY_SVC_LOADBALANCER                    a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       739
    POLICY_SVC_TLS_PROFILE_PROVIDER            a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       739
    POLICY_SVC_GLOBAL                          a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       737
    POLICY_SVC_FIREWALL                        a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       737
    POLICY_SVC_PORTMIRRORINGPROFILE            a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       737
    MtuCheckQuartzSetupServiceImpl             a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       739
    POLICY_SVC_FLOOD_PROTECTION_PROFILES_PROVIDER a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       737
    POLICY_SVC_IDS_SECTION_PROVIDER            a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       740
    EdgeNodeExternalConfigWorker-EdgeNodeExternalConfig a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       737
    FirewallStatsPersistedQueueProcessor       a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       737
    AutoHealthCheckMonitor                     a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       739
    POLICY_SVC_IDS_SIGNATURES_COMP_FILE_PROVIDER a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       737
    LbAlarmShardingServiceImpl                 a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       737
    POLICY_SVC_SHA_DYNAMIC_PLUGIN              a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       740
    IntelligenceHostConfigWorker-IntelligenceHostConfig a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       740
    CentralConfigProcessor                     a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       739
    POLICY_SVC_BYOD_POLICY_SERVICE_INSERTION   a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       737
    LM_NOTIFICATION_MANAGER                    a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       737
    ALARMS_REFRESH_TASK                        a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       739
    POLICY_SVC_GENERAL_SECURITY_PROFILES_PROVIDER a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       737
    TraceflowCacheManager                      a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       740
    POLICY_SVC_FORWARDING                      a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       737
    POLICY_SVC_IDFW_IDS_TOGGLE                 a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       739
    EdgeTNDeleteWorker-TransportNodeState      a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       739
    POLICY_SVC_EDGE_FIREWALL                   a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       739
    CertificateShardingServiceImpl             a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       737
    POLICY_SVC_FIREWALL_IDENTITY               a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       739
    POLICY_SVC_LM_SITE_SPAN                    a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       740
    POLICY_SVC_POLICY_FQDN_ANALYSIS_CONFIG_PROVIDER a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       740
    OpsClusterService                          a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       737
    POLICY_SVC_SECURITY_FEATURE_TOGGLE         a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       737
    POLICY_SVC_DFW_EXCLUDE_LIST                a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       737
    POLICY_SVC_IPFIX_DFW_PROFILE               a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       739
    POLICY_SVC_CLUSTER_CONTROL_PLANE           a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       737
    POLICY_SVC_QOS_PROFILE                     a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       739
    POLICY_SVC_IPFIX_L2_COLLECTOR_PROFILE      a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       739
    POLICY_SVC_POLICY_SERVICE_INSERTION        a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       739
    POLICY_SVC_POLICY_GUEST_INTROSPECTION      a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       737
    POLICY_SVC_SEGMENTPORT                     a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       737
    POLICY_SVC_MALWARE_PREVENTION_PROFILE_PROVIDER a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       739
    POLICY_SVC_ADVANCELOADBALANCER             a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       739
    POLICY_SVC_POLICY_SERVICE_INSERTION_EW     a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       737
    ENFORCEMENT_POINT_RELOAD_TASK              a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       737
    POLICY_SVC_GATEWAY_QOS_PROFILE             a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       737
    RealizationServiceMaintenanceManager       a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       739
    IntelligenceClusterConfigWorker-IntelligenceClusterConfig a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       737

    MirrorStackMonitorImpl                     a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       737
    IP_REPUTATION_FEED_DOWNLOAD_TASK           a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       739
    ShaClusterServiceImpl                      a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       739
    POLICY_SVC_NSSERVICEGROUP                  a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       737
    POLICY_SVC_POLICY_UC_DEPLOYMENT_CONFIG     a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       739
    POLICY_SVC_IPFIX_L2_GLOBAL_PROFILE         a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       737
    SECURITY_ALARM_SERVICE                     a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       739
    POLICY_SVC_DISCOVERY                       a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       737
    POLICY_SVC_IDS_GLOBAL_CONFIG               a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       739
    POLICY_SVC_FIREWALL_SCHEDULER              a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       739
    POLICY_SVC_IDS_GATEWAY_SECTION_PROVIDER    a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       737
    POLICY_SVC_CERTIFICATE                     a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       739
    POLICY_SVC_OPS_GLOBAL_CONFIG               a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       737
    POLICY_SVC_POLICY_EDGE_CLUSTER_PROVIDER    a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       739
    POLICY_SVC_VM_TAG_REPLICATION_POLICY_PROVIDER a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       739
    POLICY_SVC_MAC_DISCOVERY                   a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       737
    POLICY_SVC_LATENCY_STAT_PROFILE            a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       739
    LicensingShardingServiceImpl               a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       737
    LiveTraceMessageManager                    a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       737
    POLICY_SVC_IDS_STANDALONE_HOST_CONFIG      a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       737
    POLICY_SVC_IPFIX_DFW_GROUP_PROFILE         a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       737
    POLICY_SVC_L7_ACCESS_PROFILE               a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       740
    POLICY_SVC_GROUPING                        a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       739
    DataReaper                                 a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       739
    POLICY_SVC_ROUTING                         a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       740
    POLICY_SVC_METADATA_PROXY                  a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       739
    COMMON_AGENT_SERVICE                       a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       739
    POLICY_SVC_VPN                             a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       737
    POLICY_SVC_IPFIXSWITCHCOLLECTION           a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       737
    POLICY_SVC_CONTEXT_PROFILE                 a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       737
    NodeStatusPropertiesStreamListenerService  a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       737
    POLICY-INTENT-CLEANUP-SERVICE              a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       737
    POLICY_SVC_FIREWALL_CPU_MEMORY_THRESHOLDS_PROFILE_PROVIDER a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       737

    COMMON_AGENT_ALARM_SERVICE                 a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       737
    POLICY_SVC_TIER1                           a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       737
    FirewallPersistenceQueueProcessor          a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       739
    POLICY_SVC_DNS                             a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       737
    POLICY_SVC_TIER0                           a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       737
    TNStateWorker-TransportNodeState           a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       740
    POLICY_SVC_NATRULE                         a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       739
    ManualHealthCheckMonitor                   a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       739
    POLICY_SVC_BASE_HOST_SWITCH_PROFILE        a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       737
    ActivityPurger                             a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       740
    POLICY_SVC_METRIC_GLOBAL_CONFIG            a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       739
    CentralNodeConfigService                   a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       739
    POLICY_SVC_IPFIX_L2_PROFILE                a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       737
    POLICY_SVC_IPFIXDFWCOLLECTORPROFILE        a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       739
    POLICY_SVC_SHA_PLUGIN_PROFILE              a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       737
    POLICY_SVC_POLICY_URL_CATEGORIZATION_CONFIG_PROVIDER a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       737
    POLICY_SVC_DFW_SESSION_TIMER_PROFILE       a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       739
    POLICY_SVC_IPAM                            a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       737
    POLICY_SVC_SESSION_TIMER_PROFILES_PROVIDER a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       739
    LM_CONSUMER_SERVICE                        a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       737
    POLICY_SVC_INITIALIZER                     a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       737
    POLICY_SVC_IDS_PROFILE_PROVIDER            a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       737
    com.vmware.nsx.management.nsxealarms.facade.NsxeAlarmFacadeImpl a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       737

    ServiceConfigChangeWorker-ServiceConfig    a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       740
    HealthCheckRequestMonitor                  a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       739
    POLICY_SVC_SECURITY_PROFILE                a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       737
    IdfwDbDaemon                               a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       737
    METRIC_AGENT_SERVICE                       a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       739
    POLICY_SVC_CVX_SECURITY                    a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       739
    POLICY_SVC_TRACE_GLOBAL_CONFIG             a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       737
    POLICY_SVC_REDIRECTION_FIREWALL            a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       737
    LM_SITE_OFFBOARDING                        a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       737
    TransportNodeStatusMessageListener         a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       737
    CentralNodeConfigProcessor                 a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       739
    INTELLIGENCE_AGENT_SERVICE                 a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       737
    QuartzSetupServiceImpl                     a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       739
    POLICY_SVC_POLICY_PLATFORM_DEPLOYMENT_CONFIG a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       739
    POLICY_SVC_TAG_BULK_OPERATION              a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       737
    ServiceInsertionPersistenceQueueProcessor  a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       737
    POLICY_SVC_CONNECTIVITY                    a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       737
    POLICY_SVC_POLICY_TRANSPORT_ZONE_PROFILE   a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       739
    POLICY_SVC_TLS_FQDN_STATE                  a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       737
    POLICY_SVC_TRANSPORT_NODE                  a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       740
    ShardingMaster                             a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       739
    POLICY_SVC_PORTMIRRORINGINSTANCE           a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       739
    AUTO_DRAFT_PURGE_TASK                      a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       739
    POLICY_SVC_SEGMENT                         a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       737
    POLICY_SVC_IP_DISCOVERY                    a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       740
    POLICY_SVC_NSSERVICE                       a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       739
    SERVICE_CONFIG_PRECEDENCE_PROVIDER         a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       737

Group Type: HTTPS
Group Status: STABLE

Members:
    UUID                                       FQDN                                       IP               STATUS
    a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       Pod-120-NSXT-LM-1.SDDC.Lab                 10.203.120.12    UP
    09d4df47-f293-4ea7-8173-92a320fed685       Pod-120-NSXT-LM-2                          10.203.120.13    UP
    f77633c9-69f2-41a2-b3f8-b14c96a7bec5       Pod-120-NSXT-LM-3                          10.203.120.14    UP

Leaders:
    SERVICE                                    LEADER                                     LEASE VERSION
    api                                        a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       739

Group Type: IDPS_REPORTING
Group Status: STABLE

Members:
    UUID                                       FQDN                                       IP               STATUS
    a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       Pod-120-NSXT-LM-1.SDDC.Lab                 10.203.120.12    UP
    09d4df47-f293-4ea7-8173-92a320fed685       Pod-120-NSXT-LM-2                          10.203.120.13    UP
    f77633c9-69f2-41a2-b3f8-b14c96a7bec5       Pod-120-NSXT-LM-3                          10.203.120.14    UP

Leaders:
    SERVICE                                    LEADER                                     LEASE VERSION
    idps-reporting                             a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       739

Group Type: MONITORING
Group Status: STABLE

Members:
    UUID                                       FQDN                                       IP               STATUS
    a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       Pod-120-NSXT-LM-1.SDDC.Lab                 10.203.120.12    UP
    09d4df47-f293-4ea7-8173-92a320fed685       Pod-120-NSXT-LM-2                          10.203.120.13    UP
    f77633c9-69f2-41a2-b3f8-b14c96a7bec5       Pod-120-NSXT-LM-3                          10.203.120.14    UP

Leaders:
    SERVICE                                    LEADER                                     LEASE VERSION
    monitoring                                 a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       755
    ShardingMaster                             a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       755
    CoordinatedDataCollectionLeader            a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       755

Group Type: CM-INVENTORY
Group Status: STABLE

Members:
    UUID                                       FQDN                                       IP               STATUS
    a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       Pod-120-NSXT-LM-1.SDDC.Lab                 10.203.120.12    UP
    09d4df47-f293-4ea7-8173-92a320fed685       Pod-120-NSXT-LM-2                          10.203.120.13    UP
    f77633c9-69f2-41a2-b3f8-b14c96a7bec5       Pod-120-NSXT-LM-3                          10.203.120.14    UP

Leaders:
    SERVICE                                    LEADER                                     LEASE VERSION
    ShardingMaster                             a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       755

Group Type: MESSAGING-MANAGER
Group Status: STABLE

Members:
    UUID                                       FQDN                                       IP               STATUS
    a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       Pod-120-NSXT-LM-1.SDDC.Lab                 10.203.120.12    UP
    09d4df47-f293-4ea7-8173-92a320fed685       Pod-120-NSXT-LM-2                          10.203.120.13    UP
    f77633c9-69f2-41a2-b3f8-b14c96a7bec5       Pod-120-NSXT-LM-3                          10.203.120.14    UP

Leaders:
    SERVICE                                    LEADER                                     LEASE VERSION
    messaging-manager                          a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       763

Group Type: SITE_MANAGER
Group Status: STABLE

Members:
    UUID                                       FQDN                                       IP               STATUS
    a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       Pod-120-NSXT-LM-1.SDDC.Lab                 10.203.120.12    UP
    09d4df47-f293-4ea7-8173-92a320fed685       Pod-120-NSXT-LM-2                          10.203.120.13    UP
    f77633c9-69f2-41a2-b3f8-b14c96a7bec5       Pod-120-NSXT-LM-3                          10.203.120.14    UP

Leaders:
    SERVICE                                    LEADER                                     LEASE VERSION
    site-manager                               a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       765

Group Type: CORFU_NONCONFIG
Group Status: STABLE

Members:
    UUID                                       FQDN                                       IP               STATUS
    a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a       Pod-120-NSXT-LM-1.SDDC.Lab                 10.203.120.12    UP
    09d4df47-f293-4ea7-8173-92a320fed685       Pod-120-NSXT-LM-2                          10.203.120.13    UP
    f77633c9-69f2-41a2-b3f8-b14c96a7bec5       Pod-120-NSXT-LM-3                          10.203.120.14    UP

Pod-120-NSXT-LM-1&gt;</pre></div></div>

The output shows that the leader is <code>a7d94d56-cbfd-4ca9-8b9b-b2a9daa2d45a</code> and this is the NSX Manager Node with the IP address of 10.203.120.12/24.

<div id="74c44cb1-7692-4f9c-b603-4a2ae70869e3" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/12/Untitled%2075.png

</div>

'''Continue with >>''' [[Lab: NSX Manager backup configuration]]

[[Category:NSX]]
[[Category:Networking]]
[[Category:VMware]]
[[Category:NSX Academy]]