Juniper ADVANCED INSIGHT SCRIPTS 2.5 - RELEASE NOTES REV 1 Release Note page 21

Table 1: Events Detected by AI-Scripts (continued)
EVENT ID
PFE: I-CHIP New packet errors in WO HDRF,
iwo_hdrf_poll_stats
PFE: imq_stream_disable_stream
PFE: LCHIPnew errors in LSIF
PFE: mrvl_dfw_log_effuse_status:Firewall rows
PFE: Multi-bit ECC error
PFE: Multiple Correctable ECC
PFE: Multiple UnCorrectable ECC
PFE: Packet drop in Ichip
PFE: RCHIP: SRAM parity error
PFE: Route TCAM rows could not be redirected on
device
PFE: RT: Failed prefix change
PFE: SDRAM ECC Error
PFE: SHEAF: possible leak
©
Copyright 2010, Juniper Networks, Inc.
DESCRIPTION
Potential ICHIP stream problem possibly due to IFL flooding. Potential
match with PR/289104—may need software upgrade.
The I-chip wedge issue described in PR 277853, which can lead to packet
corruption or packet loss. The Event trigger contains the string:
imq_stream_disable_stream.
The FPC is reporting LCHIP interface errors.
The TCAM error messages listed indicate a permanent non-fixable error
with TCAM, if they persist after rebooting the EX Switch or Virtual Chassis
(VC). These errors are TCAM hardware issues on this FPC and are not
harmless. ACLs will be unreliable on this FPC.
The Packet Forward Engine detected a multi-bit error correcting code (ECC)
error in one of the forwarding engine boards.
The Packet Forward Engine board is reporting multiple correctable ECC
memory errors.
The Packet Forward Engine board is reporting multiple uncorrectable ECC
memory errors.
The Ichip packet writer drop counter is incrementing, possibly indicating
packet drops which may, but not necessarily, be due to a faulty switching
board.
SRAM parity error detected on FPC RCHIP.
The TCAM error messages listed indicate a permanent non-fixable error
with TCAM, if they persist after rebooting the EX Switch or Virtual Chassis
(VC). These errors are TCAM hardware issues on this FPC and are not
harmless. ACLs will be unreliable on this FPC.
These messages indicate that the Routing Engine is trying to delete routes
from the Packet Forwarding Engine, but it can't because the routes aren't
there. This usually means the Packet Forwarding Engine has run out of
memory. For example, if you bring up many BGP peers, the number of
routes the Routing Engine can hold may surpass the number the Packet
Forwarding Engine can hold. In this case, the Packet Forwarding Engine
runs out of memory and can't add the routes. Later, when the Routing
Engine tries to remove the routes, the prefix it's looking for is unknown.
Any Packet Forwarding Engine SDRAM ECC error that occurs in
conjunction with a system exception message, for example: router-name
fpc0 ADPC: detected 1 DDR SDRAM Single-bit ECC errors in the last 30
seconds.
Possible FPC SHEAF memory leak.
Events Detected by AI-Scripts
21