All MIBs › RMON2-MIB › usrHistoryControlInterval
usrHistoryControlInterval
Module: RMON2-MIB
OID (symbolic): RMON2-MIB::usrHistoryControlInterval
OID (numeric): 1.3.6.1.2.1.16.18.1.1.5
Node type: OBJECT-TYPE
Type: Integer32
Access: read-create
Description:
The interval in seconds over which the data is sampled for each bucket in the part of the usrHistory table associated with this usrHistoryControlEntry.
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 usrHistoryControlInterval object to a value less than this interval.
This object may not be modified if the associated usrHistoryControlStatus object is equal to active(1).
What is usrHistoryControlInterval?
This number sets how many seconds each bucket should cover—the sampling period for collecting statistics before moving to the next bucket. Engineers tune this to match their diagnosis goals: short intervals (60 seconds) catch rapid changes like packet bursts, while long intervals (3600 seconds) reduce storage but miss transient events. Setting this to 300 means each historical bucket summarizes 5 minutes of network activity.
OID Breakdown
| Numeric OID | Name | Module |
|---|---|---|
| 1 | iso | LANART-AGENT |
| 1.3 | org | BIANCA-BRICK-PPP-MIB |
| 1.3.6 | dod | BIANCA-BRICK-PPP-MIB |
| 1.3.6.1 | internet | BIANCA-BRICK-PPP-MIB |
| 1.3.6.1.2 | mgmt | BKTEL-HFC862-BASE-MIB |
| 1.3.6.1.2.1 | mib_2 | CHECKPOINT-MIB-2 |
| 1.3.6.1.2.1.16 | rmon | LBHUB-BOOM-MIB |
| 1.3.6.1.2.1.16.18 | usrHistory | RMON2-MIB |
| 1.3.6.1.2.1.16.18.1 | usrHistoryControlTable | RMON2-MIB |
| 1.3.6.1.2.1.16.18.1.1 | usrHistoryControlEntry | RMON2-MIB |
| 1.3.6.1.2.1.16.18.1.1.5 | usrHistoryControlInterval | RMON2-MIB |