Hello Dave and net-snmp Coders,
I was under the impression that the snmpwalk command, given the root oid, it will walk entire tree.
Is this true?
I'm running snmpwalk from a specfied MIB root node, say system.
I'm running net-snmp 5.4.2.1 version for Linux my snmpwalk command is:
snmpwalk -Os -v 1 -c public localhost system
and the result are:
sysDescr.0 = STRING: "Linux cmm 2.6.29.6 #9 Thu Sep 10 11:44:52 PDT 2009 i686"
sysObjectID.0 = OID: linux
sysUpTimeInstance = Timeticks: (53665) 0:08:56.65
sysContact.0 = STRING: "
Bernadette.Eyre@alca..."
sysName.0 = STRING: "cmm"
sysLocation.0 = STRING: "testlab-system"
sysServices.0 = INTEGER: 12
sysORLastChange.0 = Timeticks: (1) 0:00:00.01
sysORID.1 = OID: snmpFrameworkMIBCompliance
sysORID.2 = OID: snmpMPDCompliance
sysORID.3 = OID: usmMIBCompliance
sysORID.4 = OID: snmpMIB
sysORID.5 = OID: tcpMIB
sysORID.6 = OID: ip
sysORID.7 = OID: udpMIB
sysORID.8 = OID: vacmBasicGroup
sysORDescr.1 = STRING: The SNMP Management Architecture MIB.
sysORDescr.2 = STRING: The MIB for Message Processing and Dispatching.
sysORDescr.3 = STRING: The management information definitions for the SNMP User-based Security Model.
sysORDescr.4 = STRING: The MIB module for SNMPv2 entities
sysORDescr.5 = STRING: The MIB module for managing TCP implementations
sysORDescr.6 = STRING: The MIB module for managing IP and ICMP implementations
sysORDescr.7 = STRING: The MIB module for managing UDP implementations
sysORDescr.8 = STRING: View-based Access Control Model for SNMP.
sysORUpTime.1 = Timeticks: (0) 0:00:00.00
sysORUpTime.2 = Timeticks: (0) 0:00:00.00
sysORUpTime.3 = Timeticks: (0) 0:00:00.00
sysORUpTime.4 = Timeticks: (1) 0:00:00.01
sysORUpTime.5 = Timeticks: (1) 0:00:00.01
sysORUpTime.6 = Timeticks: (1) 0:00:00.01
sysORUpTime.7 = Timeticks: (1) 0:00:00.01
sysORUpTime.8 = Timeticks: (1) 0:00:00.01
I'm running the command from the same machine where the snmpd is running and MIBS and MIBDIRS env are set.
I started the snmpd with -f, -Dsnmp_agent and Lo options set to observe the behaviour.
Here is my snmpd command:
/sbin/snmpd -f -Dsnmp_agent -V -a -c /usr/local/etc/snmp/snmpd.conf -x /var/agentx/master -Lo
Studying the trace it seems that snmpd stops when the start oid changes from what it was set before.
Here is the tail end of the trace:
GETNEXT message
-- SNMPv2-MIB::sysORUpTime.4
snmp_agent: agent_sesion 0x84b1ae8 created
snmp_agent: add_vb_to_cache(0x84b1ae8, 1, SNMPv2-MIB::sysORUpTime.4, 0x805b478)
snmp_agent: tp->start SNMPv2-MIB::sysORUpTime, tp->end SNMPv2-MIB::sysOREntry.5,
snmp_agent: REMOVE session == 0x84b1ae8
snmp_agent: agent_session 0x84b1ae8 released
snmp_agent: end of handle_snmp_packet, asp = 0x84b1ae8
Received SNMP packet(s) from UDP: [127.0.0.1]->[127.0.0.1]:-13692
GETNEXT message
-- SNMPv2-MIB::sysORUpTime.5
snmp_agent: agent_sesion 0x84b1ae8 created
snmp_agent: add_vb_to_cache(0x84b1ae8, 1, SNMPv2-MIB::sysORUpTime.5, 0x805b478)
snmp_agent: tp->start SNMPv2-MIB::sysORUpTime, tp->end SNMPv2-MIB::sysOREntry.5,
snmp_agent: REMOVE session == 0x84b1ae8
snmp_agent: agent_session 0x84b1ae8 released
snmp_agent: end of handle_snmp_packet, asp = 0x84b1ae8
Received SNMP packet(s) from UDP: [127.0.0.1]->[127.0.0.1]:-13692
GETNEXT message
-- SNMPv2-MIB::sysORUpTime.6
snmp_agent: agent_sesion 0x84b1ae8 created
snmp_agent: add_vb_to_cache(0x84b1ae8, 1, SNMPv2-MIB::sysORUpTime.6, 0x805b478)
snmp_agent: tp->start SNMPv2-MIB::sysORUpTime, tp->end SNMPv2-MIB::sysOREntry.5,
snmp_agent: REMOVE session == 0x84b1ae8
snmp_agent: agent_session 0x84b1ae8 released
snmp_agent: end of handle_snmp_packet, asp = 0x84b1ae8
Received SNMP packet(s) from UDP: [127.0.0.1]->[127.0.0.1]:-13692
GETNEXT message
-- SNMPv2-MIB::sysORUpTime.7
snmp_agent: agent_sesion 0x84b1ae8 created
snmp_agent: add_vb_to_cache(0x84b1ae8, 1, SNMPv2-MIB::sysORUpTime.7, 0x805b478)
snmp_agent: tp->start SNMPv2-MIB::sysORUpTime, tp->end SNMPv2-MIB::sysOREntry.5,
snmp_agent: REMOVE session == 0x84b1ae8
snmp_agent: agent_session 0x84b1ae8 released
snmp_agent: end of handle_snmp_packet, asp = 0x84b1ae8
Received SNMP packet(s) from UDP: [127.0.0.1]->[127.0.0.1]:-13692
GETNEXT message
-- SNMPv2-MIB::sysORUpTime.8
snmp_agent: agent_sesion 0x84b1ae8 created
snmp_agent: add_vb_to_cache(0x84b1ae8, 1, SNMPv2-MIB::sysORUpTime.8, 0x805b478)
snmp_agent: tp->start SNMPv2-MIB::sysORUpTime, tp->end SNMPv2-MIB::sysOREntry.5,
snmp_agent: add_vb_to_cache(0x84b1ae8, 1, SNMPv2-MIB::sysORUpTime.8, 0x805b550)
snmp_agent: tp->start SNMPv2-MIB::sysOREntry.5, tp->end IF-MIB::ifNumber,
snmp_agent: add_vb_to_cache(0x84b1ae8, 1, SNMPv2-MIB::sysORUpTime.8, 0x80be228)
snmp_agent: tp->start IF-MIB::ifNumber, tp->end IF-MIB::ifTable,
snmp_agent: REMOVE session == 0x84b1ae8
snmp_agent: agent_session 0x84b1ae8 released
snmp_agent: end of handle_snmp_packet, asp = 0x84b1ae8
Any comments are appreictaed.
thanks,
Bernadette
opensubscriber is not affiliated with the authors of this message nor responsible for its content.