[f-nsp] configuring port groups for health checks

[Brent Van Dussen]

We have accomplished this using Track groups in the past.  Group port 80 as 
the primary and 443 as the grouped service.  If port 80 should fail its 
healtcheck, all the rest of the ports that are in the same group will also 
be taken out of service.  Yes it is more for sticky but it does exactly 
what you want in a fairly easy to configure fashion.

"

track

You can configure the SI to send all client requests for a specific set of 
TCP/UDP ports to the same real server as a "primary" TCP/UDP port grouped 
with the other ports. You can group a primary TCP/UDP port with up to four 
additional TCP/UDP ports. After the SI sends a client request for the 
primary port to a real server, subsequent requests from the client for 
ports grouped with the primary port go to the same real server. See 
<http://www.foundrynet.com/services/documentation/sichassis/slb.html#wp105437>"TCP/UDP 
Application Groups" for an example of application grouping.

Note that if any service port is down for a real server, any track ports on 
that real server are not considered for load balancing.
"

http://www.foundrynet.com/services/documentation/sichassis/slb.html#wp105437

That link is for chassis but the config should be the same on the 
stackables.  Give it a shot.

-Brent

At 04:21 PM 8/19/2005, Matt Stockdale wrote:
>I've checked the archives briefly, and I've been staring at the docs for
>a while, but it's friday and my brain is frazzled. I'm hoping someone
>can take pity on me and answer this -
>
>Can I configure a real server to mark all ports as failed if any one of
>them fails? I've been looking at the port groups, but those seem to be
>more for sticky..
>
>(Specifically, the code we are running on one of our old XL's doesn't
>allow us to do in depth health checks on port 443, I want it to fail
>that port if the content-matching on port 80 fails. I'll upgrade if I
>have to, but it will affect many customers, and I'd rather avoid it)
>
>Thanks in advance,
>   Matt
>_______________________________________________
>foundry-nsp mailing list
>foundry-nsp at puck.nether.net
>http://puck.nether.net/mailman/listinfo/foundry-nsp