Defining the Notification Servers

In this task, you configure the Solaris computers, NS1 and NS2, as your primary and backup notification servers.

You must use the PATROL KM for Event Management to complete this task.

To Define NS1 as the Primary Notification Server

1. From the PATROL console on NT1, right-click NS1 and access the KM menu commands as described in Accessing KM Commands and InfoBoxes.
2. Choose the KM menu command Event Management > Quick Config > Notification Server.
    The QUICK CONFIG - NOTIFICATION SERVER dialog (the following figure) is displayed.
   
   QUICK CONFIG - NOTIFICATION SERVER Dialog Box
   
3. Enter the default e-mail account that receives notifications for all events that go into an alarm or warning state. For this example, use admin@abc.com as the default e-mail account. Later, you will define the e-mail target for our specific event: low disk space.
    The default e-mail account acts as a catch-all for events that don't have a specific e-mail target associated with them. Typically, when e-mail notifications are sent to the default e-mail account, you determine whether the event is valid and requires notification. If it is valid, you would associate the appropriate e-mail target to that event. For example, if the event was related to Microsoft Exchange, you would assign the e-mail target to the Microsoft Exchange administrator. If the event is not valid or is not important, you would adjust the alarm thresholds or possibly deactivate the parameter that spawned the event.
4. Enter the file name of the script that is run for event notification.
    To prevent the notification script from being overwritten during upgrades or new installations, make sure you have copied the notification script from the directory in which it is installed to another directory outside of the BMC Software directory structure. For more information, see Using-Notification-Scripts.
5. Click Accept.
6. Repeat Steps 1 to 6 for NS2, the backup notification server.

In this example, NS1 is the primary notification server for all of the monitored agents. However, you could configure NS1 as the primary notification sever for some of the remote agents and as the backup notification server for the other remote agents.