What is the Official Slogan of the net-snmp-coders list? Where can I get it? These binaries are also available on the project FTP site, with a link on the same web page. There is also a mirror at ftp: Although the project originally started at UC Davis hence the name , and it has always been based there, most of the contributors have had little or no connection with this institution.
The move to SourceForge was intended to provide a more flexible environment for the project, and to distribute the administrative workload more evenly. The change of name simply reflects this move, which was the last remaining link with UC Davis. Much of the work done for the various 5.
However attempts have been made to retain backwards compatibility as much as possible, and most code written for earlier releases should continue to work.
The most visible change from the 4. What operating systems does it run on? See the next question but one for the status of Windows support. Certain systems fail to compile particular portions of the agent.
These can usually be persuaded to compile at the loss of some functionality by omitting the modules affected. See the next question for more details. Also note that the presence of a particular configuration in this list does not imply a perfect or complete implementation.
This is simply what various people have reported as seeming to work. Or more frequently, the configurations where people have reported problems that we think we've subsequently fixed! What happens if mine isn't listed? Unless your system is significantly different to the supported configurations, most of the code library, applications and the agent infrastructure should probably compile with little or no difficulty.
The most likely source of problems will be MIB modules within the agent, as this tends to be where the most system-specific code is found. If a large number of modules fail, then it might be easier to start from a relatively bare system, using "configure --enable-mini-agent --with-defaults". Then if this minimal agent compiles and runs successfully, try adding each of the missing mibgroups individually using the configure option '--with-mib-module'.
If configure fails with "invalid configuration" messages, or you get completely stuck, contact the coders list for advice. Similarly, if you manage to get this working on a new system, please let us know of any code changes that you needed to make, together with details of the hardware you're using, and what versions of the operating system you've tried it on. The entry 'host' in the file 'config.
Does it run on Windows? Pre-compiled binaries are available from the project web site. Volunteers to assist with these missing modules are likely to welcomed with open arms: How do I find out about new releases? Advance notice of upcoming releases are also made on the net-snmp-users list for "release candidates" for a week or two before the full release, and on the net-snmp-coders list for "pre-releases" during the period prior to this.
Major code revisions may be announced more widely, but these lists are the most reliable way to keep in touch with the status of the package. Patches to fix known problems are also made available via the web site: There is also a net-snmp IRC channel set up on the freenode. You can connect to this via chat. Several core developers hang out on this channel on a fairly regular basis.
How do I submit a patch or bug report? Questions about using the package should be directed at the net-snmp-users lists. Note that this mailing list is relatively busy, and the people answering these questions are doing so out of the goodness of their hearts, and in addition to their main employment.
Please note the following: But remember that this is basically an unsupported package. It's Open Source, so if you need something fixing badly enough, fundamentally it's up to you to do the work. All patches should be submitted to the patch manager at http: The best way to submit patch diff information is by checking out the current code from the development git trunk, making your changes and then running "git diff" or "git format-patch" after you're done.
You should have your lawyer read this file if you wish to use the code in your commercial application. We will not summarize here what is in the file, as we're not lawyers and are unqualified to do so.
Practical experience showed up various problems and deficiencies with this, and a number of revised frameworks were developed to try and address these problems.
Unfortunately, it proved difficult to achieve any sort of agreement - particularly over the details of the administrative framework to use. There was less disagreement over the proposed changes to the protocol operations. This retained the same administrative framework as SNMPv1 with all of the accompanying limitations , but using the new protocol operations.
More recently, a new administrative framework has been developed, building on the various competing SNMPv2 proposals, and using the same SNMPv2 protocol operations.
It addresses some of the deficiencies of the community-based versions, including significant improvements to the security of SNMP requests like it finally has some! Which versions of SNMP are supported in this package? The agent will respond to requests using any of these protocols, and all the tools take a command-line option to determine which version to use. Support for SNMPv2 classic a. This is almost completely unrelated to the versions of the protocol used to operate on these values.
SNMPv1 requests will either treat such objects as an error, or skip them completely. That's not really the focus of the Net-SNMP project - our tools are more low-level, single-shot commands. The other approach is to configure the SNMP agent to monitor the relevant information itself, and issue an alert when the values pass suitable limits.
That's because it is impossible to provide a universal answer to these questions. The information to monitor, and the normal operating values will ultimately depend on your local environment. Where can I find more information about network management? Some of the most useful are http: This is available from ftp: What ports does SNMP use? However, it is possible to use the library within a multi-threaded management application. This reads in and parses MIB information which isn't thread-safe as well as preparing a session structure for subsequent use.
The command-line tools shipped as part of the Net-SNMP distribution are simple single-threaded applications, and are not designed for multi-threaded use. Adapting these to a threaded model is left as an exercise for the student.
The same holds true for the notification receiver snmptrapd. Unfortunately, the SNMPv3 support was added about the same time as the thread support and since they occurred in parallel the SNMPv3 support was never checked for multi-threading correctness. It is most likely that it is not thread-safe at this time. See the next question or the next section respectively. How do I add a MIB to the tools? Not just giving the object names, but also showing named enumeration values, and interpreting table indexes properly particularly for string and OID index values.
There are two steps required to add a new MIB file to the tools. Firstly, copy the MIB file into the appropriate location: Secondly, tell the tools to load this MIB: These are typically the same apart from the. Or use the special value "all" to have the tools load all available MIBs which may slow them down, particularly if you have a large number of MIB files.
The agent needs to be explicitly extended to support the new MIB objects, which typically involves writing new code. Most of the tools apart from 'snmptable' will work quite happily without any MIB files at all - although the results won't be displayed in quite the same way. Why can't I see anything from the agent? Either the management application does not like the request so never sends it , or the agent does not like the request so never responds.
The simplest way to distinguish between the two is to run the command with the command-line option '-d'. If this doesn't display a hex dump of the raw outgoing packet, then it's the client side which is dropping the request. Hopefully you should also see an error message, to help identify what's wrong. If this displays one or more outgoing dumps but nothing coming back , then the request is failing at the agent end. See the next entry for more details. There are three further possibilities to consider: One is that the agent may return a response to the original query, but the management application may not like this response, and refuse to display it.
This is relatively unusual, and typically indicates a flaw with the remote agent. I hope you're not contemplating the suggestion that the Net-SNMP command-line tools might contain bugs! The typical symptoms of this would be that the '-d' option would display a sequence of sending and received packet dumps, with the same contents each time. Ask on the mailing list for advice. Alternatively, the agent may simply not support the MIB objects being requested.
This is most commonly seen when using the "snmpwalk" tool particularly with SNMPv1. Repeating the same request with the "snmpgetnext" command-line tool should show the information if any that the agent returned, which was then discarded by snmpwalk as irrelevant.
Note that this is how snmpwalk was designed to work.