Re: Unformatted Traps received; have MIB compiled

Ok so it seems like ONMS is reading the traps incorrectly or the MIB event definitions incorrectly.

The traps come in as

Received unformatted enterprise event (enterprise:.1.3.6.1.4.1 generic:6 specific:6102).
12 args:
.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="309544"
.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-1V-HRC] Issue resolved with incoming requests being dropped by the Edge Server" .1.3.6.1.4.1.6102.1.2.5="\LYNCEDGE-1V-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 the wireshark showing the OID defining the enterprise and the events which is reflected in the MIB events

[cid:[email protected]]

Which are also reflected in the MIB Defintions

-- MIB Categories
--
--      The Integrated Research Enterprise number is 6102.
--      The ASN.1 prefix to, and including the Integrated Research Enterprise is:
--           1.3.6.1.4.1.6102

    integratedResearch                     OBJECT IDENTIFIER ::= { enterprises 6102 }

-- MIB Groups under integratedResearch enterprise

    irPROGNOSIS       OBJECT IDENTIFIER ::= { integratedResearch  1 }

--      irPROGNOSIS Group              (1.3.6.1.4.1.6102.1)
--       irThresholdTrap Group         (1.3.6.1.4.1.6102.1.2)

--
-- Object Definitions for the Trap MIB

And in the Event files definitions that were generated from the MIB however, the mask elements in the Event file definitions are as such:

Id = .1.3.6.1.4.1.6102
Generic = 6
Specific = 2

These are all different for each even UEI

The only thing we have done for the time being is edit the mask elements to match the incoming event ID which I guess is the fix for now, but any insight here is appreciated!

Id = .1.3.6.1.4.1
Generic = 6
Specific = 6102


Thank you,

Freddi Guerrero
[New Glowpoint Logo]<http://www.glowpoint.com/>
video: [email protected]<mailto:[email protected]>

From: Freddi Guerrero [mailto:[email protected]]
Sent: Tuesday, August 07, 2018 6:22 AM
To: General OpenNMS Discussion <[email protected]>
Subject: Re: [opennms-discuss] Unformatted Traps received; have MIB compiled

Ok, thanks for clearing that up Michael. Looks like everything is the way its supposed to be in OpenNMS. Ill keep digging.

Thank you,
Freddi Guerrero
Sent via Outlook Mobile<https://aka.ms/blhgte>

________________________________
From: Seibold, Michael <[email protected]<mailto:[email protected]>>
Sent: Tuesday, August 7, 2018 1:30:26 AM
To: General OpenNMS Discussion
Subject: Re: [opennms-discuss] Unformatted Traps received; have MIB compiled

Hi Freddi,


>  I finally got root access

If you use the GUI you can compile the mibs and generate the events without having root access


>  One interesting part is that I am not seeing an <events> open tab; only the </events> closing tab on the bottom, anyone see this before?

The beginning of this part is the keyword "events" in the first line, this definition get's closed in the last line:

<events xmlns="http://xmlns.opennms.org/xsd/eventconf">
...
</events>

-Michael

------------------------------------------------------------------------------
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