I've had TAC chewing on this error for the past month. Seems that the DFC in slot 2 and slot 3 are reporting the error. TAC's first inclination was bad hardware, so it was RMA'd, however the error showed up again a few days ago. A reboot cleared it and I haven't seen it since, but it's still alarming that "brand new" hardware would show exactly the same error, of which I have never seen before in my life.
Anyone seen this in the wild? Software issue perhaps? Gear: 7609/SUP720-3BXL15.2(2)S. 6748-GE-TX-3BXL (slot 2) 6748-GE-TX-3BXL (slot 3) Apr 25 16:16:22.527: %EARL_L2_ASIC-DFC2-4-SRCH_ENG_FAIL: EARL L2 ASIC Search Engine has failed -Traceback= 20B9414Cz 20B9AA84z 20BBA7FCz 20BBB638z 20BDC2A0z 20BDE674z Apr 25 16:16:22.531: DFC2: Dumping srcb info sman_setup_search Apr 25 16:16:22.531: DFC2: se_flags: 100 Apr 25 16:16:22.531: DFC2: se_data: 0x00040000000000000000000000000000 Apr 25 16:16:22.531: DFC2: se_mask: 0x00040000000000000000000000200000 Apr 25 16:16:22.531: DFC2: sew_data: 0x00000000000000000000000000000000 Apr 25 16:16:22.531: DFC2: sew_mask: 0xFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF ... <repeat a bazillion times until box is rebooted> Apr 25 16:16:32.927: %EARL_L2_ASIC-DFC3-4-SRCH_ENG_FAIL: EARL L2 ASIC Search Engine has failed -Traceback= 20B9414Cz 20B9AA74z 20BBA7FCz 20BBB638z 20BDC2A0z 20BDE674z Apr 25 16:16:32.927: DFC3: Dumping srcb info sman_setup_search Apr 25 16:16:32.927: DFC3: se_flags: 100 Apr 25 16:16:32.927: DFC3: se_data: 0x00040000000000000000000000000000 Apr 25 16:16:32.927: DFC3: se_mask: 0x00040000000000000000000000200000 Apr 25 16:16:32.927: DFC3: sew_data: 0x00000000000000000000000000000000 Apr 25 16:16:32.927: DFC3: sew_mask: 0xFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF ... <repeat a bazillion times until box is rebooted> _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
