problems with traps

Frank Fock frank.fock____marconi.com
Tue Jul 18 12:07:53 CEST 2000


DavidGL wrote:
>         pdu.set_notify_enterprise((Oidx)"1.3.6.1.4.1.6517");
>         pdu.set_notify_id((Oidx)"1.3.6.1.4.1.6517.1.2.4.1.2");
> 
> 
>  But the received trap shows the following:
> 
>  "Enterprise Specific (1.3.6.1.4.1.6517.1.2.4.1.0.2) from..."
>  "Enterprise = 1.3.6.1.4.1.6517.1.2.4.1"
> 
>  So the enterprise specific notify_id has a '0' added,
>  and the enterprise_id has "1.2.4.1" added.
>  The varbind is ok.
> 

There is no problem ;-) It is working perfectly, because a SNMPv1
trap (that is what your are sending) cannot be of use the oid
you specified. As enterprise ID you should have used:

1.3.6.1.4.1.6517.1.2.4.1

and as notify id:

1.3.6.1.4.1.6517.1.2.4.1.0.2

then you will not see any differences between what you send
and what you get. If you send a notification (SMIv2 "trap")
you sould not set the enterprise id and you can choose an arbitrary
oid for the notification id. With traps this is different
they always have to be like:

<oid>.0.<trapnum>

where <oid> == <enterprise> and trapnum is a number between 1 and
2^32-1.

Please read the book "Understanding SNMP MIBs" by D.Perkins
for more details.

Best regards,
Frank



More information about the AGENTPP mailing list