HP Integrity BL870c i2 Server-Blade - Manual (Page 81)

Command line 81
Name RFC Description
Probe location plays a much
smaller role when considering
10BASE-T. 14.2.1.4 (10BASE-T)
of IEEE standard 802.3 defines a
collision as the simultaneous
presence of signals on the DO
and RD circuits (transmitting and
receiving at the same time). A
10BASE-T station can only detect
collisions when it is transmitting.
Thus probes placed on a station
and a repeater, should report the
same number of collisions.
Note also that an RMON probe
inside a repeater should ideally
report collisions between the
repeater and one or more other
hosts (transmit collisions as
defined by IEEE 802.3k) plus
receiver collisions observed on
any coax segments to which the
repeater is connected.
rfc1757_StatsDropEvents 1757 The total number of events in
which packets were dropped by
the probe due to lack of
resources. Note that this number
is not necessarily the number of
packets dropped; it is just the
number of times this condition has
been detected.
rfc1757_StatsFragments 1757 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
(which are normal occurrences
due to collisions) and noise hits.
rfc1757_StatsJabbers 1757 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-