Do You Need to Install Agents?

Depending on your network management needs, you do not have to install agents on machines in order to make effective use of the product . All Sun machines and most other machines that run on TCP/IP networks support protocols that enable the Console machine to obtain useful data from machines without agents.

The Console has the capability to manage agent-less machines through its proxy feature, working in conjunction with the ping and hostperf agents running on the Console machine. The proxy feature allows agents running on

one machine--the Console machine or any machine running agents--to respond as if they were running on another machine. This feature is described the Administration Guide.

Through use of the hostperf and ping proxy agents you can obtain the following information from a remote machine:

From the hostperf agent:

• number of CPU interrupts
• disk usage
• number of input and output packets
• percentage of CPU usage

All of the above items are expressed per unit of time.

From the ping agent:

• the reachability of a remote host
• round-trip time for a packet sent to a remote host

The information returned by the ping agent is analogous to that returned by the ping -s command.

You can use the hostperf and ping agents to send both data and event requests. You can save, browse, graph, and strip-chart data from a machine without agents in the same way that you manipulate data returned from a machine with host-resident agents.

Good reasons to install agents, rather than relying on the hostperf and ping proxies, are:

• You can obtain a far greater breadth and depth of information on each machine.
• You do not have a single point-of-failure (that is, the machine running the proxy agents).

If you install the SNMP agents, you gain the ability to set, as well as obtain, the values of parameters on a remote machine.

Proxy agents have uses other than obtaining data from machines that are not running agents. For example, they allow you to use the product to manage networks that use protocols other than TCP/IP or let you manage remote networks. Their ability to allow you to obtain data from agent-less machines is offered here as a consideration for your decision as to whether to install agents.

Overview of Agent Installation

The workstation running the Console (the "manager station") is the focal point for collecting and analyzing information. It gets the information from data collection programs (agents) usually running on remote machines.

The product software provides agents that run on Solaris 2.x systems and on SunOS 4.x systems. You use the getagents script to install agents on both types of systems.

Overview of the getagents Script

The getagents script allows a Sun workstation to run the product agents and proxy agents by editing system files (similar to what the installation script does) and copying agents, libraries, and the SNMP proxy agent schema from the manager station to another machine. The script makes backups of all system files that are modified.

Specifically, the getagents script:

• Copies the agents, schema files, libraries, and native SNMP agent files from the manager station.
• On a machine running Solaris 2.x, creates the /var/opt/SUNWconn/snm directory for log files. On a machine running SunOS 4.x, creates the /var/adm/snm directory for log files. (For a description of these log files, see the snm.conf(5) man page.)
• Under SunOS 4.x only, creates symbolic links from the libnetmgt.sa.2.0 and libnetmgt.so.2.0 shared library files to /usr/lib. These files are used by agent and manager applications. Under Solaris 2.x, the script creates symbolic links if the library files were installed in a location other than the default, /opt/SUNWconn/lib.

  If the link creation fails, an error message is printed, and you'll need to make the links yourself.

---

Note - Shared library files (or links to them) should be placed in /usr/lib. If you put them somewhere else, run ldconfig(8) with the library path names.

---

• On a machine running Solaris 2.x, creates a /etc/opt/SUNWconn/snm/snm.conf file if none exists, or updates the old one. On a machine running SunOS 4.x, creates a /etc/snm.conf file if none exists, or updates the old one. For a description of the snm.conf file, see the snm.conf(5) man page.
• Adds agent entries to /etc/rpc--see rpc(5).
• Adds SNMP definitions to the /etc/inet/services file for Solaris 2.x systems, or to the /etc/services file for SunOS 4.x systems.

  If you are running NIS/NIS+, you must manually add the agent entries to /etc/rpc and /etc/services on the NIS/NIS+ master. To update the rpc.bynumber and services maps on both the master and the server, see the "Updating NIS Maps or NIS+ Tables" on page 3-23 for instructions.

