Probe question on ACE

[kirit_patel]

I have a serverfarm with four rservers defined with port 80,8080,8009. Each rserver is defined with a probe for each individual probes like TCP_80, TCP_8080 and TCP_8009

Out of these three ports only port 80 is listening. Other ports are down

When I do show serverfarm it says probe failed. why? I know 2 ports are down but port 80 is listening

[followurself]

Thanks

more to add

actually all these ports will be listen by a http server. so with your config i have replaced the probe type to be http

The config you attached has a class map to match the vip address with a policy map type loadbalance and have a action with server farm. how do i also get stickyness applied. within the policy -map only one action is allowed

so when a request on port 8111, it should be loadbalanced and translated to port 9111. and stickyness applied. with any other ports probing 9010, 9112 failure the server should be removed from the requests being sent.

will appreciate your comments

Thanks

[Frederick Reimer]

For sticky, just create a sticky serverfarm and reference your existing serverfarm, then change your loadbalance policy to refer to your sticky serverfarm instead of your existing serverfarm. You could try reading the manuals...

[followurself]

load balancing policy can have either sticky command or server farm. so with the config attached where we need a single vip listening for multiple ports and then understand when a request received for a port say 8010 translated to 9010 only and not others. the load balance policy is created for the same. how do i get also sticky group attached in the same policy without affecting the requirements

Thanks

[followurself]

part of the config from the attachment given before

class-map match-all APP-8010

2 match virtual-address 192.168.1.100 tcp eq 8010

policy-map type loadbalance first-match APP-8010-Policy

class class-default

serverfarm SF-PORT-8010

serverfarm host SF-PORT-8010

predictor leastconns

probe TCP9111

probe TCP9010

probe TCP9112

rserver Realserver1 9010

inservice

rserver Realserver2 9010

inservice

rserver Realserver3 9010

inservice

policy-map multi-match VIPS

class APP-8010

loadbalance vip inservice

loadbalance policy APP-8010-Policy

loadbalance vip icmp-reply active

how do i also get stickyness for http cookie in

Thanks

[Syed Iftekhar Ahmed]

Just for an example if you want to stick you sessions based on "JSESSION" cookie then the above config will change to

serverfarm host SF-PORT-8010

predictor leastconns

probe TCP9111

probe TCP9010

probe TCP9112

rserver Realserver1 9010

inservice

rserver Realserver2 9010

inservice

rserver Realserver3 9010

inservice

sticky http-cookie JSESSIONID APP-8010-STICKY

cookie offset 53 length 10

timeout 120

replicate sticky

serverfarm SF-PORT-8010

class-map match-all APP-8010

2 match virtual-address 192.168.1.100 tcp eq 8010

policy-map type loadbalance first-match APP-8010-Policy

class class-default

sticky-serverfarm APP-8010-STICKY

policy-map multi-match VIPS

class APP-8010

loadbalance vip inservice

loadbalance policy APP-8010-Policy

loadbalance vip icmp-reply active

Syed

[Frederick Reimer]

You can read the "Cisco Application Control Engine Module Server Load-Balancing Configuration Guide" Chapter 5 - "Configuring Stickiness" to start. There is a section there on the Overview of Stickiness, Configuration Requirements and Considerations, and a specific section on Configuring HTTP-Cookie Stickiness. Finally, there are sections on Configuring an SLB Traffic Policy for Stickiness, Displaying Sticky Configurations and Statistics, Clearing Sticky Statistics, and actual Example of a Stick Configuration.

If you have a specific question, by all means ask, but a general "how do I configure stickiness" is well answered by the manuals.