Hi,
I am sending SNMPv3 queries to two
different net-snmp agents one running on 161 and the other on 2050 port number
through vc++.The first time querying is fine and I am getting all the values
correctly..but during the second time requests seem to go to only one snmp
[EMAIL PROTECTED] wrote:
I am sending SNMPv3 queries to two different net-snmp agents one
running on 161 and the other on 2050 port number through vc++.The first
time querying is fine and I am getting all the values correctly..but
during the second time requests seem to go to only one
Thomas,
Thank you for your response. I am willing to help resolving the issue. Let
me know what can I do to help.
Sergey
Thomas Anders
[EMAIL
Dave Shield wrote:
Can you try the following patch, and see if it helps.
--- agent_registry.c.cln2006-02-15 13:25:22.603744208 +
+++ agent_registry.c2006-02-15 13:27:11.136244760 +
@@ -587,7 +587,8 @@
DEBUGMSGTL((register_mib, registering \%s\ at , moduleName));
Apologizes if this is a stupid question, but using Net SNMP
is there a clean way to split the OID into its various indices?
For example:
.1.3.6.1.2.1.16.14.2.1.3.1.0.1.4.172.20.110.167
hlHostControlIndex 0
nlHostTimeMark 1
protocolDirLocalIndex 4
nlHostAddr 172.20.110.167
All,
I have been atempting to use the event mib to simply watch a process
and send a trap to OpenNMS when the process fails. here is my config,
i am running net-snmp 5.2.2, I compiled 5.3 but was recieving mte
trigger failed errors in the log.. I am running on SUSE SLES9SP3.
syslocation Server
all. I have compiled and installed net-snmp 5.3, and configured with
the follwoing for testing:
syslocation Server Room
syscontact Sysadmin ([EMAIL PROTECTED])
createUser_internal MD5 the first sign of madness
iquerySecName _internal
rouser_internal
defaultMonitors yes
proc
Robert Reilly wrote:
all. I have compiled and installed net-snmp 5.3, and configured with
the follwoing for testing:
Can you please retry with 5.3.1.pre3 or later?
+Thomas
--
Thomas Anders (thomas.anders at blue-cable.de)
___
Net-snmp-users
