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.
active-standby pair
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 cluster
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.
BIG-IP hardware or virtual edition (VE).
device group
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.
fail over
fails over
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.
high availability
highly available
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
multiple-arm mode
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
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.
Two (2) BIG-IP devices configured to use the active-standby HA mode.
A BIG-IP partition is a logical container containing a defined set of BIG-IP system objects. See the BIG-IP documentation for more information.
Two (2) or more BIG-IP devices configured as an active device cluster.
segmentation ID
segmentation id
VLAN tag
SSL offloading
SSL offloading relieves a Web server of the processing burden of encrypting and/or decrypting traffic sent via the SSL security protocol.
A single BIG-IP device; no HA.
BIG-IP device (hardware or VE) deployed outside of OpenStack.
Virtual Clustered Multiprocessing (vCMP) is a feature of the BIG-IP system that allows you to run multiple instances of the BIG-IP software on a single hardware platform.
vCMP guest
A vCMP guest is an instance of BIG-IP software created on the vCMP system for the purpose of provisioning one or more BIG-IP modules to process application traffic.
vCMP host
The vCMP host is the system-wide hypervisor that makes it possible for you to create and view BIG-IP instances, or vCMP ‘guests’.