Basically nhSnmpTool walks on a subtree... Once the agent starts returning OIDs from other subtrees, it stops with a warning message "Walk ended with a larger response oid" .
In this example, target OID had specified:
StartOid=1.3.6.1.4.1.2636.3.15.1.1
Each oid returned is compared with 1.3.6.1.4.1.2636.3.15.1.1, and if it matches, the walk continues.
When the tool did a getnext request, the agent returned something like 1.3.6.1.4.1.2636.3.16 which did not match the original StartOid, and the walk was stopped.
So this is a warning message and means the device doesn't have required OIDs for QoS certification. You would need to configure QoS or contact the manufacturer or SNMP agent vendor to find out why.
2. Case 2: "#Got NO_SUCH_NAME. Making sure no more oids left. Trying 1.3.6.1.4.2"
This is a normal situation that walks all possible MIB branches to make sure we get all OIDs with the target OID
# enterprises 1.3.6.1.4.1
#
#sapwalk: ver 2.7
#Copyright (c) 1994-2006 SIMPLESOFT Inc.
#Address=138.42.243.21, StartOid=1.3.6.1.4.1
#TimeOut=20000, MaxRetries=4, CompareFlag=1, DebugFlag=0
1.3.6.1.4.1.2021.4.1.0 , Integer , 0
?
1.3.6.1.4.1.11070.4.14.1.0 , Integer , 1
#Got NO_SUCH_NAME. Making sure no more oids left. Trying 1.3.6.1.4.1.11070.4.14.2
#Got NO_SUCH_NAME. Making sure no more oids left. Trying 1.3.6.1.4.1.11070.4.15
#Got NO_SUCH_NAME. Making sure no more oids left. Trying 1.3.6.1.4.1.11070.5
#Got NO_SUCH_NAME. Making sure no more oids left. Trying 1.3.6.1.4.1.11071
#Got NO_SUCH_NAME. Making sure no more oids left. Trying 1.3.6.1.4.2
#Walk ended
3. Case 3: noResponse
The default time out is 20 seconds. If you see noResponse in MIB walk file, it means the agent is responding slowly. You can increase the time-out with the "-t" flag and value (sec), e.g.-t 60
.