[j-nsp] Core network design for an ISP

Brad Fleming bdflemin at gmail.com
Fri Mar 25 10:52:02 EDT 2016


Might reach out to your Juniper SE.. I believe they have some internal “gold configs” for different sized ISPs that have been well tested internally. One of their configs might make a good base to start from.


> On Mar 24, 2016, at 6:57 PM, Matthew Crocker <matthew at corp.crocker.com> wrote:
> 
> 
> 
> Hello,
> 
> 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
> 
> Thanks
> 
> -Matt



More information about the juniper-nsp mailing list