Cisco Provisioning Center Installation and Administration Guide, 3.0
Initial Installation
Downloads: This chapterpdf (PDF - 368.0KB) | Feedback

Initial Installation

Table Of Contents

Initial Installation

Installation Worksheet

Create the Group and User Accounts

Using Admintool

Add Groups

Add Users

Setting CPC User Accounts

Verify the Informix Software Prerequisites

Informix Licensing

Create Data Space for Informix

Raw Partition Space

Configuring the Raw Device

Installing Informix OnLine

Configuring Informix

Verify the Java Runtime Environment Software Prerequisites

Installing the Java Runtime

Patching the Java Runtime

Reboot the System

Install CPC

CPC Pre-Installation

Install the Server

Install CPC Server Patches

Run the SYfinalizeInstall Utility

Add Server Users

Test the Server Installation

Install the Client

Install CPC Client Patches

Run the SYfinalizeInstall Utility

Add Client Users

Test the Client Installation

Enabling CORBA After the Initial CPC Installation

Patching a CPC Installation

Server Patching

Client Patching

Removing a CPC Installation

To Remove a CPC Installation

Understanding the CPC Release Directory

Distribution Structure

Installed Structure

Directory Contents

CPC Runtime Upgrade Process

Backing up the Installation Files

Backing up the Installation Database

Running the Update Utility

Database Migration Error Recovery

Restoring the Installation Files

Restoring the Installation Database

Troubleshooting Server and Client Start-Up


Initial Installation


This chapter provides instructions for the initial installation of Cisco Provisioning Center and the associated software programs. The initial installation is comprised of the following steps:

Complete the Installation Worksheet

Create the Informix and CPC Group and User Accounts

Configure Environment Variables for CPC Users

Install Informix OnLine

Configure Informix

Install the Java Runtime

Install the CPC server

Install the CPC client

Patch a CPC Installation (as required)

Installation Worksheet

During the installation of the CPC server and client software and the creation of CPC Operator accounts, you will be prompted for some information.

Table 3-1 provides a worksheet that you can use to record the information that applies to your installation.

Table 3-1 Installation Worksheet 

Prompt/Argument
Description
Default Value
Your Value

CMS SERVER hostname

Hostname of the CPC server host system (must not include the hyphen '-' character)

none

 

CMS SERVER Logger port

Port numbers for the logger process

7127

 

CMS SERVER NameServer port

Port numbers for the NameServer process

7128

 

CMS WatchDog port

Port number for the WatchDog process

7129

 

DATABASE name

Name to be given to the CPC database

admincmsdb

 

username used to create the DATABASE

Name to be given to the CPC 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

none

 

Is CORBA to be enabled?

Enable or disable CORBA

name of the machine being installed on

 

CORBA DAEMON port

Port number for the CORBA DAEMON

1570

 

CORBA local domain name

Local domain 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

none

 

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.

   

Create the Group and User Accounts

You must create a group name and account number for the Informix database and the CPC account. You must also create a user account for the CPC Administrator and the Informix admin users. You can also create multiple user accounts for other CPC users. All CPC user accounts that you create must belong to the same CPC group account and the Informix admin user account must belong to the Informix group account. For Informix the group name and user account must be informix (lowercase).

You can create user and group accounts through the admintool utility or through the command line interface. Creating accounts with admintool is described below.

Using Admintool


Step 1 Log in to the system as root.

Step 2 Display the admintool interface by entering:

admintool

Add Groups


Step 1 Select Groups from the Browse pull-down menu.

Step 2 Select Add from the Edit pull-down menu.

Step 3 Fill in the required values, listed below, in the dialog box that displays.
You need to create new groups for both CPC and Informix.


Table 3-2 Group Attribute Values  

Attribute
Description
Sample Value

Group Name

Mandatory.

Specifies a name used by the system to identify a user's group. A group name is a text string composed of lowercase alphabetical characters (a-z) and digits (0-9). A group name can be 1-8 characters.

cpc, informix

Group ID

Mandatory.

Specifies a group
identification number used by the system to create a user's primary group. By default the next available number displays here.

102, 103

Members List

Optional.

Specifies users or groups who belong to this group. If there is more than one member in the list, then separate names with a comma but do not use any spaces.

bill,bob,barney


Add Users


Step 1 Select Users from the Browse pull-down menu.

Step 2 Select Add from the Edit pull-down menu.

Step 3 Fill in the required values, listed below, in the dialog box that displays.
You need to create new users for both CPC and Informix.


Table 3-3 User Attribute Values  

Attribute
Description
Sample Value

User Name

Required.

Specifies the login name the operating system will use to identify this user. The user name must be a unique name composed of uppercase or lowercase alphabetical characters (a-z) or digits (0-9). A user name can be 1-8 characters long.

admin, informix

User ID

Required.

Specifies a number by which the operating system can identify a user. The user's UID is typically a number between 100 and 60000.

1003, 1004

Primary Group

Required.

Specifies a group number or a group name.The operating system will assign the group number to files
created by the user.

cpc, informix

Secondary Groups

Optional.

Specifies other groups this user will belong to.

 

Comment

Optional.

Specifies notes about this user account.

 

Login Shell

Required.

Specifies a login shell for the user. The Korn shell is mandatory.

 

Password

Required.

Specifies the means by which a user sets up a password.

Select Normal Password from the drop-down menu and enter a password for the user.

Min Change

Optional.

Specifies the minimum number of days allowed between password changes.

 

Max Change

Optional.

Specifies the maximum number of days a user can go without having to set up a new password.

 

Max Inactive

Optional.

Specifies the maximum number of days the user account can be inactive before the user must set up a new password.

 

Expiration Date

Optional.

Specifies the expiration day, month, and year for a user's password.

 

Warning

Optional.

Specifies when users will start receiving warning messages about their password expiring.

 

Create Home Dir