• Updates /etc/inet/inetd.conf under Solaris 2.x, or /etc/inetd.conf under SunOS 4.x and asks inetd(8C) to reread its configuration file. See the inetd.conf(5) man page.
• Creates a sample database file you can add to your management database on the manager station.
• On a machine running Solaris 2.x, creates the /var/opt/SUNconn/snm/snmp.hosts and /var/opt/SUNWconn/snm/snmp.traps files for use by the SNMP proxy agent. On a machine running SunOS 4.x, creates the /var/adm/snm/snmp.hosts and the /var/adm/snm/snmp.traps files for use by the SNMP proxy agent.

Copying Scenarios

There are various ways the manager station can make files available to other machines. Two common approaches are NFS and rcp(1). NFS is the recommended method, but not an option at every site. If rcp is used, the /.rhosts file on the manager station must contain the name of the remote (agent) machine, allowing the agent machine root access to the manager machine. Once you have installed the agents, you may remove the agent machine name from the manager's /.rhosts file to restore security.

Since the getagents script copies files across the network, it needs to know what access method is going to be used for the copy. The three basic scenarios are:

• The system has the the product distribution NFS mounted from the manager station. You do not want to copy the agents because you're going to run the agents over the mount.
• The system has the distribution NFS mounted from the manager station. You want to copy the agents because you're going to run the agents from a different file system.
• The distribution is not NFS mounted, so rcp is needed to copy the agents.

The programs do not use copy methods such as tftp(1).

The following sections specify the following procedures:

• Running the getagents script using an NFS mount on Solaris 2.x systems (page 4-10)
• Running the getagents script using an NFS mount on SunOS 4.x systems (page 4-5)
• Running the getagents script using rcp on Solaris 2.x systems (page 4-20)
• Running the getagents script using rcp on SunOS 4.x systems (page 4-15)

Running getagents Using an NFS Mount from SunOS 4.x Systems

In the following procedure, the local machine (agenthost) has the distribution files NFS mounted from the manager (mgrhost) station.

To run the getagents script using an NFS mount:

1. Log in as root on the manager station. Enter the following commands to export the filesystem and start the NFS daemons, if they are not already running:

mgrhost# exportfs -o ro /usr/snm mgrhost# /usr/etc/nfsd 8 mgrhost# /usr/etc/rpc.mountd

If the file /etc/exports does not exist on your system, as root, create the file and, in that file, enter the line: /usr/snm -ro and nothing else. Then, enter the nfsd and rpc.mountd commands as above and enter, in addition, exportfs -a.

2. Log in as root to the machine that will run the agents (this machine will be referred to as the "local machine").

3. Create a mountpoint on the local machine.

4. Mount the the product software on your local machine from the manager station (by default, in /usr/snm):

agenthost# mount mgrhost:/usr/snm <mountpoint>

5. Run the getagents script from the bin directory under the mountpoint you created on the local machine.

   The getagents script starts and asks for the name of the directory where the agents will be installed.

# <mountpoint>/bin/getagents -- Site/SunNet/Domain Manager 2.3 agent installation -- Copyright (c) 1990-1995 by Sun Microsystems, Inc. What is the name of the root directory where agents will be installed? Agents will be installed into the 'agents' subdirectory of the directory you specify. Type 'NFS' if you intend to run the agents via an NFS mount. [/usr/snm]

6. To run the agents over an NFS mount, enter NFS; to install the agents on the local system, press Return to accept the default, /usr/snm, or enter another path name.

---

Note - If you enter NFS, the getagents script asks for the name of the root directory under which the the product agents and libraries are located. Go to Step 9.

---

The getagents script asks if you want to create the agents directory.

/usr/snm/agents doesn't exist, should I create it? [y]

7. Press Return to accept the default, y.

   The getagents script asks for the name of the host where the agents are located.

OK, /usr/snm/agents was made. What is the name of the host where the agents are? Type Return if you have the directory NFS mounted: [localhost]

