Please note that if, at any point, a particular check fails to return the results expected you should not proceed with the next stage. Instead you should try and identify what went wrong since the previous (successful) check, and fix it.
Note further that the various names (MIB files, modules, objects and numeric OIDs) are examples only. You should replace them with the appropriate names for the MIB module you are implementing. Such names will be given in italics in the examples.
$ cd ~/ucd-snmp-4.2.1 or wherever the tarball was unpacked to $ cd agent/mibgroup $ cp ~/mymib.[ch] . or wherever the files were generated
$ cd ../.. $ ./configure --with-mib-modules=mymib
$ agent/snmpd -f -L -d -p 9999(This runs the agent on a temporary port ( -p 9999) so that it doesn't need special priviledges, or interfere with your 'normal' agent. Incoming and outgoing packets are printed (-d), to show what's happening, and the agent is run as a 'non-daemon' command (-f -L) so that you can see these messages. Note that this ties up the current shell, so you'll need to run the following checks in a different terminal window.).
$ snmpgetnext -p 9999 localhost public system system.sysDescr.0 = something or other
$ snmpgetnext -p 9999 localhost public .1.3.6.1.4.1.9999 .1.3.6.1.4.1.9999.1.1.0 = something or other(Replace this OID with the OID at the top of the subtree that you're implementing in this module.)
$ snmpgetnext -OS -p 9999 localhost public MY-MIB::myObject MY-MIB::myObject.0 = something or other(Replace the module name with the name of the MIB module you are implementing, and the object name with the name of one of the objects in this module.)
$ ls -l /usr/local/sbin/snmpd(This is the most likely location for the new agent. But use whatever was reported as part of the make install output).
$ /usr/local/sbin/snmpd -f -L -d -p 9999
Last modified: Wednesday, 01-Aug-2018 04:41:28 UTC
For questions regarding web content and site functionality, please write to the net-snmp-users mail list.