2-714
Catalyst 6500 Series Switch Command Reference—Release7.6
78-15328-01
Chapter2 Catalyst 6500 Series Switch and ROM Monitor Commands
show counters
Related Commands clear counters
rxPause Number of control frames received at the gigabit level. This counter is valid only o n a
Gigabit Ethernet port.
rxTotalDrops The rxTotalDrops field includes these counters:
•Number of bad packets because of a CRC error, a coding violation, or a sequence error.
•Number of CBL blocking drops.
•Number of instances of invalid encapsulation.
•Number of broadcast suppression drops.
•Number of drops because the packet length is less than 64 or gr eate r than 15 18.
1. This number is not necessarily the number of packets dropped; it is just the number of times this condition has been detected.
2. It is entirely normal for etherStatsFragments to increment because it counts both runts (which are normal occurrences due to collisions) and noise hits.
3. This definition of jabber is different than the definition in IEEE-802.3 section 8.2.1.5 (10BASE5) and section 10.3.1.4 (10BASE2), which define jabber
as the condition where any packet exceeds 20 ms. The allowed range to detect jabber is between 20 ms and 150 ms.
4. An RMON probe inside a repeater should ideally report collisions between the repeater and one or more other hosts (transmit collisions as defined by
IEEE 802.3k) plus receiver collisions observed on any coax segments to which the repeater is connected.
5. This number is incremented when the alignmentError status is returned by the MAC service to the LLC (or other MAC user). Received frames for which
multiple error conditions obtained are counted exclusively according to the error status presented to the LLC.
6. This number is incremented when the frameCheckError status is returned by the MAC service to the LLC (or ot her MAC u ser). Receiv ed frames for which
multiple error conditions obtained are counted exclusively according to the error status presented to the LLC.
7. 512 bit-times corresponds to 51.2 microseconds on a 10-Mbps system. A (late) collision represented by an instance of this object is also considered as a
(generic) collision for other collision-related statistics.
8. The precise meaning of the count represented by an instance of this object is implementation-specific. In particular, an instance of this object may
represent a count of transmission errors on a particular interface not otherwise counted.
9. The precise meaning of the count represented by an instance of this object is implementation-specific. In particular, an instance of this object may
represent a count of receive errors on a particular interface not otherwise counted.
Table2-28 show counters Command Output Fields (continued)
Field Description