Decoding Traps
To extract the variable bindings from the trap, it is recommended to use the OID (of the variables) instead of their positions. The reason is that the OID never changes while the position may change when additional variables are added to the trap. For example, the ruckusSCGSystemMiscEventTrap trap may originally contain the following four variable bindings:
- ruckusSCGEventSeverity
- ruckusSCGEventType
- ruckusSCGEventDescription
- ruckusSCGEventCode
Assuming in a future release, a new variable binding - ruckusSCGEventReason, is added to this trap, then ruckusSCGSystemMiscEventTrap trap will have the following five variable bindings:
- ruckusSCGEventSeverity
- ruckusSCGEventType
- ruckusSCGEventReason
- ruckusSCGEventDescription
- ruckusSCGEventCode
If the variable bindings are extracted based on the position, the original logic fails when the binding - ruckusSCGEventReason is added.
Though a newly-added variable binding is normally added at the end of the existing binding, sometimes it may placed in the middle to make it consistent with other traps.