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
...
On the Kubernetes master, run the script:
...
| language | text |
|---|---|
| theme | RDark |
| title | sdnc.cluster |
...
(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:
| Code Block | ||||||
|---|---|---|---|---|---|---|
| ||||||
ubuntu@k8s-s1-master:/oom/kubernetes/sdnc/resources/geo/bin$ ./sdnc.cluster
active |
Alternatively, the sdnc.cluster script available in the PROM pod can be run:
| Code Block | ||||
|---|---|---|---|---|
| ||||
root@dev-prom-6485f566fb-hdhzs:/app/bin# ./sdnc.cluster
active |
Earlier Releases
Beijing
| Expand | |||||||||
|---|---|---|---|---|---|---|---|---|---|
The sdnc.cluster script is available in Beijing, though only on the Kubernetes master node. (The PROM component was introduced in Casablanca.)
|