Forum Discussion
Neo_Ph
Altocumulus
AltocumulusiRule cookie persistence and pool redirect
Hi all, base on the on below setup... When Pool A/NodeA1 goes down, we expect URI /beta/ requests to be sent to Pool B, as nodeA2 can't accept URI /beta/ requests. However, when Pool A/NodeA1 goes...
Tests were done in the production LTM instead, by creating a temporary VIP with same pool members. A few users were able to test via the temporary VIP, and everything was working as expected. Yet, it wasn't working on the production VIP.
I end-up creating a PoolC containing nodeA1 ONLY for /beta/ URI ONLY. That way /beta/ URI would never reach nodeA2 when nodeA1 is down.
If PoolC/nodeA1 is UP, then PoolC will be used. Otherwise, it will hit the 2nd condition, redirecting /beta/ to PoolB. Problem solved.
AlexBCT
Cumulonimbus
CumulonimbusHi Neo_Ph,
Seen that you get different behaviour in the lab as in live, that's interesting indeed! Have you gone through the virtual server configuration to ensure that they are exactly the same? Especially the profiles?
Also, can you check that the iRules in the live and lab systems are attached in the same order? (order very much matters when it comes to attaching iRules under the Resource tab)
And are there any other differences either in software or configuration between the live and lab systems?
Neo_PhAltocumulus
AltocumulusThere are a few differences such as the use of F5-TCP-WAN & F5-TCP-LAN in the lab, instead of just using tcp profile. There is only 1 iRule. But the major difference would be the lab version at 13.x vs Prod at 15.x.
I will have to upgrade to version 15.x and redo my tests. And also use the same profiles, just in case it would impact the way cookie persistence is operating; which would surprise me. I'll add an update afterwards. Thanks AlexBCT