SPECTRUM Alarm Notification Manager (SANM)

Transcription

1 Titlepage SPECTRUM Alarm Notification Manager (SANM) Document Application & Gateway

2 Copyright Notice Document Copyright December 2001 Aprisma Management Technologies, Inc., 121 Technology Drive, Durham, NH USA. All rights reserved worldwide. Use, duplication, or disclosure by the United States government is subject to the restrictions set forth in DFARS (c)(1)(ii) and FAR Liability Disclaimer Aprisma Management Technologies, Inc. ("Aprisma") reserves the right to make changes in specifications and other information contained in this document without prior notice. In all cases, the reader should contact Aprisma to inquire if any changes have been made. The hardware, firmware, or software described in this manual is subject to change without notice. IN NO EVENT SHALL APRISMA, ITS EMPLOYEES, OFFICERS, DIRECTORS, AGENTS, OR AFFILIATES BE LIABLE FOR ANY INCIDENTAL, INDIRECT, SPECIAL, OR CONSEQUENTIAL DAMAGES WHATSOEVER (INCLUDING BUT NOT LIMITED TO LOST PROFITS) ARISING OUT OF OR RELATED TO THIS MANUAL OR THE INFORMATION CONTAINED IN IT, EVEN IF APRISMA HAS BEEN ADVISED OF, HAS KNOWN, OR SHOULD HAVE KNOWN, THE POSSIBILITY OF SUCH DAMAGES. Trademark, Service Mark, and Logo Information SPECTRUM, IMT, and the SPECTRUM IMT/VNM logo are registered trademarks of Aprisma Management Technologies, Inc., or its affiliates. APRISMA, APRISMA MANAGEMENT TECHNOLOGIES, the APRISMA MANAGEMENT TECHNOLOGIES logo, MANAGE WHAT MATTERS, DCM, VNM, SpectroGRAPH, SpectroSERVER, Inductive Modeling Technology, Device Communications Manager, SPECTRUM Security Manager, and Virtual Network Machine are unregistered trademarks of Aprisma Management Technologies, Inc., or its affiliates. For a complete list of Aprisma trademarks, service marks, and trade names, go to All referenced trademarks, service marks, and trade names identified in this document, whether registered or unregistered, are the intellectual property of their respective owners. No rights are granted by Aprisma Management Technologies, Inc., to use such marks, whether by implication, estoppel, or otherwise. If you have comments or concerns about trademark or copyright references, please send an to spectrum-docs@aprisma.com; we will do our best to help. SPECTRUM Alarm Notification Manager (SANM) Page 2

3 Restricted Rights Notice (Applicable to licenses to the United States government only.) This software and/or user documentation is/are provided with RESTRICTED AND LIMITED RIGHTS. Use, duplication, or disclosure by the government is subject to restrictions as set forth in FAR (June 1987) Alternate III (g)(3) (June 1987), FAR (June 1987), or DFARS (c)(1)(ii) (June 1988), and/or in similar or successor clauses in the FAR or DFARS, or in the DOD or NASA FAR Supplement, as applicable. Contractor/manufacturer is Aprisma Management Technologies, Inc., 121 Technology Drive, Durham, NH In the event the government seeks to obtain the software pursuant to standard commercial practice, this software agreement, instead of the noted regulatory clauses, shall control the terms of the government's license. Virus Disclaimer Aprisma makes no representations or warranties to the effect that the licensed software is virusfree. Aprisma has tested its software with current virus-checking technologies. However, because no anti-virus system is 100 percent effective, we strongly recommend that you write-protect the licensed software and verify (with an anti-virus system in which you have confidence) that the licensed software, prior to installation, is virus-free. Contact Information Aprisma Management Technologies, Inc. 273 Corporate Drive Portsmouth, NH Phone: U.S. toll-free: Web site: SPECTRUM Alarm Notification Manager (SANM) Page 3

4 Contents Preface 7 Overview 10 The Alarm-Monitoring Process...11 What SPECTRUM Does...11 What Alarm-Monitoring Applications Do...11 What SANM Does...11 The Policy Administrator...12 Policies...12 Association Restriction...13 The Filters within a Policy...13 SANM and Distributed SpectroSERVERs...14 The Policy Administrator Window 15 Opening the Policy Administrator Window...15 Command Line...16 SpectroGRAPH...16 Describing the Policy Administrator Window...17 Sections...17 Buttons and Fields...19 Creating and Editing Alarm Notification Policies 21 Creating a New Policy...22 Naming a Policy...22 Specifying Filters for a Policy...23 Saving a Policy...28 The IP Subnet Parameter...29 Inserting IP Network or Subnet Addresses into the Filter...29 Editing IP Subnet Values...31 Deleting IP Subnet Values...32 Deleting values in the Add Filter Values dialog box...32 Deleting values in the Open Policy window...33 Alarm Age...34 Alarm Notification Manager Page 4

5 Contents The Alarm Probable Cause Parameter...35 Notification Data...36 The Auto-Edit Parameter Values Option...39 Editing a Policy...40 Managing Associations 43 The Association Process...43 Understanding the Default Policy...44 Associating a Policy with an Application...45 Adding Application Names...46 Deleting Application Names...48 Deleting Policies...49 Scheduling Associations 52 Accessing the Scheduler...52 Describing the Scheduler Window...54 Scheduling Associations...56 Editing Scheduled Association Commands...60 Editing Procedures...61 Using SANM in a Distributed SpectroSERVER Environment 63 Managing SANM Policies Across Multiple Landscapes...63 Creating SANM Policies on Many Landscapes...64 Creating SANM Policies on One Landscape...64 Determining the Landscapes that are Currently Monitored...65 Monitoring SANM Events 67 SANM Events in the SPECTRUM Event Log...67 SANM Event Codes...68 Tracing Policies...69 Specifying Tracing for a SANM-Enabled Application...70 The Summary Trace File...72 The Detailed Trace File...72 SANM Resource File 75 Describing Resource File Parameters...75 Alarm Notification Manager Page 5

6 Contents Resource File Backups...77 Index 78 Alarm Notification Manager Page 6

7 Preface Describes this manual s audience and user prerequisites, organizational structure, and conventions. Welcome to the SPECTRUM Alarm Notification Manager (SANM) User s Guide. This manual describes how to use SPECTRUM Alarm Notification Manager (SANM) to manage the alarm notification process for SANMenabled applications. Who Should Read This Manual This manual is intended for SPECTRUM administrators or other networkmanagement personnel responsible for regulating the flow of SPECTRUM alarm notifications to SANM-enabled client applications. Prerequisites for Users Users should be familiar with the capabilities of the platform (Solaris, Windows NT/2000) on which SPECTRUM is installed, SPECTRUM modeling concepts and the SPECTRUM alarm-generation process, distributed SpectroSERVER, and SANM-compatible SPECTRUM applications. Alarm Notification Manager Page 7

