All MIBs › CISCO-CEF-MIB › cefNotifThrottlingInterval
cefNotifThrottlingInterval
Module: CISCO-CEF-MIB
OID (symbolic): CISCO-CEF-MIB::cefNotifThrottlingInterval
OID (numeric): 1.3.6.1.4.1.9.9.492.1.9.4
Node type: OBJECT-TYPE
Type: Integer32
Access: read-write
Description: This object controls the generation of the cefInconsistencyDetection notification.
If this object has a value of zero, then the throttle control is disabled.
If this object has a non-zero value, then the agent must not generate more than one cefInconsistencyDetection 'notification-event' in the indicated period, where a 'notification-event' is the transmission of a single trap or inform PDU to a list of notification destinations.
If additional inconsistency is detected within the throttling period, then notification-events for these inconsistencies should be suppressed by the agent until the current throttling period expires. At the end of a throttling period, one notification-event should be generated if any inconsistency was detected since the start of the throttling period. In such a case, another throttling period is started right away.
An NMS should periodically poll cefInconsistencyRecordTable to detect any missed cefInconsistencyDetection notification-events, e.g., due to throttling or transmission loss.
If cefNotifThrottlingInterval notification generation is enabled, the suggested default throttling period is 60 seconds, but generation of the cefInconsistencyDetection notification should be disabled by default.
If the agent is capable of storing non-volatile configuration, then the value of this object must be restored after a re-initialization of the management system.
The actual transmission of notifications is controlled via the MIB modules in RFC 3413.
What is cefNotifThrottlingInterval?
This object controls how frequently the cefInconsistencyDetection notification can be sent, either disabling throttling with a value of 0 or capping it to at most one notification-event per the configured number of seconds. An admin sets a nonzero value here specifically to prevent a flapping or systemically corrupt FIB from flooding the NMS with a storm of near-identical traps, which could otherwise bury more important alerts or overload the trap receiver. On a router that occasionally experiences a burst of dozens of inconsistency detections within a few seconds, setting this to 60 would ensure the NMS receives at most one notification per minute rather than dozens of near-duplicate traps.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.9.9.492.1.9.4 snmpwalk -v2c -c public <target> CISCO-CEF-MIB::cefNotifThrottlingInterval
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.9.9.492.1.9.4.1 snmpget -v2c -c public <target> CISCO-CEF-MIB::cefNotifThrottlingInterval.1
Set instance 1 (SNMPv2c):
snmpset -v2c -c private <target> 1.3.6.1.4.1.9.9.492.1.9.4.1 i <value>
Start monitoring Cisco routers/Layer-3 switches (Cisco Express Forwarding) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CISCO-CEF-MIB::cefNotifThrottlingInterval OID value, configure state conditions and alerts, and monitor any Cisco routers/Layer-3 switches (Cisco Express Forwarding) from a single console.
OID Breakdown
Upper-level ancestors (8 from the standard OID tree / other modules)
| Numeric OID | Name | Module |
|---|---|---|
| 1 | iso | LANART-AGENT |
| 1.3 | org | AirPair-MIB |
| 1.3.6 | dod | AirPair-MIB |
| 1.3.6.1 | internet | AirPair-MIB |
| 1.3.6.1.4 | private | AirPair-MIB |
| 1.3.6.1.4.1 | enterprises | AirPair-MIB |
| 1.3.6.1.4.1.9 | cisco | CAT2600-MIB |
| 1.3.6.1.4.1.9.9 | ciscoMgmt | CISCO-SMI |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.9.9.492 | ciscoCefMIB | CISCO-CEF-MIB |
| 1.3.6.1.4.1.9.9.492.1 | ciscoCefMIBObjects | CISCO-CEF-MIB |
| 1.3.6.1.4.1.9.9.492.1.9 | cefNotifCntl | CISCO-CEF-MIB |
| 1.3.6.1.4.1.9.9.492.1.9.4 | cefNotifThrottlingInterval | CISCO-CEF-MIB |