[j-nsp] Nexthop index allocation failed: regular index space exhausted
Peter Brenner
peter5193 at hotmail.com
Sun Mar 18 12:56:43 EST 2007
Hello,
today the following appeared in the logs of a Juniper M160 running JunOS
7.6R1.10
and hasn't stopped yet.
Mar 18 12:54:47 ham-cr2-re0 /kernel: Nexthop index allocation failed:
regular index space exhausted
Mar 18 12:55:03 ham-cr2-re0 last message repeated 24 times
Mar 18 12:57:03 ham-cr2-re0 last message repeated 116 times
Mar 18 13:00:03 ham-cr2-re0 last message repeated 175 times
The router isn't learning new arp entries and lost about 1000.
Normally around 8500 arp entries are active at any given time.
de-pb at ham-cr2-re0> show arp no-resolve | count
Count: 7630 lines
When I try to ping a directly connected host whose arp entry has been
lost, I get:
de-pb at ham-cr2-re0> show pfe route ip prefix xx.xx.xx.xx
Slot 2
IPv4 Route Table 0, default.0, 0x0:
Destination NH IP Addr Type NH ID Interface
--------------------------------- --------------- -------- ----- ---------
xx.xx.xx.xx xx.xx.xx.xx Unicast 4290 ge-0/1/0.3
de-pb at ham-cr2-re0> ping xx.xx.xx.xx
PING xx.xx.xx.xx (xx.xx.xx.xx): 56 data bytes
ping: sendto: Cannot allocate memory
ping: sendto: Cannot allocate memory
ping: sendto: Cannot allocate memory
ping: sendto: Cannot allocate memory
^C
--- xx.xx.xx.xx ping statistics ---
4 packets transmitted, 0 packets received, 100% packet loss
Any help is appreciated, Thanks in advance,
-- peter
_________________________________________________________________
Don't just search. Find. Check out the new MSN Search!
http://search.msn.click-url.com/go/onm00200636ave/direct/01/
More information about the juniper-nsp
mailing list