Hi Dave, Please find my answers below. On Thu, May 13, 2010 at 1:20 PM, Dave Shield <d.t.shi...@liverpool.ac.uk> wrote: > On 13 May 2010 05:27, A Singh <asingh.t...@gmail.com> wrote: >>> What happens if you compare the response times of >>> >>> snmpget ... hrMemorySize.0 >>> and >>> snmpgetnext .... hrMemorySize >> >> Response time of both OIDs is immediate. > > Hmmm.... that would tend to indicate the delay is associated with > traversing the end of the hrSystem group, rather than hrMemorySize itself. > > To confirm this, please try the following queries, > and report back as to the presence or absence of a delay: > > - snmpgetnext hrSystemMaxProcesses.0 ; snmpgetnext hrSystemMaxProcesses.0 > (i.e. run the same query twice in rapid succession - does the delay > appear both times?) Yes, delay is the same for both queries.
16:34:34.145799 IP 10.0.13.0.52189 > 10.0.6.103.161: GetNextRequest(29) .1.3.6.1.2.1.25.1.7.0 16:34:40.151953 IP 10.0.6.103.161 > 10.0.13.0.52189: GetResponse(32) .1.3.6.1.2.1.25.2.2.0=897832 16:34:40.315343 IP 10.0.13.0.37227 > 10.0.6.103.161: GetNextRequest(29) .1.3.6.1.2.1.25.1.7.0 16:34:46.321096 IP 10.0.6.103.161 > 10.0.13.0.37227: GetResponse(32) .1.3.6.1.2.1.25.2.2.0=897832 > - snmpgetnext hrSystem.8 Delay 6 sec. 16:36:03.544645 IP 10.0.13.0.44989 > 10.0.6.103.161: GetNextRequest(28) .1.3.6.1.2.1.25.1.8 16:36:09.550255 IP 10.0.6.103.161 > 10.0.13.0.44989: GetResponse(32) .1.3.6.1.2.1.25.2.2.0=897832 > > - snmpgetnext hrStorage Delay 6 sec. 16:37:26.596090 IP 10.0.13.0.48087 > 10.0.6.103.161: GetNextRequest(27) .1.3.6.1.2.1.25.2 16:37:32.602472 IP 10.0.6.103.161 > 10.0.13.0.48087: GetResponse(32) .1.3.6.1.2.1.25.2.2.0=897832 > > > You original message implies that this was a widespread problem > affecting the whole of the host group. But above you state that > getnext on hrMemorySize is reporting back promptly. Getnext on hrMemorySize does return immediately, but I've seen delays elsewhere in host mibtree. > > Which MIB object(s) are affected by this problem? > If you walk the whole of the host subtree, where do the delays appear? > I'm listing all instances where I see 6 sec delay for host walk. Getnext commands: snmpgetnext -v2c -t30 -c public 10.0.6.103 mib-2.25 snmpgetnext -v2c -t30 -c public 10.0.6.103 mib-2.25 snmpgetnext -v2c -t30 -c public 10.0.6.103 mib-2.25.1.1.0 snmpgetnext -v2c -t30 -c public 10.0.6.103 mib-2.25.1.7.0 snmpgetnext -v2c -t30 -c public 10.0.6.103 mib-2.25.2.2.0 snmpgetnext -v2c -t30 -c public 10.0.6.103 mib-2.25.2.2.0 snmpgetnext -v2c -t30 -c public 10.0.6.103 mib-2.25.2.3.1.1.1 snmpgetnext -v2c -t30 -c public 10.0.6.103 mib-2.25.2.3.1.6.32 snmpgetnext -v2c -t30 -c public 10.0.6.103 mib-2.25.3.2.1.1.768 snmpgetnext -v2c -t30 -c public 10.0.6.103 mib-2.25.3.2.1.6.1283 snmpgetnext -v2c -t30 -c public 10.0.6.103 mib-2.25.3.3.1.1.768 snmpgetnext -v2c -t30 -c public 10.0.6.103 mib-2.25.3.3.1.2.769 snmpgetnext -v2c -t30 -c public 10.0.6.103 mib-2.25.3.4.1.1.1027 snmpgetnext -v2c -t30 -c public 10.0.6.103 mib-2.25.3.5.1.1.1280 snmpgetnext -v2c -t30 -c public 10.0.6.103 mib-2.25.3.5.1.1.1283 snmpgetnext -v2c -t30 -c public 10.0.6.103 mib-2.25.3.6.1.1.1536 snmpgetnext -v2c -t30 -c public 10.0.6.103 mib-2.25.3.6.1.4.1536 snmpgetnext -v2c -t30 -c public 10.0.6.103 mib-2.25.3.7.1.1.1536.1 snmpgetnext -v2c -t30 -c public 10.0.6.103 mib-2.25.3.7.1.5.1536.3 snmpgetnext -v2c -t30 -c public 10.0.6.103 mib-2.25.3.8.1.1.1 snmpgetnext -v2c -t30 -c public 10.0.6.103 mib-2.25.3.8.1.9.2 snmpgetnext -v2c -t30 -c public 10.0.6.103 mib-2.25.4.2.1.1.1 snmpgetnext -v2c -t30 -c public 10.0.6.103 mib-2.25.4.2.1.7.32019 snmpgetnext -v2c -t30 -c public 10.0.6.103 mib-2.25.5.1.1.1.1 snmpgetnext -v2c -t30 -c public 10.0.6.103 mib-2.25.5.1.1.2.32019 snmpgetnext -v2c -t30 -c public 10.0.6.103 mib-2.25.6.1.0 snmpgetnext -v2c -t30 -c public 10.0.6.103 mib-2.25.6.2.0 snmpgetnext -v2c -t30 -c public 10.0.6.103 mib-2.25.6.3.1.1.1 snmpgetnext -v2c -t30 -c public 10.0.6.103 mib-2.25.6.3.1.5.1020 snmpgetnext -v2c -t30 -c public 10.0.6.103 mib-2.28.1.1.2.1 RESPONSE: HOST-RESOURCES-MIB::hrSystemUptime.0 = Timeticks: (347244760) 40 days, 4:34:07.60 HOST-RESOURCES-MIB::hrSystemUptime.0 = Timeticks: (347245377) 40 days, 4:34:13.77 HOST-RESOURCES-MIB::hrSystemDate.0 = STRING: 2010-5-15,16:47:42.0,+5:30 HOST-RESOURCES-MIB::hrMemorySize.0 = INTEGER: 897832 KBytes HOST-RESOURCES-MIB::hrStorageIndex.1 = INTEGER: 1 HOST-RESOURCES-MIB::hrStorageIndex.1 = INTEGER: 1 HOST-RESOURCES-MIB::hrStorageIndex.3 = INTEGER: 3 HOST-RESOURCES-MIB::hrDeviceIndex.768 = INTEGER: 768 HOST-RESOURCES-MIB::hrDeviceIndex.769 = INTEGER: 769 HOST-RESOURCES-MIB::hrProcessorFrwID.768 = OID: SNMPv2-SMI::zeroDotZero HOST-RESOURCES-MIB::hrProcessorFrwID.769 = OID: SNMPv2-SMI::zeroDotZero HOST-RESOURCES-MIB::hrNetworkIfIndex.1025 = INTEGER: 1 HOST-RESOURCES-MIB::hrPrinterStatus.1280 = INTEGER: unknown(2) HOST-RESOURCES-MIB::hrPrinterStatus.1281 = INTEGER: unknown(2) HOST-RESOURCES-MIB::hrDiskStorageAccess.1536 = INTEGER: readWrite(1) HOST-RESOURCES-MIB::hrDiskStorageMedia.1536 = INTEGER: unknown(2) HOST-RESOURCES-MIB::hrPartitionIndex.1536.1 = INTEGER: 1 HOST-RESOURCES-MIB::hrPartitionIndex.1536.2 = INTEGER: 2 HOST-RESOURCES-MIB::hrFSIndex.1 = INTEGER: 1 HOST-RESOURCES-MIB::hrFSIndex.2 = INTEGER: 2 HOST-RESOURCES-MIB::hrSWRunIndex.1 = INTEGER: 1 HOST-RESOURCES-MIB::hrSWRunIndex.2 = INTEGER: 2 HOST-RESOURCES-MIB::hrSWRunPerfCPU.1 = INTEGER: 1057 HOST-RESOURCES-MIB::hrSWRunPerfCPU.2 = INTEGER: 61 HOST-RESOURCES-MIB::hrSWInstalledLastChange.0 = Timeticks: (0) 0:00:00.00 HOST-RESOURCES-MIB::hrSWInstalledLastUpdateTime.0 = Timeticks: (0) 0:00:00.00 HOST-RESOURCES-MIB::hrSWInstalledIndex.1 = INTEGER: 1 HOST-RESOURCES-MIB::hrSWInstalledIndex.2 = INTEGER: 2 Apparently delays appear when we go to next branch. > > Dave > Thanks. Avnindra ------------------------------------------------------------------------------ _______________________________________________ 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/listinfo/net-snmp-users
