T.R | Title | User | Personal Name | Date | Lines |
---|
285.1 | | SMURF::DANIELE | | Tue Mar 18 1997 17:33 | 21 |
| I may not understand your question... but SNMP agents aren't
supposed to do anything with RECEIVED traps (other than silently
discard them, and for SNMPv1, increment a counter in the snmp MIB).
SNMP agents sometimes SEND traps. Typically you configure an agent
to know where to send traps. Then some software (like NetView) running on
those systems, does something with the traps.
eSNMP provides a way for subagents to indicate to the master agent
that a trap should be sent. The master agent (snmpd) sends them according
to its configuration file. See the doc for esnmp_trap() and the snmpd
man page.
So, if you are sending a trap to a Digital UNIX system, the (extensible)
agent running there isn't even going to see them. You can run
/usr/sbin/snmp_traprcv, which is just a program that listens on UDP 162 and
dumps out what it receives, to see if traps are arriving at the system...
Hope this helps. If I'm not understanding your question please let me know.
Mike
|
285.2 | more infos | MLNCSC::VOCI | | Wed Mar 19 1997 10:45 | 17 |
| Hello Mike,
I've talked to the customer and he is developping a SNMP agent that sends a trap
when a particular event happens. They are using the esnmp_trap().
He has put under trace /usr/sbin/snmpd, but the trap is never received by the
daemon.
He has also tried using netview on the same machine but it doesn't receive any
trap.
So, if my uderstanding is correct, the snmp agent never receives traps, but it
sends them to the snmpd (or it tells with esnmp_trap () to send a trap); but
where do I associate the program that must react to the trap (for example
printing an allarm message on the console?
Forgive my ignorance.
Thanks,
Gea
|
285.3 | docs? | MLNCSC::VOCI | | Wed Mar 19 1997 11:55 | 21 |
| Hello,
I'm trying to use the chess example and I wanted to get from the agent
the number of registered games.
I went through the man page and the rfcs and decided that the
snmp_request was the right command.
I ran chess_mib -trace on one window and issued the command
/usr/sbin/snmp_request opale chess get 1.3.6.1.4.1.36.2.15.2.99.3
/usr/sbin/snmp_request: no response - try again.
I tried the following agent name with no success: chess_mib,
chess_subtree
In output of the trace I see
RESPONSE to REGISTRATION of 'chess': OK
Is there any white paper for snmp beginners ?
Thanks,
Gea
|
285.4 | | SMURF::DANIELE | | Wed Mar 19 1997 16:22 | 23 |
| >I've talked to the customer and he is developping a SNMP agent that sends a trap
>when a particular event happens. They are using the esnmp_trap().
>He has put under trace /usr/sbin/snmpd, but the trap is never received by the
>daemon.
>He has also tried using netview on the same machine but it doesn't receive any
>trap.
when a subagent calls esnmp_trap(), libesnmp.so communicates w/
snmpd. you probably won't see this in any trace (since it doesn't
use TCP/IP).
you're probably not seeing the trap go anywhere because snmpd
isn't configured to send them. the default snmpd.conf does not
contain any entries that cause traps to be sent, you need to add them.
see the snmpd man page.
if you edit snmpd.conf and have traps sent to a Digital UNIX system,
you can display them on that system by running /usr/sbin/snmp_traprcv.
I don't know how to configure NetView to display/do something with
traps.
Mike
|
285.5 | | SMURF::DANIELE | | Wed Mar 19 1997 16:27 | 22 |
| re .3:
> /usr/sbin/snmp_request opale chess get 1.3.6.1.4.1.36.2.15.2.99.3
> /usr/sbin/snmp_request: no response - try again.
> I tried the following agent name with no success: chess_mib,
> chess_subtree
the second command line argument is a community name, not the name
of the subagent or of a MIB. community names are how SNMP access control
is done.
again, see snmpd.conf for how to configure community names.
by default, snmpd.conf permits read access to the world using the
community name "public". so try that and you'll probably see something :-)
> Is there any white paper for snmp beginners ?
Not really. eSNMP for Digital UNIX is intended for folks who are
knowledgable in SNMP and want to develop subagents.
Mike
|