[c-nsp] Cisco CSS 11501 Load Balancer - Load Balancing on a sorry service
Richard Thomas
Richard.Thomas at the-logic-group.com
Tue Jan 31 10:11:37 EST 2012
Hi David,
Thanks for getting back to me so quickly.
I had seen the secondarySorryServer config when first looking into this.
I really want load balanced 'Sorry' service, instead of fail to first 'Sorry' service and if that's also down, fail to secondary 'Sorry' service.
Thanks for the idea though :)
Richard.
The Logic Group Enterprises Limited. Logic House, Waterfront Business Park, Fleet Road, Fleet, Hampshire, GU51 3SB, United Kingdom. Registered in England. Registered No. 2609323
The information in this email and any attachments are confidential and may be legally privileged and protected by law. It is for the intended recipient only. If you are not the intended recipient you may not use, disclose, copy, distribute, print or rely on the content of this email or its attachments. If this email has been received by you in error please advise the sender and delete the email from your computer.
-----Original Message-----
From: cisco-nsp-bounces at puck.nether.net [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of David Farrell
Sent: 31 January 2012 14:55
To: cisco-nsp at puck.nether.net
Subject: Re: [c-nsp] Cisco CSS 11501 Load Balancer - Load Balancing on a sorry service
Hi Richard,
If you just want to guarantee the availability of the 'Sorry' service would the secondarySorryServer config line suit requirements? Not true load balancing but at least more than one 'Sorry' server in the loop.
Cheers,
David.
DAVID FARRELL
IP Engineer
Tibus
T: +44 (0)28 9033 1122
F: +44 (0)28 9042 4709
E: dfarrell at tibus.com
W: www.tibus.com
Follow us on Twitter: http://twitter.com/tibus
Tibus is a trading name of The Internet Business Ltd, a company limited by share capital and registered in Northern Ireland, NI31235. It is a part of UTV Media Plc.
This e-mail and any attachment may contain confidential and privileged information for the sole use of the intended recipient. Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorised to receive for the recipient), please contact the sender by reply e-mail and delete all copies of this message.
On 31/01/2012 14:39, Richard Thomas wrote:
> Hi,
>
> I'm hoping to get some advice as to if what I'm trying to do is achievable or not and if so, how I go about it.
>
> I would like configure a CSS content, that uses the sorry service principal in an advanced way.
>
> I am familiar with the primarySorryServer command and see that the CSS would send all connections to the named service that is configured as the primarySorryServer.
>
> What I would like to do is to configure the CSS, so that once it's decided it's in a "sorry" state (all the services that are configured with "add service" are down) that it load balances to a different set of services.
>
> To explain what I've been trying to do in the form of configuration on the CSS, I've pasted some pretend config below.
>
> Connections come into IP address 1.1.1.1, which normally get load balanced between 9.1.1.1, 9.1.1.2 and 9.1.1.3.
>
> If 9.1.1.1, 9.1.1.2 and 9.1.1.3 are all down, the sorry service is used and the CSS starts passing traffic to 1.1.2.1, which I want it to load balance between 9.1.2.1, 9.1.2.2 and 9.1.2.3.
>
> The order that I have applied the config, is different to the below, as I set out to configure in this order: secondary services, secondary content, sorry service, primary services, primary content.
>
> The order of the config below is different, because I wanted it in the order that the traffic flows and the CSS won't take the config in that order!
>
> The wall I have ran into, is that when I try to create the service I have named "SorryService", I get the following error:
> %% Service IP Address conflicts with a local I/F, VIP, mgmt route
>
> If anybody has any ideas about how I can tweak my config below to make
> it work or other ways I can achieve what I am trying to do, I would
> be REALLY grateful
>
> Many thanks in advance :)
>
> Richard.
>
>
>
>
> owner Owner
>
> content Primary
> vip address 1.1.1.1
> <snip>
> add service Primary1
> add service Primary2
> add service Primary3
> primarySorryServer SorryService
>
>
>
> service Primary1
> ip address 9.1.1.1
> <snip>
>
> service Primary2
> ip address 9.1.1.2
> <snip>
>
> service Primary3
> ip address 9.1.1.2
> <snip>
>
>
>
> service SorryService
> ip address 1.1.2.1
> <snip>
>
>
>
> owner Owner
>
> content Secondary
> vip address 1.1.2.1
> <snip>
> add service Secondary1
> add service Secondary2
> add service Secondary3
>
>
>
> service Secondary1
> ip address 9.1.2.1
> <snip>
>
> service Secondary2
> ip address 9.1.2.2
> <snip>
>
> service Secondary3
> ip address 9.1.2.2
> <snip>
>
>
>
>
>
>
>
>
> Thanks in advance,
>
> Richard.
>
> Want to acquire and retail new customers across all your channels?
>
> Visit us on our stand 2.1C72 at the Mobile World Congress 2012<http://www.mobileworldcongress.com/> event and get an insight into our mobile offerings.
> Come and see us on ourstand 520 at the Retail Business Technology 2012<http://www.retailbusinesstechnologyexpo.com/Content/Registration/26/> to find out how we can deliver value to you.
>
> Follow us on Twitter<http://twitter.com/thelogicgroup> for all the latest developments at The Logic Group.
> <http://www.the-logic-group.com/>[http://www.the-logic-group.com/CP/Up
> loadedImages/75bd388c-1f27-41f4-8f68-adf034d0b2ea.jpg]<http://www.the-
> logic-group.com/>
>
> The Logic Group Enterprises Limited, Logic House, Waterfront Business
> Park, Fleet Road, Fleet, Hampshire, GU51 3SB, United Kingdom.
> Registered in England. Registered No. 2609323
>
>
> The information in this email and any attachments are confidential and may be legally privileged and protected by law. It is for the intended recipient only. If you are not the intended recipient you may not use, disclose, copy, distribute, print or rely on the content of this email or its attachments. If this email has been received by you in error please advise the sender and delete the email from your system.
>
>
> _______________________________________________
> cisco-nsp mailing list cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
_______________________________________________
cisco-nsp mailing list cisco-nsp at puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
More information about the cisco-nsp
mailing list