Hi, It looks like a memory error that is getting corrected. If it is working now I would continue to monitor. Rebooting the stack and then updating firmware would be the next steps.
hi, I got yesterday (once) this error block, firmware version is 6.3.3.10: <187> Dec 28 21:37:10 10.222.0.10-2 DRIVER[bcmDPC]: trident.c(3115) 12873 %% unit 0 L2_ENTRY_ONLY parity hardware inconsistency <187> Dec 28 21:37:10 10.222.0.10-2 DRIVER[bcmDPC]: trident.c(3115) 12872 %% unit 0 L2_ENTRY_ONLY parity hardware inconsistency <187> Dec 28 21:37:10 10.222.0.10-2 DRIVER[bcmDPC]: trident.c(3115) 12871 %% unit 0 L2_ENTRY_ONLY parity hardware inconsistency <187> Dec 28 21:37:10 10.222.0.10-2 DRIVER[bcmDPC]: trident.c(3115) 12870 %% unit 0 L2_ENTRY_ONLY parity hardware inconsistency <187> Dec 28 21:37:10 10.222.0.10-2 DRIVER[bcmDPC]: trident.c(3115) 12869 %% unit 0 L2_ENTRY_ONLY parity hardware inconsistency <187> Dec 28 21:37:10 10.222.0.10-2 DRIVER[bcmDPC]: trident.c(3115) 12868 %% unit 0 L2_ENTRY_ONLY parity hardware inconsistency <187> Dec 28 21:37:10 10.222.0.10-2 DRIVER[bcmDPC]: trident.c(3115) 12867 %% unit 0 L2_ENTRY_ONLY parity hardware inconsistency <187> Dec 28 21:37:10 10.222.0.10-2 DRIVER[bcmDPC]: ser.c(4655) 12866 %% CLEAR_RESTORE: L2X[3349] blk: ipipe0 index: 75779 : [0][0] <187> Dec 28 21:37:10 10.222.0.10-2 DRIVER[bcmDPC]: ser.c(4276) 12865 %% SER_CORRECTION: reg/mem:3349 btype:-1 sblk:0 at:1 stage:0 addr:0x00000000 port: 0 index: 75779 <187> Dec 28 21:37:10 10.222.0.10-2 DRIVER[bcmDPC]: trident.c(3224) 12864 %% unit 0 L2_ENTRY_ONLY entry 0x7132803 parity error <188> Dec 28 21:37:10 10.222.0.10-2 DRIVER[bcmDPC]: trident.c(3205) 12863 %% L2X entry id:12803 data:0x00000000 0x20000000 0x00000000 0x00000000 . <187> Dec 28 21:37:10 10.222.0.10-2 DRIVER[bcmDPC]: trident.c(3115) 12862 %% unit 0 L2_ENTRY_ONLY parity hardware inconsistency <187> Dec 28 21:37:10 10.222.0.10-2 DRIVER[bcmL2X.0]: mem.c(4979) 12861 %% L2_ENTRY.ipipe0 failed(NAK)   The error has not reappeared and everything as far as I can tell is working properly. This is a stack of 2 N4032 switches. The switch nor the stack have not been rebooted. I have seen some parity errors on this forum but not the one I got. Does anybody know what is means or can point me to a some manual where errors would be listed ? I checked N4032 documentation but did not find any reference to parity errors. Maybe there is nothing to do or maybe I just show reboot, or update firmware. I appreciate any input. Thank you
N4032 - Swtich parity error