Required

Specifies whether or not the user's home directory is to be set up automatically. By default, the user's home directory is set up automatically.

Yes

Path

Required

Specifies the path for the user's home directory. The path is where admintool will place the user's initialization files. If Create Home Dir is selected you must specify a path.

/disk2/SY/users/admin

disk2/SY/users/informix


Step 4 Change to the Informix users directory by entering:

cd /opt/CPC/users/informix 

Step 5 Edit the .profile file with a text editor. The values listed below must be specified.

Informix user:

export INFORMIXSERVER=hostname
where hostname is the name of the computer on which Informix is installed

export INFORMIXDIR=/opt/informix

export PATH=$PATH:$INFORMIXDIR/bin

export ONCONFIG=onconfig.hostname


Note The hostname specified for INFORMIXSERVER and ONCONFIG must be entered in lower case for all user profiles.


Step 6 Change to the CPC admin user directory by entering:

cd /opt/CPC/users/admin

Step 7 Edit the user profile with a text editor.

vi .profile

Step 8 Add the following lines to the profile:

export INFORMIXSERVER=hostname

export INFORMIXDIR=/opt/informix

export ONCONFIG=onconfig.hostname

export JAVA_HOME=/opt/CPC/java/jre1.2.1_04p

export PATH=$JAVA_HOME/bin:$PATH:$INFORMIXDIR/bin

CCP_REL=/opt/CPC/Server

if [[ -f $CCP_REL/mng/utility/syccpovdef ]]


Setting CPC User Accounts

You can create additional CPC user accounts for Operators and Network Managers.

All accounts must run in a Korn shell (ksh) environment because CPC uses scripts in that syntax. The admin account and all client accounts must belong to the same UNIX group. The following environment variables must be set in the user profile for all client accounts in order to run CPC.

export DISPLAY=hostname:0.0

export JAVA_HOME=/opt/java/jre1.2.1_04p

export JAVA_BIN=$JAVA_HOME/bin

export JAVA_LIB =$JAVA_HOME/lib

export PATH =$JAVA_BIN:$PATH

user=username . /opt/CPC/Client/mng/utility/syccpovdef


Note A space is required on both sides of the "." in the last variable.

System startup will fail if the DISPLAY variable exceeds 31 characters.

The JAVA_HOME environment variable is necessary to run the CPC client. This variable must be a path to a Java runtime installation. For more information about Java runtime requirements, refer to the section "Installing the Java Runtime" section.

If you plan to login as admin using a CDE session, then edit the .dtprofile file in the admin home directory to add (or uncomment) the following line:
DTSOURCEPROFILE=true


Verify the Informix Software Prerequisites

The required version of Informix for CPC is Informix OnLine Version 7.30 UC11.

Informix Licensing

Informix must be licensed separately from CPC. The following formula can be used to determine the number of "Informix users" required to be licensed for a given CPC environment.

nInformix = 2 * (nSession + 2 + nAbort)

where:

nInformix is the number of database connections to the Informix server. Informix calls this the number of users

nSession is the number of CPC sessions. Usually, a GUI or FTI thread counts as one session each

nAbort is the number of sessions currently cleaning up after abnormal session termination

Create Data Space for Informix

The procedures described below and the installation procedures described in the following chapter assume that you have not yet installed Informix. If Informix has already been installed, you can ignore these steps.

Informix uses a raw partition for data space.

Raw Partition Space

Decide on how much space you need for the database. A 1-2 Gb partition should be enough. Create the partition close to the centre of the disk for better performance. If you start the partition at cylinder 0, initialization of Informix will overwrite the disk's partition table which is stored on track 1. There are two ways around this problem. One is to create a placeholder partition with a size of 1 cylinder at cylinder 0. This placeholder will keep the partition table safe. The other solution is to use Informix's ROOTOFFSET and MIRROROFFSET parameters. For more information on offsets, refer to the Informix documentation.


Note Do not mount or newfs the Informix data space partition.


Configuring the Raw Device

You should create a symbolic link to the raw partition and make sure that the permissions and ownership are correct. Do not put the link anywhere in the Informix home directory.


Step 1 Make a directory for the Informix raw partition by issuing the following command:

mkdir /opt/CPC/informixdb

Step 2 Change to the new directory by issuing the following command:

cd /opt/CPC/informixdb

/opt/CPC/informixdb is the path to the informix directory


Step 3 Create a symbolic link within this directory by issuing the following command:

ln -s /dev/rdsk/<rawdisk> raw_dev

where <rawdisk> is the location of the raw device

Step 4 Change permissions and ownership using the following commands:

chmod 660 /dev/rdsk/rawdisk
chown informix /dev/rdsk/rawdisk
chgrp informix /dev/rdsk/rawdisk

Note To view the permissions for the link, enter: ls -l raw_dev



Installing Informix OnLine


Note The following steps outline the recommended procedure for a basic installation of Informix OnLine. More advanced scenarios are possible. For more information on installing Informix OnLine, refer to the appropriate Informix documentation.



Step 1 Log in as root.

Step 2 Create a directory for the Informix installation by entering the following command:

mkdir /opt/CPC/informix

Step 3 Change to the newly created directory by entering:

cd /opt/CPC/informix

Step 4 Extract Informix from the CD by entering:

tar xvf filename

where filename is the absolute path of the directory containing the OnLine media.


Step 5 Export the following environment variable by entering:

export INFORMIXDIR=/opt/CPC/informix

Step 6 Start the installation script by entering:

./installserver

Step 7 The Informix welcome screen displays. Press Return when prompted, as indicated below:

INFORMIX-OnLine Version 7.3.UC11 
Copyright (C) 1986-1999 Informix Software, Inc.
Installation and Configuration Script
This installation procedure must be run by root (super-user). It will change the owner, 
group, mode and other file attributes on secure systems of all files of this package in 
this directory. 
There must be a user "informix" and a group "informix" known to the system.
	Press RETURN to continue, or the interrupt key (usually CTRL-C or DEL) to abort.
