Hi All,
Could any one explain me the difference between snmp agent and sub-agent.
Thanks in advance.
Regards,
Ravi
--
This SF.net email is sponsored by
Make an app they can't live without
Enter the BlackBerry Developer
Hi,
I followed the steps mentioned in the following website
(http://search.cpan.org/~hardaker/NetSNMP-TrapReceiver-5.0301/TrapReceiver.pm)
and configured snmptrapd.conf to register my perl module.
The module is called for every trap received but when the first trap
is received the formatting is n
> On Tue, 17 Aug 2010 10:36:29 -0400, Robert Story
> said:
RS> d'oh!
+1
--
Wes Hardaker
Please mail all replies to [email protected]
--
This SF.net email is sponsored by
Make an app they
On Tue, 17 Aug 2010 07:04:54 -0700 Wes wrote:
WH> Well, you didn't attach a patch. But I suspect I'm going to say +1 when
WH> I see it.
d'oh!
attached
# alternative: move to netsnmp_check_outstanding_agent_requests() [which
# is really about delayed instances] or run_alarms()
#
diff --git a/net-
SM> The SNMP v3 communication seems to be problem. For the first time
SM> devices are not responding and second time if I try again it is
SM> responding.
Which are you using Net-SNMP on: the agent side, the manager side or both?
SM> Should any major fixes are done in net snmp 5.5 regarding V3
SM
> On Tue, 17 Aug 2010 09:20:23 -0400, Robert Story
> said:
RS> In 5.6 I added an API for mib modules to signal that their
RS> persistent data had changed and that snmp_store should be
RS> called. But I only added the check in the agent_check_and_process,
RS> which snmpd doesn't actually
In 5.6 I added an API for mib modules to signal that their persistent data had
changed and that snmp_store should be called. But I only added the check in
the agent_check_and_process, which snmpd doesn't actually use. The attached
patch adds the call to receive, which is snmpd's main loop. An alte
Hello,
I am using netsnmp 5.4.1.
The SNMP v3 communication seems to be problem. For the first time devices are
not responding and second time if I try again it is responding.
Should any major fixes are done in net snmp 5.5 regarding V3 communication
regarding this problem.
What is best versio