Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Replacing the net-snmp 8072 identifier

11 views
Skip to first unread message

lanas

unread,
Dec 20, 2009, 11:00:16 AM12/20/09
to
Hello,

Is it possible to easily change the 8072 identifier when, for
instance, receiving an IF-MIB trap such as:

'SNMPv2-MIB::snmpTrapEnterprise.0 (1.3.6.1.6.3.1.1.4.3.0):
1.3.6.1.4.1.8072.3.2.10'.

I cannot try it at the moment (can try it tomorrow), but would this
be solved by what a previous poster reported in June, namely, to have
an entry in snmpd.conf like:

sysobjectid 1.3.6.1.4.1.5713.1.1.2.4

Would that effectively replace by 5713 all instances of 8072 in
any polling reply and traps ?

Thanks.

------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev
_______________________________________________
Net-snmp-users mailing list
Net-snm...@lists.sourceforge.net
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users

Thomas Anders

unread,
Dec 20, 2009, 6:00:18 PM12/20/09
to
lanas wrote:
> Is it possible to easily change the 8072 identifier when, for
> instance, receiving an IF-MIB trap such as:
>
> 'SNMPv2-MIB::snmpTrapEnterprise.0 (1.3.6.1.6.3.1.1.4.3.0):
> 1.3.6.1.4.1.8072.3.2.10'.

Check the (help output for the) configure options "--with-enterprise-oid" and "--with-enterprise-notification-oid" when building net-snmp from source.


+Thomas

Dave Shield

unread,
Dec 23, 2009, 4:38:31 AM12/23/09
to
2009/12/22 lanas <la...@securenet.net>:
> Would an IF-MIB trap be considered entreprise specific ?

Enterprise-specific traps cover everything bar the six "standard"
traps from SNMPv1 (coldStart, warmStart, ifUp, ifDown, and
two I can't remember offhand).

Under SNMPv1, every other trap uses 'enterprise(6)' for the
generic trap field, and another (enterprise-specific) integer
for the specific trap field. the enterprise OID is used to
identify how to interpret this integer.

This is less relevant for SNMPv2 notifications (i.e SNMPv2c/v3)
where the trap is always identified by a full OID.

Dave

0 new messages