|
|
Product No. DOC-785432=
This document contains information to updated the Cisco Access Manager Software Installation and Configuration Guide. It reflects changes made in the 3.1 release of Cisco Access Manager (CAM).
CAM 3.1 now provides:
Use this document in conjunction with the following documents:
The information in this section replaces Chapter 1, "Installing Cisco Access Manager," in the Cisco Access Manager Software Installation and Configuration Guide.
The Cisco AccessPath Integrated Access System and the Cisco AS5800 Universal Access Server are scalable, high-density dial systems designed to terminate a large number of mixed digital and analog calls. Cisco Access Manager (CAM) provides configuration and management functions for your Cisco AccessPath or Cisco AS5800 system.
This chapter describes the procedures for installing and removing CAM and configuring the Netscape FastTrack web server software. You can install the CAM software before or after you install the hardware.
 | TimeSaver f you use CAM to configure your Cisco AccessPath system or Cisco AS5800, you might not need to use the software configuration guide that shipped with your hardware. |
Topics covered in this chapter include:
To install CAM, you must have the following:
| System | Number of CPUs | RAM | CPU Speed | Total Disk Space | Swap Space | Oracle Software/ CAM Database Tablespace |
|---|---|---|---|---|---|---|
Ultra 60 | 2 | 1 GB | 360 MHz | 4 GB | 512 MB | 3 GB |
This section describes the first-time installation of CAM 3.1 on local or remote workstations. For instructions on upgrading Cisco AccessPath Manager (APM) 2.0 to CAM 3.1, see the "Upgrade from APM 2.0" section. For instructions on upgrading CAM 3.0 to CAM 3.1, see the "Upgrade from CAM 3.0" section.
CAM 3.1 installation involves two packages, CSCOcamdb and CSCOcam:
| Package | Requirements/Description | To Install | To Remove | ||||
|---|---|---|---|---|---|---|---|
Must be installed on the same machine as the Oracle server software.
| Run camdb_pkgadd | Run camdb_pkgrm | |||||
Before you can install the CSCOcam package, the CAM database (CSCOcamdb) must be installed and the database instance must be up and running.
| Run cam_pkgadd | Run cam_pkgrm |
CAM 3.1 can be set up in one of two ways:
In either case, however, the CAM database instance (CSCOcamdb) can serve only one CAM system, locally or remotely. See Figure 1.
Prior to installing CAM, the Oracle server software must be installed. To install Oracle, refer to the Oracle database documentation and Appendix A, "Installing Oracle Software."
The CAM 3.1 installation process installs and runs a copy of the Netscape FastTrack web server. Prior to installing CAM 3.1, you must shut down any other web servers installed on the CAM workstation.
To install CAM 3.1 software, complete the procedures described in the following sections:
After the installation, continue with the "Backing Up the CAM Installation" section.
To mount the CD-ROM, complete the following steps:
Step 1 Log in as root.
#su
Step 2 Place the CAM CD-ROM in your CD-ROM drive and mount the drive.
CD-ROM mount policies vary with different systems. In some systems, the CD-ROM is automounted or managed by the Solaris vold process. In such cases, you will have a standard mount point for the CD-ROM such as /cdrom/cdrom0.
If your CD-ROM is not automounted, enter the following command to manually mount the CD-ROM:
# mount -F hsfs -r /dev/dsk/cddevice /cdpath
where:
If you will be installing the CSCOcamdb database on the same machine as the CSCOcam executables, Cisco recommends that you run camdb_pkgadd first.
To install the CSCOcamdb database, complete the following steps:
Step 1 Run the camdb_pkgadd script to create the CSCOcamdb database:
# cd /device # ./camdb_pkgadd
where device is the device name of the CD-ROM drive mount point.
The script allows you to install CAM in a location other than the default location (/opt/CSCOcam). A symbolic link (/opt/CSCOcam) to the actual location is created automatically.
For example:
# cd /cdrom/cdrom0 # ./camdb_pkgadd
You can terminate the script by typing Ctrl-c.
Step 2 Verify that the CSCOcamdb package is being installed on the machine where the Oracle server software is installed, and that the server has sufficient disk space available:
Continue with CSCOcamdb installation? (y/n) [y]
The CSCOcamdb package requires Oracle server software on this machine.
By default, the installation automatically configures the Cisco Access Manager Oracle database. Automatic configuration creates the needed spaces and tables, and requires 2 GB of available disk space on a single file system. If your system does not meet this requirement or you want the table space to be spread over several file systems, DO NOT choose Automatic Configuration in Step 4.
For more information on manual database configuration, refer to the readme file located at /opt/CSCOcamdb/README.database or the section "CAM Database and Upgrade Issues" in "Installing Oracle Software."
If your Oracle Server and Cisco Access Manager will run on different machines, you need to configure the Oracle server as a remote database server. Remote Oracle database setup for Cisco Access Manager is divided into two phases: Database setup and SQL*NET configuration. This installation will setup the database. SQL*NET has to be set up manually on both the local and remote workstations. Contact your Oracle Administrator for site-specific information on configuring SQL*NET.
Step 3 Enter the base directory for the CSCOcamdb installation:
Enter the Base Directory for CSCOcamdb installation? [/opt]
The CSCOcamdb will be installed under the directory basedir/CSCOcamdb.
Step 4 Verify that you have the necessary 2 GB of disk space required for automatic configuration of the tablespace required for the CAM database:
Auto configure Cisco AccessManager Database (y/n)? [y]
Step 5 Enter the installed location of the Oracle software:
Please enter Oracle Home location? [$ORACLE_HOME]
where $ORACLE_HOME is the Oracle home directory environment variable.
For example: /scratch/oracle/product/7.3.4
Oracle must be installed before CAM can be installed. If Oracle is not installed, quit the installation process with Ctrl-c, and install Oracle before continuing.
Step 6 Enter the Oracle username:
Please enter Oracle user name? [oracle]
Step 7 Enter the Oracle group name:
Please enter Oracle group name? [dba]
Step 8 Enter the Oracle database instance name:
Please enter Oracle DB instance name: ? [CAMDB]
Step 9 Enter the location of the CAM database directory (ORACLE_BASE).
By default, database administration scripts will be placed in $ORACLE_BASE/admin/CAMDB, and data files will be placed in $ORACLE_BASE/oradata/CAMDB. $ORACLE_BASE should reside on a file system with 2 GB of available disk space.
Please enter Oracle Base location ? [/oracle/db]
Step 10 Enter the Oracle system user password:
Please enter Oracle default 'system' user password: ? [manager]
Step 11 Enter the CAM database username:
Please enter CAM DB user name? [cam]
Step 12 Enter the CAM database user password:
Please enter CAM DB user password? [cam]
A summary of your selection settings, similar to the following display, will appear.
The following settings will be used: CSCOcamdb Installation Location:/opt/CSCOcamdb Oracle's Home Location: /scratch/oracle/product/7.3.4 Oracle's unix user name:oracle Group name for unix user 'oracle' :dba Automatic Database configuration:YES CAM DB Oracle SID: CAMDB CAM DB user name: cam CAM DB user password:cam CAM DB Data files' Location: /extra/gopal/oradata/CAMDB CAM DB Admin files' Location: /extra/gopal/admin/CAMDB Password for oracle user 'system':manager Are these acceptable, continue install (y/n)? y
Step 13 Review the settings and enter one of the following:
Step 14 If the CSCOcamdb package base directory does not already exist, the installation script will ask if you want the directory to be created:
The selected base directory </opt/CSCOcamdb> must exist before installation is attempted. Do you want this directory created now [y,n,?,q] y Using <opt/CSCOcamdb> as the package base directory.
Confirm the creation of the CSCOcamdb base directory by entering y (press Enter).
If you do not confirm the directory creation, the installation script will terminate.
Step 15 The installation script will next ask you to confirm that the package can perform scripts requiring superuser privileges:
This package contains scripts which will be executed with super-user permission during the process of installing this package. Do you want to continue with the installation of <CSCOcamdb> [y,n,?] y
Confirm that the package can use superuser privileges by entering y (press Enter).
The installation process now installs the CSCOcamdb database on your workstation. No additional CAM-specific intervention is required for the package installation and configuration to complete.
During the final steps of the installation process, file ownerships and permissions are set, and the Oracle CAM database is created and started up. The installation takes 10 to 20 minutes.
If you intend to run Cisco Access Manager on a machine other than the one on which you installed the CSCOcamdb Oracle database, you must manually configure SQL*NET for both local and remote workstations. Contact your Oracle administrator for site-specific information on configuring SQL*NET. In addition, you will need to restart the listener for the new CSCOcamdb instance.
To create an additional CAM database instance, perform the following steps:
Step 1 Make sure that /etc/system has been modified to accommodate for the new database that you will be adding. (If you modify /etc/system, you must reboot the system after making this modification.)
Step 2 Log in as the Oracle user:
# su - oracle
Step 3 Change to the /opt/CSCOcamdb/db/admin directory:
$ cd /opt/CSCOcamdb/db/admin
Step 4 Run the add_dbinstance.sh command:
$ ./add_dbinstance.sh
Step 5 Enter the Oracle user password, or press Enter to accept the default in square brackets [ ]:
Please enter Oracle default 'system' user password: ? [manager]
Step 6 Enter the name of the Oracle database instance you would like to create:
Please enter Oracle DB instance name: ? MYDB
Step 7 Enter the Oracle base location, or press Enter to accept the default in square brackets [ ]:
By default, database admin scripts will be placed in <Oracle Base>/admin/MYDB, and data files will be placed in <Oracle Base>/oradata/MYDB. Please enter Oracle Base location ? [/oracle/db]
Step 8 Enter the Oracle username and password:
Please enter Oracle DB user name ? Please enter Oracle DB user password ?
Step 9 A summary of your selection settings will appear. Review these settings.
CAMHOME=/opt/CSCOcamdb ORACLE_HOME=/oracle/db/product/7.3.4 ORA_SYSTEMPWD=manager ORACLE_SID=MYDB ORACLE_BASE=/oracle/db CAM_DBADMIN=/oracle/db/admin/MYDB CAM_DBDATA=/oracle/db/oradata/MYDB CAM_DBUSER=oracle CAM_DBPASSWORD=password Please review that the environment variables are correct and enter 'y' to continue or 'n' to enter new value (default n) y
Step 10 Run the ApmSchema.sh script, as the root user.
# cd /opt/CSCOcamdb/db/schema # ./ApmSchema.sh <apm_dbuser> <apm_dbpassword> <oracle_sid> <oracle_home>
Step 11 Load the default data into this additional database, from the CAM server machine that will use this database.
# cd /opt/CSCOcam/db/schema # ./ApmData.sh <apm_dbuser> <apm_dbpassword> <oracle_sid>
To install the CSCOcam package, complete the following steps:
Step 1 Run the cam_pkgadd script to install the CSCOcam software:
# cd /device # ./cam_pkgadd
where device is the device name of the CD-ROM drive.
The script allows you to install CAM in a location other than the default location (/opt/CSCOcam). A symbolic link (/opt/CSCOcam) to the actual location is created automatically.
For example:
# cd /cdrom/cdrom0 # ./cam_pkgadd
You can terminate the script by typing Ctrl-c.
Step 2 Specify whether CSCOcam will be using a local or a remote database. (Remote databases are located on a different machine than the one running CSCOcam.)
Cisco Access Manager can use either a local Oracle database or a remote Oracle database. Will Cisco Access Manager use a local Oracle database. (y/n)? [y]
Step 3 Enter the base directory for CSCOcam installation:
CSCOcam will be installed under the directory
<base directory>/CSCOcam Enter the base directory for CSCOcam installation ? [/opt]
Continue as follows:
Step 4 For remote Oracle database installations only, enter the installed location of the Oracle software:
Please enter Oracle Home location? [$ORACLE_HOME]
where $ORACLE_HOME is the Oracle home directory.
For example: /oracle/db/product/7.3.4
The Oracle database must be installed before the CAM software can be installed. If the Oracle database is not installed, quit the installation process with Ctrl-c, and install the Oracle database before continuing.
Step 5 Enter the remote Oracle database alias. This alias must match the alias configured for the remote database in the /var/opt/oracle/tnsnames.ora file:
Remote Oracle DB alias is needed for Cisco Access Manager to connect to the database and it has to match the name setup in /var/opt/oracle/tnsnames.ora in this machine. Please enter remote Oracle DB alias?
Step 6 Enter the Oracle database username and password:
Please enter the Oracle DB user name ? [cam] Please enter the Oracle DB password ? [cam]
Step 7 Enter the tftpd root directory:
Please enter tftpd root directory ? [/opt/CSCOcam/tftpboot]
Step 8 Enter the device username (required by the AAA server):
Please enter the device username ? [CAMadmin]
Step 9 Enter the device password (registered with the AAA server):
Please enter the device password ? [cam]
Step 10 Enter the password for the CAM administrator:
Please enter the CAM admin user (CAMadmin) password ? [cam]
Step 11 A summary of your selection settings will appear. Review these settings.
The following settings will be used: CSCOcam Installation location:/opt/CSCOcam CAM Oracle Database SID (Local):CAMDB Oracle Home location:/scratch/oracle/product/7.3.4 CAM DB user name:cam CAM DB user password:cam tftpd root directory:/opt/CSCOcam/tftpboot Device login username:CAMadmin Device login password:lab CAM administrator password:cam Are these acceptable, continue install (y/n)? [y]
After reviewing the settings, enter one of the following:
Step 12 If the CSCOcam base directory does not exist, the installation script will ask if you want the directory to be created. Confirm the creation of the CSCOcam directory:
The selected base directory </opt/CSCOcam> must exist before installation is attempted. Do you want this directory created now [y,n,?,q] y
Step 13 Confirm that the package can perform scripts requiring superuser privileges:
This package contains scripts which will be executed with super-user permission during the process of installing this package. Do you want to continue with the installation of <CSCOcam> [y,n,?] y
The installation process installs the CSCOcam executables on your workstation. No additional CAM-specific intervention should be required for the package installation and configuration to complete.
During the final steps of the installation process, file ownerships and permissions will be set, and the Netscape FastTrack web server will be configured and started. The installation takes 10 to 20 minutes.
When the installation of CAM is complete, you can change Netscape FastTrack configuration items, such as the Admin password. For instructions, see the section "Backing Up the CAM Installation".
This section describes an upgrade installation from AccessPath Manager (APM) 2.0 to CAM 3.1. As with CAM initial installation, the upgrade procedure involves the installation of two packages, CSCOcam and CSCOcamdb. The upgrade preserves the device configuration data from the prior APM 2.0 installation and makes it available to the Configuration File Manager and Template File Manager in CAM 3.1.
The APM 2.0 to CAM 3.1 upgrade procedure deletes all the historical data. However, historical reports are still available after the upgrade at the following location:
/opt/CSCOcam/docs/apm20_reports
The reports are accessible from your browser at http://cam_host/cam/apm20_reports
where cam_host is the name of the host machine for your CAM system.
The APM 2.0 to CAM 3.1 upgrade procedure also migrates and stores all the custom templates at /opt/CSCOcam/apm20_templates.
Devices that utilized custom templates in APM 2.0 are modified to utilize CAM 3.1 default templates for the relevant device type. If you wish to revert to the custom template after the upgrade, go to the CAM Template Manager, import the migrated APM 2.0 custom template from the above directory, review it for accuracy, and if satisfied, apply it to the device.
When upgrading from APM 2.0, two new CAM 3.1 packages (CSCOcamdb and CSCOcam) are added to the system. An existing APM 2.0 system can be upgraded to CAM 3.1 in different ways. The different upgrade scenarios are as follows:
1. Local Upgrade---APM 2.0 system is upgraded to a CAM 3.1 system, on the existing APM 2.0 machine(s).
2. Remote Upgrade---APM 2.0 system is upgraded to a CAM 3.1 system, residing on a remote machine (a different machine than the current APM 2.0 database machine)..
3. Migrate and Merge---Multiple APM 2.0 systems are migrated and merged into one CAM 3.1 system.
This section discusses the following upgrade topics.
Upgrading APM 2.0 to CAM 3.1 first requires upgrading Solaris from 2.5.1 to 2.6 and upgrading Oracle from 7.3.3 to 7.3.4.
For the Oracle upgrade procedure, refer to /device/CSCOcamdb/reloc/README.database or "CAM Database and Upgrade Issues" in Appendix A.
The APM 2.0 system should be backed up using the script "apm_clone" prior to performing the above upgrades.
The custom templates created in APM 2.0 are converted to CAM 3.1 format and stored in a temporary location. To use them, they must be reimported with the Template Manager Import feature.
The historical data from APM 2.0 is not preserved in CAM 3.1 after the upgrade.
During the CAM upgrade, you will need to know the following information:
The CAM upgrade process also installs and runs a copy of the Netscape FastTrack Web server.
Before upgrading CSCOapm, perform the following steps:
Step 1 Mount the CD-ROM as described in the section "Mount the CD-ROM".
Step 2 Login as the root user and shut down the APM software.
# /opt/CSCOapm/admin/APM_shutdown
Step 3 Login as the Oracle user and start the Oracle database.
$ /opt/CSCOapm/oracle/admin/database_start.sh
Step 4 Backup or clone your existing installation.
Back up your APM 2.0 system using the apm_clone script as described in the "APM Backup/Clone" section.
Step 5 Upgrade Solaris 2.x to Solaris 2.6. For the Solaris upgrade procedures refer to the Solaris documentation.
Step 6 Upgrade Oracle 7.3.3 to Oracle 7.3.4. For the Oracle upgrade procedures refer to the section "Upgrade Oracle 7.3.3 to Oracle 7.3.4" of this document.
Step 1 Log in as root.
#su
Step 2 Place the CAM CD-ROM in your CD-ROM drive and mount the drive.
CD-ROM mount policies vary with different systems. In some systems, the CD-ROM is automounted or managed by the Solaris vold process. In such cases, you will have a standard mount point for the CD-ROM, such as /cdrom/cdrom0.
If your CD-ROM is not automounted, enter the following command to manually mount the CD-ROM:
# mount -F hsfs -r /dev/dsk/cddevice /cdpath
where:
The apm_clone script is used to backup an existing APM 2.0 system, including the database, reports, templates, and so on, from an existing server to a new server, then upgrading the new server to a CAM 3.1 system. To back up the APM 2.0 system follow steps 1 to 5. The tar files generated by apm_clone can be used to restore the original APM 2.0 system to a fully functional state, on any machine. For details refer to the"Recovery From Local Upgrade Failure" section.
Cloning can be done for a local or remote configuration APM 2.0 system. If the existing system uses a remote configuration, the apm_clone script should be executed as described on both machines. On the CSCOapm machine, the file apm20_files.tar is created in the user specified directory. On the CSCOapmdb machine, the file apm20_db.tar is also created in the user specified directory.
To clone an APM 2.0 system, complete the following steps:
Step 1 Log in to the APM 2.0 system as root, with the CAM 3.1 installation CD ROM already mounted:
# su
Step 2 Change directory to the location of the APM cloning script.
$ cd <path>/cdrom0
where <path> is the mounted location of the CAM 3.1 installation CD.
Step 3 Execute the apm_clone script.
$ ./apm_clone
Step 4 Enter the output directory for the archived files or accept the default.
Please Enter the absolute path of the Directory in which the tar files
(exported DB and files) should be created ? [/opt/CSCOapm]
Step 5 Confirm the settings at the prompt.
The following settings will be used for the Remote Upgrade Oracle's Home Location /data/oracle/product/7.3.3 Oracle's unix user name oracle Group name for unix user 'oracle' dba CAM DB Oracle SID APMDB CAM DB user name apm CAM DB user password apm CAM DB Data files' Location /extra/APMDB CAM DB Admin files' Location /extra/APMDB Continue with the APM DB Backup/Upgrade (y/n)? [y] y
The cloning script will then archive the relevant files to the following tar files, in the directory specified in step 4:
Step 6 After the files are archived, manually transfer the files to the destination machines. Place the tar files in the directory of your choice.
Step 7 Link the directory /opt/CSCOapm to the directory containing the tar files.
$ ln -s <tar files dir_path> /opt/CSCOapm $ cd /opt/CSCOapm
Step 8 Untar the files, using the -p option to preserve file permissions.
$ tar -xvpf /data/CSCOapm/apm20_db.tar
Step 9 Install the CSCOcamdb package and CSCOcam package normally. The APM 2.0 database and files will be detected and imported during CSCOcamdb installation, then migrated to 3.1 data during CSCOcam installation, if the upgrade is approved in the installation script. If the upgrade is not approved, the installation scripts will install a raw copy of CAM 3.1, with no preserved files or database information.
When upgrading locally, the APM 2.0 software is upgraded to CAM 3.1 on the existing APM 2.0 machine. The CAM 3.1 package installations detect existing APM 2.0 installations and upgrade accordingly, if the user chooses to do so. The package CSCOcamdb must be installed prior to installing CSCOcam. For CAM package installation details refer to the sections "Upgrade the APM 2.0 Oracle Database" and "Upgrade the APM 2.0 Executables".
APM 2.0 software can be installed in two different configurations.
In the local database case, the CAM 3.1 packages CSCOcamdb and CSCOcam must be installed on the APM 2.0 machine. In the remote database case, CSCOcamdb must be installed on the machine with CSCOapmdb 2.x installed, and CSCOcam must be installed on the machine with CSCOapm 2.x installed.
For both local and remote databases, the ORACLE_SID and the physical location of the database remain the same, even after the upgrade. Do not change or delete them manually.
The existing APM 2.0 packages (CSCOapm and CSCOapmdb) should not be removed using the APM2.0 removal procedure. This will result in removal of the upgraded CAM 3.1 database. If it is necessary to remove these packages, follow the procedure recommended in the "Postupgrade ProcedurePackage Removal" section.
This section describes how to upgrade an APM 2.0 installation that employs a local database to CAM 3.1 on the same machine.
To upgrade APM 2.0 using a local database to CAM 3.1, complete the following steps:
Step 1 Login as root and shutdown the APM server.
Su # /opt/CSCOapm/admin/APM_shutdown
Step 2 Login as Oracle user and start the APM 2.0 database
# su - oracle % /opt/CSCOapm/oracle/admin/database_start.sh
Step 3 Login as root and mount the CD-ROM.
Refer to the section "Mount the CD-ROM".
Step 4 Backup the APM 2.0 system (database, reports, custom templates, scripts, etc.) as user root.
Refer to the section "APM Backup/Clone" for details.
# cd /cdrom/cdrom0 # ./apm_clone
Step 5 Login as Oracle user and shutdown the APM database.
# su - oracle % /opt/CSCOapm/oracle/admin/database_stop.sh
Step 6 Upgrade Solaris 2.5.x to Solaris 2.6.
Refer to the Solaris upgrade documentation for the procedure(s).
Step 7 Upgrade Oracle 7.3.3 to Oracle 7.3.4.
Refer Oracle product documentation, and Appendix A of this document.
Step 8 Login as root and mount the CD-ROM.
Refer to the section "Mount the CD-ROM".
Step 9 Log in as root and shutdown the APM server.
% su # /opt/CSCOapm/admin/APM_shutdown
Step 10 Login as the Oracle user and start the APM database.
# su - oracle % /opt/CSCOampdb/oracle/admin/database_start.sh
Step 11 Login as root, change the directory to the location of the CAM 3.1 installation CD, and upgrade the APM 2.0 database.
% su # cd /cdrom/cdrom0 # ./camdb_pkgadd
Refer to the section "Upgrade the APM 2.0 Oracle Database" for the detailed procedure.
Step 12 Upgrade the CSCOapm executables.
# ./cam_pkgadd
Refer to the section "Upgrade the APM 2.0 Executables" for the detailed procedure.
This section describes how to upgrade an APM 2.0 installation that employs a remote database to a CAM 3.1 such that CSCOapm 2.0 is upgraded to CSCOcam 3.1 and CSCOapmdb 2.0 is upgraded to CSCOcamdb 3.1 on the corresponding APM 2.0 machines.
On the APM 2.0 machine with CSCOapmdb 2.0 installed, complete the following steps:
Step 1 Login as root and shutdown the APM Server
Su # /opt/CSCOapm/admin/APM_shutdown
Step 2 Login as the Oracle user and start the APM 2.0 database
# su - oracle % /opt/CSCOapm/oracle/admin/database_start.sh
Step 3 Log in as root and mount the CD-ROM.
Refer the section "Mount the CD-ROM".
Step 4 Backup the APM 2.0 database as user root.
# cd /cdrom/cdrom0 # ./apm_clone
Refer to the section "APM Backup/Clone" for details.
Step 5 Log in as the Oracle user and shutdown the APM database.
# su - oracle % /opt/CSCOapm/oracle/admin/database_stop.sh
Step 6 Upgrade Solaris 2.5.x to Solaris 2.6.
Refer to the Solaris upgrade documentation for detailed procedure(s).
Step 7 Upgrade Oracle 7.3.3 to Oracle 7.3.4.
Refer to the Oracle product documentation and Appendix A of this document for detailed information.
Step 8 Log in as the Oracle user and start the APM database.
# su - oracle % /opt/CSCOampdb/oracle/admin/database_start.sh
Step 9 Log in as root and mount the CD-ROM.
Refer to the section "Mount the CD-ROM".
Step 10 Upgrade the APM 2.0 database.
# cd /cdrom/cdrom0 # ./camdb_pkgadd
Refer to the section "Upgrade the APM 2.0 Oracle Database" for detailed information.
On the APM 2.0 machine with CSCOapm 2.0 installed, complete the following steps
Step 1 Log in as root and shutdown the APM Server
% Su # /opt/CSCOapm/admin/APM_shutdown
Step 2 Login as root and mount the CD-ROM.
Refer the section "Mount the CD-ROM".
Step 3 Backup the APM 2.0 database as user root.
Refer the section "APM Backup/Clone".
# cd /cdrom/cdrom0 # ./apm_clone
Step 4 Upgrade Solaris 2.5.x to Solaris 2.6.
Refer to the Solaris documentation for detailed upgrade procedure(s).
Step 5 Login as the user root and mount the CD-ROM.
Step 6 Upgrade the APM 2.0 database.
Refer to the section "Upgrade the APM 2.0 Oracle Database" for detailed information.
# cd /cdrom/cdrom0 # ./cam_pkgadd
To upgrade the APM 2.0 Oracle database, complete the following steps:
Step 1 Run the camdb_pkgadd script to create the CSCOcamdb database:
# cd /device # ./camdb_pkgadd
where device is the device name of the CD-ROM drive.
The script allows you to install CAM in a location other than the default location (/opt/CSCOcamdb). A symbolic link (/opt/CSCOcamdb) to the actual location will be created automatically.
For example:
# cd /cdrom/cdrom0 # ./camdb_pkgadd
You can terminate the script by typing Ctrl-c.
Step 2 The script will detect the presence of APM 2.0 and asks that you confirm that you want to continue with the upgrade.
CSCOapm 2.0 (0.20) is installed on this machine Do you want to upgrade this package to CAM (y/n)? [y] y
Step 3 The script prompts you for the base directory for your CSCOcamdb installation.
Enter the Base Directory for CSCOcamdb Installation ? [/opt]
A symbolic link from /opt/CSCOcamdb to basedir/CSCOcamdb will be created.
Step 4 The script prompts you for a password.
Please enter user `system' s password: ? [manager]
Step 5 The script prompts you for the location of your Oracle software:
Please enter Oracle's Home Location: ? [/extra/oracle/product/7.3.4]
Step 6 A summary of your selection settings will appear.
The following settings will be used for the upgrade: CSCOcamdb Installation Location: /extra/CSCOcamdb Oracle's Home Location: /extra/oracle/product/7.3.4 Oracle's unix user name: oracle Group name for unix user 'oracle' : dba Password for oracle user 'system': manager CAM DB Oracle SID: APMDB CAM DB user name: apm CAM DB user password: apm CAM DB Data files' Location: /extra/oracle/product/7.3.3/dbs/APMDB CAM DB Admin files' Location: /extra/oracle/product/7.3.3/dbs/APMDB Are these acceptable? Proceed with the CAM upgrade (y/n)? [y] y
Review these settings and enter one of the following:
Step 7 If the CSCOcamdb package base directory does not already exist, the installation script will ask if you want the directory to be created:
The selected base directory </extra/CSCOcamdb> must exist before installation is attempted. Do you want this directory created now [y,n,?,q] y Using <opt/CSCOcamdb> as the package base directory.
Confirm the creation of the CSCOcamdb base directory by entering y (press Enter).
If you do not confirm the directory creation, the installation script will terminate.
Step 8 Confirm that the package can perform scripts requiring superuser privileges:
This package contains scripts which will be executed with super-user permission during the process of installing this package. Do you want to continue with the installation of <CSCOcamdb> [y,n,?] y
The installation process now installs the CSCOcamdb database on your workstation. When the upgrade is complete, the script will notify you with the message:
Installation of <CSCOcamdb> was successful.
To upgrade the APM 2.0 executables, complete the following steps:
Step 1 Run the cam_pkgadd script to upgrade the executable files:
# ./cam_pkgadd
Step 2 Select whether to use a local or remote Oracle Database:
Will Cisco Access Manager use the local Oracle database. (y/n)? [y] y
Cisco Access Manager can use either a local Oracle database or a remote Oracle database.
Step 3 Confirm that you wish to upgrade:
CSCOapm 2.0(0.20) is installed on this machine Do you want to upgrade this package to CSCOcam 3.1(0.3) (y/n)? [y]
Step 4 Enter the base directory of your new installation.
Enter the Base Directory for CSCOcam Installation ? [/opt]
A symbolic link /opt/CSCOcam to basedir/CSCOcam will be created.
Step 5 Enter the following installation settings:
Please enter tftpd root directory (full path) ? [/opt/CSCOcam/tftpboot] Please enter the device username ? [CAMadmin] Please enter the device password ? [cam] Please enter the CAM admin user (CAMadmin) password ? [cam]
Step 6 Confirm the rest of the settings:
The following settings will be used: Upgrade From APM 2.0 to CSCOcam 3.1(0.14): YES CSCOcam Installation location: /extra/CSCOcam CAM Oracle Database SID (Local): APMDB Oracle Home location: /extra/oracle/product/7.3.4 CAM DB user name: apm CAM DB user password: apm tftpd root directory: /tftpboot Device login username: CAMadmin Device login password: cam CAM administrator password: cam Are these acceptable, continue install (y/n)? [y]
Step 7 If the CSCOcam base directory does not exist, the installation script will ask if you want the directory to be created. Confirm the creation of the CSCOcam directory:
The selected base directory </extra/CSCOcam> must exist before installation is attempted. Do you want this directory created now [y,n,?,q] y
Step 8 Confirm that the package can perform scripts requiring superuser privileges to install the CAM 3.1 files:
Do you want to continue with the installation of <CSCOcam> [y,n,?] Installing Cisco Access Manager as <CSCOcam>
The installation process now installs the CSCOcam executables on your workstation. When the upgrade is complete, the script will notify you with the message:
Installation of <CSCOcamdb> was successful.
During the final steps of the installation process, file ownerships and permissions will be set, and the Netscape FastTrack web server will be configured and started. The complete installation takes 10 to 20 minutes. When the installation of CAM is complete, you can change Netscape FastTrack configuration items, such as the administrator's password. For instructions, see the "Changing Netscape FastTrack Admin Server Port, User ID, and Password" section.
To restore the APM 2.0 database, and upgrade the APM 2.0 system to a CAM 3.1 system, complete steps 1 through 6. To restore the APM 2.0 database, and revert to the APM 2.0 system, complete steps 1 through 5 and steps 7 through 9.
Step 1 Backup the environment file and the package parameters.
# cp -p /opt/CSCOapm/www/cgi-bin/env apm20_env.bak # pkgparam -v CSCOapm > ap20_params.bak
Step 2 Remove the CAM 3.1 packages that were installed during the upgrade. For details refer to the "Postupgrade ProcedurePackage Removal" section.
Step 3 Remove the APM 2.0 packages that were originally installed. For details refer to the APM 2.0 installation document.
Step 4 Make sure that no Oracle processes for the APM 2.0 ORACLE_SID are running. If there are processes for this ORACLE_SID, kill them.
# ps -ef | grep ora. # kill -9 pid [ pid ]
Remove the semaphores and shared memory segments being used by the Oracle processes.
# ipcs # ipcrm -m id ( if required ) # ipcrm -s id ( if required )
Step 5 Delete the file $ORACLE_HOME/dbs/init$ORACLE_SID.ora, and the directories $ORACLE_HOME/dbs/APM_dump and $APM_DBPATH.
Step 6 Use the tar files generated by the apm_clone script, in the preupgrade step, and follow the upgrade procedure described in the "APM Backup/Clone" section.
Step 7 Install the APM 2.0 packages, as they were originally, using the information backed up in step 1. For installation instructions refer to the APM 2.0 installation document.
Step 8 Copy the tar files generated by the apm_clone script in the preupgrade step into the directory /opt/CSCOapm and untar them as follows.
# tar -xvfp apm20_files.tar # tar -xvfp apm20_db.tar
Step 9 Import the database with the following commands
# su - oracle (log on as user oracle) $ . /opt/CSCOapm/www/cgi-bin/env (source env file) $ sqlplus $APM_DBUSER/$APM_DBPASSWORD SQL> @/opt/CSCOapm/oracle/devsql/drop_all.sql; SQL> exit; $ imp $APM_DBUSER / $APM_DBPASSWORD PARFILE=/opt/CSCOapm/importAPMDB.par
Before you attempt to remove the CSCOapm package files, save the backup tar files generated by the apm_clone script (and any other files you wish to retain) to another location.
To remove the APM 2.0 packages do the following procedure:
Step 1 Make sure the file $APMHOME/Uiroutines exists and is readable.
Step 2 Make sure the file $APMHOME/www/cgi-bin/env exists and is readable.
Step 3 Edit $APMHOME/www/cgi-bin/env to set the variable APM_REMOTEDB to "yes."
APM_REMOTEDB=yes export APM_REMOTEDB
Ensure that the permissions of the file are unchanged.
Step 4 Execute the package remove command as root.
# pkgrm CSCOapm
Step 5 Execute /tmp/CSCOapm_remove as root.
# /tmp/CSCOapm_remove
To remove CSCOapmdb:
Step 1 Backup the oratab file.
# cp -p /var/opt/oracle/oratab /var/opt/oracle/oratab.bak
Step 2 As root, run the package remove command.
# pkgrm CSCOapmdb
Do not execute /tmp/CSCOapmdb_remove script. Ignore the message from the pkgrm script.
Step 3 Remove the /tmp/CSCOapmdb_remove script.
# rm /tmp/CSCOapmdb_remove
Step 4 Restore the oratab file. Make sure the original owner, group, and permissions are retained.
# cp -p /var/opt/oracle/oratab.bak /var/opt/oracle/oratab
Step 5 Start the oracle database using the CAM 3.1 script.
# su - oracle $ ./opt/CSCOcamdb/Apm.sh $ /opt/CSCOcamdb/db/admin/database_start.sh
APM 2.0 installations can be upgraded to CAM 3.1 on remote machines, over the network, using the Oracle Distributed Database and remote database access (SQL*NET) features. This procedure does not affect the existing APM 2.0 system in any way. CAM 3.1 software should be installed on the target machines. The remote database connectivity between the APM 2.0 server machine and the CAM 3.1 database machine should be established. Then the script migrate_merge should be executed on the APM 2.0 server machine. This script migrates and merges the APM 2.0 database into the CAM 3.1 database, and also creates an archive (apm20.tar) of APM 2.0 reports and custom templates. The script merge_apmfiles should be executed on the CAM 3.1 server machine, after transferring the apm20.tar file onto it. For details refer to the section "Migration and Merge Process".
The remote upgrade procedure requires the Oracle7 Distributed Database option on the APM 2.0 database machine.
This section describes how to upgrade APM 2.0, using either a local or a remote database, to CAM 3.1 on a new machine (a machine other than the existing APM 2.0 database machine).
To install the CAM 3.1 software on the CAM 3.1 target machine(s), complete the following steps:
Step 1 Login as root.
Step 2 Mount the CD-ROM.
Refer the section "Mount the CD-ROM".
Step 3 Change the directory to the location of the CAM 3.1 installation CD.
# cd /cdrom/cdrom0
Step 4 Install the CSCOcamdb 3.1 package.
Refer to the section "Install the CSCOcamdb Oracle Database".
# ./camdb_pkgadd
Step 5 Install the CSCOcam 3.1 package.
Refer to the section "Install the CSCOcam Executables".
# ./cam_pkgadd
On the APM 2.0 server machine (the machine containing the CSCOapm package) complete the following steps:
Step 1 Login as root.
#su
Step 2 Shutdown the APM 2.0 server software, as user root.
# /opt/CSCOapm/admin/APM_shutdown
Step 3 Login as user oracle.
# su - oracle
Step 4 Start the APM 2.0 database, as user oracle.
$ /opt/CSCOapm/oracle/admin/datatbase_start.sh
Step 5 Login as root.
#su
Step 6 To setup the database connectivity to the CAM 3.1 database, execute the following steps. For detailed information on each of these steps, refer to the corresponding steps in the section "Migration and Merge Process".
(a) Edit the init$ORACLE_SID.ora file.
(b) Add a CAM 3.1 entry to /var/opt/oracle/tnsnames.ora.
(c) Set environment variables---CAM31_DBUSER and CAM31_DBPASSWORD.
Step 7 Mount the CD-ROM on the APM 2.0 client machine (the machine that contains CSCOapm).
For more information see the section "Mount the CD-ROM".
Step 8 Change directory to the location of the CAM 3.1 installation CD.
$ cd <path>/cdrom/cdrom0
where <path>/cdrom/cdrom0 is the path to the mounted CAM 3.1 installation CD.
Step 9 Run ./migrate_merge.
For more information, refer to the section "Migration and Merge Process".
Step 10 Transfer the tar file apm20.tar to the target CAM 3.1 client machine (the machine containing CSCOcam).
On the target CAM 3.1 server machine (the machine on which you installed CSCOcam 3.1), complete the following steps:
Step 1 Login as root.
#su
Step 2 Mount the CD-ROM
Step 3 Change directory to the location of the CAM 3.1 installation CD.
$ cd <path>/cdrom/cdrom0
where <path>/cdrom/cdrom0 is the path to the mounted CAM 3.1 installation CD.
Step 4 Run ./merge_apmfiles.
For more information, refer to the next section "Migration and Merge Process."
Multiple APM 2.0 systems can be migrated and merged into one CAM 3.1 system. This process migrates and merges the APM 2.0 database, reports, and custom templates into a CAM 3.1 system. This is done in two steps by the following two scripts, as described below.
The script migrate_merge.sh migrates and merges a APM 2.0 database into an existing CAM 3.1 database on a remote/local machine. It creates an archive of the APM 2.0 reports and templates. The archive "apm20.tar" should be transferred to the machine with the target CAM 3.1 installed.
On the target machine, the script "merge_apmfiles" must be executed to upgrade and merge the APM 2.0 reports and custom templates, into the CAM 3.1 system. The script merge_apmfiles restores APM 2.0 reports into the directory /opt/CSCOcam/docs/apm20_reports/<apm20_instance_dir>, and migrates APM 2.0 custom templates into the directory /opt/CSCOcam/apm20_templates/apm20_instance_dir>/custom. If multiple APM 2.0 systems are being merged into one CAM 3.1 system, you should specify a separate directory <apm20_instance_dir> for each APM 2.0 system.
The custom template conversion process renames the templates by appending a ".txt" extension to conform with the CAM 3.1 standard. The converted templates will still be equivalent to their APM 2.0 counterparts, and only the substitution variable names will be changed to those used and understood by CAM 3.1.
This procedure does not affect the data on the APM 2.0 system at all. It is safe to run it against a production APM 2.0 system. However, because the data will be copied into the CAM 3.1 database, we recommend backup of the CAM 3.1 database before performing the merge. This is particularly important if the CAM 3.1 database already contains data that you do not want to jeopardize. After you complete the merge, and if it results in failure, you should restore the CAM 3.1 database to the original state, troubleshoot the merge problem, and try the process again.
For the distributed database option, the merge procedure requires the Oracle7 Distributed Database option on the source database machine (your APM 2.0 system in this case). To check if this option is installed on your machine run the following command as the Oracle user:
# $ORACLE_HOME/orainst/inspdver
This will list all the options installed on your database server. Look for a line that says "Oracle7 Distributed Database option." If the system does not show this option, then you must install it before running the merge.
Perform all these steps on the APM 2.0 system as the Oracle user (unless noted otherwise).
Step 1 Install CAM 3.1 on the target machine. For details see the "Software Installation" section.
Step 2 Shut down APM 2.0.
While this is not absolutely necessary for the migration/merge process to work, we recommend you do so. You have to run the APM 2.0 shutdown procedure as the root user.
Step 3 Edit the init$ORACLE_SID.ora file (for example, initAPMDB.ora) and restart the database.
The GLOBAL_NAMES parameter in the APM 2.0 database's init$ORACLE_SID.ora file has to be set to FALSE. Edit the file and either change the setting to FALSE if the global_names parameter is already there, or add the following line to the end of the file:
global_names = FALSE
After you modify the init$ORACLE_SID.ora file, shutdown and restart the database for the change to take effect.
Step 4 Add a CAM 3.1 entry to /var/opt/oracle/tnsnames.ora.
cam31 = # DO NOT CHANGE THIS !!!
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS =
(PROTOCOL = TCP)
(Host = <hostname>) # CHANGE THIS !!!
(Port = 1521)
)
)
(CONNECT_DATA =
(SID = CAMDB) # MAYBE CHANGE THIS
(GLOBAL_NAME = <hostname>) # CHANGE THIS !!!
)
)
The lines marked "CHANGE THIS" have to be modified to reflect your environment. Change hostname to the fully qualified host name on which the CAM 3.1 database resides. The "CAMDB" SID is the default name of the CAM 3.1 database. If your CAM 3.1 SID name is different, then you must also change this line.
Verify cam31 database connectivity by invoking sqlplus using the correct userid and password as follows (cam/cam is the default userid/password):
> sqlplus cam/cam@cam31
If you are unable to connect, then verify that the listener Oracle process is running on the CAM 3.1 database machine. If the listener is running, yet the connection is failing, then you must edit the /var/opt/oracle/listener.ora file to add the appropriate entry to accept remote connections to the CAM 3.1 database. You must resolve the database connectivity problem before you proceed. For detailed information, refer to the "Remote Database Considerations" section in Appendix A and your database administrator.
Step 5 Set environment variables.
You must provide the CAM 3.1 database login userid and password. Go to the directory in which you have the migration/merge script. Set the following environment variables using the appropriate syntax for your UNIX shell (sh,bsh, ksh, csh, etc.):
CAM31_DBUSER=cam CAM31_DBPASSWORD=cam
Note that the defaults for CAM 3.1 are both "cam." If you selected something different when you installed CAM 3.1, then set the environment variables accordingly.
Step 6 Run the migrate/merge command as root.
You are ready to run the migration/merge process. Invoke the master script as follows:
./migrate_merge <group_name>
The <group_name> is an optional parameter that can be used to specify a new group name under which all the APM 2.0 stacks will be created on your CAM 3.1 system. If the group_name parameter is not provided, then all the APM 2.0 stacks will be created under the topmost CAMROOT group.
Specifying a group name is strongly recommended as it provides a convenient logical separation among stacks merged from multiple APM 2.0 systems. This grouping is MANDATORY if there are naming conflicts among stacks coming from different APM 2.0 systems.
For example, to merge all the APM 2.0 data into CAM 3.1 and store all the stacks under a new group called "san_jose," you would invoke the script as follows:
> ./migrate_merge san_jose
Step 7 Check for errors.
As the migrate_merge.sh script executes you will see progress messages on the screen. The last message will indicate whether the process was successful or not. You will notice that two logs are created in the current directory:
/tmp/migrate_merge.log /tmp/CAM_migrate.log
The migrate_merge.log file contains all the messages produced by the master script. Examine it for errors and warnings (there should not be any if success was reported).
The CAM_migrate.log file is a detailed log of the data conversion process. It is very useful for troubleshooting problems. You might want to check if it has any entries with strings "ERR"or "WARN" (using vi or grep tools).
Step 8 Transfer the file "apm20.tar" to the CAM 3.1 machine and execute merge_apmfiles as root
# ./merge_apmfiles
The log file /opt/CSCOcam/logfiles/install/merge_apmfiles is created.
Step 9 Verify CAM 3.1.
If you got this far, then you are ready to access the merged data on your CAM 3.1 system. Start your browser and login to CAM 3.1 (If your browser is already logged in to the CAM 3.1 system, then logoff, and login again.)
The tree view should show the new group (if you specified one at the time of the merge) and all the APM 2.0 stacks and devices.
This section describes the upgrade installation from CAM 3.0 to CAM 3.1. The installation software will detect existing installations of CAM 3.0, and upgrade accordingly. As with an initial CAM 3.1 installation, the upgrade procedure involves the installation of two packages, CSCOcam and CSCOcamdb. CSCOcamdb 3.1 should be installed on the machine with CSCOcamdb 3.0 installed. CSCOcam 3.1 should be installed on the machine with CSCOcam 3.0 installed. CSCOcamdb 3.1 must be installed prior to installing CSCOcam 3.1.
The ORACLE_SID and the physical location of the database will remain the same, even after the upgrade. Do not change or delete them manually.
When upgrading from CAM 3.0, no new packages are added. The existing packages (CSCOcam 3.0 and CSCOcamdb 3.0) are updated with new or modified files, and the database is migrated to a new schema without a loss of essential data. New data (device types, templates, and so on) is also added to the database. The physical location of all package and database files is unaltered.
No Oracle or Solaris upgrades are needed to upgrade from CAM 3.0 to CAM 3.1.
As with a clean installation, a CAM upgrade installation involves two packages:
CAM can be set up in one of two ways:
The CAM database instance can serve only one CAM system, either locally or remotely.
To upgrade CAM 3.0 software, you must complete the following tasks in the order shown:
During the CAM 3.0 upgrade, you will need to know the following information:
The CAM upgrade process will also install and run a copy of the Netscape FastTrack Web server. Before upgrading CAM 3.0, perform the following tasks:
Step 1 Obtain CAM 3.0 package installation parameters. These parameters must be reused during CAM 3.1 installations.
# pkgparam -v CSCOcam > cam30.env # pkgparam -v CSCOcamdb > camdb30.env
Step 2 Login as the root user and shut down the CAM 3.0 software, it it is not already shutdown.
# su # /opt/CSCOcam/admin/CAM_shutdown
# tar -cvfp cam30.tar /opt/CSCOcam
Step 4 Login as the Oracle user and stop the Oracle database, if it is not already stopped.
# su - oracle % sh $ . /opt/CSCOcamdb/Apm.sh % /opt/CSCOcamdb/oracle/admin/database_stop.sh
Step 5 Back up the CAM database files. As the Oracle user, enter the following:
% tar -cvfp camdb_pkg.tar /opt/CSCOcamdb % tar -cvfp cam30_db.tar $ORACLE_HOME/dbs/init$ORACLE_SID.ora \ $ORACLE_BASE/oradata $ORACLE_BASE admin
Be sure to back up both the CAM file system and the Oracle database files.
Step 6 Start the database. As the Oracle user, enter the following
% sh $ . /opt/CSCOcamdb/Apm.sh $ cd /opt/CSCOcamdb/db/admin $ database_start.sh
Step 7 If upgrading from CAM 3.0 system with 1K port size database, extend the tablespaces.
$ sqlplus $APM_DBUSER/$APM_DBPASSWORD SQL> ALTER DATABASE DATAFILE '$APM_DBDATA/apm_data01.dbf' RESIZE 950M; SQL> ALTER DATABASE DATAFILE '$APM_DBDATA/apm_index01.dbf' RESIZE 400M; SQL> quit;
To mount the CD-ROM, complete the following steps:
Step 1 Log in as root.
Step 2 Place the CAM 3.1 CD-ROM in your CD-ROM drive and mount the drive.
CD-ROM mount policies vary with different systems. In some systems, the CD-ROM is automounted or managed by the Solaris vold process. In such cases, you will have a standard mount point for the CD-ROM, such as /cdrom/cdrom0.
If your CD-ROM is not automounted, enter the following command to manually mount the CD-ROM:
# mount -F hsfs -r /dev/dsk/cddevice /cdpath
where:
When upgrading locally, the CAM 3.0 software is upgraded to CAM 3.1 on the existing CAM 3.0 machine. The CAM 3.1 package installations detect existing CAM 3.0 installations and upgrade accordingly, if the user chooses to do so. The package CSCOcamdb must be installed prior to installing CSCOcam. For CAM package installation details refer to the sections "Upgrade the CSCOcamdb Oracle Database" and "Upgrade the CSCOcam Executables".
CAM 3.0 software can be installed in two different configurations.
In the local database case, the CAM 3.1 packages CSCOcamdb and CSCOcam must be installed on the CAM 3.0 machine.
In the remote database case, CSCOcamdb 3.1 must be installed on the machine with CSCOcamdb 3.0 installed, and CSCOcam 3.1 must be installed on the machine with CSCOcam 3.0 installed.
For both local and remote databases, the ORACLE_SID and the physical location of the database remain the same, even after the upgrade. Do not change or delete them manually.
The existing CAM 3.0 packages (CSCOcam and CSCOcamdb) are updated to CAM 3.1 packages. Therefore, the packages CSCOcam and CSCOcamdb should not be removed using the CAM3.0 removal procedure. This will result in removal of the upgraded CAM 3.1 database and packages.
To upgrade a CAM 3.0 installation with a local database to CAM 3.1, on the CAM 3.0 server complete the following steps:
Step 1 Backup the CAM 3.0 software, if you have not already done so.
Refer to the "Preupgrade Tasks" section for the backup procedure.
Step 2 Login as root.
# su
Step 3 Shutdown the CAM server software (if it is not already shutdown).
# /opt/CSCOcam/admin/CAM_shutdown
Step 4 Login as Oracle user.
# su - oracle
Step 5 Start the CAM 3.0 database, as Oracle user (if it is not already running).
% sh $ /opt/CSCOcamdb/db/admin/database_start.sh
Step 6 Extend the tablespaces if upgrading from a CAM 3.0 1K ports size database.
$ . /opt/CSCOcamdb/Apm.sh $ sqlplus $APM_DBUSER/$APM_DBPASSWORD SQL> ALTER DATABASE DATAFILE '$APM_DBDATA/apm_data01.dbf' RESIZE 950M; SQL> ALTER DATABASE DATAFILE '$APM_DBDATA/apm_index01.dbf' RESIZE 400M; SQL> quit;
Step 7 Login as root again.
su
Step 8 Mount the CD-ROM.
Refer to the section "Mount the CD-ROM" for the detailed procedure, if necessary.
Step 9 Change the directory to the CD-ROM drive.
# cd /cdrom/cdrom0
Step 10 Install the CSCOcamdb 3.1 package.
# ./camdb_pkgadd
Refer to the section "Upgrade the CSCOcamdb Oracle Database" for the detailed upgrade procedure, if necessary.
Step 11 Set the GMT offset system property as Oracle user.
(a) Login as Oracle user and connect to the CAM 3.1 database.
# su - oracle % setenv ORACLE_SID <cam30_sid> % sqlplus cam/cam
(b) Set the GMT offset. Enter the following lines exactly as shown.
SQL> insert into apm_sys_property values ('ApmGmtOffset', 99, 1);
SQL> commit;
SQL> quit;
% cd /opt/CSCOcamdb/db/schema
% ./gmt_offset.sh
Step 12 Login as root again.
# su
Step 13 Change the directory to the CD-ROM drive.
# cd /cdrom/cdrom0
Step 14 Install the CSCOcam 3.1 package.
# ./cam_pkgadd
Refer to the section "Upgrade the CSCOcam Executables" for the detailed upgrade procedure, if necessary.
To upgrade a CAM 3.0 installation with a remote database to CAM 3.1, on the CAM 3.0 database server (the machine with the CSCOcamdb 3.0 database installed) complete the following steps:
Step 1 Backup the CSCOcamdb 3.0 software, if you have not already done so.
Refer to the "Preupgrade Tasks" section for the backup procedure.
Step 2 Login as Oracle user.
su - oracle
Step 3 Start the CAM 3.0 database, as Oracle user (if it is not already running ).
% sh $ /opt/CSCOcamdb/db/admin/database_start.sh
Step 4 Extend the tablespaces if upgrading from a CAM 3.0 1K ports size database.
$ . /opt/CSCOcamdb/Apm.sh $ sqlplus $APM_DBUSER/$APM_DBPASSWORD SQL> ALTER DATABASE DATAFILE '$APM_DBDATA/apm_data01.dbf' RESIZE 950M; SQL> ALTER DATABASE DATAFILE '$APM_DBDATA/apm_index01.dbf' RESIZE 400M; SQL> quit;
Step 5 Login as root.
su
Step 6 Mount the CD-ROM.
Refer to the section "Mount the CD-ROM" for the detailed procedure, if necessary.
Step 7 Change the directory to the CD-ROM drive.
# cd /cdrom/cdrom0
Step 8 Install the CSCOcamdb 3.1 package.
# ./camdb_pkgadd
Refer to the section "Upgrade the CSCOcamdb Oracle Database" for the detailed upgrade procedure, if necessary.
Step 9 Set the GMT offset system property as user oracle
(a) Login as user oracle and connect to the CAM database
# su - oracle % setenv ORACLE_SID <cam30_sid> % sqlplus cam/cam
(b) Set GMT offset
SQL> insert into apm_sys_property values ('ApmGmtOffset', 99, 1);
SQL> commit;
SQL> quit;
% cd /opt/CSCOcamdb/db/schema
% ./gmt_offset.sh
On the CAM 3.0 Server (the machine with the CSCOcam 3.0 software installed) complete the following steps:
Step 1 Backup the CAM 3.0 software, if you have not already done so.
Refer to the "Preupgrade Tasks" section for the backup procedure.
Step 2 Login as root.
# su
Step 3 Shutdown the CAM server software.
# /opt/CSCOcam/admin/CAM_shutdown
Step 4 Mount the CD-ROM.
Refer to the section "Mount the CD-ROM" for the detailed procedure.
Step 5 Change the directory to the CD-ROM drive.
# cd /cdrom/cdrom0
Step 6 Install the CSCOcam 3.1 package.
# ./cam_pkgadd
Refer to the section "Upgrade the CSCOcam Executables" for the detailed upgrade procedure, if necessary.
If you will be installing the CSCOcamdb database on the same machine as the CSCOcam executables, Cisco recommends that you run camdb_pkgadd first, then cam_pkgadd.
Step 1 Run the camdb_pkgadd script to create the CSCOcamdb database:
# cd /<device> # ./camdb_pkgadd
where device is the device name of the CD-ROM drive.
The script will allow you to install CAM in a location other than the default location (/opt/CSCOcamdb). A symbolic link (/opt/CSCOcamdb) to the actual location will be created automatically.
For example:
# cd /cdrom/cdrom0 # ./camdb_pkgadd
You can terminate the script by typing Ctrl-c.
Step 2 The script detects the presence of CAM 3.0, and asks you to confirm that you want to continue with the upgrade.
CSCOcam 3.0 (0.10) is installed on this machine Do you want to upgrade this package to CAM (y/n)? [y] y
Step 3 The script prompts you for the base directory for your CSCOcamdb installation.
Enter the Base Directory for CSCOcamdb Installation ? [/opt]
A symbolic link from /opt/CSCOcamdb to basedir/CSCOcamdb will be created.
Step 4 A summary of your selection settings will appear.
The following settings will be used for the upgrade: CSCOcamdb Installation Location: /extra/CSCOcamdb Oracle's Home Location: /extra/oracle/product/7.3.4 Oracle's unix user name: oracle Group name for unix user 'oracle' : dba Password for oracle user 'system': manager CAM DB Oracle SID: CAMDB CAM DB user name: cam CAM DB user password: cam CAM DB Data files' Location: /extra/oradata/CAMDB CAM DB Admin files' Location: /extra/admin/CAMDB Are these acceptable? Proceed with the CAM upgrade (y/n)? [y] y
Review these settings and enter one of the following:
Step 5 Confirm that the package can perform scripts requiring superuser privileges:
This package contains scripts which will be executed with super-user permission during the process of installing this package. Do you want to continue with the installation of <CSCOcamdb> [y,n,?] y
The installation process now installs the CSCOcamdb database on your workstation. When the upgrade is complete, the script will notify you with the message:
Installation of <CSCOcamdb> was successful.
Step 1 Run the cam_pkgadd script to upgrade the executable files:
# ./cam_pkgadd
Step 2 Select whether to use a local or remote Oracle Database:
Will Cisco Access Manager use the local Oracle database. (y/n)? [y] y
Cisco Access Manager can use either a local Oracle database or a remote Oracle database. Answer y if Cisco Access Manager uses a local Oracle database, or n if Cisco Access Manager uses a remote Oracle database.
Step 3 Confirm that you wish to upgrade:
CSCOcam 3.0(0.10) is installed on this machine Do you want to upgrade this package to CSCOcam 3.1(0.3) (y/n)? [y]
Step 4 Enter the base directory of your new installation.
Enter the Base Directory for CSCOcam Installation ? [/opt]
A symbolic link /opt/CSCOcam to basedir/CSCOcam will be created.
Step 5 Confirm the rest of the settings:
The following settings will be used: Upgrade From CAM 3.0 to CSCOcam 3.1(0.14): YES CSCOcam Installation location: /extra/CSCOcam CAM Oracle Database SID (Local): CAMDB Oracle Home location: /extra/oracle/product/7.3.4 CAM DB user name: cam CAM DB user password: cam tftpd root directory: /tftpboot Device login username: CAMadmin Device login password: cam CAM administrator password: cam Are these acceptable, continue install (y/n)? [y]
Step 6 Confirm that the package can perform scripts requiring superuser privileges to install the CAM 3.1 files:
Do you want to continue with the installation of <CSCOcam> [y,n,?] Installing Cisco Access Manager as <CSCOcam>
The installation process now installs the CSCOcam executables on your workstation.
No additional CAM-specific intervention is required for the package installation and configuration to complete. When the upgrade is complete, the script will notify you with the message:
Installation of <CSCOcam> was successful.
During the final steps of the installation process, file ownerships and permissions will be set, and the Netscape FastTrack web server will be configured and started. The installation takes 10 to 20 minutes. When the installation of CAM is complete, you can change Netscape FastTrack configuration items, such as the administrator's password. For instructions, see the "Configure the Netscape FastTrack Server and Install Additional Instances of Netscape Navigator (Optional)" section.
To restore the CAM 3.0 database, and upgrade to CAM 3.1 system, do steps 1 to 5.
Step 1 As user "oracle" shutdown the database.
# su - oracle % sh $ . /opt/CSCOcamdb/Apm.sh $ cd /opt/CSCOcamdb/db/admin $ database_stop.sh
Step 2 Login as root.
Step 3 Remove the database directories and backup the init$ORACLE_SID.ora file.
# sh # . /opt/CSCOcamdb/Apm.sh # rm -rf $ORACLE_BASE/admin/* # rm -rf $ORACLE_BASE/oradata/* # cp -p $ORACLE_HOME/dbs/init$ORACLE_SID.ora \ $ORACLE_HOME/dbs/init$ORACLE_SID.ora.bak
Step 4 Restore the database directories $ORACLE_BASE/admin and $ORACLE_BASE/oradata, which were backed up in the preupgrade step.
Make sure the ownership and permissions of the files are retained.
# tar -xvfp <path>/cam30_db.tar
Step 5 Start the database.
# su - oracle % sh $ . /opt/CSCOcamdb/Apm.sh $ cd /opt/CSCOcamdb/db/admin $ database_start.sh
If upgrading from CAM 3.0 1K port size database, extend the tablespaces.
$ sqlplus $APM_DBUSER/$APM_DBPASSWORD SQL> ALTER DATABASE DATAFILE '$APM_DBDATA/apm_data01.dbf' RESIZE 950M; SQL> ALTER DATABASE DATAFILE '$APM_DBDATA/apm_index01.dbf' RESIZE 400M; SQL> quit;
Step 6 Run the database migration script as root.
$ su # cd /opt/CSCOcamdb/db/schema # ./cam30_to_cam31.sh > /opt/CSCOcamdb/logfiles/install/cam30_to_cam31.log 2>&1
To remove the CAM software:
1. "Remove CSCOcam Executables"
2. "Remove Any Additional CAM Database Instances"
3. "Remove the CSCOcamdb Files and the Primary Database Instance"
To remove the CSCOcam package:
Step 1 As root, enter the following to remove the CAM product package:
# cd /device # ./cam_pkgrm
where device is the device name of the CD-ROM drive.
For example:
# cd /cdrom/cdrom0 # ./cam_pkgrm
The cam_pkgrm command automatically does the following:
Step 2 If you are sure you want to remove the CSCOcam package, enter y:
Do you want to remove this package? y
Step 3 You will be reminded that this uninstallation will execute scripts with superuser permissions. If you still want to remove CAM, enter y:
This package contains scripts which will be executed with super-user permission during the process of removing this package. Do you want to continue with the removal of this package [y,n,?,q] y
Step 1 Log in as the Oracle user:
# su - oracle %
Step 2 Change to the /opt/CSCOcamdb/db/admin directory:
% cd /opt/CSCOcamdb/db/admin
Step 3 Run the remove_dbinstance.sh script:
% ./remove_dbinstance.sh
Step 4 Enter the name of the Oracle instance you want to remove:
Please enter the ORACLE_SID which you want to take action: MYDB
Step 5 Enter the Oracle base directory for the instance you want to remove, or press Enter to accept the default in square brackets [ ]:
Please enter the ORACLE_BASE for MYDB:[/oracle/db]
Step 6 Confirm that you want to remove this database instance:
Database MYDB about to be removed from server. Enter 'y' to continue or 'n' to abort removal (default n) y
Step 1 As root, enter the following to remove the CAM product package:
# cd /device # ./camdb_pkgrm
where device is the device name of the CD-ROM drive.
For example:
# cd /cdrom/cdrom0 # ./camdb_pkgrm
Step 2 If you are sure you want to remove the CSCOcam package, enter y:
Do you want to remove this package? y
Step 3 You will be reminded that this uninstallation will execute scripts with superuser permissions. If you still want to remove CAM, enter y:
This package contains scripts which will be executed with super-user permission during the process of removing this package. Do you want to continue with the removal of this package? [y,n,?,q] y
Step 4 After removing the CAM database files, the primary CAM database instance will remain. To remove these files, as the root user, enter the following:
# /tmp/camdb_remove.sh
This completes the procedure for removing CAM. If you need additional documentation, see the "Related and Referenced Documentation" section.
Normal CAM interaction requires only a Java-enabled web browser. However, to customize the Netscape FastTrack Server, you will need a Javascript-enabled browser. CAM includes the Netscape Navigator for Solaris browser that has both Java and Javascript capabilities enabled.
The following are key file locations used by Netscape FastTrack Server software:
| Software | Directory Location |
|---|---|
CAM | /opt/CSCOcam |
Netscape FastTrack web server | /opt/CSCOcam/ns-home |
Netscape Navigator installation executables: ---UNIX ---Windows 95 or Windows NT |
/opt/CSCOcam/navigator-v405/netscape /opt/CSCOcam/win/cp32e405.exe |
Netscape FastTrack Server software includes two servers that are important for CAM:
By default, both of these servers are started during installation and the workstation boot procedure.
By default, only the CAM server will be allowed to access the Netscape FastTrack Admin Server. For information on allowing other hosts access to the Netscape FastTrack Admin Server, see the Netscape online documentation on editing the ns-admin.conf file.
For example, if your CAM machine name is cam_server_name, you would use the following URLs for access:
http://cam_server_name/cam
http://cam_server_name:8887
Using the Netscape FastTrack Admin Server, several web security measures can be used. The following are recommended for CAM web security:
The procedure for making these changes is described in the following section.
To change the CAM default settings for the Netscape FastTrack Admin Server:
Step 1 Open http://cam_server_name:8887 with a Javascript-enabled browser, where cam_server_name is the name of your CAM server. Enter a user ID of admin and a password of CAM in the password dialog box.
Step 2 Click Configure Administration.
Step 3 Select Daemon Configuration.
Step 4 Change the Netscape FastTrack Admin Server port from 8887 to an unused port number of your choice. Click OK.
Step 5 Select Enter to Administrative Configuration.
Step 6 Select Access Control.
Step 7 Change the authentication username and password. Click OK.
Step 8 Click Shut it down. Click OK in the Authorization Failed Retry dialog box.
Step 9 Enter your new username and password in the Authentication dialog box.
Step 10 Click Shutdown the Administrative Server.
Step 11 Restart the Netscape FastTrack Admin Server. As root, enter the following:
# /opt/CSCOcam/ns-home/start-admin
This completes the procedure for editing the CAM default settings for the Netscape FastTrack Admin Server.
The following changes are needed in Chapter 4, "Configuring Containers."
Replace Table 4-1 on page 4-8 with the following:
| Stack Type | Access Server | Cisco 7206s | Primary Switch | Failover Switch | Controller |
|---|---|---|---|---|---|
AccessPath TS | 1-14 Cisco AS5200s | 2 | 1 x 5000 | None | Cisco 2611 |
1-7 Cisco AS5300s | 1 | 1 x Eclipse | 1 x Eclipse | Cisco 3640 | |
1-11 Cisco AS5300s | 1 | 1 x 5002 | 1 x Eclipse | Cisco 3640 | |
1-14 Cisco AS5300s | 2 | 1 x 5002 | 2 x Eclipse | Cisco 3640 | |
15-21 Cisco AS5300s | 2 | 1 x 5002 | 2 x Eclipse | Cisco 3640 | |
1-4 Cisco AS5300s | None | None | None | Cisco 3640 |
Replace the section beginning on page 4-11, titled "Configure Stack General Information," with the following:
The first dialog box that appears allows you to configure general information about the stack. (See Figure 4-1.)
To configure general information about the stack:
| Step | Description | |||
|---|---|---|---|---|
| Enter a stack name. | The case-sensitive stack group authentication name. It must be unique in the rack. | ||
| (Optional.) Enter a stack description. | Description cannot exceed 64 characters. | ||
| Select the number of Cisco 7206 routers in the stack. | Defines the maximum number of Cisco 7206 routers. For all stack types that use a Catalyst 5000 series Switch Shelf, the maximum is 2. (See "Supported Cisco AccessPath Stack Types" section for details.) | ||
| Select the number of network access servers (NAS) in the stack. | Defines the maximum number of Access Server Shelves in the stack. The number of Access Server Shelves depends on your configuration. (See the"Supported Cisco AccessPath Stack Types" section for details.) | ||
| Select the type of NAS in the stack. | You may choose the Cisco AS5200 or AS5300 access servers. If you choose Cisco AS5200, options relating to other devices in the stack change slightly or may not be available, as appropriate for your stack type. | ||
| Select yes if your stack has a Catalyst switch, otherwise select no. | The Catalyst 5002 switch is optional depending on your configuration. (See the "Supported Cisco AccessPath Stack Types" section for details.) | ||
| Select now or later for Config the Stack. (Modify only.) | If you are modifying a stack, you can choose whether to configure the stack now or later. If you choose later, then you need to schedule the download. (See the "Scheduling a Stack Download" section for information.) | ||
| Enter the EIGRP system number. | The Enhanced Interior Gateway Routing Protocol (EIGRP) Autonomous system number must be a value from 1 to 65535. | ||
| Enter a Cisco IOS secret password. | The Cisco IOS software secret password is encrypted so that it cannot be read when crossing a network. After you issue this command, the encryption cannot be reversed. The encrypted version of the password appears in output of the show running-config and show startup-config commands. The password cannot exceed 25 characters. You must enter the same password in the Confirm field. | ||
| Enter an SGBP password. | The Stack Group Bidding Protocol (SGBP) password establishes a username-based authentication system; the stack password is used to access the name argument. The password cannot exceed 25 characters.You must enter the same password in the Confirm field. | ||
| Click next. | Proceed to the "Configure Stack Trunk and Name Server Information" section. | ||
Replace the information on page 4-22 with the following:
The fourth dialog box that appears allows the user to configure stack addressing information. (See Figure 3)
CAM 3.1 requests two /26 subnet IP addresses and automatically assigns management network addresses and the Net-1 addresses of all devices in a stack. The starting and ending addresses of the IP pool range on every Cisco AS5300 access server in a stack will come from user input through the device configuration (creation/modification) GUI.
All the address and net mask fields displayed in the GUI can be modified, allowing efficient use of the IP addresses. The IP Summary address and netmask fields are available for stacks that use Cisco AS5300s, but not for stacks that use Cisco AS5300. The information for these fields is not automatically generated, and must be added manually.
Replace the text on page 4-23 with the following:
To configure stack addressing information:
| Step | Description | |||
|---|---|---|---|---|
| Enter the first 3 octets of the /26 data network. | In this field, enter the first 3 octets of the network address for the first class C network. CAM uses this information to create IP addresses for the ports in your Cisco AccessPath system. | ||
| Enter the 4th octet. | Select the 4th octet of the starting class C data network address. This affects the address map that applies to your configuration. | ||
| Enter the first 3 octets of your management network. | In addition to your data network, you need a management network. This network is a /26 network for Cisco AccessPath system stacks. | ||
| Enter the 4th octet. | Select the 4th octet of the starting class C network address. This affects the address map that applies to your configuration. This value applies only to the /26 management network. | ||
| (Optional) Select a shelf type to show address assignment for the shelves in the stack. | Use this pull-down menu to select the shelves for which you want to see the planned IP addressing. Select from the following: | ||
| Click next. | Proceed to the "Configure Stack Network Management" section. | ||
The following changes should be made to Chapter 5, Configuring Shelves.
Add the following note at the bottom of page 5-3, in the section titled "Modifying a Shelf in a Stack:"
The following section replaces the information on page 5-4 to 5-5, which is the section titled "Configure Shelf Global Information/Passwords."
Configure the information in the Shelf Configuration dialog box (see Figure 4-1) as the first step in either the Create Shelf or Modify Shelf procedure. See the following table for a detailed procedure for configuring this information.
| Step | Description | |||
|---|---|---|---|---|
| (Optional.) Enter a description of the shelf. | This description of the shelf is for your convenience. (64-character limit.) | ||
| (Optional.) Enter a serial number. | The serial number of the shelf. (32-character limit.) | ||
| Select a device type. | The device types displayed in this menu depend on two things:
| ||
| Select a shelf number. | The shelf number is a unique identifier of the shelf indicating where it is located in the stack. This pull-down menu displays only the shelf numbers that are available for the device type you are creating, and depends on the stack type and the shelves that you have already created in the stack. Note On Cisco AccessPath-TS3 systems, shelf numbers go from bottom to top. However, if CAM detects any new Cisco AS5300 DMM device added between the first dial shelf (shelf number 5) and the 14th dial shelf (shelf number 18), the GUI will rearrange the Shelf Number list by moving 18 (shelf 14) to the bottom of the list in the Create Shelf screen. | ||
| Enter a host name. | A case-sensitive, unique name for the shelf. The default host name contains the stack state ID, the device type, and the shelf number. For example, s5AS01 would be the first Access Server Shelf in a stack with the stack state ID s5. | ||
| (Optional.) Enter an original secret password. | When CAM enters the enable mode, if the secret password was preconfigured for the shelf, it prompts CAM for the original secret password. Note If the shelf is configured for an original secret password, and you do not enter one here or enter an incorrect password, the shelf configuration fails. | ||
| (Optional.) Enter an original line password. | When CAM Telnets into the shelf, if the line password was preconfigured to the shelf, it prompts CAM for the original line password. Note If the shelf is configured for an original line password, and you do not enter one here or enter an incorrect password, the shelf configuration fails. | ||
| Continue with either the "Configure VPDN/Shelf Trunk Interface (Cisco AS5300 Shelves Only)" section or the "Configure the Shelf Addresses" section, depending on the type of shelf you are configuring. |
| ||
The following information should be inserted beginning on page 5-7, and replaces the section "Configure VPDN/Shelf Trunk Interface (Cisco AS5300 Shelves Only)":
Configuring VPDN and the Shelf Trunk Interface is the second step in either the Create Shelf or Modify Shelf procedure for Cisco AS52300 and Cisco AS5300 shelves only. (See Figure 4-2 and the following table for instructions.)
| Step | Description | |||
|---|---|---|---|---|
| (Optional.) Enable or disable VPDN support. | Select yes or no to enable or disable VPDN1 support. (An option for Cisco AS5300-based Cisco AccessPath systems using PRI, T1/PRI, or E1/PRI trunk types, where VPDN was enabled during the Create Stack or Modify Stack process.) Note: VPDN is not available for the Cisco AS5200. | ||
| Select your framing. | Type of transmission unit used in the T1 or E1 link. Available choices for Channelized E1 and PRI include:
Available choices for Channelized T1 and PRI include:
| ||
| Select a line code. | Variety of Zero Code Suppression used on the link, which in turn affects a number of its characteristics. Available choices for Channelized E1 and PRI include:
Available choices for Channelized T1 and PRI include:
| ||
| (Optional.) Select a trunk type. | Trunk type of the shelf. Valid selections (which are limited depending on the configuration of the stack) include:
| ||
| (PRI trunk type only.) Select an ISDN switch type. | ISDN switch type that services your T1 or E1 PRI lines. You should obtain the correct switch type from your ISDN service provider (telco). Available choices include:
| ||
| Continue with the next section, "Configure the Shelf Addresses."
| Depending on the type of shelf you are configuring, proceed as follows: | ||
| 1VPDN = Virtual Private Dialup Network. |
The following section should be inserted beginning on page 5-9, to replace the "Configure the Shelf Addresses" section:
CAM will assign most IP addresses for devices based on the two /26 IP addresses given when the stack is initially configured, and these addresses should not be changed. All you need to fill in are the addresses left blank on the Shelf Address dialog boxes, which make up the third step in either the Create Shelf or Modify Shelf procedure. These dialog boxes vary, depending on the shelf you are creating or modifying. Use the appropriate procedure for your shelf. (See Table 2 for complete instructions.)
To configure the addresses for the Cisco 2511:
| Step | Description | |||
|---|---|---|---|---|
| Confirm the Ethernet 1/0 address. | Ethernet port 1/0 IP address. | ||
| Confirm the Ethernet 1/0 mask. | Ethernet port 1/0 subnet mask. | ||
| Confirm the Ethernet 1/1 address. | Ethernet port 1/1 IP address. | ||
| Confirm the Ethernet 1/1 mask. | Ethernet port 1/1 subnet mask. | ||
| Confirm the Loopback 1 address. | Network management IP address for the shelf. | ||
| Confirm the Loopback 1 mask. | Network management subnet mask for the shelf. | ||
| Confirm the Async Aux IP address. | IP address used for the remote dial-in, out-of-band management. | ||
| Confirm the Async Aux IP mask. | Subnet mask for the connection to remote dial-in, out-of-band management. | ||
| Configure the shelf configuration parameters. | Continue with the "Configure the Shelf Configuration Parameters" section. | ||
To configure the addresses for the Cisco 3640:
| Step | Description | |||
|---|---|---|---|---|
| Confirm the Ethernet 1/0 address. | Ethernet port 1/0 IP address. | ||
| Confirm the Ethernet 1/0 mask. | Ethernet port 1/0 subnet mask. | ||
| Confirm the Ethernet 1/1 address. | Ethernet port 1/1 IP address. | ||
| Confirm the Ethernet 1/1 mask. | Ethernet port 1/1 subnet mask. | ||
| Confirm the Loopback 1 address. | Network management IP address for the shelf. | ||
| Confirm the Loopback 1 mask. | Network management subnet mask for the shelf. | ||
| Confirm the Async Aux IP address. | IP address used for the remote dial-in out-of-band management. | ||
| Confirm the Async Aux IP mask. | Subnet mask for the connection to remote dial-in out-of-band management. | ||
| Configure the shelf configuration parameters. | Continue with the "Configure the Shelf Configuration Parameters" section. | ||
To configure the addresses for the Cisco AS5200:
| Step | Description | |||
|---|---|---|---|---|
| Confirm the Ethernet address. | Ethernet IP address. | ||
| Confirm the Ethernet mask. | Subnet mask of the Ethernet. | ||
| Confirm the Loopback 0 address. | Virtual IP interface carrying all the dial-in users. Exists only in the access server shelves. Assign an IP network number to the loopback interface, then let each asynchronous interface borrow this network number. | ||
| Confirm the Loopback 0 mask. | Subnet mask of Loopback 0. | ||
| Confirm the Loopback 1 address. | Network management address for the shelf. | ||
| Confirm the Loopback 1 mask. | Network management subnet mask for the shelf. | ||
| Configure the beginning and ending IP local pool addresses. | IP local pool is a pool of IP addresses that exists inside the Access Server Shelves, all of which are on the same IP subnet as loopback interface 0. (In Cisco AccessPath-TS3 systems, the loopback interface 0 is on the first class C network, but the IP pool addresses begin in the second class C network.) | ||
| Configure the shelf configuration parameters. | Continue with the "Configure the Shelf Configuration Parameters" section. | ||
To configure the addresses for the Cisco AS5300:
| Step | Description | |||
|---|---|---|---|---|
| Confirm the Ethernet address. | Ethernet IP address. | ||
| Confirm the Ethernet mask. | Subnet mask of the Ethernet. | ||
| Confirm the Loopback 0 address. | Virtual IP interface carrying all the dial-in users. Exists only in the Access Server Shelves. Assign an IP network number to the loopback interface, then let each asynchronous interface borrow this network number. | ||
| Confirm the Loopback 0 mask. | Subnet mask of Loopback0. | ||
| Confirm the Loopback 1 address. | Network management address for the shelf. | ||
| Confirm the Loopback 1 mask. | Network management subnet mask for the shelf. | ||
| Configure the beginning and ending IP local pool addresses. | IP local pool is a pool of IP addresses that exists inside the Access Server Shelves, all of which are on the same IP subnet as loopback interface 0. (In Cisco AccessPath-TS3 systems, the loopback interface 0 is on the first class C network, but the IP pool addresses begin in the second class C network.) | ||
| Confirm the Fast Ethernet address. | The Fast Ethernet IP address. | ||
| Confirm the Fast Ethernet mask. | The subnet mask of the Fast Ethernet. | ||
| Configure the IP Summary address. | The IP Summary address. | ||
| Configure the IP Address mask. | The subnet mask of the IP Summary address. | ||
| Configure the shelf configuration parameters. | Continue with the "Configure the Shelf Configuration Parameters" section. | ||
To configure the addresses for the Cisco AS5300 with DMM:
| Step | Description | |||
|---|---|---|---|---|
| Confirm the Ethernet address. | Ethernet IP address. | ||
| Confirm the Ethernet mask. | Subnet mask of the Ethernet. | ||
| Confirm the Loopback 0 address. | Virtual IP interface carrying all the dial-in users. Exists only in the Access Server Shelves. Assign an IP network number to the loopback interface, then let each asynchronous interface borrow this network number. | ||
| Confirm the Loopback 0 mask. | Subnet mask of Loopback 0. | ||
| Confirm the Loopback 1 address. | Network management address for the shelf. | ||
| Confirm the Loopback 1 mask. | Network management subnet mask for the shelf. | ||
| Configure the beginning and ending IP local pool addresses. | IP local pool is a pool of IP addresses that exists inside the Access Server Shelves, either in the first class C network, or in the second class C network. | ||
| Confirm the Fast Ethernet address. | The Fast Ethernet IP address. | ||
| Confirm the Fast Ethernet mask. | The subnet mask of the Fast Ethernet interface. | ||
| Configure the IP Summary address. | The IP Summary address. | ||
| Configure the IP Address mask. | The subnet mask of the IP Summary address. | ||
| Configure the shelf configuration parameters. | Continue with the "Configure the Shelf Configuration Parameters" section. | ||
To configure the addresses for the Cisco 7206:
| Step | Description | |||
|---|---|---|---|---|
| Configure the default route. | Static route that can be overridden by dynamic routing information. | ||
| Confirm the FE0/0 primary address. | Fast Ethernet primary IP address. | ||
| Confirm the FE0/0 primary mask. | Fast Ethernet primary subnet mask. | ||
| Confirm the FE1/0 primary address. | Fast Ethernet primary IP address. | ||
| Confirm the FE1/0 primary mask. | Fast Ethernet primary subnet mask. | ||
| Configure the Loopback1 address. | Network management address for the shelf. | ||
| Configure the Loopback1 mask. | Network management subnet mask for the shelf. | ||
| Confirm the FE1/0 secondary address. | Fast Ethernet secondary IP address. | ||
| Confirm the FE1/0 primary mask. (For stacks with Cisco AS5200 only.) | Fast Ethernet secondary subnet mask. | ||
| Configure the beginning and ending IP local pool addresses.(For stacks with Cisco AS5200 only.) | IP local pool is a pool of IP addresses that exists inside the Access Server Shelves, either in the first class C network, or in the second class C network. | ||
| Configure the shelf configuration parameters. | Continue with the "Configure the Shelf Configuration Parameters" section. | ||
To configure the addresses for the Catalyst 5002:
| Step | Description | |||
|---|---|---|---|---|
| Confirm the sc0 address. | IP address of the in-band interface. | ||
| Confirm the sc0 mask. | Subnet mask of the in-band interface. | ||
| Configure the shelf configuration parameters. | Continue with the next section, "Configure the Shelf Configuration Parameters." | ||
The information in this section supplements or corrects the information in Chapter 8, "Using Tools."
Add the following note to the bottom of page 8-12 in the "Using the IOS Image Manager" section.
Add the following note to the bottom of page 8-30 in the "Using the Modem Firmware Image Manager" section.
The information in this section replaces the information in Appendix A, "Installing Oracle Software."
This appendix gives detailed instructions for installing Oracle Enterprise Server software Version 7.3.4 on Solaris 2.6 to be used as the relational database management system (RDBMS) component of the Cisco Access Manager (CAM). Oracle Enterprise Server software Version 7.3.4 is the recommended release.
The following topics are covered:
Before you can install Oracle 7.3.4, you must perform the following steps:
1. "Configure Kernel Parameters for Shared Memory"
2. "Verify Your Server Has the Solaris Packages Needed by Oracle7"
3. "Create a dba Group in the /etc/group File"
4. "Create the Oracle UNIX Administration Account"
5. "Create the /opt/bin Directory"
To prepare for Oracle installation, you must tune the kernel so that it can use shared memory. You can refer to the etc_system.example.
Step 1 Log in as the root user.
Step 2 Use a text editor such as vi to edit the /etc/system file, adding the following statements to the end of it:
forceload: sys/shmsys forceload: sys/semsys * suggested values used for CAM db in Oracle server set dosynctodr=0 set pt_cnt=512 set shmsys:shminfo_shmseg=10 set shmsys:shminfo_shmmni=512 set shmsys:shminfo_shmmin=1 set semsys:seminfo_semmni=200 set semsys:seminfo_semume=10 * ~ half of real memory, and at least 128M (128*1024*1024) set shmsys:shminfo_shmmax=134217728 *The following is equal to semni set semsys:seminfo_semmnu=200 * sum of the processes value in all the db instances that will be *concurrently up. One db instance for CAM is 200 set semsys:seminfo_semmsl=200 * sets number of db instances on the server * The following two are set to semni X semmsl set semsys:seminfo_semmns=40000 set semsys:seminfo_semmap=40000
Step 3 Save the /etc/system file.
When using forceload, you must specify a filename which includes a directory. The forceload statements cause the specified modules to be loaded at boot time, that is, prior to mounting the root file system rather than at first reference. (Loading a module does not mean that the module will be installed.) If you do not include the forceload statements as indicated, the shared memory parameters might not be set after reboot.
Step 4 Reboot the system.
If you are following along with the Oracle installation guide, it might tell you to install patches at this point. Do not install any patches. Solaris 2.5.1 does not require them.
Confirm the kernel parameter settings by entering the following command:
# /usr/sbin/sysdef
To install Oracle 7.3.4, the following Solaris 2.x packages must already be installed on the server:
To install these packages:
Step 1 Determine if the above-listed Solaris 2.x packages are installed. As the root user, enter the following command:
# pkginfo -i SUNWarc SUNWbtool SUNWlibm SUNWlibms SUNWsprot SUNWtoo
Solaris lists a description of each of the installed packages.
Step 2 Use /usr/sbin/pkgadd to install any of the above packages that are not already installed. Refer to your Solaris installation documentation for full instructions.
For example, to add the SUNWarc package from the Solaris 2.5.x CD-ROM, enter the following commands:
# cd /cdrom/solaris_2_5_1_sparc/s0/Solaris_2.5.1 # pkgadd -d . SUNWarc
As the root user, create a group called dba. We recommend you do this by editing the /etc/group file using the Solaris Admintool, but you can also edit the /etc/group file manually.
If you are running the X Window System (OpenWindows or CDE), you can also use the Admintool graphical user interface (GUI) to create the dba group as follows:
Step 1 Start the Admintool by entering the following command:
# admintool &
Step 2 Choose Browse>Groups, and then Edit>Add.
Step 3 Under Group Name, enter dba. (The Group ID field will be automatically filled with a valid Group ID value.)
Step 4 Click OK.
To manually add the group dba:
Step 1 Check to make sure the 101 group ID (GID) is unassigned by entering the grep command on the /etc/group file:
% grep 101 /etc/group
If you do not receive any output, you can use 101. If you receive output, 101 is in use. In the later case, repeat this step using other group IDs until you find an available one.
Step 2 To manually edit the file, append the following command to the /etc/group file:
dba::101:root,oracle
This can also be done by entering the following command:
% groupadd -g GID dba
where GID is the group ID (GID) that is assigned to the group. (If 101 is already assigned to another group, use a different, unassigned number.)
As the root user, create a user account named oracle. Although this user account could be named something other than Oracle, we recommend that you name the account Oracle for consistency with other Oracle installations. You can create the Oracle account using the Admintool or manually.
To create the Oracle account, you must have the following information:
If you are running the X Windows System (OpenWindows or CDE), you should use the Admintool to create the Oracle account as follows:
Step 1 If the Admintool is not already running, start the Admintool by entering the following command:
# admintool &
Step 2 If you are not in the Admintool: Users screen, select Browse>Users.
Step 3 Select Edit>Add. The Admintool: Modify Users screen appears. (See Figure 5.)
Step 4 Fill out the form as follows:
(a) Under User Name, type oracle.
(b) Under Primary Group, type dba.
(c) Select Create Home Dir.
(d) Under path, type mntpoint/oracle/product/7.3.4.
where mntpoint is the mount point for the Oracle installation that you have determined has at least 3.0 GB of available disk space.
(e) Click OK.
(f) Enter the following commands:
# cd mntpoint # chown -fR oracle oracle # chgrp -fR dba oracle
To create the Oracle user manually:
Step 1 Use vi or another text editor to add the following line to the /etc/passwd file:
oracle:x:UID:101:Oracle Admin:mntpoint/oracle/product/7.3.4:/bin/csh
where UID is the User ID you have determined and uniquely assigned to the Oracle account and mntpoint is the mount point for the Oracle installation that you have determined has at least 4.0 GB of available disk space.
Step 2 Edit the /etc/shadow file. Append the following line:
oracle::::::::
Step 3 Create the Oracle user's home directory. Your home directory would be /mntpoint/oracle/product/7.3.4, where mntpoint is the Oracle installation mount point. This is the same directory into which you will be installing the Oracle software, which will also be known as ORACLE_HOME. Your home directory should be the same as ORACLE_HOME so when you log in as the Oracle user, you will be placed into the directory structure to which you will need access.
To create ORACLE_HOME, enter the following commands:
% cd mntpoint % mkdir -p oracle/product/7.3.4 % chown -fR oracle oracle % chgrp -fR dba oracle
where mntpoint is the mount point for the Oracle installation.
The chown command changes the owner of Oracle directory to Oracle user. The chgrp command changes the group of Oracle directory to dba.
Step 4 Set the Oracle user password. As the root user, enter the following command:
# passwd oracle
You are prompted for the new password and asked to re-enter it to verify you have entered it correctly. Do not forget the Oracle user password.
As the root user, create the /opt/bin directory. Enter the following command:
% mkdir /opt/bin
To set environment variables for the Oracle user:
Step 1 Log in as the Oracle user.
Step 2 Copy .cshrc to .cshrc.save.
Step 3 Using vi or another text editor, add the following statements to the .cshrc file.
umask 022 setenv ORACLE_LBIN /opt/bin setenv ORACLE_BASE mntpoint/oracle setenv ORACLE_HOME mntpoint/oracle/product/7.3.4 setenv ORACLE_DOC $ORACLE_BASE/doc setenv ORACLE_SID CAMDB setenv TNS_ADMIN /var/opt/oracle setenv ORACLE_TERM xsun5 setenv ORACLE_PATH \ $ORACLE_HOME/bin:/usr/local/bin:/opt/bin:/bin:/usr/bin:usr/ccs/bin setenv LD_LIBRARY_PATH \ $ORACLE_HOME/lib:/usr/openwin/lib:/usr/dt/lib:/usr/lib setenv TMPDIR /var/tmp setenv PATH .:$ORACLE_PATH setenv ORAENV_ASK NO source /opt/bin/coraenv unsetenv ORAENV_ASK set filec stty erase ^h #------- setenv APM_DBADMIN $ORACLE_BASE/admin/$ORACLE_SID setenv APM_DBDATA $ORACLE_BASE/oradata/$ORACLE_SID
where mntpoint is the mount point for the Oracle installation.
Step 4 Enter the source command to add the environment variables to your current environment:
% source.cshrc
You might receive an error message that says the /opt/bin/coraenv file is not found. This error will be resolved when you have finished installing Oracle and run the root.sh script.
As the root user, add the following line to the /etc/services file:
listener 1521/tcp # Oracle Listener process
This completes the preinstallation procedures. Continue with the next section, "Installing the Oracle Server Software."
To install the Oracle Server software, follow the steps in this section. Be sure to log in as the Oracle user you created earlier.
Step 1 Insert the Oracle 7.3.4 CD-ROM into the system's local CD-ROM drive.
Step 2 Optionally, as the Oracle user, you can check the environment settings by entering the env command:
% env
Step 3 Change directories to the Oracle installation directory on the CD-ROM:
# cd /cdrom/cdrom0/orainst
Step 4 Enter the orainst command:
%./orainst /m
%./orainst /c
Step 5 Select Default Install and press Enter.
The Installation Activity Choice screen appears:
Step 6 Select the default option, Install, Upgrade, or De-Install Software.
The Installation Options screen appears:
Step 7 Select the second option, Install New Product - Do Not Create DB Objects.
The Environmental Variables screen appears:
Step 8 Make sure that:
Step 9 Press Enter.
The Relink All Executables screen appears:
Step 10 Select No and press Enter. It is not necessary to re-link the executables.
The Summary of Installation Options screen appears:
Step 11 Check to make sure that all of the Oracle file locations are correct. If they are, select OK and press Enter.
The Software Asset Manager screen appears:
Step 12 Select the following components:
*If you are installing CAM client software on your machine only, you need to install only SQL*Plus and SQL*Net.
Step 13 When all of the items listed above are marked for installation, press Enter or click Install.
The DBA Group screen appears, but does not apply to the client.
Step 14 Select dba and press Enter.
The OSOPER Group screen appears, but does not apply to the client.
Step 15 With dba selected as the OSOPER group, press Enter. The Shared Library Installation screen appears:
Step 16 Select OK and press Enter. After 25 to 40 minutes, the Installer Actions Completed screen appears:
Step 17 Press Enter.
The Software Asset Manager screen appears. Press Tab until Exit is highlighted, and then press Enter twice. This completes the Oracle Server software installation. Proceed to "Postinstallation Procedure."
Login as root user and run the root.sh script. Enter the following commands:
# setenv ORACLE_HOME /mntpoint/oracle/product/7.3.4 # setenv ORACLE_SID CAMDB # cd $ORACLE_HOME/orainst # /usr/bin/sh./root.sh
where mntpoint is the mount point for the Oracle installation which you have determined has at least 2.0 GB of available disk space.
This completes the postinstallation procedure. Resolve any issue with the Oracle dbstart and dbshut scripts.
For additional documentation, refer to the Oracle Corporation Web site at http://www.oracle.com.
Cisco recommends that you setup automatic shutdown and startup of the database at system shutdown and startup respectively. To acheive this, add the run control script CSCOcam_oracle.example to the system and edit the oratab file as described below:
To add the run control script:
Step 1 Login as the root user on the Oracle Server machine:
Step 2 Enter the following commands:
# cp /opt/CSCOcamdb/db/admin/CSCOcam_oracle.example
/etc/init.d/CSCOcam_oracle # ln -s /etc/init.d/CSCOcam_oracle
/etc/rc2.d/S80CSCOcam_oracle # ln -s /etc/init.d/CSCOcam_oracle
/rc0.d/K80CSCOcam_oracle
To edit the /var/opt/oracle/oratab file:
Step 1 Open the file using a text editor.
Step 2 Find the entries for all the databases that you startup and shutdown automatically. They are identified by the sid in the first field.
Database entries in the oratab file appear in the following format:
<ORACLE_SID>:<ORACLE_HOME>:[y/n]
where y or n specifies whether you want the database started and shutdown automatically.
Step 3 Change the last field for each to y.
This section discusses Oracle issues relevant to CAM Database installation (or upgrade) and configuration. It is to be used as a reference by the local DBA when configuring a server for use with CAM, but it does not provide comprehensive procedures.
You may notice that many files/variables' names start with APM. This is because CAM's previous major release was APM 2.0.
The CAM Database stores configuration and statistical data describing the devices managed by CAM . There are two types of tables in the database:
CAM can use either a local Oracle database or a remote Oracle database. The package CSCOcamdb is the package to install/configure a database instance for CAM (either local or remote.) And, this CSCOcamdb must be installed sucessfully first in order for CAM (either local or remote) package (CSCOcam) to be installed/configured.
The package CSCOcamdb must be installed in the machine in which the Oracle server is installed and running. Package CSCOcam must be installed in the machine in which the CAM server will be running on. If the CAM server machine is the same as Oracle server machine, it is a local database case, otherwise, it is a remote database case.
The CAM installation package (CSCOcamdb) contains scripts for automatically creating the CAM database. The APM_dbcreate.sh script in /opt/CSCOcamdb/db/admin (or in /opt/CSCOcam/db/admin for a remote database) is the master database creation script that invokes all the other necessary scripts.
If you do not want to use the default database settings created by automatic database installation in the package CSCOcamdb, then you should do the following (do NOT do this if you are an Oracle novice):
Step 1 Install the CSCOcamdb package without the database automatic configuration.
Step 2 Log in as the Oracle user.
Step 3 Edit the appropriate database creation scripts in
/opt/CSCOcamdb/db/admin and/or in /opt/CSCOcamdb/db/schema.
Step 4 Run APM_dbcreate.sh to create the CAMDB database.
The default database is large enough to support up to 100,000 ports. It is unlikely that the user will have to increase tablespace sizes because the CAM product cannot support that many ports yet. The amount of disk space used by the database is roughly 2 GB.
Edit the scripts described in this document to control the location of the database and the sizes of the various tablespaces. The environment variable ORACLE_BASE control the location for admin files and data files. APM_dbcreate.sh will use $ORACLE_BASE/admin/$ORACLE_SID for storing admin files, and $ORACLE_BASE/oradata/$ORACLE_SID for storing data files.
As with all databases, the local DBA should constantly monitor tablespace usage. Depending on how the CAM product is used, it is possible that at one point or another you may have to increase a tablespace size by either adding new data files or extending existing ones. Other standard DBA tasks would include rebuilding indexes, and doing an occasional export and import for defragmentation purposes.
The following SQL scripts contain the commands to create the database objects and allocate space for them:
By default, all the database data files are created in the directory pointed to by the $APM_DBDATA and by default it is set to be $ORACLE_BASE/oradata/$ORACLE_SID. If this is not where you would want to put your database data files, so you should edit these SQL scripts (create_db.sql, create_ts.sql, create_user_data.sql, and create_user_index.sql ), and specify the locations that are appropriate for your local environment.
In the directory /opt/CSCOcamdb/db/schema, ApmTablesCom.sql and ApmTablesHist.sql scripts create all the tables and assign them to the appropriate tablespace. You can edit this script to change the tablespace assignments.
The space for the CAM Database is distributed as follows:
The specified table and index sizes are estimates based on calculations. The actual sizes and extents may be different.
TABLE Total (apm_data_ts): | 950 MB |
INDEX Total (apm_index_ts): | 400 MB |
Fixed overhead: | 600 MB |
TOTAL DB space requirement: | 1,950 MB ( roughly 2 GB) |
| Object Name | MB |
|---|---|
hist_pris | 80 |
hist_pris_pk | 20 |
hist_pris_ix | 20 |
hourly_pris | 90 |
hourly_pris_pk | 22 |
hourly_pris_ix | 22 |
daily_pris | 15 |
daily_pris_pk | 5 |
daily_pris_ix | 3 |
hist_shelf | 20 |
hist_shelf_pk | 8 |
hist_shelf_ix | 8 |
daily_modem_conn | 380 |
daily_modem_conn_pk | 60 |
daily_modem_conn_ix | 40 |
daily_modem_conn_ix2 | 40 |
Note that the final database space requirement totals include the 100 MB of estimated space required for logs and dumps. This space is not preallocated, but it has to be taken into account when estimating the total CAM database disk space requirements.
It is recommended that the index and data tablespaces are created on different physical disks for optimal performance.
After creating the database, if at any time in the future you wish to increase the size of the tablespaces:
Step 1 Log into the Oracle server machine as oracle
Step 2 Set up the CAM database environment. The easiest way to do this is to execute the /opt/CSCOcamdb/Apm.sh script in a Bourne or Korn shell. Then set environment APM_DBPATH to be $ORACLE_BASE/oradata/$ORACLE_SID
Step 3 Invoke sqlplus:
% sqlplus db user id/db user password
Step 4 To add space to an existing tablespace, you can either extend an existing datafile, or add a new datafile. To extend an existing datafile execute the following SQL command at the sqlplus prompt:
% ALTER DATABASE DATAFILE 'datafile_path/datafile_name' % RESIZE numberM;
Replace datafile_path with the full path to the datafile you wish to resize. Replace datafile_name with the name of the datafile, and replace number with the number of megabytes you want the resized file to occupy.
To add a datafile to an existing tablespace, execute the following command:
% ALTER TABLESPACE <tablespace_name> ADD DATAFILE % 'datafile_path/datafile_name' SIZE numberM;
Replace tablespace_name with the name of the tablespace to which you are adding the new datafile. Replace datafile_path with the full path to the datafile you are about to create. Replace datafile_name with the name of the new datafile, and replace number with the number of megabytes you want to allocate to the new file.
New data files can be created in any filesystem that has enough free space. In other words, you do not have to create the new files in the same directory, or in the same partition, or on the same physical disk as the existing data files. Always make sure there is enough available space in the file system in which you are resizing existing data files or adding new ones.
EXAMPLES:
apm_data01.dbf is the default datafile for the apm_data_ts tablespace.
To change the size of the data01.dbf datafile to 1200M do the
following:
% ALTER DATABASE DATAFILE '$APM_DBPATH/apm_data01.dbf' % RESIZE 1200M;
To create a new 200MB datafile for the apm_index_ts tablespace:
% ALTER TABLESPACE apm_index_ts ADD DATAFILE % '$APM_DBPATH/apm_index02.dbf' SIZE 200M;
Because there are a large number of inserts and deletes in the CAM database, it is necessary to rebuild indexes occasionally. This is a standard database maintenance task. About once a month, run the following command:
% ALTER INDEX index_name REBUILD TABLESPACE apm_index_ts;
This will rebuild the index using the storage parameters that were in effect when the index was originally created. If you determine that too many extents have been allocated to the index, and rebuilding does not help to reduce the number of extents, then run the following:
% ALTER INDEX index_name REBUILD STORAGE (INITIAL XX M NEXT YY M) % TABLESPACE apm_index_ts;
Replace XX with the new INITIAL extent size, and replace YY with the new value for the size of the NEXT extent of this index. It is important to always specify the tablespace name, or else the index will be rebuilt in the user's default tablespace (which is unlikely to be index_ts).
If the above commands are ineffective because Oracle is unable to allocate the initial extent, then do the following:
Step 1 In sqlplus:
% "DROP INDEX index_name;"
Step 2 Find the index creation command for this index in ApmTablesCom.sql
Step 3 Copy/paste the complete index creation command into sqlplus.
For Remote DB support, tailoring of both the Client and Server SQL*Net is left to your local Oracle support personnel familiar with the specific Oracle installation.
If CAM is not on the same machine or the Oracle server, then both Oracle database server machine and the CAM server machine need to be configured so that CAM can access the database.
On the Oracle server machine, the configuration file:/var/ora/oracle/listener.ora must be configured for listener and listener must be restarted up after the CAM DB instance is created. There should be a port (default 1521) reserved in the /etc/services file.
In the CSCOcamdb package, the file CSCOcamdb/reloc/db/admin/listener.ora.example (before CSCOcamdb is installed) or /opt/CSCOcamdb/db/admin/listener.ora.example (after CSCOcamdb is installed) are provided for your reference as how to configure /var/opt/oracle/listener.ora.
To restart the listener, login as the Oracle user and enter
% $ORACLE_HOME/bin/lsnrctl stop % $ORACLE_HOME/bin/lsnrctl start % $ORACLE_HOME/bin/lsnrctl status
On the CAM server machine (database client machine), the Oracle software SQL*Plus and SQL*Net must be installed before installation of CSCOcam package.
There is no need to create Oracle UNIX user and DBA group in the CAM server machine in remote case. You may directly install only Oracle SQL*Plus and SQL*Net software package using Oracle CD image the same as Oracle server machine uses.
The configuration file:/var/opt/oracle/oracle/tnsnames.ora must be configured and environment variable TNS_ADMIN must be set to /var/opt/oracle.
There are two possible ways on a database client machine:
1. If there is NO /var/opt/oracle/oracle/sqlnet.ora file, or /var/opt/oracle/oracle/tnsnames.ora is configured as CAMDB = (No domain name associates with tns name.), refer to the example in the CSCOcamdb pacakge: CSCOcamdb/reloc/db/admin/tnsnames.ora.example1 before installation, or /opt/CSCOcamdb/db/admin/tnsnames.ora.example1 after installation. This is also in the CSCOcam package: CSCOcam/reloc/db/admin/tnsnames.ora.example1 before installation, or /opt/CSCOcam/db/admin/tnsnames.ora.example1 after installation.
2. If there is a /var/opt/oracle/oracle/sqlnet.ora file, /var/opt/oracle/oracle/tnsnames.ora is configured as CAMDB.<domain name> = (There must be a domain name associated with the tns name).
There are examples for tnsnames.ora and sqlnet.ora in the CSCOcamdb package at CSCOcamdb/reloc/db/admin/tnsnames.ora.example2 before installation, or /opt/CSCOcamdb/db/admin/tnsnames.ora.example2 after installation, and at CSCOcamdb/reloc/db/admin/sqlnet.ora.example before installation, or /opt/CSCOcamdb/db/admin/sqlnet.ora.example after installation.
There are also examples for tnsnames.ora and sqlnet.ora in the CSCOcam package: CSCOcam/reloc/db/admin/tnsnames.ora.example2 before installation, or /opt/CSCOcam/db/admin/tnsnames.ora.example2 after installation. CSCOcam/reloc/db/admin/sqlnet.ora.example before installation, or /opt/CSCOcam/db/admin/sqlnet.ora.example after installation.
In either case, CAM needs to have the following matched to the configuration:
1. In /opt/CSCOcam/Apm.sh, TNS_ADMIN=/var/opt/oracle
2. In /opt/CSCOcam/cgi-bin/apm.ini:
dbServer=<tns name>
(this should be the same as ORACLE_SID in /opt/CSCOcam/Apm.sh.)
dbUserName=<db user id>
dbPassword=<db user password>
dbremote=1
The Oracle Database and listener automatically start up after system reboot. Usually, if you set up the UNIX system in /etc/rd2.d for automatically startup script and /etc/rd0.d for automatically shutdown script, when the UNIX system reboots, the Oracle server will be shutdown properly and startup automatically.
There is a script in CSCOcamdb package for your referece to set up the system so that the Oracle Database and listener will automatically shutdown and start up in the system reboot time, CSCOcam/reloc/db/admin/CSCOcam_oracle.example before installation, or /opt/CSCOcam/db/admin/CSCOcam_oracle.example after installation.
The steps are:
Step 1 Login to the Oracle server machine as root, and copy CSCOcam_oracle.example as /etc/init.d/CSCOcam_oracle using the command
% 'cp /opt/CSCOcamdb/db/admin/CSCOcam_oracle.example \ /etc/init.d/CSCOcam_oracle'
and make sure it is runable by the root user.
Step 2 Setup the symblic links so that /etc/rc2.d/S80CSCOcam_oracle -> /etc/init.d/CSCOcam_oracle and /etc/rc0.d/K80CSCOcam_oracle -> /etc/init.d/CSCOcam_oracle.
# 'ln -s /etc/init.d/CSCOcam_oracle /etc/rc2.d/S80CSCOcam_oracle' # 'ln -s /etc/init.d/CSCOcam_oracle /etc/rc0.d/K80CSCOcam_oracle'
The listener will take some minutes to start up after the system reboot. The script CSCOcam_oracle will automatically start ALL database instances in /var/opt/oracle/oratab which have "Y" in the end.
To create a new database instance after the CSCOcamdb package is installed:
Step 1 Make sure /etc/system have modified to enough resources for the new database which you are going to add. If you need to modify /etc/system, you need to reboot the machine after the modification.
Step 2 su to Oracle user .
Step 3 cd /opt/CSCOcamdb/db/admin.
Step 4 Run the ./add_dbinstance.sh, and answer all the questions.
There will be a logfile in /opt/CSCOcamdb/logfiles/add_dbinstance.log
To remove a database instance before the CSCOcamdb package is removed:
Step 1 su to Oracle user.
Step 2 cd /opt/CSCOcamdb/db/admin.
Step 3 Run ./remove_dbinstance.sh and answer all the questions.
There will be a logfile in /opt/CSCOcamdb/logfiles/remove_dbinstance.log. You must remove all the database instances which you created after CSCOcamdb package installed first prior removing CSCOcamdb package. That is, in the process of removing CSCOcamdb package, it can only remove one database instance at most.
To upgrade Oracle 7.3.2 to Oracle 7.3.4:
When upgrading from APM 2.0 to CAM 3.1, you must first upgrade Oracle to 7.3.4. Below are the steps for performing the Oracle upgrade:
Step 1 Shutdown APM 2.0.
Step 2 Shutdown Oracle.
Step 3 Install Oracle 7.3.4.
Step 4 Do the following as the Oracle user:
Step 5 Do the following as the root user:
Step 6 Edit $ORACLE_HOME/dbs/initAPMDB.ora file
Step 7 Do the following commands as the Oracle user:
$ cd $ORACLE_HOME/rdbms/admin $ svrmgrl SVRMGR> connect internal SVRMGR> startup restrict SVRMGR> @cat7303.sql # do this one if going from 7.3.3!! SVRMGR> @cat7304.sql SVRMGR> @catalog.sql SVRMGR> @catproc.sql SVRMGR> alter system disable restricted session; SVRMGR> quit
Step 8 If your APMDB database directory is NOT under the 7.3.3 Oracle directory, you can remove the 7.3.3 tree with rm -rf.
If APMDB is under the 7.3.3 tree, you can either leave the 7.3.3 tree there, or (to reclaim disk space) delete all the directories under 7.3.3 EXCEPT the dbs directory.
Step 9 OPTIONAL: Apply a patch to Oracle 7.3.4 that prevents a core dump in sqlplus when installing the CSCOcamdb package. If you find that package installation fails due to scripts abruptly failing, then you MUST install the patch. The patch is available on the CAM 3.1 CD at :
cd_mount_point/CSCOcamdb/reloc/db/admin/oracle_734_patch.tar
To apply the patch, untar the file, and follow the directions in the README.647741 file (647741 is Oracle's bug number).
For additional documentation, refer to the Oracle Corporation Web site at http://www.oracle.com.
Cisco Connection Online (CCO) is Cisco Systems' primary, real-time support channel. Maintenance customers and partners can self-register on CCO to obtain additional information and services.
Available 24 hours a day, 7 days a week, CCO provides a wealth of standard and value-added services to Cisco's customers and business partners. CCO services include product information, product documentation, software updates, release notes, technical tips, the Bug Navigator, configuration notes, brochures, descriptions of service offerings, and download access to public and authorized files.
CCO serves a wide variety of users through two interfaces that are updated and enhanced simultaneously: a character-based version and a multimedia version that resides on the World Wide Web (WWW). The character-based CCO supports Zmodem, Kermit, Xmodem, FTP, and Internet e-mail, and it is excellent for quick access to information over lower bandwidths. The WWW version of CCO provides richly formatted documents with photographs, figures, graphics, and video, as well as hyperlinks to related information.
You can access CCO in the following ways:
For a copy of CCO's Frequently Asked Questions (FAQ), contact cco-help@cisco.com. For additional information, contact cco-team@cisco.com.
Posted: Wed Jun 9 12:14:56 PDT 1999
Copyright 1989-1999©Cisco Systems Inc.