etherHistoryTable

1.3.6.1.2.1.16.2.2.1.1

etherHistoryIndex

Integer32{(1,65535)}

read-only

The history of which this entry is a part. The

history identified by a particular value of this

index is the same history as identified

by the same value of historyControlIndex.

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

1.3.6.1.2.1.16.2.2.1.2

etherHistorySampleIndex

Integer32{(1,2147483647)}

read-only

An index that uniquely identifies the particular

sample this entry represents among all samples

associated with the same historyControlEntry.

This index starts at 1 and increases by one

as each new sample is taken.

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

1.3.6.1.2.1.16.2.2.1.3

etherHistoryIntervalStart

TimeTicks

read-only

The value of sysUpTime at the start of the interval

over which this sample was measured. If the probe

keeps track of the time of day, it should start

the first sample of the history at a time such that

when the next hour of the day begins, a sample is

started at that instant. Note that following this

rule may require the probe to delay collecting the

first sample of the history, as each sample must be

of the same interval. Also note that the sample which

is currently being collected is not accessible in this

table until the end of its interval.

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

1.3.6.1.2.1.16.2.2.1.4

etherHistoryDropEvents

Counter32

read-only

The total number of events in which packets

were dropped by the probe due to lack of resources

during this sampling interval. 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.2.2.1.5

etherHistoryOctets

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 is implemented as defined in the corresponding MIB files.

1.3.6.1.2.1.16.2.2.1.6

etherHistoryPkts

Counter32

read-only

The number of packets (including bad packets)

received during this sampling interval.

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

1.3.6.1.2.1.16.2.2.1.7

etherHistoryBroadcastPkts

Counter32

read-only

The number of good packets received during this

sampling interval that were directed to the

broadcast address.

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

1.3.6.1.2.1.16.2.2.1.8

etherHistoryMulticastPkts

Counter32

read-only

The number of good packets received during this

sampling interval that were directed to a

multicast address. Note that this number does not

include packets addressed to the broadcast address.

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

1.3.6.1.2.1.16.2.2.1.9

etherHistoryCRCAlignErrors

Counter32

read-only

The number of packets received during this

sampling interval that had a length (excluding

framing bits but including FCS octets) 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.2.2.1.10

etherHistoryUndersizePkts

Counter32

read-only

The number of packets received during this

sampling interval 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.2.2.1.11

etherHistoryOversizePkts

Counter32

read-only

The number of packets received during this

sampling interval that were longer than 1518

octets (excluding framing bits but including

FCS octets) but were otherwise well formed.

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

1.3.6.1.2.1.16.2.2.1.12

etherHistoryFragments

Counter32

read-only

The total number of packets received during this

sampling interval that were less than 64 octets in

length (excluding framing bits but including FCS

octets) 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 etherHistoryFragments 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.2.2.1.13

etherHistoryJabbers

Counter32

read-only

The number of packets received during this

sampling interval 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.2.2.1.14

etherHistoryCollisions

Counter32

read-only

The best estimate of the total number of collisions

on this Ethernet segment during this sampling

interval.

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

etherHistoryUtilization

Integer32{(0,10000)}

read-only

The best estimate of the mean physical layer

network utilization on this interface during this

sampling interval, in hundredths of a percent.

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