cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
846
Views
0
Helpful
4
Replies

rxTotalDrops

kevinroper
Level 1
Level 1

I have a switch that has high rxTotalDrops. I've cleared counters for the port and the counters quickly grows. In the course of day the counter climbs into them millions. There are no other errors and none of the other switches show a high count. We are using VTP but are not blocking any VLANs. We are not using syslog either. We are looking at the counters telneted into the switch.

Ideas of where to start looking appreciated.

4 Replies 4

pkhatri
Level 11
Level 11

Hi Kevin,

It might help to know what types of drops these are... Would you be able to provide more info on the types of drops that are contributing to the high rxTotalDrops ?

Paresh

I don't see any other errors. I've pasted the sh count below

64 bit counters

0 rxHCTotalPkts = 133970164

1 txHCTotalPkts = 123558204

2 rxHCUnicastPkts = 121868238

3 txHCUnicastPkts = 121889497

4 rxHCMulticastPkts = 70128

5 txHCMulticastPkts = 189007

6 rxHCBroadcastPkts = 599547

7 txHCBroadcastPkts = 1479700

8 rxHCOctets = 89285405256

9 txHCOctets = 74205030855

10 rxTxHCPkts64Octets = 30852177

11 rxTxHCPkts65to127Octets = 79301345

12 rxTxHCPkts128to255Octets = 33413728

13 rxTxHCPkts256to511Octets = 12323378

14 rxTxHCpkts512to1023Octets = 9723078

15 rxTxHCpkts1024to1518Octets = 39350011

16 txHCTrunkFrames = 74378727

17 rxHCTrunkFrames = 75467478

18 rxHCDropEvents = 0

32 bit counters

0 rxCRCAlignErrors = 0

1 rxUndersizedPkts = 0

2 rxOversizedPkts = 0

3 rxFragmentPkts = 0

4 rxJabbers = 0

5 txCollisions = 0

6 ifInErrors = 0

7 ifOutErrors = 0

8 ifInDiscards = 0

9 ifInUnknownProtos = 0

10 ifOutDiscards = 0

11 txDelayExceededDiscards = 0

12 txCRC = 0

13 linkChange = 0

14 wrongEncapFrames = 0

0 dot3StatsAlignmentErrors = 0

1 dot3StatsFCSErrors = 0

2 dot3StatsSingleColFrames = 0

3 dot3StatsMultiColFrames = 0

4 dot3StatsSQETestErrors = 0

5 dot3StatsDeferredTransmisions = 0

6 dot3StatsLateCollisions = 0

7 dot3StatsExcessiveCollisions = 0

8 dot3StatsInternalMacTransmitErrors = 0

9 dot3StatsCarrierSenseErrors = 0

10 dot3StatsFrameTooLongs = 0

11 dot3StatsInternalMacReceiveErrors = 0

12 dot3StatsSymbolErrors = 0

0 txPause = 0

1 rxPause = 0

0 rxTotalDrops = 11432515

1 rxFIFOFull = 0

2 rxBadCode = 0

Last-Time-Cleared

--------------------------

Fri Jan 20 2006, 13:11:10

The rxTotalDrops counter includes a sum of the following counters:

* The number of bad packets because of a CRC error.

* A coding violation or sequence error.

* The number of Color Blocking Logic (CBL) blocking drops.

* The number of instances of invalid encapsulation.

* The number of broadcast suppression drops.

* The number of drops because the packet length is less than 64 or greater than 1518 bytes.

CBL refers to the spanning-tree state of a particular VLAN (color) on the port in question. If the port is in a spanning-tree blocking state for a particular VLAN, it is normal to drop packets received on that port for that VLAN.

I suspect these are CBL blocks ... Does anything above match your setup ?

Hope that helps - pls rate posts that help.

Regards,

Paresh

I had read these docs. I don't think any match. CRCs have a counter but how do you check for the others?

* A coding violation or sequence error.

* The number of Color Blocking Logic (CBL) blocking drops.

* The number of instances of invalid encapsulation.

* The number of broadcast suppression drops.

* The number of drops because the packet length is less than 64 or greater than 1518 bytes.

Also, how siginificant is the high count this switch exhibiting?

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: