snmpv2d.conf manual page
Table of Contents

NAME

snmpv2d.conf - the SNMP agent configuration

SYNOPSIS

TAG VALUE

DESCRIPTION

The configuration file snmpv2d.conf is one of several configuration files required by the SNMPv2 entities and the only file required by the SNMPv1 entities. The default location of snmpv2d.conf is /etc/opt/snm/agent for Solaris 2.x and /etc/snm/agent for Solaris 1.x, but can be specified by the environment variable SR_AGT_CONF_DIR.

The snmpv2d.conf file defines initial values for the system group, community names, trap community names, and whether authentication-failure traps should be generated.

Note: for bilingual and SNMPv2 agents, the snmpv2d.conf initializes the system variables and defines authenticationfailure traps. Communities are defined only when compiled as SNMPv1.

The form of each line is:

TAG VALUE

Where TAG is one of

sysDescr
sysLocation
sysContact
snmpEnableAuthenTraps
community
trap

and VALUE is a valid value for the given key.

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

System Variable Initialization
When the TAG is one of the system variables:

sysDescr
sysLocation
sysContact
snmpEnableAuthenTraps

that variable will be initialized to whatever value follows it.

According to RFC1213, the variables sysDescr, sysLocation, and sysContact can be any string of 0 to 255 NVT ASCII characters, and snmpEnableAuthenTraps can be either

1 to enable traps

or
2 to disable traps.

For example:

sysDescr
SNMP agent from My Company
sysLocation
Anywhere, USA
sysContact
Woody Boyd (156) 555-7667 snmpEnableAuthenTraps 1

initializes sysDescr, sysLocation, and sysContact to appropriate strings and enables authentication-failure traps.

Community Entries
When the TAG is "community," the format of the VALUE clause is:

community-name IP-address privileges community-id

where

· community-name may be any string.

· IP-address indicates the remote's site for which this
community is valid. If the IP address is 0.0.0.0,any address may communicate using that session name.

· privileges are any one of:
READ for read only, WRITE for read/write, or NONE to lock out a community name.

· The community identifier may be used internally.

For example,

community test1
130.117.1.20 READ 0

defines a community named test1 that allows reads only from IP address 130.117.1.20.

Trap Community Entries
When the TAG is "trap," the format of the VALUE clause is:

trap-community-name IP-address

where

· The trap-community name may be any string.

· The IP address indicates the destination address to be
included in the trap PDU.

For example,

trap test2
128.169.4.15

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.

FILES

SNMPv2 Configuration Files
When the agent is compiled with either SNMPv2 or both SNMPv1 and SNMPv2 defined, the additional configuration files acl.pty, agt.pty, context.pty, and view.pty are required.

Additional SNMPv2 Configuration Files
When the agent is compiled with either SNMPv2 or both SNMPv1 and SNMPv2 defined, the configuration files acl.pty, agt.pty, context.pty, and view.pty are required.

acl.pty
Access control privileges for the SNMPv2 parties.

agt.pty
Party information for the manager routines.

context.pty
Context information for the SNMPv2 parties.

view.pty
MIB view information for the SNMPv2 parties.acl.pty

For Solaris 2.x, the files are located under:

/etc/opt/snm/agent/acl.pty
/etc/opt/snm/agent/agent.pty
/etc/opt/snm/agent/context.pty
/etc/opt/snm/agent/snmpv2d.conf
/etc/opt/snm/agent/view.pty

For Solaris 1.x, the files are located under:

/etc/snm/agent/acl.pty
/etc/snm/agent/agent.pty
/etc/snm/agent/context.pty
/etc/snm/agent/snmpv2d.conf
/etc/snm/agent/view.pty

SEE ALSO

snmpv2d(1), v2install(1), acl.pty(5), agt.pty(5), context.pty(5), mgr.cnf(5), mgr.pty(5), view.pty(5), SNMP RFCs (RFC1155 RFC1157 RFC1212 RFC1213 RFC1215, RFCs 14411452)

LIMITATIONS

Not all MIB variables can be supported without source code alterations to the kernel or device drivers.

Table of Contents