ACE Loadbalancing with Single Server and 2 different TCP ports

[Spawn]

Hi there,

if anybody has encountered or worked with Cisco ACE 4710 and following scenario:

ACE is configured with one virtual ip, for load balancing of a single server on different unique TCP ports.

Its just like loadbalancing 2 physical servers but only difference being here the ip is common for 2 physical servers, but we are hosting the application on Two TCP ports using Apache on the Application server

We are experiencing Application logout issues as the moment ACE tries load balancing to the 2nd entry of server, clients are logged out.

Topology

Client --------------------------Firewall----------------------ACE----------------------Single Server ( 10.1.1.1)

ACE virtual ip

10.1.1.10- port 80,

default L7 load balancing

10.1.1.1 port 2222- inservice.

10.1.1.1 port 2333- inservice.

[dario.didio]

Hi,

Can you try to configure stickyness, this will force a client to connect to the same server as where he connected on before.

Assign sticky resources to your context, configure a sticky serverfarm and configure that sticky serverfarm in your policy-map.

If that doesn't work, capture the client traffic and see what is happening.

To make sure, at this point your should config looks like this:

rserver server1

ip address 10.1.1.1

inservice

serverfarm farm

rserver server1 2222

  inservice

rserver server1 2333

  inservice

HTH,

Dario

[Spawn]

Thanks dario.....i will try that, will post back on the results.

[Spawn]

Hi Dario,

Sticky configuration did not work, for some reason the ACE 4710 load balancer is still trying to loadbalance the traffic for single session as well. Either the server or the ACE are not retaining the connection state.

sticky http-cookie COOKIETEST
  timeout 1440
  replicate sticky
  serverfarm TESTSERVERFARM
  8 static cookie-value "F0123" rserver TESTSERVER 8001
  16 static cookie-value "F4567" rserver TESTSERVER 8002


Policy-map type loadbalance first-match testtraffic

   class class-default
     sticky-serverfarm COOKIETEST

Client logs in and is  suppose to retain the session for one server on 8001 but some how during  his session, one request lands on the other server at 8002 and  subsequently he is logged out.

[Surya ARBY · Accepted solution]

what about using cookie insertion with the browser-expire parameter enabled ?

[Spawn]

Yes Surya

unfortunately it still trying to establish session with the server on the 8002 port.

Session persisitence is not working with this.

[Spawn]

ok this is clear now.....sticky persistence is acheived.

[Surya ARBY]

how did you solve the issue ?