[j-nsp] Core network design for an ISP
raph at futomaki.net
Fri Mar 25 10:37:19 EDT 2016
There are so much debate on how to construct a good network core,
but if you don't need special features, I will stay with something very
- IGP : ISIS (over OSPF because it doesn't relies on IP, more flexible,
more simple) with only loopback
- iBGP full mesh with DMZ in the main table/main vr (vrf provide more
flexibility for a little increased complexity)
- LDP for signaling MPLS (unless you really need FRR, and/or QOS)
as always KISS is a good approach :)
Le 25/03/2016 00:57, Matthew Crocker a écrit :
> What is the current best practice for carrying full tables in MX series routers? I have 3 new MX480s coming soon and will use them to rebuild my core network (currently a mix of MX240 & MX80 routers). MPC-NG (w/ 20x1g & 10x10g MICS )& RE-S-X6-64G-BB.
> I’m running MPLS now and have full tables in the default route instance. Does it make more sense (i.e. more secure core) to run full tables in a separate virtual-router? I’ve been doing this small ISP thing for 20+ years, Cisco before, Juniper now, I’ve always bashed my way through.
> Looking for a book, NANOG presentation or guide on what is current best practice with state of the art gear.
> MPLS? BGP? IS-IS? LDP? etc.
> The network is a triangle (A -> B -> C -> A), MX480 at each POP, 10g connections between POPs, 10g connections to IX & upstreams. Most customers are fed redundantly from A & B
> juniper-nsp mailing list juniper-nsp at puck.nether.net
More information about the juniper-nsp