CSS Stickyness between different ports and Peoplesoft

Unanswered Question
Jun 12th, 2007
User Badges:

We are attempting to "stick" a user to a specific server. We have three different server that run different services on different ports.

The peoplesoft server initial will go to 80 and then get redirected to port 7402, then 9002, then 8002.

Is it possible to have the CSS configured to be able to do the following:


User hits portal.domain.com (port 80)

This will direct this to one of three servers and stick them there using sticky-srcip

Then have the user redirected to port 7402 on the same server that they hit when accessing the content rule for port 80

After that, it needs to be able to still stay on the same server to port 9002

Then another call to 8002 again, to the same server.


Currently I have 4 content rules for each port. However, when calling the alias that points to the VIP (same VIP for all 4 rules, different port for each)

When I try to use sticky and the server sends a URL back to the client browser, they are returned the same alias:PORT and it then gets rebalanced and stuck to one of the three services. Is it possible for the client to remain stuck to the same server and just use the different port.


Here are my current content rules:



content virtual-pshr-eps-ssl

add service easpw1-eps-ssl

add service easpw2-eps-ssl

add service easpw3-eps-ssl

protocol tcp

port 9002

url "/*"

vip address 192.168.8.27

advanced-balance sticky-srcip

application ssl

active

content virtual-pshr-epsproxy-http

add service easpw1-epsproxy-http

add service easpw2-epsproxy-http

add service easpw3-epsproxy-http

protocol tcp

port 80

url "/*"

vip address 192.168.8.27

advanced-balance sticky-srcip

active

content virtual-pshr-epsproxy-ssl

add service easpw1-epsproxy-ssl

add service easpw2-epsproxy-ssl

add service easpw3-epsproxy-ssl

protocol tcp

port 7402

url "/*"

vip address 192.168.8.27

advanced-balance sticky-srcip

application ssl

active

content virtual-pshr-hcm-ssl

add service easpw1-hcm-ssl

add service easpw2-hcm-ssl

add service easpw3-hcm-ssl

protocol tcp

port 8002

url "/*"

vip address 192.168.8.27

advanced-balance sticky-srcip

application ssl

active



  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Syed Iftekhar Ahmed Wed, 06/13/2007 - 01:53
User Badges:
  • Blue, 1500 points or more

you have two options


Option 1:


Instead of using Layer 4 content rules, use a single Layer3 rule with "advanced-balance sticky-srcip".


Option 2:

Configure the servers in all content rules in the same order and use "balance srcip".


if the servers are not steady then with each state change the hash is recalculated which may cause clients to end up at a different server.


Syed


Actions

This Discussion