NimbostratusHi F5 peers,
Need some help on how to approach a requirement from our DB team.
Customized LB which distributes traffic to pool_member 1 and pool-member2. If and when pool_member2 is unavailable traffic should go to pool_member1. But if pool_member1 is unavailable it SHOULD NOT go to pool_member2.
Thanks in advance!!
NimbostratusHi,
when HTTP_REQUEST {
if { [active_members [pool_1] ] > 0 } {
if { !([lsearch -exact [active_members -list pool_1] pool_member1:its_port]) } {
reject
}
}
}
Nimbostratus
CirrostratusHi,
when HTTP_REQUEST {
if { [active_members [pool_1] ] > 0 } {
if { !([lsearch -exact [active_members -list pool_1] pool_member1:its_port]) } {
reject
}
}
}
This iRule will check if member1 is down. If it is, the request will be rejected. Then you also have to define priority group into your pool, with a higher priority for your member_2.
NimbostratusYes, I don't see any way to do it without iRules.
CumulonimbusYou could also do member-specific monitors applied to member_2. the first monitor would be the monitor used to check member_2, the second monitor could check the status of member_1 using monitor configuration items alias-address and alias-port settings that specify member_1
NimbostratusCumulonimbus
NimbostratusYou could also do member-specific monitors applied to member_2. the first monitor would be the monitor used to check member_2, the second monitor could check the status of member_1 using monitor configuration items alias-address and alias-port settings that specify member_1
NimbostratusNimbostratus