NAME
discover.conf - configuration file for SunNet Manager Discover Tool
SYNOPSIS
$SNMDISCOVERMAP/discover.conf
DESCRIPTION
The configuration file discover.conf contains parameters for certain less commonly used features of the Discover Tool. The file is stored in the directory specified by the value of the environment variable $SNMDISCOVERMAP . The discover.conf file is located in the directory defined by SNMDBDIR. If SNMDBDIR is undefined, then /var/opt/SUNWconn/snm for Solaris 2.x or /var/adm/snm for Solaris 1.x is the default directory.
You need to deal with discover.conf only if you want to:
Within discover.conf, the order of fields is significant.
OID Section
The OID section maps object identifiers (OIDs) to element types. An element type determines the glyph used for a given element. An entry has the form <oid> <element_type>, where <element_type> is in a schema file that has been loaded into the Console. For example:
#OID
#
COLORS Section
The COLORS section of discover.conf allows you to create your own color names for the two sections, COMPONENTS and DEFAULTS, that follow COLORS. As shipped with SNM, the COLORS section is as follows:
#COLORS
#
COMPONENTS Section
The COMPONENTS section of discover.conf associates element types with the colors defined in the COLORS section. For example:
#COMPONENTS
#
#DEFAULTS
#
MAPPINGS Section
The MAPPINGS section allows you to map a keyword returned from the SNMP system description to an SNM element type. If a keyword has whitespace, it must be enclosed in quotes. The Discover Tool has the Sun machine types listed below as defaults.
SNMP agent ibm pc
and you have the following entries in your discover.conf file:
#MAPPINGS
MONITOR COMPONENTS Section
The MONITOR COMPONENTS section enables the monitor function to monitor views of types other than networks and subnets. An entry in this section has the following form:
<view type>
where <view type> identifies the type of view that you want to the monitor function to monitor. The view type and view instance must be successfully loaded in the Console. The view type must have a netmask field; for the view instance, the netmask field must have a non-null value.
The view types shipped with SNM do not qualify for monitoring because they do not have a netmask field. To see the list of view types, invoke Edit>Create in the Console's control area, then click SELECT on the View category in the Create Object window.
AGENTS Section
The AGENTS section enables the Discover Tool to search for agents in addition to those shipped with SNM. An entry has the following form:
<RPC_number> <agent_name> proxy
The fields in this entry are described as follows:
<RPC_number>
The RPC number of the agent as it is specified in the /etc/services file or a directory service map or table.
<agent_name>
The agent name as it appears in the properties sheet for an element. Note that this is not na. <name>, but simply <name>.<agent_name> must identify an agent that is in a schema file that is loaded in the Console.
proxy
If the agent is a proxy agent, use the word proxy to indicate its proxy status.
AGENT Schema Section
The agent schemas for a specific type of device is configurable. The agent schemas should be listed in this section of the discover.conf file. The discover application will automatically activate the agent schemas for all the device types listed in this section along with the existing defaults. The configuration information has to be entered in a specific format. Following is an example of an entry in this section:
#
# AGENT SCHEMA MAPPING
#
<snm element type 1>
{
agentschema1
agentschema2
agentscheman
}
<snm element type 2>
{
agentschema1
agentschema2
agentscheman
}
<element type n>: These types are specified in the #OID section. <agentschema n>: Agent schema name. For example:
component.ssio
{
cpustat
diskinfo
}