Overview

With SDN-C deployed in a geo-redundant fashion, activity can be switched from one site to the other in one of two ways:

• manually by the site operator
• automatically via PROM, based on healthiness of active site

Manual (forced) failover

From the Kubernetes master node in the site, simply run the makeActive script:

# /path/makeActive

Automatic failover

The PROM instance in each SDN-C site is responsible for monitoring the health of the local site as well as the role of the site so that it may decide whether or not the local site should be made the active site.

The following script can be used to switch between the primary and secondary roles for an SDNC server.

Pre-condition:

 1. The script “sdnc.failover” has dependencies on script “sdnc.cluster”, “sdnc.isPrimaryCluster” and “switchVoting.sh”.

 2. Run as "ubuntu" instead of "root".

To execute:

(1)    Make sure to run as “ubuntu”.

(2)    Run “./sdnc.failover” in the command line.

Expected results:

(1)    Return result as “success”. The clustering role should be changed from “active” to “standby”, or vice versa. Type “./sdnc.cluster” to confirm.

(2)    Return result as “failure”. The clustering role should not be changed.