How do I check the auxiliary database status?

Purpose

Perform the following procedures to obtain the status of the auxiliary database clusters in an NSP deployment through RESTCONF APIs or the NSP UI.

Steps

Check the auxiliary database status from the NSP UI.

 
1 

As an NSP administrator, choose System Health from the NSP main menu.

2 

View the information in the Auxiliary Database Clusters panel, which lists the following:

  • Backup status

    • Scheduled backup—whether backups are enabled

    • Next backup—date and time

    • Last backup—date and time when the last backup started. This field indicates whether the backup is scheduled or manual. The status of the last backup is displayed only if it fails.

  • Clusters

    • Status and cluster name—the dot beside the name shows the cluster status

    • Role—active or standby

    • Status—whether the cluster is up

    • Alarms—number of alarms per type

To view expanded details for a cluster, click Show nodes below the cluster details to display the following:

  • Status and IP address or cluster name—the dot beside the IP address or name of the cluster shows the cluster status

  • Node status—whether the node is up

  • Proxy status—whether the auxiliary database proxy is up

  • Internal address—internal cluster address

End of steps

Steps

Check the current status of the auxiliary database clusters from RESTCONF APIs.

 
1 

Log in to a station that has access to the NSP system.

2 

Open a console window.

3 

Issue the following RESTCONF API call:

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

GET https://address/restconf/data/auxdb:/clusters

where address is the NSP advertised address

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>

4 

View each status value.

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

5 

If each status value of the standby cluster nodes is not READY, contact technical support.

Each status value of the active cluster nodes is expected to be UP.

6 

Close the console window.

End of steps