Connected: An Internet Encyclopedia
RFC 1850 - 4.4. Throttling Traps

Top: Connected: An Internet Encyclopedia
Up: Requests For Comments
Up: RFC 1850
Up: 4. OSPF Traps
Prev: 4.3. Ignoring Initial Activity
Next: 4.5. One Trap Per OSPF Event

### 4.4. Throttling Traps

The mechanism for throttling the traps is similar to the mechanism explained in RFC 1224 [11], section 5. The basic idea is that there is a sliding window in seconds and an upper bound on the number of traps that may be generated within this window. Unlike RFC 1224, traps are not sent to inform the network manager that the throttling mechanism has kicked in.

A single window should be used to throttle all OSPF traps types except for the ospfLsdbOverflow and the ospfLsdbApproachingOverflow trap which should not be throttled. For example, if the window time is 3, the upper bound is 3 and the events that would cause trap types 1,3,5 and 7 occur within a 3 second period, the type 7 trap should not be generated.

Appropriate values are 7 traps with a window time of 10 seconds.

Next: 4.5. One Trap Per OSPF Event

Connected: An Internet Encyclopedia
RFC 1850 - 4.4. Throttling Traps