[177149] in North American Network Operators' Group
Re: MPLS VPN design - RR in forwarding path?
daemon@ATHENA.MIT.EDU (Andriy Bilous)
Fri Jan 2 05:16:35 2015
X-Original-To: nanog@nanog.org
In-Reply-To: <54A3E72F.20801@marcinkurek.com>
Date: Fri, 2 Jan 2015 11:16:26 +0100
From: Andriy Bilous <andriy.bilous@gmail.com>
To: Marcin Kurek <notify@marcinkurek.com>
Cc: nanog@nanog.org
Errors-To: nanog-bounces@nanog.org
Given that you assign unique RD per PE, RR out of the forwarding path
provides you with a neat trick for fast convergence (and debugging
purposes) when CE has redundant paths to different PEs. Routes to those CEs
will be seen as different routes on RR.
On Wed, Dec 31, 2014 at 1:08 PM, Marcin Kurek <notify@marcinkurek.com>
wrote:
> Hi everyone,
>
> I'm reading Randy's Zhang BGP Design and Implementation and I found
> following guidelines about designing RR-based MPLS VPN architecture:
> - Partition RRs
> - Move RRs out of the forwarding path
> - Use a high-end processor with maximum memory
> - Use peer groups
> - Tune RR routers for improved performance.
>
> Since the book is a bit outdated (2004) I'm curious if these rules still
> apply to modern SP networks.
> What would be the reasoning behind keeping RRs out of the forwarding path?
> Is it only a matter of performance and stability?
>
> Thanks,
> Marcin
>
