Forum Discussion
How to mark VS down when default pool goes down
Hello,
I have came across very strange behavior from f5. When default PoolA marked down by health monitor then VS is stays up because PoolB is up. Hence GTM will not mark node down for fail over. VS will only be marked down if PoolA and PoolB goes down. Is there anyway I configure if PoolA goes down mark VS down or mark PoolB down?
I have got following irule applied on VS.
Thanks
Vishal
when HTTP_REQUEST {
switch -glob [string tolower [HTTP::path]] {
"/test/*" {
pool poolB
}
default {
pool poolA
}
}
}
2 Replies
- IainThomson85_1
Cumulonimbus
If I understand correctly, you've got a GTM Providing DNS for services to LTM VIP's
To solve your problem, I would create a "Dummy" Virtual server on the LTM, with Pool A (or pool B, whichever is the non-default pool on the normal vip) and assign dependencies based on this availbility.
Therefore the GTM would only advertise/respond to requests via DNS if both pools are up.
Hope that makes sense.
do you have an actual default pool assigned? so not via the irule, but on the virtual server?
if you have one then that one determines the up / down state of the virtual server, so next to the irule you could do that.
also see: http://support.f5.com/kb/en-us/solutions/public/6000/500/sol6514
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com
