How do I view the global auxiliary database status?

Purpose

Perform this procedure to display the standalone or geo-redundant auxiliary database cluster status.

Steps
 
1 

To display the cluster status from a main server station that is not part of a shared-mode NSP deployment:

  1. Log in to the station as the root user.

  2. Open a console window.

  3. Enter the following:

    # nspdctl auxdb status↵

    Cluster status information such as the following is displayed:

    CLUSTER    DC-ROLE   STATE

    cluster_1  ACTIVE    UP

    NODE           INTERNAL IP   STATE

    203.0.113.101  10.1.2.101    UP

    203.0.113.102  10.1.2.102    UP

    203.0.113.103  10.1.2.103    UP

    CLUSTER    DC-ROLE   STATE

    cluster_2  STANDBY   ON_STANDBY

    NODE           INTERNAL IP    STATE

    203.0.113.104  10.1.2.104     READY

    203.0.113.105  10.1.2.105     READY

    203.0.113.106  10.1.2.106     READY

  4. View the information.

  5. If each STATE value is not as shown above, alert technical support.

  6. Close the console window.

2 

To display the cluster status from a main server station that is part of a shared-mode NSP deployment:

Note: The cluster_1 and cluster_2 values in the status information below correspond to the ipList and standbyIpList parameter values in the auxDb section of the NSP configuration file.

Note: In order to issue a REST API call, you require a REST token; see the My First NSP API Client tutorial on the Network Developer Portal for information.

  1. Issue the following REST API call:

    GET https://address:8545/RESTCONF/data/auxdb:/clusters

    where address is the advertised address of the NSP system

    The call returns auxiliary database cluster status information like the following:

    <HashMap>

        <clusters>

            <cluster>

                <name>cluster_1</name>

                <mode>ACTIVE</mode>

                <status>UP</status>

                <nodes>

                    <external-ip>203.0.113.101</external-ip>

                    <internal-ip>10.1.2.101</internal-ip>

                    <status>UP</status>

                </nodes>

                <nodes>

                    <external-ip>203.0.113.102</external-ip>

                    <internal-ip>10.1.2.102</internal-ip>

                    <status>UP</status>

                </nodes>

                <nodes>

                    <external-ip>203.0.113.103</external-ip>

                    <internal-ip>10.1.2.103</internal-ip>

                    <status>UP</status>

                </nodes>

            </cluster>

            <cluster>

                <name>cluster_2</name>

                <mode>STANDBY</mode>

                <status>ON_STANDBY</status>

                <nodes>

                    <external-ip>203.0.113.104</external-ip>

                    <internal-ip>10.1.2.104</internal-ip>

                    <status>READY</status>

                </nodes>

                <nodes>

                    <external-ip>203.0.113.105</external-ip>

                    <internal-ip>10.1.2.105</internal-ip>

                    <status>READY</status>

                </nodes>

                <nodes>

                    <external-ip>203.0.113.106</external-ip>

                    <internal-ip>10.1.2.106</internal-ip>

                    <status>READY</status>

                </nodes>

            </cluster>

        </clusters>

    </HashMap>

  2. View each status value.

  3. If each status value is not as shown above, contact technical support.

3 

Close the console window.

End of steps