8. Press Return to accept the default, localhost.

   The getagents script asks for the name of the root directory under which the agents and libraries are located.

What is the name of the root directory under which the the product agents and libraries are located? []

9. Enter the name of the mountpoint you created in Step 3.

   The getagents copies agents from the manager station to the agent station, displays these agent files, then creates library links and asks if you want to install the Sun SNMP agent.

Backing up old library links in /usr/lib ... done. Creating library links into /usr/lib ... done. Would you like to install the Sun SNMP agent? [y]

10. Press Return to accept the default, y, to install the Sun SNMP agent, or enter n for no, if you do not want to install the Sun SNMP agent.

    Note - If you enter n, the getagents script creates the /etc/snm.conf file, then asks for the location of the database files. Go to Step 14.

    The getagents script displays several messages and information about community names, and then asks for the read community name.

Access to SNMP devices is controlled via community names. The default community names for this SNMP agent installation will be: read: public write: private You should change the write community name to a site specific name to control access to this system via the SNMP agent. You may also modify the read community name if desired. New read community name? [public]

11. Press Return to accept the default read community name, public, or enter a new read community name.

    The getagents script asks if you want to change the default write community name.

New write community name? [private]

12. Press Return to accept the default write community name, private, or enter a new write community name.

    The getagents script displays lines that must be added to the /etc/rc.local file, and asks if you want them to be added now.

To run the Sun SNMP agent at each reboot, the following lines need to be added to the end of /etc/rc.local: if [ -x /etc/init.snmpd ]; then /etc/init.snmpd start && echo 'Starting snmpd.' fi Would you like me to do this? [y]

13. Press Return to accept the default, y, or enter n for no. If you enter n, be sure to manually update the file after the installation. The getagents script creates the /etc/snm.conf file, then asks for the location of the database files.

Creating /etc/snm.conf ... done. By default, database and log files are placed under the directory /var/adm/snm which will be created during this installation. A minimum of 10Mb to 15Mb of free space in the default database location is recommended. If you would like to put the databases in an alternate directory by default, a link will be created from /var/adm/snm to the new location. The current usage for /var/adm/snm is: Filesystem kbytes used avail capacity Mounted on /dev/sd1g 20570 1139 17373 6% /var Would you like the databases to be written to a new default directory? [n]

14. Press Return to accept the default location for the database files,

    /var/adm/snm, or enter y to specify a different location. If you enter y, you will be prompted for the location for the database files. The getagents script asks for the location of the log files.

Some of the daemons create log files that can grow over 1 Mb each in size, depending on the number of nodes you are managing. The default directory for these log files is /var/adm/snm. Here is the current usage for /var/adm/snm: Filesystem kbytes used avail capacity Mounted on /dev/sd1g 20570 1139 17373 6% /var Would you like the log files to be written somewhere else (like /usr/snm/logs)? [n]

15. Press Return to accept the default location for the log files,

    /var/adm/snm, or enter y to specify a different location. If you enter y, you will be prompted for the location for the log files. The getagents script creates snmp files, updates other files, and displays a message that it has finished.

    You have installed the agents, and they are ready to be run and managed on this system.

Running getagents Using an NFS Mount from Solaris 2.x Systems

In the following procedure, the local machine (agenthost) has the distribution files NFS mounted from the manager (mgrhost) station.

To run the getagents script using an NFS mount:

1. Log in as root on the manager station. Enter the following commands to export the filesystem and start the NFS daemons, if they are not already running:

mgrhost# exportfs -o ro /usr/snm mgrhost# /usr/etc/nfsd 8 mgrhost# /usr/etc/rpc.mountd

If the file /etc/exports does not exist on your system, as root, create the file and, in that file, enter the line: /usr/snm -ro and nothing else. Then, enter the nfsd and rpc.mountd commands as above and enter, in addition, exportfs -a.

2. Log in as root to the machine that will run the agents (this machine will be referred to as the "local machine").

