[afnog] Need help on Disaster Recovery Site Setup

[Mark Tinka]

On Thursday, October 06, 2011 04:15:37 PM Bernard Wanyama 
wrote:

> - routing protocols to use?

Any decent link-state routing protocol will do. OSPF and IS-
IS tend to be typical.

For the l2vpn setup itself, LDP and RSVP are common, as is 
BGP if you're Juniper-inclined.

We find LDP simple, and just use that.

> - keepalive and hold timer values?

For the IGP? Well, I'm more of an IS-IS guy; there are some 
knobs that we've used to tweak the performance of IS-IS, 
both from a stability and convergence point of view.

I gave a talk on a multi-vendor, dual-stack deployment of 
IS-IS back in Manila in 2009 at that year's APRICOT event. 
You may take a look here if you're interested:

http://www.apricot.net/apricot2009/images/lecture_files/isis_deployment.pdf

> - any other important aspects

Typical l2vpn services require MPLS. Think about whether you 
can afford to deploy it. l2tpv3 is another option, but 
you'll quickly find that not many modern high-end routers 
support it.

Of course, if you already have an MPLS network, or use a 
provider that does, then you're half-way there.

> I am actually working on a project where the service
> provider won't go l3vpn for the same reasons you are
> quoting - less than 30 sites with Cisco 1841 at branch
> and Cisco 2821 at two core sites.

If your provider can't support MPLS, and you can't find an 
alternative, then your only option is to use IPSec/VPN's or 
tunnels. Or build your own MPLS network :-).

Cheers,

Mark.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
URL: <http://afnog.org/pipermail/afnog/attachments/20111006/e6b73126/attachment.pgp>