86 ServerView Event Manager
Displaying traps in the Windows event log
5.2 Displaying traps in the Windows event log
When you install the Windows agents, you can specify whether the traps from
the Fujitsu MIB (e.g. HD.MIB, Mylex.MIB) are also to be written to the Windows
event log. The trap ID in the event log is shown increased by 10000 and not as
in the subsequent trap descriptions (e.g. the trap mylexBBUFound with the trap
number 275 is shown in the event log with the trap number 10275).
I With the Event Manager you can use alarm forwarding (logging) to
specify that traps are to be written to the Windows or LINUX event log.
The source name of the events in the event log is ServerView Services in
both Windows and Linux.
The event type of the log of UnknownTrap becomes an ERROR level.
5.3 Trap overview
The table below provides an overview of the MIBs which are integrated in the
Event Manager. Because these contents are frequently updated, this table and
the following trap lists are only a snapshot and do not claim to be complete. You
can find out which MIBs are currently integrated in the Event Manager via the
Alarm Configuration window (in the MIB column of the Alarm Rules - Assign Alarms
dialog box) or via the Event Manager online help.
The sections after the table provide an overview of the main types of trap. In
later sections of this chapter, the traps are ordered alphabetically by category.
Inside each category the traps are ordered alphabetically by name.
The Comments column indicates the number of the page on which the traps are
listed. You can also use the Event Manager to print out the trap lists. For more
information, see the section "Displaying trap information" on page 83.
MIB Traps from Comments
aac.mib Adaptec controller
ADICLIBMIB-v2.mib see page 119
adptinfo.mib
Asmpro.mib ASM PRIVATE COMMIB traps see page 160
baspCfg.mib
baspStat.mib
Table 17: MIB overview