Chapter 6. Event management products and best practices 315
Handling related events
You may be concerned with tracking events from the same problem that come in
after you open a trouble ticket. One way to manage this is in the supplied
If the flag
called _assoc_flag is set to on, it calls TroubleTicket.sh to send only an
update event and not to create a new ticket. This is for any events that are
duplicates of the original event that came in.
6.8 Maintenance mode
There are a many things to consider when it comes to maintenance modes. This
section attempts to describe how the corresponding IBM products handle this
type of situation.
NetView tracks the status of the devices it manages. It generates traps when it
detects changes in the condition of those devices. It also receives and processes
traps sent to it by SNMP-capable devices that have NetView defined as one of
their trap receivers. When discussing maintenance mode, it is important to
consider both types of traps.
Another consideration is how the NetView product is used. Consider the example
where all events within an organization are managed from IBM Tivoli Enterprise
Console, and no-one uses the NetView console for monitoring traps. In this case,
it may be sufficient to handle maintenance mode at the IBM Tivoli Enterprise
Console level and allow NetView to continue processing as normal. See 6.8.2,
“IBM Tivoli Enterprise Console” on page 328, for information about handling
event from devices in maintenance mode at the IBM Tivoli Enterprise Console
event server. Likewise, if the NetView user who monitors the console is the same
person who is performing the maintenance, it may not be necessary to take any
special action for the events.
We recommend that you use IBM Tivoli Enterprise Console to handle
maintenance mode when possible. Allow NetView to process traps as normal.
NetView and IBM Tivoli Switch Analyzer’s correlation capabilities can be used to
handle events generated by those products, performing root cause analysis to
suppress several unnecessary events. The device in maintenance mode is most
likely identified as the root cause of the problems. A trap reporting its status is
forwarded to other event processors. Assuming the processors were informed
that the network device is in maintenance mode through their normal means,