I have some question about the code at the end of this function:
1.) Why is the send_trap_to_sess() called for each entry at sinks
without check the snmpNotifyFilter?
2.) And why is the snmpNotifyFilter called via callback 2 times (with
v1 and v2 trap pdu)?
3.) Why is the callback called too
You should start by reading our tutorials at:
http://www.net-snmp.org/tutorials
They talk about how to use our command line tools like "snmpget" to
query hosts.
--
Wes Hardaker
Cobham Analytic Solutions
--
Nokia and
On 20 October 2010 11:20, Queenie de Melo wrote:
> We know that, the SNMP agent(Server) listens on port 161 for SNMP GET/SET
> requests from the SNMP Manager (Client). The SNMP Agent then sends back a
> response (GET-RESPONSE) to the SNMP Manager. This will be received by the
> SNMP Manager on wh
Thanks Dave, for a wonderful explanation
Another question struck my mind...
We know that, the SNMP agent(Server) listens on port 161 for SNMP GET/SET
requests from the SNMP Manager (Client). The SNMP Agent then sends back a
response (GET-RESPONSE) to the SNMP Manager. This will be received by the
On 19 October 2010 19:00, Kathy McLeod wrote:
> I asked this awhile back but didn't get a reply - several questions in that
> note so you may have missed it.
Well, speaking personally - the couple of months just gone are
probably the busiest part of the academic year for me, so I've
been concentr
On 19 October 2010 16:59, Ray Van Dolson wrote:
> Running Net-SNMP 5.3.2.2 on RHEL 5.5 (POWER). The machine is also
> running Red Hat Cluster services and a GFS2 filesystem.
That's a fairly old version of the agent.
Would it be possible to try compiling and running a more recent release
on one o
