Motorola MPC8260 User Manual
MOTOROLA
Chapter 30. Fast Ethernet Controller
30-15
Part IV. Communications Processor Module
30.12 Ethernet Address Recognition
The Ethernet controller can Þlter the received frames based on different addressing typesÑ
physical (individual), group (multicast), broadcast (all-ones group address), and
promiscuous. The difference between an individual address and a group address is
determined by the I/G bit in the destination address Þeld.
physical (individual), group (multicast), broadcast (all-ones group address), and
promiscuous. The difference between an individual address and a group address is
determined by the I/G bit in the destination address Þeld.
Figure 30-4 is a ßowchart for address recognition on received frames.
etherStatsFragments
The total number of packets received that were less than 64 octets
long (excluding framing bits but including FCS octets) and 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).
Note that it is entirely normal for etherStatsFragments to increment,
because it counts both runts (which are normal occurrences due to
collisions) and noise hits.
long (excluding framing bits but including FCS octets) and 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).
Note that it is entirely normal for etherStatsFragments to increment,
because it counts both runts (which are normal occurrences due to
collisions) and noise hits.
FRGC
etherStatsJabbers
The total number of packets received that were longer than 1518
octets (excluding framing bits but including FCS octets) and 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).
Note that this deÞnition of jabber is different than the deÞnition in
IEEE-802.3 Section 8.2.1.5 (10BASE5) and Section 10.3.1.4
(10BASE2). These documents deÞne jabber as the condition
where any packet exceeds 20 ms. The allowed range to detect
jabber is between 20 ms and 150 ms.
octets (excluding framing bits but including FCS octets) and 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).
Note that this deÞnition of jabber is different than the deÞnition in
IEEE-802.3 Section 8.2.1.5 (10BASE5) and Section 10.3.1.4
(10BASE2). These documents deÞne jabber as the condition
where any packet exceeds 20 ms. The allowed range to detect
jabber is between 20 ms and 150 ms.
JBRC
etherStatsCollisions
The best estimate of the total number of collisions on this Ethernet
segment.
segment.
COLC
etherStatsPkts64Octets
The total number of packets (including bad packets) received that
were 64 octets long (excluding framing bits but including FCS
octets).
were 64 octets long (excluding framing bits but including FCS
octets).
P64C
etherStatsPkts65to127Octets
The total number of packets (including bad packets) received that
were between 65 and 127 octets long inclusive (excluding framing
bits but including FCS octets).
were between 65 and 127 octets long inclusive (excluding framing
bits but including FCS octets).
P65C
etherStatsPkts128to255Octets
The total number of packets (including bad packets) received that
were between 128 and 255 octets long inclusive (excluding framing
bits but including FCS octets).
were between 128 and 255 octets long inclusive (excluding framing
bits but including FCS octets).
P128C
etherStatsPkts256to511Octets
The total number of packets (including bad packets) received that
were between 256 and 511 octets long inclusive (excluding framing
bits but including FCS octets).
were between 256 and 511 octets long inclusive (excluding framing
bits but including FCS octets).
P256C
etherStatsPkts512to1023Octets
The total number of packets (including bad packets) received that
were between 512 and 1023 octets long inclusive (excluding
framing bits but including FCS octets).
were between 512 and 1023 octets long inclusive (excluding
framing bits but including FCS octets).
P512C
etherStatsPkts1024to1518Octets The total number of packets (including bad packets) received that
were between 1024 and 1518 octets long inclusive (excluding
framing bits but including FCS octets).
framing bits but including FCS octets).
P1024C
Table 30-5. RMON Statistics and Counters (Continued)
Statistic
Description
Counter