Forum Discussion

Tom_51318's avatar
Tom_51318
Icon for Nimbostratus rankNimbostratus
Nov 01, 2012

LTM logging of persistence and load-balancing algorithm results

Hi there,

 

this is my first post to DevCentral, so I hope it's not a stupid question!

 

I have an HTTPS virtual server

 

  • default persistence is cookie insert
  • fallback persistence is source IP

Although I can verify the presence of the LTM-created cookie, in the response to the client browser, I am concerned that there are still source IP persistence records being created in the LTM.

 

Now, I can change the fallback persistence to None, and then no source IP persistence records appear.

 

But I would really like concrete answers as to why these persistence records get created in the first place.

 

My browser

 

  • is accepting the cookies
  • can be stuck to another server, by maniulating the cookie content

This proves to me that the cookie-insert persistence is obeyed.

 

Is/are there (a) logfile(s) that record why the LTM took the action it did.

 

For example:

 

  • received request from client with IP A for virtual server with IP W and port X
  • no persistence cookie found in request
  • no source IP persistence record found where source IP = A
  • virtual server W:X uses least-connection(member) load-balance algorithm to pool Y
  • pool Y member connection counts:
  • pool member D: 100
  • pool member E: 106
  • pool member F: 96
  • client balanced to pool member F with least connections

Cheers,

 

Tom.

 

3 Replies

  • It's not a stupid question. I've always wondered about the fallback persistence operation myself. Anyway, from what I can gather from a few other forum posts is that both types of persistence operate simultaneously, but with the fallback only being used when needed. So, yes you should expect to see records for your fallback persistence method.

     

     

    A few comments also suggest CMP needs to be disabled for the VS but this restriction may have been removed in recent code?
  • nathe's avatar
    nathe
    Icon for Cirrocumulus rankCirrocumulus
    Tom,

     

     

    I can concur with Steve re fallback source address persistence - you will definitely see these entries in the persistence records (so it's there to be used in cases where the default persistence fails for a client).

     

     

    You may find this iRule helpful:

     

     

    https://devcentral.f5.com/wiki/iRules.Persistence_Cookie_Logger.ashx

     

     

    Hope this helps,

     

    N

     

  • ::Steve and Nathan: thank you for your responses.

     

    The application (Blackboard 9.1) I am load-balancing requires the client browser to support cookies, and indeed still works if I set the fallback persistence profile to none.

     

    So, what I would like to know is how to determine why there are client IP persistence records being created, even though my browser is confirmed to be supporting cookies.

     

    Cheers,

     

    Tom.