---
oid: "1.3.6.1.4.1.171.10.76.16.47.3.1.1.4"
asn1-notation: "{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) 171 dlink-products(10) dlink-DGS12XXSeriesProd(76) dgs-1210-28pbx(16) companyRMON(47) rmonHistory(3) rmonHistoryTable(1) rmonHistoryEntry(1) rmonHistoryInterval(4)}"
description: "rmonHistoryInterval OBJECT-TYPE"
classification: "MIB object for network management"
last-modified: "2022-08-03"
---

## OID : `1.3.6.1.4.1.171.10.76.16.47.3.1.1.4`

```asn1
{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) 171 dlink-products(10) dlink-DGS12XXSeriesProd(76) dgs-1210-28pbx(16) companyRMON(47) rmonHistory(3) rmonHistoryTable(1) rmonHistoryEntry(1) rmonHistoryInterval(4)}
```

### Description

```asn1
rmonHistoryInterval OBJECT-TYPE
SYNTAX Integer32 (1..3600)
UNITS "Seconds"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"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)."
DEFVAL {1800}
```

**Classification**: MIB object for network management

### Child OIDs

No child OID

### Terms of Use
[Terms of use](https://oid-base.com/disclaimer.htm.md)
