Overview

The following is a summary of the steps to install the product 2.2.3 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 product software using cdmanager or cdm.

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 access the executable files
• Setting up access to on-line help and man pages;
• Verifying installation.

Inserting and Accessing the CD-ROM

To install the the product 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 filesystem.

---

Note - Your target machine for installing the the product software must always be a system running SunOS 4.1.3 U1 Rev B (Solaris 1.1.1). You can use a remote SunOS 4.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.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

Enter 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/sr0 /cd

Go to "Selecting and Running an Installation Program" on page 3-7.

·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.1.x (Solaris 1.x), SunOS 5.1 (Solaris 2.1), and SunOS 5.2 or later (Solaris 2.2 or later) systems and are described in separate procedures.

Exporting from a Remote SunOS 4.1.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 -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.1.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 remote SunOS 4.1.x and SunOS 5.1 systems enter:

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

For SunOS 5.2 systems enter:

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

Selecting and Running an Installation Program

Whether you have a directly connected or remotely accessed CD-ROM player, you can now run the cdm or cdmanager commands. Using either program to install 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. Installing the AnswerBook files will take an additional 1 or 2 minutes, if the nil option is selected, or as long as 30 minutes for the heavy option.

The cdmanager program is an OpenWindows application that allows you to install Sun applications from CD-ROM. The cdm program is a command-line counterpart to cdmanager that allows you to install applications directly onto a machine that does not have a graphics display monitor. Instructions for invoking cdmanager or cdm are given below. After the initial commands for either program, installation instructions are essentially the same. These start in the section "Installing the Product Software" on page 3-10.

Before embarking on the following instructions, make sure you have mounted the CD-ROM, as described in the previous section.

Using cdmanager

To install the product using cdmanager, do the following:

1. Either login as root or enter the following commands in normal user mode:

hostname% xhost +<machinename> hostname% su

where <machinename> is the name of the local system. The xhost command is needed to enable CDmanager display.

2. In a shell, cd to the directory on which you have the CD-ROM filesystem mounted and enter ./cdmanager. The cdmanager window appears, with the product icons (Site/SunNet/Domain Manager, Cooperative Consoles, and AnswerBook) displayed.

---

Note - Be sure to install the Site/SunNet/Domain Manager package before the Cooperative Consoles package. Failure to do so will result in error.CDmanager Window

---

3. Use the left mouse button to select the icon. The icon colors invert, and a box appears around the icon, indicating selection. Press the MENU button and drag the pointer to the Install option before releasing. The installation script appears, as described in the next section.

Using cdm

To install the product using cdm, do the following:

1. Login as root or enter the su command at the system prompt.

2. In a shell, cd to the directory on which you have the CD-ROM filesystem mounted and enter ./cdm. You receive the following display:

---

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

---

----->>>>> CDM <<<<<----- 1. Select Application 2. Show Current Application 3. Install Application 4. Display Application Text File 5. Print Application Text File 6. List Applications 7. List Categories 8. Change Current Category 9. Change Current Directory 10. Show Program Environment Please enter a number or q to quit: 1. Cooperative Consoles 2. Site/SunNet/Domain Manager Please enter a number or q for the main menu:

3. Enter 1 to select an application from the CDM menu, then enter the number for the application. You should see a line showing that Site/SunNet/Domain Manager and Cooperative Consoles are selected as the new application.

4. From the CDM menu, enter 3 to install the application. At the "Begin installation now?" prompt, enter y. The installation script appears, as described in the next section.

Installing the Product Software

After invoking cdmanager or cdm, from this point forward, the installation script proceeds in the same way.

1. You receive a product description and copyright notice and are queried:

Do you want to continue [y|n]?

Enter y to proceed with the installation. You receive the following display:

* NOTICE * Many non-Sun vendors provide management applications that run on the platform. If you are using such an application, check with the vendor for compatibility with the product *before* you install the the product software. The run-time database format has changed since the 1.X releases. Before upgrading to Site/SunNet/Domain Manager 2.3 from a 1.X release please be sure to save all existing run-time databases in ASCII format. After completing the installation, you may reload your saved ASCII files. Please refer to the Administration Guide for more information. Do you wish to continue with the installation? [n]

2. Enter y to the prompt above to proceed with the installation or press Return to leave the script.

   For the remainder of these instructions, we assume you enter y. You receive the following display:

Site/SunNet/Domain Manager2.3 requires at least SunOS 4.1.3, with the 'Networking Tools and Programs' option installed. The sun4 package requires about 13000 KB. This package is usually installed into the directory /usr/snm. In most cases, it should be installed into /export/exec/ARCH/snm (ARCH is your current machine architecture), which is a link to /usr/snm. You may specify a different directory. When performing a server installation, if the software you are installing does not match the server's architecture, the server's system files will not be modified to run the product 2.2.3. Installation requires five to fifteen minutes. Supported architecture is: sun4. Do you want to install into /export/exec [y]

