Overview

The following is a summary of the steps to install the software. Complete procedures for these steps are given following this section.

Before starting installation, make sure that you have verified installation requirements as specified in "Installation Requirements" on page 1-1.

1. Insert the product CD-ROM in a local or remote CD drive.

2. Install the software using /usr/sbin/pkgadd.

3. Finish installation.

   Finishing installation includes:

• Updating the Network Information Service (NIS/NIS+) maps/tables, if you are running NIS/NIS+;
• Modifying your PATH to point to the executables;
• Setting up access to on-line help and man pages;
• Verifying installation.

Inserting and Accessing the CD-ROM

To install the software you must have either a local CD-ROM drive or a drive that is accessible over a network.

This section describes how to insert the CD-ROM in the drive and, if you are using a remote CD-ROM drive, how to export or share the CD-ROM file system.

---

Note - Your target machine for installing the software must always be a system running SunOS 5.4 (Solaris 2.4) or later. You can use a remote SunOS 4.1.x or 5.x system to provide the CD-ROM drive.

---

· Inserting Your CD-ROM

1. Remove the CD-ROM from its plastic case and place the CD-ROM in its caddy.

2. Insert the caddy into the drive slot. (Make sure the CD drive is powered on.)

Proceed to the following section if you are accessing a locally installed CD drive. Go to "Mounting the CD-ROM from a Remote CD Drive" if you are accessing a remotely installed CD drive.

---

Note - Unless noted otherwise, you must log in as or become root to perform all of the following procedures.

---

· Mounting the CD-ROM from a Local CD Drive

There is no explicit mounting of the CD-ROM filesystem for a locally-attached CD drive under Solaris 2.2 or later. When you insert the CD into the drive, the CD-ROM filesystem is automatically mounted. In the unlikely event that volume management--the feature that provides this automatic mounting--is disabled, you must, as root, perform the following commands:

1. Make the directory to mount the CD-ROM if it does not already exist:

hostname# mkdir /cd

2. Mount the CD-ROM:

hostname# mount -r /dev/dsk/c0t6d0s0 /cd

Go to "Installing the Software" on page 3-8.

· Mounting the CD-ROM from a Remote CD Drive

To install the software on a machine that does not have its own CD-ROM drive, you must perform some activities on the remote machine (the machine with the CD-ROM device) and some on the local machine (the machine onto which you are installing the software). Be sure you follow the directions carefully. The instructions specify on which machine you must perform the steps.

· Exporting or Sharing from the Remote Machine

Because you are mounting the software from a remote CD-ROM, you must first export or share it from the remote machine. The methods are slightly different for remote SunOS 4.x, SunOS 5.1 (Solaris 5.1), and SunOS 5.2 or later (Solaris 5.2 or later) systems and are described in separate procedures.

Exporting from a Remote SunOS 4.x System Perform the following steps on the remote machine:

1. Make a directory on which to mount the CD-ROM if it does not already exist:

hostname# mkdir /cd

2. Mount the CD-ROM on the remote machine:

hostname# mount -t hsfs -r /dev/sr0 /cd

3. If the entry is not already present, edit the /etc/exports file by adding the following line:

/cd -ro

4. Export the directory from the remote machine:

hostname# exportfs /cd

5. If they are not already running, start the NFS mount daemons by entering the following commands:

hostname# nfsd 8 hostname# rpc.mountd &

6. Check to see that the machine is exporting the directory by entering the

   exportfs command. The screen should show the /cd directory:

hostname# exportfs . . . /cd

Go to "Mounting the Remote CD-ROM on the Local Machine" on page 3-7.

Sharing from a Remote SunOS 5.1 System Perform the following steps on the remote machine:

1. On the remote machine, make a directory on which to mount the CD-ROM if it does not already exist:

hostname# mkdir /cd

2. Mount the CD-ROM on the remote machine:

hostname# mount -r /dev/dsk/c0t6d0s0 /cd

3. If they are not already running, start the NFS daemons by entering the following commands:

hostname# /usr/lib/nfs/nfsd 8 hostname# /usr/lib/nfs/mountd

4. Share the directory from the remote machine:

hostname# share -F nfs -o ro /cd

5. Check to see that the machine is exporting the directory by entering the

   share command. The screen should show the /cd directory:

hostname# share . . . - /cd ro " " . . .

It takes a few minutes for this shared directory to become available over the network.

Sharing from a Remote SunOS 5.2 System Perform the following steps on the remote machine:

1. If they are not already running, start the NFS daemons by entering the following commands:

hostname# /usr/lib/nfs/nfsd 8 hostname# /usr/lib/nfs/mountd

2. Share the directory from the remote machine by entering the command:

hostname# share -F nfs -o ro /cdrom/sunnet_manager_2_3

3. Ensure that the machine is exporting the directory by entering the share command. The screen should show the /cdrom/sunnet_manager_2_3 directory:

hostname# share . . . - /cdrom/sunnet_manager_2_3 ro " " . . .

It takes a few minutes for this shared directory to become available over the network.

· Mounting the Remote CD-ROM on the Local Machine

Having exported or shared the remote CD-ROM, you can now mount it on your local machine. Perform the following step on the local machine:

• Use the automounter to automatically mount the exported or shared filesystem.

  For remote SunOS 4.x and SunOS 5.1 systems enter:

hostname# cd /net/<remote_machine>/cd

For remote Solaris 2.2 or later systems enter:

hostname# cd /net/<remote_machine>/cdrom/sunnet_manager_2_3

• If the automounter is not running on your machine, do the following on your local machine:

1. Make a directory on which to mount the CD-ROM if it does not already exist:

hostname# mkdir /cd

2. Mount the remote directory on /cd:

   For remoteSunOS 4.1.x and SunOS 5.1 systems enter:

hostname# mount -r -F nfs <remote_machine>:/cd /cd

For SunOS 5.2 or later systems enter:

hostname# mount -r -F nfs <remote_machine>:/cdrom/sunnet_manager_2_3 /cd

Installing the Software

Whether you have a directly connected or remotely accessed CD-ROM player, you can now run the pkgadd command. The running of pkgadd for the product can take 15 minutes when installing from a directly connected CD-ROM player, or minutes longer for a remotely accessed CD-ROM player on a busy network.

1. Invoke the pkgadd command.

   a. If you want to install the packages in the default directory, /opt, enter the following command:

hostname# /usr/sbin/pkgadd -d <pathname>

The replacement for <pathname> depends on you method of accessing your CD-ROM player. The possibilities are as follows:

• If you statically mount (using the mount command) your CD-ROM directory, whether it be local or remote, use /cd.
• If you are running Solaris 2.2 or later, have vold running (the default case), and have a local CD-ROM player, use /cdrom/sunnetmanager_2_3.
• If you use the automounter and are accessing a remote CD-ROM player connected to a remote SunOS 4.x machine or a Solaris 2.x machine that is not running vold, use /net/<remote_hostname>/cd.
• If you use the automounter and are accessing a remote CD-ROM player connected to a Solaris 2.2 or later machine that is running vold, use /net/<remote_hostname>/cdrom/sunnetmanager_2_3.

b. If you want to install the packages in a directory other than the default, enter the following command:

hostname# /usr/sbin/pkgadd -d <pathname> -a none

...where <pathname> is the pathname you would supply for the command shown in Step 1a.

With the latter command, pkgadd prompts you for the destination directory prior to installing each package. Be sure to enter the same base directory for each package you install. If you choose a heavy-option AnswerBook installation, you do not have use your base directory for AnswerBook.

After invoking either of the above commands, you receive a list of packages available for installation:

---

Note - Be sure to install the Site/SunNet/Domain Manager packages (SUNWsnm*) before the Cooperative Consoles packages (SUNWcc*). Failure to do so will result in error.

---

The following packages are available: 1 SUNWabsnm Site/SunNet/Domain Manager 2.3 AnswerBook 2 SUNWsnmag Site/SunNet/Domain Manager 2.3 Agents & Libraries 3 SUNWsnmct Site/SunNet/Domain Manager 2.3 Core Tools 4 SUNWsnmpd Site/SunNet/Domain Manager 2.3 SNMP daemon 5 SUNWsnmla Site/SunNet/Domain Manager 2.3 Network Layout Asst (Domain Manager sites only) 6 SUNWccfg Cooperative Consoles 1.2 - Configuration Tool (all Site/SunNet/Domain Manager sites) 7 SUNWccrcv Cooperative Consoles 1.2 - Receiver Application (all Site/SunNet/Domain Manager sites) 8 SUNWccsnd Cooperative Consoles 1.2 - Sender Daemon (Domain Manager sites only) Select package(s) you wish to process (or 'all' to process all packages). (default: all) [?,??,q]:

2. Press Return to accept the default to install all packages.

   You receive the following display:

Processing package instance <SUNWabsnm> from </cd> Site/SunNet/Domain Manager 2.3 AnswerBook <Copyright notice> Using </opt or other directory> as the package base directory. The installation options are as follows: Option: Description: -------------------------------------------- 1. nil: less than 1 Megabyte disk space required [slowest performance]. 2. heavy: 34.26 Megabytes disk space required [best performance]. Enter the number of an installation option from the list above (1 or 2). Select an installation option: 1

3. Enter your choice for Answerbook, 1 or 2.

   The following is the output if you select 1 for the nil option.

Installation option: nil selected. The next request for input asks you to specify the parent directory of AnswerBook Make sure to choose a parent directory on a file system big enough to accommodate all the files to be moved for the INSTALL OPTION you selected. Specify the parent of the AnswerBook home directory: <your directory choice> ## Processing package information. ## Processing system information. ## Verifying package dependencies. ## Verifying disk space requirements. ## Checking for conflicts with packages already installed. ## Checking for setuid/setgid programs. This package contains scripts which will be executed with super-user permission during the process of installing this package. Do you want to continue with the installation of this package [y,n,?] y Installing Site/SunNet/Domain Manager 2.3 AnswerBook as <SUNWabsnm> ## Installation of part 1 of 1 is complete. ## Executing postinstall script. Installation of <SUNWabsnm> was successful.

You then receive the display for the next package:

Processing package instance <SUNWsnmag> from </cd> Site/SunNet/Domain Manager Agents & Libraries (sparc) 2.3 <Copyright notice> You will now need to answer a few questions to configure Site/SunNet/Domain Manager for your workstation. Some of the Site/SunNet/Domain Manager daemons create log files which can grow to over 1 Meg each in size (depending on the number of nodes being managed). The directory where they reside should allow for appropriate free space. Please enter the location for the log files [/var/opt/SUNWconn/snm]:

4. Press Return to accept the default location (/var/opt/SUNWconn/snm) for log files or enter an absolute pathname if you do not want the default. The installation script responds:

You have entered the following values: Log File location: /var/opt/SUNWconn/snm (or your own choice) Is this correct (y/n) [y]:

5. Press Return to accept the log file location as displayed by the script or enter n and enter the log file location you want.

   After you accept or enter a log file location, the script proceeds:

## Processing package information. ## Processing system information. 3 package pathnames are already properly installed. ## Verifying disk space requirements. ## Checking for conflicts with packages already installed. The following files are already installed on the system and are being used by another package: /etc/inet/inetd.conf /etc/inet/services /etc/rpc Do you want to install these conflicting files [y,n,?,q]

6. Enter y to install the specified files.

   To run correctly, the files specified by the script need to be modified.

   After you install the "conflicting" files, the script proceeds:

## Checking for setuid/setgid programs. This package contains scripts which will be executed with super-user permission during the process of installing this package. Do you want to continue with the installation of this package [y,n,?] y

7. Enter y to continue with installation.

   The script responds:

Installing Site/SunNet/Domain Manager Agents & Libraries as <SUNWsnmag> ## Installing part 1 of 1. <List of files> Modifying /etc/inet/inetd.conf Modifying /etc/inet/services Modifying /etc/rpc [ verifying class <sed> ] ## Executing postinstall script. updating /etc/opt/SUNWconn/snm/snm.conf Updating /etc/inet/inetd.conf to reflect SNM's installation directory /var/opt/SUNWconn/snm created Instructing inetd to re-read config file If you're running NIS/NIS+, you need to update the services map/table. Installation of <SUNWsnmag> was successful.

Following installation of the SUNWsnmag package, the script continues:

Processing package instance <SUNWsnmct> from </cd> Site/SunNet/Domain Manager Core Tools (sparc) 2.3 <Copyright notice> You will now need to answer a few questions to configure Site/SunNet/Domain Manager for your workstation. By default, database files are placed under the directory /var/opt/SUNWconn/snm. A minimum of 10Mb to 15Mb of free space is recommended for this usage. Please enter the location for the databases [/var/opt/SUNWconn/snm]:

