[ First - *please* don't mail me privately, without copying
any responses to the mailing list. I don't have the time
or inclination to offer private, unpaid, SNMP consultancy.
Keep discussions to the list, where others can both learn
and offer advice. Thanks. ]
2009/8/27 shakeb ainul <[email protected]>:
> I had trapsink lines in my snmpd.conf file and commenting them out solved
> the issue.
>
> But i was wondering trapsink is used to send trap messages to a host, then
> how come it is making my server listen on ports other than 161.
The agent sets up an "SNMP session" for each trap destination.
This is a standard mechanism, used for all SNMP communication,
both notifications (traps and informs), and information retrieval
(GET* and SET). The library doesn't distinguish between sessions
used for acknowledged requests (GET*, SET and INFORM), and
those used for unacknowleged requests (TRAP and TRAP2).
For acknowleged requests, the session needs to be capable of receiving
the response PDU, and hence listens on the opened port.
That's what is happening here.
Dave
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
