Forum Discussion

jay_41157's avatar
jay_41157
Icon for Nimbostratus rankNimbostratus
Feb 27, 2009

persistence at GTM

Hi,

 

 

I have a question regarding persistence at the GTM level.

 

 

I am currently using static persist at the LB algorithm and had modified the option to use a /16 CIDR, since we had users that were jumping across sites, as they were accessing the site from multiple DNS servers on different networks.

 

 

So the question / problem is: i want to use a different LB algorithm and not static persist... but need persistence based on a /16 network for the LDNS...

 

 

any thoughts? have others run into this problem?

 

 

Thanks,

7 Replies

  • Take a look here:

     

     

    http://devcentral.f5.com/Default.aspx?tabid=63&articleType=ArticleView&articleId=243 Click here
  • HI,

     

     

    Thanks for the response... from what I understood with the irule example you have ... I would have to know the client LDNS ranges? to set persistence? or am I missing something?

     

     

     

    Thanks,

     

     

    rule "SelectivePersist-rule" {

     

    when DNS_REQUEST {

     

    if { [IP::addr [IP::client_addr]/16 equals "10.1.0.0"] \

     

    or [IP::addr [IP::client_addr]/16 equals "10.2.0.0"] } {

     

    cname "myService-noPersist.gtm.test.com"

     

    }

     

    }

     

    }
  • Thanks,

     

     

    I think i get the idea but am having trouble completely understanding it.

     

     

    here is what I am trying to do...

     

     

    I need all the user request's to persist based on LDNS/16; Do you mind elaborating on your idea from above based on what I am trying to achieve.

     

     

    Thanks,
  • Ah, okay, I think I understand what you're asking now. You want any LDNS server within the CIDR block of the first LDNS request from that range to persist to the same target, yes? The persist command is not yet in the GTM feature set, so static persist with the CIDR notation is your best bet. You could layer your algorithms and choose an alternative method at the wideIP level by using multiple pools, then use static persist at the pool level, placing only one (or more if necessary) virtual server per pool so that after the pool selection is completed with your alternative algorithm at the wideIP level, the pool algorithm will ensure future request from that /16 are persisted appropriately.
  • Thanks, thats what i was trying to do, sorry for not explaining it better at first.
  • the persist [enable | disable] command is now available in version 10!
  • Hi,

     

     

    Sorry I am missing how that will be of use in the GTM scenario.

     

     

    Thanks,