For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

Martin_Renneke_'s avatar
Martin_Renneke_
Icon for Nimbostratus rankNimbostratus
May 24, 2017

LTM has lost sticky persistence after one node went down

Our LTM (Version 10.2.4 - Build 817) Hotfix HF2 and HF7 installed will loose the sticky persistence, after one of the nodes is down. After the node is down the LTM will transfer requests to a wrong n...
application delivery
BIG-IP
LTM
jaikumar_f5's avatar
jaikumar_f5
Icon for Noctilucent rankNoctilucent
May 24, 2017

Persistence logic would vary based on the connection type. If its an active existing connection and the pool member is down, then LB algorithm wouldn't be triggered here. This is where we use the action on service down concept.

 

But if the connection is close, and the following request comes from the same source with the pool member down,then LB algorithm would be applied.

 

Reset your persistence stats and see whats happening. LB algorithm would choose just 1 member, it cannot jump between 7 and 10.