NAME
snmpv2d - Sun SNMPv2 Agent
snmpv2d supports the coldStart, linkUp, linkDown, and authentication traps.
snmpv2d uses UDP port 161, the standard SNMP port. snmpv2d issues traps through the same port on which it receives SNMP requests.
snmpv2d must run with ``root'' privileges and is typically started at system startup via /etc/rc.local. snmpv2d may not be started using inetd . When started, snmpv2d detaches itself from the keyboard, disables all signals except SIGKILL, SIGILL, SIGUSR1, and SIGUSR2, and places itself in the background.
OPTIONS
There are no options.
FILES
The following files are provided or created during installation for agent operation:
For more information on the configuration files, see their corresponding man page.
INSTALLATION
snmpv2d and its configuration file ( snmpv2d.conf(5) ) may be placed in any directory. However, /opt/SUNWconn/snm/agents for Solaris 2.x or /usr/snm/agents for Solaris 1.x is suggested for snmpv2d itself and /etc/opt/snm/agent (Solaris 2.x) or /etc/snm/agent (Solaris 1.x) for the configuration file. You should modify the configuration file as appropriate. If you make any changes to snmpv2d.conf(5) file keyword values, you must kill and restart snmpv2d for the changes to take effect.
To kill snmpv2d, as root, type /etc/init.d/init.snmpd stop for Solaris 2.x and /etc/init.snmpd stop for Solaris 1.x. To start snmpv2d, as root, type /etc/init.d/init.snmpd start for Solaris 2.x and /etc/init.snmpd start for Solaris 1.x.
Your /etc/services file (or NIS equivalent) should contain the following entries:
(Note that you need not explicitly place snmpv2d into the background. Also note that snmpv2d may not be started by inetd .)
SECURITY
SNMPv2 uses DES and MD5 for authentication and encryption. However, due to export licensing, DES and MD5 are not included in this release. See the configuration files man pages for more information about security.
ERRORS
cannot dispatch request
The proxy cannot dispatch the request. The rest of the message indicates the cause of the failure.
select(2) failed
A select(2) system call failed. The rest of the message indicates the cause of the failure.
sendto(2) failed
A sendto(2) system call failed. The rest of the message indicates the cause of the failure.
recvfrom(2) failed
A recvfrom(2) system call failed. The rest of the message indicates the cause of the failure.
no response from system
The SNMP agent on the target system does not respond to SNMP requests. This error might indicate that the SNMP agent is not running on the target system, the target system is down, or the network containing the target system is unreachable.
response too big
The agent could not fit the results of an operation into a single SNMP message. Split large groups or tables into smaller entities.
missing attribute
An attribute is missing from the requested group.
bad attribute type
An object attribute type received from the SNMP agent that does not match the attribute type specified by the proxy agent schema. The rest of the message indicates the expected type and received type.
cannot get sysUpTime
The proxy agent cannot get the variable sysUpTime from the SNMP agent.
sysUpTime type bad
The variable sysUpTime received from the SNMP agent has the wrong data type.
unknown SNMP error
An unknown SNMP error was received.
bad variable value
The requested specified an incorrect syntax or value for a set operation.
variable is read only
The SNMP agent did not perform the set request because a variable to set may not be written.
general error
A general error was received.
cannot make request PDU
An error occurred building a request PDU.
cannot make request varbind list
An error occurred building a request variable binding list.
cannot parse response PDU
An error occurred parsing a response PDU.
request ID - response ID mismatch
The response ID does not match the request ID.
string contains non-displayable characters A displayable string contains non-displayable characters.
cannot open schema file
An error occurred opening the proxy agent schema file.
cannot parse schema file
The proxy agent couldn't parse the proxy agent schema file.
cannot open host file
An error occurred opening the file associated with the na.snmp.hostfile keyword in /etc/opt/snm/snm.conf for Solaris 2.x and /etc/snm.conf for Solaris 1.x.
cannot parse host file
The proxy agent was unable to parse the file associated with the na.snmp.hostfile keyword in /etc/opt/snm/snm.conf for Solaris 2.x and /etc/snm.conf for Solaris 1.x.
attribute unavailable for set operations
The set could not be completed because the attribute was not available for set operations.
BUGS
snmpv2d returns the wrong interface speed for the SBUS FDDI interface (for example, ``bf0'').
snmpv2d does not return a MAC address for the SBUS FDDI interface (for example, ``bf0'').
Process names retrieved from snmpv2d contain a leading blank space.
When you change attribute values in the system group with an SNMP set request, the change is effective only as long as snmpv2d is running. snmpv2d does not save the changes to /etc/opt/snm/agent/snmpv2d.conf for Solaris 2.x and /etc/snm/agent/snmpv2d.conf for Solaris 1.x.
SEE ALSO
v2install(1), agt.pty(5), context.pty(5), mgr.cnf(5), mgr.pty(5), snmpv2d.conf(5), view.pty(5), SNMP RFCs (RFC1155 RFC1157 RFC1212 RFC1213 RFC1214, RFCs 1441-1452)