METRObility Optical Systems 8100 Manual Do Utilizador
Remote Network Monitoring 59
EtherStats CRC Align Errors: The total number of packets
received that had a length (excluding framing bits, but including
FCS octets) between 64 and 1518 octets, but 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).
received that had a length (excluding framing bits, but including
FCS octets) between 64 and 1518 octets, but 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).
EtherStats Undersize Pkts: 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.
received that were less than 64 octets long (excluding framing
bits, but including FCS octets) and were otherwise well formed.
EtherStats Oversize Pkts: The total number of packets
received that were longer than 1518 octets (excluding framing
bits, but including FCS octets) and were otherwise well formed.
received that were longer than 1518 octets (excluding framing
bits, but including FCS octets) and were otherwise well formed.
EtherStats 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: this is entirely normal for etherStatsFragments
to increment. This is because it counts both runts (which are
normal occurrences due to collisions) and noise hits.
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: this is entirely normal for etherStatsFragments
to increment. This is because it counts both runts (which are
normal occurrences due to collisions) and noise hits.
EtherStats Jabbers: 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).
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).
EtherStats Collisions: The best estimate of the total number of
collisions on this Ethernet segment. The value returned will
depend on the location of the RMON probe.
collisions on this Ethernet segment. The value returned will
depend on the location of the RMON probe.
Pkts 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) received that were 64 octets in length (excluding
framing bits, but including FCS octets).