[88750] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: Disaster recovery using as-prepend?

daemon@ATHENA.MIT.EDU (Andy Davidson)
Thu Feb 16 10:04:59 2006

In-Reply-To: <6004a3f50602160656k4cd97047x@mail.gmail.com>
Cc: nanog@merit.edu
From: Andy Davidson <andy@nosignal.org>
Date: Thu, 16 Feb 2006 15:04:32 +0000
To: Christopher J.Pilkington <christopher.j.pilkington@gmail.com>
X-SA-Exim-Mail-From: andy@nosignal.org
Errors-To: owner-nanog@merit.edu



On 16 Feb 2006, at 14:56, Christopher J. Pilkington wrote:

> We have a PI /24 we'd like to advertise out of our primary data center
> for production use.  (Well, actually, we'll be advertising a more
> specific from our /21 assignment, so already not too friendly... but I
> digress.)
[...]
> I'm thinking advertising the same prefix and just doing several
> as-prepends.  However, now I'm not sure if this is a polite thing to
> do or not.

How about advertising all of your PI from all of your perimeter  
routers, and configuring internal routing to ensure packets get to  
the rightful live/preferred data centre.  Then, in the event of a  
failover situation, you can change the routing behaviour so that  
packets for the production /24 end up in the alternative dc.

To work, this does imply you have good connectivity between your live  
and failover environments (but i guess you have this so that you can  
copy over state/live data between your two environments anyway..), so  
that you can carry customer/live data over the link too.

Double plus good for you if you can get cheap transit delivered to  
your failover dc - you could use this for your preferred environment  
too !

cheers
-a


home help back first fref pref prev next nref lref last post