Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

MSISDN Based sticky problem

Hi,

We need persistency (or sticky load balancing) based on MSISDN and destination ip&port pairs.

My content configuration shown below:

owner WEBLOGIC

content weblogic

add service msisdn-9001-1

add service msisdn-9001-2

add service msisdn-9001-3

add service msisdn-9002-1

add service msisdn-9002-2

add service msisdn-9002-3

url "/*"

advanced-balance wap-msisdn

protocol tcp

port 9003

vip address 10.200.148.15

active

As a service ,there are 3 server (ofcourse 3 IP) But each server has 2 instance (Port 9001 and 9002)

Here is the service configuration:

service msisdn-9001-1

ip address 10.200.148.20

protocol tcp

port 9001

keepalive type tcp

keepalive port 9001

active

service msisdn-9001-2

ip address 10.200.148.21

protocol tcp

port 9001

keepalive type tcp

keepalive port 9001

active

service msisdn-9001-3

ip address 10.200.148.60

protocol tcp

port 9001

keepalive type tcp

keepalive port 9001

active

service msisdn-9002-1

ip address 10.200.148.20

protocol tcp

port 9002

keepalive type tcp

keepalive port 9002

active

service msisdn-9002-2

ip address 10.200.148.21

protocol tcp

port 9002

keepalive type tcp

keepalive port 9002

active

service msisdn-9002-3

protocol tcp

port 9002

keepalive type tcp

keepalive port 9002

ip address 10.200.148.60

active

But I didn't achieve that coming MSISDN go to always same service.

1 REPLY
Silver

Re: MSISDN Based sticky problem

Please confirm that you want to configure stickiness both based on the MSISDN header and the destination ip/port. What you can try to do in this case is set a separate content rules based on the destination port and use the 'advanced-balance wap-msisdn' in conjunction with the content rule based on the destination port.

156
Views
0
Helpful
1
Replies