Cisco 500 Series - Rmon History

Status and Statistics
RMON
31 Cisco 500 Series Stackable Managed Switch Administration Guide
2
• Jabbers—Received packets that were longer than 1632 octets. This
number excludes frame bits, but includes FCS octets that had either a bad
FCS (Frame Check Sequence) with an integral number of octets (FCS Error)
or a bad FCS with a non-integral octet (Alignment Error) number. A Jabber
packet is defined as an Ethernet frame that satisfies the following criteria:
- Packet data length is greater than MRU.
- Packet has an invalid CRC.
- Received (Rx) Error Event has not been detected.
• Collisions—Collisions received. If Jumbo frames are enabled, the threshold
of Jabber frames is raised to the maximum size of Jumbo frames.
• Frames of 64 Bytes—Frames, containing 64 bytes that were received.
• Frames of 65 to 127 Bytes—Frames, containing 65-127 bytes that were
received.
• Frames of 128 to 255 Bytes—Frames, containing 128-255 bytes that were
received.
• Frames of 256 to 511 Bytes—Frames, containing 256-511 bytes that were
received.
• Frames of 512 to 1023 Bytes—Frames, containing 512-1023 bytes that
were received.
• Frames of 1024 Bytes or More—Frames, containing 1024-2000 bytes, and
Jumbo Frames, that were received.
To clear statistics counters:
• Click Clear Interface Counters to clear the selected interfaces counters.
• Click View All Interfaces Statistics to see all ports on a single page.
RMON History
The RMON feature enables monitoring statistics per interface.
The History Control Table page
defines the sampling frequency, amount of
samples to store and the port from which to gather the data.
After the data is sampled and stored, it appears in the History Table page that can
be viewed by clicking History Table.