OIDs - control_interval monitor
The objects described here can be monitored with the IPHost Network Monitor.
You can start SNMP monitoring using free 30-day trial version of IPHost right now.
OID list for control interval
- history Control Interval
- historyControlInterval 1.3.6.1.2.1.16.2.1.1.5 (defined in RMON-MIB)
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). - history Control Interval
- historyControlInterval 1.3.6.1.2.1.16.2.1.1.5 (defined in rfc1271)
The interval in seconds over which the data is sampled for each bucket in the part of the media-specific table associated with this historyControl entry. 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). - history Control Interval
- historyControlInterval 1.3.6.1.2.1.16.2.1.1.5 (defined in rfc1757)
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). - Cabletron Discovery Control Age Interval
- ctDiscoveryControlAgeInterval 1.3.6.1.4.1.52.4.3.2.20.2.1.6 (defined in ctrmonxt-mib)
The minimum amount of idle time that will be allowed for an entry before it may be deleted from the table by the agent. The aging routine is not required to run every second. - bsn Global Dot11b Dynamic Tx Power Control Interval
- bsnGlobalDot11bDynamicTxPowerControlInterval 1.3.6.1.4.1.14179.2.3.2.1.10 (defined in AIRESPACE-WIRELESS-MIB)
When Tx PowerControl dynamic alogirthm is running, this interval(in secs) specifies how often TxPower control updates are attempted on an Airespace AP. NOTE: hysteresis is build into the algorithms so we will not have uproductive changes occuring. Default value is 600 secs - bsn Global Dot11a Dynamic Tx Power Control Interval
- bsnGlobalDot11aDynamicTxPowerControlInterval 1.3.6.1.4.1.14179.2.3.3.1.14 (defined in AIRESPACE-WIRELESS-MIB)
When Tx PowerControl dynamic alogirthm is running, this interval(in secs) specifies how often TxPower control updates are attempted on an Airespace AP. NOTE: hysteresis is build into the algorithms so we will not have uproductive changes occuring. Default value is 600 secs