This article explains the meaning of the "LUCHIP(1) RMC 2 Correctable ECC @ 0x5200e9, cnt 1, syn 0x0 - EDMEM[0x14803bb]" syslog message that may be observed on MX480 Routers or other MX series routers and describes the action that can be taken to clear it.
You will see below alarm
Below, logs will be seen
Mar 13 13:06:28 Router : %PFE-3: fpc2 LUCHIP(1) RMC 2 Correctable ECC @ 0x5200e9, cnt 1, syn 0x0 - EDMEM[0x14803bb] Mar 13 13:06:29 Router : %PFE-3: fpc2 LUCHIP(1) RMC 2 Correctable ECC @ 0x5200e9, cnt 1, syn 0x0 - EDMEM[0x14803bb] Mar 13 13:06:29 Router chassisd[8642]: %DAEMON-3-CHASSISD_FPC_ASIC_ERROR: <FPC 2> ASIC Error detected errorno 0x00040018 (null) Mar 13 13:06:29 Router alarmd[8782]: %DAEMON-4: Alarm set: FPC id=167772776, color=YELLOW, class=CHASSIS, reason=FPC 2 Minor Errors Mar 13 13:06:29 Router craftd[8646]: %DAEMON-4: Minor alarm set, FPC 2 Minor Errors Mar 13 13:06:30 Router rpd[8739]: %DAEMON-3: bgp_recv: read from peer 196.60.9.204 (External AS 327926) failed: Unknown error: -10064 Mar 13 13:06:30 Router : %PFE-3: fpc2 Cmerror Op Set: LUCHIP(5): LUCHIP(1) RMC 2 Correctable ECC @ 0x5200e9, cnt 1, syn 0x0 - EDMEM[0x14803bb] (URI: /fpc/2/pfe/0/cm/0/LUCHIP(5)/1/LKUP_ASIC_SINGLE_BIT_ECC) Mar 13 13:06:31 Router : %PFE-3: fpc2 LUCHIP(1) RMC 2 Correctable ECC @ 0x5200e9, cnt 1, syn 0x0 - EDMEM[0x14803bb]
The "LKUP_ASIC_SINGLE_BIT_ECC errors on LUCHIP(x) - Single-bit ECC" error is caused by a transient hardware memory error. "ECC" stands for Error Checking and Correction, which permits error detection as well as correction of specific errors. On-chip memory is ECC-protected and can detect single-bit or double-bit errors. When a single-bit ECC is detected, an alarm is raised with a level minor and can be cleared via the Command Line Interface. ++++++++ Below is the procedure to follow for recovery ++++++++ 1. Please go through the below logs for investigation
RSI and /var/log request pfe execute command "show nvram" target fpc0 request pfe execute command "show syslog messages" target fpc0 request pfe execute command "show syslog messages" target fpc0 request pfe execute command "show nvram" target fpc0 request pfe execute command "show cmerror module brief" target fpc0
2. If alarm is still active on the router then use command "clear chassis fpc errors fpc-slot 2 all" to clear the alarm.
Router> clear chassis fpc errors fpc-slot 2 all Clearing error(s) on fpc 2, option all
{master}Router> show chassis alarms No alarms currently activeMar 14 00:24:57 Router : %PFE-3: fpc2 Cmerror Op Clear All: LUCHIP(5): cleared by junos CLI. (URI: /fpc/2/pfe/0/cm/0/LUCHIP(5)/1/LKUP_ASIC_SINGLE_BIT_ECC)[Mar 14 00:24:56.688 LOG: Debug] Cmerror: Draining ASIC error message queue[Mar 14 00:24:56.688 LOG: Debug] cmerror_process_queue: module = LUCHIP(5)[Mar 14 00:24:56.688 LOG: Debug] Cmerror: processing the task op_type 6 for scope 1 and category 0 level 0 level_count 5 occur_count 5 clear_count 0 level_threshold 1 level_action 0x5 item errid 262168 item_threshold 1 item_count 5 item_sub_err_state 0 sub_item errid 0 sub_i[Mar 14 00:24:56.688 LOG: Debug] Cmerror: Level 0 count decrement 0 occur_count 5 clear_count 5[Mar 14 00:24:56.688 LOG: Debug] alarm count for level 0 is decrmented and set to 0[Mar 14 00:24:56.688 LOG: Debug] Cmerror: Level 0 count 0 (occur_count 5, clear_count 5)dropped below threshold 1 clear_action 0x8[Mar 14 00:24:56.688 LOG: Notice] Performing action clear-cmalarm for error /fpc/2/pfe/0/cm/0/LUCHIP(5)/1/LKUP_ASIC_SINGLE_BIT_ECC (0x40018) in module: LUCHIP(5) with scope: pfe category: functional level: minor[Mar 14 00:24:56.688 LOG: Debug] cmerror_take_action_helper: performing action 8 for scope 1 category 0 level 0 err_id /fpc/2/pfe/0/cm/0/LUCHIP(5)/1/LKUP_ASIC_SINGLE_BIT_ECC(0x40018) module id 13[Mar 14 00:24:56.688 LOG: Err] Cmerror Op Clear All: LUCHIP(5): cleared by junos CLI. (URI: /fpc/2/pfe/0/cm/0/LUCHIP(5)/1/LKUP_ASIC_SINGLE_BIT_ECC)
2. If clearing alarm does not help then you should ask for reseating of FPC. 3. FPC shell logs we can see LUCHIP error occured 5 times and cleared 5 times. Last LUCHIP error was seen 77876475 miliseconds ago which after conversion to hours show 21.63 hours which is matching the last LUCHIP error time "Mar 13 14:01:09 "
Router> request pfe execute command "show cmerror module" target fpc2 | no-more Module-id Name Error-id PFE Level Threshold Count Occurred Cleared Last-occurred(ms ago) Name ----------------------------------------------------------------------------------------------------------- 13 LUCHIP(5) 0x040040 1 Major 1 0 0 0 0 LKUP_ASIC_HSL2_MAJOR_CRC_ERROR 0x040048 1 Fatal 1 0 0 0 0 LKUP_ASIC_HSL2_FATAL_CRC_ERROR 0x040018 1 Minor 1 0 5 5 77876475 LKUP_ASIC_SINGLE_BIT_ECC ------------------------------------------------------------------------- Module Name Active Errors PFE Callback ModuleData Specific Function ------------------------------------------------------------------------- 13 LUCHIP(5) 0 No 0x00000000 0x4aa498e8
4. If you still see the alarm or problematic logs then go for RMA.