Gateway

Forcing failover on the primary or secondary node

January 8, 2024

Contributed by:

C S C

If you force failover on the primary node, the primary becomes the secondary and the secondary becomes the primary. Forced failover is possible only when the primary node can determine that the secondary node is UP.

If the secondary node is DOWN, the force failover command returns the following error message: “Operation not possible due to invalid peer state. Rectify and retry.”

If the secondary system is in the claiming state or inactive, the command returns the following error message: Operation not possible now. Please wait for system to stabilize before retrying.

If you run the force failover command from the secondary node, the secondary node becomes primary and the primary node becomes secondary. A force failover can occur only if the secondary node’s health is good and the node is not configured to stay secondary.

If the secondary node cannot become the primary node, or if secondary node was configured to stay secondary (using the STAYSECONDARY option), the node displays the following error message: “Operation not possible as my state is invalid. View the node for more information.”

To force failover on the primary or secondary node

In the configuration utility, on the Configuration tab, in the navigation pane, expand System and then click High Availability.
In the details pane, on the Nodes tab, select the primary node, and then in Actions, click Force Failover.
In the Warning dialog box, click Yes.

The official version of this content is in English. Some of the Cloud Software Group documentation content is machine translated for your convenience only. Cloud Software Group has no control over machine-translated content, which may contain errors, inaccuracies or unsuitable language. No warranty of any kind, either expressed or implied, is made as to the accuracy, reliability, suitability, or correctness of any translations made from the English original into any other language, or that your Cloud Software Group product or service conforms to any machine translated content, and any warranty provided under the applicable end user license agreement or terms of service, or any other agreement with Cloud Software Group, that the product or service conforms with any documentation shall not apply to the extent that such documentation has been machine translated. Cloud Software Group will not be held responsible for any damage or issues that may arise from using machine-translated content.

Forcing failover on the primary or secondary node

January 8, 2024

Contributed by:

C S C

January 8, 2024

Contributed by:

C S C

Forcing failover on the primary or secondary node

To force failover on the primary or secondary node

In this article