8 Preface How This Manual is Organized This manual is organized as follows: Section Description Overview The Policy Administrator Window Creating and Editing Alarm Notification Policies Managing Associations Scheduling Associations Using SANM in a Distributed SpectroSERVER Environment Monitoring SANM Events SANM Resource File Describes SANM features. Describes how to start Policy Administrator and describes the Policy Administrator window. Describes how to create alarm notification policies with the SANM Policy Describes how to associate alarm notification policies with SANM-compatible applications and how to manage associations. Describes how to schedule associations between alarm notification policies and SANMcompatible applications using the SANM Policy Administrator Scheduler. Describes how SANM operates in a distributed SpectroSERVER environment. Describes how to track SANM events using the SPECTRUM Event Log and trace files. Describes SANM resource file parameters. Typographical Conventions This manual uses the following typographical conventions: User-supplied text appears in boldface within angle brackets. For example, <resource file> indicates that you must supply the name of a resource file. Alarm Notification Manager Page 8

9 Preface Screen text appears in Courier font. Examples of text you type in application fields, application commands, window sections, and directories and filenames appear in boldface. References to SPECTRUM publications appear in bold italics. References to chapter and section names appear in italics. (hypertext blue italics for on-line readers). Note: Calls your attention to information of special importance. Caution: Calls your attention to any action that may adversely effect application performance. Alarm Notification Manager Page 9

10 Overview Describes SANM features. SPECTRUM Alarm Notification Manager (SANM) enhances the functionality of SANM-compatible, SPECTRUM-client applications that respond in various ways ( notifications, trouble tickets, etc.) to alarms generated by SPECTRUM. SANM s Policy Administrator, an alarm filter configuration tool, enables you to specify and associate alarm notification policies with applications. A policy enables you to specify the types of alarms you want an alarm-processing application to receive and to filter out the alarms that you consider unimportant. When SANM is installed on your system, all SANM-compatible applications on your system are automatically enhanced by SANM, regardless of whether SANM is installed before or after the SANMcompatible applications. SANM extends the functionality of SANM-compatible applications in these specific ways: Provides additional alarm-management commands and adds to the feature set included with each particular SANM-compatible application. SANM s Policy Administrator enables you to design alarm notification policies that you can associate with SANM-compatible applications to regulate the alarm notifications generated or processed by each application. The SANM Policy Administrator Scheduler enables you to schedule the association of alarm notification policies with applications at specified times and frequencies. See the SPECTRUM Installation Guide (0675) for information on setting up the Windows NT/2000 Task Scheduler service. Provides the capability to manage alarms in a distributed SpectroSERVER environment from a single SpectroSERVER. Alarm Notification Manager Page 10

11 Overview The Alarm-Monitoring Process The Alarm-Monitoring Process The following sections describe how SPECTRUM, alarm-processing applications, and SANM work together in the alarm-monitoring process. What SPECTRUM Does SPECTRUM duties include: Polling network devices (routers, switches, etc.) and storing the information about their status in the SpectroSERVER database. Sharing alarm-filtering duties with SANM. (This functionality is only available when SANM Trace file options are not used. See Tracing Policies (Page 69) for more information.) Detecting alarm conditions for network and SPECTRUM elements modeled in SPECTRUM and generating alarms that indicate the severity of those conditions. What Alarm-Monitoring Applications Do SPECTRUM-client applications that receive and process SPECTRUM alarms use the alarm information generated by SPECTRUM in various ways. SPECTRUM s AlarmNotifier, for example, executes scripts that output alarm information to the terminal and can be configured to generate notifications. What SANM Does SANM capabilities are described as follows: SANM enhances the functionality of all the SANM-compatible applications on the system. In addition to the capabilities provided by SANM s Policy Administrator, these applications also gain additional commands, options, and parameters. Furthermore, SANM allows you to manage alarms from distributed landscapes from a single SpectroSERVER. Alarm Notification Manager Page 11

12 Overview The Policy Administrator SANM s Policy Administrator lets you create and associate alarm notification policies with SANM-compatible applications. Then SANM passes the alarm information to the applications only when the types of alarms specified in the policies occur. SANM reports new alarms in the order they are received and this is assumed to be chronological order. However, existing alarms are reported by the SpectroSERVER(s) in no particular order. SANM does not sort and may possibly change the order of the existing alarms. SANM s Policy Administrator Scheduler automates the association process by enabling you to schedule application and policy associations. The Policy Administrator SANM s Policy Administrator is a configuration tool that enables you to create, save, and implement alarm notification filtering policies. The procedures you perform with Policy Administrator fall into two basic categories: Creating and managing policies Define the various filters, parameters, and parameter values that make up policies. Save and revise policies. Associating policies with applications Associate a single policy to each application for immediate implementation or schedule associations between policies and applications on a one-time, daily, weekly, or monthly basis. Policies The Policy Administrator allows you to create alarm notification policies of varying complexity. A simple policy might specify that SANM pass information about Critical alarms for all routers to an application that is associated with the policy. A more complex policy might specify that SANM pass information about those Critical and Major alarms that remain unresolved for 10 minutes for a particular type of router and a particular type of switch that are NOT on a particular sub-network. Alarm Notification Manager Page 12

13 Overview The Policy Administrator Association Restriction Please note that you can associate an application instance with only one uniquely named alarm notification policy at a time. If you want a particular application to process different alarms, you must associate another policy with the application. You can do this manually at the time you want to implement the new policy, or you can use the Scheduler to schedule the new association automatically at the time and date you specify. To run the same application with different policies, you have to start multiple instances of the application, each with a unique name, and then associate the different policies with them. For example, the Policy Administrator recognizes AlarmNotifier1 and AlarmNotifier2 as different applications. Once you create unique names for the application, you can associate a unique policy with each instance of the application. The Filters within a Policy An alarm notification policy can include one or more filters. A filter can include one or more parameters, and each parameter can include one or more parameter values. Filters, parameters, and parameter values are the building blocks of an alarm notification policy. When you design a policy, remember the following guidelines: A policy can include up to a maximum of 100 filters. The Policy Administrator performs a Boolean logical AND between the parameters within the filter and a Boolean logical OR between the filters within the policy when evaluating an alarm. When you use the Negate option (for example, pass alarms that are not red and not orange from subnet ,....) to include a negative value in a parameter, all values for that parameter are negated. You cannot have a positive and a negative value in the same parameter. To illustrate these guidelines, consider the policy in Figure 1. This policy includes two filters, and each filter contains three Parameters: Model Type Name, Device Location, and Alarm Severity. Alarm Notification Manager Page 13

14 Overview SANM and Distributed SpectroSERVERs After you associate this policy with the application, SANM notifies the application when there is a critical alarm for a device of a Rtr_Cisco model type in any location except Building_A and Building_B OR when there is a critical alarm for a device of a Rtr_Wellfleet model type in Building_C. Figure 1: Sample Policy Containing Two Filters Filter 1 Parameter Model Type Rtr_Cis Model Type Name Rtr_Cisco AND Parameter Device Location NOT Building_A NOT Building_B AND Parameter Alarm Severity CRITICAL Policy Parameter OR Parameter Parameter Filter 2 Model Type Name Rtr_Wellfleet AND Device Location Building_C AND Alarm Severity CRITICAL SANM and Distributed SpectroSERVERs SANM monitors alarms from all landscapes in a distributed SpectroSERVER (DSS) environment. Even though different landscapes may model each other in a DSS environment, your SANM-enabled applications do not receive duplicate alarm information. See Using SANM in a Distributed SpectroSERVER Environment (Page 63) for complete information. Alarm Notification Manager Page 14