3. Create a mountpoint on the local machine.

4. Mount the the product software on your local machine from the manager station (by default, in /usr/snm):

agenthost# mount <mgrhost>:/usr/snm <mountpoint>

5. Run the getagents script from the bin directory under the mountpoint you created on the local machine.

   The getagents script starts and asks for the name of the directory where the agents will be installed.

# <mountpoint>/bin/getagents -- Site/SunNet/Domain Manager 2.3 agent installation -- Copyright (c) 1990-1995 by Sun Microsystems, Inc. What is the name of the root directory where agents will be installed? Agents will be installed into the 'agents' subdirectory of the directory you specify. Type 'NFS' if you intend to run the agents via an NFS mount. [/opt/SUNWconn/snm]

6. To run the agents over an NFS mount, enter NFS; to install the agents on the local system, press Return to accept the default, /opt/SUNWconn/snm, or enter another pathname.

---

Note - If you enter NFS, the getagents script asks for the name of the root directory under which the agents and libraries are located. Go to Step 9.

---

The getagents script asks if you want to create the agents directory.

/opt/SUNWconn/snm/agents doesn't exist, should I create it? [y]

7. Press Return to accept the default, y.

   The getagents script asks for the name of the host where the agents are located.

OK, /opt/SUNWconn/snm/agents was made. What is the name of the host where the agents are? Type Return if you have the directory NFS mounted: [localhost]

8. Press Return to accept the default, localhost.

   The getagents script asks for the name of the root directory under which the agents and libraries are located.

What is the name of the root directory under which the agents and libraries are located? []

9. Enter the name of the mountpoint you created in Step 3.

   The getagents script creates library links, then asks if you want to install the Sun SNMP agent.

Would you like to install the Sun SNMP agent? [y]

10. Press Return to accept the default, y, to install the Sun SNMP agent, or enter n for no, if you do not want to install the Sun SNMP agent.

    Note - If you enter n, the getagents script creates the /etc/opt/SUNWconn/snm/snm.conf file, then asks for the location of the database files. Go to Step 14.

    The getagents script displays several messages and information about community names, and then asks for the read community name.

Access to SNMP devices is controlled via community names. The default community names for this SNMP agent installation will be: read: public write: private You should change the write community name to a site specific name to control access to this system via the SNMP agent. You may also modify the read community name if desired. New read community name? [public]

11. Press Return to accept the default read community name, public, or enter a new read community name.

    The getagents script asks if you want to change the default write community name.

New write community name? [private]

12. Press Return to accept the default write community name, private, or enter a new write community name.

    The getagents script displays information about the init.snmpd script, and asks if you want the script to be added to the /etc/init.d directory now.

To run the Sun SNMP agent at each reboot, the init.snmpd startup/shutdown script needs to be added to the /etc/init.d directory. Would you like to add this script? [y]?

13. Press Return to accept the default, y, or enter n for no. If you enter n, be sure to manually add the script after the installation; see the snmpd man page for instructions on how to add the script.

    The getagents script creates the /etc/opt/SUNWconn/snm/snm.conf file, then asks for the location of the database files.

Creating /etc/opt/SUNWconn/snm/snm.conf ... done. By default, database and log files are placed under the directory /var/opt/SUNWconn/snm which will be created during this installation. A minimum of 10Mb to 15Mb of free space in the default database location is recommended. If you would like to put the databases in an alternate directory by default, a link will be created from /var/opt/SUNWconn/snm to the new location. The current usage for /var/opt/SUNWconn/snm is: Filesystem kbytes used avail capacity Mounted on /dev/dsk/c0t3d0s0 20570 1139 17373 6% /var Would you like the databases to be written to a new default directory? [n]

14. Press Return to accept the default location for the database files,

    /var/opt/SUNWconn/snm, or enter y to specify a different location. If you enter y, you will be prompted for the location for the database files. The getagents script asks for the location of the log files.

