HP OpenView System Administration Handbook [Electronic resources] : Network Node Manager, Customer Views, Service Information Portal, HP OpenView Operations نسخه متنی

14.7 ACTIONS, MONITORS, COMMANDS AND EXTERNAL NOTIFICATION SERVICES

The components that are used to supplement the templates are usually created as scripts or programs. The files are referred to collectively as instrumentation. After distribution to the managed node the files are located in the directory /var/opt/OV/bin/instrumentation. A listing of the directory is shown here for reference.

# cd /var/opt/OV/bin/instrumentation
# ls
E10000Log.sh          mailq_l.sh            opclpst               ssp_config.sh        
 ana_disk.sh           mailq_pr.sh           opcnprcs              st_inetd.sh          
 cpu_mon.sh            mondbfile.sh          opcps                 st_mail.sh
disk_mon.sh           mwa_read.sh           perf_alxp.sh          st_syslogd.sh        
 dist_del.sh           opc_get_ems_resource  proc_mon.sh           swap_mon.sh
dist_mon.sh           opc_sec_v.sh          pv.sh                 vp_chk.sh            
 itogpm.sh             opcdf                 sh_procs.sh           last_logs.sh         
 opcfwtmp              ssp_chk.sh

14.7.1 Actions

The templates can be further enhanced to execute programmed automatic or operator-initiated actions on the managed nodes. The configuration interface is found in the actions section of the template. See Figure 14-18 for an example of the Actions and External Services configuration interface on for a template condition.

14.7.2 Monitors

A monitor is an external program or script that periodically, based on the template configuration, executes to determine run-time values that are forwarded via the monitor agent to the message agent. The program opcmon is used to send the values to the monitor agent. If the monitor agent evaluates the value and determines it violates the threshold established by the template configuration, a message is created.

14.7.3 Trouble Ticket Interface

The template also provides the configuration interface to instruct the agents to send message attribute information to external programs, such as trouble ticket, paging, and email systems. On the server, enable sending the message to a trouble ticket system. Configure the trouble ticket interface and select Forward to Trouble Ticket (the button is on the Conditions window). Some external application may provide the interface program for the pager program or trouble ticket system. Select

ActionsUtilitiesExternal Notification . See Figure 14-19.

14.7.4 External Services

The external Notification Schedule Configuration interface is found in the actions section of the template. Place a checkmark in the box for a notification service to receive the event notification from OVO via an external program, such as email or pager. Figure 14-18 shows the template interface that selects the Notification Service. The schedule for external notification programs, shown in Figure 14-20, is configured on the management server.

Configure the notification service to send a message using the external notification program at a specific time of the day or day of the week. The configuration process includes the following steps:

1. Select

   ActionsUtilitiesNotification Service, if there are notification schedules already configured, the window will show different colors for the vertical bars that represent the start and end of the service schedules.

2. Select Modify, which brings up the configuration dialog box (see Figure 14-21).

   Figure 14-21. Notification Method Configuration window determines which program to use for external notifications, such as a pager program.

   
   

   [View full size image]

   

3. Add the name of the program and the full path to the program, as shown in Figure 14-21. Add a second notification method if appropriate. Someone can create the interface program that will take the output of the OVO message and forward the information to the external application (trouble ticket system or pager system). The example shows a pager notification.

4. Create the notification schedule (see Figure 14-20) to send a page or email at the scheduled time. Select the day of the week from the top of the Notification Schedule window.

5. Enter the time to send the page (see Figure 14-22); if there are multiple notification methods, for example page and email, they are indicated with different vertical bars in the notification schedule window.

   Figure 14-22. The example schedule for the pager system shows the start and end time for pager notifications.

   
   

   

6. Select

   OK . If there is another type of notification service it will show up in the list. Select the arrow as shown in Figure 14-22 to view the list.

7. For each day, build the desired notification schedules. Figure 14-23 is the result of a notification schedule for each week, a pager schedule for the weekdays during business hours, and a separate email notification schedule for after hours and weekends.

   Figure 14-23. A weekly notification schedule could contain multiple notification methods each represented by a different vertical bar.

   
   

   [View full size image]