The syslog message XMCHIP_CMERROR_WI_MISC_SRAM_PAR_PROTECT_FSET_REG_DETECTED_ISTREAM2SBUCKET_MAP_SRAM reports issue related to XMCHIP on the FPC card. The article explains this error message along with other events that occur on the device.

Following is the log/message that appears on the device:

fpc.* XMCHIP(.*): XMCHIP(.*): WI0: Misc SRAM Protect: Multiple Errors 0x8 

fpc.* Cmerror Op Set: XMCHIP(.*): XMCHIP(.*): WI.*: Misc SRAM Protect: Parity error for IStream to Sbucket map SRAM (URI: /fpc/.*/pfe/.*/cm/.*/XMCHIP(.*)/.*/XMCHIP_CMERROR_WI_MISC_SRAM_PAR_PROTECT_FSET_REG_DETECTED_ISTREAM2SBUCKET_MAP_SRAM) 

Following alarm is active on the device:

1 alarms currently active

Alarm time Class Description

2024-11-01 07:40:21 PDT Minor FPC 0 Minor Errors

Since this is a CMERROR, we can proceed with the recommended actions based on the frequency of the logs

• If there is only single occurrence then these errors are non impacting and transient, no action needed.
• If the rate is 6 events per second or more, the system reports Minor alarm and FPC restart can help to clear the alarm
• If the rate is more than 255 events per second, then the system reports its as a Major alarm and we cab proceed with RMA for the FPC

This is a Troubleshooting Article for a PFE ASIC Syslog Event.

To view other documented Syslog events related to XMCHIP, XLCHIP, MQCHIP, LUCHIP, EACHIP, and PECHIP, see KB31893 [juniper.net].