Prognosis 10.3 - flood of traps being cut for the same

[Anon]

Welcome All,
this is my first post on this forum and Im quite newbie on Prognosis world as well.
I've observerd that Prognosis generates bunch of similar traps for the same problem. (Avaya PBX only)
Im looking on EMC Smarts VoIP collector logs where I can see:

Processing PMT-AVA-AVDS1AVA-001===========
pm-trap-processing@3434109248: [194.41.72.23]Could not find DS1Service for \M1GBRDC-SVX00-S8730 boardNumber=T08257 ServiceName=SVC-10.154.58.10/T08257
pm-trap-processing@3434109248: [194.41.72.23]October 21, 2015 7:06:13 AM GMT+00:00 pm-trap-processing@3434109248: PROCESS_DS1_SERVICE - DS1 Service object is Null!!
pm-trap-processing@3434109248: [194.41.72.23]=========== Processed Trap: #1429458 PMT-AVA-AVDS1AVA-001===========

All these traps are for the same only difference is a PBX and D or T card name.

Details of the traps:
====== Trap Header ======
TIMESTAMP: 29387
IPADDRESS: 194.41.72.23
ENTERPRISE: .1.3.6.1.4.1.6102
GENERIC: 6
SPECIFIC: 13
==== VARBINDS: [Index]->[oid]->[varbind] ====
varbind[0]=.1.3.6.1.4.1.6102.1.1=PROGNOSIS
varbind[1]=.1.3.6.1.4.1.6102.1.2.2=4
varbind[2]=.1.3.6.1.4.1.6102.1.2.3=342462
varbind[3]=.1.3.6.1.4.1.6102.1.2.4=PMT-AVA-AVDS1AVA-001
varbind[4]=.1.3.6.1.4.1.6102.1.2.1=
varbind[5]=.1.3.6.1.4.1.6102.1.2.5=\M1GBRDC-SVX00-S8730
varbind[6]=.1.3.6.1.4.1.6102.1.2.6=AVDS1AVA.TRNKSDN
varbind[7]=.1.3.6.1.4.1.6102.1.2.7=0
varbind[8]=.1.3.6.1.4.1.6102.1.2.8=AVDS1AVA.TRNKSTOT
varbind[9]=.1.3.6.1.4.1.6102.1.2.9=7
varbind[10]=.1.3.6.1.4.1.6102.1.2.10=AVDS1AVA.TRNKSACT
varbind[11]=.1.3.6.1.4.1.6102.1.2.11=0
varbind[12]=.1.3.6.1.4.1.6102.1.2.12=AVDS1AVA.BRDNUM
varbind[13]=.1.3.6.1.4.1.6102.1.2.13=T08257
varbind[14]=.1.3.6.1.4.1.6102.1.2.27=EMEA
varbind[15]=.1.3.6.1.4.1.6102.1.2.26=A trigger has occurred for the following Board:


Looks like the same bunch of traps (in my case >1000) came at one shoot every 5 mminutes.

What I checked these are not regular alarms as I cannot see configured treshold for that alerts.

Any hint how to determine root cause of this events? ( it concerns to Avaya PBX only).
To me it looks like Prognosis cannot obtain data for object - as each of this traps keeps below message:

"Boards Configured in Gateway
No information was available for AvayaMediaGatewayMediaModules. The query was successful, but no rows were returned."

[GeraldC]

Hi There

Welcome to the forum! It could be. I guess when Prognosis received null data from the Avaya CM for DS1 service, it set the list of Trunk Boards to all down status triggering so many SNMP Trap alerts.

Perhaps first check if the Avaya CM login ID that Prognosis authenticates to the CM as, has the correct permissions to retrieve the data it requires.
Here's the Help location detailing the required permissions:
Product Guides > Prognosis for Unified Communications > Avaya Aura Communication Manager > Configuration > Avaya Setup > Configure SAT User Profile (CM 4+)
Product Guides > Prognosis for Unified Communications > Avaya Aura Communication Manager > Configuration > Avaya Setup > Create Login Account (CM 4+)

Otherwise, you could open a case with Support, and include a new IRFAX that they can use to see if they can identify the source threshold and give you suggestions to try if there are ways to refine it. Those alerts do not come from the default out-of-box threshold Avaya_Alerts. Perhaps it is something some one created or that was carried over from a previous version if this was an upgrade.

HTH