Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 13 Next »

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:

sdnc.cluster
ubuntu@k8s-s1-master:/dockerdata-nfs/cluster/script$ ./sdnc.cluster
active
ubuntu@k8s-s1-master:/dockerdata-nfs/cluster/script$

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.

  • No labels