CSS persistence different content

Unanswered Question
Apr 15th, 2008

Hi all,

little problem :). I may need to do a silly stuff like this:

clientA --> contentX --> serviceA or B

clientA --> contentY --> serviceA or B

where client is random...internet

contentXipaddressXportX has serviceA_ipaddressAportA and serviceB_ipaddressBportA

contentYipaddressXportY has serviceA_ipaddressAportB and serviceB_ipaddressBportB

so client has to go to first content and balance to one server, then server reply and client open new connection (may be FTP) to second content but balanced server must be the same.

i've no idea at moment...anyone knows?

thk anyway


I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 2.5 (2 ratings)
agiaccone Wed, 04/16/2008 - 01:39

Hi Dan,

try using the command

"advanced-balance sticky-srcip"

in the content, so that the same client will be sticked on the same server for all the time you decide in the "sticky-inact-timeout" command.



danilo.dicesare Wed, 04/16/2008 - 01:55

Hi Alberto,

yes i know the feature...problem is different content and same behaviour...before client have token from one content and then client open a new connection to a new content but must land on same server (different content but same physical services listen on different port)



agiaccone Wed, 04/16/2008 - 02:06

oh sorry, I didn't understand the scenario.

Maybe you could try creating only one content rule without specifying port, so that clients looking for different services on different servers will pass through the same content rule.

In this content apply the sticky-srcip feature.




This Discussion