Re: [j-nsp] Stealing from MX firewall jtree space

2009-12-18 Thread Krasimir Avramski
... Regards, Krasi > -Original Message- > From: Richard A Steenbergen [mailto:r...@e-gerbil.net] > Sent: 18.12.2009 9:21 AM > To: Krasimir Avramski > Cc: juniper-nsp@puck.nether.net > Subject: Re: [j-nsp] Stealing from MX firewall jtree space > > On Wed, Dec 16,

Re: [j-nsp] Stealing from MX firewall jtree space

2009-12-17 Thread Richard A Steenbergen
On Wed, Dec 16, 2009 at 11:37:06PM +0200, Krasimir Avramski wrote: > What about terminating bgp neighbor in inet.0 with bgp operating over > a rib-group under family inet: > > protocols bgp > group xy { > neighbor x.x.x.x { > import xy; > family inet { > unicast { >

Re: [j-nsp] Stealing from MX firewall jtree space

2009-12-16 Thread Krasimir Avramski
Hello, route-memory-enhanced introduced in 9.6 What about terminating bgp neighbor in inet.0 with bgp operating over a rib-group under family inet: protocols bgp group xy { neighbor x.x.x.x { import xy; family inet { unicast { rib-group xy;

Re: [j-nsp] Stealing from MX firewall jtree space

2009-12-16 Thread Richard A Steenbergen
On Wed, Dec 16, 2009 at 11:54:33AM -0800, Derick Winkworth wrote: > ## > To allocate more memory for routing tables, include the route-memory-enhanced > statement at the [edit chassis] hierarchy level: > [edit chassis] > route-memory-enhanced; > ## > > You have to restart the FPC o

Re: [j-nsp] Stealing from MX firewall jtree space

2009-12-16 Thread Derick Winkworth
Steenbergen To: juniper-nsp@puck.nether.net Sent: Wed, December 16, 2009 1:26:55 PM Subject: [j-nsp] Stealing from MX firewall jtree space Anybody know the command on MX to steal unused memory from the firewall rldram segment to use it for routing data? I remember reading about this, I just can't rem

[j-nsp] Stealing from MX firewall jtree space

2009-12-16 Thread Richard A Steenbergen
Anybody know the command on MX to steal unused memory from the firewall rldram segment to use it for routing data? I remember reading about this, I just can't remember the actual command. Last night I was trying to fire up a routing-instance and it ran out of fib memory much sooner than I expected,