[190310] in North American Network Operators' Group
Re: 1GE L3 aggregation
daemon@ATHENA.MIT.EDU (Mark Tinka)
Thu Jun 23 02:17:41 2016
X-Original-To: nanog@nanog.org
To: Owen DeLong <owen@delong.com>, David Charlebois <dcharlebois@gmail.com>
From: Mark Tinka <mark.tinka@seacom.mu>
Date: Thu, 23 Jun 2016 08:17:31 +0200
In-Reply-To: <536F8E9D-7E3B-429F-8FD1-2D9F66299E54@delong.com>
Cc: nanog@nanog.org
Errors-To: nanog-bounces@nanog.org
On 23/Jun/16 08:07, Owen DeLong wrote:
> If it’s 100% for redundancy, why not just ECMP defaults and not take a full table?
Well, firstly, ring length may be different on either end. So you can't
always guarantee ECMP of traffic to/from the device (without much
difficulty such as MPLS-TE).
You also can't do hop-by-hop routing based on 0/0 or ::/0 when the ring
contains multiple devices also doing the same thing. You'll just create
a loop. MPLS-based forwarding is your friend here.
But yes, if your device is not in a ring, then your suggestion is fine.
Mark.