8. The licensing installation begins by listing the phone numbers to call to obtain a license password. The script then displays:

The license distributor will ask you for the following information: Server Name : <server name> Host ID : <host id name> You will also need to provide the Serial Number and the product name from the license certificate. Please Hit Return to continue .....

After you press Return, you will be asked:

You can install the license now or after the installation or the product. If you choose to install the license later, you'll need to run the script install_snm_license. Do you want to install the license now (y/n) [y]:

Press return to continue with the license installation.

Please enter the License Password for this node:

When you call the license distribution center, you must do the following:

a. The operator will provide you with a license password which you must type in at the prompt shown above.

b. Give the operator your serial number from your license certificate, product name and version, host name, and host ID.

c. The operator will ask you for your company address, phone number, and e-mail address.

After you type in the license password that the operator gives you, you will receive the following prompt:

Is this a demo license (y/n) [n]:

If you enter y, then you will be prompted to enter the expiration date of the demo license. For example:

Please enter the expiration date (dd-mmm-yyyy): 01-jan-1995

The following product selection is displayed:

Please choose the name of the product from the following list. The name of the product s available with the license certificate that you received along with the serial number. Type 1 for Site Manager Type 2 for SunNet Manager Type 3 for Domain Manager Type 4 for University Wide Domain Manager Please enter the number corresponding to the product.

Currently the University Wide Domain Manager is only available for Universities. It is a special licensing variety of the Site/SunNet/Domain Manager product. If you are installing University Wide Domain Manager licensing, you need the network domain name in order to complete the licensing procedure.

Please enter your network domain(eg,. leland.stanford.edu):

After selecting a products, you are prompted for the database location. By default, databases are placed under the /var/opt/SunWconn/snm directory. A minimum of 10Mb of free space is recommended:

Please enter the location for the SNM databases [/var/opt/SUNWconn/snm]:

9. Press Return to accept the database location as displayed by the script or enter n and enter the location you want.

   After you accept or enter a database location, the script proceeds:

You have entered the following values: Database location: /var/opt/SUNWconn/snm (or your own choice) Is this correct (y/n) [y]:

10. Press Return to accept the database location as displayed by the script or enter n and enter the database location you want.

    After you accept or enter a database location, the script proceeds:

## Processing package information. ## Processing system information. 10 package pathnames are already properly installed. ## Verifying package dependencies. ## Verifying disk space requirements. ## Checking for conflicts with packages already installed. ## Checking for setuid/setgid programs. The following files are being installed with setuid and/or setgid permissions or are overwriting files which are currently setuid/setgid: /opt/SUNWconn/snm/bin/snm_ip_discover <setuid root> /opt/SUNWconn/snm/bin/snm_ipx_discover <setuid root> Do you want to install these setuid/setgid files [y,n,?,q] y

11. Enter y to install the specified file.

    The snm_ip_discover and snm_ipx_discover programs are an important part of the product.

    Following this, you receive:

This package contains scripts which will be executed with super-user permission during the process of installing this package. Do you want to continue with the installation of this package [y,n,?] y

12. Enter y to continue with installation.

    Following your y input, the script proceeds:

Installing Site/SunNet/Domain Manager Core Tools as <SUNWsnmct> <List of files> Installation of <SUNWsnmct> was successful. Processing package instance <SUNWsnmpd> from </cd> Site/SunNet/Domain Manager SNMP daemon (sparc) 2.3 <Copyright notice> You will now need to answer a few questions to configure the SNMP agent for your workstation. 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]:

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

    The script proceeds:

New write community name? [private]:

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

    After accepting read/write community name defaults or entering names that you want, you receive:

You should also change the system specific information. The discover tool uses the description information when creating icons. (ex. sparcstation 10, ipx, sun3, sc2000) New system description? [Sun SNMP Agent, SPARCStation 10]:

The pkgadd script attempts to find out your machine architecture. Most customers, particularly those running Sun machines, will be able to press Return to accept the default.

The script proceeds:

