Activating the Failover Node
Activating the failover node on a involves these three steps at a high level:
gateway83
Activating the failover node on a
API Gateway
involves these three steps at a high level:- Log in to the Disaster Recovery (DR) node.
- Stop replication.
- Activate the node.
Once the node is activated, you can route traffic to it.
In this topic, the two nodes in the cluster are referred to as
Gateway1
and Gateway2,
where Gateway1
is the database node hosting the primary database. The DR node being configured is referred to as Gateway-DR.
It is very important that the slave on the DR node is disabled. This is a precaution, should the database on Gateway2 inadvertently come back up.
To activate the failover node:
- Access the privileged shell on Gateway-DR.
- Stop the database from slaving the secondary node:#mysqladmin stop-slaveSlave stopped #mysql -e "SHOW SLAVE STATUS\G" | grep RunningSlave_IO_Running: No Slave_SQL_Running: No
- (Optional) Disable replication monitoring in crontab:#crontab -e# Monitor DR database replication#0 * * * * /usr/local/bin/monitor_replication.sh
- Exit the privileged shell and return to the Gateway main menu.
- Select the following options:2( Display CA API Gateway Configuration menu),3(Configure the CA API Gateway),4(Node Configuration).
- Enteryesto enable the node.
- SelectS(Save and exit). You are presented with a summary of the configuration that will be applied:--------------------- Configuration Summary --------------------- Press < to go to the previous step, type "quit" to quit.The following configuration will be applied:Database Connection Database Host = localhost Database Port = 3306 Database Name = ssg Database Username = gatewayNode Configuration Enabled = YesPress [Enter] to continue.
- Review the summary carefully and then pressEnterto apply the configuration. This may take a moment to complete.
- Upon completion, pressEnterto return to the Gateway Configuration menu.
- Select option7(Manage CA API Gateway status) to check state of the Gateway startup. If it is not running, exit back to the menu and wait, then select option 7 again. When you seeNode Status = RUNNING, proceed to the next step.
- Exit the Gateway main menu and confirm that the Policy Manager can connect to the DR node directly.
- Configure the network routing infrastructure to route messages to the DR system.