NAME
v2install - generate SNMPv2 configuration files for agents and managers
SYNOPSIS
v2install <host name>
DESCRIPTION
The v2install utility generates the SNMPv2 configuration files for a given list of agents and managers, and copies them to the /etc/opt/snm/{agent|manager} directory for Solaris 2.x and /etc/snm/{agent|manager} for Solaris 1.x.
There are no options to the v2install command.
INPUT
Three files are required by v2install; all must be present but may be empty, depending on which manager files are being generated. The file agents contains a list of agents, the file mgrs.v1, contains a list of SNMPv1 managers, and mgrs.v2 contains a list of SNMPv2 managers.
Note: The mgrs.v2 and agents files should be present because information is shared between SNMPv2 agents and managers that must be reflected in their configuration files. The mgrs.v1 file is necessary only if SNMPv1 managers will be used with bilingual agents.
agents
lists address information for each agent. The format is as follows:
IP-address Nodename
where
IP-address is the dotted decimal version of the IP address of the agent (i. e., 128.169.4.16), Nodename is the alias string for the IP-address (i. e., myserver). Each entry must begin on a separate line.
mgrs.v1
lists any community strings---with read or read/write privileges - - - that should be included on each agent. Nothing extra is generated for the manager configuration files.
Note: The community strings found in snmpv2d.conf(5) are ignored in bilingual agents. The entries in mgrs.v1 are used to generate the appropriate parties for SNMPv1 communities in a bilingual system. The format is as follows:
IP-addr Nodename read-community write-community where
IP-addr is the dotted decimal version of the IP address of the manager (i. e., 128.169.4.16), Nodename is the alias string for the IP-addr (i. e., myserver),
read-community is the community name, found in the snmpv2d.conf(5) file, that defines the read access privileges for this manager, and
write-community is the community name, found in the snmpv2d.conf(5) file, that defines the write access privileges for this manager. Each entry must begin on a separate line.
mgrs.v2
lists address information for each manager. The format is as follows:
IP-address Nodename
where
IP-address is the dotted decimal version of the IP address of the manager (i. e., 128.169.4.16), Nodename is the alias string for the IP-address (i. e., myserver). Each entry must begin on a separate line.
OUTPUT
The v2install tool will place each group of configuration files in a hostname directory based on the Nodename in either configs/nodename/agent or configs/nodename/manager, depending on which files were supplied. There will be two parties generated for each agent-manager pair.
Note: All managers will share a common noauth/nopriv pair of parties. The first two parties in the agent's table will always be noauth/nopriv parties with party names of
initialPartyId. IP-address. 1
and
initialPartyId. IP-address. 2
Each manager address will have the following files generated for it:
mgr.pty - party configuration file
acl.pty - access control configuration file context.pty - MIB context configuration file
mgr.cnf - manager configuration file view.pty -MIB view configuration file
Each agent address will have the following files generated for it:
agt.pty - party configuration file
acl.pty - access control configuration file context.pty - MIB context configuration file snmpv2d.conf - snmpv2d configuration file view.pty - MIB view configuration file
EXAMPLES
Example agents file:
128.169.4.16 myserver
128.169.4.47 screamer
Example mgrs.v2 file:
128.169.4.16 myserver
128.169.4.20 bossie
128.169.4.15 murvle15
128.169.4.25 wildman
Example mgrs.v1 file:
128.169.4.16 myserver public TopSecret 128.169.4.47 screamer ten30 private
128.169.4.15 murvle15 sparc woof
128.169.4.25 wildman common secret
FILES
Input:
agents - list of agents
mgrs.v1 - list of managers that are SNMPv1 mgrs.v2 - list of managers that are SNMPv2
Output:
managers:
mgr.pty - party configuration file acl.pty - access control configuration file context.pty - MIB context configuration file mgr.cnf - manager configuration file view.pty - MIB view configuration file
agents:
agt.pty - party configuration file acl.pty - access control configuration file context.pty - MIB context configuration file
snmpv2d.conf - snmpv2d configuration file view.pty - MIB view configuration file
SEE ALSO
acl.pty(5), agt.pty(5), context.pty(5), mgr.cnf(5), mgr.pty(5), snmpv2d.conf(5), view.pty(5), SNMP RFCs (RFC1155 RFC1157 RFC1212 RFC1213 RFC1215, RFCs 1441-1452)
KNOWN BUGS
Blank lines are not tolerated.
Duplicate Nodenames are not detected.
Randomly generated keys are not always unique. A better seeding function is needed.