Forum Discussion
NimbostratusVIP monitoring multiple Pools
NimbostratusDario,
Here is the config,
VS:
ltm virtual test_443_VIP {
destination 10.xx.xx.xx:443
ip-protocol tcp
mask 255.255.255.255
pool abc_POOL
profiles {
rdmh_2018 {
context clientside
}
http { }
tcp { }
}
rules {
uri_forward
}
source 0.0.0.0/0
source-address-translation {
pool UP_snatpool
type snat
}
translate-address enabled
translate-port enabled
vs-index 19
}
Pools:
ltm pool ghi_POOL {
members {
x1:8082 {
address 10.xx.xx.xx
session monitor-enabled
state down
}
x2:8082 {
address 10.xx.xx.xx
session monitor-enabled
state down
}
}
monitor http_keepalive_html
}
ltm pool jkl_POOL {
members {
x3:4082 {
address 10.xx.xx.xx
session monitor-enabled
state down
}
x4:4082 {
address 10.xx.xx.xx
session monitor-enabled
state down
}
}
monitor http_keepalive_html
}
ltm pool abc_POOL {
members {
a1:8081 {
address 10.xx.xx.xx
session monitor-enabled
state up
}
a2:8081 {
address 10.xx.xx.xx
session monitor-enabled
state up
}
}
monitor http_keepalive_html
}
ltm pool def_POOL {
members {
b1:8084 {
address 10.xx.xx.xx
session monitor-enabled
state up
}
b2:8084 {
address 10.xx.xx.xx
session monitor-enabled
state up
}
}
monitor http_keepalive_html
}
irule:
when HTTP_REQUEST {
switch -glob [string tolower [HTTP::uri]] {
"/abc*" {
pool abc_POOL
}
"/def*" {
pool def_POOL
}
"/ghi*" {
pool ghi_POOL
}
"/jkl*" {
pool jkl_POOL
}
default {
reject
}
}
}
Here in my config my default pool is abc_POOL.other pools were added in irule only. though ghi_POOL, jkl_POOL were down, VS is still showing UP.
I am looking for a way where if any of the Pools (abc_POOL, def_POOL, ghi_POOL, jkl_POOL) is down, then I want to mark the Virtual Server down.
NoctilucentThe normal behaviour is to not mark VS 'down' if at least one of the configured pools is 'up'.
I don't know if it's possible, but you can try to create an iRule with 'active_members' to compare if one of the pools is mark as 'down'. After that, you can use 'LB::down' to force all pool members down.
https://clouddocs.f5.com/api/irules/active_members.html
https://clouddocs.f5.com/api/irules/LB__down.html
Base on this info, I don't know for sure if this solution is feasible:
"Note: Calling LB::down in an iRule triggers an immediate monitor probe regardless of the monitor interval settings."
Other thing you can do and it's feasible it's to configure an iCall which runs when one of those pools is down for disabling the VS.
REF - https://devcentral.f5.com/s/articles/what-is-icall-27404
KR,
Dario.
