Forum Discussion
Eric_Waite_1046
Nimbostratus
NimbostratusPersistence
I am a novice in BIG-IP and was hoping someone could point me in the correct direction.
I have 3 tomcat servers that I want to use in a pool in BIG-IP.
These 3 servers point to a single MS SQL database. One of these server also contains IIS.
When I use the GUI and use Cookie Insert witha fallback persistence of source_addr. I have some clients, that do not persist to their respective servers and get sessionId timeout errors. I have validated that the cookie is being received by the client.
What could cause a client to fall through cookie insert and source_addr? Especially since I see the cookie on the client side?
I have spoken to f5 support, they are stumped. Does someone have an idea that could send me in the right direction for an iRule. I was thinking about putting a text varible in the session that represents the server, that is randomly chose at login. Then parse this global session variable in BIG-IP and forward the traffic to the node. It seems like this should be built in.
Does anyone have any suggestions?
Thanks in advance.
hoolioCirrostratus
Hi,
Rather than re-inventing the wheel and building an iRule to replace the persistence functionality already present in the product I think it would be more efficient to work with support to troubleshoot the issue.
I realize you've tried this already, but I would expect they would be able to figure out the issue if you're able to provide tcpdumps and 'b persist ...' output for a failure.
Aaron