[j-nsp] MX-series: SHEAF: possible leak ...

[Nilesh Khambal]

Hi Alex,

Sometimes, these messages also suggest a transient spike in the sheaf memory utilization on the FPC for one of sheaves. It may not be necessarily a memory leak. Sheaf memory is used for sending and receiving the control and data packets between RE and the PFE.

Seeing the SHEAF and NH App messages together in this scenario suggests too many nexthop related operations in the PFE. If those messages started after adding the new customer, you might want to check if this customer is receiving any kind attack traffic. This may also include the traffic for non-existing destinations which are directly connected to this new customer interface. Are there any PFE_NH_RESOLVE_THROTTLED messages seen as well in the logs along with these SHEAF messages?

Is this customer running multicast with IGMP receivers connected to this newly provisioned interface?

Please get the below command outputs from FPC3 and get in touch with JTAC by opening a case. Provide them with these outputs with answers to above queries.

>From FPC3:
++++++++++

 *   show  route summary
 *   show route manager statistics
 *   show nhdb management operations
 *   show packet
 *   show packet statistics
 *   show jtree [0-3] memory extensive composition
 *   show jtree [0-3] memory extensive
 *   show rsmon

Take at least 2-3  snapshots of these commands when these syslog messages are seen.

Thanks,
Nilesh.



On 8/28/09 2:25 AM, "Alexandre Snarskii" <snar at snar.spb.ru> wrote:



Hi!

Since yesterday one of our MX-series routers started logging
next messages:

 fpc3 SHEAF: possible leak, ID 5 (packet(600)) (10563/512/1024)
 Stats bucket for jtree app NH negative..

(both are logged by fpc3, another fpc's not affected), and after some
googling I started worrying, because first message (SHEAF leak) is only
mentioned in j-nsp some years ago in context of PFE memory leak that can
stop your router forwarding (PSN-2004-06-009), and the second is cosmetic
bug closed in PR/400917, concerning PFE memory leak too.

So, the question is: do you think that fpc reload may help with
this issue or i should plan JunOS upgrade in next maintenance
window ? (now this router running JunOS 8.4R4.2 that is EOE/EOL
anyway).

PS: messages starter right after provisioning another client's
interface, nothing special:

cvs diff -u -D '2009-08-27 13:00' -D '2009-08-27 14:00' rt077-201
[...]
+        unit 2103 {
+            description <censored>
+            vlan-id 2103;
+            family inet {
+                mtu 1500;
+                policer {
+                    input 512Kbit;
+                    output 512Kbit;
+                }
+                address <censored>;
+            }
+        }

_______________________________________________
juniper-nsp mailing list juniper-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp