[168172] in North American Network Operators' Group
Re: best practice for advertising peering fabric routes
daemon@ATHENA.MIT.EDU (Cb B)
Tue Jan 14 21:09:40 2014
In-Reply-To: <1389750938.95176.YahooMailNeo@web181605.mail.ne1.yahoo.com>
Date: Tue, 14 Jan 2014 18:09:27 -0800
From: Cb B <cb.list6@gmail.com>
To: Eric A Louie <elouie@yahoo.com>
Cc: NANOG <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On Jan 14, 2014 6:01 PM, "Eric A Louie" <elouie@yahoo.com> wrote:
>
> I have a connection to a peering fabric and I'm not distributing the
peering fabric routes into my network.
>
> I see three options
> 1. redistribute into my igp (OSPF)
>
> 2. configure ibgp and route them within that infrastructure. All the
default routes go out through the POPs so iBGP would see packets destined
for the peering fabric and route it that-a-way
>
> 3. leave it "as is", and let the outbound traffic go out my upstreams and
the inbound traffic come back through the peering fabric
>
>
> Advantages and disadvantages, pros and cons? Recommendations?
Experiences, good and bad?
>
>
> I have 5 POPs, 2 OSPF areas, and have not brought iBGP up between the
POPs yet. That's another issue completely from a planning perspective.
>
> thanks
> Eric
>
http://tools.ietf.org/html/rfc5963
I like no-export
