For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

High Availability Groups on BIG-IP

High Availability of applications is critical to an organization’s survival. On BIG-IP, HA Groups is a feature that allows BIG-IP to fail over automatically based not on the health of the BIG-IP s...
Published Apr 18, 2017
Version 1.0
application delivery
BIG-IP
fail over
ha groups
high availability
LTM
PSilva's avatar
Ret. Employee
Technical writer, evangelist, speaker, video host, story teller and overall clever guy. Bringing the slightly theatrical and fairly technical together, I train, write, speak, along with overall evangelism. Highly technical information security professional with social media skills who has also been in such plays as The Glass Menagerie, All’s Well That Ends Well, Cinderella and others.
View Profile
PSilva's avatar
Ret. Employee
Technical writer, evangelist, speaker, video host, story teller and overall clever guy. Bringing the slightly theatrical and fairly technical together, I train, write, speak, along with overall evangelism. Highly technical information security professional with social media skills who has also been in such plays as The Glass Menagerie, All’s Well That Ends Well, Cinderella and others.
View Profile
dragonflymr's avatar
dragonflymr
Icon for Cirrostratus rankCirrostratus
Apr 19, 2017

Hi,

 

Very nice article. I am a bit confused by differences in article pictures (as well as in video "Setting up HA Groups (part 2 of 2)").

 

On first picture there are three HA Groups named ha_group_deviceA_tg1, ha_group_deviceB_tg1, ha_group_deviceC_tg1 (configuration in video is as well using those names)

 

On second picture all HA Groups are named ha_group_deviceA_tg1

 

Is that correct?

 

Another question I have is related to video. In presented config there are three pools, HA Group on each device is using different pool.

 

What is logic behind it? Each pool contains members only available on given BIG-IP, like members of poolA are available only on BIG-IP A and so on?

 

Or members from all pools are available via all BIG-IPs but each pool is containing members pointing to different servers? It makes little sense if members in all pools are pointing to the same servers because then member Down will be reported in all pools - except of course if each BIG-IP has completely separate network path to the same servers - or I am wrong here?

 

Piotr