This article explains why the event message Errors ucode data error might appear in the syslog.
When an Errors ucode data error event occurs, a message similar to the following is reported:
fpc1 LU 2 PPE_14 Errors ucode data error 0x0000010b
This can occur in relation to other messages in the syslog, such as one or more of the following:
fpc1 PPE PPE HW Fault Trap: Count 17680, PC dc, 0x00dc: egress_proc_start 0x00dc: egress_proc_start
fpc1 PPE PPE HW Fault Trap: Count 50086065588, PC 8f, 0x008f: load_stream_entry
chassisd: CHASSISD_FASIC_OUTPUT_DROP: Fchip (CB 2, ID 0): dropped 50 cells per second destined for Packet Forwarding Engine 1 on FPC 2
fpc7 PQ3_IIC(WR): %PFE-3: I/O error (i2c_stat=0xa3, i2c_ctl=0xb0, bus_addr=0x51)
fpc0 LU 2 RD_NACK 2 AP[0x04] TOE Write 0x002d1260
fpc0 LU 2 IDMEM Parity error in Bank 2, Count 20, IDMEM Bank 2 Offset 0x00016897 IDMEM[0x0005a24c].
fpc<x> PPE PPE HW Fault Trap: Count 152192, PC 28, 0x0028: entry_buf_mod_nh
rpd: Cannot perform nh operation ADDANDGET nhop (null) type unilist index 0 errno 2
Transient errors might cause corruption in ASIC code, resulting in hardware fault messages in the syslog. These errors can result from some of the ASIC code on the hardware becoming corrupt. The term “ucode” refers to code driving the hardware, rather than any of the Junos OS code. This is also the reason that a hardware fault is usually (but not always) indicated in the previous log entry. Because this condition is rare and unpredictable, it is impossible to say what exactly caused the corruption.
Perform these steps to determine the cause and resolve the problem (if any). Continue through each step until the problem is resolved.
1.Collect the show command output:
Capture the output to a file (in case you have to open a technical support case). To do this, configure each SSH client/terminal emulator to log your session.
show log messages
show log chassid
start shell pfe network fpc#
show syslog messages
show jnh 2 trap-info
2.Analyze the show command output:
Look for any related events that occurred at or just before the Errors ucode data error message in the syslog output.
During a maintenance window, try the following:
Reboot the FPC using the following command:
request chassis fpc slot <x> restart
Reseat the FPC in its slot.