15 The Policy Administrator Window The Policy Administrator Window Describes how to start Policy Administrator and describes the Policy Administrator window. Opening the Policy Administrator Window You can open the Policy Administrator window (Figure 2) as follows on both the Solaris and Windows NT/2000 platforms: Command Line SpectroGRAPH Figure 2: Policy Administrator Window Alarm Notification Manager Page 15

16 Command Line 1 From a terminal window (Solaris) or bash shell (Windows NT/2000), navigate to the <$SPECROOT>/SANM directory. 2 Start up the Policy Administrator in one of the following ways: If you want to use the default resource file,.sanmrc, enter:./policyadmin If you want to use a modified version of the default resource file, enter:./policyadmin -r <resource file> (See SANM Resource File (Page 75) for information about the.sanmrc resource file.) SpectroGRAPH Select the SANM Policy Administrator option (Figure 3) from the Tools menu. Figure 3: Policy Administrator from the SpectroGRAPH Tools Menu Alarm Notification Manager Page 16

17 The Policy Administrator Window Describing the Policy Administrator Window Describing the Policy Administrator Window This section describes the sections, buttons, and fields of the Policy Administration window. Sections The three main sections (Figure 4) of the Policy Administrator window are described as follows: Associations Alarm Notification Policies Applications Lists policies and applications that have been associated. If you have run a SANM-enabled application but have not associated a policy with it, the application appears in the Associated Policies section linked with the DefaultPolicy. Lists all the policies that have been created. If you have just installed SANM, only the DefaultPolicy appears in this section. This initial DefaultPolicy is a null policy that is, it does not filter alarms. Lists applications that you can associate with policies. Application names appear in the section when you manually create an application name in the Policy Administrator window or automatically after you first run the SANM-enabled application. Alarm Notification Manager Page 17

18 The Policy Administrator Window Describing the Policy Administrator Window Figure 4: Policy Administrator Window Sections Associations Section Applications Section Alarm Notification Policies Section Alarm Notification Manager Page 18

19 The Policy Administrator Window Describing the Policy Administrator Window Buttons and Fields Policy Administrator fields and buttons are described as follows: Associates a policy with an application after you select a policy in the Alarm Notification Policies section and an application in the Applications section. The button becomes enabled after you select a policy and an application. See Managing Associations for more information on managing associations between policies and applications. Opens the Scheduler window, where you can schedule an association between a policy and an application. The button becomes enabled after you select an application from the Applications section. See Scheduling Associations for more information on scheduling associations between policies and applications. Opens the Open Policy window, where you can view or edit existing policies. The button becomes enabled after you select a policy from the Alarm Notification Policies section. See Creating and Editing Alarm Notification Policies for more information on viewing and editing policies. Selects or deselects the section that it points to either the Alarm Notification Policies or the Applications section. (You can also select these sections by clicking on an entry in the section.) When selected, a yellow border appears around the section and the New button becomes enabled. Alarm Notification Manager Page 19

20 The Policy Administrator Window Describing the Policy Administrator Window Adds a new policy name to the Alarm Notification Policies section, or adds a new application to the Applications section, after you select either section and type the policy or application name in the text-entry field. The button becomes enabled when you select an entry from either section. See Creating and Editing Alarm Notification Policies for information on creating a policy and Managing Associations for information on specifying applications you want to associate with policies. Deletes policies or applications after you select the policy or application you want to delete. The button becomes enabled when you select an entry from either the Applications or Alarm Notification Policies section. See Managing Associations for more information on deleting policies and applications. Search for a policy or application from a long list. Select the section you want to search, and type part or all of the policy or the application name you want to find. The field becomes enabled after you select the section you want to search. Alarm Notification Manager Page 20

21 Creating and Editing Alarm Notification Policies Creating and Editing Alarm Notification Policies Describes how to create alarm notification policies with the SANM Policy SANM s Policy Administrator enables you to create, save, and associate policies with SANM-enabled applications such as AlarmNotifier. A policy can consist of one or all of the following elements: Filter criteria based on a choice of eight parameters: SpectroSERVER Host, Landscape, Model Type Name, Model Name, Device Location, IP Subnet, Alarm Severity, and Alarm Cause. You must specify at least one filter in a policy and one parameter in a filter otherwise, you would just re-create the default policy, and all alarms for all models would pass through the policy. (Mandatory) Aging interval for an alarm specified in a policy filter. The Alarm Age parameter value is the length of time an alarm must exist before SANM allows notification of the alarm to the SANM-compatible application associated with a policy. (Optional) Comments or the names of recipients with each alarm in the Notification Data parameter. The user guide included with each SANMcompatible application suggests ways to use this parameter. (Optional) After you create a policy, you can associate it with one or more SANMcompatible applications. SANM then enforces that policy on all alarms and allows the application(s) access only to those alarms that meet the policy criteria. Alarm Notification Manager Page 21

22 Note: The information displayed in the Policy Administrator is always current. SANM dynamically updates the information in this window whenever any SANM user installs and runs new SANMenabled applications, creates, deletes, or associates policies, or adds new application names to the Applications section. Creating a New Policy You perform the following steps to create an alarm notification policy: 1 Name a policy. See Naming a Policy. 2 Create and assign filters to a policy. See Specifying Filters for a Policy. 3 Save the policy. See Saving a Policy. Naming a Policy To name a new policy, see Figure 5 and follow these steps: 1 Select the Alarm Notification Policies section in the Policy Administrator window. 2 Type the name of the new policy in the New name field (up to 32 characters allowed). If you give policies names that suggest when and under what circumstances they are used (e.g., ciscortrpm), you will more easily be able to select and implement policies available to you from a collection of saved policies. Alarm Notification Manager Page 22

23 Creating and Editing Alarm Notification Policies Figure 5: Naming a New Policy Click the New button. The new policy name appears in the Alarm Notification Policies section, and the Open Policy window (Figure 6) opens. It includes the policy name you entered in the New field. Specifying Filters for a Policy After you name a policy, you can define one or more filters (maximum of 100) for a policy. A policy requires at least one filter. To specify filters, see Figure 6 and follow these steps: 1 Click the Create button in the Open Policy window. If a filter already exists, you can select and make a copy of the existing filter using the Duplicate button. Then you can modify the copy. Alarm Notification Manager Page 23

24 Creating and Editing Alarm Notification Policies A filter box labeled Filter1 appears. Repeat to create additional filter boxes. 2 Click the Parameter button in Filter 1 to invoke the list of parameters that you can include in that filter. Figure 6: Specifying Filters in the Open Policy Window Policy Name Select a parameter from the Parameter list (Figure 7). An Add Filter Values dialog box for the parameter opens. Alarm Notification Manager Page 24

