historyControlTable

1.3.6.1.2.1.16.2.1.1.1

historyControlIndex

Integer32{(1,65535)}

read-only

An index that uniquely identifies an entry in the

historyControl table. Each such entry defines a

set of samples at a particular interval for an

interface on the device.

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

1.3.6.1.2.1.16.2.1.1.2

historyControlDataSource

OBJECT IDENTIFIER

read-create

This object identifies the source of the data for

which historical data was collected and

placed in a media-specific table on behalf of this

historyControlEntry. This source can be any

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

historyControlStatus object is equal to valid(1).

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

1.3.6.1.2.1.16.2.1.1.3

historyControlBucketsRequested

Integer32{(1,65535)}

read-create

The requested number of discrete time intervals

over which data is to be saved in the part of the

media-specific table associated with this

historyControlEntry.

When this object is created or modified, the probe

should set historyControlBucketsGranted as closely to

this object as is possible for the particular probe

implementation and available resources.

The actually supported value range is 1-10.

1.3.6.1.2.1.16.2.1.1.4

historyControlBucketsGranted

Integer32{(1,65535)}

read-only

The number of discrete sampling intervals

over which data shall be saved in the part of

the media-specific table associated with this

historyControlEntry.

When the associated historyControlBucketsRequested

object is created or modified, the probe

should set this object as closely to the requested

value as is possible for the particular

probe implementation and available resources. The

probe must not lower this value except as a result

of a modification to the associated

historyControlBucketsRequested object.

There will be times when the actual number of

buckets associated with this entry is less than

the value of this object. In this case, at the

end of each sampling interval, a new bucket will

be added to the media-specific table.

When the number of buckets reaches the value of

this object and a new bucket is to be added to the

media-specific table, the oldest bucket associated

with this historyControlEntry shall be deleted by

the agent so that the new bucket can be added.

When the value of this object changes to a value less

than the current value, entries are deleted

from the media-specific table associated with this

historyControlEntry. Enough of the oldest of these

entries shall be deleted by the agent so that their

number remains less than or equal to the new value of

this object.

When the value of this object changes to a value greater

than the current value, the number of associated media-

specific entries may be allowed to grow.

The actually supported value range is 1-10.

1.3.6.1.2.1.16.2.1.1.5

historyControlInterval

Integer32{(1,3600)}

read-create

The interval in seconds over which the data is

sampled for each bucket in the part of the

media-specific table associated with this

historyControlEntry. This interval can

be set to any number of seconds between 1 and

3600 (1 hour).

Because the counters in a bucket may overflow at their

maximum value with no indication, a prudent manager will

take into account the possibility of overflow in any of

the associated counters. It is important to consider the

minimum time in which any counter could overflow on a

particular media type and set the historyControlInterval

object to a value less than this interval. This is

typically most important for the 'octets' counter in any

media-specific table. For example, on an Ethernet

network, the etherHistoryOctets counter could overflow

in about one hour at the Ethernet's maximum

utilization.

This object may not be modified if the associated

historyControlStatus object is equal to valid(1).

The actually supported value range is 5-3600.

1.3.6.1.2.1.16.2.1.1.6

historyControlOwner

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

historyControlStatus

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

read-create

The status of this historyControl entry.

Each instance of the media-specific table associated

with this historyControlEntry will be deleted by the agent

if this historyControlEntry is not equal to valid(1).

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