By default, HA takeover occurs only if the primary node (This node) stops working or becomes unreachable from the secondary node (Other node). However, this does not cover the scenario when the primary node becomes unaccessible to the outside world (for example its external interface or the router or switch connected to the external interface breaks down) while the secondary node would be still accessible (for example because it is connected to a different router).

To address such situations, you can specify IP addresses (usually next hop routers) to continuously monitor from both the primary and the secondary nodes using ICMP echo (ping) messages. One such address can be set up for every interface.

When setting up next hop monitoring, you have to make sure that the primary and secondary nodes can ping the specified address directly. You can either:

  • Choose the addresses of the redundant-HA syslog-ng Store Box (SSB) interfaces so that they are on the same subnet as the next-hop address

  • Configure the next-hop device with an additional IP-address that is on the same subnet as the redundant-HA SSB interfaces facing it

If any of the monitored addresses becomes unreachable from the primary node while being reachable from the secondary node (in other words, more monitored addresses are accessible from the secondary node), then it is assumed that the primary node is unreachable and a forced takeover occurs — even if the primary node is otherwise functional.

Naturally, if the secondary node is not capable of taking over the primary node (for example, because there is data not yet synchronized from the current primary node), no takeover is performed.

The following describes how to configure next hop monitoring.

To configure next hop monitoring

  1. Navigate to Basic Settings > High Availability > Next hop monitoring.

  2. Select the interface to use for monitoring its next-hop router.

    Figure 63: Basic Settings > High Availability > Next hop monitoring — Configuring next hop monitoring

  3. Enter the IP address to monitor from the current primary node (for example, the IP address of the router or the switch connected to the interface) into the This node > Next hop monitoring > Interface IP field of the selected interface. This IP address must be a real IP address that is visible from the interface, and must be on the same local network segment.

  4. Enter the IP address to monitor from the current secondary node (for example, the IP address of the router or the switch connected to the interface) into the Other node > Next hop monitoring > Interface IP field of the selected interface. This IP address must be a real IP address that is visible from the interface, and must be on the same local network segment.

  5. Repeat the previous steps to add IP addresses to be monitored from the other interfaces if needed.

  6. Click .

    		 Caution:

    For the changes to take effect, you have to restart both nodes. To restart both nodes, click Reboot Cluster.