Some of the the product daemons create log files that can grow over 1 Mb each in size, depending on the number of nodes you are managing. The default directory for these log files is /var/opt/SUNWconn/snm. Here is the current usage for /var/opt/snm: Filesystem kbytes used avail capacity Mounted on /dev/dsk/c0t3d0s0 20570 1139 17373 6% /var Would you like the log files to be written somewhere else (like /usr/snm/logs)? [n]

15. Press Return to accept the default location for the log files,

    /var/opt/SUNWconn/snm, or enter y to specify a different location. If you enter y, you will be prompted for the location for the log files. The getagents script creates snmp files, updates other files, and displays a message that it has finished.

    You have installed the agents, and they are ready to be run and managed on this system.

Running getagents Using rcp for SunOS 4.x Systems

The following procedure uses rcp to copy agents from mgrhost (the manager station) to agenthost (the "local host").

To run the getagents script using rcp:

1. Set up the manager station to allow root access across the network for the host(s) that will be running getagents (add "agenthost" to list of trusted hosts).

mgrhost# cat >>/.rhosts agenthost ^D

If /.rhosts does not exist, enter touch /.rhosts prior to the preceding command.

2. Copy getagents from the manager station to the local machine.

mgrhost# rlogin agenthost Password: SunOS Release 4.1.1 (AGENTHOST) #1: Wed May 6 12:30:46 PDT 1992 agenthost# rcp mgrhost:/usr/snm/bin/getagents /tmp

3. Run the getagents script. (The following instructions assume that you have copied getagents to /tmp on the local host, although you may copy it to any directory that is writable by root.)

   The getagents script starts and asks for the name of the directory where the agents will be installed.

agenthost# /tmp/getagents -- Site/SunNet/Domain Manager 2.3 agent installation -- Copyright (c) 1990-1995 by Sun Microsystems, Inc. What is the name of the root directory where agents will be installed? Agents will be installed into the 'agents' subdirectory of the directory you specify. Type 'NFS' if you intend to run the agents via an NFS mount. [/usr/snm]

4. Press Return to accept the default, /usr/snm. The getagents script asks if you want to create this directory.

5. Press Return to accept the default, y (for yes, create the directory). The getagents script asks for the name of the host where the agents are located.

OK, /usr/snm/agents was made. What is the name of the host where the agents are? Type Return if you have the directory NFS mounted: [localhost]

6. Enter the name of the manager station.

   The getagents script asks for the name of the root directory on the manager station under which the agents and libraries are located.

What is the name of the root directory on mgrhost under which the the product agents and libraries are located? [/usr/snm]

7. Press Return to accept the default, /usr/snm or specify a different directory if a non-default directory was used on the manager station. The getagents script continues and installs the agents. The getagents script then asks if you want to install the Sun SNMP agent.

Getting the agents ... done. Here are the agents now in agenthost:/usr/snm/agents - na.activity na.hostif na.ippath na.lpstat na.snmp na.diskinfo na.hostmem na.iproutes na.ping na.snmp-trap na.etherif na.hostperf na.layers na.rpcnfs na.sync na.event na.iostat na.logger na.sample na.traffic Getting the libraries ... done. Creating library links into /usr/lib ... done. Would you like to install the Sun SNMP agent? [y]

8. Press Return to accept the default, y, to install the Sun SNMP agent, or enter n for no, if you do not want to install the Sun SNMP agent.

---

Note - If you enter n, the getagents script creates the /etc/snm.conf file, then asks for the location of the database files. Go to Step 12.

---

The getagents script displays several messages and information about community names, and then asks for the read community name.

Access to SNMP devices is controlled via community names. The default community names for this SNMP agent installation will be: read: public write: private You should change the write community name to a site specific name to control access to this system via the SNMP agent. You may also modify the read community name if desired. New read community name? [public]

9. Press Return to accept the default read community name, public, or enter a new read community name.

   The getagents script asks if you want to change the default write community name.

