Description

This article explains the "ASIC Error detected errorno 0x00040018 (null) " error that is observed on MX 80 router which leads to crash the MX 80 router

Symptoms

Below logs are observed -

Sep 7 18:33:19 RTR-MX80 chassisd[2088]: CHASSISD_FPC_ASIC_ERROR: ASIC Error detected errorno 0x00040018 (null)
Sep 7 18:33:19 RTR-MX80 alarmd[2346]: Alarm set: FPC id=1744830474, color=YELLOW, class=CHASSIS, reason=FPC 0 Minor Errors
Sep 7 18:33:19 RTR-MX80 craftd[2091]: Minor alarm set, FPC 0 Minor Errors
Sep 7 18:33:19 RTR-MX80 tfeb0 Error: /fpc/0/pfe/0/cm/0/LUCHIP(0)/0/LKUP_ASIC_SINGLE_BIT_ECC (0x40018), scope: pfe, category: functional, severity: minor, module: LUCHIP(0), type: Single-bit ECC error
Sep 7 18:33:19 RTR-MX80 tfeb0 Performing action log for error /fpc/0/pfe/0/cm/0/LUCHIP(0)/0/LKUP_ASIC_SINGLE_BIT_ECC (0x40018) in module: LUCHIP(0) with scope: pfe category: functional level: minor
Sep 7 18:33:20 RTR-MX80 tfeb0 Performing action cmalarm for error /fpc/0/pfe/0/cm/0/LUCHIP(0)/0/LKUP_ASIC_SINGLE_BIT_ECC (0x40018) in module: LUCHIP(0) with scope: pfe category: functional level: minor
Sep 7 18:33:20 RTR-MX80 tfeb0 Cmerror Op Set: LUCHIP(0): LUCHIP(0) RMC 2 Correctable ECC @ 0x20019, cnt 13, syn 0x0 - EDMEM[0x80065] (URI: /fpc/0/pfe/0/cm/0/LUCHIP(0)/0/LKUP_ASIC_SINGLE_BIT_ECC)
 
After sometime we can observe below logs-
 
Sep 7 22:25:36 RTR-MX80 tfeb0 ttrace_single_step(4186): Error reading the NH at 0x00180cc0.
Sep 7 22:25:36 RTR-MX80 tfeb0 LUCHIP(0) PPE_2 Errors sync xtxn error
Sep 7 22:25:36 RTR-MX80 tfeb0 LUCHIP(0) PPE_4 Errors sync xtxn error
Sep 7 22:25:36 RTR-MX80 tfeb0 PPE Sync XTXN Err Trap: Count 3, PC 6203, 0x6203: KT4Way_BTT0_ARS00 0x6203: KT4Way_BTT0_ARS10
Sep 7 22:25:37 RTR-MX80 tfeb0 Error: /fpc/0/pfe/0/cm/0/LUCHIP(0)/0/LKUP_ASIC_DOUBLE_BIT_ECC (0x40020), scope: pfe, category: functional, severity: major, module: LUCHIP(0), type: Double-bit ECC error
Sep 7 22:25:37 RTR-MX80 tfeb0 Performing action get-state for error /fpc/0/pfe/0/cm/0/LUCHIP(0)/0/LKUP_ASIC_DOUBLE_BIT_ECC (0x40020) in module: LUCHIP(0) with scope: pfe category: functional level: major 
Sep 7 22:25:38 RTR-MX80 tfeb0 ttrace_single_step(4186): Error reading the NH at 0x00180cc0.
Sep 7 22:25:38 RTR-MX80 tfeb0 LUCHIP(0) PPE_2 Errors sync xtxn error
Sep 7 22:25:38 RTR-MX80 tfeb0 LUCHIP(0) PPE_6 Errors sync xtxn error
Sep 7 22:25:38 RTR-MX80 tfeb0 LUCHIP(0) PPE_10 Errors sync xtxn error 
Sep 7 22:25:38 RTR-MX80 tfeb0 PPE Sync XTXN Err Trap: Count 6, PC 6203, 0x6203: KT4Way_BTT0_ARS00 0x6203: KT4Way_BTT0_ARS10
 

A single-bit ECC error occurs when the hardware detects and corrects a 1-bit memory error on the LUCHIP ASIC.

While correctable, frequent or persistent ECC errors may point to:

  • Faulty TFEB memory component.
  • Midplane hardware issue.
  • Transient error conditions (e.g., power/thermal events)

 

Solution

We can follow the below troubleshooting steps as a possible solution

  1. Reboot the device in a controlled maintenance window and monitor for recurrence.
  2. If the error persists, restart the affected TFEB to clear memory and reset error counters.
  3. If the issue still continues after a TFEB restart, an RMA for the midplane is recommended.

 

Modification History

2025-09-14 : Article Created