All, I was able to have net-snmp agent (snmpd) respond to network related MIB queries with v4.4.y kernel and corresponding file system with net-snmp installed. When I migrate to a v4.9.y kernel and a corresponding file system, I see that snmpd is only responding to system MIB queries, but not to any network related MIB queries. In our case, the agent is running on an ARM based board and file system is built using yocto.
snmpwalk -v 2c -c public 192.168.2.20 interfaces IF-MIB::interfaces = No more variables left in this MIB View (It is past the end of the MIB tree) What is the best way to debug this? The MIBs are at root@am57xx-evm:~# ls /usr/share/snmp/mibs AGENTX-MIB.txt IP-FORWARD-MIB.txt RFC1155-SMI.txt SNMPv2-CONF.txt BRIDGE-MIB.txt IP-MIB.txt RFC1213-MIB.txt SNMPv2-MIB.txt DISMAN-EVENT-MIB.txt IPV6-FLOW-LABEL-MIB.txt RMON-MIB.txt SNMPv2-SMI.txt DISMAN-SCHEDULE-MIB.txt IPV6-ICMP-MIB.txt SCTP-MIB.txt SNMPv2-TC.txt DISMAN-SCRIPT-MIB.txt IPV6-MIB.txt SMUX-MIB.txt SNMPv2-TM.txt EtherLike-MIB.txt IPV6-TC.txt SNMP-COMMUNITY-MIB.txt TCP-MIB.txt HCNUM-TC.txt IPV6-TCP-MIB.txt SNMP-FRAMEWORK-MIB.txt TRANSPORT-ADDRESS-MIB.txt HOST-RESOURCES-MIB.txt IPV6-UDP-MIB.txt SNMP-MPD-MIB.txt TUNNEL-MIB.txt HOST-RESOURCES-TYPES.txt NET-SNMP-AGENT-MIB.txt SNMP-NOTIFICATION-MIB.txt UCD-DEMO-MIB.txt IANA-ADDRESS-FAMILY-NUMBERS-MIB.txt NET-SNMP-EXAMPLES-MIB.txt SNMP-PROXY-MIB.txt UCD-DISKIO-MIB.txt IANA-LANGUAGE-MIB.txt NET-SNMP-EXTEND-MIB.txt SNMP-TARGET-MIB.txt UCD-DLMOD-MIB.txt IANA-RTPROTO-MIB.txt NET-SNMP-MIB.txt SNMP-TLS-TM-MIB.txt UCD-IPFWACC-MIB.txt IANAifType-MIB.txt NET-SNMP-PASS-MIB.txt SNMP-TSM-MIB.txt UCD-SNMP-MIB.txt NET-SNMP-TC.txt SNMP-USER-BASED-SM-MIB.txt UDP-MIB.txt IF-INVERTED-STACK-MIB.txt NET-SNMP-VACM-MIB.txt SNMP-USM-AES-MIB.txt IF-MIB.txt NOTIFICATION-LOG-MIB.txt SNMP-USM-DH-OBJECTS-MIB.txt INET-ADDRESS-MIB.txt RFC-1215.txt SNMP-VIEW-BASED-ACM-MIB.txt Also created .snmp folder and copied a snmpd.conf to it using snmpconf command with basic community based access control using public and private community names. I know I could use the debug token to enable selective traces and see what is going on. But what trace token to be used for seeing the flow of snmpget coommands for example to see if-mib?? I tried snmpd -f -Le -DifTable -d root@am57xx-evm:~# snmpd -f -Le -d -DifTable registered debug token ifTable, 1 ifTable:init_ifTable: Registering ifTable as a mibs-for-dummies table. ifTable:access: creating new entry ifTable:access: creating new entry ifTable:access: creating new entry ifTable:access: creating new entry ifTable:access: creating new entry ifTable:access: creating new entry ifTable:access: creating new entry ifTable:access: creating new entry ifTable:init_ifTable: ignoring duplicate call NET-SNMP version 5.7.3 ifTable:access: updating existing entry lo ifTable:access: updating existing entry eth0 ifTable:access: updating existing entry eth1 ifTable:access: updating existing entry sit0 ifTable:access: updating existing entry can0 ifTable:access: updating existing entry eth2 ifTable:access: updating existing entry eth3 ifTable:access: updating existing entry lo ifTable:access: updating existing entry eth0 ifTable:access: updating existing entry eth1 ifTable:access: updating existing entry sit0 ifTable:access: updating existing entry can0 ifTable:access: updating existing entry eth2 ifTable:access: updating existing entry eth3 Received 41 byte packet from UDP: [192.168.2.30]:46105->[192.168.2.20]:161 0000: 30 27 02 01 01 04 06 70 75 62 6C 69 63 A1 1A 02 0'.....public... 0016: 04 5C 91 6F 8E 02 01 00 02 01 00 30 0C 30 0A 06 .\.o.......0.0.. 0032: 06 2B 06 01 02 01 02 05 00 .+....... Sending 41 bytes to UDP: [192.168.2.30]:46105->[192.168.2.20]:161 0000: 30 27 02 01 01 04 06 70 75 62 6C 69 63 A2 1A 02 0'.....public... 0016: 04 5C 91 6F 8E 02 01 00 02 01 00 30 0C 30 0A 06 .\.o.......0.0.. 0032: 06 2B 06 01 02 01 02 82 00 .+....... ifTable:access: updating existing entry lo ifTable:access: updating existing entry eth0 ifTable:access: updating existing entry eth1 ifTable:access: updating existing entry sit0 ifTable:access: updating existing entry can0 ifTable:access: updating existing entry eth2 ifTable:access: updating existing entry eth3 ifTable:access: updating existing entry lo ifTable:access: updating existing entry eth0 ifTable:access: updating existing entry eth1 ifTable:access: updating existing entry sit0 ifTable:access: updating existing entry can0 ifTable:access: updating existing entry eth2 ifTable:access: updating existing entry eth3 ifTable:access: updating existing entry lo ifTable:access: updating existing entry eth0 ifTable:access: updating existing entry eth1 ifTable:access: updating existing entry sit0 ifTable:access: updating existing entry can0 ifTable:access: updating existing entry eth2 ifTable:access: updating existing entry eth3 But it doesn't show any helpful trace. Any help? I am desperately looking for ways to debug this issue. -- Murali Karicheri Linux Kernel, Keystone ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ 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
