Unless I'm missing something you shouldn't have any issues at all... Here is an MX480 running a pair of RE2000 routing engines.... this includes the full IPv4 and IPv6 bogons list as well:
inet.0: 354429 destinations, 1571796 routes (354275 active, 1 holddown, 5659 hidden) inet6.0: 36578 destinations, 82963 routes (36548 active, 0 holddown, 102 hidden) Not remotely close to any limits that I'm aware of....;) Paul -----Original Message----- From: juniper-nsp-boun...@puck.nether.net [mailto:juniper-nsp-boun...@puck.nether.net] On Behalf Of Michael Hare Sent: Tuesday, February 08, 2011 8:08 PM To: juniper-nsp@puck.nether.net Subject: [j-nsp] juniper / mx series fib usage information? Hello- A quick google didn't help; is there a way to tell how much space you have left in your FIB [absolute RAM, percentage, whatever], specifically for an MX with DPCs? I am contemplating activating cymru fullbogons [v4/v6]. We currently carry about 350,000k v4 and 5000k v6 routes. While initially I'm not worried, my gut tells me the v6 fullbogons feed will not be sustainable as it is already at 30k route for ~5k active v6 announcements. While their template doesn't suggest so, I plan to put in ingress prefix-limit maximum on their sessions to something 'reasonable'. If I activate this, I'm hoping there is a better way to find out than the hard way [frantic syslogs when the FIB is full]. -Michael _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp