Content-type: text/html Man page of snmpd

snmpd

Section: Maintenance Commands (8)
Index Return to Main Contents
 

NAME

snmpd, snmpd.conf - Simple Network Management Protocol (SNMP) agent daemon  

SYNOPSIS

/usr/sbin/snmpd  

DESCRIPTION

The snmpd daemon is an extensible SNMP V1 agent that starts automatically at boot time. It listens for SNMP requests on UDP port 161 and for local subagents wishing to register extended MIBs. The snmpd daemon itself contains no MIB code, it processes SNMP requests by communicating with registered subagents. The snmpd daemon collates the subagents replies and sends the SNMP response to logically remote network management stations.

For information about building subagents and extensible SNMP support, refer to the Network Programmer's Guide .

Tru64 UNIX standard MIB support is implemented in the subagent process /usr/sbin/os_mibs. This process is started and stopped automatically in conjunction with the snmpd daemon.

The snmpd daemon reads its configuration file, /etc/snmpd.conf, at startup time. You can change the configuration by editing the /etc/snmpd.conf file, as described in the Configuring snmpd section in this reference page. The default configuration grants read access to the world, and does not generate any traps. The snmpd daemon logs error messages through the syslog function to the /usr/var/adm/syslog.dated/date/daemon.log log file.  

Configuring snmpd

The /etc/snmpd.conf file defines the initial values for four MIB variables, as well as access control based on community names. It also can contain device-related information for use within the Host Resources MIB. The entries have the following format: sysName name sysLocation location sysContact contact snmpEnableAuthenTraps n community community-name IP-address privileges trap trap-community-name IP-address hrDevice_ignore file

White space (tabs, spaces, line feeds, and carriage returns) and blank lines are ignored.  

MIB Variable Initialization

When an entry in the /etc/snmpd.conf file is one of the following MIB variables, it is assigned the value that follows it: sysName name sysLocation location sysContact contact snmpEnableAuthenTraps n

According to RFC 1213, the variables sysName, sysLocation, and sysContact can be any string of 0 to 255 NVT ASCII characters. The value of the snmpEnableAuthenTraps entry can be either 1 or 2 to enable or disable traps; for example: sysLocation City, USA sysContact Kathy Berberian 555-7667 snmpEnableAuthenTraps 1 If the values of the sysName, sysLocation, and sysContact variables are modified by SNMP set commands, the new values are updated in the snmpd.conf file. (The sysName variable does not affect the system's host name.) If sysName is not defined in the snmpd.conf file, the system's host name is used.  

Community Entries

Community entries have the following format: community-name IP-address privileges

Can be any string. Indicates the remote site for which this community is valid. If the IP address is 0.0.0.0, any address can communicate using that community name. Can be read for read-only or write for read and write.

The following is a sample entry for the community variable: community test1 130.117.1.20 READ

This example defines a community named test1 that allows read-only access from the IP address 130.117.1.20. The Tru64 UNIX agent implements write access to all MIB II variables so defined. Authorized parties are able to change the Tru64 UNIX environment; such as bring down an interface or delete an entry from the routing table.  

Disabling snmpd

By default, the snmpd.conf file contains a community entry that permits read access of all MIB variables via the community public. You can constrain access to different communities by removing this default entry and by adding entries with different community names.

If you want to disable access to MIB variables completely (some sites might want to do this), the recommended method is to remove all community entries in the snmpd.conf file and to restart snmpd.  

Trap Community Entries

Trap entries have the following format: trap-community-name IP-address

Can be any string. Indicates the destination address to be included in the trap PDU.

The following is a sample trap entry: trap test2 128.169.4.15

This example indicates to the agent that if a trap needs to be sent, the trap PDU should be built using the community name test2 and sent to the trap port at 128.169.4.15.  

Host Resources MIB Device Entries

Device entries have the following format: hrDevice_ignore file This type of entry causes the Host MIB implementation to ignore (never attempt to open) any files that match the file string. This feature is available in cases where you do not want certain devices to be probed. For example, the following entry causes all of the /dev/rrz3 device files (/dev/rrz3a, /dev/rrz3b, and so on) to be ignored. hrDevice_ignore /dev/rrz3

Sending the SIGUSR1 signal to snmpd causes it to dump its registry of MIBs and subagents to the file /var/tmp/snmpd_dump.log. A simple way to do this is to use the /sbin/init.d/snmpd dump command.  

FILES

The snmpd daemon configuration file. The system daemon log file, where date is the date. The file containing a dump of the snmpd daemon's MIB registry. This directory contains eSNMP UNIX domain sockets.  

RELATED INFORMATION

Commands: os_mibs(8), syslog(3)

Network Administration , Network Programmer's Guide , /usr/examples/esnmp/*

Structure and Identification of Management Information for TCP/IP-Based Internets (RFC 1155), A Simple Network Management Protocol (RFC 1157), Concise MIB Definitions (RFC 1212), Conventions for Defining Traps for Use With the SNMP (RFC 1215), delim off


 

Index

NAME
SYNOPSIS
DESCRIPTION
Configuring snmpd
MIB Variable Initialization
Community Entries
Disabling snmpd
Trap Community Entries
Host Resources MIB Device Entries
FILES
RELATED INFORMATION

This document was created by man2html, using the manual pages.
Time: 02:40:41 GMT, October 02, 2010