Aug 27 14:26:22.650 2024 RE0 fpc0 precl_cmalarm_info_create: idx 1 for fpc 0 pic 0 aisc-id 112 asic-inst 0 pg 0 from config idx 0 error 0x340001 level 1 threshold 1 PRECL_CMERROR_INSTMEM_PARITY_FAIL

These events appear in the messages log:

Aug 27 14:26:22.650 2024 host-re0 fpc0 precl_cmalarm_info_create: idx 1 for fpc 0 pic 0 aisc-id 112 asic-inst 0 pg 0 from config idx 0 error 0x340001 level 1 threshold 1 PRECL_CMERROR_INSTMEM_PARITY_FAIL

Aug 27 14:26:22.650 2024 host-re0 fpc0 precl_cmalarm_info_create: idx 1 for fpc 0 pic 0 aisc-id 112 asic-inst 0 pg 0 from config idx 2 error 0x340004 level 1 threshold 1 PRECL_CMERROR_TCAM_PARITY_FAIL

Aug 27 14:26:22.650 2024 host-re0 fpc0 precl_cmalarm_info_create: idx 2 for fpc 0 pic 0 aisc-id 112 asic-inst 0 pg 1 from config idx 0 error 0x5c0001 level 1 threshold 1 PRECL_CMERROR_PG1_INSTMEM_PARITY_FAIL

These log events are NOT parity errors.

These are debug messages printed to inform that cmerrors are being registered and these are logged during the initialization when the FPC boots up.

They will only be displayed in messages log if 'any' is configured under syslog pfe

syslog-defaults {

       system {

           syslog {

               host <*> {

                   daemon info;

                   pfe any;