Manual Chapter :
High Availability (HA)
Failover
Applies To:
Show Versions
BIG-IP LTM
- 17.1.1, 17.1.0, 17.0.0, 16.1.5, 16.1.4, 16.1.3, 16.1.2, 16.1.1, 16.1.0, 16.0.1, 16.0.0, 15.1.9, 15.1.8, 15.1.7, 15.1.6, 15.1.5, 15.1.4, 15.1.3, 15.1.2, 15.1.1, 15.1.0, 15.0.1, 15.0.0, 14.1.5, 14.1.4, 14.1.3, 14.1.2, 14.1.0, 14.0.1, 14.0.0
High Availability (HA)
Failover
High Availability (HA)
Failover
High Availability (HA)
Failover
High Availability (HA)
Failover
Overview
A BIG-IP® system provides high availability via packet mirroring across
two chassis. When discussing redundancy, one should consider more than the initial failover. If
the backup chassis also fails a fail-back will be required. The following tables provides a quick
summary of the initial failover and the fail-back scenarios. Note, a BIG-IP system does not
support Geo-Redundant failover. In other words, a BIG-IP system supports the concept of a local
HA Pair. However, a BIG-IP system does not support a second HA Pair which will take over if the
first HA Pair fails. This type of scenario is required where multiple redundant data centers are
available to handle geographic failure scenarios.
SIP HA Support
Control Messages |
Media |
|
|---|---|---|
Failover (active failed) |
Supported |
Supported |
Failback (new active failed after old active came back online) |
Supported |
Partial Support |
The above table shows that after the initial failover, if a second failover happens, the media
streams, created after the failover, will be maintained. However, media streams created prior to
the initial failover will be dropped.
Configuration Guideline
For each BIG-IP in Traffic Group
- Check the tmm count to be same on each blade as well as each device.
- tmsh list sys db provision.tmmcountactual.
- Load the stable build from your branch. (Make sure it’s the same build on each device)
- Load the default config. (Start Fresh)
- tmsh load sys config default.
- Configure hostname/users on each device
- Provision the device with Management – “Small”, LTM – “Nominal”
- Exit wizard by clicking ‘Finished’ on each device
- Create vlans (internal/external/HA – advised to create 3 vlans to keep traffic discrete)
- GUI:
- Network >> vlans >> new
- TMSH:
- tmsh create net vlan <VLAN_NAME> interfaces add {1.1 {tagged}} tag <TAG_ID>
- Create self-ip for each vlan and floating self-ip for both internal and external vlan ( internal,external and HA- with traffic-group-local-only and internal_float, external_float with traffic-group-1)
- GUI:
- Network >> self-ips >> new
- TMSH:
- tmsh create net self <SELF_IP_NAME> address <IP_ADDRESS/PREFIX> allow-service default traffic-group <TRAFFIC-GROUP-NAME> vlan <VLAN_NAME>.
- Set Config sync address:
- GUI:
- Device Management >> Devices >> (self device) >> Device Connectivity >> ConfigSync
- Specify HA self ip
- TMSH:
- tmsh modify cm device <DEVICE_NAME> configsync-ip <SYNC_SELF_IP>
- Set Mirror address (if mirroring is desired): (For clusters make sure network mirroring is “Between Clusters”.)
- GUI:
- Device Management >> Devices >> (self device) >> Device Connectivity >> Mirroring
- Specify HA self ip
- TMSH:
- tmsh modify cm device <DEVICE_NAME> mirror-ip <MIRROR_SELF_IP>
- Set Failover unicast address(es): (GUI preferred)
- GUI:
- Device Management >> Devices >> (self device) >> Device Connectivity >> Failover
- Add
- Specify HA self ip (as well as mgmt. Ip for backup)
- TMSH:
- tmsh modify cm device <DEVICE_NAME> unicast-address { { effective-ip <HA_IP_ADDRESS>} { effective-ip <MGMT_IP_ADDRESS>}}
Primary BIG-IP
- Discover device(s) for trust: (GUI Preferred)
- GUI:
- Device Management >> Device Trust >> Peer List
- Add…
- Enter IP and credentials for peer device
- TMSH:
- tmsh modify cm trust-domain /Common/Root ca-devices add { <IP_OF_REMOTE_DEVICE>} name <NAME_OF_REMOTE_DEVICE> username admin password <ADMIN_PASSWORD>
- Each device should now have a trust-sync created device group (not visible) and should show as ‘In Sync’ and ACTIVE
- Create a device-group of type sync-failover
- GUI:
- Device Management >> Device Groups
- new
- Enter name
- Specify type of sync-failover
- Specify network failover
- Add both devices
- Save
- TMSH:
- tmsh create cm device-group <DGFO_NAME> devices add {<DEVICE_1_NAME>… <DEVICE_2_NAME>} type sync-failover network-failover enabled
- Perform initial sync of device-group failover.
- GUI:
- Device Management >> Overview >> Select device-group failover >> Select a device
- Click ‘Sync’
- TMSH:
- tmsh run cm config-sync to-group <DGFO_NAME>
- Devices should now show as ‘In sync’, but one should be ACTIVE the other STANDBY.
