Nicolaj,
I was more trying to understand why the kernel is complaining
of
"Nexthop index allocation failed: regular index space
exhausted"
In this version the regular index space from kernels
perspective is 256k. Before you
Richard A Steenbergen wrote:
Hi Richard,
> Apparently the way some people have solved this is to upgrade the DRAM on
> the SSB (unsupported). The offical way to do it is to get an SSB-E-16 with
> larger SRAM and DRAM. But yeah an M20 just isn't a good platform for an
> edge box like this.
isn
On Mon, Jun 11, 2007 at 01:13:34AM +0200, Niels Bakker wrote:
> * [EMAIL PROTECTED] (Nicolaj Kamensek) [Sat 09 Jun 2007, 20:16 CEST]:
> >today I found the following messages in my /var/log/messages:
> >
> >Jun 9 19:59:53 re0 /kernel: Nexthop index allocation failed: regular
> >index space exhaus
* [EMAIL PROTECTED] (Nicolaj Kamensek) [Sat 09 Jun 2007, 20:16 CEST]:
>today I found the following messages in my /var/log/messages:
>
>Jun 9 19:59:53 re0 /kernel: Nexthop index allocation failed: regular
>index space exhausted
>
>[EMAIL PROTECTED]> show arp no-resolve | count
>Count: 7205 lines
Josef Buchsteiner wrote:
Hi Josef,
> show version
> show system virtual-memory
the output is below. But meanwhile of course I had to fix the problem
and therefore moved some Gateway IPs to a different router to decrease
the arp count from 7200 to 5611 currently. I had to reboot the SSB-E to
f
Nicolaj,
please post
show version
show system virtual-memory
thanks
Josef
Saturday, June 9, 2007, 8:16:01 PM, you wrote:
NK>
NK>
NK> Hello list,
NK>
NK> today I found the following messages in my /var/log/messages:
NK>
NK> Jun 9 19:59:53 re0 /kernel: Nexthop index allocation fa
Hello list,
today I found the following messages in my /var/log/messages:
Jun 9 19:59:53 re0 /kernel: Nexthop index allocation failed: regular
index space exhausted
That messages occures several times. The hardware is a Juniper M20 with
SSB-E and standard FPC. ge-0/0/0 and ge-1/0/0 are membe
7 matches
Mail list logo
