Description

The "MQSS: FI: Protect: Parity error detected for timer SRAM" message reports a hardware parity error detected in the EACHIP Fabric Input block.

Symptoms

When a "Parity error detected for timer SRAM" event occurs with error code 0x2204b1, a message similar to the following is reported:

 

Aug 29 14:33:33.831 router fpc2 Performing action log for error /fpc/2/pfe/0/cm/0/MQSS(1)/1/MQSS_CMERROR_FI_PAR_PROTECT_FSET_REG_DETECTED_TIMER_SRAM (0x2204b1) in module: MQSS(1) with scope: pfe category: functional level: minor 

Aug 29 14:33:33.831 router fpc2 Cmerror Op Set: MQSS(1): MQSS(1): FI: Protect: Parity error detected for timer SRAM - data32_log_err 0x1, data32_log_address 0x30  

 

Indications:

 

  • Single occurrence of syslog and not seen with other events, indicates one time transient hardware error with no operational impact. - No Action is needed
  • Multiple continuous occurrences indicate persistent underlying issues and possibly may have service impact. 
  • The Minor Alarm will be raised.

Solution

This may be due to transient hardware SRAM error within EACHIP Fabric input block.

 

Perform these steps to determine the cause and resolve the problem (if any). Continue through each step until the problem is resolved.

 

  • Collect the show command output.

show log messages

show log chassisd

start shell network pfe

show nvram

show syslog messages

 

  • Analyze the show command output

In the 'show log messages', review the events that occurred at or just before the appearance of the "Parity error detected for timer SRAM" message. Frequently these events help identify the cause.


No RMA is required


With a single occurrence, the alarm can be cleared using the command:
clear chassis fpc errors fpc-slot <fpc-slot>

Multiple occurrence of these errors may require FPC reboot 
request chassis fpc slot X offline
request chassis fpc slot X online

Contact your technical support representative if this issue is seen repeatedly even after fpc reboot

Note: This error is classified as follow:

  • Junos 17.4 or later, the severity is downgraded to MINOR (from field data)
  • Junos 17.3 or earlier, the severity was classified as MAJOR causing PFE disabled

 

Tip: When looking at an event in the logs, it is important to focus on the first error message in a collection of syslog messages. The first error message is usually the cause of all the follow-on error messages. The follow-on collateral damage error messages can be ignored.

Modification History

New Article created