Hi, On Tue, Sep 16, 2014 at 12:55:40AM -0400, Wes Smith wrote: > I've often wondered how large ISPs handle some basic IGP design issues re > routing between I-BGP nodes in the network.
All routers on the path need to have "full information" (not necessarily
full tables, but they need to agree on the set of routes, possibly including
a default route).
So you'd usually ensure that the "core" of your network is either all
speaking BGP (full mesh or BGP route reflectors), or you have an MPLS
core where you tunnel through the core, and the core doesn't need to
know anything, because MPLS P routers won't look at the IP header.
This is really BGP 101, so you want to get a good BGP book, like the
Halabi "Internet Routing Architectures" book - it's old, but BGP hasn't
changed in that regard (there is a v2 edition which I haven't seen yet,
so maybe all the new BGP stuff is in there already).
gert
--
USENET is *not* the non-clickable part of WWW!
//www.muc.de/~gert/
Gert Doering - Munich, Germany [email protected]
fax: +49-89-35655025 [email protected]
pgpfJxG1OMGOO.pgp
Description: PGP signature
_______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
