Visara Master Console Center Administration Guide - Manual (Page 141)

Chapter 9 Managing and Editing Events with Event Manager
Administration Guide 141
How Event Manager Works
When the MCC is started, the Event Manager:
ƒ Begins scanning the printer queues for console messages.
ƒ Asks SNMP Trap Manager to forward all traps to Event Manager.
ƒ Begins checking scheduled rules against the current time and date.
When a new console message appears, Event Manager sequentially scans
through the Console Message Rules looking for a match. The first match causes
that rule’s actions to be performed. No additional rules are searched; the first
rule that matches is the only one that is triggered. Thus, event rule ordering is
an important factor.
When a new SNMP trap arrives, Event Manager sequentially scans through the
SNMP Trap Rules in a fashion similar to that for Console Messages.
When the current date and time match those specified in a Time Event, Event
Manager sequentially scans through the Time Event Rules, executing those
actions that are due.
For additional information, see Console Message Rules on page 143, SNMP Trap
Rules on page 152, and Time Event Rules on page 153.
When changes are made to the event rules using the Event Editor, a
configuration file is also changed. Event Manager normally only reads the
configuration file at startup. However, when configuration changes are saved,
Event Manager can be signaled to reprocess the event configuration file. Once
told to reprocess the configuration, Event Manager attempts to reset itself.
However, if there are pending actions to perform, Event Manager may not be
able to immediately reset. In this case, after 2 seconds of delay, the attempt will
fail and Event Editor brings up a screen indicating that Event Manager was too
busy. If this occurs, the choices are:
ƒ Attempt an immediate retry.
ƒ Initiate periodic retry (with 15 seconds delay between attempts).
ƒ Exit. In this case, Event Manager continues to use the old rules—the new
rules take effect at next system start or the next time changes are made and
saved, whichever occurs first.