show rmon stats

Example

This example shows how to display RMON statistics for port 4 on module 1:

System(rw)->show rmon stats tg.1.4
Port: tg.1.4
--------------------
Index          = 1052
Owner          = monitor
Data Source    = ifIndex.13004
Direction      = rx+tx
Drop Events    = 0              Packets            = 0
Collisions     = 0              Octets             = 0
Jabbers        = 0              0    -   64 Octets = 0
Broadcast Pkts = 0              65   -  127 Octets = 0
Multicast Pkts = 0              128  -  255 Octets = 0
CRC Errors     = 0              256  -  511 Octets = 0
Undersize Pkts = 0              512  - 1023 Octets = 0
Oversize Pkts  = 0              1024 - 1518 Octets = 0
Fragments      = 0
System(rw)->

show rmon stats Output Details provides an explanation of the command output.

show rmon stats Output Details

Output...	What it displays...
Port	Port designation.
Owner	Name of the entity that configured this entry. Monitor is default.
Data Source	Data source of the statistics being displayed.
Direction	The direction (transmit/receive) from which statistics are collected.
Drop Events	Total number of times that the switch was forced to discard frames due to lack of available switch device resources. This does not display the number of frames dropped, only the number of times the switch was forced to discard frames.
Collisions	Total number of collisions that have occurred on this interface.
Jabbers	Total number of frames that were greater than 1518 bytes and had either a bad FCS or a bad CRC.
Packets	Total number of frames (including bad frames, broadcast frames, and multicast frames) received on this interface.
Broadcast Pkts	Total number of good frames that were directed to the broadcast address. This value does not include multicast frames.
Multicast Pkts	Total number of good frames that were directed to the multicast address. This value does not include broadcast frames.
CRC Errors	Number of frames with bad Cyclic Redundancy Checks (CRC) received from the network. The CRC is a 4-byte field in the data frame that ensures that the data received is the same as the data that was originally sent.
Undersize Pkts	Number of frames received containing less than the minimum Ethernet frame size of 64 bytes (not including the preamble) but having a valid CRC.
Oversize Pkts	Number of frames received that exceeded 1518 data bytes (not including the preamble) but had a valid CRC.
Fragments	Number of received frames that are not the minimum number of bytes in length, or received frames that had a bad or missing Frame Check Sequence (FCS), were less than 64 bytes in length (excluding framing bits, but including FCS bytes) and had an invalid CRC. It is normal for this value to increment since fragments are a normal result of collisions in a half-duplex network.
Octets	Total number of octets (bytes) of data, including those in bad frames, received on this interface.
0 – 64 Octets	Total number of frames, including bad frames, received that were 64 bytes in length (excluding framing bits, but including FCS bytes).
65 – 127 Octets	Total number of frames, including bad frames, received that were between 65 and 127 bytes in length (excluding framing bits, but including FCS bytes).
128 – 255 Octets	Total number of frames, including bad frames, received that were between 128 and 255 bytes in length (excluding framing bits, but including FCS bytes).
256 – 511 Octets	Total number of frames, including bad frames, received that were between 256 and 511 bytes in length (excluding framing bits, but including FCS bytes).
512 – 1023 Octets	Total number of frames, including bad frames, received that were between 512 and 1023 bytes in length (excluding framing bits, but including FCS bytes).
1024 – 1518 Octets	Total number of frames, including bad frames, received that were between 1024 and 1518 bytes in length (excluding framing bits, but including FCS bytes).