etherStatsTable

1.3.6.1.2.1.16.1.1.1.1

etherStatsIndex

Integer32{(1,65535)}

read-only

The value of this object uniquely identifies this

etherStats entry.

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.2.1.16.1.1.1.2

etherStatsDataSource

OBJECT IDENTIFIER

read-create

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.

An agent may or may not be able to tell if fundamental

changes to the media of the interface have occurred and

necessitate an invalidation of this entry. For example, a

hot-pluggable ethernet card could be pulled out and replaced

by a token-ring card. In such a case, if the agent has such

knowledge of the change, it is recommended that it

invalidate this entry.

This object may not be modified if the associated

etherStatsStatus object is equal to valid(1).

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.2.1.16.1.1.1.3

etherStatsDropEvents

Counter32

read-only

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.

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.2.1.16.1.1.1.4

etherStatsOctets

Counter32

read-only

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.

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.2.1.16.1.1.1.5

etherStatsPkts

Counter32

read-only

The total number of packets (including bad packets,

broadcast packets, and multicast packets) received.

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.2.1.16.1.1.1.6

etherStatsBroadcastPkts

Counter32

read-only

The total number of good packets received that were

directed to the broadcast address. Note that this

does not include multicast packets.

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.2.1.16.1.1.1.7

etherStatsMulticastPkts

Counter32

read-only

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.

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.2.1.16.1.1.1.8

etherStatsCRCAlignErrors

Counter32

read-only

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).

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.2.1.16.1.1.1.9

etherStatsUndersizePkts

Counter32

read-only

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.

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.2.1.16.1.1.1.10

etherStatsOversizePkts

Counter32

read-only

The total number of packets received that were

longer than 1518 octets (excluding framing bits,

but including FCS octets) and were otherwise

well formed.

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.2.1.16.1.1.1.11

etherStatsFragments

Counter32

read-only

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.

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.2.1.16.1.1.1.12

etherStatsJabbers

Counter32

read-only

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.

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.2.1.16.1.1.1.13

etherStatsCollisions

Counter32

read-only

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.

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.2.1.16.1.1.1.14

etherStatsPkts64Octets

Counter32

read-only

The total number of packets (including bad

packets) received that were 64 octets in length

(excluding framing bits but including FCS octets).

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.2.1.16.1.1.1.15

etherStatsPkts65to127Octets

Counter32

read-only

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).

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.2.1.16.1.1.1.16

etherStatsPkts128to255Octets

Counter32

read-only

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).

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.2.1.16.1.1.1.17

etherStatsPkts256to511Octets

Counter32

read-only

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).

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.2.1.16.1.1.1.18

etherStatsPkts512to1023Octets

Counter32

read-only

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).

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.2.1.16.1.1.1.19

etherStatsPkts1024to1518Octets

Counter32

read-only

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).

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.2.1.16.1.1.1.20

etherStatsOwner

OCTET STRING{(0,127)}

read-create

The entity that configured this entry and is therefore

using the resources assigned to it.

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.2.1.16.1.1.1.21

etherStatsStatus

INTEGER{valid(1),createRequest(2),underCreation(3),invalid(4)}

read-create

The status of this etherStats entry.

This object is implemented as defined in the corresponding MIB files.