Forum Discussion

U_franco_117956's avatar
U_franco_117956
Icon for Nimbostratus rankNimbostratus
Jan 22, 2014

LTM tries to persist to pool member down

Hi. We need help to troubleshoot this curious behavior in our ltm guest on Viprion 2400. We are noticing high cpu utilization on ltm guest when web administrators deactivate HTTP service in one of ...
application delivery
devops
iRules
persistence
U_franco_117956's avatar
U_franco_117956
Icon for Nimbostratus rankNimbostratus
Jan 22, 2014

Hi.

 

Thanks a lot for your responses.

 

We can´t ditch the irule because we need it to maintain HTTP-to-HTTPS persistece. Built-in persistence doesn´t implement match across services option, that is the reason we use this irule.

 

Our monitor is not aggresive. It is an HTTP monitor testing in 15 sec. steps

 

Action on service down option is configured with default value none. Perhaps we had to try with Reselect, Am I wrong??

 

Thanks

 

BinaryCanary_19's avatar
BinaryCanary_19
Historic F5 Account
Jan 23, 2014
Correct me if I'm wrong. [thought adventure] Cookie persistence encodes the selected pool member into the cookie value. The client presents this cookie to the server each time it makes a request, the Bigip decodes this and sends the request to the pool member found. Browsers send this cookie whenever they are making a request to a site with the same domain name. https only modifies the scheme, not the domain name. ------- I would be very surprised if cookie persistence needed any "modification" in order to match across services. I think it should, as long as the domain name remains the same. But I'd have to test to know for sure.