NAME
snm.conf - Site/SunNet/Domain Manager configuration file for agents and daemons
DESCRIPTION
/etc/opt/SUNWconn/snm/snm.conf for Solaris 2.x or /etc/snm.conf for Solaris 1.x is an ASCII text file that acts as a central place for defining Site/SunNet/Domain Manager agent and daemon resources and operations.
/etc/opt/SUNWconn/snm/snm.conf for Solaris 2.x or /etc/snm.conf for Solaris 1.x also specifies per-host security levels for agents and may be used for third - party Site/SunNet/Domain Manager applications.
SYNTAX
Blank lines are allowed. Entries cannot span lines. Comments start with a ``#'' as the first non-white space character on the line and continue through the end of the line.
Entries have the format:
keyword<whitespace>string_value
keyword is an identifier defined by the agent or daemon. The agent or daemon looks for keyword, skips the white space (TABS and spaces), and uses string_value as the associated value. You should not change the keywords because the agent or daemon won't find them.
Each agent has an entry of the form na.name , just like their file names. The Agent Services library uses these entries to set agent security levels when an agent is started.
The interpretation of string_value is up to the agent using it. It can be a file, a directory, a list of directories, a number or anything else that will fit on a line. string_value may contain embedded white space if the agent supports it.
You can always change the value of string_value to satisfy local site requirements. Ensure the value is appropriate for the way the agent uses keyword. If writing an agent, ensure that the agent's usage of the keyword's value is well -documented.
ENTRIES
These are the keywords used by Site/SunNet/Domain Manager agents and daemons:
na.snmp.schemas
list of directories where SNMP schema files reside. Separate each directory with a colon. The keyword's supplied value is /opt/SUNWconn/snm/agents for Solaris 2.x and /usr/snm/agents for Solaris 1.x.
na.snmp.default-schema
file name where the SNMP proxy agent can find its default schema. The default schema file is used if no schema file is defined in the optional arguments for a request.
This file must exist (and be identical) on both the manager station and the machine where the agent runs. On the manager station, the agent schema is treated like any other; that is, it defines groups, tables, attributes, and so on, for the user interface. The SNMP proxy agent uses the schema to map information returned by the target host into Site/SunNet/Domain Manager attributes.
The keyword's supplied value is /opt/SUNWconn/snm/agents/snmp-mibII.schema for Solaris 2.x and /usr/snm/agents/snmp-mibII.schema for Solaris 1.x if Site/SunNet/Domain Manager was installed in /opt/SUNWconn/snm for Solaris 2.x and /usr/snm for Solaris 1.x.
na.snmp.hostfile
the file name where the SNMP proxy agent gets hostspecific information for SNMP requests if certain information is not included in the manager request. The file is also where the SNMP trap daemon gets the name of the trap file to be used for specified devices. The keyword's supplied value is /var/opt/SUNWconn/snm/snmp.hosts for Solaris 2.x and /var/adm/snm/snmp.hosts for Solaris 1.x.
na.snmp.request_timeout
the number of seconds the SNMP proxy agent will wait for an SNMP response from the target device. If the round trip time between the SNMP proxy agent and the managed devices is longer than 5 seconds (due to a slow link or the amount of traffic), you may want to increase this number. If the packet round trip time is predictably faster than five seconds, you can decrease this number.
The keyword's supplied value is 5.
na.snmp.max_attempts
the maximum number of Get or Get-Next packets that the SNMP proxy agent will attempt to send to a target device for each reporting interval. If the SNMP proxy agent is on the same subnet as the devices it is managing, you may want to decrease this number to 1. If the SNMP proxy agent is communicating with the devices across a relatively unreliable link, you may want to increase this number.
The keyword's supplied value is 3.
na.snmp.report_timeout
the number of seconds before the SNMP proxy agent will time out while trying to send a report to an SNM rendezvous. The keyword's supplied value is 5.
na.snmp.ack_timeout
the number of seconds before the SNMP proxy agent will time out while waiting for an acknowledgement from a subprocess that the subprocess will perform a new request. If the proxy agent times out, it will create a new subprocess to handle the request. Note that a subprocess may fail to acknowledge a new request if it is blocked while sending a request to the target device or blocked while sending a report to an SNM rendezvous. You should increase this time out value only if you have a large number of subprocesses in relation to the number of requests the proxy agent is performing. The keyword's supplied value is 15.
na.snmp.max-subprocs
the maximum number of subprocesses the SNMP proxy agent will fork to handle new requests.
The keyword's supplied value is 20.
na.snmp.max-requests
the maximum number of requests that an SNMP proxy agent subprocess will handle.
The keyword's supplied value is 50.
na.snmp.trap-if-no-response
specifies whether the SNMP proxy agent is to send a `no response' trap instead of an error report if the target device does not respond to a poll. The keyword's supplied value is true.
na.snmp.exit-if-no-requests
specifies whether the SNMP proxy agent is to exit if it is not performing any requests. The value `true' minimizes the number of processes running on your system. Set the value to `false' if you have one or more large SNMP schema files and you find that the SNMP proxy agent is exceedingly slow to start up. Since the proxy agent loads all SNMP schema files when it starts up, setting this keyword value to `false' removes the overhead of loading the schema files each time the proxy agent restarts.
The keyword's supplied value is true.
na.snmp.get-next-force-full-varbindlist
specifies whether the SNMP proxy agent should forcibly send the full variable binding list everytime while performing a SNMP get-next request. It is particularly useful especially when querying tables from target SNMP agents, where different rows of the same table do not support all the attributes as defined in the variable bind list, but only a subset of them. If the value is set to `false' then all the variables not serviced/returned from the previous get-next request are dropped before performing the next get-next operation. Setting the value to `true' will force the full variable bind list for each get-next request, even though the previous request might not have returned certain attributes.
The keyword's supplied value is false.
na.snmpv2.default-schema
file name of default MIB (in schema format). The keyword's supplied value is
na.snmp-trap.forward.snmp-traps
forwards the SNMP trap PDU to other hosts. Up to two hosts can be specified.
na.snmp-trap.raw
specifies a flag used to indicate whether the trap daemon should also send raw oid/value in the trap report. The keyword's supplied value is false.
na.hostperf.request_timeout
the number of seconds the hostperf proxy agent will wait for an rstat(8r) response from the target device. The keyword's supplied value is 5.
na.hostperf.report_timeout
the number of seconds before the hostperf proxy agent will time out while trying to send a report to an SNM rendezvous.
The keyword's supplied value is 5.
na.hostperf.ack_timeout
the number of seconds before the hostperf proxy agent will time out while waiting for an acknowledgement from a subprocess that the subprocess will perform a new request. If the proxy agent times out, it will create a new subprocess to handle the request. Note that a subprocess may fail to acknowledge a new request if it is blocked while sending a request to the target device or blocked while sending a report to an SNM rendezvous. You should increase this time out value only if you have a large number of subprocesses in relation to the number of requests the proxy agent is performing. The keyword's supplied value is 15.
na.hostperf.max-subprocs
the maximum number of subprocesses the hostperf proxy agent will fork to handle new requests. The keyword's supplied value is 20.
na.hostperf.max-request
the maximum number of requests that a hostperf proxy agent subprocess will handle.
The keyword's supplied value is 50.
na.hostperf.trap-if-no-response
specifies whether the hostperf proxy agent is to send a `no response' trap instead of an error report if the target device does not respond to a poll. The keyword's supplied value is true.
na.ping.reach-packets
the maximum number of ICMP ping request packets that are sent to the target device before the device is reported as `unreachable'.
The keyword's supplied value is 3.
na.ping.stats-packets
the number of ICMP ping request packets that are sent to the target device to gather statistics for the `stats' group.
The keyword's supplied value is 5.
na.ping.request_timeout
the number of seconds the ping proxy agent will wait for a ping response from the target device. The keyword's supplied value is 1.
na.ping.report_timeout
the number of seconds before the ping proxy agent will time out while trying to send a report to an SNM rendezvous. The keyword's supplied value is 5.
na.ping.ack_timeout
the number of seconds before the ping proxy agent will time out while waiting for an acknowledgement from a subprocess that the subprocess will perform a new request. If the proxy agent times out, it will create a new subprocess to handle the request. Note that a subprocess may fail to acknowledge a new request if it is blocked while sending a request to the target device or blocked while sending a report to an SNM rendezvous. You should increase this time out value only if you have a large number of subprocesses in relation to the number of requests the proxy agent is performing. The keyword's supplied value is 15.
na.ping.max-subprocs
the maximum number of subprocesses the ping proxy agent will fork to handle new requests.
The keyword's supplied value is 20.
na.ping.max-requests
the maximum number of requests that a ping proxy agent subprocess will handle.
The keyword's supplied value is 50.
na.snmp-trap.default-trapfile
file name where enterprise-specific SNMP traps are defined. See na.snmp.trapfile(5).
The keyword's supplied value is /var/opt/SUNWconn/snm/snmp.traps for Solaris 2.x and /var/adm/snm/snmp.traps for Solaris 1.x.
na.snmp-trap.rendez
list of hosts to which the SNMP trap proxy should send traps. Separate each host with a colon. This keyword is not supplied in the default file. This causes the SNMP trap proxy to send traps to the local host.
na.snmp-trap.raw
specifies whether the SNMP trap daemon returns raw OIDs and their values without translation for attributes in trap reports, in addition to the translated attribute names and values.
The keyword's supplied value is false.
activity-log
file name of the activity log. The activity daemon, na.activity, uses this file to maintain a record of the currently active data and event reporting activities started from manager applications on the local machine. The keyword's supplied value is /var/opt/SUNWconn/snm/activity.log for Solaris 2.x and /var/adm/snm/activity.log for Solaris 1.x.
event-log
file name of the event log. The event dispatcher, na.event, uses this file to log all event reports it receives.
The keyword's supplied value is /var/opt/SUNWconn/snm/event.log for Solaris 2.x and /var/adm/snm/event.log for Solaris 1.x.
monitor-log
file name the logger, na.logger, uses to log all data and event reports it receives.
The keyword's supplied value is /var/opt/SUNWconn/snm/monitor.log for Solaris 2.x and /var/adm/snm/monitor.log for Solaris 1.x.
request-log
file name of the request log. The Agent Services library uses this file to track the requests running on the local machine with the restart option specified. When an agent starts after an abnormal termination, the Agent Service library attempts to restart any requests for the agent that are listed in this file. The keyword's supplied value is /var/opt/SUNWconn/snm/request.log for Solaris 2.x and /var/adm/snm/request.log for Solaris 1.x.
na.agentname
agent's security level, from zero (none) to five (highest). There is one entry for each agent. The keyword's supplied value is 0 (zero - no security).
linkmap
specifies the location for the link map file. This file is used by Discover and Console for link management. The keyword's supplied value is /var/opt/SUNWconn/snm/linkmap for Solaris 2.x and /var/adm/snm/linkmap for Solaris 1.x.
snmdb-directory
specifies the location for the database. The keyword's supplied value is /var/opt/SUNWconn/snm for Solaris 2.x and /var/adm/snm for Solaris 1.x.
get-requested-attributes-only
retrieves only the specified attributes. On previous versions of SunNet manager, all the attributes in a group were retrieved by default. If this behaviour is required, set this keyword to false. The keyword's supplied value is true.
WARNING
Keywords are very agent-specific. Agents must never assume there is any relationship between keywords, never use a keyword for more than one purpose, and never use another agent's keywords.
SEE ALSO
na.snmp.hostfile(5), na.snmp(8)
NOTES
Site/SunNet/Domain Manager does not currently provide any API functions to retrieve or validate the contents of this file; it must be done by the agent.