Simple Redundant Topology

You can have redundancy of clustering without Bonding.

If a switch or Cluster Member Security Gateway that is part of a cluster. fails, a High Availability A redundant cluster mode, where only one Cluster Member (Active member) processes all the traffic, while other Cluster Members (Standby members) are ready to be promoted to Active state if the current Active member fails. In the High Availability mode, the Cluster Virtual IP address (that represents the cluster on that network) is associated: (1) With physical MAC Address of Active member (2) With virtual MAC Address. Synonym: Active/Standby. Acronym: HA. cluster Two or more Security Gateways that work together in a redundant configuration - High Availability, or Load Sharing. solution provides system redundancy.

For example, you can have a redundant system with two synchronized Cluster Members deployed in a simple redundant topology.

Item	Description
1	Cluster Member GW1 with interfaces connected to the external switches (5 and 6)
2	Cluster Member GW2 with interfaces connected to the external switches (5 and 6)
3	Interconnecting network C1
4	Interconnecting network C2
5	Switch S1
6	Switch S2

If Cluster Member GW1 (1), its NIC, or switch S1 (5) fails, Cluster Member GW2 (2) becomes the only Active State of a Cluster Member that is fully operational: (1) In ClusterXL, this applies to the state of the Security Gateway component (2) In 3rd-party / OPSEC cluster, this applies to the state of the cluster State Synchronization mechanism. member, connecting to switch S2 (6) over network C2 (4).

If any component fails (Cluster Member, NIC, or switch), the result of the failover Transferring of a control over traffic (packet filtering) from a Cluster Member that suffered a failure to another Cluster Member (based on internal cluster algorithms). Synonym: Fail-over. is that no further redundancy exists.

A further failure A hardware or software problem that causes a Security Gateway to be unable to serve as a Cluster Member (for example, one of cluster interface has failed, or one of the monitored daemon has crashed). Cluster Member that suffered from a failure is declared as failed, and its state is changed to Down (a physical interface is considered Down only if all configured VLANs on that physical interface are Down). of any active component completely stops network traffic through this cluster.