cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2065
Views
0
Helpful
2
Replies

Dup Packet Fail cisco 4506 E

Shibu1978
Level 1
Level 1

Hi,

Does anyone know what the message below means?  It's from our WS-C4506-E log running Version 03.01.01.SG.


Dec 20 16:27:26.182: (Suppressed 851 times)Dup Packet Fail for Sw Port
Dec 20 2011 16:27:28.068 UTC: %LINK-3-UPDOWN: Interface GigabitEthernet4/22, changed state to up
Dec 20 2011 16:27:29.070 UTC: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet4/22, changed state to up
Dec 20 2011 16:29:13.738 UTC: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet4/22, changed state to down
Dec 20 2011 16:29:14.738 UTC: %LINK-3-UPDOWN: Interface GigabitEthernet4/22, changed state to down
Dec 20 16:42:37.173: (Suppressed 162 times)Dup Packet Fail for Sw Port
Dec 20 2011 16:42:39.071 UTC: %LINK-3-UPDOWN: Interface GigabitEthernet4/22, changed state to up
Dec 20 2011 16:42:40.071 UTC: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet4/22, changed state to up


cisco WS-C4506-E (MPC8572) processor (revision 8) with 786516K/16384K bytes of memory
Cisco IOS Software, IOS-XE Software, Catalyst 4500 L3 Switch Software (cat4500e-UNIVERSAL-M), Version 03.01.01.SG RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2010 by Cisco Systems, Inc.
Compiled Tue 14-Dec-10 21:30 by prod_rel_team


Backup#sh boot
Backup#sh bootf
Backup#sh bootflash:
-#- --length-- ---------date/time--------- path
  1      4096 Jul 08 2011 12:34:31 +00:00 .
  2  85229120 Mar 30 2011 10:24:55 +00:00 cat4500e-universal.SPA.03.01.01.SG.150-1.XO1.bin
  3      1152 Jul 08 2011 12:34:31 +00:00 FOX1502GZHQ_20110708132324790.lic

695681024 bytes available (85426176 bytes used)

Thanks

Shibu

2 Replies 2

acampbell
VIP Alumni
VIP Alumni

Hi,

The message "Dup Packet Fail for Sw Port" is seen when certain multicastpackets are software bridged and software has run out of buffers whilereplicating the packets in software.In typical deployments, one should NOT have a lot of multicast packets to CPU. Could you check what iscausing multicast packets to CPU periodically? Can you get the output of"show platform cpu packet driver" ? This could provide a hint as to packets drops due to high incoming rate to CPU.

It can be normal situation as some multicast should come to CPU to build all records, so depending on the mcast groups number sometimes buffers can be filled. So you can Change the logging level to '5' not to see that message.

Other possibility is that you get Multicast packets with TTL expired (TTL=1) thus those punted to CPU and dropped there. For this sniffer should be done on mcast ports to check mcast packets

Regards

Alex

Regards, Alex. Please rate useful posts.

Please find the output

Backup#show platform cpu packet driver
Forerunner Packet Engine 0.21

Receive Queues: received packets summary
Qu  Capac  Guara  CurPo  Unpro  Accum   Kept  BperP           Packets
2   2512    112   1770      0      2      2    398         186875167
8    512    512    268      0      4      4    226             71753
9   2512    304    257      0      1      1     73          15629740
11    208     64    192      0      0      0     66            346304
19   2512     64   1006      0      5      6     95           4781311
25    112     32      3      0      3      3     64                 3
40     64     16     55      0      7      7    741             43084
60    512    112    121      0      1      1    367         192580086
62   2512     64   2321      0      1      1   1369             69077

Receive Queues: dropped packets summary
Qu     Total Packets      Drop No Cell      Drop Overrun     Drop Underrun
2         186875167              9324                 0                 0
40             43084             52057                 0                 0
60         192580086              7137                 0                 0
62             69077             11275                 0                 0

Transmit Queues
Qu  PosAdd  Pendng           Packets               Bytes
0     952       1         851358591        132160133069
1    1848       0         327659329         22456412085

Transmitted via RxProc: 129430150

Link Stats
Rx Ucast 5197846, Mcast 332142936, Bcast 63174389
Tx Ucast 4820083, Mcast 1173849241, Bcast 348555
Rx Jumbo Packets 0, No Jumbo Buffer 0
Interrupt 408131061, Rx review 290409987, Driver review 118196117
Rx Buffers taken 400430393, returned 400430392
Run Mode 4, reset count 0, lost Tx packets 0
Free count 11823, guaranteed 3255, ptr 0B1EFC00, base 0B1EAA00
Rx overruns 0, Rx underruns 0 Freelist errors 0

SEU
seu_err_hist 0, seu_busy_hist 0 seu_det_hist 0
seu_err 0, seu_busy 0
seu_det 0, seu_mode 0, seu_err_inject 0, seu_run 1
Backup#

Thanks