> From: Fulko Hew [mailto:fulko....@gmail.com]
> Sent: Friday, January 29, 2010 11:29 AM
> MIB definition
> --------------
>
> In the case of MIB definition, we want to discriminate between SMIv1
> and SMIv2.
No, we distinguish (and the agent discriminates) SNMPv1 traps (which
are notifications) and SNMPv2 notifications (which are also used in SNMPv3).
SNMPv1 traps can be, and usually are, written in SMIv2.
> When rewriting an SMIv1 MIB into SMIv2, the OID is defined with
> an intermediate .0 between the enterprise value and the trap ID.
The v2 notification has only an OID, not
enterprise-id/generic-trap/specific-trap. However, if the second last
identifier of that OID is 0, then the notification can be converted to, and
received as, a v1 trap with an enterprise-id of all but the last two
identifiers, a generog-trap of 6, and a specific-trap of the final identifier.
The reverse transform is also applicable, and thus, such notifications "roud
trip".
> When writing a SMIv3 NOTIFICATION_TYPE from scratch, (not when up-
> converting)
> you _do not_ include the intermediate .0 ???
I don't remember SMIv1, and I'm happier that way. You would be, too.
:-)
> Ie. the intermediate 0 indicates a translated definition.
*translatable*
HTH,
Mike
------------------------------------------------------------------------------
The Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers and the best network in the business
Choose flexible plans and management services without long-term contracts
Personal 24x7 support from experience hosting pros just a phone call away.
http://p.sf.net/sfu/theplanet-com
_______________________________________________
Net-snmp-users mailing list
Net-snmp-users@lists.sourceforge.net
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users