New system contact? [System administrator]: New system location? [System administrator's office]:

15. Enter a name and location for the preceding two prompts.

    The values you specify here are for your own use and for the use of other network administrators. Enter names and locations according to the conventions followed in your network. If you have no conventions, enter information that will be meaningful on your network.

    After entering a contact and location, you receive:

You have entered the following values: SNMP read community name: public SNMP write community name: private SNMP system description: Sun SNMP Agent, SPARCStation 10 SNMP system contact: System administrator SNMP system location: System administrator's office Is this correct (y/n) [y]:

16. Press Return to accept the SNMP information as displayed by the script or enter n and enter the values you want.

    After you confirm the SNMP information, the script proceeds:

## Processing package information. ## Processing system information. 8 package pathnames are already properly installed. ## Verifying disk space requirements. ## Checking for conflicts with packages already installed. ## Checking for setuid/setgid programs. This package contains scripts which will be executed with super-user permission during the process of installing this package. Do you want to continue with the installation of this package [y,n,?] y

17. Enter y to continue with installation.

    Following your y input, the script proceeds:

Installing Site/SunNet/Domain Manager SNMP daemon as <SUNWsnmpd> ## Installing part 1 of 1. /etc/init.d/init.snmpd /etc/opt/SUNWconn/snm/snmpd.conf /opt/SUNWconn/snm/agents/snmpd /opt/SUNWconn/snm/agents/snmpd.conf /opt/SUNWconn/snm/agents/snmpv2d /opt/SUNWconn/snm/agents/snmpv2d.conf.t /opt/SUNWconn/snm/agents/sun.mib [ verifying class <none> ] /etc/rc2.d/K25snmpd <linked pathname> /etc/rc3.d/S25snmpd <linked pathname> ## Executing postinstall script. Updating /etc/opt/SUNWconn/snm/snmpd.conf with community name information... Updating /etc/init.d/init.snmpd with snmpd agent location... Starting snmpd.

18. A final prompt is displayed associated with the licensing. Enter y to continue with installation.

I am installing licensing for <product name> Now. ok?

licensing for <product name> 2.3 is completed successfully .... Installation of <SUNWsnmpd> was successful.

When pkgadd is finished, it returns to its initial display of packages. You Enter q to exit the command. (Pressing Return to re-run pkgadd does no harm, but is a waste of your time.)

19. When you finish running pkgadd, eject the CD-ROM, using one of the following sets of commands:

    a. For Solaris 2.2 or later systems, enter:

hostname# cd / hostname# eject

b. For SunOS 4.x and SunOS 5.1 systems, enter:

hostname# cd / hostname# umount /cdrom hostname# eject cdrom

Finishing Installation

Finishing installation includes these tasks:

• Updating NIS/NIS+ maps/tables, if you are running NIS/NIS+
• Setting up access to on-line help and man pages
• Defining the SNMHOME variable, if you installed in a non-default directory

---

Note - If you installed the software on a server, you can run the Console from a client. To do so, run the getagents or pkgadd program as described in the next chapter, and specify that you are using an NFS mount. Because of local site variations, you may need to modify environment variables on the client before all the resources are available to the various Site/SunNet/Domain Manager applications.

---

Updating NIS Maps or NIS+ Tables

If you are running NIS/NIS+, you must manually update the NIS services and rpc.bynumber maps or the equivalent tables in NIS+.

To update the NIS/NIS+ maps/tables:

1. On the master NIS/NIS+ server, log in as or become superuser:

hostname% su Password: enter your superuser password

2. Edit the file /etc/services by adding the following lines:

snmp 161/udp # Simple Network Mgmt Protocol snmp-trap 162/udp snmptrap # SNMP trap (event) messages

3. Edit the file /etc/rpc by adding the following lines, if they do not already exist in the file:

event 100101 na.event logger 100102 na.logger sync 100104 na.sync diskinfo 100105 na.diskinfo iostat 100106 na.iostat hostperf 100107 na.hostperf activity 100109 na.activity lpstat 100111 na.lpstat hostmem 100112 na.hostmem sample 100113 na.sample ping 100115 na.ping rpcnfs 100116 na.rpcnfs hostif 100117 na.hostif etherif 100118 na.etherif ippath 100119 na.ippath iproutes 100120 na.iproutes layers 100121 na.layers snmp 100122 na.snmp traffic 100123 na.traffic layers2 100131 na.layers2 etherif2 100135 na.etherif2 hostmem2 100136 na.hostmem2 iostat2 100137 na.iostat2 snmpv2 100138 na.snmpv2 sender 100139 cc_sender

4. Make the changes effective:

   a. If you are running NIS, update the maps using the ypmake command, then push the maps out to the slave NIS servers using the yppush command.

   b. If you are running NIS+, update the tables using the nisaddent command.

---

Note - Refer to your system administration documentation if you need additional information on these commands.

---

5. Look for and kill the inetd process by entering the following commands:

hostname# ps -ef | grep inetd hostname# kill -HUP <processnumber>

where <processnumber> is the inetd process number returned.

Setting up Access to Executables, On-line Help, and man Pages

To allow access to executables, append the path of those executables--the default is /opt/SUNWconn/bin--to your PATH variable in your shell startup file.

For a C-shell, in your $HOME/.cshrc file enter:

setenv PATH ${PATH}:/opt/SUNWconn/snm/bin

For a Bourne or Korn shell, in your $HOME/.profile file enter:

set PATH=${PATH}:/opt/SUNWconn/snm/bin export PATH

Context-sensitive help is available for the Console and tools. In order to use the on-line help, you need to put the help directory in a HELPPATH environment variable in your shell startup file. If you installed the software in /opt/SUNWconn/snm, use one of the following commands.

For a C-shell, in your $HOME/.cshrc file enter:

setenv HELPPATH ${HELPPATH}:/opt/SUNWconn/snm/help

For a Bourne or Korn shell, in your $HOME/.profile file enter:

set HELPPATH=${HELPPATH}:/opt/SUNWconn/snm/help export HELPPATH

To get on-line help on windows, menus, fields, and buttons, point the cursor to the appropriate item on the screen and press the F1 or Help key on the keyboard (see the following Note). A pop-up Help window is displayed that contains information about the item. You can then move the pointer to another screen item in a screen and press the Help key again. When you are done with the Help window, click SELECT on the Help window pushpin to dismiss the window.

---

Note - To invoke on-line help, you must use the key that is mapped as the Help key. The xmodmap command in the .xinitrc file in your home directory is used to modify keyboard mappings. If the line xmod -e 'keysym F1 = Help' is not commented out in the .xinitrc file, you should use the F1 key to display the pop-up Help window. If the line xmodmap $HOME/.xmodmap exists in the .xinitrc file, you should check the .xmodmap file in your home directory for any lines that remap the Help key.

---

To use the man pages, you need to put the man page directory in a MANPATH environment variable in your shell startup file. If you installed the software in /opt/SUNWconn/snm, use one of the following commands.

For a C-shell, in your $HOME/.cshrc file enter:

setenv MANPATH ${MANPATH}:/opt/SUNWconn/snm/man

For a Bourne or Korn shell, in your $HOME/.profile file enter:

set MANPATH=${MANPATH}:/opt/SUNWconn/snm/man export MANPATH

The preceding examples assumed you installed the software in its default location. If you installed the product in a directory other than /opt, specify the non-default directory when you assign a value to PATH or MANPATH.

If You Installed the Software in a Non-Default Directory...

If you installed the software in a directory other than /opt, you must set the SNMHOME environment variable to the directory where the software is stored. For example, if you installed the software in /usr2, enter assign a value to SNMHOME as follows:

For a C-shell, in your $HOME/.cshrc file enter:

setenv SNMHOME /usr2/SUNWconn/snm

Then, as the .cshrc owner, enter:

hostname# source $HOME/.cshrc

For a Bourne or Korn shell, in your $HOME/.profile file enter:

set SNMHOME=/usr2/SUNWconn/snm export SNMHOME

Then, as the .profile owner, enter:

hostname# . $HOME/.profile

Remember that, for all shell types, for root, $HOME is your root (/) directory.

If you have a $HOME/.SNMdefaults file left over from a previous version of Site/SunNet/Domain Manager and have installed version 2.3 in a different directory from the one used for the previous version, change the values of the snm.console.schemaPath_2.x and snm.console.iconPath_2.x parameters to reflect the non-default directory.

The Next Step...

Proceed to Chapter 4, "Installing Agent Software on Remote Systems," for instructions on installing agents (the remote data collection programs) on remote systems.

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