Table of Contents

Installation Requirements Summary
Determine Your Host Configuration
Verify the Hardware Requirements

Disk Space Requirements
Swap Space

Verify the Solaris Operating System Prerequisites

Operating System Version
Operating System Patch Level
Operating System Resource Limits
Per Process Resource Limits

Getting Started

This chapter provides pre-installation requirements. Before installing CPC, you must complete the following:

• Determine which host system (Sun SPARCstations) you will use for the Informix database server, the CPC Server, and the CPC Client(s). Together these host systems comprise your host configuration.

• Verify that the hardware requirements are met.

• Verify that the Solaris operating system software prerequisites are met.

• Verify that the Informix software prerequisites are met.

• Verify that the Java Development Kit (JDK) software prerequisites are met.

Note   The Solaris operating system, and Informix RDBMS must be licensed independently and installed prior to installing CPC. Guidelines for installing and verifying these components are described in this guide.

Installation Requirements Summary

Table 3-1 provides a list of the software requirements for CPC. These requirements are explained in more detail throughout the chapter.

Table 3-1: Installation Requirements for CPC

Vendor	Software Product	Version	Notes
Sun	Solaris Operating System	2.5.1 or 2.6	See patch requirements below
Sun	Solaris 2.5.1 Patch	101242-11	SUNWlibC 5.5.1
Sun	Solaris 2.5.1 Patch	103566-08	Java native threads patch
Sun	Solaris 2.5.1 Patch	103640-08	Java native threads patch
Sun	Solaris 2.5.1 Patch	103461-18	Motif patch
Sun	Solaris 2.5.1 Year 2000 Patch Cluster	July 26, 1999 or later	Refer to the Appendix titled, "Recommended Patches" for a list of the patches included in this cluster.
Sun	Solaris 2.5.1 Cluster Patch	Dec 8, 1997 or later	Refer to the Appendix titled, "Recommended Patches" for a list of the patches included in this cluster.
Sun	Solaris 2.6 Patch	105591-02	SunOS 5.6: shared library patch for C++ (libC.so.5)
Sun	Solaris 2.6 Year 2000 Patch Cluster	July 27, 1999 or later	Refer to the Appendix titled, "Recommended Patches" for a list of the patches included in this cluster.
Sun	Solaris 2.6 Recommended Patch Cluster	July 24, 1998	Refer to the Appendix titled, "Recommended Patches" for a list of the patches included in this cluster.
Sun	CDE	1.0.2 (for Solaris 2.5.1), 1.2 (for Solaris 2.6)
Sun	Java	JRE 1.1.6	The CPC installation will set the environment variables JAVA_HOME, JAVA_LIB, and JAVA_BIN, and will put JAVA_BIN on the path.
Informix	Informix Database	7.3 UC7	You must have access to an Informix database server, and have database creation privileges.

Determine Your Host Configuration

To meet a range of customer performance and capacity requirements, the CPC software comprises two distinct components, the CPC Server and the CPC Client. You can choose to run these components on a variety of host system configurations using the following guidelines:

• You can run the CPC Server component on only one host system in your installation. This host system is called the Server host.

• You can run the CPC Client software on one or more host systems, depending on the number of concurrent CPC sessions (either Operators or applications) your installation needs to support. These host systems are called Client hosts and each Client host is capable of supporting one or more concurrent sessions.

• You need a host system to run the Informix RDBMS server. This host system is called the Informix host.

• Host systems can be combined. For example, one host system can be both the Server host, the Client host, and the Informix host (as illustrated Figure 3-1 below). It is possible to run everything on a single host system.

• You can install the CPC Server or Client software files locally on the Server or Client host; or you can install the software files on any NFS file server on your LAN that is mounted by the Server and Client hosts.

Note   In addition to host systems for CPC, you will need host systems to run the network management systems. The host system hardware requirements described in this chapter do not include the requirements for network management systems or for the Informix RDBMS.

Verify the Hardware Requirements

Once you have determined what your host configuration will be, you must verify that your host system hardware is sized correctly. If you decide to run everything on a single host system, the minimum recommended hardware requirements for a single Operator are:

• Single host configuration (combined CPC Server, Client, and Informix Server, see Figure 3-1 above):

  • Sun UltraSPARC 60,2 CPUs

  • 9 BG hard disk with a minimum 2 GB partition for Informix

  • 512 MB physical RAM

  • CD-ROM drive, mouse, keyboard, monitor

  • graphics card with at least 256-color map. Note that running other applications concurrently with CPC may reduce the number of available entries in the color map and an 1152 x 900 pixel display (minimum).

Higher capacity configurations are possible. For example, if you need to support four concurrent Operators, the recommended minimum 2-host configuration (see Figure 3-2 above) is:

• Server host:

  • Sun UltraSPARC 450, 3 CPUs

  • 1 GB physical RAM

  • 9 GB hard disk with a minimum 2 GB raw partition for Informix

• Server Client host for four concurrent Operators):

  • 256 MB physical RAM

  • 4 GB hard disk

Disk Space Requirements

If you plan to install CPC and all related software, such as Informix, on one machine, you should have about 4GB of available disk space. The installation process requires an additional 350 MB in either /tmp or another location specified as an argument to the installation kit.

Check to make sure that you have enough disk space in the /tmp directory using the following command:

df -k /tmp

Swap Space

The recommended minimum swap space allocation, for both Server and Client hosts, is twice the amount of physical RAM, up to 1 GB of physical RAM, and an equal amount of swap space for physical RAM in excess of 1 GB.

For example, if the host system has 512 MB of physical RAM, the swap space allocation should be at least 1024 MB. If the host system has 2 GB of physical RAM, the swap space allocation should be 3 GB: 2 GB for the first 1 GB of physical RAM and an additional 1GB for the second 1 GB of physical RAM.

