ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Spectrum Alarm Notifier not processing email or tickets


Article ID: 198610


Updated On:


CA Spectrum CA eHealth


I have an alarm that I can see in the AlarmNotifier log file but it doesn't follow through to the ticketing. I have validated that the SANM filters are correct and that everything is correct for it to ticket.  Spectrum is processing it but the email and ticket for this one alarm is not working.


Bad Data in the mib of the device


Component : Spectrum Core / SpectroSERVER


Open the Notifier log file with Notepad++ and review the alarm detail.  

Notice the alarm detail has a bad value:

EventMessage:     Thu 27 Aug, 2020 - 08:38:51 - The eBGP session with peer has gone from established to active.  The LastError is . (event [0x00220013])
EventMessage:     Thu 27 Aug, 2020 - 08:57:47 - The eBGP session with peer has gone from established to active.  The LastError is . (event [0x00220013])

In this example, the device had a bad value in the bgpPeerLastError table.

This will need to be resolved at the device level, but to workaround this in Spectrum you can remove the varbind read.

For the above example, launch Event Configuration and filter for events 0x220013 and 0x220014 and remove this:

The LastError is {S 1}.

Save the Events. Copy them from the OneClick server $SPECROOT/custom/Events/CsEvFormat folder to the SS that is running AlarmNotifier and put them in that same folder.

Kill the AlarmNotifier so it restarts.

This will allow the email and ticketing to process the alarm.