, pub-4920175566720914, DIRECT, f08c47fec0942fa0 Skip to main content

NSX-T Manager Node Recovery

In the NSX-T environment, there were scenarios where it's required to bring down the manager node instances off from the cluster due to several abnormal reasons.

Scenarios like if there were some issues during the upgrade of the manager node instance or having any abnormal circumstances where is node unable to recover from NSX-T Manager UI. 

To recover/replace the node from the manager cluster its require to attempt with the manual process.

Let's discuss the manual path to recover/Replace a Manager Node in the Cluster.

1) Login to NSX-T manager using CLI

2) Use command 'get cluster status'

This command will list all the NSX-T manager/controllers nodes into the cluster.

Find the UUID of the existing node and Cluster to identify the node which requires recover/replace.

3) Now that we have identifying the manager node ID from the above command, its time to detect the node from the cluster. 

Using detach node command "node id" will remove the node from the cluster.

This process will delete that specific node completely from the cluster and NSX-T enviornment.

Now once you deploy a new NSX-T manager node, its require to add the node into the cluster.

4) To add the node manually its require to know the API thumbprint certificate of the cluster to associate the node with the cluster

Using get certificate api thumbprint will get the certificate api.

5) Now, once we get the API thumbprint certificate, we can add the node using the node ID with API thumbprint certificate.
This will successfully add the new node into the NSX-T Cluster in full motion.

6) Here, we need to identify which manager node is the orchestrator node within the cluster.
 It is a self-contained web application that orchestrates the upgrade process of hosts, NSX Controller cluster, and Management plane.

Users can check which node is orchestrator node by running CLI "get service install-upgrade". The IP of the orchestrator node will be shown in the "Enabled-on" output.

"set repository-ip' will make a manager node the orchestrator node. It is needed if the node on which install-upgrade server is enabled (orchestrator node) is being detached from MP Cluster. 

Note: Changing the IP address of the Manager Node needs to follow the same procedure.

This conclude the process to add the NSX-T manager/controller node into the cluster using the manual method.

If you like the contents of this article then please share it further on the social platforms.  :)


Popular posts from this blog

Changing the FQDN of the vCenter appliance (VCSA)

This article states how to change the system name or the FQDN of the vCenter appliance 6.x
You may not find any way to change the FQDN from the vCenter GUI either from VAMI page of from webclient as the option to change the hostname always be greyed out.
Now the option left is from the command line of VCSA appliance.
Below steps will make it possible to change the FQDN of the VCSA from the command line.
Access the VCSA from console or from Putty session.Login with root permissionUse above command in the command prompt of VCSA : /opt/vmware/share/vami/vami_config_netOpt for option 3 (Hostname)Change the hostname to new nameReboot the VCSA appliance.After reboot you will be successfully manage to change the FQDN of the VCSA .

Note: Above step is unsupported by VMware and may impact your SSL certificate and face problem while logging to vSphere Web Client.

If you are using self-signed certificate, you can regenerate the certificate with the help of below KB 2112283 article.

Happy Sharin…

VM Creation Date & Time from Powercli

Most of the times we have several requirement when we talk about IT environment like designing , deployment , compliance check or for Security auditing the environment.
Somewhere during security auditing we require to provide several information to security team to get successful audit.
One of them is the compliance of Virtual machine auditing of creation date and time.
Here into this post we will explore how to get the creation date and time of virtual machine hosted into the vCenter or ESXi.
To get the details we will use VMware Powercli to extract the details.
By default there is no function added into Powercli to get such details, so here we will add a function of vm creation date.
Below is the function which needed to be copy and paste into the Powercli.
function Get-VMCreationTime { $vms = get-vm $vmevts = @() $vmevt = new-object PSObject foreach ($vm in $vms) { #Progress bar: $foundString = "       Found: "+$v…

Could not connect to one or more vCenter Server systems: https://FQDN:443/sdk

Recently I got a case where vCenter 6.0 where the webclient was not showing inventory while loading. Issue occur when the customer was performing migration activity of virtual machine.
We verified that the vpxd services of vCenter, which is VCSA (Appliance), went into stopped stated just after starting means its crashing.
On VCSA Shell: service-control --status vmware-vpxd shows "stopped" service-control --start vmware-vpxd starts the service starts for a couple of seconds and stops again
VCSA 6.0 is linked with extrnal PSC 6.0. Verified the services of PSC and found all looks into good state.
Tried to power off both the VCSA and PSC and Power on in sequence where we started first PSC and later VCSA. After restarting the VCSA, status of the VPXD services was same as it was getting stopped after couple of seconds.
Checked the VPXD logs and found that the heartbeat between ESXi and VCSA was getting timed out for more than 1032 ms or more.
VCSA has generated the core dump at /var/core. …