Re: [j-nsp] juniper / mx series fib usage information?
On Tue, Feb 08, 2011 at 07:08:21PM -0600, Michael Hare wrote: > 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? ras@re1.router> start shell pfe network fpc0 ADPC platform (1200Mhz MPC 8548 processor, 1024MB memory, 512KB flash) ADPC0(re1.router vty)# sh jtree 0 memory Jtree memory segment 0 (Context: 0x4430cfd0) --- Memory Statistics: 16777216 bytes total 6366560 bytes used 10407144 bytes available (6060032 bytes from free pages) <--- 3024 bytes wasted 488 bytes unusable 32768 pages total 11529 pages used (2568 pages used in page alloc) 9403 pages partially used 11836 pages free (max contiguous = 11285) You can also see a breakdown of the individual services like so, but the output above will take multiple tables into account and show you the true utilization on the rldram. In a default configuration, segment 0 is your routing memory, segment 1 is your firewall filters. ADPC0(re1.router vty)# sh jtree 0 summary Protocol Routes Bytes Used - -- -- IPv4 341307 4906680 IPv64579 84256 MPLS 4876792 Multi-service 1 16 > 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'. Carrying a bogons bgp feed is pretty darn close to worthless really, but you're in no danger of bumping an MX's route capacity unless you're running multiple tables. -- Richard A Steenbergenhttp://www.e-gerbil.net/ras GPG Key ID: 0xF8B12CBC (7535 7F59 8204 ED1F CC1C 53AF 4C41 5ECA F8B1 2CBC) ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] juniper / mx series fib usage information?
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
[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
