Re: SNMPv1 traps in SMIv2 MIB (TRAP-TYPE to NOTIFICATION-TYPE)

eric.voisard@xxxxxxxxx wrote:

I'm trying to make an SMIv2 MIB for an SNMPv1 agent, therefore I must
translate the TRAP-TYPE to NOTIFICATION-TYPE.
I used the rule in RFC2576: take the SNMPv1 trap's ENTERPRISE OID,
append a .0 and then the enterprise specific trap number.

In my case, the SNMPv1 agent's ENTREPRISE parameter is not simply the
enterprise OID but it has a .2 appended (afaik, it's allowed). A
simplified SMIv1 MIB would look something like:

[...]

This translates back to SMIv1 as follows (smidump output):

myTraps OBJECT IDENTIFIER
::= { my 2 }

myTrapPrefix OBJECT IDENTIFIER
::= { myTraps 0 }

myTrap8 TRAP-TYPE
ENTERPRISE myTraps
-- STATUS mandatory
DESCRIPTION
"Test trap, specific number 8"
::= 8

myTrap9 TRAP-TYPE
ENTERPRISE myTraps
-- STATUS mandatory
DESCRIPTION
"Test trap, specific number 9"
::= 9

I guess this is indeed what you wanted.

I've loaded this MIB onto two different SNMP Managers (Network
Instruments' Observer and MG Soft's MIB Browser) and then I sent fake
SBMPv1 traps identical to the real agent's ones. While both managers
indeed received the traps, they have been unable to translate them. I
don't know if it's due to an error in my MIB or if the managers are
simply not capable of doing the translation...

Not sure what you mean by "translate them". The MIB module looks fine
as far as I can tell.

/js

--
Juergen Schoenwaelder Jacobs University Bremen gGmbH
Phone: +49 421 200 3587 Campus Ring 1, 28759 Bremen, Germany
Fax: +49 421 200 3103 <http://www.jacobs-university.de/>
.

Relevant Pages