On 04/01/2008, Mike Ayers <[EMAIL PROTECTED]> wrote:
>>> Note that this *notification* can not be converted
>>> to v1 format.
>> That's not actually true.
>> The names aren't important, but you should always define SMIv2
>> notifications with '0' as the penultimate subidentifier.
>> This allows SNMPv2->SNMPv1->SNMPv2 conversions to work cleanly.
>
> Hmmm... I thought the '0' was required fo5r the conversion to work at
> all..?
Nope.
See RFC 2576, section 3.2, step (1), second bullet:
- If the SNMPv2 snmpTrapOID parameter is not one of the standard
traps as defined in RFC1907 [12], then the SNMPv1 enterprise
parameter SHALL be determined from the SNMPv2 snmpTrapOID
parameter as follows:
- If the next-to-last sub-identifier of the snmpTrapOID is
zero, then the SNMPv1 enterprise SHALL be the SNMPv2
snmpTrapOID with the last 2 sub-identifiers removed,
otherwise
- If the next-to-last sub-identifier of the snmpTrapOID is
non-zero, then the SNMPv1 enterprise SHALL be the SNMPv2
snmpTrapOID with the last sub-identifier removed.
That second sub-bullet covers Wendy's situation.
However section 3.1, step (2):
(2) If the SNMPv1 generic-trap parameter is 'enterpriseSpecific(6)',
the SNMPv2 snmpTrapOID parameter SHALL be the concatentation of
the SNMPv1 enterprise parameter and two additional sub-
identifiers, '0', and the SNMPv1 specific-trap parameter.
will insert that '0' subidentifier when converting back the other way
(hence breaking the conversion symmetry).
Dave
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
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
