[c-nsp] eBGP --> OSPF --> eBGP vs eBGP --> iBGP --> eBGP

Adam Greene maillist at webjogger.net
Sat May 9 08:59:39 EDT 2009

Hi Charles,

Everyone said *not* to inject customer eBGP routes into OSPF and then back 
into eBGP for upstream providers.

In general, it was suggested that the customer-facing BGP router should 
communicate with the Internet-facing BGP routers via iBGP. That way, 
whatever attributes the customer advertises to us can be retained (if 
desired) on the advertisements to our upstream providers.

Something I hadn't expected was that many suggested that OSPF only be used 
to propagate infrastructure routes throughout our backbone, and that iBGP be 
used for all other (i.e. customer) routes. A link describing this best 
practice was offered: 

Hope that helps,


----- Original Message ----- 
From: <Charles at thewybles.com>
To: "Adam Greene" <maillist at webjogger.net>; 
<cisco-nsp-bounces at puck.nether.net>; <cisco-nsp at puck.nether.net>
Sent: Monday, May 04, 2009 4:21 PM
Subject: Re: [c-nsp] eBGP --> OSPF --> eBGP vs eBGP --> iBGP --> eBGP

> Can you post a summary?
> ------Original Message------
> From: Adam Greene
> Sender: cisco-nsp-bounces at puck.nether.net
> To: cisco-nsp at puck.nether.net
> Subject: Re: [c-nsp] eBGP --> OSPF --> eBGP vs eBGP --> iBGP --> eBGP
> Sent: May 4, 2009 6:36 AM
> I never said thanks to all those who responded on and offlist to this 
> thread
> last week. It was very helpful, thanks, and sorry for the delay
> acknowledging your help.
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
> Sent via BlackBerry from T-Mobile

More information about the cisco-nsp mailing list