[j-nsp] M20 PFE/SSB-E problems
Drechsel, Thiago (NSN - BR/Curitiba)
thiago.drechsel at nsn.com
Wed Oct 1 12:48:07 EDT 2008
Hi Jonas, thanks for your prompt answer.
The weird thing is that looks like my memory is OK:
someuser at some-router> show chassis ssb
SSB status:
Slot 0 information:
State Master
Temperature 41 degrees C / 105 degrees F
CPU utilization 10 percent
Interrupt utilization 0 percent
Heap utilization 34 percent
Buffer utilization 51 percent
Total CPU DRAM 64 MB
Internet Processor II Version 1, Foundry IBM, Part
number 9
Start time: 2008-09-15 10:23:24 BRT
Uptime: 10 days, 7 hours, 33 seconds
Slot 1 information:
State Backup
Since you faced this problem in the past, do you know wich commands I
can use in order to be sure if this is lack of memory?
Thank you.
Thiago Drechsel
-----Original Message-----
From: ext Jonas Frey [mailto:jf at probe-networks.de]
Sent: Wednesday, October 01, 2008 12:53 PM
To: Drechsel, Thiago (NSN - BR/Curitiba)
Cc: juniper-nsp at puck.nether.net
Subject: Re: [j-nsp] M20 PFE/SSB-E problems
Hello,
as Nicolaj already pointed out, you are short on memory (heap or sram
but most likely heap) on your SSB. Time to buy some EDO ram or go with a
-E16 (much more expensive). See:
http://juniper.cluepon.net/index.php/Unofficial_hardware_upgrades
Regards,
Jonas
On Wed, 2008-10-01 at 16:41, Drechsel, Thiago (NSN - BR/Curitiba) wrote:
> Hi list.
>
>
>
> We are having the following messages in one M20, when activating BGP
> neighbors:
>
>
>
> <... OUTPUT SUPRESSED ....>
>
>
>
> Sep 15 07:00:59 any-router-name ssb RT: Failed prefix add IPv4:0 -
> 189.57.60.64/29 (no memory)
>
> Sep 15 07:00:59 any-router-name ssb RT: Failed prefix add IPv4:0 -
> 189.57.66.4/30 (no memory)
>
> Sep 15 07:00:59 any-router-name ssb RT: Failed prefix add IPv4:0 -
> 201.91.127.144/29 (no memory)
>
> Sep 15 07:00:59 any-router-name ssb RT: Failed prefix add IPv4:0 -
> 201.91.108.88/30 (no memory)
>
> Sep 15 07:01:04 any-router-name /kernel: RT_PFE: NH IPC op 1 (ADD
> NEXTHOP) failed, err 6 (No Memory)
>
> Sep 15 07:01:04 any-router-name /kernel: RT_PFE: NH details: idx 963
> type 2 ifl 69
>
> Sep 15 07:01:04 any-router-name /kernel: RT_PFE: NH IPC op 32 (ADD
> INDIRECT NEXTHOP) failed, err 5 (Invalid)
>
> Sep 15 07:01:04 any-router-name /kernel: RT_PFE: RT msg op 1 (PREFIX
> ADD) failed, err 5 (Invalid)
>
> Sep 15 07:01:04 any-router-name /kernel: RT_PFE: RT msg op 1 (PREFIX
> ADD) failed, err 5 (Invalid)
>
> Sep 15 07:01:04 any-router-name ssb NH: Indirect nh (262324) with
> unknown target nh (963)
>
> Sep 15 07:01:04 any-router-name ssb RT: Failed prefix add IPv4:0 -
> 189.56.186.70 (unknown nh_id)
>
> Sep 15 07:01:04 any-router-name ssb RT: Failed prefix add IPv4:0 -
> 189.56.186.70, nh 262324, ifidx 0, nhifl 0, flag 0x0, cos 0
>
> Sep 15 07:01:04 any-router-name ssb RT: Failed prefix add IPv4:0 -
> 189.56.186.68/30 (unknown nh_id)
>
> Sep 15 07:01:04 any-router-name ssb RT: Failed prefix add IPv4:0 -
> 189.56.186.68/30, nh 262324, ifidx 0, nhifl 0, flag 0x0, cos 0
>
> Sep 15 07:01:05 any-router-name /kernel: RT_PFE: RT msg op 3 (PREFIX
> CHANGE) failed, err 5 (Invalid)
>
> Sep 15 07:01:05 any-router-name /kernel: RT_PFE: RT msg op 3 (PREFIX
> CHANGE) failed, err 5 (Invalid)
>
> Sep 15 07:01:05 any-router-name /kernel: RT_PFE: NH IPC op 11 (DELETE
> NEXTHOP) failed, err 7 (Doesn't Exist)
>
> Sep 15 07:01:05 any-router-name /kernel: RT_PFE: NH IPC op 11 (DELETE
> NEXTHOP) failed, err 7 (Doesn't Exist)
>
> Sep 15 07:01:05 any-router-name ssb RT: Failed prefix delete IPv4:0 -
> 116.212.104/21 (unknown prefix)
>
> Sep 15 07:01:05 any-router-name ssb RT: Failed prefix delete IPv4:0 -
> 120.50.0/19 (unknown prefix)
>
> Sep 15 07:01:05 any-router-name ssb RT: Failed prefix change IPv4:0 -
> 189.56.186.70, nh 262153, ifidx 0, nhifl 0, flag 0x0, cos 0
>
> Sep 15 07:01:05 any-router-name ssb RT: Failed prefix change IPv4:0 -
> 189.56.186.70 (unknown prefix)
>
> Sep 15 07:01:05 any-router-name ssb RT: Failed prefix change IPv4:0 -
> 189.56.186.68/30, nh 262153, ifidx 0, nhifl 0, flag 0x0, cos 0
>
> Sep 15 07:01:05 any-router-name ssb RT: Failed prefix change IPv4:0 -
> 189.56.186.68/30 (unknown prefix)
>
> Sep 15 07:01:05 any-router-name ssb NH: Failed to find nh (963) for
> deletion
>
> Sep 15 07:01:05 any-router-name ssb NH: Failed to find nh (262324)
for
> deletion
>
> Sep 15 07:01:06 any-router-name /kernel: RT_PFE: NH IPC op 1 (ADD
> NEXTHOP) failed, err 6 (No Memory)
>
> Sep 15 07:01:06 any-router-name /kernel: RT_PFE: NH details: idx 963
> type 2 ifl 69
>
> Sep 15 07:01:06 any-router-name /kernel: RT_PFE: NH IPC op 32 (ADD
> INDIRECT NEXTHOP) failed, err 5 (Invalid)
>
> Sep 15 07:01:06 any-router-name /kernel: RT_PFE: RT msg op 1 (PREFIX
> ADD) failed, err 5 (Invalid)
>
> Sep 15 07:01:06 any-router-name last message repeated 3 times
>
>
>
> <... OUTPUT SUPRESSED ....>
>
>
>
> Off course, many other log messages like these are being generated.
>
>
>
> After researching on the problem, I could check that this issue was
> already observed on the list:
>
>
>
> https://puck.nether.net/pipermail/juniper-nsp/2005-March/003914.html -
> Author: Jonas Frey
>
>
https://puck.nether.net/pipermail/juniper-nsp/2004-November/003245.html
> - Author: Jonas Frey
>
>
>
> Unfortunately, none of the above subjects had a solution....
>
>
>
> Possible causes should be:
>
>
>
> - next hop change can not be completed;
>
> - Lack of memory on the SSB0.
>
>
>
>
>
> Does anybody know what are the real causes of this behavior and the
> solution? Maybe Mr. Jonas Frey?
>
>
>
> Thanks in advance!
>
>
>
>
>
> Thiago Drechsel
>
>
>
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
More information about the juniper-nsp
mailing list