Re: Listening the snmptrapd

2008/6/25 Murilo Fujita <murilofujita@yahoo.com.br>:
> What machine should listen the traps to receive the traps?
> NMS or the agent?

Traps will be received by a NMS, not an agent.
They will often be sent *by* an agent.


> I follow the example:
>
> snmptrap -v 1 -c public host TRAP-TEST-MIB::demotraps localhost 6 17 '' \
> SNMPv2-MIB::sysLocation.0 s "Just here"

Then you need a trap receiver (e.g. snmptrapd) running on the machine 'host'


>
> I type changing the community name in the agent:
> C:> snmptrap -v 1 -c fujitaro fujita:162 .1.3.6.1.6.3.1.1.5.3 fujita:162 2 0


The agent is not relevant here.

Dave

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
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/...net-snmp-users

> From: net-snmp-users-bounces@lists.sourceforge.net
> [mailto:net-snmp-users-bounces@lists.sourceforge.net] On
> Behalf Of Dave Shield
> Sent: Wednesday, June 25, 2008 7:09 AM

> 2008/6/25 Murilo Fujita <murilofujita@yahoo.com.br>:
> > What machine should listen the traps to receive the traps?
> > NMS or the agent?
>
> Traps will be received by a NMS, not an agent.
> They will often be sent *by* an agent.

I am obligated to throw in my two bits here. The original(v1) SNMP specifications were written in terms of manager and managed systems, i.e. NMS and agents. The new (v3) SNMP specifications, however, use very carefully constructed language which speaks of "command generator applications", "notification receiver applications", etc. There are a number of implications of this change. Applications which only generate notifications, such as snmptrap, are now covered by the specs, which they previously were not. It is also legitimate, some say intended, to perform command generation, command response, notification generation, notifcation reception, and notification response all on the same UDP port!

To answer the original question in the new terms: any SNMP engine may receive notifications, provided, of course, that it can receive notifications. Confusing, but liberating.


HTH,

Mike

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
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/...net-snmp-users