PART05-NSX Series Check NSX controller status

NSX Controller A control Plane is responsible for obtaining distributed network messages for the host, and the previous section (Part04) has discussed how to prepare a cluster for an NSX controller and related considerations. NSX controllers will form a control cluster, and the presence of cluster requires more machines to circumvent the brain fissure scene. It is because of this existence that it is required that the total number of NSX controllers is odd, for example: 3, 5, 7, and so on. It exists to manage the routing and switching modules inside the hypervisor. For its management, information query, etc., all need to be done through the command line. The command line of the NSX controller can be executed with a series of commands;

If you want to view the status of the NSX Controller cluster, you can execute the command:

1. #show control-cluster Status

01 is shown below:

Figure 01

In the output of the command shown in Figure 01, we can see several more important parameters:

· Majority status– Check if controller cluster is connected to cluster Majority;

· Join status– verifies that the current NSX controller is successfully added to the NSX controller Cluster;

· Cluster ID – displays the current Cluster ID, all NSX controllers will share an identical ID;

· Node uuid– The UUID message of the current nodes;

· Configured status– shows the current related roles (Api_provider,persistence_server,switch_manager,directory_server, Nvp-controller) The current configuration state of these roles;

· Active status– shows the active status of the relevant role;

· Restart status– Indicates whether the current controller node can be restarted without affecting the business;

If you want to view the connection status of NSX Control cluster, you can use the command:

1. #show control-cluster Connections

This command shows the status of the communication port for the relevant component in the current environment, for example: Persistence_server's communication port is 2878, and when its listening status is Y, it indicates that it is currently in listening state. At the same time, you can see the client, election and other services such as Port 2888, 3888, 02 is shown:

Figure 02

Within a 3-node cluster, Control node will have 2 connections, as well as the other nodes in the same controller cluster, as shown in 03 and figure 04:

Fig. 03 FIG. 04

In the NSX Control cluster, there will also be related roles, each controller node will have a different role to see the command as follows:

1. #show control-cluster Roles

The execution of this command outputs the results shown in 05:

Figure 05

Figure 05 is composed of the output of the different nodes. Look at the results, you can see that there will be a master node state. If one of the roles of a master NSX controller object fails, the entire controller cluster will elect a new, usable NSX controller by election. The new master NSX controller will reassign the remaining NSX controller's job role to replace the failed NSX controller. All NSX controller objects are on control plane, so an NSX controller failure does not affect the data plane part, that is, it does not affect the communication portion (which is clear if you play VDS);

If you want to see the history of the entire NSX Controller cluster, you can use the command:

1. #show control-cluster History

As shown in 06, it will record what happened in the past time of this cluster, including: Reboot, upgrade, malfunction and warning when the quantity is insufficient;

Figure 06

In this command line can see more things, however, this article is mainly to explain how to view the status of NSX controller information, so, do not go to enumerate the other functions;

To be Continued ... For details, please download the Download center of Bo Master.

Your attention, will prove to you yourself!

Wechat:vmanager_forum

Part05-(graphics) NSX series Check NSX controller status