snmpd(1M) snmpd(1M)
NAME
snmpd, snmpdm - Simple Network Management Protocol (SNMP) Process
SYNOPSIS
contact] contact] location] location] logfile] logfile] logmask] logmask] portnum] portnum] description] description]
extendFile]
contact] contact] location] location] logfile] logfile] logmask] logmask] value] description] description]
DESCRIPTION
The Master SNMP Agent and the collection of subAgents that would attach to the Master Agent collectively form a single SNMP Agent. The
SNMP Agent accepts SNMP Get, GetNext and Set requests from an SNMP Manager which cause it to read or write the Management Information Base
The objects are instrumented by the subAgents.
The Master Agent can bind to separate process subagents.
Options
The Master agent and the manual startup script recognize the following command line options:
Log all error messages, warnings messages and trace messages. This
option forces to run in the foreground.
Log all error messages. This option can be used in conjunction with
and
Log all trace messages. This option can be used in conjunction with
and
Log all warning messages. This option can be used in conjunction with
and
Suppress sending authenticationFailure traps.
Specify the contact person responsible for the network management agent.
This option overrides the contact person specified in the Master Agent configuration file It does not alter the value
specified in the file. By default, the agent's contact is a blank string. To configure the agent's contact, add the
contact after the word contact: in the configuration file or use the option.
This option is provided for backward compatibility with the pre-emanate
snmpd.ea extensible SNMP agent. It is applicable only to the script and only if the EMANATE extensible agent is
installed. It is installed if the file exists. This option causes the extsubagt to use the command line specified
extendFile instead of the default file to add user defined MIB objects to the SNMP agent.
Display command line options and log mask values.
Specify the location of the agent.
This option overrides the location specified in It does not alter the value in By default, the agent's location is a
blank string. To configure the agent's location, add the location to or use the option.
Use the logfile for logging rather than the default logfile, A value of will direct logging to
The value can be
or means use traditional logging format for file. means use new logging format. The new logging format gives the
Log level, Timestamp, Program Name, File name, Line Number and message in separate lines.
Sets the initial logging mask to
logmask. The logmask option may not be used in the agent start up scripts. This option should be used only while
debugging the agent. See the SNMP Agent Logging section for valid values of logmask and for other details.
Normally puts itself into the background as if the command was terminated with an ampersand(&). This option inhibits that
behavior and makes the agent run in the foreground.
Specify the UDP port number that the agent will listen on for SNMP requests.
The default is port 161. The value can also be specified in Only the super-user can start and only one can execute
on a particular UDP port.
Allows the user to specify the value for the
object. The format is a text string enclosed in quotes. This option overrides the specified in For example,
Allow Master agent to accept connections from any subagent.
This is a default option.
Allow Master agent to accept connections from local TCP subagents.
Do not allow Master agent to accept connections from any TCP subagent.
SNMPv1 Security
Each request is accompanied by a community name, which is essentially a password that enables access to values on an agent. A Manager can
request to read a value by issuing an GetRequest/GetNextRequest, or a manager may request to alter a value by issuing an SetRequest.
By default, the agent does not respond to any requests, regardless of community name used in the request. To configure the agent to
respond to GetRequests/GetNextRequests, add a to See the snmpd.conf(4) manpage. To configure the agent to respond to SetRequests AND
GetRequests/GetNextRequests, add a to
SNMPv2c
Simple Network Management Protocol Community based Version 2 is supported in this version of the Agent.
Traps
The agent also sends information to a manager without an explicit request from the manager. Such an operation is called a By default,
traps are not sent to any destination. To configure the agent to send traps to one or more specific destinations, add the trap destina-
tions to
The Master Agent and the MIB-2 subAgent collaborate to send the following traps:
Sends a coldStart trap when the SNMP Agent is invoked.
Sends a linkDown trap when an interface goes down.
Sends a linkUp trap when an interface comes up.
Sends an authenticationFailure trap when an
request is sent to the agent with a community name that does not match the community names specified in
The Master Agent and the IPv6 subAgent collaborate to send the following traps:
Sends a linkDown trap when an IPv6 interface goes down.
Sends a linkUp trap when an IPv6 interface comes up.
SNMP Agent Logging
The SNMP Agent provides the capability to log various types of errors and events. There are three types of logging: Errors, Warnings and
Traces.
Log Masks
Log masks enable the user to specify the particular classes of messages that should be logged to or the specified logfile. There are three
different ways in which you can specify the logmask that you want. They are:(1) decimal number, (2) hex number, or(3) text string. The
three may not be used in combination.
To select multiple output types do the following. For decimal or hex format simply add the individual logmask values together and enter
that number. When entering strings, place multiple strings on the same line, space separated, without quotes.
For example, to turn on error log messages:
Supported MIB Objects
The Management Information Base is a conceptual database of values on the agent. The Master SNMP Agent implements a small number of
objects but most objects are implemented by subAgents that have attached to the Master Agent. See on systems with HP OpenView products
installed for definitions of particular objects.
This version of the SNMP Agent includes the subAgents, and which implement the MIB-2, HP UNIX and IPv6 MIBs respectively. The IPv6 sub-
agent is supported on HP-UX 11i Version 1 platform with the IPv6 depot installed. The MIB-II and HP-UX MIBs are described in and on sys-
tems with HP Openview products installed.
It also includes the subagents and The trapdestagt supports the MIB variables used for updating the trapdest entries in snmpd.conf file.
For details on the naaagt subagent please refer to naaagt man page.
The MIB-2 subAgent supports most of the objects in The group is not supported. The HP-UX subAgent supports most of the objects in the HP-
UX MIB. The IPv6 subagent supports most of the objects in and
Deprecated MIBS
The ieee8023Mac group corresponding to the following OID is no longer supported:
private(4).enterprises(1).hp(11).nm(2).interface(4).ieee8023Mac(1)
This group is replaced with the "Ether-Like" group (RFC1398) which corresponds to OID:
mgmt(2).mib-2(1).transmission(10).dot3(7)
SNMP Agent Startup
The SNMP Agent startup mechanism is built upon the System V.4 file system paradigm. The startup script, which was used in previous
releases of the SNMP Agent is no longer used.
Automatic Startup
As installed, the SNMP Master Agent and all subAgents should startup automatically each time the system re-boots or any time the system
transitions from run level 1 to run level 2. When the system enters run level 2 the operating system will execute which will startup the
Master Agent. Similarly, and will startup the MIB2, HP-UX and IPv6 subAgents respectively immediately after the Master Agent is started.
The trapdestagt and naaagt subagents are started by and
Prior to executing these startup scripts the system will examine all scripts in for environment variables which could potentially influence
the startup of the Master Agent and each subAgent. See the particular startup script or configuration file for details on supported envi-
ronment variables. The user should never modify scripts in Instead the startup behavior should be controlled by adjusting values in the
appropriate configuration script in
The interactions and relationships among these processes and files at invocation time is shown below.
Solaris
/etc/rc2 invokes /etc/rc2.d/S98SnmpMaster
/etc/rc2.d/S98SnmpMaster invokes /sbin/init.d/SnmpMaster
/sbin/init.d/SnmpMaster invokes /usr/sbin/snmpdm
/usr/sbin/snmpdm reads /etc/SnmpAgent.d/snmpd.conf
/etc/rc2 invokes /etc/rc2.d/S97SnmpMib2
/etc/rc2.d/S97SnmpMib2 invokes /sbin/init.d/SnmpMib2
/sbin/init.d/SnmpMib2 invokes /usr/sbin/mib2agt
/etc/rc2 invokes /etc/rc2.d/S97SnmpHpunix
/etc/rc2.d/S97SnmpHpunix invokes /sbin/init.d/SnmpHpunix
/sbin/init.d/SnmpHpunix invokes /usr/sbin/hp_unixagt
/etc/rc2 invokes /etc/rc2.d/S97SnmpTrpDst
/etc/rc2.d/S97SnmpTrpDst invokes /sbin/init.d/SnmpTrpDst
/sbin/init.d/SnmpTrpDst invokes /usr/sbin/trapdestagt
/etc/rc2 invokes /etc/rc2.d/S97Naa
/etc/rc2.d/S97SnmpNaa invokes /sbin/init.d/SnmpNaa
/sbin/init.d/SnmpNaa invokes /usr/sbin/naaagt
HP-UX 10.X, 11i
/sbin/rc invokes /sbin/rc2.d/S560SnmpMaster
/sbin/rc2.d/S560SnmpMaster invokes /sbin/init.d/SnmpMaster
/sbin/init.d/SnmpMaster invokes /usr/sbin/snmpdm
/usr/sbin/snmpdm reads /etc/SnmpAgent.d/snmpd.conf
/sbin/rc invokes /sbin/rc2.d/s565SnmpMib2
/sbin/rc2.d/s565SnmpMib2 invokes /sbin/init.d/SnmpMib2
/sbin/init.d/SnmpMib2 invokes /usr/sbin/mib2agt
/sbin/rc invokes /sbin/rc2.d/s565SnmpHpunix
/sbin/rc2.d/s565SnmpHpunix invokes /sbin/init.d/SnmpHpunix
/sbin/init.d/SnmpHpunix invokes /usr/sbin/hp_unixagt
/sbin/rc invokes /sbin/rc2.d/s565SnmpTrpDst
/sbin/rc2.d/s565SnmpTrpDst invokes /sbin/init.d/SnmpTrpDst
/sbin/init.d/SnmpTrpDst invokes /usr/sbin/trapdestagt
HP-UX 11i Version 1 (with IPv6 depot installed)
/sbin/rc invokes /sbin/rc2.d/S560SnmpMaster
/sbin/rc2.d/S560SnmpMaster invokes /sbin/init.d/SnmpMaster
/sbin/init.d/SnmpMaster invokes /usr/sbin/snmpdm
/usr/sbin/snmpdm reads /etc/SnmpAgent.d/snmpd.conf
/sbin/rc invokes /sbin/rc2.d/s565SnmpMib2
/sbin/rc2.d/s565SnmpMib2 invokes /sbin/init.d/SnmpMib2
/sbin/init.d/SnmpMib2 invokes /usr/sbin/mib2agt
/sbin/rc invokes /sbin/rc2.d/s565SnmpHpunix
/sbin/rc2.d/s565SnmpHpunix invokes /sbin/init.d/SnmpHpunix
/sbin/init.d/SnmpHpunix invokes /usr/sbin/hp_unixagt
/sbin/rc invokes /sbin/rc2.d/s565SnmpIpv6
/sbin/rc2.d/s565SnmpIpv6 invokes /sbin/init.d/SnmpIpv6
/sbin/init.d/SnmpIpv6 invokes /usr/sbin/ipv6agt
/sbin/rc invokes /sbin/rc2.d/s565SnmpTrpDst
/sbin/rc2.d/s565SnmpTrpDst invokes /sbin/init.d/SnmpTrpDst
sbin/init.d/SnmpTrpDst invokes /usr/sbin/trapdestagt
Manual Startup
There are two ways to start the SNMP Agent manually. The first way is to execute and then start each subAgent. Separate process subAgents
are started by invoking the particular subAgent executables.
The second and simplest way to start the SNMP Agent manually is to execute the startup script which will invoke the Master Agent and all
subAgents who have been installed and designed to operate in this paradigm. The script is layered upon the V.4 startup paradigm and so
makes use of the component startup scripts in and configuration scripts in When is invoked it starts passes all its command line arguments
to it and then executes each script (S*) found in
Objects on which the agent supports requests:
o
Objects that return Null values (Solaris only):
o
Objects that return errors (Solaris only):
o
o
o
o
o
ERRORS
Duplicate community names may not be used in the configuration file. In the past the agent allowed a user to have the same name used many
times in the file. This typically happens when the user would set the same name for a get and set community name. The implication being
that the name could be used for gets and sets. Due to the new agent, it would cause problems to allow this. So, now the set community
names have read/write access. That is, they are both a set and get community name. When this error occurs, the agent will still start.
However, an ERROR log will be written in the logfile and you will likely end up with undesirable results.
EXTERNAL INFLUENCES
Environment Variables
determines the language in which messages appear. If is not specified or is set to the empty string, a default of "C" (see lang(5)) is
used instead of If any internationalization variable contains an invalid setting, behaves as if all internationalization variables are set
to "C." See environ(5).
The environment variables specific to the master agent snmpdm are as below:
Environment Variables
Exporting this variable to >= 1MB restricts the size of the
log file. When the size grows beyond the value exported, the log file rolls over.
This variable can be exported to change the default port on which
listens.
This variable can be exported to change the default port to which
sends traps.
Exporting this variable to any value between 1 and 600 seconds will
control the behaviour of in sending the coldstart trap. The trap will be sent after the expiry of the num-
ber of seconds specified or registering, whichever is earlier.
This variable can be exported to specify the directory where the log file
will be created.
This variable can be exported to specify the directory in which the
configuration file is available.
International Code Set Support
Supports single-byte character code sets.
AUTHOR
was developed by HP, Massachusetts Institute of Technology and SNMP Research.
FILES
SEE ALSO
snmpd.conf(4).
RFC 1155, RFC 1157, RFC 1212, RFC 1213, RFC 1231, RFC 1398, RFC 2452 RFC 2454, RFC 2465, RFC 2466
snmpd(1M)