New write community name? [private]

10. Press Return to accept the default write community name, private, or enter a new write community name.

    The getagents script displays lines that must be added to the /etc/rc.local file, and asks if you want them to be added now.

To run the Sun SNMP agent at each reboot, the following lines need to be added to the end of /etc/rc.local: if [ -x /etc/init.snmpd ]; then /etc/init.snmpd start && echo 'Starting snmpd.' fi Would you like me to do this? [y]

11. Press Return to accept the default, y, or enter n for no. If you enter n, be sure to manually update the file after the installation. The getagents script creates the /etc/snm.conf file, then asks for the location of the database files.

Creating /etc/snm.conf ... done. By default, database and log files are placed under the directory /var/adm/snm which will be created during this installation. A minimum of 10Mb to 15Mb of free space in the default database location is recommended. If you would like to put the databases in an alternate directory by default, a link will be created from /var/adm/snm to the new location. The current usage for /var/adm/snm is: Filesystem kbytes used avail capacity Mounted on /dev/sd1g 20570 1139 17373 6% /var Would you like the databases to be written to a new default directory? [n]

12. Press Return to accept the default location for the database files,

    /var/adm/snm, or enter y to specify a different location. If you enter y, you will be prompted for the location for the database files. The getagents script asks for the location of the log files.

Creating /var/adm/snm ... done. Some of the daemons create log files that can grow over 1 Mb each in size, depending on the number of nodes you are managing. The default directory for these log files is /var/adm/snm. Here is the current usage for /var/adm/snm: Filesystem kbytes used avail capacity Mounted on /dev/sd1g 20570 1139 17373 6% /var Would you like the log files to be written somewhere else (like /usr/snm/logs)? [n]

13. Press Return to accept the default location for the log files,

    /var/adm/snm, or enter y to specify a different location. If you enter y, you will be prompted for the location for the log files. The getagents script creates snmp files, updates other files, and displays a message that it has finished.

    You have installed the agents, and they are ready to be run and managed on this system.

    Note - If you previously modified the /.rhosts file on the manager station to temporarily allow root access to other hosts, you should now remove the entries to prevent future security breaches.

Running getagents Using rcp for Solaris 2.x Systems

The following procedure uses rcp to copy agents from mgrhost (the manager station) to agenthost (the "local host").

To run the getagents script using rcp:

1. Set up the manager station to allow root access across the network for the host(s) that will be running getagents (add "agenthost" to list of trusted hosts).

mgrhost# cat >>/.rhosts agenthost ^D

2. Copy getagents from the manager station to the local machine.

mgrhost# rlogin agenthost Password: SunOS Release 5.3 (AGENTHOST): January 1994 agenthost# rcp mgrhost:/usr/snm/bin/getagents /tmp

3. Run the getagents script. (The following instructions assume that you have copied getagents to /tmp on the local host, although you may copy it to any directory that is writable by root.)

   The getagents script starts and asks for the name of the directory where the agents will be installed.

agenthost# /tmp/getagents -- Site/SunNet/Domain Manager 2.3 agent installation -- Copyright (c) 1990-1995 by Sun Microsystems, Inc. What is the name of the root directory where agents will be installed? Agents will be installed into the 'agents' subdirectory of the directory you specify. Type 'NFS' if you intend to run the agents via an NFS mount. [/opt/SUNWconn/snm]

4. Press Return to accept the default, /opt/SUNWconn/snm or enter a different pathname if you want to use a non-default directory. The getagents script asks if you want to create the directory (default or specified by you).

5. Press Return to accept the default, y (for yes, create the directory). The getagents script asks for the name of the host where the agents are located.

OK, /opt/SUNWconn/snm/agents was made. What is the name of the host where the agents are? Type Return if you have the directory NFS mounted: [localhost]

6. Enter the name of the manager station.

   The getagents script asks for the name of the root directory on the manager station under which the agents and libraries are located.

