Specifications

Traps, Events, and Alarms Vanguard 6400 and 6500 Trap Support
Device Management Page 118 Motorola Vanguard
Vanguard 6400 and 6500 Trap
Support
The Vanguard 6400 and 6500 series of devices
support approximately 1990 proprietary traps
from the vanguard-65xx-trap.mib MIB. The trap
OIDs supported are in the range
1.3.6.1.4.1.449.2.1.6.1000 ->
1.3.6.1.4.1.449.2.1.6.426019. Each of these
traps is processed directly on the device model in
SPECTRUM and is represented in the AlertMap
file, including a comment line that contains the
trap name.
The vanguard-65xx-trap.mib defines the severity
of individual traps in comments within the MIB.
For example, the code-power-supply-down trap is
defined as CRITICAL.
When mapping traps to events in the AlertMap
file, the SEVERITY comment is used to determine
which event should be generated for the the trap.
Based on severity, each trap will be mapped to
one of five unique events (Table 43):
The code-power-supply-down trap is CRITICAL so
we will generate the 0x2580050 event, which is
defined as critical and will result in an alarm.
Table 43: Vanguard 6400 Events
Unique Event
Generated
Event
Severity
Event or
Alarm
Generated
Event
Logged
0x02580020 Information Event Only No
0x02580025 Warning Event Only No
0x02580030 Minor Event Only No
0x02580040 Major Event Only No
0x02580050 Critical Event and
Red Alarm
Yes
Note:
Note:
Each of the traps in the vanguard-65xx-
trap.mib contain a common variable
binding (cdx6500SNMPLastTrap) which
is displayed in the EvFormat message
and can contain trap-specific variable
data in a format defined by the
vanguard-65xx-trap.mib. This variable
data can be used to create event rules
with the Event Condition rule. For more
information on event rules, see the
Event Configuration Files Guide
(5070).