Aug 21 14:35:19.941 2024 router : %PFE-3: fpc1 XMCHIP(0): XMCHIP(0): PT0: Protect: Log Error 0x4, Log Address 0x0, Multiple Errors 0xc Aug 21 14:35:19.942 2024 router : %SYSLOG-3: re1 Aug 21 14:35:19.942 2024 router other-RE: eventd: sendto Aug 21 14:35:20.372 2024 router : %PFE-5: fpc1 CMError: /fpc/1/pfe/0/cm/0/XMCHIP(0)/0/XMCHIP_CMERROR_PT_MEM_PROTECT_FSET_REG_DETECTED_CPFIFO_PMEM_2 (0x702bd), scope: pfe, category: functional, severity: minor, module: XMCHIP(0), type: PT_PROTECT: Detected: Parity error for CPFIFO data memor Aug 21 14:35:21.092 2024 router : %PFE-5: fpc1 Performing action log for error /fpc/1/pfe/0/cm/0/XMCHIP(0)/0/XMCHIP_CMERROR_PT_MEM_PROTECT_FSET_REG_DETECTED_CPFIFO_PMEM_2 (0x702bd) in module: XMCHIP(0) with scope: pfe category: functional level: minor Aug 21 14:35:21.580 2024 router kernel: %KERN-7: match_inp_rtbl_index:, none criteria match for the connection, returning FALSE, local port =6123, foreign port = 0 Aug 21 14:35:21.580 2024 router last message repeated 3 times Aug 21 14:35:21.584 2024 router : %PFE-5: fpc1 Performing action cmalarm for error /fpc/1/pfe/0/cm/0/XMCHIP(0)/0/XMCHIP_CMERROR_PT_MEM_PROTECT_FSET_REG_DETECTED_CPFIFO_PMEM_2 (0x702bd) in module: XMCHIP(0) with scope: pfe category: functional level: minor Aug 21 14:35:22.081 2024 router : %PFE-3: fpc1 Cmerror Op Set: XMCHIP(0): XMCHIP(0): PT0: Protect: Parity error for CPFIFO data memory 2 (0x3) (URI: /fpc/1/pfe/0/cm/0/XMCHIP(0)/0/XMCHIP_CMERROR_PT_MEM_PROTECT_FSET_REG_DETECTED_CPFIFO_PMEM_2) Aug 21 14:35:22.706 2024 router chassisd[10941]: %DAEMON-3-CHASSISD_FPC_ASIC_ERROR: <FPC 1> ASIC Error detected errorno 0x000702bd (null) Aug 21 14:35:22.706 2024 router alarmd[21440]: %DAEMON-4: Alarm set: FPC id=167772520, color=YELLOW, class=CHASSIS, reason=FPC 1 Minor Errors Aug 21 14:35:22.706 2024 router craftd[10946]: %DAEMON-4: Minor alarm set, FPC 1 Minor Errors
This message is due to a transient hardware memory parity error in the PT0 block on the XMCHIP ASIC. This error is caused by a transient hardware issue. A single occurrence of the message in syslog, not seen in combination with other events, indicates a one-time transient hardware problem. However, multiple continuous occurrences indicate persistent underlying issues.
Perform these steps to determine the cause and resolve the problem (if any). Continue through each step until the problem is resolved.
1) Alarms are cleared after executing command "clear chassis fpc errors fpc-slot <> all"
Please verify that errors are not incrementing after clearing the fpc errors:XMCHIP_CMERROR_PT_MEM_PROTECT_FSET_REG_DETECTED_CPFIFO_PMEM_2 (0x702bd)
start shell pfe network fpc <FPC number>
show cmerror module brief <<<< get the module from here which has active errors
show cmerror module <> error <>
2) FPC should be restarted if errors are incrementing after clearing the fpc errors,
user@mx>request chassis fpc slot <slot number> offline
Wait for a few minutes.
user@mx> request chassis fpc slot <slot number> online
OR
user@mx> request chassis fpc slot <slot number> restart
Further Assistance:
If the issue remains unresolved, please contact Juniper Technical Support for further investigation.