Both BIG-IP devices in a pair are in an active state, processing traffic for different virtual servers or SNATs. If one device fails over, the remaining device processes traffic from the failed device in addition to its own traffic.
Only one of the two BIG-IP devices is in an active state – that is, processing traffic – at any given time. If the active device fails over, the second device enters active mode and processes traffic that was originally targeted for the primary device.
device service cluster
device service clusters
Device Service Clustering provides synchronization and failover of BIG-IP configuration data among multiple BIG-IP devices on a network. You can configure a BIG-IP device on a network to synchronize some or all of its configuration data among several BIG-IP devices; fail over to one of many available devices; and/or mirror connections to a peer device to prevent interruption in service during failover.
A device group is a component of a device service cluster. It consists of a collection of BIG-IP devices that trust each other and can synchronize, and sometimes fail over, their configuration data.
Failover occurs when one device in an active-standby pair becomes unavailable; the secondary device processes traffic that was originally targeted for the primary device.
The ability of a BIG-IP device to process network traffic successfully. An HA device is generally part of a device cluster.
A BIG-IP system redundancy feature that ensures sharing of connection and persistence information across a device service cluster; mirroring helps prevent service interruptions if/when failover occurs.
Multi-arm mode is a network topology wherein servers/clients connect to the BIG-IP via different interfaces; use two or more VLANs to separate management and data traffic.
One-arm mode is a network topology wherein servers/clients connect to the BIG-IP via a single interface; a single VLAN handles all traffic.
BIG-IP virtual edition (VE) deployed as an OpenStack instance.