Use the following procedure to display Rmon History statistics.
|
|
Step | Action |
---|---|
|
|
1 |
Open the RmonControl window by selecting Serviceability, RMON, Control from the menu. |
2 |
Select a port in the RMON History tab. |
3 |
Click Graph. |
4 |
The RMON History window opens for the selected port. |
|
|
--End-- | |
|
The following table describes the RMON History window fields.
Field | Description |
---|---|
SampleIndex | Indicates the sample number. As history samples are taken, they are assigned greater sample numbers. |
Utilization | Estimates the percentage of a link’s capacity that was used during the sampling interval. |
Octets | The number of octets received on the link during the sampling period. |
Pkts | The number of packets received on the link during the sampling period. |
BroadcastPkts | The number of packets received on the link during the sampling interval that were destined for the broadcast address. |
MulticastPkts | The number of packets received on the link during the sampling interval that are destined for the multicast address. This does not include the broadcast packets. |
DropEvents | The number of received packets that were dropped because of system resource constraints. |
CRCAlignErrors | The number of packets received during a sampling interval that were between 64 and 1518 octets long. This length included Frame Check Sequence (FCS) octets but not framing bits. The packets had a bad FCS with either an integral number of octets (FCS Error), or a non-integral number of octets (Alignment Error). |
UndersizePkts | The number of packets received during the sampling interval were less than 64 octets long (including FCS octets, but not framing bits. |
OversizePkts | The number of packets received during the sampling interval were longer than 1518 octets (including FCS octets, but not framing bits, and were otherwise well formed. |
Fragments | The number of packets received during the sampling interval were less than 64 octets long (including FCS octets, but not framing bits. The packets had a bad FCS with either an integral number of octects (FCS Error), or a non-integral number of octets (Alignment Error). |
Collisions | The best estimate of the number of collisions on an Ethernet segment during a sampling interval. |