3. Press Return at the preceding prompt to install the product in

   /export/exec (which is a link to /usr) or enter n and specify an absolute pathname where you want to install SunNet Manager. After accepting the default installation directory or specifying a different directory, you receive:

It is recommended that you do not change the elements.schema file. You may add your own element schema by creating a personalized file with a .schema extension in one of the directories specified in the 'Schema Locations' field in the console property sheet. Don't worry if you don't know what this means. Would you like to install the Sun SNMP agent? [y]

4. Press Return at the preceding prompt to install the Sun SNMP agent.

   If you have the agent installed from a previous release, the script asks if you want to save your existing snmpd.conf file in /etc and install a new file. Press Return to leave the existing file untouched or enter y to install a new file.

   After you respond to the agent installation queries, the script checks the /etc/rc.local file to determine if it is configured to run the Sun SNMP agent at each reboot. If not, you will receive the following query:

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 fi Would you like me to do this for you? [y]

5. Press Return at the preceding prompt to add the lines to /etc/rc.local or enter n to not add the lines.

   After responding to the prompt above, you receive a display such as the one shown below. Note that the values displayed under the row that begins with Filesystem are for example purposes. Your own display will differ from this.

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 74722 33631 33618 50% /var Would you like the databases to be written to a new default directory? [n]

6. Press Return to have the database and log files placed in /var/adm/snm or enter y if you want these files to be stored elsewhere. If you enter y, you are prompted to enter a new pathname. This should be an absolute pathname of a directory that is writable by root.

   After responding to the database and log file prompts, you receive a display such as the one shown below. Note that the values displayed under the row that begins with Filesystem are for example purposes. Your own display will differ from this.

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 74722 33632 33617 50% /var Would you like the log files to be written somewhere else (like /usr/snm/logs)? [n]

7. Press Return to have the daemon log files placed in /var/adm/snm or enter y if you want these files to be stored elsewhere. If you enter y, you are prompted to enter a new pathname. This should be an absolute pathname of a directory that is writable by root.

   After responding to daemon log file queries you receive:

I'm about to install Site/SunNet/Domain Manager 2.3 into /export/exec for sun4, OK? [y]

8. The licensing install script 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 : <host-name> Host ID : <host-ID> 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:

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 installation will continue with the following prompts::

Please enter the loction where the SNM databases will be created? [/var/adm/snm]

For the location of where the databases will be created, type in the location that you specified while installing the product using (cd or cdmanager) If a value is entered that is different from the location entered while installing, license information will be installed in the wrong place. Your product software will indicate that you do not have a license.

Once a valid database location is entered, the following 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 one of the products, the following is displayed:

I am installing licensing for <product name> now. ok? (y/n) [y]

If license installation is successful, the following is displayed::

Licensing for <product name> 2.300 is completed successfully

The license password is stored in the /var/adm/snm/snm_license.dat file.

9. Press Return to begin the copying of files to the default or specified destination directory.

   The script displays a long list of the files as they are copied. This portion of the script can take from two to ten minutes, depending on the location of the CD drive and machine resources.

   After file copying completes, the installation script performs some "housekeeping" chores. Shown below is example excerpt from this stage of installation. Your own display might differ from this.

Setting root execute permission on snm_discover ... done. [Lines omitted] Generating /var/tmp/<machine_name>.db file ... done. An example database file called /var/tmp/<machine_name>.db has been created. Before using SunNet Manager, you should set the environment variable SNMHOME to the directory /usr/snm. You may also want to add /usr/snm/bin to your PATH environment variable. You may then use 'snm' to start the Console, or use 'snm /var/tmp/<machine_name>.db' to start the product with the example database. Please refer to the Administration Guide for information on how to set the location of Databases with the SNMDBDIR environment variable. Finished Installation on <machine_name>. A log of the installation is in /usr/tmp/unbundled/2.3 SNM.log. You should check this log for any errors that may have occurred during the installation process. Site/SunNet/Domain Manager 2.3 Installation Completed on Mon Aug 21 08:07:07 PST 1995

If you are using cdm, you have finished the software installation.

If you are using cdmanager, when installation completes, you receive the query Done analyzing results?. Enter y to continue.

If you want to install the AnswerBook files at this time, go directly to Step 4 in the next section, under "Starting the AnswerBook Installation Using cdmanager." If you choose not to install the AnswerBook files at this time, pull down the window menu in the cdmanager window title bar and select Dismiss to dismiss the cdmanager window, then skip to the section below entitled "Ejecting the CD-ROM."

Installing the AnswerBook Software

As with the the product software, the AnswerBook can be installed using either cdm or cdmanager. You can install the AnswerBook files at the same time as the the product software installation or at a different time.

If you choose to install AnswerBook, you should make certain that root on the installation machine has write permission on the directories where AnswerBook will be installed.

Starting the AnswerBook Installation Using cdmanager

If you are installing the AnswerBook files on a system that is running the OpenWindows environment, you can accomplish the AnswerBook installation using cdmanager. If you have just installed the the product software and are still running cdmanager, go directly to Step 4.

