Chapter 6. Event management products and best practices 249
nvpaging.protocols: Defines the characteristics of the paging protocols:
TAP, IXO, PET, and PAKNET. The Protocol field in the nv.carriers file
specifies the paging protocol being used and points to the
nvpaging.protocols file for configuration information. If you are using a
paging protocol similar to TAP, IXO, PET, and PAKNET, copy the
information provided for one of these protocols and modify it with the
appropriate information for the protocol you are using.
See the nvpaging.protocols man page for more information.
After you update the configuration files, stop and restart the nvpagerd
daemon to make the changes available to the paging utility.
4. Create NetView security user profiles for those individuals who you want to
page automatically through an event correlation rule set.
When you use the Pager node in an event correlation rule set, you specify the
user ID of the person you want to page. The NetView security user profile defines
the user ID and the paging information. It is not necessary to activate security to
access the paging information in a user’s profile.
You can also send a page from the command line using the nvpage command.
See the man page for more information.
6.4.2 IBM Tivoli Enterprise Console
IBM Tivoli Enterprise Console has various methods of notification. This section
describes those methods.
Consoles
The IBM Tivoli Enterprise Console Version 3.9 now has two ways to view events
on a console:
򐂰 Java-based console
򐂰 Web-based console
The Java-based console is usually installed locally on an administrator’s desktop.
In IBM Tivoli Enterprise Console Version 3.9, it is mainly used for the console
configuration. Tivoli administrators responsible for that configuration should have
access to this console. Figure 6-19 shows an example of the configuration
window of the Java-based console.
250 Event Management and Best Practices
Figure 6-19 Example of an administrator’s configuration window
Also with this console, you have the functionality to view, close, acknowledge,
and run automated tasks for events. Operators can use this version of the
console to view all the events for which they are responsible. Figure 6-20 shows
an example of the event viewing section of the Java-based console. The main
disadvantage is that you have to install it on a workstation before you can view it.
Figure 6-20 Example of the Event Viewer window on the Java console

Get Event Management and Best Practices now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.