25 Creating and Editing Alarm Notification Policies Note: As a general rule, select more inclusive parameters before less inclusive parameters. Parameters are listed in descending order of inclusiveness (i.e., SpectroSERVER Host... Model Type Name... Alarm Severity). If you choose a less inclusive parameter first, you will not be able to select certain more inclusive parameters. For example, if you first specify the Location parameter, World, which is one of the default location views modeled in all SpectroSERVERS, you will not be able to then select a particular SpectroSERVER or Landscape parameter. Because you have specified that you want notification of alarms from all World locations, you have precluded selecting a particular SpectroSERVER or Landscape providing a world view of a particular network or network segment. 4 Select the parameter value(s) you want in the Add Filter Values dialog box and insert them into the filter using either of the following methods: Click the OK button to insert values in the filter and close the dialog box. Click the Apply button to insert the values in the filter and leave the dialog box open for more selections. Then click the OK or Cancel button to close the dialog box after you have finished applying values to the filter. To locate a value from a lengthy list, you can use the Search field in the Add Filter Values dialog box. See The Policy Administrator Window if you need information about the Search feature. To filter out values except those which contain specific characters, you can click the Search button to toggle to the Filter button. Then type the characters in the Add Filter Values dialog box. Only values which contain those characters appear in the list. The Filter function is not case-sensitive. Alarm Notification Manager Page 25

26 Creating and Editing Alarm Notification Policies Figure 7: Selecting Parameters for a Filter 3 4 Note: The parameter-selection procedures in this section are described based on the assumption that the Auto-Edit Parameters Values option in the Options menu is ON, the default setting. If you turn Auto-Edit OFF, the parameter selection process will differ slightly. See The Auto-Edit Parameter Values Option for more information. 5 Continue to select parameters and parameter values until you have added all the necessary parameters to your filter. Multiple values can be selected by pressing the Control key, then selecting individual values. Each selected value will be highlighted for inclusion. The IP Subnet and Alarm Cause parameters require special considerations. If you are adding these parameters, see The IP Subnet Parameter and The Alarm Probable Cause Parameter for more information. Alarm Notification Manager Page 26

27 Creating and Editing Alarm Notification Policies 6 Specify the Alarm Age (optional) using the increment and decrement arrow buttons in the Age field (Figure 8). You can specify an alarm age from 0 hours to 23 hours, 59 minutes. An alarm age of 0 means that the alarm notification is forwarded immediately. See Alarm Age for more information. 7 Specify the Notification Data (optional) for this filter (Figure 8). You can customize the information in this field for each application. If an alarm passes a filter, SANM sends the Notification Data from that filter to the application. If multiple filters pass the alarm, the application will receive a series of Notification Data entries in a string. See Notification Data for more information. Figure 8: Specifying Alarm Age and Notification Data Parameters Repeat Steps 1-7 to create additional filters. Figure 9 shows an example policy with multiple filters. Alarm Notification Manager Page 27

28 Creating and Editing Alarm Notification Policies Figure 9: Sample Policy Saving a Policy Saved policies are listed in the Policy Administrator window s Alarm Notification Policy section. To save a policy: 1 Select the Save or Save As option from the File menu (Figure 10). Figure 10: Saving a Policy 1 2 Alarm Notification Manager Page 28

29 Creating and Editing Alarm Notification Policies The Save As dialog box (Figure 11) opens if you select the Save As option. Type the name of the policy in the Enter Policy Name field, and then click the OK button. Figure 11: Save As Dialog Box Policy names must be unique. If you enter a duplicate name, an error message appears. menu. 2 Close the Open Policy window by selecting the Close option from the File The saved policy is listed in the Policy Administrator window s Alarm Notification Policies section. You can now associate the policy with one or more applications. The IP Subnet Parameter The Add Filter Values dialog box for the IP Subnet parameter allows you to enter the address of an IP network or any of its subnets as an alarm filter parameter. Inserting IP Network or Subnet Addresses into the Filter To insert values: 1 Type the value in the text field. IP network address (Class A, B, or C) Alarm Notification Manager Page 29

30 Creating and Editing Alarm Notification Policies -x for a Class A network (x = 1 127) -x.y.0.0 for a Class B network (x = ) -x.y.z.0 for a Class C network (x = ) IP Subnet address -x.y.z (e. g., ) -x.y.z.0 (e. g., ) 2 Insert the value(s) into the IP Subnet list using either of the methods described in Specifying Filters for a Policy. If you do not enter the IP address value in the correct format, an error message box displaying the correct format opens. Figure 12 shows an example invalid entry and an error message. Alarm Notification Manager Page 30

31 Creating and Editing Alarm Notification Policies Figure 12: Add Filter Values Dialog Box for the IP Subnet Parameter Invalid Entry Editing IP Subnet Values You can edit IP Subnet values included in the IP Selection list before you close the Add Filter Values dialog box. Once the dialog box has been closed, the values cannot be edited, it must be deleted and a new one inserted into the filter. To edit a value, see Figure 13 and follow these steps: 1 Select the value in the Add Filter Values dialog box. The value appears in the text field. The Update button is enabled once you make any change to the existing value. 2 Modify the value in the text field, and then click the Update button. This replaces the old value in the IP Subnet list above with the edited value. (If you click the Add button at this point, the new value is added to the list along with the old value rather than replacing the old value.) Alarm Notification Manager Page 31

32 Creating and Editing Alarm Notification Policies 3 Insert the new value into the filter by clicking Apply to continue editing other values or by clicking the OK button to close the box. Figure 13: Editing IP Network/Subnet Values 1 Value Changed 2 3 Deleting IP Subnet Values You can delete IP Subnet values in the Add Filter Values dialog box and in the Open Policy window. Deleting values in the Add Filter Values dialog box You can delete a value in the Add Filter Values dialog box list any time you are working with the box. The delete operation does not remove values you have previously added to IP Subnet list in the Open Policy window with the Apply button. It removes instead values you have added to the IP Subnet Selection list in the Add Filter Values dialog box. To delete an IP Subnet value in the Add Filter Values dialog box, see Figure 14 and follow these steps: 1 Select the value you want to delete. Alarm Notification Manager Page 32

33 Creating and Editing Alarm Notification Policies 2 Click the Delete button. The value disappears from the Subnet Selection list in the Add Filter Values dialog box (but not from the IP Subnet list in the Open Policy window). Figure 14: Deleting an IP Subnet Value from the Add Filter Values Dialog Box 1 Value Deleted From List 2 Deleting values in the Open Policy window The values you delete from the IP Subnet list in the Open Policy window are removed from the filter for the policy. To delete a value, see Figure 15 and follow these steps: 1 Select the IP Subnet value you want to delete from IP Subnet list in the Open Policy window. 2 Click Delete in the Parameter Operations section. The value disappears from the IP Subnet list. Alarm Notification Manager Page 33

34 Creating and Editing Alarm Notification Policies Figure 15: Deleting an IP Subnet Value from the Open Policy Window 2 1 Value Deleted From List Alarm Age The Alarm Age parameter for a policy filter specifies the time an alarm must exist before the alarm notification is passed to the application that is associated with the policy. Some alarms do not require attention because they are cleared within minutes, and thus can be filtered out using the Alarm Age parameter. Figure 16 shows an example of a filter with an alarm age of 5 minutes. If you have a policy with multiple filters with different Alarm Age values, the Policy Administrator uses the minimum value. For example, if a policy Alarm Notification Manager Page 34