<RETURN> 

Step 8 You will be asked to provide the serial number and key for the software.

Enter your serial number (for example, INF#X999999)
INF#Xnnnnnn <RETURN>
Enter your serial number KEY (uppercase letters only)
XXXXXX <RETURN>
Once you have correctly entered the serial number and key, the system displays the 
following:
WARNING: This INFORMIX SOFTWARE, INC. SOFTWARE is licensed for use on this computer 
system. In the event you exceed the End User License Agreement, and the licenses granted 
to you thereunder, are subject to immediate termination by Informix.
Press RETURN to continue or the interrupt key (usually CTRL-C or DEL)to abort.
<RETURN>

Step 9 Installation will proceed normally.



Configuring Informix


Step 1 Log in as the Informix user.

Step 2 Change to the /informix/etc directory by entering:

cd /opt/CPC/informix/etc

Step 3 Copy the onconfig.std file and rename it by entering:

cp onconfig.std onconfig.hostname

where hostname is the name of the host computer.


Step 4 Customize the onconfig.hostname file using a text editor. Table 3-4 lists the values that you must customize.

Table 3-4 Customized Values for onconfig.hostname file  

Variable
Description
Example Value based on Minimum Hardware Configuration

ROOTOFFSET

Value of 0 or greater specifying the offset into the disk partition or device to reach the initial chunk of root dbspace

0

ROOTNAME

Provide a name

rootdbs

ROOTPATH

Absolute path to the data space file or symbolic link to the raw partition

/disk2/SY/infomixdb/raw_dev

ROOTSIZE

Size of the root database space (in Kbytes)

300000

DBSPACETEMP

Temporary dbspace (set to ROOTNAME value)

 

SERVERNUM

Unique number between 0 and 255

 

LOGFILES

Number of logical log files

6

LOGSIZE

Logical log size (in Kbytes)

6000

MSGPATH

Path for system message log files

/opt/informix/online.log

CONSOLE

Absolute path for console messages

 

TAPEDEV

For archival backups

/dev/null

LTAPEDEV

For Transaction log backups. This is set to /dev/null if not backing up Transaction logs

/dev/null

DBSERVERNAME

Name of default database server

hostname

RESIDENT

Forced residency flag (1=yes, 2=no)

1

MULTIPROCESSOR

Multiprocessor enable

0

NUMCPUVPS

Number of virtual CPU processors

1

SINGLE_CPU_VP

Maximum number of virtual CPU processors

1

NOAGE

UNIX scheduler processes aging disable

1

LOCKS

Maximum number of locks

20000

BUFFERS

Maximum number of shared memory buffers that user threads have available for disk I/O on behalf of client applications

10000

LOGSMAX

Maximum number of logical log files

16

RA_PAGES

Number of pages to attempt to read ahead

4

RA_THRESHOLD

Number of pages left before next group

2



Step 5 Return to the /informix/etc directory by entering:

cd /opt/CPC/informix/etc

Step 6 Edit the sqlhosts file using a text editor. Add the following line:

<hostname> ontlitcp <hostname> online2

where <hostname> is the name of the Informix server host.


Step 7 Change to the /etc directory by entering:

cd /etc

Step 8 View the services file to make sure the following line appears:

online2 1002/tcp #informix

Step 9 If this line does not appear in the file, add it with a text editor.


Step 10 Initialize the database by entering:

oninit -i

Note To shutdown the database use the onmode-k command. To re-start the database use the oninit command. Do not use oninit-i again, or your database will be lost.



Verify the Java Runtime Environment Software Prerequisites

The Java Runtime Environment (JRE) version 1.2.1 must be installed on or accessible to each client host. To verify that you have installed the correct version of the JRE, login to each client host machine and enter the following command at the terminal prompt:

cd <app_path>/java/jre1.2.1 

where <app_path> is the path where applications such as the JRE are installed. If the JRE version 1.2.1 is installed, then the path ~/jre1.2.1 will exist. If the cd command fails, you do not have the JRE version 1.2.1 installed or it has been installed in a different path.

The full path of the JRE version 1.2.1 installation must be used to set the JAVA_HOME environment variable for each CPC Operator. This path will have the format:

<app_path>/java/jre1.2.1 

If JRE is not installed, you must install it.

Installing the Java Runtime

Java runtime must be installed prior to installing the CPC server and client software. The Java runtime is provided in the following file:

JRE_SystemInstall.bin

To install the Java runtime, perform the following procedure.


Step 1 As the root user, create a Java installation directory by executing the following commands (where /opt/CPC is the path to the Java installation directory):

mkdir /opt/CPC/java
chown admin /opt/CPC/java
chgrp cpc /opt/CPC/java
chmod 775 /opt/CPC/java

Step 2 Log in as the admin user.

Step 3 Set the following environment variable:

export CCP_REL=/tmp

Step 4 Change to the directory in which you want the Java installation to occur:

cd opt/CPC/java

Step 5 Install the Java runtime by executing the following command:

/cdrom/cdrom0/install/JRE_SystemInstall.bin

If the installation is successful, it will create a directory named jre1.2.1_04p.


Patching the Java Runtime

After you have installed the Java runtime and the jre1.2.1_04p directory has been created, you must install necessary Solaris patches for Java. Within the jre1.2.1_04p directory there is a readme file that contains complete information about installation and patching requirements. Follow the instructions in this file carefully. Pay particularly close attention to the patching instructions for Solaris under the section titled "Requirements".

All tar files mentioned in the readme file must be obtained from Sun at http://sunsolve.sun.com. Ignore the section titled "JDK/JRE Installation - Self-extracting binary" as this has already been fulfilled by the installation of the JRE_SystemInstall.bin file distributed with the CPC software.

Ensure that JAVA_HOME is set to the Java installation directory (containing this readme file) and that $JAVA_HOME/bin appears on the PATH environment variable in ksh.

Reboot the System

After you have completed these pre-installation steps you must reboot the system. Reboot your system by entering the following command (as root):

sync; sync; init 6

Install CPC

There are two parts to the CPC installation procedure. There is a separate server installation and a separate client installation.

CPC Pre-Installation

Complete the following preparatory steps before installing CPC.


Step 1 Log in as the root account.

Step 2 Create the base installation area for installing the CPC software and change its ownership and group permissions to specify the admin user under the cpc group:

mkdir /opt/CPC
chown admin /opt/CPC
chgrp cpc /opt/CPC
chmod 755 /opt/CPC

Step 3 Log in as the admin account.


Step 4 Create the server installation subdirectory:

mkdir /opt/CPC/Server

Step 5 Create the client installation subdirectory:

mkdir /opt/CPC/Client

Install the Server

Install the server software with the following steps:


Step 1 Log in as the root account. If you require a distributed multi user installation, go to step 2, otherwise, go to step 6.

Step 2 For a distributed multi user installation, the machine acting as the CPC server must be set up as a NFS server. Verify that the nfsd process is running.

ps -aef | grep nfsd

Step 3 If nfsd is not running, go to step 5. If nfsd is running, export the CPC server directory by editing the file/etc/usr/dfstab to include the following line (this ensures that the CPC server will be re-exported if the system is rebooted):

share -F nfs -o rw -d "CPC_Server" /opt/CPC/Server

Step 4 Apply these changes immediately by entering:

usr/sbin/shareall

Step 5 If nsfd is not running, edit the file/etc/dfs/dfsharetab to include the following line:

/usr/sbin/share -F nfs -o rw -d "CPC_Server" /opt/CPC/Server

and then start the network file server daemon:

/etc/init.d/nfs.server start

Step 6 Log in as the admin account.

Step 7 Load the CPC CD-ROM in the CD-ROM drive attached to (or mounted by) the CPC server host system. The following steps assume the CD-ROM device name is/cdrom/cdrom0. You should substitute the correct device name for your installation.


Step 8 Change to the server installation subdirectory:

cd /opt/CPC/Server

Step 9 Install the CPC activation engine software by entering:

/cdrom/cdrom0/install/cpcKit.bin -s

Step 10 Respond to the prompts accordingly. Press Enter to accept a default value. The only prompt for which you must provide information is the database creation password. If you enter an incorrect password at this prompt, you must change the password by completing the procedure outlined in the section "Changing Informix Database Server Password" in "Administration." In the following example, the CPC server and Informix host are the same system (hostname: rainbow).

The port numbers with default values of 7127, 7128, and 7129 must be unique for each installation of CPC. If you have multiple copies of CPC installed on the same host you must select unique port values for each installation.

As well, the DATABASE name must be unique for each CPC installation that is using the same version of Informix. The DATABASE name must be 18 characters or less. The first character must be a letter (a-z) or an underscore (_). The remaining letters can be any combination of letters, numbers, and underscores.

The DOMAIN name will vary according to the site where CPC is installed. Please consult the network administrator for the valid domain name. If you want to install the CORBA API provided with CPC, you must respond 'Y' to the enable CORBA prompt. If you do not want to enable the CORBA, you will still be prompted for the CORBA-specific configuration information. You can accept the default values provided. This will allow you to enable CORBA at a later date without having to re-install CPC.

$cdrom/cdrom0/install/cpcKit.bin -s
CPC (tm) Installation
										Version 3.0 

Unpacking...
Copy NPS files
/usr/bin/uncompress -c
/tmp/CPCInstall.470/kitfiles/nps_server.tar.Z
	/usr/sbin/tar xof -
Copy CPC files
/usr/bin/uncompress -c
/tmp/CPCInstall.470/kitfiles/kit_server.tar.Z |
	/usr/sbin/tar xof -
Enter the CMS SERVER host name(rainbow):
Enter the CMS SERVER Logger port(7127):
Enter the CMS SERVER NameServer port(7128):
Enter the CMS SERVER WatchDog port(7129):
Enter the DATABASE name(admincmsdb): 
Enter the username used to create the DATABASE(admin): 
Enter the DATABASE SERVER host name(rainbow): 
Enter the password for the username used to create the database(): adminpassword
Is CORBA to be enabled (N):
Enter the CORBA DAEMON host name(rainbow): 
Enter the CORBA DAEMON port (1570):
Enter the CORBA local domain name (syndesis.com):
Now creating ./mng/config/configFile.site

*************** Invoking: synptsetup -s ../config/configFile.site
Reading configuration file ...
Global or global/transaction server install ...


Step 11 Check to make sure that the Informix database server is running before proceeding by entering the following command:

onstat

Step 12 Create the CPC database by entering the following commands:

cd /opt/CPC/Server/mng/utility
. syccpovdef
./SYccpDBbuild

and respond y when prompted:

$ ./SYccpDBbuild
Do you want to create database <Y/N>
y
CREATE DATABASE admincmsdb WITH LOG
Database created.
Database closed.
Creating and Initializing tables proceeding ...
The database has been created.
Creating database messages are logged in /tmp/admincmsdb.log.
$ 

Step 13 If you are using CORBA (you entered Y at the" Is CORBA to be enabled" prompt) enter the following command:

syRegisterCorba 

Step 14 Change to the server installation directory by entering:

cd /opt/CPC/Server 

Step 15 Install the CPC Resource Models, Equipment Modules, and Service Applications by running the following commands in the order listed in Table 3-5. Installation of all Resource Models is required.

Table 3-5 Install File s

Install File (cdrom/install/...)
Description

RF_ResourceInstall.bin

Installs the Frame Relay Resource Model

RA_ResourceInstall.bin

Installs the ATM Resource Model

RC_ResourceInstall.bin

Installs the CBR (Constant Bit Rate) Resource Model

RD_ResourceInstall.bin

Installs the DSL (Digital Subscriber Line) Resource Model

RL_ResourceInstall.bin

Installs the LAN (Local Area Network) Resource Model

RI_ResourceInstall.bin

Installs the IP (Internet Protocol) Resource Model

RP_ResourceInstall.bin

Installs the Partner Resource Model

SCR_ServiceInstall.bin

Installs the Resource Model for Service Applications built with Service Designer

RASO_ServiceInstall.bin

Installs the ATM Service Application

RFSO_ServiceInstall.bin

Installs the Frame Relay Service Application

SCB_ServiceInstall.bin

Installs the Private Line Service Application

SDL_ServiceInstall.bin

Installs the DSL Service Application

VPI_ServiceInstall.bin

Installs the IP-VPN Service Application

CS_BladeInstall.bin

Installs the Cisco WAN Equipment Module

C1_BladeInstall.bin

Installs the Cisco NI-1 Equipment Module

C4_BladeInstall.bin

Installs the Cisco 6400 Equipment Module

C2_BladeInstall.bin

Installs the Cisco NI-2 Equipment Module

CV_BladeInstall.bin

Installs the Cisco VPN Solutions Center Equipment Module



Each of these commands will display a progress report, similar to the
following example:

	$cdrom/install/RASO_ServiceInstall.bin
Cisco Provisioning Center (tm) RASO Service Installation
												Version 3.3
	Unpacking... 
	This is a Server installation 
	Creating Tables 
	loading Metadata 
	Creating triggers/procedures 
	Database loading complete 
	copying files 
	REMEMBER to remove directory and files in: /tmp/BladeInstall.1391 
	$

Install CPC Server Patches

Patching programs for any given installation kit are identified by the same upper case acronym used to identify the kit. Patches should be installed in the same order as the original kits were installed. Any patches with the code "SR" in the /cdrom/cdrom0/install directory should be installed first.

Complete these steps to install the CPC server patches:


Step 1 Install SRPatches:

/cdrom/cdrom0/install/SRPatchnnn

where nnn is the three digit patch number associated with the SRPatch.

Step 2 Install Equipment Module patches in the /cdrom/cdrom0/install directory by entering:

cdrom/cdrom0/install/XXPatchnnn

where XX is the Equipment Module component code and nnn is the patch number.

Step 3 Install Service Application patches in the /cdrom/cdrom0/install directory by entering:

cdrom/cdrom0/install/XXXPatchnnn

where XXX is the Service Application component code and nnn is the patch number.


Run the SYfinalizeInstall Utility

Run the Finalize Install utility by entering:

/opt/CPC/Server/mng/utility/SYfinalizeInstall

Add Server Users

Add security privileges for CPC users. For example, for the admin user, enter:

addServerUser admin superUser 

Repeat this step for any other users of the CPC server, replacing admin with the user IDs of all clients who will be using CPC.

Test the Server Installation

Test the server installation as follows:


Step 1 Logoff by entering:

exit

Step 2 Login to the CPC admin account.

su - admin
cd../CPC/Server
. ./mng/utility/syccpovdef

Step 3 If you are using the CORBA, start the CORBA daemon by entering:

SYcorba -s 

Step 4 Start the CPC server as follows:

SYnpt - sS

This command should display:

performing system startup (server only)

Step 5 Execute the following command:

tail -f $CCP_OUTPUT/current/*npt*/stdout

This command should display a list of the current processes that will be similar to the following output:

starting SYNameServer 
starting SYLogger 
starting SYSecurityServer 
starting SYMVCServer 
starting SYSiteServer 
starting SYCCSServer 
starting  SYCRController
starting  SYGuardianAngel
starting  SYChangeInitiationManager
system startup complete

The CPC server software is now installed—you can start and stop the server software manually, or you can configure the server software to start automatically when the CPC server system boots. For detailed instructions, refer to the section titled "Automating CPC Start-Up" on page 4-2 of "Administration."

Install the Client

The CPC client software must be installed so that it is accessible by all client hosts. If the client hosts will access the files on a common file server, the client software only needs to be installed once (on the file server). If the client hosts will access the files on their local hard disks, the client software must be installed on each client host.

Install the client software by completing the following steps:


Step 1 Log in as the admin account. If you are performing a distributed multi-user installation you must create a user with the same User Name, User ID, and Primary Group as the CPC user you created in the section titled "Create the Group and User Accounts". This should be done in each client machine.

Step 2 If you are performing a distributed multi-user installation, you must mount the server to a local hard disk on each client machine. Mount the server by performing the following procedure as root:

a. Verify on the client workstation that the server directory has been exported.

user/sbin/dfshares CPC_Server

b. Create a directory for the server mount (must be done as admin user).

mkdir /opt/cpc/Server

c. Edit the file /etc/vfstab to include the following line (this ensures that the CPC server will be re-mounted if the system is rebooted).

<server_hostname>: /opt/cpc/Server - /opt/cpc/Server nfs - yes soft,bg,rw

where server_hostname is the hostname of the machine where the CPC server is installed.

d. Mount the CPC server.

mount -a

If you are unable to mount the server, you must start the daemon. As the root user:

a. Navigate to the / usr/lib/nfs/directory

b. Enter the following:

./nfsd

c. Enter the following:

./mountd

Step 3 Load the CPC CD-ROM into the CD-ROM drive attached to (or mounted by) the CPC client host system. The following steps assume the CD-ROM device name is /cdrom - you should substitute the correct device name for your installation.

Step 4 Change to the client installation subdirectory:

cd /opt/cpc/Client

Step 5 Install the CPC activation engine software by entering:

/cdrom/cdrom0/install/cpcKit.bin -c /opt/cpc/Server

where /opt/cpc/Server is the path to your server installation directory. In the case of a multiple-client distribution, the you would enter the path for the server mount on each client workstation.

The output will resemble the following:

					CPC (tm) Installation
										Version 3.3
Unpacking...
Copy NPS files
/usr/bin/uncompress -c
/tmp/CPCInstall.1630/kitfiles/nps_client.tar.Z
	/usr/sbin/tar xof -
Copy CPC files
/usr/bin/uncompress -c
/tmp/CPCInstall.1630/kitfiles/kit_client.tar.Z |
	/usr/sbin/tar xof -
Now creating ./mng/config/configFile.site

*************** Invoking: synptsetup -c ../disk2.SY/CPC/Server
../config/configFile.site
Reading configuration file ...
Client install ...
*************** Invoking: synptsetup -m ../config/configFile.site
Reading configuration file ...
Multiuser install ... 
$

Step 6 Source the client environment:

. /opt/cpc/Client/mng/utility/syccpovdef

Step 7 Install the CPC Resource Models, Equipment Modules, and Service Applications by running the commands listed in Table 3-5 on page 3-17. Installation of all Resource Models is required.

Each of these commands will display a progress report, similar to the following example:

	$ cdrom/install/RASO_ServiceInstall.bin
						NetProvision (tm) RASO Service Installation
												Version 3.0
	Unpacking... 
	This is a Client installation 
	copying files 
	REMEMBER to remove directory and files in: /tmp/BladeInstall.2197 
	$ 

Install CPC Client Patches

Patching programs for any given installation kit are identified by the same upper case acronym used to identify the kit. Patches should be installed in the same order as the original kits were installed. Any patches with the code "SR" in the /cdrom/cdrom0/install directory should be installed first.

Complete these steps to install the CPC client patches:


Step 1 Enter the following command to install the SRPatches:

/cdrom/cdrom0/install/SRPatchnnn

where nnn is the three digit patch number associated with the SRPatch.

Step 2 Install Equipment Module patches in the /cdrom/cdrom0/install directory by entering:

cdrom/cdrom0/install/XXPatchnnn

where XX is the Equipment Module component code and nnn is the patch number.

Step 3 Install Service Application patches in the /cdrom/cdrom0/install directory by entering:

cdrom/cdrom0/install/XXXPatchnnn

where XXX is the Service Application component code and nnn is the patch number.

The CPC client software is now installed. Repeat the procedure for any additional client host(s) that do not have access to this installation.


Run the SYfinalizeInstall Utility

Run the Finalize Install utility by entering:

/opt/CPC/Client/mng/utility/SYfinalizeInstall

Add Client Users

Add security privileges for CPC users. For example, for the admin user, enter:

addClientUser admin

Repeat this step for any other users of the CPC client, replacing admin with the user IDs of all clients who will be using CPC.

Test the Client Installation

Complete these steps to test the client installation:


Step 1 Establish your user environment:

user=username ./opt/CPC/Client/mng/utility/syccpovdef

where username is the name of a CPC client user

Step 2 Export the DISPLAY variable:

export DISPLAY=hostname:0.0

where hostname is the name of the client host machine

Step 3 Test the client installation as follows:

SYnpt -sC

This command should display:

performing system startup (client only)

Step 4 Wait approximately 30 seconds, then execute the following command:

SYnpt

This command should display:

system is running 

The client GUI should appear on the monitor to which you exported your display.


Step 5 If the client GUI does not appear, change to the output directory and view the log files by entering the following commands.

cd $CCP_OUTPUT/current
more */stdout

This will provide you with information about why the CPC client did not start.

Step 6 Shut down the client as follows:

SYnpt -h

The CPC client software is now installed. You can start and stop the client software manually.


Note The server must be running before you can start a client session.


To automate to CPC startup, refer to "Administration."


Enabling CORBA After the Initial CPC Installation

If you did not enable CORBA during the installation of the CPC server, complete the following steps to enable CORBA.


Step 1 Log in as the admin account and ensure that syccpovdef is sourced in your server environment.

Step 2 Make sure that the server is shut down:

SYnpt -h

Step 3 Execute:

cd $CCP_REL/mng/config

Step 4 Edit the configFile.site file to remove the comment sign (#) from the beginning of the following line:

#SYCRB.SYCorbaDispatcher SYCorbaDispatcher

Step 5 Enter the following command:

synptsetup -s configFile.site

The output will appear as:

Reading configuration file...
Global or global/transaction server install...

Step 6 Edit the files syavconfig.site and syavconfig.site.org to remove the comment sign (#) from the beginning of the following line:

#SYNPT.server15 = AVCorbaDispatcher

Step 7 Register CORBA:

syRegisterCorba

Step 8 Ensure that the CORBA servers are started using SYcorba -s before starting CPC.


Note CORBA can be disabled by re-doing the above steps, adding the comment sign (#) back to the relevant lines that you removed the comment sign from.



Patching a CPC Installation

CPC patches are executable files that must be run within properly configured CPC environments. Patches apply only to certain CPC releases. To view specific information about the patch, run the patch with a -l option:

XXPatchnnn -l

where XX is the component code, and nnn is the patch number, for example:

N7Patch002-1

This command displays output similar to the following:

Patch           : CS8.1.0.0.00.02.pch
NPA (s)         : 3.3.3/31.08
PR(s)           : 8891a - VPI is incorrect
		                  9100b - bandwidth is incorrect
Special Instructions: System can be running, database is changed,
Prerequisite patch: CS81.0.00.01.pch

The description of the above output is as follows:

Table 3-6 Patch Information Listing

Patch
Shows Internal Patch Name.

NPA

Indicates which NPA release this patch applies to.

PR(s)

Brief description of the problem(s) that this patch fixes.

Special Instructions

How to install the patch. What the patch modifies. Prerequisites or precautions.



Note You must be in a directory where you have to write permission when applying patches or running a patch with the -1 option.

The XXPatchnnn format is the external patch numbering system which is relevant to one release stream. The corresponding internal patch number (XXn.n.n.nn.nn.pch) is unique.


In most cases, the CPC server and client should be shut down before applying the patch, unless specified in the Special Instructions section. Also, you should install patches within the same component sequentially according to the patch number (the exceptions are specified in the Special Instructions). For example, you should apply CSPatch001 before CSPatch002. You must apply the patch both to the server and client installations.

Patches must be applied by the admin user account. When applying patches to the client, the environment of the client installation must be sourced.

Server Patching


Step 1 Sign on to the admin account on the CPC server.

su admin

Step 2 Source the server environment:

. /opt/CPC/Server/mng/utility/syccpovdef

Step 3 View the patch information by running the patch with the -l option:

For Equipment Modules and CPC engine (SR) patches:

XXPatchnnn -l

For Service Application patches:
XXXPatchnnn -l

Step 4 Shutdown the CPC server:

SYnpt -h

Step 5 Apply the patch as directed in the Special Instruction section of the patch information.

XXPatchnnn


Client Patching


Step 1 Sign on to the admin account on the CPC client Installation:

su admin

Step 2 Source the environment of the main client installation:

. /opt/CPC/Client/mng/utility/syccpovdef

Step 3 View the patch information by running the patch with the -l option:

For Equipment Modules and CPC engine (SR) patches, enter:

XXPatchnnn -l

For Service Application patches, enter:
XXXPatchnnn -l

Step 4 Shut down the CPC client (make sure that all client sessions are shutdown for this client installation):

SYnpt -h

Step 5 Apply the patch as directed in the Special instruction section of the patch information:

XXPatchnnn

After both the server and client have been patched successfully, you may start the CPC server and client as normal.


Note All applied patches generate a logfile located in the $CCP_MNG/version_info directory. The patches will appear as XXnn.n.n.nn.nn.pch.log corresponding with the internal patch number. Each log contains information on the modifications that the patch incurred.



Removing a CPC Installation

CPC installations may need to be removed for several reasons:

if errors occur during installation

if updates are required to already installed modules.

To Remove a CPC Installation


Step 1 Log in to the admin account and shutdown CPC.

Step 2 Drop the database using the following Informix command:

dbaccess -dd

Respond to the prompts to delete the database.

Step 3 Remove the CPC client installation directory:

chmod -R +w $CCP_REL
rm - rf /opt/CPC/Client

Step 4 Remove the CPC server installation directory:

chomd -R + w $CCP_REL
rm -rf /opt/CPC/ServerRelease Inventory


Understanding the CPC Release Directory

This section describes the directory structure and the files contained therein that are relevant to the CPC Administrator. Two structures are described:

distribution structure

installed structure

Distribution Structure

CPCDist is the mount point for the distribution media. It is the root of the directory tree containing all distribution files. Note that some of the subdirectories may be empty. Table 3-7 lists the CPCDist subdirectories and their functions.

Table 3-7 Distribution Structure 

Directory/File
Function

docs

This directory contains the released documentation

install

This directory contains all installation programs and archives

scripts

This directory contains scripts to be uses with CPC

Manifest

This file contains version information which uniquely identifies a given release.


Installed Structure

$CCP_REL is the base directory where you install CPC. $CCP_REL is set when you establish the environment with syccpovdef. It is the root of the directory tree containing all files for a server and/or client installation. Note that some of the subdirectories may be empty. Table 3-8 lists the $CCP_REL subdirectories and their functions.

Table 3-8 Installed Structure 

Directory/File
Function

data

This directory maintains the internal CPC data files, such as those generated during the CR preparation phase (for example, configuration, activation, and control files).

log

This directory maintains CPC log files such as the Audit log.

mng

This directory maintains CPC management script files.

sys

This directory maintains CPC executable modules and registration files.

user

This directory contains user files in the client or combined installations only. This directory is empty in a server only installation.


Directory Contents

data Directory

This directory maintains the internal CPC data. It consists of the following subdirectories:

AUTOLOAD—This subdirectory contains the TCL routines used by various NPT processes which run the TCL Interpreter to effect translation, delivery, and activation of Change Request information at a given site.

check—This subdirectory contains all the check files used by the check engine to do runtine checking.

chreq—This subdirectory keeps temporary files created for each CR as it is processed. The files consist of product configuration, activation files, and other support files necessary to apply the changes to the network.

The subdirectories are named CRnn for the Change Request number nn and URnn for the Upload Request number nn. These subdirectories contain all files generated during Change Request preparation and are delivered to the network.

db—This subdirectory contains all SQL files that create the default database.

dbsql—This subdirectory contains the database NPT-specific SQL files.

product—This subdirectory is reserved for client network application skeleton files used during Change Request preparation to generate configuration files.

security—This subdirectory contains the securityInfo file.

log Directory

This directory maintains all CPC log files. For more information about reading the log files, refer to "Maintenance." The log directory consists of the following subdirectories:

audit—This subdirectory keeps Audit logs that are generated during CPC processing.

debug—This subdirectory contains the debug log files from all of the executables that had debugging turned on. For more information about configurable debugging parameters, refer to "Maintenance."

event—This subdirectory contains the event log files which logs the system level events and errors.

output—This subdirectory keeps miscellaneous types of log files or debug files created while running CPC. The structure of this directory depends on the mechanism used to start the application. For example, when started by SYnpt, each restart creates an additional subdirectory, name with the date and time of the restart.

site—This subdirectory contains the site log files that track the site state as it progresses through various states of delivery and activation.

siteerror—This subdirectory contains the siteerror log files that track all errors that a site encounters during processing.

systemadmin—This subdirectory contains the messages created by the end user through the error dialog.

mng Directory

This directory maintains all CPC management files. It consists of the following subdirectories:

config—This subdirectory holds all CPC configuration files.

convert—This subdirectory holds conversion scripts for conversions required between different versions of the CPC.

template—This subdirectory contains template files which can be copied and then edited as part of the system configuration. For more information about template files, refer to"Maintenance."

utility—This subdirectory keeps CPC utility script files available for use by the Administrator. For more information about utility files, refer to"Maintenance."

version info—This subdirectory contains version information for the components you installed with CPC.

sys Directory

This directory maintains all CPC system files. It consists of the following subdirectories.

bin—This subdirectory keeps all CPC executable modules, error messages, and OAF files.

cleanup—This subdirectory contains the client-specific cleanup files/scripts that are called when a session critical process dies.

cms—This subdirectory contains the CMS object-specific files.

gui—This subdirectory contains the files which drive the GUI.

java—This subdirectory contains Java archive files and Java classes used for the GUI.

lib—This subdirectory contains the CMS packages.

lrf—This subdirectory contains the local registration files (LRFs, named *.lrf) and argument files (named *.arg). These files are used to start up CPC background processes.

registration—This subdirectory keeps CPC application registration files.

resources—This subdirectory keeps the X default setup .file .ccp_xdefaults and the GUI resource files (bit map files and ptrmsk files).

idl—This subdirectory contains the IDL files for the CORBA interface.

corba—This subdirectory contains the CORBA runtime.

user Directory

This directory contains the user directories and files for the user which can be customized. This directory is important for multi-user client installations.

CPC Runtime Upgrade Process

If you already have an installation of CPC, you can run avupdate to upgrade a new version of CPC. The avupdate utility will upgrade your existing installation. It does not make a backup copy of the existing installation. You must run avupdate for every server and client installation of CPC. If the new installation contains new Service Applications or new Equipment Modules you must install these according to the instructions contained in the User Guide after you have run avupdate.

For each CPC installation, complete these steps:


Step 1 Shut down CPC.

Step 2 Back up the installation files.

Step 3 Backup the installation database.

Step 4 Run the update utility.


Backing up the Installation Files

To back up the installation files, perform the following procedure.


Step 1 Log in as the admin account and ensure that syccpovdef is sourced in your environment.

Step 2 Determine the amount of space required by executing:

df -k $CCP_REL

Step 3 Find enough space on disk or another media (in this example, /tmp) to store the backup archive.

Step 4 Execute:

cd $CCP_REL
su

When prompted, enter the root password.

Step 5 Execute the following command:

tar cvf /tmp/install.tar .


Backing up the Installation Database

To back up the installation database, perform the following procedure.


Step 1 Login as the admin account and ensure that syccpovdef is sourced in your environment.

Step 2 Determine the amount of space required by using dbaccess and running the following SQL command.

Select sum(size)* 2 from sysmaster:sysdatabases, sysmaster:sysextents where name=dbsname 
and name="dbName" 

where dbName is the name of the database (in quotations) defined by $CCPDB.

This takes a few minutes to execute and returns a conservative estimate of the size of the database in kB.

Step 3 Find enough space on disk or another media (in this example /tmp) to store the backup archive. Make sure that the current directory is writeable and execute:

dbexport -q -ss -o /tmp $CCPDB

This creates a logfile (dbexport.out) in the current directory.


Running the Update Utility

To run the update utility, perform the following procedure.


Step 1 Log in as the admin account and ensure that syccpovdef is sourced in your environment.

Step 2 Locate the directory containing the installation software (in this example,
/cdrom/cdrom0) and execute:

/cdrom/cdrom0/avupdate


Database Migration Error Recovery

In the event of errors during an update, complete these steps:


Step 1 Restore the installation files.

Step 2 Restore the installation database (for server installations only).


Restoring the Installation Files

To restore the installation files, perform the following procedure.


Step 1 Login as the admin account and ensure that syccpovdef is sourced in your environment.

Step 2 Locate the installation backup (in this example, /tmp/install.tar). Execute:

cd $CCP_REL
su

When prompted, enter the root password.

Step 3 To remove the damaged installation, execute:

rm -fr *

Step 4 To restore the installation files, execute:

tar xvfp /tmp/install.tar

Restoring the Installation Database

To restore the installation database, perform the following procedure.


Step 1 Login as the admin account and ensure that syccpovdef is sourced in your environment.

Step 2 Delete the database $CCPDB using dbaccess.

Step 3 Locate the installation backup (in this example, /tmp). Make sure that the current directory is writeable and execute:

dbimport -q -i /tmp -l $CCPDB

This creates a logfile (dbimport.out) in the current directory.


Troubleshooting Server and Client Start-Up

CPC produces a log file that corresponds with each process within the start-up of the server and client. In the event of a problem starting up either the server or the client, it is useful to view the associated log files to determine at what point in the start-up process the problem occurred.

To track the processes of the server or client during startup, execute the following command:

tail -f CCP OUTPUT/current/*npt*/stdout

This command will display a list of processes currently running within the server or client start-up.

If one of the processes failed to start, read the corresponding log file by executing the following commands:


Step 1 Navigate to the relevant directory:

cd $CCP_OUTPUT/current/<process name>

Step 2 View the log file:

more stdout

If the server fails to start because of the Informix Database server password was incorrectly set up during the server installation, you only need to change the CCPPASSWORD variable rather than re-install the server. Execute the following procedure:


Step 1 Complete Steps 1 through 5 on page 9 of "Administration," in this guide.

If the client fails to start, check to see that you have completed the following steps:

Step 2 The display variable must be set correctly for the client to run. The command echo $DISPLAY will show the current display configuration. If this configuration is incorrect, you must export the display to your hostname by entering the command:

export DISPLAY=<hostname>:0.0

Step 3 As the root user, open another window and enter the command:

xhost +