>> MIB - Management Information Base
>> Table: etherStatsTable - (.1.3.6.1.4.1.272.4.45.2.1)
Description: A collection of statistics kept for a particular Ethernet interface. As an example, an instance of the etherStatsPkts object might be named etherStatsPkts.1
etherStatsTable
OID | Name | Type | Access
.1 | Index | Integer32 | R
.2 | DataDirection | ENUM | R
.3 | DropPkts | Counter32 | R
.4 | Octets | Counter64 | R
.5 | GoodPkts | Counter64 | R
.6 | BroadcastPkts | Counter32 | R
.7 | MulticastPkts | Counter32 | R
.8 | CRCAlignErrors | Counter32 | R
.9 | UndersizePkts | Counter32 | R
.10 | OversizePkts | Counter32 | R
.11 | Fragments | Counter32 | R
.12 | Jabbers | Counter32 | R
.13 | Collisions | Counter32 | R
.14 | Pkts64Octets | Counter32 | R
.15 | Pkts65to127Octets | Counter32 | R
.16 | Pkts128to255Octets | Counter32 | R
.17 | Pkts256to511Octets | Counter32 | R
.18 | Pkts512to1023Octets | Counter32 | R
.19 | Pkts1024to1518Octets | Counter32 | R
.20 | PausePkts | Counter32 | R
Index
The value of this object together with the value of the etherStatsDataDirection object identifies this etherStats entry.
DataDirection
This object identifies the source of the data that this etherStats entry is configured to analyze. This source can be any ethernet interface on this device. In order to identify a particular interface, this object shall identify the instance of the ifIndex object, defined in RFC 2233 [17], for the desired interface. For example, if an entry were to receive data from interface #1, this object would be set to ifIndex.1. The statistics in this group reflect all packets on the local network segment attached to the identified interface. Enumerations: rx (1) tx (2)
DropPkts
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.
Octets
The total number of octets of data (including those in bad packets) received on the network (excluding framing bits but including FCS octets). This object can be used as a reasonable estimate of 10-Megabit ethernet utilization. If greater precision is desired, the etherStatsPkts and etherStatsOctets objects should be sampled before and after a common interval. The differences in the sampled values are Pkts and Octets, respectively, and the number of seconds in the interval is Interval. These values are used to calculate the Utilization as follows: Pkts * (9.6 + 6.4) + (Octets * .8) Utilization = ------------------------------------- Interval * 10,000 The result of this equation is the value Utilization which is the percent utilization of the ethernet segment on a scale of 0 to 100 percent.
GoodPkts
The total number of packets (including bad packets, broadcast packets, and multicast packets) received.
BroadcastPkts
The total number of good packets received that were directed to the broadcast address. Note that this does not include multicast packets.
MulticastPkts
The total number of good packets received that were directed to a multicast address. Note that this number does not include packets directed to the broadcast address.
CRCAlignErrors
The total number of packets received that had a length (excluding framing bits, but including FCS octets) of between 64 and 1518 octets, inclusive, 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).
UndersizePkts
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.
OversizePkts
The total number of packets received that were longer than 1518 octets (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 (which are normal occurrences due to collisions) and noise hits.
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). 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.
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. Section 8.2.1.3 (10BASE-5) and section 10.3.1.3 (10BASE-2) of IEEE standard 802.3 states that a station must detect a collision, in the receive mode, if three or more stations are transmitting simultaneously. A repeater port must detect a collision when two or more stations are transmitting simultaneously. Thus a probe placed on a repeater port could record more collisions than a probe connected to a station on the same segment would. 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.
Pkts64Octets
The total number of packets (including bad packets) received that were 64 octets in length (excluding framing bits but including FCS octets).
Pkts65to127Octets
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).
Pkts128to255Octets
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).
Pkts256to511Octets
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).
Pkts512to1023Octets
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).
Pkts1024to1518Octets
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).
PausePkts
The total number of pause packets received.

MIB Reference to Software Version 10.1.21 generated on 2016/12/23. Provided by webmaster@bintec-elmeg.com Copyright ©2016 by bintec elmeg GmbH