NAME

mgr.cnf - SNMPv2 manager configuration

SYNOPSIS

Clustername

readInformation

| -

writeInformation

| -

noAuthClkSyncInformation | -

md5ClkSyncInformation

| -

adminInformation

| -

DESCRIPTION

The configuration file mgr.cnf is one of five files required by the SNMPv2 manager routines. The default location of mgr.cnf is /etc/opt/snm/manager for Solaris 2.x and /etc/snm/manager for Solaris 1.x, but can be specified by the environment variable SR_MGR_CONF_DIR.

The mgr.cnf file defines clusternames to be used as shorthand references to the clusters of information that define the access privileges and authentication protocol used for the request.

Each cluster of information contains six lines:

Clustername

readInformation

| -

writeInformation

| -

noAuthClkSyncInformation | -

md5ClkSyncInformation

| -

adminInformation

| -

where

Clustername

is a unique name for the cluster. This field is a string and must be present.

readInformation

defines the parties and context that should be used when performing gets, getnexts, getones, and getbulks.

This field is three OIDs. A "-" signifies a NULL record for that particular line.

writeInformation

defines the parties and context that should be used when performing sets.

This field is three OIDs. A "-" signifies a NULL record for that particular line.

noAuthClkSync

and

md5ClkSync

define the parties and context that should be used for clock synchronization if using the read, write, or admin record and the authType of the corresponding parties is md5. These fields are each three OIDs. A "-" signifies a NULL record for the particular line.

adminInformation

defines the parties and context that should be used for system administrator or "root" level activities.

Note: The adminInformation record is an unsupported feature in release 12 and is reserved for future use. The value "-" should be used for this field at this time.

EXAMPLE

A read only mgr.cnf entry might look like:

Test

jmja1 jajm2 initialContextId.128.169.4.16.1

-

-

-

-

This clustername can read, but it cannot write, request authentication protocols above the "no-authorization" level, or perform administrator-level functions.

Note: The parties jmja1 and jajm2 would need to be defined in the MIB and the mgr.pty(5) file. The initialContextId.128.169.4.16.1 would be defined in the context.pty(5) file.

FILES

Additional SNMPv2 Configuration Files

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

acl.pty Access control privileges for the SNMPv2 parties.

context.pty

Context information for the SNMPv2 parties.

mgr.pty

Party information for the manager routines.

view.pty

MIB view information for the SNMPv2 parties.

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

/etc/opt/snm/manager/acl.pty
/etc/opt/snm/manager/context.pty
/etc/opt/snm/manager/mgr.cnf
/etc/opt/snm/manager/mgr.pty
/etc/opt/snm/manager/view.pty

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

/etc/snm/manager/acl.pty
/etc/snm/manager/context.pty
/etc/snm/manager/mgr.cnf
/etc/snm/manager/mgr.pty
/etc/snm/manager/view.pty

SEE ALSO

v2install(1), acl.pty(5), agt.pty(5), context.pty(5), mgr.pty(5), snmpv2d.conf(5), view.pty(5),

SNMP RFCs (RFC1155 RFC1157 RFC1212 RFC1213 RFC1215, RFCs 1441-1452)