Ken,
I had a conversation with support long back and if I remember it right Chassis
down and Blade status are defined in different cisco mibs, that causes multiple
alarms and enable_correlation will not work.
There are gotcha in any approach you take to filter out these
alerts/notification.
1. Suppose you use SANM not to notify you about Blade Status unknown
alert, in case of an actual alert (someone pulling out a blade) you will miss
notification.
2. If you play with Events as below, (you will be able to reduce alarm
and notification), however there could be a situation (based on device/model
condition) where an actual blade alarm might not be generated, however the
event will be logged.
I did open an enhancement request for engineering to see if they can do a
better correlation for these alarms, however I am not the owner of the ticket
so will not be able to update you the status.
# Chassis down (0x10f69) normally generates a Blade Status event 0x10f71
# If the status of the device is already 3 (critical), just generate a new
event 0xfff00006 and log it
0x00010f69 E 20 A 3,0x00010f69 R CA.EventCondition, "{a 0x1000a} == {I 3}" ,
"0xfff00006 -:-","default" , "0x00010f71"
0xfff00006 E 10
# The 0x10f71 event is the Blade Status event.
#
# 1. Copied event 0x10f71 to two new events; 0xfff00003 and 0xfff00004
# 2. Removed the alarming for event 0x10f71 and 0xfff0003
# 3. Created an Event Condition rule on the 0x10f71 event to check the value of
the Condition attribute.
# If the value of the Condition attribute (0x1000a) on model is 5 (suppressed)
or 3 (critical)
# generate event 0xfff00003 else
# the default is to generate event 0xfff00004 which asserts the major alarm.
0x10f71 E 20 R CA.EventCondition, "{a 0x1000a} == {I 5} || {a 0x1000a} == {I
3}" , "0xfff00003 -:-","default" , "0xfff00004 -:-"
0xfff00003 E 20
0xfff00004 E 20 A 2,0x00010f71
Saurabh Bohra
260-766-0842
From: Pfleger, Jim [mailto:[email protected]]
Sent: Friday, October 28, 2011 12:24 PM
To: spectrum
Subject: Re: [spectrum] Alarm Notifier
If you're using SANM to simply filter out the cause codes you don't want, that
should work fine. However I would caution that, if you're looking at the cause
count (0x12a07) in your notifier scripts to determine if the alarm is a symptom
or root cause, this will not work consistently. There is a race condition in
the SpectroServer between the threads that mark alarms as symptoms and the
threads that hand alarms to Alarm Notifier, which means that symptoms may not
be marked as such when your Notifier script is called. CA has accepted this as
an issue with an expected fix in 9.5.
HTH,
Jim
--
JIM PFLEGER | Application Architect | Insight | insight.com
t. 480.889.9680 f. 480.889.9599 [email protected]
On 10/28/11 12:07 AM, "Kenneth Kirchner" <[email protected]> wrote:
You are correct. Someone off-list put me on the right path (SANM) and that
works perfectly.
Many thanks.
-Ken
On Oct 27, 2011, at 10:47 PM, Cristi Mitrana wrote:
>
>
> ----- Original Message -----
>> Can someone tell me how to make the alarm notifier more selective in
>> what it reports? For example, in my lab if I reboot a device I get
>> 3 different alarms (3 calls to SetScript) for STOPPED RESPONDING TO
>> POLLS, CHASSIS DOWN, and BLADE STATUS UNKNOWN.
>>
>> Only 1 alarm shows up in my alarm table, namely CHASSIS DOWN. I
>> would like AlarmNotifier to suppress those extraneous alarms if
>> possible. I have played with the ENABLE_CORRELATION and
>> SHOW_ONLY_ORIGINATING_EVENT options, but I usually don't get any
>> alarm at all with those enabled.
>> [...]
>
> Instead of using the Notifier to do filtering, I would do the filtering using
> SANM to supress the extraneous alarms. The SetScript would only receive the
> alarm you need to send notification for.
>
> regards,
> --
> Cristi Mitrana
>
> ---
> To unsubscribe from spectrum, send email to [email protected] with the body:
> unsubscribe spectrum [email protected]
---
To unsubscribe from spectrum, send email to [email protected] with the body:
unsubscribe spectrum [email protected]
* --To unsubscribe from spectrum, send email to
[email protected]<mailto:[email protected]> with the body: unsubscribe spectrum
[email protected]<mailto:[email protected]>
________________________________
Please consider the environment before printing this e-mail.
---
To unsubscribe from spectrum, send email to [email protected] with the body:
unsubscribe spectrum [email protected]
