This article provides information about manually switching the HA roles of your primary and secondary Sockets.
Overview
Manual high availability (HA) failover lets you test your Socket environment by temporarily failing a site over to the Secondary Socket from within the Cato Management Application (CMA). This can help to validate that HA is correctly configured and responsive to failover events
This capability gives you control over failover timing, allowing for a safer and more predictable validation process. Use the Socket page fail over to the Secondary Socket.
Important:
Ensure that onsite Socket personnel are available before performing a manual HA failover in case any issues require physical access.
Do not use the manual HA failover to perform Socket maintenance - this can create a split-brain issue for the Sockets
How Manual Failover Works
Triggering a manual failover from the CMA performs these actions:
The CMA tells the Primary Socket to stop sending VRRP packets
The Secondary Socket detects the failure and takes over as the Primary Socket
After approximately 120 seconds, the CMA displays:
Status: HA not ready
Both Sockets may temporarily appear as Primary (split-brain scenario), indicating the Secondary has taken ownership
This behavior is expected and confirms that the Secondary is now active.
Prerequisites
Before triggering a manual HA failover, make sure:
Both Sockets are running Socket version 24 or higher
The HA state is Ready in the CMA
Best Practices
Do not leave the environment in a manual failover state longer than necessary
Use this feature only for maintenance or validation scenarios
Always return HA to a Ready state promptly to maintain system resilience
Activating Manual HA Failover

To trigger the manual failover:
From the navigation menu, select Socket > Actions > Activate Manual HA Failover.
Wait approximately 120 seconds.
Refresh the Socket page to verify the new status.
Reverting to the Primary Socket
You can return control to the Primary Socket in one of the following ways:
Option 1: From the navigation menu, select Socket > Actions > Stop HA Failover
Option 2: Restart the Primary Socket. The CMA automatically restores the original HA configuration to the site.