How do I change alarm view settings?

Alarm settings

This section describes configuration options for alarm appearance and behavior. To access the settings page, click on the More button in any alarm list and choose Settings.

Note: Alarm settings can only be configured by an administrator.

What can I configure on the Current Alarms settings panel?

The Current Alarms settings panel manages settings related to the alarm database and alarms in the alarm list. These settings apply to NSP, WS-NOC, and MDM alarms. NFM-P alarm settings are configured in NFM-P; see the NFM-P Administrator Guide. Using this panel, you can:

• Enable alarm aging Enable the Aging Settings option and configure the number of days after which an alarm is deleted in the Delete After (days) parameter. You can also configure aging for a specific alarm using an alarm policy.

• Configure when an overflow warning is triggered Configure the Warning Threshold (%) parameter

• Purge alarms in the event of an overflow Select Wrap from the Overflow Action drop-down list, then configure the percentage of the database to purge in the Purge Amount parameter, and which alarms to purge first in the Purge Policy parameter.

• Halt alarm collection in the event of an overflow Select Halt from the Overflow Action drop-down list.

What can I configure on the Historical alarms settings panel?

The Historical Alarms settings page manages settings related to the historical alarm database. These settings apply to NSP, WS-NOC, and MDM alarms. NFM-P alarm settings are configured in NFM-P; see the NFM-P Administrator Guide. Using this page, you can:

• Configure archive settings Enable the Archive Settings pattern and select either the Log on Change or Log on Deletion options.

• Specify overflow actions Specify the maximum alarm count, then specify warning and critical thresholds as a percentage of the maximum, and the number of alarms to purge when each threshold is reached.

What can I configure on the Global Alarm Policies page?

The System settings page manages settings related to NSP, WS-NOC, and MDM alarms. Using this page, you can:

• Enable manual changes to alarms Enable the Manual Settings parameter, then enable options to allow users to promote, demote, or clear alarms.

• Configure when users can delete alarms Enable the Alarm Deletion Settings and Manual Alarm Deletion Settings parameters, then choose an option that specifies when a user can delete a system alarm (for example, only after it has been acknowledged, or anytime without restriction).

• Enable notifications for deleting correlated alarms Enable the Alarm Deletion Settings and Correlated Alarm Settings for Manually Deleted Alarms parameters, then choose an option that specifies whether an alert is displayed when correlated alarms would be deleted by manually deleting a system alarm.

• Configure automatic deletion of alarms Enable the Alarm Deletion Settings and Automatic Alarm Deletion Settings parameters, then choose an option that specifies when to automatically delete alarms.

• Configure automatic acknowledgement of correlated alarms. Enable the Alarm Acknowledgement Policy and Correlated Alarm Settings for Manually Acknowledged Alarms parameters to automatically acknowledge any correlated alarms when a system alarm is manually acknowledged, and specify whether a GUI notification occurs when the correlated alarms are acknowledged.

• Configure automatic acknowledgement of cleared alarms. Enable the Alarm Acknowledgement Policy and Acknowledge alarms when cleared parameters to automatically acknowledge any alarms when they are cleared.

What can I configure on the Individual Alarm Policies page?

The Alarm Policies page manages policies related to NSP, WS-NOC, and MDM alarms. When the NSP receives an alarm for the first time, an alarm policy is created for the received alarm. You can use an alarm policy to perform automatic operations on an alarm when it is received. Changes to alarm policies are not retroactive, and only apply to alarms received in the future; to modify existing alarms, use the Alarm List view.

You can filter and sort the list using the columns, and select multiple policies at a time to perform mass configurations. Select one or more alarm policies, click on the More button, select Edit, and configure the parameters as required. Alarm properties you can configure using an alarm policy are:

• Squelch alarms. Enable the Squelch parameter to squelch all alarms of this type.

• Assign severity. Select a severity in Initial Assignment Severity to change the alarm’s type when it is raised.

• Acknowledge alarms. Enable the Auto Acknowledge parameter to acknowledge the alarm when it is raised.

• Disable historical alarm archiving. Disable the History parameter to disable archiving of the alarm.

