If you need to reboot multiple members of your NSX Controller cluster, you must reboot one member at a time. A three-member cluster can have majority if one member is offline. If two members are offline, the cluster will lose majority and will not function normally.

Procedure

  1. Log in to the CLI of an NSX Manager.
  2. Get the status of the management and control clusters.
    nsx-manager-1> get management-cluster status
    Number of nodes in management cluster: 3
    - 192.168.110.201  (UUID 564D2E9C-A521-6C27-104F-76BBB5FCAC7F) Online
    - 192.168.110.202  (UUID 564D0B9E-DEBD-A19E-233C-C13432CB23FB) Online
    - 192.168.110.203  (UUID 564D666C-EB23-CDC1-8101-95155E9EB916) Online
    
    Management cluster status: STABLE
    
    Number of nodes in control cluster: 3
    - 192.168.110.53   (UUID f5348a2e-2d59-4edc-9618-2c05ac073fd8)
    - 192.168.110.51   (UUID 03fad907-612f-4068-8109-efdf73002038)
    - 192.168.110.52   (UUID 1228c336-3932-4b5b-b87e-9f66259cebcd)
    
    Control cluster status: STABLE
    
  3. Log in to the CLI of an NSX Controller you need to reboot, and reboot it.
    nsx-controller-2> reboot
    Are you sure you want to reboot (yes/no): y
    
  4. Get the status of the management and control cluster again. Wait until the control cluster status is STABLE before rebooting any additional members.

    In this example, the NSX Controller 192.168.110.53 is rebooting, and the control cluster has a status of DEGRADED. This means the cluster is in majority, but one of the members is down. See Get the NSX Controller Cluster Status for more information about NSX Controller cluster status.

    nsx-manager-1> get management-cluster status
    Number of nodes in management cluster: 3
    - 192.168.110.201  (UUID 564D2E9C-A521-6C27-104F-76BBB5FCAC7F) Online
    - 192.168.110.202  (UUID 564D0B9E-DEBD-A19E-233C-C13432CB23FB) Online
    - 192.168.110.203  (UUID 564D666C-EB23-CDC1-8101-95155E9EB916) Online
    
    Management cluster status: STABLE
    
    Number of nodes in control cluster: 3
    - 192.168.110.53   (UUID f5348a2e-2d59-4edc-9618-2c05ac073fd8)
    - 192.168.110.52   (UUID 1228c336-3932-4b5b-b87e-9f66259cebcd)
    - 192.168.110.51   (UUID 03fad907-612f-4068-8109-efdf73002038)
    
    Control cluster status: DEGRADED

    Once the NSX Controller cluster has status of STABLE, it is safe to reboot any additional members.

    nsx-manager-1> get management-cluster status
    Number of nodes in management cluster: 3
    - 192.168.110.201  (UUID 564D2E9C-A521-6C27-104F-76BBB5FCAC7F) Online
    - 192.168.110.202  (UUID 564D0B9E-DEBD-A19E-233C-C13432CB23FB) Online
    - 192.168.110.203  (UUID 564D666C-EB23-CDC1-8101-95155E9EB916) Online
    
    Management cluster status: STABLE
    
    Number of nodes in control cluster: 3
    - 192.168.110.53   (UUID f5348a2e-2d59-4edc-9618-2c05ac073fd8)
    - 192.168.110.51   (UUID 03fad907-612f-4068-8109-efdf73002038)
    - 192.168.110.52   (UUID 1228c336-3932-4b5b-b87e-9f66259cebcd)
    
    Control cluster status: STABLE
    

  5. If you need information about individual NSX Controller appliance statuses, you can log into an NSX Controller and run the get control-cluster status command.
    nsx-controller-1> get control-cluster status
    uuid: 03fad907-612f-4068-8109-efdf73002038
    is master: true
    in majority: true
    uuid                                 address              status
    03fad907-612f-4068-8109-efdf73002038 192.168.110.51       active
    1228c336-3932-4b5b-b87e-9f66259cebcd 192.168.110.52       active
    f5348a2e-2d59-4edc-9618-2c05ac073fd8 192.168.110.53       not active
    
  6. Repeat the steps to reboot additional NSX Controller appliances if needed.