35 Creating and Editing Alarm Notification Policies contains two filters one with an Alarm Age of 5 minutes and the other with an Alarm Age of 10 minutes and the alarm passes both filters, SANM will let the alarm age for 5 minutes before notifying the application. Existing alarms are aged from the time SPECTRUM generates the alarm (specified by the timestamp for the alarm). For example, if an existing alarm is 3 minutes old when you start a SANM-enabled application that is able to receive the alarm and the filter in the policy with which the application is associated specifies a 5 minute alarm age, SANM lets the alarm age 2 minutes before notifying the application. Figure 16: Alarm Age Section of the Filter Alarm Click increment arrows to increase interval. Click decrement arrows to decrease interval. Note: Synchronize the times on all SpectroSERVERs in a SANMenhanced distributed SpectroSERVER environment to ensure precise aging. The Alarm Probable Cause Parameter The Add Filter Values dialog box for the Alarm Cause parameter allows you to select the alarm probable cause ID(s) to include in a filter. When you select an ID, the description of the probable cause associated with the ID appears in the adjacent text section. Alarm Notification Manager Page 35

36 Creating and Editing Alarm Notification Policies When you select multiple IDs, the text related to the most recently selected ID is displayed. Figure 17 shows an example alarm probable cause selection. You apply alarm ID parameter values to your filter just as you would any other parameter value. Figure 17: Alarm Probable Cause Selection Dialog Box Notification Data The Notification Data parameter is an application-specific parameter. The type of data you provide it may vary, depending on how the SANMenabled application uses the Notification Data. You can use the information in this parameter for passing along information that may assist you in debugging policies, for notifying troubleshooting personnel about alarms, or for other application-specific purposes. The user s guide for each SANM-enabled application suggests ways to use this parameter. Alarm Notification Manager Page 36

37 Creating and Editing Alarm Notification Policies It is important to understand that SANM sends a filter s Notification Data to the application only if an alarm passes that particular filter. If the policy contains several filters that pass the alarm, SANM concatenates the Notification Data string from these filters, separating each string with a colon (:). The data from the first filter that passes the alarm appears first in the string, the second filter appears next, and so on. SANM passes the concatenated strings as an entire string to an application. The application then displays the entire string as a single Notification Data parameter. What begins as several strings of data from the various filters ends up as a single string of data in the SANM-enabled application. To illustrate the process, let us assume that you create a policy consisting of three filters that include the following Notification Data information: Filter1 Notification Data Williams or Varitek Filter2 Notification Data Offerman, Garciaparra Filter3 Notification Data Martinez, O Leary or Everett If an alarm passes Filter1 and Filter3 of the policy, SANM would send the following string to the application for the application s Notification Data parameter: If an alarm passes Filter1 and Filter3 of the policy, SANM would send the following string to the application for the application s Notification Data parameter: Williams or Varitek : Martinez, O Leary or Everett Filter 1 Filter 3 Entering information in the Notification Data parameter: 1 Click the User icon on the filter panel in the Open Policy window. Alarm Notification Manager Page 37

38 Creating and Editing Alarm Notification Policies A User Selection dialog box (Figure 18) opens. It lists authorized SPECTRUM users (user models created in the SpectroSERVERS that SANM monitors). 2 Select the names from the user list that you want forwarded to the SANM-enabled application. If you select multiple names, insert a separator between each user s name. To do this, either click the or button or the, (and) button or type the separator ( or or, ) directly in the text field. (The program will not let you choose another name from the user list until you first insert a separator.) SANM does not interpret the separators in any special way. It just passes the separators to the application. 3 Type directly in the text field if you want to insert a comment or other information that the application could use. 4 Click the OK button to insert the information in your filter and close the User Selection dialog box. Figure 18: Selecting User Names for Notification Data Note: The Policy Administrator does not check if Notification Data entries are valid. When entering names of SPECTRUM users, be sure to type them exactly as they appear listed in the SPECTRUM User Editor. Alarm Notification Manager Page 38

39 Creating and Editing Alarm Notification Policies The Auto-Edit Parameter Values Option The Auto-Edit Parameter Values option (Figure 19) from the Open Policy window s Options menu enables you to control the order in which you insert parameters and parameter values into the filter. Figure 19: Auto-Edit Parameter When Auto_Edit Parameter Values is enabled, parameter selection works this way: When you select one parameter in the Parameter list, the Add Filter Values dialog box for that parameter opens. Then you select the desired values for that parameter and insert them into the filter. You repeat this process (selecting one parameter and then its values in the Add Filter Values dialog box) until the filter is completed. When Auto_Edit Parameter Values is disabled, parameter selection works this way: The Policy Administrator allows you to select the parameters from the Parameter list all at once. Notice that the Add Filter Values dialog box does not automatically appear when you select a parameter. As you click each parameter, an empty parameter box appears in the filter. After the parameter boxes are inserted in the filter, you click the parameter name at the top of the parameter box to bring up that parameter s Add Filter Values dialog box. Then you select the desired values for that parameter and insert them into the filter. You continue by clicking on each parameter name at the top of the empty parameter box to bring up the Add Filter Values dialog box for that parameter until the filter is completed. Alarm Notification Manager Page 39

40 Creating and Editing Alarm Notification Policies Editing a Policy Editing a Policy You can edit a policy before or after you save it, regardless of whether or not it is associated with an application. If the policy is associated with an application, SANM begins enforcing the new policy as soon as you save your changes. When you edit policies, you are either in an edit filter mode or an edit parameter mode depending on whether the Filter Operations or Parameter Operations section is highlighted. The buttons in the Operations sections enable you to edit all filters and all parameters except Alarm Age and Notification Data. Figure 20 points out basic editing procedures. Figure 20: Editing a Policy To Enable Filter Operations Click in the Filter box background. To Enable Parameter Operations Click a parameter value. To Add Another Parameter to the Filter Click the Parameter button to pull down the parameter list. Then select a new parameter. To Add Values to a Parameter Click a parameter name to open the Add Filter Values dialog box. To Negate All Values in a Parameter Select a parameter value, then click the Negate button. All values in that parameter are negated. Alarm Notification Manager Page 40

41 Creating and Editing Alarm Notification Policies Editing a Policy Editing tasks are described as follows: If you want to... Add a new filter to the policy Duplicate a filter Delete a filter Add another parameter to the filter Negate parameter values Make negative parameter values positive Delete one or more parameter values Do this... Click the Create button to create the first filter in a policy. To insert additional filters to an existing policy, select a filter s background area to enable filter operations, and then click the Create button. A new filter appears in the window. Select the filter, and then click the Duplicate button. The duplicate filter appears in the window. Select the filter you want to delete, and then click the Delete button. Click the Parameter button and select another parameter. If the parameter is grayed-out, you cannot include it in the filter. The Policy Administrator does not allow incompatible parameter values in the same filter. You must create a new filter if you need the unavailable parameter or delete the parameter that is blocking it. Select a parameter value and click the Negate button. Notice that the Policy Administrator negates all the values listed under the parameter. You cannot have positive and negative values within the same parameter. Select a negative parameter value and click the Negate button. Notice that the Policy Administrator makes all the negative values listed under the parameter positive. You cannot have positive and negative values within the same parameter. Select one or more values in a parameter, and then click Delete in the Parameter Operations section. Deleting all parameter values deletes the parameter. Alarm Notification Manager Page 41