• Apply custom text. Configure the Custom Text parameter to set the custom text of the alarm when it is raised. This will overwrite any other custom text on the alarm.

• Restore default values. Click Restore to Default to return all parameters to their default values.

• Enable alarm debouncing. Enable the Alarm Debouncing parameter. Alarm debouncing is only available for implicitly cleared alarms.

• Configure automatic escalation and de-escalation. Configure the Escalation Policies parameters to enable alarm escalation.

You can delete an alarm policy by clicking on the More button, and selecting Delete. Stale alarm policy entries may occur due to drift in alarm dictionary keys; it is safe to delete these stale policies.

What can I configure on the E-mail Policies page?

The e-mail policy feature allows administrative users to configure e-mail notification policies for specific alarm messages in NFM-P, WS-NOC, MDM, and NSP. An e-mail policy is configured with a filter. When an alarm message matches the filter criteria, the policy sends alarm notifications to a specified list of up to 20 user e-mail addresses. In order to manage bursts of alarms, e-mail notifications are pooled for up to one minute before sending. If there are more than ten alarms within one minute for a specific policy, a single e-mail notification is sent with a list of ten alarms. Each e-mail policy specifies the maximum number of e-mail notifications (up to 10) that can be sent over a one-hour period. The recipients are notified when the maximum has been reached.

Note: LI and mirror service alarms are not sent in e-mail notifications.

E-mails are not sent for alarm attribute change events, only for alarm creation. For example, if an alarm is created with a severity of major, and the severity is subsequently changed to critical, alarm e-mail policy filters for critical alarms will not include this alarm.

In order for NSP to send e-mail notifications, you must configure connection information for an e-mail server through the NSP settings page.

Using the E-Mail Policies settings page, you can:

• Create an e-mail policy Click on the + Email Policy button and configure the parameters. See How do I configure an e-mail policy?.

• Configure an e-mail policy Select an e-mail policy and configure the parameters in the details panel.

• Disable an e-mail policy Select an e-mail policy and disable the Enable parameter in the details panel.

• Delete an e-mail policy Select an e-mail policy and click the Delete button at the end of the row.

Example e-mail notification

The e-mail sent by the NSP consists of a link to the affected alarm, and a set of information about the alarm. The following is an example e-mail sent for a single NSP system alarm:

Subject: NSP Notification - New NSP Health-Alarm Received Select the link(s) below to launch the filtered alarm list for each alarm. To view the alarm you will be required to have access to an NSP system and to use your existing credentials for log in. https://233.252.0.0:443/FaultManagement/?view=alarmListImpacts＆alarmId;=fdn%3Amodel%3Afm%3AAlarm%3A213673 Severity: major Alarm Name: NspApplicationPodDown Alarm Type: communicationsAlarm Alarm ID: fdn:model:fm:Alarm:213673 Probable Cause: systemFailed Alarmed Object ID: fdn:app:server:cam-im-deployer-app-1676634176763-job-rr2sr:233.252.0.0 Alarmed Object Type: NmsSystem Alarmed Object Name: cam-im-deployer-app-1676634176763-job-rr2sr:233.252.0.0 Last Time Detected: 2023/02/17 11:46:04 159 UTC Is Service Affecting: false Site ID: cam-im-deployer-app-1676634176763-job-rr2sr:233.252.0.0 Site Name: cam-im-deployer-app-1676634176763-job-rr2sr:233.252.0.0 Implicitly Cleared: false Administrative State: unknown Source Type: nsp Source System: fdn:app:server Additional Text: null Custom Text: N/A

When the NSP has reached the configured maximum number of e-mails permitted in one hour, the following statement is added:

The configured maximum number of e-mail notifications has been reached for this e-mail notification filter. NSP will not send further notifications for up to one hour. Open the FM App to verify current alarm information.

When there are more than 10 new alarms to be included in the e-mail, the following statement is added:

A set of 10 or more alarms exist for this e-mail notification policy. This e-mail notification only displays 10 of the reported set. Open the FM App to verify all the current alarm information.