Forum Discussion

juan_47813's avatar
juan_47813
Icon for Nimbostratus rankNimbostratus
Dec 30, 2009

Persistence Across Pools/Services

Hello!!

 

First of all, sorry for my English...

 

I've got to configure a F5 LTM v9.4.8 for a customer. The idea is to create an only virtual server with HTTPS service. Depending on the URI, the requests will be redirected to two pools, JBOSS one (port 8080) and Apache one (port 80). The nodes' IP's are the same for both pools, but the members obviously aren't. For this, I'll use ProxyPass iRule. I've used it before in another customer and it works fine.

 

My question is about persistence. I think the best option here is source address persistence, but I'd like that the persistence works between both port's, that is, if client A does a request to an Apache content, and after that, it links a page of JBOSS service, this second request stays in the same node. Will it work using Match Across Services option?

 

I've read through the post and I've found two contradictory statements:

 

 

1.

 

Match Across Services

 

The Match Across Services option is used in the following two configurations:

 

* Configurations that have multiple virtual servers with the same IP address but have different services specified

 

* Configurations that have pool members sharing the same address but have different services specified

 

 

According to this, it'd work. But I found this in another forum:

 

 

 

2.

 

You can only persist across virtuals/services if the pool members are the same in both cases (IP+port must match). Otherwise the system cannot find the "same" pool member in each pool.

 

 

 

Which one is the correct statement in my case?

 

 

Thank you very much.

 

6 Replies

  • In my opinion it would be item 1 because that is exactly how it's behaving in one instance in my environment.

     

     

    Bhattman
  • I used to think both statements are correct, but they're not referring to the exact same configuration options. For match across services, LTM ignores the service (port) of the pool member. So the IP address of the two pools must be the same, but the ports can be different.

     

     

    For match across virtuals (without match across services enabled), the IP and port of each pool member must be the same.

     

     

    Here are the relevant links, by the way:

     

     

    F5 and RTCP

     

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

     

     

    SOL5837: Match Across options for session persistence

     

    https://support.f5.com/kb/en-us/solutions/public/5000/800/sol5837.html

     

     

    Aaron
  • juan's avatar
    juan
    Icon for Nimbostratus rankNimbostratus
    Thank you very much for your replies. Aaron, could you paste the text of SOL5837: Match Across options for session persistence? I haven't got an account yet.

     

    Thanks.
  • Hi Juan,

     

     

    Whether you have a support contract or not, you can sign up for a free AskF5 account here:

     

     

    https://login.f5.com/resource/registerEmail.jsp

     

     

    And if you want a temporary login, you can check bugmenot.com for some accounts.

     

     

    Aaron
  • juan's avatar
    juan
    Icon for Nimbostratus rankNimbostratus
    Hi Aaron.

     

    I'll sign up right now, thank you.

     

  • Juan: Not to take the original question off track, but are you sure you need to use proxy pass? It seems to me like you may be able to use a basic setup with HTTP classes to do URI switching. Proxypass is an awesome rule, but if you can use normal Profiles to accomplish your task, I say use them...

     

     

    I may be missing something though.

     

     

    -Matt