cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
972
Views
0
Helpful
4
Replies

Cookie is not always set by ACE - cookie insert problem

appelappe
Level 1
Level 1

First: I’m truly quite a beginner with all the techniques used in my question, so please bear with my poor use of the terminology and be aware that the answer is probably a very simple one. My position at the moment is a test-developer.

We are using cookie insert as a LB technique behind a reversed proxy (Apache).

     Apache -> ACE -> (Webservers)

The problem is that when running a test-script (using Silk Performer) to load-test the solution, the cookie used for cookie insert is not always set when going through the reversed proxy. In some GET the LB-cookie is set, and that virtual user keeps sending that cookie in subsequent requests. But for other users it is not set. The cookie does later get set for other users, and it also seems as ACE ignores it in most of the cases when it is set.

It seems to a novice like me that several http-gets are looked upon by ACE as one session somehow, and the reading and setting of the LB-cookies is only honourd for the firs of those GETs ignored for subsequent GETs.

If we run our tests directly against ACE it works fine! Even if we use the option to run all virtual users from the same IP! The cookie for LB is always set and is used properly.

What could possible be the problem? The guys running the reversed proxy denies to have anything to do with it since they are using only the simplest form of configuration and are just forwarding the connections.

I know I’m giving you far too few details, and the reason is of cause that I don’t know them. J But perhaps you can point me in some directions anyway?

1 Accepted Solution

Accepted Solutions

pablo.nxh
Level 3
Level 3

Hi Andreas,

Do you have an ACE module or ACE 4710?

Do you have "persistence rebalance" enabled for the VIP in question?

Common problem with connections performed behind a proxy is that they tend to perform TCP optimization which causes cookie-persistence to fail.

ACE doesn't do L7 LB for multiple request in the same TCP connection; it does it just for the first request so after the first cookie is inspected the ACE assumes all other cookies are from the same connection.

HTH

__ __

Pablo

View solution in original post

4 Replies 4

pablo.nxh
Level 3
Level 3

Hi Andreas,

Do you have an ACE module or ACE 4710?

Do you have "persistence rebalance" enabled for the VIP in question?

Common problem with connections performed behind a proxy is that they tend to perform TCP optimization which causes cookie-persistence to fail.

ACE doesn't do L7 LB for multiple request in the same TCP connection; it does it just for the first request so after the first cookie is inspected the ACE assumes all other cookies are from the same connection.

HTH

__ __

Pablo

Thank you Pablo for your reply, it was really helpful! What you say really makes sense.

I'm not sure what type of Ace we are using, if I remember correctly they are talking about a module. I'm not at work at the moment but I will find out the correct answer tomorrow.

I guess I'm now leaving the Cisco-area, but does anyone know how to determine for sure that our Apache uses any kind of TCP optimization. I now feel quite sure from what I see in the logs from Silk Performer that we do, but I was told for sure that we don't. I'm not familiar with Apache either. Where would one look for such a setting?

Again, thank you for your reply Pablo!

Our problems indeed disappeared when we turned on "persistence rebalance" (I have now learned that we have an ACE module).

Hi Andreas,

Great to hear that and glad to be of help!

__ __

Pablo

Review Cisco Networking for a $25 gift card