Extreme Networks EPICenter 6.0, Reference Manual

Page: 262 / 580

Real-Time Statistics
EPICenter Reference Guide
262
You can choose to have the component tree show the device name only, the device name followed by
the IP address in parentheses, or the device IP address followed by the device name in parentheses. See
Chapter 14 , “Administering EPICenter” for more details about how to display the device in the
component tree.
Real-Time Statistics Functions
There are multiple ways to invoke the functions provided by the Real-Time Statistics:
●
Using the menus at the top of the main applet frame
●
Using the function buttons shown directly below the EPICenter menus
●
Using commands from a pop-up menu that appears when you right-click on a device or device
group entry in the Component Tree, or when you right-click on a device node on the Topology or
EAPS map.
For simplicity, most of the instructions in this chapter only specify a one method of invoking a function
(usually the function button).
• etherHistoryCRCAlignErrors The number of packets received during this sampling interval that had a length
between 64 and 1518 octets, inclusive (excluding framing bits but including
Frame Check Sequence (FCS) octets), but that had either a bad FCS with an
integral number of octets (FCS Error) or a bad FCS with a non-integral number
of octets (Alignment Error).
• etherHistoryUndersizePkts The number of packets received during this sampling interval that were less
than 64 octets long (excluding framing bits but including FCS octets) and were
otherwise well formed.
• etherHistoryOversizePkts The number of packets received during this sampling interval that were longer
than 1518 octets (excluding framing bits but including FCS octets) but were
otherwise well formed.
• etherHistoryFragments The total number of packets received during this sampling interval that were
less than 64 octets in length (excluding framing bits but including FCS octets)
had either a bad Frame Check Sequence (FCS) with an integral number of
octets (FCS Error) or a bad FCS with a non-integral number of octets
(Alignment Error).
• etherHistoryJabbers The number of packets received during this sampling interval that were longer
than 1518 octets (excluding framing bits but including FCS octets), and had
either a bad Frame Check Sequence (FCS) with an integral number of octets
(FCS Error) or a bad FCS with a non-integral number of octets (Alignment
Error).
• etherHistoryCollisions The best estimate of the total number of collisions on this Ethernet segment
during this sampling interval.