snmpd(1M) System Administration Commands snmpd(1M)NAMEsnmpd - daemon to respond to SNMP request packets
SYNOPSIS
/usr/sfw/sbin/snmpd [options] [listening addresses]
DESCRIPTION
The snmpd daemon is an SNMP agent that binds to a port and awaits
requests from SNMP management software. Upon receiving a request, it
processes the request(s), collects the requested information, performs
any requested operation(s), and, finally, returns information to the
requester.
OPTIONS
The following options are supported:
-a
Log the source addresses of incoming requests.
-A
Append to the log file rather than truncating it.
-c file
Read file as a configuration file.
-C
Do not read any configuration files except the one optionally spec‐
ified by the -c option.
Note that this behavior also covers the persistent configuration
files. This can result in dynamically-assigned values being reset
following an agent restart, unless the relevant persistent configu‐
ration files are explicitly loaded using the -c option.
-d
Dump (in hexadecimal) the sent and received SNMP packets.
-D[token[,...]]
Turn on debugging output for the given token(s). Without any tokens
specified, this option defaults to printing all of the tokens
(which is equivalent to the keyword ALL). Use ALL for extremely
verbose output. Note that you must not put a space between the -D
flag and the listed tokens.
-f
Do not fork() from the calling shell.
-g GID
Change to the numerical group ID GID after opening listening sock‐
ets.
-h, --help
Display a brief usage message and then exit.
-H
Display a list of configuration file directives understood by the
agent and then exit.
-I -initlist
This option specifies which modules you do (or do not) want to be
initialized when the agent starts up. If the comma-separated
initlist is preceded with an hyphen (-), it is the list of modules
that you do not want to be started. Otherwise, initlist is the list
of modules to be started.
To obtain a list of compiled modules, run the agent with the argu‐
ments -Dmib_init -H This command assumes you have debugging support
compiled in.
-l [file]
Log all output from the agent (including stdout and stderr) to
file. If no filename is given, log to a default file set at compile
time, normally /var/log/snmpd.log.
-L
Do not open a log file. Send all messages to stderr instead.
-P file
Save the process ID of the daemon in file.
-q
Print simpler output for easier automated parsing.
-r
Do not require root access to run the daemon. Specifically, do not
exit if files accessible only to root (such as /dev/kmem) cannot be
opened.
-s
Use syslog for logging. See syslogd(1M)-S d[0-7]
Specifies the syslog facility to use when logging to syslog. d
means LOG_DAEMON and the integers 0 through 7 refer to LOG_LOCAL0
through LOG_LOCAL7. LOG_DAEMON is the default.
-u UID
Change to the user ID UID (which can be given in numerical or text
form) after opening listening sockets.
-v --version
Display version information for the agent and then exit.
-V
Symbolically dump SNMP transactions.
-x address
Listens for AgentX connections on address rather than on the
default /var/agentx/master. The address can either be a Unix domain
socket path or the address of a network interface. The format is
the same as the format of listening addresses described below. Note
that it is a possible security risk to expose the master agent lis‐
tening address through TCP/UDP. See section 9 of RFC 2741 for more
details.
-X
Run as an AgentX subagent rather than as an SNMP master agent.
Listening Addresses
By default, snmpd listens for incoming SNMP requests only on UDP port
161. However, it is possible to modify this behavior by specifying one
or more listening addresses as arguments to the daemon. A listening
address takes the form:
[<transport-specifier>:]<transport-address>
At its simplest, a listening address can consist of only a port number,
in which case snmpd listens on that UDP port on all IPv4 interfaces.
Otherwise, the <transport-address> part of the specification is parsed
according to the following table:
<transport-specifier> <transport-address> format
udp hostname[:port] or
IPv4-address[:port]
tcp hostname[:port] or
IPv4-address[:port]
unix pathname
Currently transports TCP/UDP over IPv4/IPv6 and unix domain sockets.
Note that <transport-specifier> strings are case-insensitive so that,
for example, tcp and TCP are equivalent. Below are some examples, with
accompanying explanations.
127.0.0.1:161
Listen on UDP port 161, but only on the loopback interface. This
prevents snmpd from being queried remotely. The :161 is redundant
because that is the default SNMP port.
TCP:1161
Listen on TCP port 1161 on all IPv4 interfaces.
unix:/tmp/local-agent
Listen on the Unix domain socket /tmp/local-agent.
/tmp/local-agent
Identical to the previous specification, because the Unix domain is
the default transport if and only if the first character of <trans‐
port-address> is a slash (/).
udp6:10161
Listen on port 10161 on all IPv6 interfaces.
Note that not all the transport domains listed above will always be
available. For example, hosts with no IPv6 support will not be able to
use udp6 transport addresses, and attempts to do so will result in the
error "Error opening specified endpoint".
FILESsnmpd checks for the existence of and parses the following files:
snmp.conf
Common configuration for the agent and applications. See
snmp.conf(4) for details.
snmpd.local.conf
Agent-specific configuration. See snmp.conf(4) for details. These
files are optional and can be used to configure access control,
trap generation, subagent protocols, and other features.
In addition to these two configuration files, the agent will read
any files with the names snmpd.conf and snmpd.local.conf in a
colon-separated path specified in the SNMPCONFPATH environment
variable, the default location upon agent startup are /etc/sma/snmp
and /usr/local/share/snmp.
/etc/sma/snmp/mibs
The agent loads all files in this directory as MIBs. It does not,
however, load any file that begins with a dot (.) or descend into
subdirectories.
EXIT STATUS
0
Successful completion.
1
A usage syntax error. A usage message is displayed. Also used for
timeout errors.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
┌─────────────────────────────┬─────────────────────────────┐
│ ATTRIBUTE TYPE │ ATTRIBUTE VALUE │
├─────────────────────────────┼─────────────────────────────┤
│Availability │SUNWsmagt │
├─────────────────────────────┼─────────────────────────────┤
│Interface Stability │Stable │
└─────────────────────────────┴─────────────────────────────┘
SEE ALSOsvcadm(1M), svccfg(1M), snmp.conf(4), attributes(5), smf(5)NOTES
In addition to basic privileges, to run successfully, the agent
requires PRIV_NET_PRIVADDR. See privileges(5).
The snmpd service is managed by the service management facility,
smf(5), under the service identifiers:
svc:/application/management/sma
svc:/application/management/seaport
Administrative actions on this service, such as enabling, disabling, or
requesting restart, can be performed using svcadm(1M). The service's
status can be queried using the svcs(1) command.
The service uses the solaris.smf.manage.sma privilege. If
/etc/sma/snmp/snmpd.conf contains DISABLE=YES, then the service does
not start and displays the message:
snmpd disabled by config file /etc/sma/snmp/snmpd.conf
SunOS 5.10 4 Aug 2006 snmpd(1M)
