We found log Alarm: %CMRP-3-DDR_SINGLE_BIT_ERROR: R0/0: cmand: Single-bit DRAM ECC error

[jewfcb001]

Hi everyone ,

I found log on ASA 1004  below .

Alarm: %CMRP-3-DDR_SINGLE_BIT_ERROR: R0/0: cmand: Single-bit DRAM ECC error 

I'm not sure this log is bug or hardware issue . Can you advise me ?

Thank you.

[Giuseppe Larosa]

Hello @jewfcb001 ,

if your platform is an ASR 1004 the following thread applies to your case

https://community.cisco.com/t5/routing/cmfp-3-ddr-single-bit-error-f0-cman-fp-single-bit-dram-ecc-error/m-p/2803349

It is in any case an hardware issue and you need to replace with an RMA the affected component likely R0= route processor.

Hope to help

Giuseppe

[jewfcb001]

Thank you for your information

[mgrabovs]

Hello,

SBE (Single Bit Error) is an error related to a parity error.

There are two different types of parity errors:

· “soft" parity error

· “hard" parity error

Soft parity error is a single-time event.
The majority of single-event errors in memory chips are caused by background radiation (such as neutrons from cosmic rays), electromagnetic interference (EMI), or electrostatic discharge (ESD). These events may randomly change the electrical state of one or more memory cells or may interfere with the circuitry used to read and write memory cells.
Known as soft parity errors, these events are typically transient or random and usually occur once.

However, if parity errors reoccur it is considered to be “hard” parity error. If it is “hard" parity error it reoccurs much more frequently.
In this case, the module is considered to be faulty (hardware fault) and it must be replaced depending on the device.

Thank you.

Marin

[jewfcb001]

Thank you for your information

[mkserg84]

Hello,

We had nearly the same issue related to SIP40 module,

%CMCC-3-DDR_SINGLE_BIT_ERROR: SIP1: cmcc: Single-bit DRAM ECC error: mme: 1, sbe: 240, address: 0x0000F3E0, pid: 9778, name: mcpcc-lc-ms

After upgrading from version 15.5 to 16.9 we have started to get the error messages above once per ~30sec.

We solved the issue by removing the SIP module and resiting the DRAM. The problem disappeared so far.

Maybe it is not a solution for everyone but you can still try to solve an issue as we did.

Hope it will help somebody in the future as a remedy.

[Georg Pauwen]

Hello,

thanks for the advice. Reseating the DRAM is usually a very good idea indeed...