Configuration for B2B high availability
B2B high availability deployment includes both primary and secondary nodes that can operate in different high availability modes.
You can establish a B2B high availability cluster with automatic failover by configuring a DataPower® Gateway to monitor your currently active DataPower Gateway, which is also known as the primary gateway. Each DataPower Gateway is a node in the high availability cluster.
The secondary node monitors the primary node with heartbeats. A heartbeat is a periodic check by the secondary node to ensure that the primary node is responding to requests. The primary node also monitors its disks and the processes that are running on it to ensure that no hardware failure occurred.
B2B high availability configuration includes the following configuration modes.
- Active-passive mode
- In active-passive mode, the HA configuration is a two-node configuration that requires a standby
group in which the primary node is in the active state and the secondary node is in the passive
state. The primary node owns the virtual IP address that is defined in standby control. The
secondary node does not receive any traffic until the primary node fails.
The primary node runs the applications in a resource group. All traffic goes to the primary node. The primary node receives and processes all transactions. The secondary node does not receive any traffic but passively synchronize its persistence store with the persistence store of the primary node. In this way, if the primary node fails, the secondary node has the latest data that is needed to continue to process the transactions among trading partners. When the primary node fails, the secondary node takes over the workload for the primary node workload and the virtual IP.
To support fast failover of the virtual IP address, all relevant network switches must operate with the fast spanning tree algorithms that are enabled.