42 Creating and Editing Alarm Notification Policies Editing a Policy Delete the parameter itself Edit Alarm Age Edit Notification Data Entries Select one or more values in a parameter, Click Select All and then the Delete button in the Parameter Operations section. When you delete all the values in the parameter box, you delete the parameter itself. Use the increment and decrement buttons to specify a new Alarm Age value. In either the Open Policy window or the User Selection dialog box, click the cursor in the Notification Data text field and then delete or add text as desired. If the complete entry is not visible, click the cursor in the text and then use the arrow keys from the keyboard to scroll the text into view. You can also select User Names and separators from the User Selection dialog box. Alarm Notification Manager Page 42

43 Managing Associations Managing Associations Describes how to associate alarm notification policies with SANM-compatible applications and how to manage associations. After you create an alarm notification policy, you can associate the policy with one or more applications. An association between a policy and an application remains in effect until you associate another policy with that application or delete the associated policy. Managing associations involves the following tasks: Associating policies with applications. Associating an application with the Default Policy to stop alarm filtering. Adding new application names to the Applications section list. Deleting applications and policies. Before you begin associating policies with applications, read the sections The Association Process and Understanding the Default Policy, to understand exactly how the association process works, and the DefaultPolicy s role in that process. The Association Process These are the important points to remember when you associate policies with applications: You can associate policies with any application listed in the Policy Administrator window s Applications section. Although you can associate a single policy with multiple applications, each application can be associated with only one policy at a time. Remember that SANM enforces only one policy at a time on the application. Alarm Notification Manager Page 43

44 To change the policy an application is associated with, you associate the Default Policy or another policy with the application. If you delete the policy instead, SANM associates the Default Policy with the application. If you edit a policy that is associated with multiple applications, you change the policy for all applications with which it is associated. You do not have to reassociate the policy with the applications. Understanding the Default Policy The following questions and answers will help you understand the circumstances under which SANM implements the Default Policy. When is the Default Policy associated with an application? SANM associates the Default Policy with an application whenever you start up a SANM-enabled application the first time or if a policy that was associated with an application is deleted. You can also explicitly associate the Default Policy with an application at any time. Is the Default Policy always a null policy? By default it is, but not if filters have been added to it. When you first install SANM and run SANM-enabled applications, SANM associates a Default Policy with the applications. This initial Default Policy is a null policy; it does not filter alarms or carry out any of the other aspects of a policy. In other words, SANM-compatible applications receive information about every alarm that occurs on every landscape in the landscape map in the SpectroSERVER to which SANM is connected. SANM does allow you, however, to modify the initial Default Policy so that it is no longer a null policy. Even though you can edit the policy, it is still associated by default with applications that are not associated with userdefined policies. How do you know if the Default Policy has been modified? Open the Default Policy and examine it. Before you delete policies, check to see if the Default Policy has been edited. The Policy Administrator does warn you that the policy you are deleting is currently associated with one Alarm Notification Manager Page 44

45 Managing Associations Associating a Policy with an Application or more applications. It does not, however, warn you that the Default Policy has been modified. If you do not want the Default Policy associated with an application, you should associate a different policy with the application before deleting the policy that is currently in effect. Can you delete the Default Policy? No. You can only modify it. Associating a Policy with an Application You can associate policies to applications before or after the applications have been started (or even installed). To associate a policy with an application, see Figure 21 and follow these steps: 1 Select an application from the Policy Administrator window s Applications section list. Applications that have not been started since SANM was installed are not listed in the Applications section. See Adding Application Names for information about adding application names to the Policy Administrator before they are started. 2 Select the policy you want to associate with the application you selected from the Policy Administrator window s Alarm Notification Policies section list. If you have many policies or applications, enter the first few letters of the of the policy or application in the Search field in the section you want to search. The list automatically scrolls to the part of the list that includes the policy or application you are seeking. 3 Click the Associate button. The application and the policy appear in the Associated Policies section at the top of the window. This policy remains in effect for the application until you either associate another policy with the application or you delete this policy and SANM associates the Default Policy with the application. Alarm Notification Manager Page 45

46 Managing Associations Adding Application Names Figure 21: Associating a Policy with an Application Default Association Listed Here New Association Listed Here Adding Application Names There is only one situation where you would have to add an application name to the Applications section list when you want to associate a policy with an application before SANM has knowledge of the application s Alarm Notification Manager Page 46

47 Managing Associations Adding Application Names presence on the system where SANM is installed. If SANM is installed on a system and the application has not been started on that system, then SANM will not have any knowledge of its presence, and the application will not be listed. However, after you manually add the application name to the Applications section list, you can associate a policy with it, and the policy will take effect for the application when it is started. To add an application name to the Applications section list, see Figure 22 and follow these steps: 1 Select the Policy Administrator window s Applications section. 2 Type an application name in the New section field. 3 Click the New button. The application name you specified appears in the Applications section list. Alarm Notification Manager Page 47

48 Managing Associations Figure 22: Naming a New Application Deleting Application Names New Application Listed Here Deleting Application Names You delete an application name from the Applications section list when you want to remove an entry listing an application you are no longer using. To delete an application name, see Figure 23 and follow these steps: 1 Select the application name you want to delete from the Policy Administrator window s Applications section list. 2 Click the Delete button. The application name is removed from the Applications section list. If the application is associated with a policy, the application and the policy with which it is associated are removed from the Associated Policies section list as well. Alarm Notification Manager Page 48

49 Managing Associations Deleting Policies Note: When the application is running and you delete the application name from the Policy Administrator, the policy with which the application is associated with remains in effect for the application until you shut down the application. When you restart the application, the application name reappears in the Applications section list and associated with the Default Policy the Associated Policies section list. Figure 23: Deleting an Application 1 2 Application Deleted From List Deleting Policies To delete an policy, see Figure 24 and follow these steps: Alarm Notification Manager Page 49

50 Managing Associations Deleting Policies 1 Select the policy name you want to delete from the Policy Administrator window s Alarm Notification Policies section list. 2 Click the Delete button. If the policy is not associated with an application, the policy is removed from the Alarm Notification Policies section list. If the policy is associated with an application, SANM also deletes the policy from the Associated Policies section list and associates the Default Policy with the application. Note: Remember that the Default Policy may or may not be a null policy, depending on whether you or other users have modified it. Be sure to check if the Default Policy has been modified before you delete policies that are associated with an application. Alarm Notification Manager Page 50

51 Managing Associations Deleting Policies Figure 24: Deleting a Policy 1 2 Policy Deleted From List Alarm Notification Manager Page 51

52 Scheduling Associations Describes how to schedule associations between alarm notification policies and SANM-compatible applications using the SANM Policy Administrator Scheduler. The Scheduler automates the association process, enabling you to implement the alarm notification policies you want whenever you want. For example, if you want an application to take action in response to a particular type of an alarm during the evening, you might create a special evening policy and schedule the association of this policy with your particular application for 6 PM daily. Moreover, you could also schedule the association of a different daytime policy with the same application for 7 AM daily. The Scheduler performs the associations at the specified times. Without the Scheduler, you would have to manually associate a new policy every time you wanted to filter alarms in a different way. You can view the results of any operation performed by the Scheduler in the SPECTRUM Event Log. Monitoring SANM Events describes the Event Log and other methods available for monitoring the implementation of alarm notification policies. Note: Windows NT/2000 Considerations Before using the Scheduler, Windows NT/2000 users should make sure that the Task Scheduler Service is setup properly. See the SPECTRUM Installation Guide (0675) for information on setting up the Windows NT/2000 Task Scheduler service. Accessing the Scheduler See Figure 25 and follow these steps to access the Scheduler: 1 Select an application in the Policy Administrator window s Applications section. Do not select the policy that you are going to associate with the application at this point. You do this from the Scheduler window. Alarm Notification Manager Page 52

