After you perform a maintenance in your environment, verify that the deployed NSX Controller instances are operational.

About this task

After you patch, update or upgrade, restore the NSX instances, or after failover or failback during disaster recovery of the management applications, verify the following configuration:

  • Software version and connectivity status of the NSX Controller instances 

  • Software version of vSphere Installation Bundles (VIBs) on the ESXi hosts

Procedure

  1. Log in to vCenter Server by using the vSphere Web Client.
    1. Open a Web browser and go to the following URL.

      Region

      Operation Type

      Management vCenter Server URL

      Region A

      • Failback

      • Update

      • Patch

      • Restore

      https://sfo01m01vc01.sfo01.rainpole.local/vsphere-client

      Region B

      • Failover

      • Update

      • Patch

      • Restore

      https://lax01m01vc01.lax01.rainpole.local/vsphere-client

    2. Log in using the following credentials.

      Setting

      Value

      User name

      administrator@vsphere.local

      Password

      vsphere_admin_password

  2. Select Home > Networking & Security and in the Navigator pane click Installation.
  3. On the Management tab, select an NSX Manager, and verify the connectivity status and the version of each controller node.
    Table 1. NSX Controller Instances to Verify in Region A

    NSX Controller location

    Operation Type

    NSX Manager

    Controller Node

    NSX Controller instances for the management cluster

    • Failback

    • Update

    • Patch

    • Restore

    172.16.11.65

    • 172.16.11.118

    • 172.16.11.119

    • 172.16.11.120

    NSX Controller instances for the shared edge and compute cluster

    • Update

    • Patch

    • Restore

    172.16.11.66

    • 172.16.31.118

    • 172.16.31.119

    • 172.16.31.120

    Table 2. NSX Controller Instances to Verify in Region B

    NSX Controller location

    Operation Type

    NSX Manager

    Controller Node

    NSX Controller instances for the management cluster

    • Failover

    • Update

    • Patch

    • Restore

    172.17.11.65

    • 172.17.11.118

    • 172.17.11.119

    • 172.17.11.120

    NSX Controller instances for the shared edge and compute cluster

    • Failover

    • Update

    • Patch

    • Restore

    172.17.11.66

    • 172.17.31.118

    • 172.17.31.119

    • 172.17.31.120

    Controller Node

    Expected Value

    Status

    Connected

    Peers

    Green icons

    Software Version

    Updated to the version applied during maintenance

  4. Repeat the step for the NSX Controller instances on the other NSX Manager instances.
    Note:

    Each controller in the primary NSX Manager has an inherited controller instance in the secondary NSX Manager. Verify that the status of those instances is Connected.

  5. Verify the status of the NSX VIBs on the management and shared edge and compute clusters.
    1. On the Installation page, click the Host Preparation tab.
    2. From the NSX Manager drop-down menu, select the 172.16.11.65 NSX Manager.
    3. Expand the sfo01-m01-mgmt01 cluster and verify that the following settings are configured.
      Table 3. Hosts to Verify NSX VIBs on in Region A

      Cluster

      NSX Manager

      Hosts Cluster

      Hosts

      NSX Controller instances for the management cluster

      172.16.11.65

      sfo01-m01-mgmt01

      • sfo01m01esx01.sfo01.rainpole.local

      • sfo01m01esx02.sfo01.rainpole.local

      • sfo01m01esx03.sfo01.rainpole.local

      • sfo01m01esx04.sfo01.rainpole.local

      NSX Manager for the shared edge and compute cluster

      172.16.11.66

      sfo01-w01-comp01

      • sfo01w01esx01.sfo01.rainpole.local

      • sfo01w01esx02.sfo01.rainpole.local

      • sfo01w01esx03.sfo01.rainpole.local

      • sfo01w01esx04.sfo01.rainpole.local

      Table 4. Hosts to Verify NSX VIBs on in Region B

      Cluster

      NSX Manager

      Hosts Cluster

      Hosts

      NSX Controller instances for the management cluster

      172.17.11.65

      lax01-m01-mgmt01

      • lax01m01esx01.lax01.rainpole.local

      • lax01m01esx02.lax01.rainpole.local

      • lax01m01esx03.lax01.rainpole.local

      • lax01m01esx04.lax01.rainpole.local

      NSX Manager for the shared edge and compute cluster

      172.17.11.66

      lax01-w01-comp01

      • lax01w01esx01.lax01.rainpole.local

      • lax01w01esx02.lax01.rainpole.local

      • lax01w01esx03.lax01.rainpole.local

      • lax01w01esx04.lax01.rainpole.local

      Object

      Setting

      Expected Value

      sfo01-m01-mgmt01 cluster

      Installation Status

      nsx_version

      Firewall

      Enabled

      VXLAN

      Configured

      Hosts in the cluster

      Installation Status

      nsx_version

      Firewall

      Enabled

    4. Repeat the steps for the remaining NSX Manager instances.
  6. (Optional) Confirm that the NSX VIBs on the hosts are updated.
    1. Open an SSH connection to a host in a cluster with user name root and password esxi_root_user_password.

      Cluster

      Host

      sfo01-m01-mgmt01

      sfo01m01esx01.sfo01.rainpole.local

      sfo01-w01-mgmt01

      sfo01w01esx01.sfo01.rainpole.local

      lax01-m01-mgmt01

      lax01m01esx01.lax01.rainpole.local

      lax01-w01-mgmt01

      lax01w01esx01.lax01.rainpole.local

    2. Run the following console command. 
      esxcli software vib list | grep esx
    3. In the command output, make sure that the esx-nsxv VIB has been updated to the expected version.
    4. Verify that the User World Agent (UWA) in the ESXi host is running.
      /etc/init.d/netcpad status
    5. Repeat the steps for a host in each of the other clusters in the SDDC.