Hi Dave:
Yes,I know what your meaning is.
But I donot know how to implement the trap in the MIB file.one hand,the trap is
a part of the MIB file,and traps have their own OIDs and related some specific
OBJECT-TYPE value(s),so we can know what happened and stand for when the trap
sent;on the other hand,how to define the trap can make the walk routine donot
walk it?
that is to say:I want to keep traps,I want the trap has its meaning when it
send(mapping some OBJECT-TYPE value).
Yes,I am a CS student.But you know it,Dave,it is too hard to understand it
deeply to me,so many RFCs,definations.The SNMP are worked by IT gurus more than
ten years,much less my poor english.
All I need is some prototype for my reference,so I can imitate,modify,implement
in my project.(I know it is hard to find one,they are all difference.)
I believe I can deal with this,and I will share all my work with the new
comers.That is my way of thanking you for given me so many help!
I work on it now.
Alex
------------------ Original ------------------
From: "Dave Shield"<d.t.shi...@liverpool.ac.uk>;
Date: Fri, Jan 22, 2010 07:15 PM
To: "Alexander King"<chenyapu1...@qq.com>;
Cc: "net-snmp-users"<net-snmp-users@lists.sourceforge.net>;
Subject: Re: when snmpwalk query my private trap OID the snmpd routine auto
termination
2010/1/22 Alexander King <chenyapu1...@qq.com>:
> when the MG-soft query my private entry
> .1.3.6.1.4.1.30901.2090.7000.2.1.3.0 the snmpd routine auto termination
> itself
>
> the OID .1.3.6.1.4.1.30901.2090.7000.2.1.3.0 is trapTestingTrapOne.0 in the
> trap testing MIB file.
> trapTestingTrapOne OBJECT IDENTIFIER ::= { systeminfoController 3 }
Given that trapTestingTrapOne is an OBJECT IDENTIFIER
(i.e. a named OID), it doesn't actually have any management
information associated with it. So a GET* request for this OID
would always fail.
You can only issue requests for OBJECT-TYPE defined
OIDs.
And a management client application wouldn't be issuing
requests for a notification either - these are inherently
agent-initiated, not manager initiated OIDs.
> Did I define the wrong trap structure?
I don't think it's anything to do with the MIB definitions.
The problem will lie within the code that you've written
to implement your MIB module.
Not least the fact that it may be trying to implement
something that doesn't actually exist.
I suggest you review and consolidate your understanding
of how SNMP works, before trying to implement new MIBs.
Don't run before you can walk......
Dave
------------------------------------------------------------------------------
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
_______________________________________________
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
------------------------------------------------------------------------------
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
_______________________________________________
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
