|
|
This chapter describes how to install the IPM server and client software on a Sun Solaris system. It also provides information on verifying the installation and uninstalling and reinstalling IPM on Solaris.
This chapter includes the following sections:
![]() |
Note If you have been running IPM Release 1.0, you must upgrade to IPM Release 2.0 before you can install IPM Release 2.1. Refer to the "Upgrading from IPM Release 1.0" section for more information on upgrading from IPM Release 1.0. |
To install the IPM software on a Sun Solaris workstation:
Step 2 Log in as the root user.
Step 3 Insert the IPM CD-ROM into the CD-ROM drive and, if necessary, mount the CD-ROM drive.
Step 4 Start the installation script by entering the following command:
# ./setup.sh
Step 5 Do one of the following when the IPM setup program menu appears:
The following message is displayed:
Enter full Netscape browser executable pathname: ? [/opt/netscape/netscape]
Step 6 If the IPM installation program determines that Netscape Communicator is installed in the default location, skip this step.
If you are prompted to specify the location of the Netscape Communicator executable file, you can accept the default path for Netscape Communicator by pressing Enter. If the Netscape Communicator executable file is located in a different directory than the default, type the full path (including file name) where the executable file is located.
The IPM installation program continues and determines whether or not your workstation meets the hardware and software requirements for running IPM.
Step 7 If your workstation meets the requirements for IPM, the following prompt is displayed:
Do you want the Express Install (y/n)? [Y]
Step 8 If your workstation does not meet all the requirements for IPM, then the installation program proceeds with the standard installation and you are prompted for information such as port numbers and product path and filename.
Step 9 Verify that the installation was completed successfully by viewing the messages displayed at the end of the installation and by viewing the installation log. The installation log path is specified at the end of the installation script.
After IPM is successfully installed, the following IPM start-up menu is displayed.
********************************************************************** * * * Cisco Systems * * + + + + * * | | Internetwork | | * * +|+ +|+ Performance Monitor +|+ +|+ * * +|||||+ +|||||+ +|||||+ +|||||+ * * ++|||||||++++|||||||++ Startup Options ++|||||||++++|||||||++* * Empowering The =============== Internet Generation* * * ********************************************************************** 1) Start IPM Server and Client 2) Start IPM Server Only 3) Exit Setup Please choose an option ->
Step 10 Start IPM by choosing one of the following options:
This section describes the hardware and software requirements to run IPM on a Solaris workstation. It includes the following sections:
![]() |
Note Hardware and software version information is subject to change, based on enhancements to the product. For the most current version information, refer to the Release Notes for Cisco Internetwork Performance Monitor available on CCO. |
Your system must meet the following hardware requirements to run IPM:
Your system must meet the following software requirements to run IPM:
The IPM installation program automatically verifies your operating system version and also checks the level of Solaris patches that your system should have.
To obtain the patches, contact your Sun Microsystems representative or download them from the Sun web site.
The following minimum patch levels are required to run IPM on Solaris version 2.5.1:
The following minimum patch levels are required to run IPM on Solaris version 2.6:
The following minimum patch levels are required to run IPM on Solaris version 2.7:
![]() |
Note Patch 107607-01 is required only if Patch 107607 has already been installed on your Solaris workstation. |
![]() |
Caution If you do not have the required patches installed, you can continue with the installation, but IPM might not operate as expected. |
![]() |
Caution As the root user, you can adversely affect your operating environment if you are unaware of the effects of the commands you use. If you are a relatively inexperienced UNIX user, limit your activities as the root user to the tasks described in this manual. |
If you are not logged in, log in as the root user, as follows:
> login: root > Password: rootpassword
If you are already logged in, but not as the root user, use the su command to change your login to root:
#su # Password:rootpassword
Step 2 Log in as the root user, as described in the "Becoming the Root User" section. The command prompt changes to the pound sign (#).
Step 3 If the /cdrom directory does not already exist, create it using the mkdir command:
# mkdir /cdrom
Step 4 Mount the CD-ROM drive.
![]() |
Note The vold process manages the CD-ROM device and performs the mounting. The CD-ROM might automatically mount onto the /cdrom/cdrom0 directory. |
If you are running File Manager, a separate File Manager window displays the contents of the CD-ROM.
Step 5 If the /cdrom/cdrom0 directory is empty because the CD-ROM was not mounted, or if File Manager did not open a window displaying the contents of the CD-ROM, verify that the vold daemon is running by entering the following command:
# ps -e | grep vold | grep -v grep
Step 6 Do one of the following:
# /usr/sbin/vold &
#kill -15process_ID_number # /usr/sbin/vold &
![]() |
Note To stop the vold process, you must know the process identification number. If you do not know the process identification number, run the ps command shown in Step 5. |
Step 7 If you have problems with the vold daemon, use the following mount command to mount the CD-ROM directly:
# mount -F hsfs -r ro /dev/dsk/device_filename /cdrom/cdrom0
Where:
-F indicates the type of file system (hsfs for the ISO 9660 standard).
-r ro mounts the CD-ROM in read-only mode.
device_filename is the name of the device, such as /dev/dsk/cxtyd0sz where x is the CD-ROM drive controller number, y is the CD-ROM drive SCSI ID number, and z is the slice partition on which the CD-ROM is located.
![]() |
Caution The instructions for mounting an NFS-exported CD-ROM drive on a local system are for like systems. For example, the instructions are for exporting a CD-ROM file system from a Solaris system and mounting it on another Solaris system for installation, but not for cross-platform operation. For help with cross-platform operations, see your system administrator. |
The mounting instructions are presented in the following two sections:
On the remote system perform the following steps:
Step 2 If the /cdrom directory does not already exist, create it using the mkdir command:
# mkdir /cdrom
Step 3 Mount the CD-ROM drive.
![]() |
Note The vold process manages the CD-ROM device and performs the mounting. The CD-ROM might automatically mount onto the /cdrom/cdrom0 directory. |
If you are running File Manager, a separate File Manager window displays the contents of the CD-ROM.
Step 4 If the /cdrom/cdrom0 directory is empty because the CD-ROM was not mounted, or if File Manager did not open a window displaying the contents of the CD-ROM, verify that the vold daemon is running by entering the following command:
# ps -e | grep vold | grep -v grep
Step 5 Do one of the following:
# /usr/sbin/vold &
#kill -15process_ID_number # /usr/sbin/vold &
![]() |
Note To stop the vold process, you must know the process identification number. If you do not know the process identification number, run the ps command shown in Step 5. |
Step 6 If you have problems with the vold daemon, use the following mount command to mount the CD-ROM:
# mount -F hsfs -r ro /dev/dsk/device_filename /cdrom/cdrom0
Where:
-F indicates the type of file system (hsfs for the ISO 9660 standard).
-r ro mounts the CD-ROM in read-only mode.
device_filename is the name of the device, such as /dev/dsk/cxtyd0sz where x is the CD-ROM drive controller number, y is the CD-ROM drive SCSI ID number, and z is the slice partition on which the CD-ROM is located.
Step 7 Edit or create the /etc/dfs/dfstab file to include the following line, which sets the NFS attributes to read-only:
share -F nfs -o ro -d /cdrom/cdrom0
Where:
-F specifies the file system share type.
-o specifies the start of file system export options.
ro specifies read-only file system export option.
-d specifies that you want to share a directory.
/cdrom/cdrom0 is the name of the directory to be shared.
Step 8 Be sure that your remote machine is enabled as an NFS server by entering the following command:
# ps -ef | grep nfs | grep -v grep
Verify that the /usr/lib/nfs/nfsd and /usr/lib/nfs/mountd daemons are running.
Step 9 If the daemons that you verified in Step 8 are not running, enable your machine as an NFS server by entering the following command:
# /etc/init.d/nfs.server start
Step 10 When your machine is enabled as an NFS server, run either of the following commands:
# share # shareall
On the local system perform the following steps:
Step 2 Log in as the root user as described in the "Becoming the Root User" section.
Step 3 If the /cdrom directory does not already exist, create it using the mkdir command:
# mkdir -p /cdrom/ipm
Step 4 To mount a file system that is exported from a remote system, use the mount command, as shown below:
# /usr/sbin/mount -r remote_hostname:/cdrom/cdrom0 /cdrom/ipm
The remote CD-ROM is mounted and ready for software installation on the local system.
After you install IPM, you need to unmount the CD-ROM drive as explained in the following sections:
To unmount a local CD-ROM drive:
Step 2 Run the following commands:
# cd # umount /cdrom/cdrom0
Step 3 Remove the CD-ROM and store it in a safe place.
To unmount a remote CD-ROM drive:
# umount /cdrom/ipm
Step 2 Log in as the root user on the remote machine and run the following command:
# umount /cdrom/cdrom0
Step 3 Remove the CD-ROM and store it in a safe place.
The IPM client software can either reside with the IPM server, or it can be installed on another workstation that is located on the same network as the IPM server. The IPM server on Solaris can also be accessed by IPM clients running on Windows 95, Windows 98, or Windows NT workstations.
You can install both the IPM server software and client software on a Solaris system, either at the same time or separately using the following menu options provided by the setup program.
The IPM software consists of the following Solaris packages:
When you install both the IPM server and client software on the same system, all of the listed package components must be successfully installed. When you install the IPM server only, then both the components (CSCOcwbS and CSCOipm-s) of the IPM server software must be successfully installed.
![]() |
Note Use the setup.sh program provided with the IPM software to install IPM on your Solaris workstation. |
Before you run the setup program on Solaris note the following information:
![]() |
Note IPM can be run without Netscape, but Netscape is required to access the online help, to install the IPM client using the web server, and to access the IPM server home page and IPM web reports. |
To begin the installation of the IPM software on Solaris.
Step 2 Mount the CD-ROM drive, as described in the "Mounting and Unmounting the CD-ROM Drive on Solaris" section.
Step 3 Change to the mounted directory using the cd command:
# cd /cdrom/cdrom0
Step 4 Start the installation script by entering the following command:
# ./setup.sh
The following IPM setup program menu appears:
********************************************************************** * * * Cisco Systems * * + + + + * * | | Internetwork | | * * +|+ +|+ Performance Monitor +|+ +|+ * * +|||||+ +|||||+ +|||||+ +|||||+ * * ++|||||||++++|||||||++ Setup Program ++|||||||++++|||||||++* * Empowering The ============== Internet Generation* * * ********************************************************************** 1) Review README File First (Recommended) 2) Install IPM Server and Client 3) Install IPM Server Only 4) Install IPM Client Only 5) Exit Setup Please choose an option ->
Step 5 Type the number of the desired installation option and press Enter. The IPM setup program verifies the system environment for installation of the software.
The following message is displayed:
Enter full Netscape browser executable pathname: ? [/opt/netscape/netscape]
Step 6 To accept the default path for Netscape Communicator, press Enter. If the Netscape Communicator executable file is located in a different directory than the default, type the full path (including file name) where the executable file is located.
The IPM installation program determines whether or not your workstation meets the hardware and software requirements for running IPM.
Step 7 If your workstation meets the requirements for IPM, the following prompt is displayed:
Do you want the Express Install (y/n)? [Y]
Step 8 If your workstation does not meet all the requirements for IPM, then the installation program proceeds with the standard installation and you are prompted for information such as port numbers and product path and filename.
Step 9 Verify that the installation was completed successfully by viewing the messages displayed at the end of the installation and by viewing the installation log. The installation log path is specified at the end of the installation script.
A successful installation is shown in the following example:
Installation of <CSCOipm-c> was successful. INFO: Checking Installation. INFO: Package CSCOipm-c installed OK. Verifying... OK. ========================================================== To start the IPM Client type: /opt/CSCOipmClient/bin/ipm or include /opt/CSCOipmClient/bin in your path and type 'ipm' ============================- Error Summary -===================== No Errors were encountered during installation. ================================================================== Started : Tue Dec 21 11:46:36 EST 1999 Finished: Tue Dec 21 11:47:10 EST 1999 Please review /var/tmp/cisco_ipmcli_install.log for detailed results. ================================================================== ==================- IPM Client Install Tool Completed -=========== ==================================================================
![]() |
Note If you are planning to install the IPM client software using the web interface on the IPM server, be sure to note the URL listed in the "To access the web server" message when the IPM server installation is complete. |
Step 10 Depending on the installation option that you selected, a menu appears with options to start the software or exit setup. If the server and client software has been successfully installed, then select an option to start the software.
The following menu appears when you install only the IPM client software:
********************************************************************** * * * Cisco Systems * * + + + + * * | | Internetwork | | * * +|+ +|+ Performance Monitor +|+ +|+ * * +|||||+ +|||||+ +|||||+ +|||||+ * * ++|||||||++++|||||||++ Startup Options ++|||||||++++|||||||++* * Empowering The =============== Internet Generation* * * ********************************************************************** 1) Start IPM Client and Connect to Remote Server 2) Exit Setup Please choose an option ->
![]() |
Note The IPM server software must be running to start and connect an IPM client. |
To start the IPM database, server, and client at a later time from the command line, use the following commands:
# cd /opt/CSCOipm/bin # ./ipm
To start just the IPM database and server at a later time from the command line, use the following commands:
# cd /opt/CSCOipm/bin # ./ipm start
For a complete list of all of the IPM commands, see the "IPM Command Reference" appendix in the Cisco Internetwork Performance Monitor User Guide.
The installation program automatically checks your system to verify that it is capable of running the express installation. The program verifies that the default TCP/IP ports that IPM is set up to use are available and that there is enough space in the default installation directory (/opt). If your system meets these requirements, then the installation program provides the option to run the express installation. The following example shows the express installation option for the IPM client software:
![]() |
Note The express installation option is only available for the IPM client software when you are installing the IPM server and IPM client software on the same workstation |
********************************************************************** * * * Cisco Systems * * + + + + * * | | Internetwork | | * * +|+ +|+ Performance Monitor +|+ +|+ * * +|||||+ +|||||+ +|||||+ +|||||+ * * ++|||||||++++|||||||++ Setup Program ++|||||||++++|||||||++* * Empowering The ============== Internet Generation* * * ********************************************************************** 1) Review README File First (Recommended) 2) Install IPM Server and Client 3) Install IPM Server Only 4) Install IPM Client Only 5) Exit Setup Please choose an option -> 3 ================================================================= ================================================================= ================- IPM Client Install Tool Started -============== ================================================================= Fri Dec 11 10:47:55 EST 1998 SunOS yoursystem 5.5.1 Generic_103640-23 sun4u sparc SUNW,Ultra-1 ============================================================ ===============- System Requirements Check -================ ============================================================ INFO: Checking UID... root, OK. INFO: Checking Host Operating System... SunOS, OK. INFO: Checking Operating System Version... 5.5.1, OK. INFO: Checking Solaris patches... OK. INFO: Checking Solaris patches... OK. INFO: Checking Solaris patches... OK. INFO: Checking Solaris patches... OK. INFO: This product requires: RAM 131072 K SWAP 262144 K INFO: Checking Ram... OK. INFO: Checking Swap... OK. INFO: Checking your release... All components present. INFO: Checking for existing product tree... None. ============================================================ ================- Disk Space Usage check -================== ============================================================ INFO: For this product the default disk space requirements are: /opt 50000 K /var/adm 5000 K /var/tmp 1000 K INFO: Checking default disk space requirements... OK. ============================================================ ============================================================ ===================- IPM Client Summary -=================== ============================================================ INFO: The following ports will be used: INFO: [ 1] Web Server: 1744/tcp INFO: [ 2] Naming Server: 44342/udp The Express Install takes all defaults and places the product in /opt. No more questions will be asked. Do you want the Express Install (y/n)? [Y]
If the program detects that the ports are unavailable, or that there is insufficient space in the default installation directory, then the express installation is disabled and you must run the standard installation to specify ports or to choose another installation directory. See the example output in the "Installing IPM to a Different Directory" section which shows a disabled express installation option for the IPM server software.
The following example shows a case where there is insufficient space in the default installation directory. Notice that after the message, "Where should the product be installed?", the program suggests an alternate directory /usr2/CSCOipm where it has determined that there is enough space to install IPM. To accept the proposed directory, press Enter. Otherwise, specify another directory and press Enter.
============================================================ ================- Disk Space Usage check -================== ============================================================ INFO: For this product the default disk space requirements are: /opt 250000 K /var/adm 5000 K /var/tmp 1000 K INFO: Checking default disk space requirements... INFO: /opt has insufficient space for installation. INFO: Express Install has been disabled. ============================================================ INFO: Local disks on this machine with enough space to install: Filesystem kbytes used avail capacity Mounted on /dev/dsk/c0t4d0s6 1925720 288623 1444527 17% /usr2 Where should the product be installed ? [/usr2/CSCOipm]
The IPM server software uses the following default ports:
![]() |
Note The IPM client and server software must be set up to communicate on the same port. If you are installing the IPM client on the same machine as the IPM server, then the installation program handles this automatically. If you are installing the IPM client on a separate workstation from the server, you must be sure that the ports specified during the client installation match those installed for the IPM server. In most installation situations the default ports should be available for the IPM client and server. |
# netstat -a -n -f inet - p {tcp|udp}
![]() |
Note If you are specifying an alternate port, remember that ports 1 through 1023 are reserved for system processes. |
The following procedure explains how to download, uncompress, extract, and install the IPM client software on a Solaris workstation.
To install the IPM client on Solaris using the web interface:
Step 2 From your browser, go to the URL for the IPM web server (for example, http://youripmserver:1744). The IPM Server Home Page is displayed (Figure 4-1).

![]() |
Note If you do not have this information, contact the system administrator who installed the IPM server software. |
Step 3 Click Download Solaris Client. The IPM Client for Solaris page (Figure 4-2) is displayed.

Step 4 Click Download IPM Client for Solaris to download the client software installation files.
Step 5 When prompted, specify the directory where you want the installation software files to be downloaded, such as /temp-directory.
Step 6 From the Solaris command line, change to the directory where you downloaded the installation software and uncompress the files using the following command:
# uncompress CSCOipmClient.tar.Z
Step 7 In the directory where you uncompressed the files, extract the IPM client installation files to the CDImage directory using the following command:
# /usr/bin/tar -xvf CSCOipmClient.tar
Step 8 Change to the CDImage directory and run the IPM client software installation program using the following command:
# ./setupCli.sh
Step 9 After verifying that the IPM client software installed successfully, remove all installation files in the temporary directory using the following command:
# rm -rf temp_directory
Where temp_directory is the directory containing the downloaded files.
To check for installation error messages:
# more install_directory/install/cisco_ipm_install.log
Where install_directory is directory where IPM was installed. The default installation directory for IPM is /opt/CSCOipm.
Step 2 Press the Space bar to scroll through the display one screen at a time.
To view packaging information for the IPM server and client:
#pkginfo -l CSCOipm-s#pkginfo -l CSCOcwbS#pkginfo -l CSCOipm-c
Step 2 Verify that you receive output similar to the following display for each component that you have queried with the pkginfo command:
PKGINST: CSCOipm-s
NAME: Cisco IPM Server
CATEGORY: application
ARCH: sparc
VERSION: 2.1
BASEDIR: /opt/CSCOipm
VENDOR: Cisco Systems, Inc
DESC: Cisco IPM Server
PSTAMP: nm-rtp-view2991220162731
INSTDATE: Dec 21 1999 11:44
HOTLINE: 1-800-553-2447
EMAIL: tac@cisco.com
STATUS: completely installed
FILES: 260 installed pathnames
26 directories
61 executables
1 setuid/setgid executables
113600 blocks used (approx)
If the result of the pkginfo command states that the package was not found as in the following example, then the software is not currently installed.
ERROR: information for "CSCOipm-s" was not found
You can also start the IPM database, IPM server, and IPM client by using the following commands:
# cd /opt/CSCOipm/bin # ./ipm
If you installed the IPM server and IPM client on different workstations, use the following commands to start IPM:
#cd /opt/CSCOipm/bin#./ipm start
# cd /opt/CSCOipmClient/bin # ./ipm start client
If the IPM server and client installation was successful, the IPM Main window should open (Figure 4-3).

The uninstall program provides you with a menu of options similar to that presented for installation. You can choose whether to uninstall both the IPM client and server software (for example, after a failed installation) or uninstall each component individually.
The IPM software consists of the following packages:
When you uninstall both the IPM server and client software on the same system, all of the listed package components need to be successfully uninstalled. When you uninstall the IPM server only, then both the components (CSCOcwbS and CSCOipm-s) of the IPM server software need to be successfully uninstalled.
Uninstalling IPM on Solaris is discussed in the following sections:
Uninstall both the IPM server software and client software on a Solaris system, either at the same time or separately, using the following menu options provided by the uninstall program.
1. Uninstall IPM Server and Client---Use when the IPM server and client software reside on the same Solaris system and you want to remove all of the IPM software on that system. This option removes all of the IPM packages from the system.
2. Uninstall IPM Server Only---Use when you only want to remove the IPM server software on this system. This option removes both the common services (CSCOcwbS) package and the IPM server (CSCOipm-s) package.
3. Uninstall IPM Client Only---Use when you only want to remove the IPM client software on this system. This option removes the IPM client (CSCOipm-c) package.
To uninstall the IPM software on Solaris:
![]() |
Note To stop the uninstall process at any time, press Break or Ctrl-C. |
Step 2 If you are running an IPM client locally, stop the client by selecting File > Exit from the IPM Main window.
Step 3 Stop the IPM database engine and server by running the following commands:
#cd /opt/CSCOipm/bin#./ipm stop
Step 4 If you want to preserve any of the IPM server data in the database, run the following commands to change directories and copy the database to a temporary directory:
# cd /opt/CSCOcwbS/db/CSCOipm # cp IPMDB.db /tmp
Step 5 To start the uninstall script, run the following commands:
# cd /opt/CSCOipm/install # ./uninstall.sh
The following menu appears:
********************************************************************** * * * Cisco Systems * * + + + + * * | | Internetwork | | * * +|+ +|+ Performance Monitor +|+ +|+ * * +|||||+ +|||||+ +|||||+ +|||||+ * * ++|||||||++++|||||||++ Uninstall Program ++|||||||++++|||||||++* * Empowering The ================== Internet Generation* * * ********************************************************************** 1) Uninstall IPM Server and Client 2) Uninstall IPM Server Only 3) Uninstall IPM Client Only Please choose an option ->
Step 6 Type the number of the desired option and press Enter.
Step 7 To continue uninstalling the package components, respond to the confirmation messages to verify that you want to remove the server packages (CSCOcwbS and CSCOipm-s) or client package (CSCOipm-c).
Step 8 When the uninstall is complete, verify that you receive messages corresponding to the packages that you selected to remove. The following example shows the message received during an uninstall of the IPM server package. You should receive a similar set of messages for the common services package (CSCOipm-s) and the client package (CSCOipm-c), depending on what you have selected to uninstall.
Removal of <CSCOcwbS> was successful. INFO: The following Cisco IPM INFO: packages have been successfully deleted from the system: CSCOipm-s CSCOcwbS Please review /var/tmp/cisco_ipm_uninstall.log for detailed results
Step 9 To further verify that the IPM server and its associated services are uninstalled, run the following pkginfo commands:
# pkginfo -l CSCOcwbS # pkginfo -l CSCOipm-s # pkginfo -l CSCOipm-c
Step 10 Verify that you receive a message for each package that you uninstalled as shown in the following example, indicating that the package can no longer be found:
ERROR: information for "CSCOipm-s" was not found
![]()
![]()
![]()
![]()
![]()
![]()
![]()
Posted: Sun Apr 16 12:32:07 PDT 2000
Copyright 1989 - 2000©Cisco Systems Inc.