[177129] in North American Network Operators' Group
Re: MPLS VPN design - RR in forwarding path?
daemon@ATHENA.MIT.EDU (Ca By)
Wed Dec 31 07:15:48 2014
X-Original-To: nanog@nanog.org
In-Reply-To: <54A3E72F.20801@marcinkurek.com>
Date: Wed, 31 Dec 2014 04:15:40 -0800
From: Ca By <cb.list6@gmail.com>
To: Marcin Kurek <notify@marcinkurek.com>
Cc: "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
On Wednesday, December 31, 2014, 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
>
Correct, these ideas are MOSTLY rooted in old school router limitations.
Ymmv. Look for facts in the replies you get, not unsubstantiated opinions.
There is no technical reason to have a bgp rr out of path on a hardware
based forwarding router that has sufficient control plane capacity to run
bgp.
CB
