From: Luan Nguyen (luan@netcraftsmen.net)
Date: Tue Jan 13 2009 - 16:02:45 ARST
With these designs, you need to take a look at your existing addressing
scheme, your connection profile: like is it going to be one router or 2
routers (one for dmvpn and one for mpls), any downstream router to make the
selection...etc
Summarization, for most of the time, won't be an option at all.
If you look at requirements like if one MPLS site goes down, will you
activate all DMVPN circuits or just for that site? Then you have to make
sure you don't have asymmetric routing going on, internet connection at each
site? At central site?
Lots of things to consider...definitely not a breeze in any account.
Regards,
Luan Nguyen
Chesapeake NetCraftsmen, LLC.
[W] http://www.netcraftsmen.net
[M] luan@netcraftsmen.net
[Blog] http://cnc-networksecurity.blogspot.com/
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Piyoush Sharma
Sent: Tuesday, January 13, 2009 12:38 PM
To: Joseph Brunner
Cc: Cisco certification
Subject: Re: DMVPN question
Another (not zero-touch though) design is, if you use BGP on MPLS, setup
iBGP on your dmvpn and let an IGP like OSPF handle the best path selection.
Dump routes from dmvpn and mpls into the local site's IGP and the mpls would
be preferred, if mpls goes down, the routes from dmvpn would be preferred..
I prefer to summarize all major subnets on the mpls and dmvpn. it limits the
routing table size and if you use correct tags, troubleshooting is a
breeze..
On Tue, Jan 13, 2009 at 8:47 AM, Joseph Brunner
<joe@affirmedsystems.com>wrote:
> We actually like to do longer prefixes known via mpls and less specific
> ones
> know via the dmvpn...
>
> So 10.1.10.0/24 would be learned on mpls while
>
> 10.1.0.0/16 would be learned (as the backup) on dmvpn
>
> -Joe
>
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
> Fake
> Name
> Sent: Tuesday, January 13, 2009 11:00 AM
> To: Cisco certification
> Subject: DMVPN question
>
> If I want to use dmvpn to be a backup for the already existing mpls
network
> where each location has a connection to the internet and mpls connections
> to
> eachother what is the best practice? Would it be configuring dmvpn and
> using the same routing protocol instance between everything and playing
> with
> the metrics to make sure traffic is going over the mpls network and not
the
> dmvpn when its up and when it does down to use the dmvpn backup? Or would
> it be using another routing protocol for the dmvpn network with a higher
> administrative distance so that routes dont go in the table till the mpls
> network is down?
>
> Please offer some advice on best practices?
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
Blogs and organic groups at http://www.ccie.net
This archive was generated by hypermail 2.1.4 : Sun Mar 01 2009 - 09:43:37 ARST