Customer may see logs and FPC0 errors as follows continuously occur and clear:
PTX resiliencyd[19838]: RESILD_PD_SYSLOG_ACTION: <FPC 0> dlu_bf_prot_intr_d_bf_mem detected errorno 0x0000068b
PTX resiliencyd[19838]: CMError: /fpc/0/evo-cda-bt/0/cm/0/btchip/1/dlu_bf_prot_intr_d_bf_mem (0x45068b), scope: pfe, category: memory, severity: minor, module: btchip, type: dlu_bf_prot_intr_d_bf_mem, oc_category: lookup
PTX resiliencyd[19838]: Cmerror Op Set: btchip: chip_num:1 intr_full_name:dlu_bf_prot_interrupts_status_detected_bf_mem intr_bit_pos:12 log_err_reg:0x00001000 log_addr_reg:0x00020000 multiple_err_reg:0x00000000 (URI: /fpc/0/evo-cda-bt/0/cm/0/btchip/1/dlu_bf_prot_intr_d_bf_mem)
PTX resiliencyd[19838]: cmerror_level_decrement: for /fpc/0/evo-cda-bt/0/cm/0/btchip/1/dlu_bf_prot_intr_d_bf_mem (0x45068b), scope: pfe, category: memory, severity: minor, module: btchip, type: dlu_bf_prot_intr_d_bf_mem
PTX resiliencyd[19838]: Performing action log for error /fpc/0/evo-cda-bt/0/cm/0/btchip/1/dlu_bf_prot_intr_d_bf_mem (0x45068b) in module: btchip with scope: pfe category: memory level: minor, oc_category: lookup
PTX resiliencyd[19838]: Cmerror Op Clear: btchip: chip_num:1 intr_full_name:dlu_bf_prot_interrupts_status_detected_bf_mem intr_bit_pos:12 log_err_reg:0x00000000 log_addr_reg:0x00020000 multiple_err_reg:0x00000000 (URI: /fpc/0/evo-cda-bt/0/cm/0/btchip/1/dlu_bf_prot_intr_d_bf_mem)
Since this auto clears/corrects, we are not expecting any service impacts
These are parity error logs, not indicating a memory leak.
parity error in dlu.bf.bf_mem
This is a non-fatal error. The lookup in the bloom filter will be treated as a hit. This could increase the false positive probability of the bloom filter and software should reprogram the bloom filter entries affected. Since there are 64 banks (0-63) in the bloom filter, the address log logs the bank id instead of the full address. Bit “i” of the address log if set indicates a parity error in either bank 2*i or 2*i-1.
Recovery steps:
> Reboot chassis to see if this clears.
> If it does not clear proceed with RMA