|
|
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:
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 4-1 provides a worksheet that you can use to record the information that applies to your installation.
| 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. |
|
|
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. Note that 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.
Step 2 Display the admintool interface by entering:
admintool
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 a new group for CPC and Informix
| Attribute | Description | Sample Value |
|---|---|---|
Group Name | 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 | Specifies a group | 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 |
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 admin and informix users.
| 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 | 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 /disk2/SY/users/informix
Step 5 Edit the .profile file with a text editor. The values listed below must be specified.
Informix user:
 |
Note The hostname specified for INFORMIXSERVER and ONCONGIF must be entered in lower case for all user profiles. |
Step 6 Change to the CPC admin user directory by entering:
cd /disk2/SY/users/admin
Step 7 Edit the .profile with a text editor, Augment the text in the profile to ensure that the values are set as values listed below.
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 .profile file for the client accounts in order to run CPC.
|
Note System startup will fail if the DISPLAY variable exceeds 31 characters. |
To run CPC as a Client user, additional setup is required. The following example illustrates how to modify the client user's .profile:
|
Note 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 |
The required version of Informix for CPC is Informix OnLine Version 7.30 UC11.
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:
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.
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. |
You should create a symbolic link to the raw partition and make sure that the permissions and ownership are correct. The link should not be in the Informix home directory.
A sample set of commands to create a partition are:
mkdir /disk2/SY/informixdb cd /disk2/SY/informixdb ln -s /dev/rdsk/c0t3d0s6 raw_dev chmod 660 /dev/rdsk/c0t3d0s6 chown informix /dev/rdsk/c0t3d0s6 chgrp informix /dev/rdsk/c0t3d0s6
|
Note If you are unsure about the location of the raw partition, contact your system administrator. |
Step 2 Make a directory for the Informix installation by entering the following command:
mkdir /disk2/SY/informix ln -s /disk2/SY/informix /opt/informix
Step 3 Change to the newly created directory by entering:
cd /opt/informix
Step 4 Extract Informix from the CD by entering:
tar xvf device-name where device-name is the name of the UNIX device containing the
OnLine media.
Step 5 Export the following environment variable by entering:
export INFORMIXDIR=/opt/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.
Step 2 Change to the /informix/etc directory by entering:
cd /opt/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 4-4 lists the values that you must customize.
| 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/informix/etc
Step 6 Edit the sqlhosts file using a text editor. Add the following line:
hostname ontlitcp hostname online2
Step 7 Change to the /etc directory by entering:
cd / etc
Step 8 View the service 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 user the oninit command. Do not use oninit-i again, or your database will be lost. |
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. JRE is included as a patch with this release. JRE_SystemInstall.bin is found in the /cdrom/cdrom0/install directory.
mkdir /disk2/SY/java chown admin /disk2/SY/java chgrp cpc /disk2/SY/java chmod 775 /disk2/SY/java
Step 2 Login 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 /disk2/SY/java
Step 5 Run the patch by executing the following command:
/cdrom/cdrom0/install/JRE_SystemInstall.bin
If the installation is successful, it will create a directory called jre1.2.1_04p.
After you have completed these pre-installation steps you must reboot the system. Reboot your system by enter the following command (as root):
sync; sync; init 6
There are two parts to the CPC installation procedure. There is a separate Server installation and a separate Client installation.
Complete the following preparatory steps before installing CPC.
Step 2 Create the base installation area for installing the CPC software by entering:
mkdir /disk2/SY/CPC
Step 3 Create a symbolic link to the opt/directory
ln -s /disk2/SY/CPC /opt/CPC
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 software with the following steps:
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 Login 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--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/ActivatorKit.bin -s
Step 10 Respond to the prompts accordingly. To accept a default just press Enter. 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 the chapter titled "Administration". In the following example, the CPC Server and Informix host are the same system (hostname: rainbow).
|
Note 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 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 cannot 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/ActivatorKit.bin -s NetProvision(tm) Activator (tm) Installation Version 3.2 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(iceberg): 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(iceberg): Enter the password for the username used to create the database(): adminpassword Is CORBA to be enabled (N): Enter the CORBA DAEMON host name(iceberg): 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 succession. All resources are required.
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 |
RASO_ResourceInstall.bin | Installs the ATM Service Application |
RFSO_ResourceInstall.bin | Installs the Frame Relay Service Application |
SCB_ResourceInstall.bin | Installs the Private Line Service Application |
SDL_ResourceInstall.bin | Installs the DSL Service Application |
VPI_ServiceInstall.bin | Installs the IP-VPN Service Application |
CS_BladeInstall.bin | Installs the Cisco WAN Equipment Module |
C4_BladeInstall.bin | Installs the Cisco 6400 Equipment Module |
C2_BladeInstall.bin | Installs the Cisco 6260 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 2.0 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
$
Step 16 Patching programs for any given installation kit are identified by the same upper case acronym used to identify the kit. For example, patches to the RA ResourceInstall (for ATM) would be installed by the program RAPatch 001. A special patching program SRPatch 001 may also be found. The patches should be installed in the following orderL SRPatch, then patches in the same order as the original kits were installed.
Install any patches in the /cdrom/cdrom0/install directory by entering:
/cdrom/cdrom0/install/xxPatchnnn where xxPatchnnn is the name of the Patch.
Step 17 Add security privileges for CPC users:
For example, for the admin user, enter:
cd /opt/CPC/Server/mng/utility . syccpovdef 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.
Step 18 Test the Server installation as follows:
a. Logoff by entering:
exit
b. Login to the CPC admin account.
su - admin cd../CPC/Server ../mng/utility/syccpovdef
c. If you are using the CORBA, start the CORBA daemon by entering:
SYcorba -s
d. Start the CPC server as follows:
SYnpt - sS
performing system startup (server only)
tail -f $CCP_OUTPUT/current/*npt*/stdout
This command should display a list of the current processes that should include:
starting SYNameServer
starting SYLogger
starting SYSecurityServer
starting SYMVCServer
starting SYSiteServer
starting SYCCSServer
starting SYCRController starting SYGuardianAngel starting SYChangeInitiationManager starting SYCorbaDispatcher starting AVCorbaDispatcher 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 tiled "Automating CPC Start-Up" in the chapter titled "Administration".
The CPC Client software must be installed so that it is accessible by all Client host(s). If the Client host(s) 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 host(s) 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 2 Load the CPC CD-ROM in 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 3 Change to the Client installation subdirectory:
cd /opt/CPC/Client
Step 4 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.
a. Verify on the client workstation that the Server directory has been exported.
/usr/sbin/dfshares CPC Server
b. Create a directory for the Server Mount.
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 - yes soft,bg.rw
d. Mount the CPC Server.
mount -a
e. Navigate to the /usr/lib/nfs directory
f. Enter ./nfsd
g. Enter ./mountd
Step 5 Install the CPC activation engine software by entering:
NetProvision(tm) Activator (tm) Installation Version 3.2 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 - *************** 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 Install the CPC Resource Models, Equipment Modules, and Service Applications by running the following commands in succession. All resources are required.
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 |
RASO_ResourceInstall.bin | Installs the ATM Service Application |
RFSO_ResourceInstall.bin | Installs the Frame Relay Service Application |
SCB_ResourceInstall.bin | Installs the Private Line Service Application |
SDL_ResourceInstall.bin | Installs the DSL Service Application |
VPI_ServiceInstall.bin | Installs the IP-VPN Service Application |
CS_BladeInstall.bin | Installs the Cisco WAN Equipment Module |
C4_BladeInstall.bin | Installs the Cisco 6400 Equipment Module |
C2_BladeInstall.bin | Installs the Cisco 6260 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/cdrom0/install/SGTSO_ServiceInstall.bin NetProvision (tm) SGTSO Service Installation Version 3.2 Unpacking...
This is a Client installation
copying files
REMEMBER to remove directory and files in: /tmp/BladeInstall.2197
$
Step 7 Patching programs for any given installation kit are identified by the same upper case acronym used to identify the kit. For example, patches to the RA ResourceInstall (for ATM) would be installed by the program RAPatch 001. A special patching program SRPatch 001 may also be found. The patches should be installed in the following orderL SRPatch, then patches in the same order as the original kits were installed.
Install any patches in the /cdrom/cdrom0/install directory by entering:
/cdrom/cdrom0/install/xxPatchnnn where xxPatchnnn is the name of the Patch.
Step 8 Add Client Users for CPC by entering:
export DISPLAY="hostname":0.0 cd /opt/cpc/Client/mng/utility/ . syccpovdef 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. Make sure that the user environment variable is not set.
Step 9 Run the VP Key Merger utility by entering:
/opt/CPC/Client/mng/utility/vpkeymerger
|
Note The VP Key Merger utility must be run separately for each Client User. |
. syccpovdef
Step 2 Test the Client Installation as follows:
SYnpt -sC
This command should display:
performing system startup (client only)
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.
If the Client GUI does not appear, change to the output directory and view the log files by entering the following commands.
cd SCCP OUTPUT/current more */stdout
This will provide you with information about why the CPC Client did not start.
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 the chapter titled "Administration".
If you did not enable CORBA during the installation of the CPC Server, complete the following steps to enable CORBA.
Step 2 Make sure that the Server is shut down:
Synpt h
Step 3 Execute:
cd $CCP_REL/mng/config
Step 4 Edit the file configFile.site file as follows.
a. Remove the comment sign (#) from the beginning of the following line:
#SYCRB.SYCorbaDispatcher SYCorbaDispatcher
Step 5 Execute:
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 as follows:
#SYNPT.server15 = AVCorbaDispatcher
Step 7 Register CORBA:
syRegisterCorba
Step 8 Ensure that the CORBA servers are started using SYcorba 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. |
CPC patches are executable files that must be run within sourced Activator environments. Patches apply only to certain CPC releases. To view specific information about the patch, run the patch with a -l option:
XXPatchYYY -l
Where XX is the component code, and YYY is the patch number, for example:
CSPatch002 -l
This command displays the following:
Patch : CS8.1.0.00.02.pch NPA (s) : 3.2 PR(s) : 9876 - bandwidth is incorrect Special Instructions : System can be running, database is changed, : Prerequisite patch: CS8.1.0.00.01.pch
The description of the above output is as follows:
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 write permission when running a patch with the -l option. The XXPatchYYY 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 with the same component sequentially according to the patch number (exceptions are specified in the Special Instructions section). For example, you should never 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 (not any user) must be sourced.
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
XXPatchYYY -l
Step 4 Shutdown the CPC Server:
SYnpt -h
Step 5 Apply the patches as directed in the Special Instructions section of the patch information.
XXPatchYYY
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:
XXPatchYYY -l
Step 4 Shutdown the CPC Client (make sure that all client sessions are shutdown for this client installation):
SYnpt -h
Step 5 Apply the patches as directed in the Special instructions section of the patch information:
XXPatchYYY
After both the Server and Client have been patched successfully, you may start the CPC Server and Client as normal.
|
Note Each applied patch will leave a log of itself in the $CCP_MNG/version_info directory. |
CPC installations may need to be removed for several reasons:
Step 2 Drop the database using the following Informix command:
dbaccess -dd
Step 3 Remove the CPC Client installation directory:
rm - fr /opt/CPC/Server
This section describes the directory structure and the files contained therein that are relevant to the CPC Administrator. Two structures are described.
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 4-8 lists the CPCDist subdirectories and their functions.
| 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. |
$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 4-9 lists the $CCP REL subdirectories and their functions.
| 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. |
This directory maintains the internal CPC data. It consists of the following subdirectories:
This directory maintains all CPC log files. For more information about reading the log files, refer to the chapter titled "Maintenance". The log directory consists of the following subdirectories:
This directory maintains all CPC management files. It consists of the following subdirectories:
This directory contains the user directories and files for the user which can be customized. This directory is important for multi-user Client Installations.
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's Guide after you have run avupdate.
For each CPC installation, the steps are:
Step 2 Backup the installation database.
Step 3 Run the update utility.
To backup the installation files, perform the following procedure.
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:
tar cvf /tmp/install.tar .
To backup the installation database, perform the following procedure.
Step 2 Determine the amount of space required by using dbaccess and running the following SQL.
Select sum(size)* from sysmaster:sysdatabase, 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.
To run the update utility, perform the following procedure.
Step 2 Locate the directory containing the installation software (in this example,
/cdrom) and execute:
/cdrom/avupdate
In the event of errors during an update:
Step 2 Restore the installation database (for server installations only).
To restore the installation files, perform the following procedure.
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
To restore the installation database, perform the following procedure.
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.
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 of 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:
cd $CCP OUTPUT/current/<procss 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. See Changing Informix Password in the chapter titled "Administration".
Step 3 If the Client fails to start, check to see that you have completed the following steps:
a. 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
b. As the root user, open another window and enter the command:
xhost +
Posted: Thu Aug 3 16:37:21 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.