cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1958
Views
0
Helpful
15
Replies

Help with error on 4507R with Sup V

branfarm1
Level 4
Level 4

Hi, I've been seeing these errors in the log of one of my 4507R switches and I need some help trying to interpret it:

Jun 18 13:32:03: %C4K_PKTPROCESSING-4-ERRORPACKET: Warning - Unexpected packet hitting output acl

pdd = 0x98000208, 0x80000076

118 bytes: 00 1C F6 DE 38 C0 00 19 BB 34 22 D6 08 00 45 00

00 64 71 A9 00 00 80 01 B2 F4 0A 0A 00 F5 0A 0A

00 F3 08 00 45 8E 00 08 C4 03 53 6F 6

Jun 18 13:32:03: %C4K_HWACLMAN-4-WARNINGSTRING: Output Acl HW Cam Stats

Jun 18 13:32:03: %C4K_HWACLMAN-4-WARNINGSTRING: Entry: 0 PacketCount: 8531106

Jun 18 13:32:03: %C4K_HWACLMAN-4-WARNINGSTRING: Entry: 2 PacketCount: 677

Jun 18 13:32:03: %C4K_HWACLMAN-4-WARNINGSTRING: Entry: 17 PacketCount: 7555084

Jun 18 13:32:03: %C4K_HWACLMAN-4-WARNINGSTRING: Entry: 48 PacketCount: 136

Jun 18 13:32:03: %C4K_HWACLMAN-4-WARNINGSTRING: Entry: 49 PacketCount: 24

Jun 18 13:32:03: %C4K_HWACLMAN-4-WARNINGSTRING: Entry: 80 PacketCount: 40196712

Jun 18 13:32:03: %C4K_HWACLMAN-4-WARNINGSTRING: Entry: 130 PacketCount: 44383869

Jun 18 13:32:03: %C4K_HWACLMAN-4-WARNINGSTRING: Entry: 16368 PacketCount: 1899438154

Jun 18 13:32:03: %C4K_HWACLMAN-4-WARNINGSTRING: Entry: 16384 PacketCount: 8531106

Jun 18 13:32:03: %C4K_HWACLMAN-4-WARNINGSTRING: Entry: 16416 PacketCount: 33274571

Jun 18 13:32:03: %C4K_HWACLMAN-4-WARNINGSTRING: Entry: 16432 PacketCount: 32117292

Jun 18 13:32:03: %C4K_HWACLMAN-4-WARNINGSTRING: Entry: 32752 PacketCount: 1899444422

As you can see from the timestamp, I'm getting these quite frequently. I don't have any outbound acl's applied anywhere so I;m confused about the warning message.

Thanks in advance,

--Brandon

15 Replies 15

Leo Laohoo
Hall of Fame
Hall of Fame

Did you experience a similar issue, with disastrous results?

Unfortunately, I had a X4013 spitting out different errors. Being a noob with Cisco gears, I didn't bother to check online. The Design Engineer went, "It's ok. Let's reboot the darn thing and see if the errors go away."

Let's just say that errors DID go away ... and the X4013 went along too.