53 Scheduling Associations Accessing the Scheduler Figure 25: Selecting an Application for a Scheduled Association Click the Schedule Association button. The Scheduler window (Figure 26) opens. The window lists pending scheduled associations. Notice that some buttons in the Scheduler window are disabled when you first open it and later when you are working within it. A disabled button indicates that its corresponding option is not available at that particular time for the operation you are performing. Alarm Notification Manager Page 53

54 Scheduling Associations Figure 26: Describing the Scheduler Window Scheduler Window Describing the Scheduler Window Fields and buttons in the Scheduler are described as follows: Current Date & Time Fields Associate Button Command Field Displays the date and time (in the 24-hour format) on the system from which you accessed Policy Administrator. Opens the Modify Association dialog box, where you can select the policy that you want the Scheduler to associate with the application you specified in the Policy Administrator window when you invoked the Scheduler. Displays the scheduled association command created for the association. You cannot modify this field. Alarm Notification Manager Page 54

55 Scheduling Associations Describing the Scheduler Window Frequency Button Scheduled Entries List Add Button Modify Button Remove Button Save Button Reset Button Specifies the frequency option for the scheduled association. Frequency options are: Once, Hourly, Daily, Weekly, and Monthly. With the exception of NT users, the Once frequency allows you to schedule an association any time between the current date and one year later. Note that associations scheduled for an Hourly, Daily, Weekly, or Monthly frequency are performed until you delete or change the entry. Windows NT/2000 Considerations The Scheduler does not include the Hourly frequency option. Notice also that the Once frequency allows you to schedule an association no more than one month after the current date. Lists entries saved to the list and entries that you have added but not yet saved to the list. You can expand the list to view entire entries by resizing the window with the mouse pointer. Adds scheduled association entries to the Scheduled Entries list. Asserts modifications made to entries listed in the Scheduled Entries list. Deletes entries from the Scheduled Entries list. Saves additions and modifications to the Scheduled Entries list and deletions from the list. Removes unsaved entries from the Scheduled Entries list. Close Button Closes the Scheduler window. Alarm Notification Manager Page 55

56 Scheduling Associations Scheduling Associations Scheduling Associations To schedule an association: 1 Click the Associate button in the Scheduler window. The Modify Association dialog box (Figure 27) opens. Figure 27: Modify Association Dialog Box Select the policy listed in the Modify Association box to associate with the application you selected in the Policy Administrator window before you invoked the Scheduler. 3 Click the OK button to close the Modify Association dialog box. The Command field now indicates the association you just specified. You should see an association command string that looks like this: Directory/SANM/associate -p A-Policy -a AlarmNotifier -ph 0x ah 0x The Scheduled Entries list remains empty until you specify when you want the association to occur. Alarm Notification Manager Page 56

57 Scheduling Associations Scheduling Associations 4 Select a Frequency option, Hourly (Solaris only), Daily, Once (the default option), Weekly, or Monthly. The Frequency section displays the configuration box for the frequency option (Figure 28) you selected. 5 Specify the time and date or both for the selected frequency option. The Once option allows you to specify the month, day, and starting time of a single operation. On Solaris you can schedule the association on any day between the current date and one year later. On Windows NT/2000 you can schedule the association on any day between the current date and one month later. The Hourly option allows you to specify the minutes after the hour to schedule an association each hour. You can schedule the association to occur at any point from the beginning of each hour (00) to 59 minutes after the hour. (Not available for Windows NT/2000 users.) The Daily option allows you to specify the time of day (hour:minute) you want to schedule an association each day. The Weekly option allows you to specify the day of the week and the time of day you want to schedule an association each week. The Monthly option allows you to specify the day of the month and the time of day you to schedule an association each month. Alarm Notification Manager Page 57

58 Scheduling Associations Scheduling Associations Figure 28: Frequency Options: Hourly, Daily, Once, Weekly, Monthly 4 Frequency Section 5 Alarm Notification Manager Page 58

59 Scheduling Associations Scheduling Associations 6 Click the Add button to insert the scheduled association command to the Scheduled Entries list. 7 The entry appears in the list (Figure 29). 8 Click the Save button to send the entry or entries to the scheduled operations queue on your system (crontabs directory for Solaris, Schedule service for Windows NT/2000) when you are finished. 9 Click the Close button to close the Scheduler window. Note: You must open a new Scheduler window each time you want to schedule an association between a particular application and a policy. Figure 29: Adding and Saving the Scheduled Association /5.2/SANM/associate -p SamplePolicy -a AlarmN Mon Nov at 01:00 /usr/data/spectrum/5.2/sanm/ass Alarm Notification Manager Page 59

60 Scheduling Associations Editing Scheduled Association Commands Editing Scheduled Association Commands You can edit a scheduled association command entry in the following ways: Change the policy and the frequency option specified in the entry before or after you save it. Delete an entry before or after you save it. A scheduled entry consists of two parts, the scheduled time at the beginning of the line followed by the command specification, which is enclosed in quotes. Policies and applications are identified by their names and their model handles. Figure 30 shows the parts of a Scheduled Entry. Figure 30: Parts of a Scheduled Entry command Application Name Application Model Handle Hourly at XX: 30 /Spectrum/SANM/associate -p EveryHalfHour -a AlarmNotifier -ph 0x22006b6 -ah 0x220065e Scheduled Time Policy Name Policy Model Handle To make editing easier, enlarge the Scheduler window to view a larger portion of an entry, as shown in Figure 31, so that you can confirm that the changes you make to an entry are correct. Click the Modify button when you have finished changing an entry. If you want to revert back to the entry s original configuration, close the window without saving your changes or click the Reset button to revert back to most recently saved version of the window. See Editing Procedures for more information. Alarm Notification Manager Page 60

61 Scheduling Associations Editing Scheduled Association Commands Figure 31: Scheduled Entry in the Scheduler Window Mon Nov at 01:00 /usr/data/spectrum/5.2/sanm/associate -p SamplePolicy -a AlarmNotifie Editing Procedures Editing procedures are described as follows: If you want to... Edit the frequency, date, or time Do this... Select the entry you want to modify in the Scheduled Entries list. Then click the Frequency button and choose a frequency (Once, Hourly, Daily, Weekly, or Monthly). After you choose a different frequency or modify the existing frequency, click the Modify button. The modified entry changes in the Scheduled Entries list. Click the Save button to save the entry to the scheduled operation queue on your system. Alarm Notification Manager Page 61

