Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

snmpd.internal(5snmp) [debian man page]

SNMPD.INTERNAL(5snmp)						     Net-SNMP						     SNMPD.INTERNAL(5snmp)

NAME
snmpd.internal - internal configuration of the Net-SNMP agent DESCRIPTION
The snmpd.conf(5) man page defines the syntax and behaviour of the main configuration directives that can be used to control the operation of the Net-SNMP agent, and the management information it provides. However there are several other configuration directives (many of which, though not all, start with a leading underscore) that are recog- nised by the agent. These are typically used to retain configuration across agent restarts, and are not intended for direct user access. This man page list these directives, giving a brief indication of where they are used. For full details - see the relevant source files. If you can't follow that source, you probably shouldn't be fiddling with these directives! AGENT BEHAVIOUR
quit ACCESS CONTROL
VACM Configuration vacmView / vacmGroup / vacmAccess These directives are used to retain dynamically configured access control settings. SYSTEM INFORMATION
System Group setSerialNo This directive is used to implement the advisory lock object snmpSetSerialNo. psyslocation / psyscontact / psysname These directives are used to retain dynamically configured system settings. They will be overridden by the corresponding sysLoca- tion, sysContact and sysName directives. ACTIVE MONITORING
Notification Handling pauthtrapenable This directive is used to retain the dynamically configured setting of whether the agent should generate authenticationFailure traps. It will be overridden by the corresponding authtrapenable directive. snmpNotify*Table targetAddr / targetParams These directives are used to retain dynamically configured notification destination settings. DisMan Event MIB _mteE*Table, _mteOTable, _mteT*Table These directives are used to retain dynamically configured event, object and monitor trigger settings. mteObjectsTable / mteTriggerTable These directives are for compatibility with the previous disman/event-mib implementation. DisMan Schedule MIB _schedTable This directive is used to retain dynamically configured scheduled events. EXTENDING AGENT FUNCTIONALITY
Arbitrary Extension Commands extend-sh exec2 / sh2 / execFix2 These directives were defined by analogy with equivalent directives in the previous ucd-snmp/extensible implementation. They are deprecated, and should not be used. FILES
/etc/snmp/snmpd.conf SEE ALSO
snmpconf(1), snmpd.conf(5), snmp.conf(5), snmp_config(5), snmpd(8), EXAMPLE.conf, read_config(3). 4th Berkeley Distribution 08 Feb 2002 SNMPD.INTERNAL(5snmp)

Check Out this Related Man Page

SNMP_CONFIG(5)							     Net-SNMP							    SNMP_CONFIG(5)

NAME
snmp_config - handling of Net-SNMP configuration files DESCRIPTION
The Net-SNMP package uses various configuration files to configure its applications. This manual page merely describes the overall nature of them, so that the other manual pages don't have to. DIRECTORIES SEARCHED
First off, there are numerous places that configuration files can be found and read from. By default, the applications look for configura- tion files in the following 4 directories, in order: /etc/snmp, /usr/share/snmp, /usr/lib/snmp, and $HOME/.snmp. In each of these directo- ries, it looks for files with the extension of both conf and local.conf (reading the second ones last). In this manner, there are 8 default places a configuration file can exist for any given configuration file type. Additionally, the above default search path can be overridden by setting the environment variable SNMPCONFPATH to a colon-separated list of directories to search for. The path for the persistent data should be included when running applications that use persistent storage, such as snmpd. Applications will read persistent configuration files in the following order of preference: file in SNMP_PERSISTENT_FILE environment variable directories in SNMPCONFPATH environment variable directory defined by persistentDir snmp.conf variable directory in SNMP_PERSISTENT_DIR environment variable default /var/db/net-snmp directory Finally, applications will write persistent configuration files in the following order of preference: file in SNMP_PERSISTENT_FILE environment variable directory defined by persistentDir snmp.conf variable directory in SNMP_PERSISTENT_DIR environment variable default /var/db/net-snmp directory Note: When using SNMP_PERSISTENT_FILE, the filename should match the application name. For example, /var/net-snmp/snmpd.conf. CONFIGURATION FILE TYPES
Each application may use multiple configuration files, which will configure various different aspects of the application. For instance, the SNMP agent (snmpd) knows how to understand configuration directives in both the snmpd.conf and the snmp.conf files. In fact, most applications understand how to read the contents of the snmp.conf files. Note, however, that configuration directives understood in one file may not be understood in another file. For further information, read the associated manual page with each configuration file type. Also, most of the applications support a -H switch on the command line that will list the configuration files it will look for and the directives in each one that it understands. The snmp.conf configuration file is intended to be a application suite wide configuration file that supports directives that are useful for controlling the fundamental nature of all of the SNMP applications, such as how they all manipulate and parse the textual SNMP MIB files. SWITCHING CONFIGURATION TYPES IN MID-FILE It's possible to switch in mid-file the configuration type that the parser is supposed to be reading. Since that sentence doesn't make much sense, lets give you an example: say that you wanted to turn on packet dumping output for the agent by default, but you didn't want to do that for the rest of the applications (ie, snmpget, snmpwalk, ...). Normally to enable packet dumping in the configuration file you'd need to put a line like: dumpPacket true into the snmp.conf file. But, this would turn it on for all of the applications. So, instead, you can put the same line in the snmpd.conf file so that it only applies to the snmpd daemon. However, you need to tell the parser to expect this line. You do this by putting a spe- cial type specification token inside a [] set. In other words, inside your snmpd.conf file you could put the above snmp.conf directive by adding a line like so: [snmp] dumpPacket true This tells the parser to parse the above line as if it were inside a snmp.conf file instead of an snmpd.conf file. If you want to parse a bunch of lines rather than just one then you can make the context switch apply to the remainder of the file or until the next context switch directive by putting the special token on a line by itself: # make this file handle snmp.conf tokens: [snmp] dumpPacket true logTimestamp true # return to our original snmpd.conf tokens: [snmpd] rocommunity mypublic COMMENTS
Any lines beginning with the character '#' in the configuration files are treated as a comment and are not parsed. INCLUDING OTHER CONFIGURATION FILES
It is possible to include other configuration files for processing during normal configuration file processing.: # include site specific config include site.conf This will search every directory in the configuration path for files named site.conf, and will process those files before returning to the processing of the original file. Note that if '.conf' is omitted, it will be appended. That is, all configuration files must end in '.conf'. API INTERFACE
Information about writing C code that makes use of this system in either the agent's MIB modules or in applications can be found in the netsnmp_config_api(3) manual page. SEE ALSO
snmpconf(1), netsnmp_config_api(3), snmp.conf(5), snmpd.conf(5) V5.6.2.1 08 Mar 2010 SNMP_CONFIG(5)
Man Page