To determine the amount of swap space (used and available) on a particular host system, login to the host system and issue the following command at a terminal prompt:

swap -s

The commands used in this chapter are in the /usr/bin, /usr/sbin,
/usr/openwin/bin directories. For convenience, be sure these paths are included in your PATH environment variable.

Verify the Solaris Operating System Prerequisites

Operating System Version

Verify that both the Server and Client(s) hosts are running either Solaris version 2.5.1 (which comprises SunOS Release 5.5.1, and CDE Version 1.0.2) or Solaris version 2.6 (which comprises SunOS Release 5.6, and CDE Version 1.2). You can verify the Solaris version as follows:

• To display the SunOS version number, login to the host system and issue the following command at a terminal prompt:

uname -a

• To display the CDE, and SunOS version numbers, login to a CDE session on the host system from the console or through an X-terminal. As you login, the system will display a Solaris welcome screen showing the CDE version number. Then, at a terminal prompt, issue the following command:

wsinfo

This command will display such information as the workstation type, operating system version, physical memory (RAM), and virtual memory (swap).

Operating System Patch Level

Verify that both the Server and Client(s) hosts have the required Solaris operating system patches installed listed in Table 3-2.

To verify that a patch has been installed, issue the following command at terminal prompt:

showrev -p grep <patch number>

where <patch number> is the patch number you wish to verify

For a complete list of recommended patches included in the Patch Cluster, refer to Appendix A.

Any patch with a version number greater than the ones listed here are acceptable provided they have the same patch number. For example, if patch number 12345-23 is specified, then any patch 12345-nm is acceptable in nm is 23 or greater. Patches may also be downloaded from the Sun Microsystems website at http://www.sun.com if they are not installed on your system.

Patch installation is simplest if the patch tar file is copied into an empty current working directory with at least 110MB of free space.

Operating System Resource Limits

Verify that the Solaris operating system resource limits are set at least as high as the values listed in Table 3-2. To display the current resource limit settings, enter the following command at the terminal prompt:

sysdef

To change a resource limit setting, you must add or edit the corresponding set command in the system configuration information file (/etc/system) and then reboot the host system. Instructions for editing the /etc/system file are contained within the file itself and in the man page for the system(4):

man -s4 system

Note   Any changes to the /etc/systemfile require a reboot of the system.

Other applications might have different system resource requirements; you must verify that your system resource limits are sufficient to run these other applications. If a particular resource limit is already higher than required for CPC, do not reduce it.

Table 3-2: System Resource Requirements

Resource ID	Description	Variable in /etc/system file	Minimum Value
SEMMAP	entries in semaphore map	semsys:seminfo_semmap	64
SEMMNI	semaphore identifiers	semsys:seminfo_semmni	4096
SEMMNS	semaphores in system	semsys:seminfo_semmns	4096
SEMMNU	undo structures in system	semsys:seminfo_semmnu	4096
SEMMSL	max semaphores per id	semsys:seminfo_semmsl	100
SEMOPM	max operations per semop call	semsys:seminfo_semopm	10
SEMUME	max undo entries per process	semsys:seminfo_semume	64
SEMVMX	semaphore maximum value	semsys:seminfo_semvmx	32767
SEMAEM	adjust on exit max value	semsys:seminfo_semaem	16384
SHMMNI	shared memory identifiers	shmsys:shminfo_shmmni	100
SHMSEG	max attached segments per process	shmsys:shminfo_shmseg	100
SHMMIN	min shared memory segment size	shmsys:shminfo_shmmin	100
SHMMAX	max shared memory segment size	shmsys:shminfo_shmmax	268435456

Per Process Resource Limits

Verify that the "per process" resource limits are set at least as high as the values listed in Table 3-3. To display all of the current resource limits, use the command:

ulimit -a

To modify the current resource limit settings, use the ulimit command with options. For more information on using the ulimit command, refer to the man pages by entering:

man ulimit

Other applications might have different "per process" resource requirements; you must verify that your system resource limits are sufficient to run these other applications. If a particular resource limit is already higher than required for CPC, do not reduce it.

Table 3-4: Installation Worksheet

Prompt/Argument	Description	Default Value	Your Value
CMS SERVER host name	Hostname of the CPC Server host system	name of the machine being installed on
CMS SERVER Logger port	Port number for the Logger process	7127
CMS SERVER NameServer port	Port number for the NameServer process	7128
CMS SERVER WatchDog port	Port number for the WatchDog process	7129
DATABASE name	Name to be given to the CPC database	<admin>cmsdb
Username used to create the DATABASE	Name of the login account to use to create the database	<admin>
Password for the username used to create the database	Password for the login account to use to create the database	none
DATABASE SERVER hostname	Hostname of the Informix host system	name of the database server machine
Is CORBA to be enabled?	Enable or Disable CORBA	N
CORBA DAEMON hostname	Hostname of CORBA DAEMON	name of the machine being installed on
CORBA DAEMON port	Port number for the CORBA DAEMON	1570
CORBA local domain name	Local domain name for CORBA	syndesis.com
INFORMIXSERVER	Hostname of the Informix host system	none
INFORMIXDIR	Path to the home directory of the Informix installation	none
ONCONFIG	Name of the Informix configuration file found in $INFORMIXDIR/etc	none
Server mount	Mount point or fully-qualified path to the Server software installation directory	/opt/cpc/Server
Client host name(s)	Hostname(s) of the Client host(s) in your installation	none
JAVA_HOME	Path to the installation directory of JRE on each Client host	none

Posted: Thu Aug 3 16:36:35 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.