Connected: An Internet Encyclopedia
RFC 1850 - 4.5. One Trap Per OSPF Event

Top: Connected: An Internet Encyclopedia
Up: Requests For Comments
Up: RFC 1850
Up: 4. OSPF Traps
Prev: 4.4. Throttling Traps
Next: 4.6. Polling Event Counters

### 4.5. One Trap Per OSPF Event

Several of the traps defined in section 5 are generated as the result of finding an unusual condition while parsing an OSPF packet or a processing a timer event. There may be more than one unusual condition detected while handling the event. For example, a link- state update packet may contain several retransmitted link-state advertisements (LSAs), or a retransmitted database description packet may contain several database description entries. To limit the number of traps and variables, OSPF should generate at most one trap per OSPF event. Only the variables associated with the first unusual condition should be included with the trap. Similarly, if more than one type of unusual condition is encountered while parsing the packet, only the first event will generate a trap.

Next: 4.6. Polling Event Counters

Connected: An Internet Encyclopedia
RFC 1850 - 4.5. One Trap Per OSPF Event