1. Enable CDmanager display with xhost.

   Type the following command from a window where you are logged in as yourself, not as root:

hostname% xhost +<hostname>

where <hostname> is the name of the local system.

2. Now enter the following command to login as root:

hostname% su

3. In a shell, cd to the directory on which you have the CD-ROM file system mounted and enter ./cdmanager. The cdmanager window appears (see Note -) with the AnswerBook icon displayed.

4. Click the left mouse button to select the AnswerBook icon in the

   cdmanager window. To start the installation, select Install, either from the Options pulldown menu or from the APPLICATION OPTIONS popup menu. (The popup menu appears if you press the right mouse button over the selected icon.)

   The installation script now begins, as described below under "Installing the AnswerBook."

Starting the AnswerBook Installation Using cdm

To install the AnswerBook using cdm, do the following:

1. Login as root or enter the su command at the system prompt.

2. At a shell prompt, cd to the directory on which you have the CD-ROM file system mounted and enter ./cdm. You receive the following display:

----->>>>> CDM <<<<<----- 1. Select Application 2. Show Current Application 3. Install Application 4. Display Application Text File 5. Print Application Text File 6. List Applications 7. List Categories 8. Change Current Category 9. Change Current Directory 10. Show Program Environment Please enter a number or q to quit:

3. Enter 1 to select an application from the CDM menu, then enter the number for theAnswerBook.

4. From the CDM menu, enter 3 to install the application. At the "Begin installation now?" prompt, enter y. From this point on, the installation script proceeds, as described in the next section.

Installing AnswerBook

After the installation has been invoked in either cdm or cdmanager, the installation script proceeds in the same way. You will be asked to complete the following steps:

1. Read the opening screens.

   The first few screens contain information about system requirements, licensing, and AnswerBook planning. Review this information, entering a y or pressing Return to move to the next screen, as instructed.

2. Choose a configuration (1, 2, or 3).

   The screen describes the hard disk space requirements and projected installation time for each option. Enter 1 to select the CD-ROM-based option, 2 for the mixed CD-ROM- and hard disk-based option, or 3 for the hard disk-based option.

After the installation software verifies that you have write permission and sufficient disk space in the target directories, it displays a list of default locations for the files in the Installation Configuration screen. A sample Installation Configuration screen is shown below.

Problems are indicated on this screen by an XX symbol; investigate them before continuing. If you do not want to change any of the default locations, go to Step 4.

3. Customize the directory locations, if necessary.

   If you want to modify the directory locations that are displayed, enter a 2. A screen of instructions will appear, together with a Customization Menu. If you want to change any of the installation settings, choose "Modify Installation Destinations" from the Customization Menu and follow the instructions that appear.

4. Specify user mount points.

   After choosing 1, Perform Installation, from the Installation Configuration menu, you will be asked for either a CD-ROM mount point, a mount point for the AnswerBook home directory (for example, ab_home) on your hard disk, or both, depending on the configuration option that you selected. For example, if you specified one of the two CD-ROM-based options, a screen such as the following appears:

Specify CD-ROM Mount Point ========================== If users will mount (access) the CD-ROM partition by a different path name than the one used during installation, you must change the CD-ROM mount point here so that it matches what users will see. [] Use the value for "CD-ROM Mount Point For Users" from your Installation Planning Worksheet. The CD mount point is currently set to "/cdrom" Enter new CD-ROM mount point, or hit Return to use current value.

Status messages appear as the installation proceeds. When the installation is complete, a prompt gives you the option of listing the files that were installed. Finally, the screen displays the command to start the AnswerBook software as well as a list of references for further reading.

Ejecting the CD-ROM

When you finish running cdm or cdmanager, eject the CD-ROM, using one of the following sets of commands:

d. For SunOS 4.x and SunOS 5.1 (Solaris 2.1) systems, enter:

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

e. For Solaris 2.2 or later systems, enter:

hostname# cd / hostname# eject

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 product software on a server, you can run the Console from a client. To do so, run the getagents 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 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 -ax | 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 run executables, you must append the path of those executables--the default is /usr/snm/bin--to your PATH variable in your shell startup file.

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

setenv PATH ${PATH}:/usr/snm/bin

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

set PATH=${PATH}:/usr/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 product in /usr/snm, use one of the following commands.

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

setenv HELPPATH ${HELPPATH}:/usr/snm/help

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

set HELPPATH=${HELPPATH}:/usr/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 popup 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 popup 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 product in /usr/snm/bin, use one of the following commands.

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

setenv MANPATH ${MANPATH}:/usr/snm/man

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

set MANPATH=${MANPATH}:/usr/snm/man export MANPATH

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

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

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

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

setenv SNMHOME /usr2/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/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 an $HOME/.SNMdefaults file left over from version 2.0 of the product and have installed version 2.2.3 in a different directory from the one used for version 2.0, change the values of the snm.console.schemaPath and snm.console.iconPath 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 agents, the next step is start the Console and create a management database of network elements that you intend to manage. See the Administration Guide for instructions on performing these tasks.