CSS11503- Sticky-cookie not working as expected

Unanswered Question
Sep 23rd, 2009
User Badges:

Hi I have a CSS11503 providing load balancing for an application. There are two servers to be load balanced. The CSS5-SSL-C-K9 hardware SSL installed on it.


I have configured the following services and css

service RESWINCOBBTAPP1_HTTP

keepalive uri "/webapps/portal/frameset.jsp"

keepalive port 80

keepalive type http

port 80

ip address 192.168.16.151

string reswincobbtapp1

active

service RESWINCOBBTAPP2_HTTP

keepalive uri "/webapps/portal/frameset.jsp"

keepalive port 80

keepalive type http

port 80

ip address 192.168.16.152

string reswincobbtapp2

active

content HTTP

advanced-balance cookies

port 80

protocol tcp

url "/*"

primarySorryServer SORRY

balance leastconn

vip address 192.168.86.215

string range 1 to 500

string process-length 15

add service RESWINCOBBTAPP1_HTTP

add service RESWINCOBBTAPP2_HTTP

string skip-length 32

string prefix "JSESSIONID="

string match first-service-match

no persistent

active


content HTTPS

add service RESWINCOBBTAPP1_HTTPS

add service RESWINCOBBTAPP2_HTTPS

balance leastconn

application ssl

url "/*"

port 443

protocol tcp

advanced-balance ssl

primarySorryServer SORRY

vip address 192.168.86.215

active



The problem are

1> When clients access the vip address on port 80 the css changes the port to 443. This is a default behavior but I want clients keep the connection on port 80, What do I need to change on CSS ?

2> When one of the server isn't available the client should move to the next available server and If the next server isn't available then client should move to SORRY page but in this case the clients are stuck to one(first) server. When I say the server isn't available that means the web page isn't available and server responds with HTTP error 500.

What do I need to change on CSS to move the client to next available server ?

I have similar configuration working in other part of the organization with some other application.


Thanks in advance

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Gilles Dufour Thu, 09/24/2009 - 01:12
User Badges:
  • Cisco Employee,

1/ this is most probably the server sending a redirect to https....not the css.


2/ if the connection is established with one server and this server then fails, the active connections will stay with that server. Only new connections will be sent to another server assuming the probe detected the server as down.


Gilles.

ravi-mistry Thu, 09/24/2009 - 14:49
User Badges:

Hi Gilles, Thanks for your response.


I will check with the Server guys. On the second point, even the new connections are going to the same server and clients get " The page cannot be displayed" message in IE.


Any Suggestions?

Actions

This Discussion