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

Advanced Insight Scripts (AI-Scripts) 2.5 Release Notes
Table 1: Events Detected by AI-Scripts (continued)
EVENT ID
PFE: SRAM Parity Error
PFE: SRCHIP-SRAM parity error
PFE:%PFE- PIO Read error.
PFE:.*CCHIP: .*abnormal discard seen.*
PFE:.*clock error.*
PFE:.*mrvl_brg_port_stg_cist_init.*
PFE:.*RSMON: Resource Category:jtree
Instance.*less than LWM limit.*
PFE:.SFP receive power low warning
PPMD_ASSERT_SOFT
PPMD_READ_ERROR
problem-event-ichipfcheck
problem-event-jbuserror
problem-event-l2cacheerror
problem-event-lchipcrc
problem-event-nfabcrcerror
RDD_EVLIB_CREATE_FAILURE
22
DESCRIPTION
Any Packet Forwarding Engine SDRAM ECC error that occurs in
conjunction with a system exception message, for example: router-name
ssb CCHIP: %PFE-3: SRAM parity error 0x80000 bank 0x1.
The FPC SRCHIP has detected an SRAM parity error.
The PIO read error could indicate a hardware issue with the PIC.
Packet Forwarding Engine board is reporting CCHIP abnormal discard
errors.
Clock error reported on PFE board.
Initialization Warning message pertaining to MSTP/STP/RSTP configured
ports for any spanning tree groups shared common IST(CIST).
RSMON is reporting critical jtree memory resource shortage.
SFP receive power low warning.
The source code for the periodic package management process (ppmd)
includes internal self-consistency checks. As ppmd with the indicated
process ID (PID) executed the binary compiled from the indicated source
file, a check failed at the indicated line number in the file. ppmd created a
diagnostic core file for analysis by technical support personnel and
continued to run.
The source code for the periodic package management process (ppmd)
includes internal self-consistency checks. As ppmd with the indicated
process ID (PID) executed the binary compiled from the indicated source
file, a check failed at the indicated line number in the file. ppmd created a
diagnostic core file for analysis by technical support personnel and
continued to run.
The FPC is reporting a bad fabric connection to one or more destinations.
Another FPC is likely to be causing the packet corruption.
An error occurred on the FPC control bus used for packet memory
allocation.
The Packet Forwarding Engine component is reporting that Layer 2 Cache
Single-bit ECC errors were detected in the last 30 seconds. If the problem
persists, this situation is likely to result in a component crash or failure.
The outbound FPC is reporting a corrupt packet received on the Nchip-to-
Lchip interface. Another FPC is likely to be causing the packet corruption.
The fabric connection to the ingress FPC is reporting a bad connection.
The redundant interfaces process (rdd) could not create a context used for
handling all asynchronous events (such as timers and message availability).
©
Copyright 2010, Juniper Networks, Inc.