Does CSS 11500 support stickiness based on source IP and source

fly · ‎10-30-2012

i don't know why cu need this feature, he want stickiness based on source ip and source port.

Does CSS 11500 support stickiness based on source IP and source port?

or is there any other method to support stickness based on source ip and sourceport?

thank you!

Jun Li

Kanwaljeet Singh · ‎10-30-2012

Hi,

What is the requirement or i should say what is it that customer wants to achieve with such an option?

You don't have such option. At L4, you can use stickiness based on src ip and destination port.

Normally, as long as the src ip and src port remains same, the connection is stuck to the same server. When the src port changes the traffic is load balanced.

Regards,

Kanwal

fly · ‎10-31-2012

HI,Kanwal,

i don't know what is that custome wants to achieve, He just ask me can CSS support stickiness based on source ip and source port.

I did a search ,find CSS doesn't support this feature, but i am not sure.

"

Normally, as long as the src ip and src port remains same, the connection is stuck to the same server. When the src port changes the traffic is load balanced.

"

you said when the src port changes, although stickiness based on only src ip address, CSS can loadbalance to different server, is that right?

thank you!

Jun li

Kanwaljeet Singh · ‎10-31-2012

Hi,

There is no option. At L3 you can have src IP based sticky and if that is configured as long as the src IP remains same, the connection would stuck to the same server.

At L4 level you have only option of src ip-dst port based sticky option. And then you have advance balance methods details of which can be found at the link given by Jorge.

Let me know if you have any doubts.

Regards,

Kanwal

Jorge Bejarano · ‎10-30-2012

Hi Jun,

Here you have the options for stickiness for the CSS.

http://www.cisco.com/en/US/docs/app_ntwk_services/data_center_app_services/css11500series/v8.20/configuration/content_lb/guide/Sticky.html#wp1073329

Hope this helps.

Jorge

fly · ‎10-31-2012

Hi Jorge,

I didn't find CSS support stickiness based on src port from this page.

is there any other method can to this?

thank you!

jun li

Jorge Bejarano · ‎10-31-2012

Hi Jun,

Src-port stickiness is not supported currently to my knowledge.

Jorge

fly · ‎10-31-2012

i know, but customer just want stickiness based on src-port, i have no idea. customer ask me to replace css with other vendor product, such as F5, may be using IRULE can do this !

Jorge Bejarano · ‎10-31-2012

Hi Jun,

I do not know the requirements of your customer but those are the options which we currently have with the CSS.

You may discuss with them and provide them with these options then they can analyze if these other options work for them.

Do not hesitate to let us know your feedback then other customers can have these forums as reference as well

Jorge

Martin Kyrc · ‎10-31-2012

currently is not possible stick based on src ip. you can use only src IP, or srcIP+dstPort:

advanced-balance sticky-srcip-dstport - Enables the content rule to stick a

client to a server based on both the client IP address and the server destination

port number, also known as Layer 4 stickiness. You can use this option with

Layer 4 or Layer 5 content rules.

--

martin

shday · ‎02-11-2013

For the sticky-srcip-dstport you say the port is based on the servers destination port. Does this mean its based on the destination port from the response of the server which would make it the source port from the client?

Jorge Bejarano · ‎02-11-2013

Shday,

"advanced-balance sticky-srcip-dstport - Enable the content rule to stick a client to a server based on both the client IP address and the server destination port number, also known as Layer 4 stickiness. You can use this option with Layer 4 or Layer 5 content rules."

Here you have the config guide:

http://www.cisco.com/en/US/docs/app_ntwk_services/data_center_app_services/css11000series/v5.00/configuration/advanced/guide/Sticky.html

Please mark, if this answers your question.

Jorge

shday · ‎02-13-2013

Ok so once the sticky entry is added to the l4 sticky table if you dont configure a sticky-inact-timeout how long does the sticky entry stay in the table? What I'm seeing in my trace is that the connection stay stuck for the duration of the cp session, but when a new connection come into the content rule the connections are being load balanced even though I just had a connection so i should have a sticky entry. The connections come in within 20 seconds of each other from the same source and destination port. When this happens the client is required to log back in. The client isnt loging out or its just the application initiating a new request with a new tcp session.