[j-nsp] Core network design for an ISP
luis at luisbalbinot.com
Thu Mar 24 21:02:58 EDT 2016
A good practice on MX480s would be to keep upstream and downstream ports at
separate MPCs if possible. Depending on your config the standard 256M
RLDRAM from some cards might be an issue in the not so near future. I'm not
sure how much RLDRAM those NG cards have though.
I don't see any advantages of running full tables on a virtual-router,
specially if you have a 64GB RE.
For iBGP consider multiple loopback addresses for different families. I'd
do v4 and v6 (6PE with MPLS) with one family and inet-vpn, l2vpn, etc on
another one. Even with newer REs a full table is taking quite some time to
For IGP keep a flat area, no need to segment.
If starting from scratch, look at BGP-LU. Running an MX core is expensive
in terms of cost per port. You could run a much cheaper MPLS-only core in
the future with 100Gbps interfaces at only a fraction of the cost of what a
bunch of MPC4 cards would cost.
For IXs I'd recommend a separate routing-instance. This will help you avoid
stuff like someone defaulting to you and transit deviations.
On Mar 24, 2016 20:57, "Matthew Crocker" <matthew at corp.crocker.com> wrote:
> 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