62 Scheduling Associations Editing Scheduled Association Commands Delete an entry from the Scheduled Entries field or the scheduled queue View the entries that have been applied to the scheduled queue Discard unsaved changes Apply any changes to entries in the scheduled queue Select the entry you want to delete in the Scheduled Entries list. Then click the Remove button. The Scheduler deletes the entry from the Entries section. Click Save before you close the Scheduler window to delete the entry from the scheduled operation queue on your system. Click the Reset button. The Scheduler rereads the scheduled queue and displays saved entries in the Scheduled Entries list. Click the Reset button. The Scheduler discards the unsaved entries and displays the scheduled queue entries in the Scheduled Entries list. Click the Save button. Note: When you use the Once frequency to schedule an association, the Scheduler performs the task and then updates the entry in the Scheduled Entries field so that the task is scheduled at the same time the following year. Alarm Notification Manager Page 62

63 Using SANM in a Distributed SpectroSERVER Environment Managing SANM Policies Across Multiple Landscapes Using SANM in a Distributed SpectroSERVER Environment This section describes how SANM operates in a distributed SpectroSERVER environment. A Distributed SpectroSERVER (DSS) environment allows you to divide SPECTRUM s network management tasks among several SpectroSERVERS. When you create a network model with multiple SpectroSERVERs, it is possible for SANM to access information from more than one SpectroSERVER at the same time. A landscape is the SPECTRUM term for a network domain that is managed by a single SpectroSERVER. When SANM operates in a distributed environment, it monitors alarms from all landscapes. Even though different landscapes may model each other in a DSS environment, SANM-enabled applications do not receive duplicate alarm information. Because SANM evaluates alarms across VNMs in a DSS environment, you will probably want to limit the type of alarm notifications that you receive. If you work in a DSS environment, you can limit the number of alarm notifications by carefully defining the Landscape, Subnet IP Address, and Device Location parameters in the alarm notification policy. Managing SANM Policies Across Multiple Landscapes There are two ways to configure SANM in a distributed environment. You can create SANM policies on any landscape and allow SANM to read all policies from all landscapes, or you can create all SANM policies on one landscape and only allow SANM to read policies from that landscape. In Alarm Notification Manager Page 63

64 either case, alarm-processing applications from any landscape can be associated with the SANM policies. Creating SANM Policies on Many Landscapes You can set up a distributed environment so that SANM policies can be defined and managed on any SpectroSERVER in the distributed environment. Alarm-processing applications on any SpectroSERVER in the distributed environment have access to all of these policies. To set up this configuration: 1 The POLICY_LANDSCAPE parameter in the.sanmrc file must have no value associated with it. 2 Change the POLICY_LANDSCAPE parameter in the alarm-processing application s resource file (.alarmrc,.arsgrc, etc.) must also have no value associated with it. 3 Restart the SpectroSERVER where SANM is installed and restart the alarm-processing applications so that the changes to the resource file parameters will be read. 4 Open SANM s policy administrator. Note that all policies that have been created within the distributed environment are available and all alarm-processing applications in the distributed environment are available for association. Creating SANM Policies on One Landscape If you set up a distributed environment so that all policies for all landscapes are defined and managed from a single SpectroSERVER, alarm-processing applications can be installed on any of the SpectroSERVERS in the distributed environment. By setting the appropriate values in the applications resource file, the application finds the server that contains the SANM policy definitions and associates with the appropriate policy. This configuration cuts down on the initial traffic exchanged on the network as alarm processing applications and SANM policies are associated, and it also makes managing SANM policies easier on an ongoing basis. Alarm Notification Manager Page 64

65 Using SANM in a Distributed SpectroSERVER Environment Determining the Landscapes that are Currently Monitored Note: It is not possible to migrate or move a SANM policy from one landscape to another. If you would like to institute this configuration and already have policies defined on various landscapes, you must recreate these policies on the single landscape from which you will be managing SANM policies. To set up this configuration: 1 Change the POLICY_LANDSCAPE parameter in the.sanmrc file to the landscape handle of the SpectroSERVER where SANM is installed and policies will be created and managed. 2 Change the POLICY_LANDSCAPE parameter in the alarm-processing application s resource file (.alarmrc,.arsgrc) to the landscape handle of the SpectroSERVER where SANM is installed. This tells the application where to look for defined policies. 3 Restart the SpectroSERVER where SANM is installed and restart the alarm-processing applications so that the changes to the resource file parameters will be read. 4 Open SANM s policy administrator. Note that the only policies available are the policies that have been created on this landscape. All alarm-processing applications which have their POLICY_LANDSCAPE parameter set to the landscape handle of this landscape will be seen in the applications list. Determining the Landscapes that are Currently Monitored You can use the following methods to determine which landscapes are monitored by SANM: Alarm Notification Manager Page 65

66 Using SANM in a Distributed SpectroSERVER Environment Determining the Landscapes that are Currently Monitored Use the SPECTRUM Command Line Interface (CLI) application to connect to the SpectroSERVER to which SANM is connected, and then type show landscapes on the command line. The CLI application displays a list of all the landscapes modeled in that server. See Command Line Interface (0664) for more information. Open the Open Policy window from SANM s Policy Administrator window, and then select Landscape from the Parameter list from a filter. An Add Filter Values dialog box appears, listing available landscapes. Open any one of the detailed trace files you may have specified for SANMenabled applications. A trace file indicates the connection status of each landscape in the landscape map for the SpectroSERVER to which SANM is connected to that SpectroSERVER. Trace files are stored by default in a trace directory in a SANM-enabled application s home directory. See Tracing Policies (Page 69) for more information about the trace files. Alarm Notification Manager Page 66

67 Monitoring SANM Events Monitoring SANM Events Describes how to track SANM events using the SPECTRUM Event Log and trace files. This section discusses two resources you can use to access information about SANM activities: the SPECTRUM Event Log and trace files that can be generated for SANM-enabled applications. The SPECTRUM Event Log provides a record of all SPECTRUM events that have occurred for a SpectroSERVER, including those related to SANM operations. Use the SPECTRUM Event Log to confirm that SANM operations (scheduled associations for example) have been executed successfully. Trace file generation can be specified for a SANM-enabled application when the application is started. A summary trace file provides a record of only the alarm notifications that were passed by SANM to an application. A detailed trace file includes information about alarms that were passed or not passed to an application and a breakdown of which alarm attributes (location, severity, etc.) that did or did not meet the criteria specified by a policy. Use the trace file to see if a policy associated with an application is working as expected. The trace files are not part of SANM, but of the application(s) that use SANM s filtering mechanism. SANM Events in the SPECTRUM Event Log The SPECTRUM Event Log lists events that occur on a SpectroSERVER. When a user or the Scheduler performs a SANM operation, the results of the operation appear in the Event Log along with other SPECTRUM events. The Event Log contains the following information about the event: Date and time of the operation Application name and policy name User s host and user s name Explanation of the event Alarm Notification Manager Page 67

68 Monitoring SANM Events SANM Events in the SPECTRUM Event Log Event code Figure 32 shows an example Event Log with a variety of SANM-related entries listed. Refer to the SPECTRUM Event Log User s Guide for information on accessing and working with the Event Log. Figure 32: SPECTRUM Event Log Policy Created Policy Deleted Policy Modified Scheduled Association SANM Event Codes Each SANM event code corresponds to a particular SANM operation or operation failure. Use the following SANM event codes to locate SANM operation entries or filter out all but specific SANM operation entries in the SPECTRUM Event Log. Event Code Event Alarm Notification Manager Page 68