6
Monitoring SAN Router Operation and Connections
6-17
Viewing Statistics
RMON (EtherStats)
(continued)
• Undersize packets - The total number of packets received that
were less than 64 octets long (excluding framing bits, but
including FCS octets) and were otherwise well formed.
• Fragments - The total number of packets received that were less
than 64 octets in length (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). Note that it is
entirely normal for etherStatsFragments to increment. This is
because it counts both runts and noise hits.
• Oversize packets - The total number of packets received 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).
Note that 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). These documents define jabber as the condition
where any packet exceeds 20 ms. The allowed range to detect
jabber is between 20 ms and 150 ms.
The oversize packet total includes the jumbo frame count, if the
Jumbo Frames feature is enabled.
• Packets (64 octets) - The total number of packets (including bad
packets) received that were 64 octets in length (excluding framing
bits but including FCS octets).
• Packets (65-127 octets) - The total number of packets (including
bad packets) received that were between 65 and 127 octets in
length inclusive (excluding framing bits but including FCS octets).
• Packets (128-255 octets) - The total number of packets (including
bad packets) received that were between 128 and 255 octets in
length inclusive (excluding framing bits but including FCS octets).
• Packets (256-511 octets) - The total number of packets (including
bad packets) received that were between 256 and 511 octets in
length inclusive (excluding framing bits but including FCS octets).
• Packets (512-1023 octets) - The total number of packets
(including bad packets) received that were between 512 and 1023
octets in length inclusive (excluding framing bits but including
FCS octets).
• Packets (1024-1518 octets) - The total number of packets
(including bad packets) received that were between 1024 and
1518 octets in length inclusive (excluding framing bits but
including FCS octets).
Table 6-6
Gigabit Ethernet/Port Statistics (Continued)
Item
Meaning
Содержание Eclipse 2640 SAN
Страница 1: ...Eclipse 2640 SAN Router Administration and Configuration Manual P N 620 00203 020 REV A...
Страница 10: ...x Eclipse 2640 SAN Router Administration and Configuration Manual Figures...
Страница 18: ...xviii Eclipse 2640 SAN Router Administration and Configuration Manual...
Страница 108: ...4 4 30 Eclipse 2640 SAN Router Administration and Configuration Manual Example Configurations and Procedures...
Страница 186: ...6 6 38 Eclipse 2640 SAN Router Administration and Configuration Manual Viewing Statistics...
Страница 202: ...7 7 16 Eclipse 2640 SAN Router Administration and Configuration Manual Retrieving and Clearing the System Log...
Страница 210: ...8 8 8 Eclipse 2640 SAN Router Administration and Configuration Manual SAN Router Troubleshooting...
Страница 276: ...Eclipse 2640 SAN Router Administration and Configuration Manual i 4 Index...