Viewing all available alarms in Spectrum

[dscarlett]

Hi all,

Pretty new to using Spectrum so bare with me.

At the moment we have some critical events that generate alarms/autotickets when then are not needed and have some minor events that are required to alarm/autoticket and currently do not.

Is there any way we can get a report/or check all the alarms currently available on Spectrum so we can filter through and see what are required and what are not.

We are trying to move away from event type autoticketing to an alarm based policy if that makes sense.

We are currently using Spectrum 8.

Let me know if you need further info.

Thanks in advance

[Anon Anon]

I dn't think we can export alarms mapped to event considering data integrity of CA spectrum tool itslef.

U can either do it manually as it will be one time activity/generate detail alarm report for global collection and select complete retention period of reporting database.
It will give you alarm report which you can filter. find respective events in ECEditor.

Hope you find this workaround feasible.

[Anon Anon]

hi,

/opt/spectrum/vnmsh/connect

./show alarms that can show you all alarms

[Anon Anon]

Hi Mate,

We have 2 options here

1. In Spectrum 9.2 we have pcasue column in Event configuration editor. You can enable this and export all the alarm codes for respective events.
2. One more option is using find command from bash login

Something like this

Bash –login

find $SPECROOT/custom/Events $SPECROOT/SS/CsVendor -name EventDisp -exec egrep -e ' A *5' {} /dev/null \; >> test.txt

This optiin "5" in the command will export all the supressed alerts into test.txt file. Similarly 0 - Normal , 1 - Minor , 2 - Major , 3 - Critical , 4 - Maintenance.

HTH

kalyan

[Frank Tonjes]

You can enable/disable events and change their properties, by opening 'Tools->Utilities->Event Configuration'.

Here you can set criticality, as well as if you want any alarms to be generated. This might be a good place to start!

Regards,

Frank

[Rajesh Rajesh]

Hello Is there a way only to extract only the custom events from the list.

[Joseph Ackley]

• Log into OneClick
• Select Tools -> Utilities -> Event Configuration from the menu
• Right mouse click on any column header in the Navigation panel
• Display the following columns

Event Code
Author
Cause Code
Event Message

• At the bottom of the Navigation panel, enter "Customer" in the "Show" field
• Sort on the Cause Code column 
• Click on the Export icon and export to csv format

The events that have a value in the Cause Code column are the customized events that generate an alarm

Joe

[Joseph Ackley]

[Rajesh Rajesh]

Thank you Joe, I need the alarm criticality also. How to get them have any shortcut

Get Outlook for Android<https: aka.ms/aab9ysg="">

[Joseph Ackley]

Rejesh,

No shortcut for that that I am aware of.

You will need to check each individual event.

Joe

[Catalin Farcasanu]

You'll need to script your way around $SPECROOT/custom.

find . -type f -name EventDisp | xargs egrep " A "

would yield the custom events that have alarms associated.

---

0x06ec1001 E 20 A 2,0x06ec1001
0x06ec1002 E 20 A 2,0x06ec1002
0x06ec1004 E 20 A 2,0x06ec1004
0x06ec1006 E 20 A 2,0x06ec1006
0x06ec1008 E 20 A 2,0x06ec1008
0x06ec100a E 20 A 3,0x06ec100a
0x06ec100e E 20 A 3,0x06ec100e

---

1 is MINOR

2 is MAJOR

3 is CRITICAL

You'd have to grep your way around the files named "*Prob*US" under $SPEROOT/custom/Events/CsPCause and get the information from there.

Prob06ec100a_en_US;AX GDM MY S Q L NOT REACHABLE
Prob06ec1002_en_US;AX GDM TEST FAIL
Prob06ec1001_en_US;AX GDM SHUTDOWN
Prob06ec1006_en_US;AX GDM N B I DOWN
Prob06ec1004_en_US;AX GDM G U I DOWN
Prob06ec1008_en_US;AX GDM T R069 DOWN
Prob06ec100e_en_US;AX GDM REDIS NOT REACHABLE

------------------------------
Cătălin Fărcășanu
Senior Consultant
SolvIT Networks
------------------------------

[Joseph Ackley]

Catalin,

Nice script. I will use this in the future.

Thank you,

Joe

[Catalin Farcasanu]

This should extract all custom events that have associated custom alarms. 

for event in $(find  $SPECROOT/custom -type f -name EventDisp | xargs egrep " A " | gawk '{print $1}'); do

  id=$(echo $event | gawk -F"0x" '{print $2}');

  alarm=$(find $SPECROOT/custom -type f -name "Prob*${id}*" | xargs head -1);

  if [[ ${alarm} != "" ]]; then

  #alarm exists

  alarm_severity=$(find $SPECROOT/custom -type f -name EventDisp |xargs egrep $event |grep A |gawk -F" A " '{print $2}' | gawk -F"," '{print $1}');

  case ${alarm_severity} in

  1)

  severity="MINOR";;

  2)

  severity="MAJOR";;

  3)

  severity="CRITICAL";;

  4)

  severity="4";;

  5)

  severity="5";;

  esac

  echo -e "$event | $severity | $alarm" >> /tmp/alarms.txt

  fi

done

------------------------------
Cătălin Fărcășanu
Senior Consultant
SolvIT Networks
------------------------------

[Rajesh Rajesh]

Thank you Frac,

It was very helpful


--
Thanks & Regards | Rajesh | Consultant | ENTIIS Pte., Ltd. |
150, Kampong Ampat, #06-06A KA Center, Singapore 368324
Mobile: [phone] | Tel: [phone] | Fax: [phone] |
Email: [e-mail]<mailto:[e-mail]> | Website: www.entiis.com<http: www.entiis.com/=""> |