SANM Filters Failing

Products

• CA Spectrum
• DX NetOps

Issue/Introduction

We have an Application/Policy for sending emails, it always worked fine, however,  last week we realized issues related to filters. I enabled SANM debug and found out below failed messages into logs:

FILTER 8 FAILED

 

Environment

Release : 21.2

Component : Spectrum Applications

Cause

The "FILTER # FAILED" in the trace log file just means that an alarm has not passed a policy and the notification is NOT sent to AlarmNotifier.

The following messages were found in the $SPECROOT/lib/SDPM/processd_log file:

Apr 11 17:19:25 The required field <PARTNAME> is missing from /ca/SPECTRUM/lib/SDPM/partslist//ServiceNotifier.idb install ticket. 

Apr 11 17:19:25 The required field <PARTNAME> is missing from /ca/SPECTRUM/lib/SDPM/partslist//ServiceNotifierTST.idb install ticket. 

Apr 11 17:19:25 The required field <PARTNAME> is missing from /ca/SPECTRUM/lib/SDPM/partslist//ServiceNotifierTrigger.idb install ticket. 

The PARTNAME in the *.idb files is not in the upper case.

Resolution

Please fix the typos in the *.idb files.

In the $SPECROOT/lib/SDPM/partslist/SERVICENOTIFIER.idb file:
# Processd Install Ticket for ServiceNotifier
PARTNAME;ServiceNotifier; (should be: SERVICENOTIFIER)

In the $SPECROOT/lib/SDPM/partslist/SERVICENOTIFIERTST.idb file:
# Processd Install Ticket for ServiceNotifierTST
PARTNAME;ServiceNotifierTST; (should be: SERVICENOTIFIERTST)

In the $SPECROOT/lib/SDPM/partslist/SERVICENOTIFIERTRIGGER.idb file:
# Processd Install Ticket for ServiceNotifierTrigger
PARTNAME;ServiceNotifierTrigger; (should be: SERVICENOTIFIERTRIGGER)

After the changes, you will need to restart the Spectrum Process Daemon. ($SPECROOT/lib/SDPM/processd --restart). Then review the new $SPECROOT/lib/SDPM/processd_log file.

You may also need to cycle your custom Notifier processes.

Also, cycle the LocServer process on all landscapes.

Additional Information

https://techdocs.broadcom.com/us/en/ca-enterprise-software/it-operations-management/spectrum/10-4/managing-client-applications/spectrum-alarm-notification-manager-sanm/monitoring-sanm-processes/tracing-policies.html

Tracing Policies

 

Contents

 

• The Summary Trace File
• The Detailed Trace File

To collect information about how a policy is working for a SANM-enabled application, at application startup you can enable the creation of a detailed or summary trace file for that application.

• Detailed trace file

  : Indicates the filters in a policy alarm that did not match when they were evaluated against that policy.
• Summary trace file

  : Indicates the time when an alarm notification is passed to the associated application when that application is started. A summary trace file does not include information about alarms that do not meet the criteria that are specified in a policy.

Use a record of policy-based actions by SANM as a decision-making tool. The results may confirm that you have the correct policy in place for an application, or they may compel you to refine your policy. For example, you can discover that you are inadvertently excluding alarms that should be passed to an application.

The Summary Trace File

The summary trace file includes a summary of all alarm notifications (set, cleared, updated) sent to the application, as follows:

05/24/2000 15:48:44 SANM Trace Entry 1 Notification sent to AlarmNotifier for Alarm 52 set on landscape 0x540000 05/24/2000 15:48:44 SANM Trace Entry 2 Notification sent to AlarmNotifier for Alarm 21 updated on landscape 0x540000 05/24/2000 15:48:44 SANM Trace Entry 3 Notification sent to AlarmNotifier for Alarm 26 cleared on landscape 0x540000

The summary trace file does not indicate the alarms that failed the policy.

The Detailed Trace File

A detailed trace file includes entries for alarms that meet and that do not meet the criteria of a policy. An alarm entry includes the alarm attribute values, which that are compared to the filter parameter values. An arrow symbol under MATCH between ALARM VALUES and FILTER VALUES indicates a match. The arrow is absent if the values do not match.

The following is an example of a trace file that indicates that an alarm passed a policy:

The following is an example of a trace file that indicates that an alarm failed a policy: