On Tue, Dec 30, 2008 at 6:13 PM, Chris Ely wrote:
> Conditional advertisements might be what you're looking for:
>
> http://www.cisco.com/en/US/tech/tk365/technologies_configuration_example09186a0080094309.shtml
I did something just like this recently. Apologies if this is
redundant, but it mig
On Dec 31, 2008, at 11:36 PM, Florian Weimer wrote:
DNS tweaks won't help with that (and to be honest, BGP doesn't
address it, either).
After all, there ought to be an internal line of communication as well
as the external one, and the availability probes can be set up with
logic such t
* Roland Dobbins:
> Have they considered doing GSLB via DNS rather than playing routing
> games? Seems as if it might answer better, be less complex, et. al.
I suspect they want to solve the split brain problem, which would
explain the strong, non-negotiable requirement of traffic flow to only
o
If an IBGP link is possible then you could automate this with the proper
attributes. > Date: Wed, 31 Dec 2008 00:08:32 +> From: nav...@calpop.com>
To: nanog@nanog.org> Subject: Failover solution using BGP> > Hi,> > I would
appreciate insight and experience for the f
On Dec 31, 2008, at 11:59 AM, Naveen Nathan wrote:
Also they didn't want to subnet the space for the failover
location, so it's all or nothing style routing.
Have they considered doing GSLB via DNS rather than playing routing
games? Seems as if it might answer better, be less complex, et
* Naveen Nathan:
> Of the several solutions presented the two that seem to be simple to
> implement and guarantee traffic were conditional route advertisements
> or using more specific routes.
One thing you need to consider is what happens if your AS is split.
In this case, traffic will probably
Thank to everyone that took the time to respond with their ideas.
To those who asked, the client didn't provide details on the application.
However they were insistent that it wasn't possible to have it run in an
active/active configuration, so load balancing at either the application
or BGP level
On Tue, Dec 30, 2008 at 7:08 PM, Naveen Nathan wrote:
> I have a client that would like to announce a /18 & /19 over BGP in
> Sacramento and LA, us being the second location in LA. Our location
> will be a failover location incase Sacramento goes down.
>
> They want failover for extreme cases when
Hi,
Am 31.12.2008 01:19 Uhr, Braun, Mike schrieb:
> Why not just AS prepend your secondary site if the services to the
> Internet are the same at both sites and tied to the same IP addresses?
because that simply does not work (reliably). It would depend on
AS-paths of the same length from every p
, December 30, 2008 5:09 PM
To: nanog@nanog.org
Subject: Failover solution using BGP
Hi,
I would appreciate insight and experience for the following situation.
I have a client that would like to announce a /18 & /19 over BGP in
Sacramento and LA, us being the second location in LA. Our lo
: nanog@nanog.org
Subject: Re: Failover solution using BGP
If the infrastructure is the same in both locations, why not load
balance with stateful failover?
If it's not the same in both locations, what are they doing for
replication and the such in the event a site does go down?
- Chandler
If the infrastructure is the same in both locations, why not load
balance with stateful failover?
If it's not the same in both locations, what are they doing for
replication and the such in the event a site does go down?
- Chandler
On Dec 30, 2008, at 7:08 PM, Naveen Nathan wrote:
Hi,
Conditional advertisements might be what you're looking for:
http://www.cisco.com/en/US/tech/tk365/technologies_configuration_example09186a0080094309.shtml
Regards,
Chris Ely
On Wed, 31 Dec 2008, Naveen Nathan wrote:
Hi,
I would appreciate insight and experience for the following situation.
Hi,
I would appreciate insight and experience for the following situation.
I have a client that would like to announce a /18 & /19 over BGP in
Sacramento and LA, us being the second location in LA. Our location
will be a failover location incase Sacramento goes down.
They want failover for extre
14 matches
Mail list logo