Overview

In order to detect the current role of the local SDN-C site within the pair of sites, the 'sdnc.cluster' script can be used.

It is important for the operator to determine what role a site is playing so that they may know whether the site is currently handling incoming messaging and, therefore, whether it's desirable to invoke a manual fail-over (see SDN-C Site Failover).

If an operator has been made aware of a fault in, say, Site 2, they should run the sdnc.cluster command on Site 2 to determine whether Site 2 is 'active'. If the site is, instead, 'standby', there is no reason to perform a fail-over. The operator can proceed with resolving the fault on Site 2 so it is available to support a future fail-over.

Show site role

Site role is determined by querying the SDN-C OpenDaylight cluster to see if the local members are voting (active) or non-voting (standby).

On the Kubernetes master, run the script:

ubuntu@k8s-s1-master:/oom/kubernetes/sdnc/resources/geo/bin$ ./sdnc.cluster
active
ubuntu@k8s-s1-master:/oom/kubernetes/sdnc/resources/geo/bin$

Alternatively, the sdnc.cluster script available in the PROM pod can be run directly:

root@dev-prom-6485f566fb-hdhzs:/pathapp/to/scripts#bin# ./sdnc.cluster
active
root@dev-prom-6485f566fb-hdhzs:/path/to/scripts#