Unformatted Traps received; have MIB compiled

Hi everyone, I am fairly new to the configuration of OpenNMS so I hope this makes sense to everyone.

I am testing out Traps coming from an application server, whose MIBs I have loaded onto the OpenNMS MIB compiler. We are receiving the traps as unformatted despite this.

I was looking at documentation and some older similar issue reports from the issues.opennms.org website and I ran across dialogue saying that loading the MIB is not enough and that we needed to add the xml file, where the events are defined, in the <Include> section of the eventconf.xml file and restart the server for it to recognize it properly?

What we have done in the interim is under the event description follow the mask element description given by ONMS and used the id, generic and specific values shown below and edited the mask elements to match within the events configuration file

Event log:

This is the default event format used when an enterprise specific event (trap) is received for which no format has been configured (i.e. no event definition exists).
The total number of arguments received with the trap: 12.
They were:
.1.3.6.1.4.1.6102.1.1="PROGNOSIS" .1.3.6.1.4.1.6102.1.2.2="9" .1.3.6.1.4.1.6102.1.2.3="309677" .1.3.6.1.4.1.6102.1.2.4="Edge-SipIncReqsDropped" .1.3.6.1.4.1.6102.1.2.1="[Glowpoint] Edge Server:[\LYNCEDGE-2V-HRC] Issue resolved with incoming requests being dropped by the Edge Server" .1.3.6.1.4.1.6102.1.2.5="\LYNCEDGE-2V-HRC" .1.3.6.1.4.1.6102.1.2.27="****************************************************************LYNC **************************************************************** Edge-SipIncReqsDropped" .1.3.6.1.4.1.6102.1.2.26="" .1.3.6.1.4.1.6102.1.2.28="" .1.3.6.1.4.1.6102.1.2.29="" .1.3.6.1.4.1.6102.1.2.30="" .1.3.6.1.4.1.6102.1.2.31=""
Here is a "mask" element definition that matches this event, for use in event configuration files:
<mask>
  <maskelement>
    <mename>id</mename>
    <mevalue>.1.3.6.1.4.1</mevalue> <<<<<<<<<<<<<<<<<
  </maskelement>
  <maskelement>
    <mename>generic</mename>
    <mevalue>6</mevalue> <<<<<<<<<<<<<<<<<<<<
  </maskelement>
  <maskelement>
    <mename>specific</mename>
    <mevalue>6102</mevalue> <<<<<<<<<<<<<<<<<<<<<<
  </maskelement>
</mask>

Took mask elements above and edited event UEI (under Manage Events Configuration)

Updated Mask Elements:

Element Name     Element Values
ID                                .1.3.6.1.4.1.6102
Generic                     6
Specific                      12

To

Element Name     Element Values
ID                                .1.3.6.1.4.1
Generic                     6
Specific                      6102

Which seemed to work. Problem is, there are several different Trap even UEI all with different Generic and Specific numbers. Copying the same configs over for each doesn't sound like the correct way to fix this. Will updating the eventconf.xml file with the event definition resolve this?

Thank you,

Freddi

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot

_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss