Irule issue

Hi Renith,

 

 

I would guess the problem is the opposite: when a client makes a request and is load balanced to the 10.103.42.101:http member, they establish a session and are sent a persistence cookie by LTM. Then when they make a request which matches the URI checks, they are sent to the 10.103.42.100:http server where they don't have a valid session.

 

 

Another possibility is that they are sent to the 10.103.42.100:http server first by the URI check in the iRule, but aren't sent a persistence cookie by LTM. Then when they make a request which is load balanced, they end up being sent to the 10.103.42.101:http server where they don't have a session.

 

 

Does either option sound possible?

 

 

I'd suggest opening a case with F5 Support on this to find out why LTM doesn't set a persistence cookie when using the pool command to specify a pool member.

 

 

As a workaround, you can manually insert a persistence cookie from the iRule using the method described in the post I linked to:

 

 

http://devcentral.f5.com/Default.aspx?tabid=53&forumid=5&tpage=1&view=topic&postid=1166691

 

 

Aaron