Forum Discussion
Andrea_Knapp_28
Nimbostratus
Mar 28, 2006Pinning sessions to a node with a failover node
Currently I have a regular pool set up with active insert persistence, including 4 nodes. However we are seeing sessions expiring, from what appears to be the cookie from one node ending up on the wrong node. We are currently running 4.2PTF9 hoping to upgrade very soon, but not soon enough to solve this issue.
So as a 'quick/interim fix' I am trying to figure out a way to pin a session to one node, but if that node is down to have it 'failover' to a different node.
I have this, but don't think the logic is quite right:
pool Node1_only_pool {
min_active_members 1
member 192.6.9.22:9011 priority 10
}
pool Node2_only_pool {
min_active_members 1
member 192.6.9.23:9011 priority 10
}
rule my_rule {
if ( http_host starts_with "URLNAME" ) {
use ( Node1_only_pool )
}
else {
use ( Node2_only_pool )
}
}
I want to consistently use Node1 and only use Node2 if Node1 fails. Just not sure how to create a rule to see if Node1 is down.
Thank you,
Andrea
- Deb_Allen_18Historic F5 AccountHi Andrea -
- zafer
Nimbostratus
Hi deb, - Deb_Allen_18Historic F5 Account
- aesguerra_1951
Nimbostratus
Hi All,
Recent Discussions
Related Content
DevCentral Quicklinks
* 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
Discover DevCentral Connects