What is the name of the root directory on mgrhost under which the agents and libraries are located? [/usr/snm]

7. Press Return to accept the default, /usr/snm or specify a different directory if a non-default directory was used on the manager station. The getagents script continues and installs the agents. The getagents script then asks if you want to install the Sun SNMP agent.

Getting the agents ... done. Here are the agents now in agenthost:/opt/SUNWconn/snm/agents - na.activity na.hostif na.ippath na.lpstat na.snmp-trap na.diskinfo na.hostmem2 na.iproutes na.ping na.sync na.etherif2 na.hostperf na.layers2 na.rpcnfs na.traffic na.event na.iostat2 na.logger na.snmp Getting the libraries. Would you like to install the Sun SNMP agent? [y]

8. Press Return to accept the default, y, to install the Sun SNMP agent, or enter n for no, if you do not want to install the Sun SNMP agent.

---

Note - If you enter n, the getagents script creates the /etc/opt/SUNWconn/snm/snm.conf file, then asks for the location of the database files. Go to Step 12.

---

The getagents script displays several messages and information about community names, and then asks for the read community name.

Access to SNMP devices is controlled via community names. The default community names for this SNMP agent installation will be: read: public write: private You should change the write community name to a site specific name to control access to this system via the SNMP agent. You may also modify the read community name if desired. New read community name? [public]

9. Press Return to accept the default read community name, public, or enter a new read community name.

   The getagents script asks if you want to change the default write community name.

New write community name? [private]

10. Press Return to accept the default write community name, private, or enter a new write community name.

    The getagents script displays information about the init.snmpd script, and asks if you want the script to be added to the /etc/init.d directory now.

To run the Sun SNMP agent at each reboot, the init.snmpd startup/shutdown script needs to be added to the /etc/init.d directory. Would you like to add this script? [y]?

11. Press Return to accept the default, y, or enter n for no. If you enter n, be sure to manually add the script after the installation; see the snmpd man page for instructions on how to add the script.

    The getagents script creates the /etc/opt/SUNWconn/snm/snm.conf file, then asks for the location of the database files.

Creating /etc/opt/SUNWconn/snm/snm.conf ... done. By default, database and log files are placed under the directory /var/opt/SUNWconn/snm which will be created during this installation. A minimum of 10Mb to 15Mb of free space in the default database location is recommended. If you would like to put the databases in an alternate directory by default, a link will be created from /var/opt/SUNWconn/snm to the new location. The current usage for /var/opt/SUNWconn/snm is: Filesystem kbytes used avail capacity Mounted on /dev/dsk/c0t3d0s0 20570 1139 17373 6% /var Would you like the databases to be written to a new default directory? [n]

12. Press Return to accept the default location for the database files,

    /var/opt/SUNWconn/snm, or enter y to specify a different location. If you enter y, you will be prompted for the location for the database files. The getagents script asks for the location of the log files.

Creating /var/opt/SUNWconn/snm ... done. Some of the daemons create log files that can grow over 1 Mb each in size, depending on the number of nodes you are managing. The default directory for these log files is /var/opt/SUNWconn/snm. Here is the current usage for /var/opt/SUNWconn/snm: Filesystem kbytes used avail capacity Mounted on /dev/dsk/c0t3d0s0 20570 1139 17373 6% /var Would you like the log files to be written somewhere else (like /usr/snm/logs)? [n]

13. Press Return to accept the default location for the log files,

    /var/opt/SUNWconn/snm, or enter y to specify a different location. If you enter y, you will be prompted for the location for the log files. The getagents script creates snmp files, updates other files, and displays a message that it has finished.

    You have installed the agents, and they are ready to be run and managed on this system.

    Note - If you previously modified the /.rhosts file on the manager station to temporarily allow root access to other hosts, you should now remove the entries to prevent future security breaches.

The Next Step...

After you have installed agents, the next step is to start the Console and create a management database of network elements that you intend to manage. See the Administration Guide for more information.