Table Of Contents
Installing IPM on Solaris
Quick Start for Solaris
Hardware and Software Requirements
Hardware Requirements
Software Requirements
Solaris Patch Requirements
Using Sun Java Plug-in 1.4.2_08
Creating Root User Privileges
Mounting and Unmounting the CD-ROM Drive on Solaris
Mounting a Local CD-ROM
Mounting a NFS-Exported CD-ROM Drive
Steps to Perform on the Remote System
Steps to Perform on the Local System
Unmounting the CD-ROM Drive
Unmounting a Local CD-ROM Drive
Unmounting a Remote CD-ROM Drive
Installing IPM on Solaris
Overview of Installing IPM on Solaris
Running the Setup Program on Solaris
Running the Express Installation
Installing IPM to a Different Directory
Specifying Alternate Ports
Verifying Port Usage
Re-installing IPM
Installing the IPM Client on Solaris From the CiscoWorks Homepage
Verifying IPM Installation on Solaris
Checking for Error Messages
Viewing Packaging Information for the IPM Server and Client
Verifying the Installation Directories
Starting IPM
Uninstalling IPM on Solaris
Overview of Uninstalling IPM on Solaris
Running the Uninstall Program on Solaris
Installing IPM on Solaris
This chapter describes how to install the IPM server and client software on a Sun Solaris system. It also provides information about verifying the installation and uninstalling IPM on Solaris.
This chapter includes the following sections:
•
Quick Start for Solaris
•
Hardware and Software Requirements
•
Creating Root User Privileges
•
Mounting and Unmounting the CD-ROM Drive on Solaris
•
Installing IPM on Solaris
•
Installing the IPM Client on Solaris From the CiscoWorks Homepage
•
Verifying IPM Installation on Solaris
•
Uninstalling IPM on Solaris
Quick Start for Solaris
This section provides basic information for installing IPM on a Solaris system.
By default, CiscoWorks Common Services uses CiscoWorks Server authentication (CiscoWorks Local) to authenticate users, and authorize them to access CiscoWorks Common Services applications, use Cisco Secure ACS.
We recommend that you integrate CiscoWorks server and Cisco Secure ACS after installing all of the LAN Management Solution applications.
If you have intergated CiscoWorks server and Cisco Secure ACS before installing IPM 2.6, you have to run the following script to register IPM 2.6:
NMSROOT/bin/perl NMSROOT/bin/AcsRegCli.pl listRegApp
If IPM is not listed, enter the following command to register IPM with ACS:
NMSROOT/bin/perl NMSROOT/bin/AcsRegCli.pl -register ipm, where NMSROOT is the CiscoWorks installation directory.
Be default, NMSROOT is /opt/CSCOpx on Solaris. On Windows, it is
System Drive\Program Files\CSCOpx, where System Drive is the Windows Operating System's drive where IPM is installed.
To install the IPM software on a Sun Solaris system:
Step 1
Before you begin the installation:
•
Make sure your Solaris system meets the requirements listed in the Hardware and Software Requirements.
•
Determine the location of the Netscape Communicator executable file. During installation, you are prompted to provide the full path to this file. The default path is /opt/netscape/netscape.
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 at command prompt:
Step 5
Do one of the following when the IPM setup program menu appears:
•
To read the latest information about IPM in the Readme file, type 1 and press Enter. The Readme file contains late-breaking information about IPM that might not be found in the product documentation.
•
To install both the IPM server and client software on the system, type 2 and press Enter.
•
To install only the IPM client on the system, type 3 and press Enter.
The following message appears:
Enter full Netscape browser executable pathname: ? [/opt/netscape/netscape]
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 directory other than the default directory, type the full path (including file name) where the executable file is located.
The IPM installation program continues and determines whether your system meets the hardware and software requirements for running IPM.
Note
If you have selected to install IPM Server or IPM Server and client, IPM prompts you to enter Database and Administrative password.
If your system meets the requirements for IPM, the following prompt appears:
Step 6
Enter a new Database password.
The password is case sensitive and should begin with an alphabet. You can enter only a maximum of 15 characters and you can enter only alphanumeric characters.
Step 7
Enter the Administrative password. Confirm the password by re-entering it.
The password is case sensitive and should begin with an alphabet. You can enter only a maximum of 15 characters and you can enter only alphanumeric characters. IPM displays the following prompt:
Do you want the Express Install (y/n)? [Y]
Step 8
Select one of the following:
•
y or press Enter to select the Express Install which installs IPM using all default settings.
•
n to select the standard installation which prompts you for additional information such as port numbers, product path, and filename.
If your system does not meet all the requirements for IPM, the installation program proceeds with the standard installation and prompts you for information such as port numbers and Netscape executable path.
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.
After IPM is successfully installed, the following IPM start-up menu appears.
**********************************************************************
* +|+ +|+ Performance Monitor +|+ +|+ *
* +|||||+ +|||||+ +|||||+ +|||||+ *
* ++|||||||++++|||||||++ Startup Options ++|||||||++++|||||||++*
* Empowering The =============== Internet Generation*
**********************************************************************
1) Start IPM Server and Client
Please choose an option ->
Step 10
Start IPM by typing 1 or 2 and pressing Enter.
Hardware and Software Requirements
This section describes the hardware and software requirements to run IPM on a Solaris system. It includes the following sections:
•
Hardware Requirements
•
Software Requirements
•
Solaris Patch Requirements
Hardware and software version information is subject to change, based on enhancements to the product. For the most current version information, See to the Internetwork Performance Monitor 2.6 documentation available on Cisco.com.
Hardware Requirements
Your system must meet the following hardware requirements to run IPM:
•
System hardware—Sun Ultra I or later and, to install software, a CD-ROM drive on the server or on a remote host system that can be accessed by the Network File System (NFS).
•
Memory—512 MB or greater RAM (512 recommended), 1 GB or more swap space.
•
Hard disk space—2 GB for server only or server and client software.
•
Color monitor—If you run the IPM client on the host system.
•
Printer—PostScript-compatible printer for printing graphs and charts.
Software Requirements
Your system must meet the following software requirements to run IPM:
•
System software—Sun Solaris 2.8, or Solaris 2.9 with the latest recommended patches from Sun Microsystems, Inc., and the required patches for IPM. For a list of the required patches for IPM, see the Solaris Patch Requirements.
•
Common Services—Common Services version 3.0.
•
Web browser software—Netscape Navigator 7.1/7.0 (Netscape Navigator 7.0 on Solaris 2.8 and Solaris 2.9) and Mozilla 1.7.
•
Java—Java plug-in 1.4.2_04 is required to run the IPM client software as an applet from the Web browser.
•
OpenWindows Version 3.5.1 with CDE.
•
Server protocols—Do not run the IPM server as a DHCP client; it must have a static IP address. The IPM server must have a valid DNS address that matches its IP address as well.
The IPM installation program automatically verifies your operating system version and checks for the required level of Solaris patches.
Solaris Patch Requirements
The Solaris patches listed by version in this section are required to install IPM. These patches can be installed separately or as a jumbo patch from Sun Microsystems, Inc.
To verify the patches installed on your Solaris system, run the showrev -p command.
To obtain the patches, contact your Sun Microsystems representative, or download them from the Sun Web site.
http://sunsolve.sun.com
Table 4-1 lists the required and recommended patches for Solaris 2.8 and 2.9.
Table 4-1 Solaris Patches
Operating System Version
|
Required
|
Recommended
|
Solaris 2.9 Patches
|
• 112808
• 112970
• 113575
• 112964
• 113713
• 112998
• 113326
• 112785
• 113244
• 114006
• 112661
• 112771
• 112233
• 112839
• 113580
• 114224
• 112811
|
112300
|
Solaris 2.8 Patches
|
• 111626
• 111327
• 111085
• 110951
• 110945
• 110934
• 110898
• 110700
• 110670
• 110662
• 110615
• 110286
• 109326
• 109324
• 108993
• 108652
• 108528
|
• 110951
• 110662
• 110615
• 110286
• 109324
• 111085
|
Caution 
If you do not have the required patches installed, you can continue with the installation, but IPM might not function as expected.
Using Sun Java Plug-in 1.4.2_08
A vulnerability in the Java Plug-in 1.4.2_04 may allow an untrusted applet to escalate privileges, through JavaScript calling into Java code, including reading and writing files with the privileges of the user running the applet. For more details, see Sun Alert ID: 57591. This is fixed in Java plugin 1.4.2_08.
CiscoWorks neither exploits nor is impacted by this vulnerability. If you choose to use Sun Java Plug-in 1.4.2_08 instead of the one provided with CiscoWorks (1.4.2_04), you can choose the plug-in manually.
To modify your CiscoWorks installation to use Sun Java Plug-in 1.4.2_08:
Step 1
Locate the Java Plug-in properties file on the IPM server.
%NMSROOT%/lib/classpath/javaplugin.properties and change the following entries in the javaplugin.properties file:
WIN_IE_VERSION=clsid:CAFEEFAC-0014-0002-0008-ABCDEFFEDCBA
WIN_NS_VERSION=application/x-java-applet;jpi-version=1.4.2_08
SOL_VERSION=application/x-java-applet;jpi-version=1.4.2_08
Step 2
Save the modified javaplugin.properties file.
Step 3
Update each Solaris client as follows:
a.
Download Java Plug-in 1.4.2_08 for Solaris from the Sun site.
b.
Install the Java Plug-in on the client.
c.
Locate the jpi.profile and jpi.cshrc files on the client, and change the MOZ_PLUGIN_PATH, to reflect the path to Java Plug-in 1.4.2_08. 9
For example, if you have installed 1.4.2_04 in /opt/jre14204, and you have installed 1.4.2_08 in /opt/jre14208
Change
MOZ_PLUGIN_PATH=/opt/jre14204/j2re1.4.2_04/plugin/sparc/ns610
To
MOZ_PLUGIN_PATH=/opt/jre14208/j2re1.4.2_08/plugin/sparc/ns610
Step 4
Update each Solaris client using Netscape 7.0 or Mozilla as follows:
a.
Modify the links to point to the links for Java Plug-in 1.4.2_08:
Change
NS7_HOME/plugins/libjavaplugin_oji.so
To
JPI1.4.2_08_HOME/plugin/sparc/ns610/libjavaplugin_oji.so
b.
Source /jpi.cshrc or execute /jpi.profile.
c.
Close any running browser instances and start them again.
Creating Root User Privileges
To install and configure IPM, you must be logged in as the root user on the system where you want to install IPM.
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 by entering:
If you are already logged in, but not as the root user, use the su command to change your login to root:
Mounting and Unmounting the CD-ROM Drive on Solaris
You can install the IPM server or client software from a CD-ROM drive connected to your local system or from a CD-ROM drive connected to a remote system. In either case, you must first mount the CD-ROM drive. Mounting a device makes it available to the local file system.
Mounting a Local CD-ROM
To mount a local CD-ROM:
Step 1
Insert the IPM CD-ROM into the CD-ROM drive.
Step 2
Log in as the root user, as described in the "Creating Root User Privileges" section. The command prompt changes to the pound sign (#).
If the /cdrom directory does not already exist, create it using the mkdir command:
Step 3
Mount the CD-ROM drive.
The vold process manages the CD-ROM device and performs the mounting. The CD-ROM should mount automatically onto the /cdrom/cdrom0 directory.
If you are running File Manager, a separate File Manager window displays the contents of the CD-ROM.
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
Do one of the following:
•
If vold is running, the system displays the process identification number of vold. If the system does not display anything, restart the daemon by entering the following command:
•
If the vold daemon is running but did not mount the CD-ROM, then stop the vold daemon process using the kill command and restart the daemon:
# kill -9 process_ID_number
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.
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.
Mounting a NFS-Exported CD-ROM Drive
IPM installation from a device on a remote system does not require any disk space on the remote system. The software is copied across the network to the local system.
Caution 
The instructions for mounting an NFS-exported CD-ROM drive on a local system are for similar 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:
•
Steps to Perform on the Remote System
•
Steps to Perform on the Local System
Steps to Perform on the Remote System
On the remote system:
Step 1
Log in as the root user as described in the Creating Root User Privileges. The command prompt changes to the pound sign (#).
If the /cdrom directory does not already exist, create it using the mkdir command:
Step 2
Mount the CD-ROM drive.
The vold process manages the CD-ROM device and performs the mounting. The CD-ROM should mount 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.
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
Do one of the following:
•
If vold is running, the system displays the process identification number of vold. If the system does not display anything, then restart the daemon by entering:
•
If the vold daemon is running but did not mount the CD-ROM, then stop the vold daemon process using the kill command and restart the daemon:
# kill -9 process_ID_number
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.
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 3
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 4
Make sure your remote machine is enabled as an NFS server by entering:
# ps -ef | grep nfs | grep -v grep
Verify that the /usr/lib/nfs/nfsd and /usr/lib/nfs/mountd daemons are running.
If the daemons you verified are not running, enable your machine as an NFS server by entering:
# /etc/init.d/nfs.server start
Step 5
When your machine is enabled as an NFS server, run either of the following commands:
Steps to Perform on the Local System
On the local system:
Step 1
Go to the machine on which you want to install IPM.
Step 2
Log in as the root user as described in the "Creating Root User Privileges" section.
If the /cdrom directory does not already exist, create it using the
mkdir command:
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.
Unmounting the CD-ROM Drive
After you install IPM, you must unmount the CD-ROM drive as explained in the following sections:
•
Unmounting a Local CD-ROM Drive
•
Unmounting a Remote CD-ROM Drive
Unmounting a Local CD-ROM Drive
To unmount a local CD-ROM drive:
Step 1
Log in as the root user as described in Creating Root User Privileges. The command prompt changes to the pound sign (#).
Step 2
Run the following commands:
Step 3
Remove the CD-ROM and store it in a safe place.
Unmounting a Remote CD-ROM Drive
To unmount a remote CD-ROM drive:
Step 1
Log in as the root user on the local machine and run the following command:
Step 2
Log in as the root user on the remote machine and run the following command:
Step 3
Remove the CD-ROM and store it in a safe place.
Installing IPM on Solaris
The IPM client software can either reside with the IPM server, or it can be installed on another system located on the same network as the IPM server. Also, the IPM server on Solaris can be accessed by IPM clients running on
Windows 2000 Professional, Windows XP Professional, or Windows 2000 Server systems.
Overview of Installing IPM on Solaris
You can install both the IPM server software and client software on a Solaris system using the following menu options provided by the setup program:
•
Install IPM Server and Client—Use when you want the IPM server and client software to reside on the same Solaris system.
•
Install IPM Client Only—Use when you want to install only the IPM client software on this system, or if you must install the IPM client software separately from the server software.
The IPM software consists of the following Solaris packages:
•
Common services (CSCOcwbS)
•
IPM server (CSCOipm-s)
•
IPM client (CSCOipm-c)
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 only the IPM client, only the client component (CSCOipm-c) must be successfully installed.
Note
Use the setup.sh program provided with the IPM software to install IPM on your Solaris system.
Running the Setup Program on Solaris
Before you run the setup program on Solaris:
•
Verify the location of the Netscape browser executable file. The IPM setup program asks you to provide the full path to this file during the installation.
If the IPM installation program determines that Netscape Communicator is installed in the default directory, /opt/netscape/netscape, then this location is used.
If necessary, you can change the location of Netscape Communicator after installing IPM by using the ipm browserpath command.
You would require Netscape if you want to access IPM from a Solaris client.
•
The default for each prompt is the value in brackets. To accept any default value, press Enter. To stop the installation script at any time, press Break or Ctrl-C.
To begin the installation of the IPM software on Solaris:
Step 1
Log in as the root user as described in the "Creating Root User Privileges" section.
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:
Step 4
Start the installation script by entering the following command:
The following IPM setup program menu appears:
**********************************************************************
* +|+ +|+ Performance Monitor +|+ +|+ *
* +|||||+ +|||||+ +|||||+ +|||||+ *
* ++|||||||++++|||||||++ Setup Program ++|||||||++++|||||||++*
* Empowering The ============== Internet Generation*
**********************************************************************
1) Review README File First (Recommended)
2) Install IPM Server and Client
3) Install IPM Client Only
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 appears:
Enter full Netscape browser executable pathname: ? [/opt/netscape/netscape]
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 system meets the hardware and software requirements for running IPM.
If your system meets the requirements for IPM, the following prompt appears:
If you have selected to install IPM Server or IPM Server and client, IPM prompts you to enter Database and Administrative password.
Step 6
Enter a new Database password.
The password is case sensitive and should begin with an alphabet. You can enter only a maximum of 15 characters and you can enter only alphanumeric characters.
Step 7
Enter the Administrative password.
The password is case sensitive and should begin with an alphabet. You can enter only a maximum of 15 characters and you can enter only alphanumeric characters.
IPM displays the following prompts:
Do you want the Express Install (y/n)? [Y]
Step 8
Select one of the following
•
y or press Enter to select the Express Install which installs IPM using all default settings.
•
n to select the standard installation which prompts you for additional information such as port numbers, product path, and filename.
If your system does not meet all the requirements for IPM, the installation program proceeds with the standard installation and you are prompted for information such as port numbers, 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-s> was successful.
INFO: Checking Installation.
INFO: Package CSCOcwbS installed OK. Verifying... OK.
INFO: Package CSCOipm-s installed OK. Verifying... OK.
Creating IPM Client Web Download Image...
Finished creating IPM Client Web Download Image...
Integrating IPM server with CiscoWorks Common Services...
To use this product, set your path to:
Check the documentation for supported browsers and versions.
============================- Error Summary -=========================
No Errors were encountered during installation.
======================================================================
Started : Tue Aug 4 06:30:38 Asia/Calcutta 2004
Finished: Tue Aug 4 06:51:02 Asia/Calcutta 2004
======================================================================
===================- IPM Server Install Tool Completed -==============
======================================================================
Depending on the installation option you selected, a menu appears with options to start the software or exit setup. If the installation was successful, select an option to start the software.
The following menu appears when you install the IPM server and client software:
**********************************************************************
* +|+ +|+ Performance Monitor +|+ +|+ *
* +|||||+ +|||||+ +|||||+ +|||||+ *
* ++|||||||++++|||||||++ Startup Options ++|||||||++++|||||||++*
* Empowering The =============== Internet Generation*
**********************************************************************
1) Start IPM Server and Client
Please choose an option ->
The following menu appears when you install only the IPM client software:
**********************************************************************
* +|+ +|+ Performance Monitor +|+ +|+ *
* +|||||+ +|||||+ +|||||+ +|||||+ *
* ++|||||||++++|||||||++ Startup Options ++|||||||++++|||||||++*
* Empowering The =============== Internet Generation*
**********************************************************************
1) Start IPM Client and Connect to Default Remote Server - cwb-sun4
2) Start IPM Client and Connect to Alternate Remote Server
Please choose an option ->
To start the IPM server and client at a later time from the command line, enter:
To start only the IPM server at a later time from the command line, enter:
For a complete list of all of the IPM commands, see the "IPM Command Reference" appendix in the User Guide for Internetwork Performance Monitor.
Running the Express Installation
The IPM software express installation method allows you to accept all of the default settings and minimizes the need to respond to system prompts.
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 uses are available and that adequate space exists in the default installation directory (/opt).
If your system meets these requirements, the installation program provides the option to run the express installation.
Note
The express installation option is available only when you are installing the IPM server and IPM client software at the same time.
The following example shows the express installation option for the IPM client software:
**********************************************************************
* +|+ +|+ Performance Monitor +|+ +|+ *
* +|||||+ +|||||+ +|||||+ +|||||+ *
* ++|||||||++++|||||||++ Setup Program ++|||||||++++|||||||++*
* Empowering The ============== Internet Generation*
**********************************************************************
1) Review README File First (Recommended)
2) Install IPM Server and Client
3) Install IPM Client Only
Please choose an option -> 3
======================================================================
=================- IPM Client Install Tool Started -==================
Started : Tue Aug 4 17:14:59 PDT 2004
Host : SunOS ipm01-u10 5.8 Generic_108528-13 sun4u sparc SUNW,Ultra-5_10
======================================================================
=========================================================================================-
System Requirements Check -======================
======================================================================INFO: Checking
UID... root, OK.
INFO: Checking Install Image... OK.
INFO: Checking Host Operating System... SunOS, OK.
INFO: Checking Operating System Version... 5.8, OK.
INFO: Checking Solaris patches [108528-13]...OK.
INFO: Checking Solaris patches [108652-35]...OK.
INFO: Checking Solaris patches [108827-15]...OK.
INFO: Checking Solaris patches [109324-02]...OK.
INFO: Checking Solaris patches [109326-05]...OK.
INFO: Checking Solaris patches [110286-02]...OK.
INFO: Checking Solaris patches [110615-01]...OK.
INFO: Checking Solaris patches [110662-02]...OK.
INFO: Checking Solaris patches [110670-01]...OK.
INFO: Checking Solaris patches [110700-01]...OK.
INFO: Checking Solaris patches [110898-02]...OK.
INFO: Checking Solaris patches [110934-01]...OK.
INFO: Checking Solaris patches [110945-01]...OK.
INFO: Checking Solaris patches [110951-01]...OK.
INFO: Checking Solaris patches [111085-02]...OK.
INFO: Checking Solaris patches [111327-02]...OK.
INFO: Checking Solaris patches [111626-01]...OK.
INFO: This product requires:
INFO: Checking Ram... OK.
INFO: Checking Swap... OK.
INFO : Checking the - "casusers" group ... OK
INFO : Checking the - "casuser" account ... 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:
INFO: Checking default disk space requirements... OK.
============================================================
============================================================
===================- IPM Client Summary -===================
============================================================
INFO: The following ports will be used:
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] y
If the program detects that the ports are unavailable, or that there is insufficient space in the default installation directory, the express installation is disabled. 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 which shows a disabled express installation option for the IPM server software.
Installing IPM to a Different Directory
To install the IPM software in a directory other than the /opt default directory, do not run the express installation method. The standard installation method allows you to specify a new location to install the IPM software.
If the setup program detects insufficient space in the /opt default directory, it cannot execute the express installation and it looks for an alternate directory.
The following example shows a case in which 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:
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]
Specifying Alternate Ports
The IPM server software uses the following default ports:
•
Open Server Gateway—44341/tcp
•
Naming Server—44342/udp
The IPM client software must know what ports the IPM server is using. By default, the client uses the following ports:
•
Naming Server—44342/udp
When you install the IPM server, or the IPM server and client, the IPM installation program determines whether or not these ports are available. (This is not done when you install only the IPM client.)
If there are conflicts with the ports, the software provides you with the option to specify an alternate port number.
For example, if port 44342/udp is already in use for the Naming Server, IPM prompts you to specify an alternate port.
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 system from the server, you must make sure 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.
Verifying Port Usage
IPM registers all the ports it uses in the /etc/services file. If you want to find out what ports are currently in use on your system, you can run the following netstat command for the corresponding port type (tcp or udp):
# netstat -a -n -f inet -P {tcp|udp}
Caution 
If you are specifying an alternate port, do not use ports 1 through 1023 as they are reserved for system processes.
Re-installing IPM
If you have an existing IPM 2.6 and Common Services 3.0 installation, and if you re-install Common Services, IPM 2.6 will stop working. To ensure that IPM continues to work in the same state as it was before you re-installed Common Services, run this command:
ipm cw2ksetup install
This command must be run after you re-install Common Services and it ensures that IPM is integrated with Common Services.
Installing the IPM Client on Solaris From the CiscoWorks Homepage
You can download access the IPM client installation software from the CiscoWorks Homepage. This is useful if you do not have the CD-ROM, or if you prefer to download the software.
After you have downloaded the IPM client installation software to your system, you must install the software on your local system by running the setupCli.sh command.
The following procedure explains how to download, uncompress, extract, and install the IPM client software on a Solaris system.
To install the IPM client on Solaris using the Web interface:
Step 1
Create a temporary directory in a disk partition that contains at least 64 MB of space on the system where you want to install the IPM client software.
Step 2
Go to the URL for the CiscoWorks homepage from your browser.
The CiscoWorks Homepage appears (Figure 4-1).
Figure 4-1 CiscoWorks Homepage
Note
If you do not have this information, contact the system administrator who installed the IPM server software.
Step 3
Click Admin > Download Client on the CiscoWorks homepage.
The IPM Client for Solaris page (Figure 4-2) appears.
Figure 4-2 IPM Client for Solaris Page
Step 4
Click Solaris Client to download the client installation files.
Step 5
Enter the user name and password.
Step 6
When prompted, specify the directory where you want the installation software files to be downloaded, such as /temp-directory.
Step 7
Go to the Solaris command line and change to the directory where you downloaded the installation software and uncompress the files and enter:
# uncompress CSCOipmClient.tar.Z
Step 8
Go to the directory where you uncompressed the files and extract the IPM client installation files to the CDImage directory. Enter:
# /usr/bin/tar -xvf CSCOipmClient.tar
Step 9
Change to the CDImage directory and run the IPM client software installation program, enter:
Step 10
Verify that the IPM client software installed successfully and remove all installation files in the temporary directory, enter:
Where temp_directory is the directory containing the downloaded files.
Verifying IPM Installation on Solaris
You can verify successful installation of the IPM server and client software by:
•
Checking for Error Messages
•
Viewing Packaging Information for the IPM Server and Client
•
Verifying the Installation Directories
•
Starting IPM
Checking for Error Messages
During installation, messages are recorded in a log file to provide diagnostic information about problems that might arise. The location of the installation log file is provided at the end of the IPM installation script.
To check for installation error messages:
Step 1
Examine the log file by using the following command:
# more install_directory/install/cisco_ipmsvr_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.
Viewing Packaging Information for the IPM Server and Client
You can use the pkginfo command to verify that the IPM server (CSCOipm-s and CSCOcwbS) and IPM client (CSCOipm-c) software packages are installed on your system.
To view packaging information for the IPM server and client:
Step 1
Run the pkginfo command as shown in the following examples:
Step 2
Verify that you receive output similar to the following display for each component you query with the pkginfo command:
VENDOR: Cisco Systems, Inc
PSTAMP: rme33-u10m02110619
INSTDATE: Apr 02 2002 14:48
STATUS: completely installed
FILES: 532 installed pathnames
217258 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 installed.
ERROR: information for "CSCOipm-s" was not found
You can verify that the IPM Server and IPM Client are installed on your system from the CiscoWorks HomePage.
To do this: Select Common Services > Software Center > Software Update from the CiscoWorks Homepage. The Software Updates page displays a table of applications installed along with packages and installation dates.
Verifying the Installation Directories
After you install IPM, use the ls command to verify that you have a new directory structure containing the IPM software:
•
For the IPM server and its services, the default directories are /opt/CSCOipm and /opt/CSCOcwbS.
•
For the IPM client, the default directory is /opt/CSCOipmClient.
Starting IPM
After you install the IPM server and client software, verify that you can start the IPM software. You can start the IPM software by selecting the corresponding option on the start-up menu after the setup program is complete.
You can also start the IPM server and client by entering:
If you installed the IPM server and client on different systems, use the following commands to start IPM:
•
To start the IPM server, enter:
•
To start the IPM client, enter:
# cd /opt/CSCOipmClient/bin
# ./ipm start client server_name
If the IPM server and client installation was successful, the IPM Main Window opens (Figure 4-3).
Figure 4-3 IPM Main Window
Uninstalling IPM on Solaris
The uninstall program provides you with a menu similar to that presented for installation. You can choose 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:
•
Common services (CSCOcwbS)
•
IPM server (CSCOipm-s)
•
IPM client (CSCOipm-c)
When you uninstall both the IPM server and client software on the same system, all of the listed package components must be uninstalled successfully.
When you uninstall only the IPM server, both the components (CSCOcwbS and CSCOipm-s) of the IPM server software must be uninstalled successfully. When you uninstall only the IPM client, only the client component (CSCOipm-c) must be uninstalled successfully.
Note
You can uninstall only the Client component when both the IPM server and client software reside on the same Solaris system, and only after you have uninstalled the IPM Server component successfully.
Uninstalling IPM on Solaris is discussed in the following sections:
•
Overview of Uninstalling IPM on Solaris
•
Running the Uninstall Program on Solaris
Overview of Uninstalling IPM on Solaris
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 want to remove only the IPM server software on this system. This option removes both the common services (CSCOcwbS) package and the IPM server (CSCOipm-s) package.
Uninstalling the IPM server also disables the IPM client. To uninstall the IPM server, we strongly recommend you choose option 1 (uninstall both the IPM server and the IPM client).
3.
Uninstall IPM Client Only—Use when you want to remove only the IPM client software on this system. This option removes the IPM client (CSCOipm-c) package. You can uninstall only the Client component when both the IPM server and client software reside on the same Solaris system, and only after you have uninstalled the IPM Server component successfully.
Caution 
The Web client will not work if you remove client software from a machine that has server and client software installed.
Running the Uninstall Program on Solaris
To uninstall the IPM software on Solaris:
Note
To stop the uninstall process at any time, press Break or Ctrl-C.
Step 1
Log in as the root user as described in the Creating Root User Privileges.
If you are running an IPM client locally, stop the client by selecting File > Exit from the IPM Main Window.
Step 2
Stop the IPM server by running:
If you want to preserve any of the IPM server data in the database, run the following command to change directories and copy the database to a temporary directory:
# cd /opt/CSCOcwbS/db/CSCOipm
Step 3
Start the uninstall script by running the following commands:
# cd /opt/CSCOipm/install
The following menu appears:
**********************************************************************
* +|+ +|+ Performance Monitor +|+ +|+ *
* +|||||+ +|||||+ +|||||+ +|||||+ *
* ++|||||||++++|||||||++ Uninstall Program ++|||||||++++|||||||++*
* Empowering The ================== Internet Generation*
**********************************************************************
1) Uninstall IPM Server and Client
2) Uninstall IPM Server Only
Please choose an option ->
Step 4
Type the number of the desired option and press Enter.
Step 5
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 6
Wait for the uninstallation to complete and verify that you receive messages corresponding to the packages you selected for removal.
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:
Please review /var/tmp/cisco_ipmsvr_uninstall.log for detailed results
To further verify that the IPM server and its associated services are uninstalled, run the following pkginfo commands:
Step 7
Verify that you receive a message for each package you uninstalled as shown in the following example, indicating that the package could not be found:
ERROR: information for "CSCOipm-s" was not found.