Problem with stickiness in CSS

ps_support · ‎11-21-2007

Hi,

I'm trying to configure a stickiness for wireless clients ( mobile phones) that accessing our sites through WAP gateway.

After doing some manual reading and some testing I created the following configuration that still doesn't work:

service server1

ip address 10.10.10.1

port 80

protocol tcp

keepalive port 80

keepalive frequency 10

keepalive uri "/heartbeat"

keepalive type http

active

service server2

ip address 10.10.10.2

port 80

protocol tcp

keepalive port 80

keepalive frequency 10

keepalive uri "/heartbeat"

keepalive type http

active

header-field-group wap

header-field 4 custom "x-up-calling-line-id" contain "34"

content http

vip address 10.10.5.10

port 80

protocol tcp

add service server1

add service server2

active

content wap

url "/*"

protocol tcp

port 80

vip address 10.10.5.10

add service server1

add service server2

advanced-balance wap-msisdn

header-field-rule wap

no persistent

active

theoretically it should check whether x-app-calling-id header contain digits 34 - in case of existence it should perform a sticky connection to the same server all the time ,if not it should go to standard http connection that is load balanced with round robbin

Gilles Dufour · ‎11-21-2007

is the traffic matching the wap rule but not sticking, or is it matching the http rule.

Just want to see what we have to troubleshoot.

Do you have a trace of the client traffic so we can see what it countains.

Thanks.

Gille.s

ps_support · ‎11-21-2007

First of all thanks for the response.

#show rule test-1 test-wap services

The output is :

server1 6,521,242 S-1 Alive 25 HTTP-80:H 0 0

server2 5,494,544 S-1 Alive 18 HTTP-80:H 0 0

so i guess it hits the rule

I also have about 1 million hits on the http rule.

So i guess the rule is being hit but the stickiness is not working correctly.

Are there any specific commands you can recommend to troubleshoot?

Gilles Dufour · ‎11-22-2007

if the problem is stickyness, the problem is that the CSS can't find the MSISDN tag.

This is the only place we look for the client id.

Get a sniffer trace and see if this tag is there.

Gilles.