|
|
This document contains information pertaining to the installation and configuration of Cisco Access Manager (CAM) version 4.0.
You must have CAM version 3.1 in order to upgrade from a previous installation. If you have an earlier version, you must uninstall it and perform a complete, new installation of version 4.0.
The information contained in this document updates the Cisco Access Manager Software Installation and Configuration Guide for version 3.0, which is included in your distribution package. Some, but not all, of the information presented here was incorporated into the online documentation (including the Cisco Documentation CD ROM) at the time of the 3.1 release. When this is the case, it will be noted in the text.
 |
Note Many of the files, directories, variables and scripts associated with CAM version 4.0 have names which include the acronym APM. This refers to an earlier name of the CAM software. |
CAM has been modified to work with the following:
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 If 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 |
|---|---|---|---|---|---|
|
Note Cisco recommends that you install CAM on a Sun Ultra 60 system with dual CPUs to allow for future expansion of managed dial pools. |
This section describes the first-time installation of CAM 4.0 on local or remote workstations.
For instructions on upgrading CAM 3.1 to CAM 4.0, see the "Upgrade from CAM 3.1" section.
CAM 4.0 installation involves two packages, CSCOcamdb and CSCOcam:
Table 1 CAM Installation Packages
CAM 4.0 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, which is summarized in the section "Appendix A Updates" of this update document.
During the CAM installation, you will need to know the following information:
The CAM 4.0 installation process installs and runs a copy of the Netscape FastTrack web server. Prior to installing CAM 4.0, you must shut down any other web servers installed on the CAM workstation.
To install CAM 4.0 software, complete the procedures described in the following sections:
2. Install the CSCOcamdb Oracle Database
3. Create an Additional CAM Database Instance (Optional)
4. Install the CSCOcam Executables
|
Note See the "System
Requirements" section and
"Preinstallation Tasks"
section before beginning the CAM installation. Refer to the release notes that accompanied your software if you receive unexpected warning messages or otherwise need to troubleshoot this procedure. |
To mount the CD-ROM, complete the following steps:
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:
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:
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.
You can terminate the script by typing Ctrl-c.
|
Note In the following steps, default values are displayed in square brackets [ ]. To accept the default values, press Enter. |
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:
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 heading "CAM Database and Upgrade Issues" in the "Appendix A Updates" section of this update document.
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 set up 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:
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:
Step 5 Enter the installed location of the Oracle software:
where $ORACLE_HOME is the Oracle home directory environment variable.
For example: /oracle/product/8.0.5
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:
Step 7 Enter the Oracle group name:
Step 8 Enter the Oracle database instance name:
Step 9 Enter the location of the CAM database directory (ORACLE_BASE).
By default, database administration scripts will be placed in the directory $ORACLE_BASE/admin/CAMDB, and data files will be placed in the directory $ORACLE_BASE/oradata/CAMDB. $ORACLE_BASE should reside on a file system with 2 GB of available disk space.
Step 10 Enter the Oracle system user password:
Step 11 Enter the CAM database username:
Step 12 Enter the CAM database user password:
A summary of your selection settings, similar to the following display, will appear.
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:
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:
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 2 Log in as the Oracle user, or change your user ID with the su command:
Step 3 Change to the /opt/CSCOcamdb/db/admin directory:
Step 4 Run the add_dbinstance.sh script:
Step 5 Enter the Oracle user password, or press Enter to accept the default in square brackets [ ]:
Step 6 Enter the name of the Oracle database instance you would like to create:
|
Note There is no default value specified for the name of the Oracle database. You must enter a name. |
Step 7 Enter the Oracle base location, or press Enter to accept the default in square brackets [ ]:
Step 8 Enter the Oracle username and password:
|
Note There are no default values specified for the Oracle database username or the Oracle database user password. You must enter a username and a password. |
Step 9 A summary of your selection settings will appear. Review these settings.
Step 10 Run the ApmSchema.sh script, as the root user.
Step 11 Load the default data into this additional database, from the CAM server machine that will use this database.
To install the CSCOcam package, complete the following steps:
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.
You can terminate the script by typing Ctrl-c.
Step 2 Specify whether CSCOcam will be using a local or a remote database. (A remote database is a database that is located on a different machine than the one running CSCOcam.)
Step 3 Enter the base directory for CSCOcam installation:
|
Note In the following steps, default values are displayed in square brackets [ ]. To accept the default values, press Enter. |
Step 4 For remote Oracle database installations only, enter the installed location of the Oracle software:
where $ORACLE_HOME is the Oracle home directory.
For example: /oracle/db/product/8.0.5
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:
Step 6 Enter the Oracle database username and password:
Step 7 Enter the tftpd root directory:
Step 8 Enter the device username (required by the AAA server):
Step 9 Enter the device password (registered with the AAA server):
Step 10 Enter the password for the CAM administrator:
|
Note CAM requires that a device account and a CAM administrator account and password be registered with the AAA server. The default username is CAMadmin. |
Step 11 A summary of your selection settings will appear. Review these settings.
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:
Step 13 Confirm that the package can perform scripts requiring superuser privileges:
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.
This section describes the process of upgrading from CAM 3.1 to CAM 4.0. The installation software will detect existing installations of CAM 3.1 and upgrade accordingly.
As with an initial CAM 4.0 installation, the upgrade procedure involves the installation of two packages, CSCOcam and CSCOcamdb.
CSCOcamdb 4.0 should be installed on the machine where CSCOcamdb 3.1 was installed. CSCOcam 4.0 should be installed on the machine where CSCOcam 3.1 was installed.
CSCOcamdb 4.0 must be installed prior to installing CSCOcam 4.0.
The ORACLE_SID environment variable 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.1, no new packages are added. The existing packages (CSCOcam 3.1 and CSCOcamdb 3.1) 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.
Prior to upgrading to CAM 4.0, you must first install Oracle 8.0.5 and migrate your existing CAM database. See the section "Migration of an existing CAM Database from Oracle 7 to Oracle 8".
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.
|
Note See the "System Requirements" section and the "Preinstallation Tasks" section before beginning the CAM 4.0 upgrade. |
To upgrade CAM 3.1 software, you must complete the following tasks in the order shown:
a. "CAM 3.1 (Local Database) to CAM 4.0 Upgrade"
b. "CAM 3.1 (Remote Database) to CAM 4.0 Upgrade"
|
Note Refer to the release notes that accompanied your software if you receive unexpected warning messages or otherwise need to troubleshoot this procedure. |
During the upgrade, you will need to know the following information:
|
Note CAM requires that a device account and a CAM administrator account and password be registered with the AAA server. The default username is CAMadmin. |
The CAM upgrade process will also install and run a copy of the Netscape FastTrack Web server. Before upgrading, perform the following tasks:
Step 2 Login as the root user or change to the root user ID using the su command and shut down the CAM 3.1 software if it is not already shutdown.
Step 3 Backup your existing CAM installation (the CAM directory), as follows:
b. Login as the Oracle user (or use the su command) and stop the Oracle database, if it is not already stopped.
Be sure to back up both the CAM file system and the Oracle database files.
Step 4 Start the database. As the Oracle user, enter the following
Step 5 Proceed to the section "Migration of an existing CAM Database from Oracle 7 to Oracle 8".
To mount the CD-ROM, complete the following steps:
Step 2 Place the CAM 4.0 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:
When upgrading locally, the CAM 3.1 software is upgraded to CAM 4.0 on the existing CAM 3.1 machine. The CAM 4.0 package installations detect existing CAM 3.1 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 Database Package" and "Upgrade the CSCOcam Executables".
CAM 4.0 software can be installed in two different configurations.
In the local database case, the CAM 4.0 packages CSCOcamdb and CSCOcam must be installed on the CAM 3.1 machine.
In the remote database case, CSCOcamdb 4.0 must be installed on the machine with CSCOcamdb 3.1 installed, and CSCOcam 4.0 must be installed on the machine with CSCOcam 3.1 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.1 packages (CSCOcam and CSCOcamdb) are updated to CAM 4.0 packages. Therefore, the packages CSCOcam and CSCOcamdb should not be removed using the CAM 3.1 removal procedure. This will result in removal of the upgraded CAM 4.0 database and packages.
To upgrade a CAM 3.1 installation with a local database to CAM 4.0, on the CAM 3.1 server complete the following steps:
Refer to the "Preupgrade Tasks" section for the backup procedure.
Step 2 Mount the CD-ROM.
Refer to the section "Mount the CD-ROM" for the detailed procedure, if necessary.
Step 3 Change the directory to the CD-ROM drive.
Step 4 Install the CSCOcamdb 4.0 package.
Refer to the section "Upgrade the CSCOcamdb Database Package" for the detailed upgrade procedure, if necessary.
Step 5 Become the superuser again.
Step 6 Change the directory to the CD-ROM drive.
Step 7 Install the CSCOcam 4.0 package.
Refer to the section "Upgrade the CSCOcam Executables" for the detailed upgrade procedure, if necessary.
On the machine with the CSCOcamdb 3.1 database package installed, complete the following steps
Refer to the "Preupgrade Tasks" section for the backup procedure.
Step 2 Login as root (or use the su command to change to the superuser ID).
Step 3 Mount the CD-ROM.
Refer to the section "Mount the CD-ROM" for the detailed procedure, if necessary.
Step 4 Change the directory to the CD-ROM drive.
Step 5 Install the CSCOcamdb 4.0package.
Refer to the section "Upgrade the CSCOcamdb Database Package" for the detailed upgrade procedure, if necessary.
On the machine with the CSCOcam 3.1 software package installed, complete the following steps:
Refer to the "Preupgrade Tasks" section for the backup procedure.
Step 2 Login as root or use the su command to change your user ID to the superuser.
Step 3 Shutdown the CAM server software.
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.
Step 6 Install the CSCOcam 4.0 package.
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 runthe camdb_pkgadd script first, then the cam_pkgadd script.
where device is the device name of the CD-ROM drive.
You can terminate the script by typing Ctrl-c.
|
Note In the following steps, default values are displayed in square brackets [ ]. To accept the default values, press Enter. |
Step 2 The script detects the presence of CAM 3.1 and asks you to confirm that you want to overwrite the existing files.
Step 3 When you say yes, the script asks you to confirm that you want to upgrade to CAM version 4.0.
Step 4 The script asks you to confirm that Oracle 8.0.5 has been installed and that you have migrated your CAM 3.1 database to the new Oracle.
If you say yes, the script will verify that Oracle has been installed, that there is sufficent space on your disk, and that configuration parameters are correct.
If there are errors, the script will stop. When you have corrected the conditions noted in the output messages, return to step 1 and rerun the camdb_pkgadd script.
Step 5 The script asks for the location of your Oracle installation. Do not select the default; this points to the Oracle 7.3.4 location. You must enter the location of your new Oracle 8.0.5 installation.
Step 6 A summary of your selection settings will appear.
Review these settings and enter one of the following:
Step 7 Confirm that the package can perform scripts requiring superuser privileges:
The installation process now installs the CSCOcamdb database on your workstation. When the upgrade is complete, the script will notify you with the message:
Step 2 Select whether to use a local or remote Oracle Database:
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 The script asks if you want to overwrite the existing installation.
Step 4 Confirm that you wish to upgrade:
Step 5 Confirm that you have installed Oracle 8.0.5 and migrated your database to the new Oracle installation.
The script will then verify that these tasks have been done. If there are errors, the script will halt.
Step 6 The script asks you to identify the location of your Oracle 8.0.5 installation.Do not accept the default; this is your previous Oracle installation. You must change the 7.3.4 to 8.0.5.
Step 7 Confirm the rest of the settings:
Step 8 Confirm that the package can perform scripts requiring superuser privileges to install the CAM 4.0 files:
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:
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.
Assuming you backed up CAM exactly as described in the CAM backup instructions, do the following:
Step 2 Restore the CSCOcamdb and CSCOcam package files, as follows:
Step 3 Restore the CAMDB database files and start the database, as follows:
1. "Remove CSCOcam Executables"
2. "Remove Any Additional CAM Database Instances"
3. "Remove the CSCOcamdb Files and the Primary Database Instance"
|
Note These procedures only shutdown and remove only the files, executables, and databases that have been installed, located, or configured by the CAM Installation scripts. Any executables and databases that were manually created or configured will not be removed. |
To remove the CSCOcam package:
where device is the device name of the CD-ROM drive.
The cam_pkgrm command automatically does the following:
Step 2 If you are sure you want to remove the CSCOcam package, enter 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:
Step 2 Change to the /opt/CSCOcamdb/db/admin directory:
Step 3 Run the remove_dbinstance.sh script:
Step 4 Enter the name of the Oracle instance you want to remove:
Step 5 Enter the Oracle base directory for the instance you want to remove, or press Enter to accept the default in square brackets [ ]:
Step 6 Confirm that you want to remove this database instance:
where device is the device name of the CD-ROM drive.
Step 2 If you are sure you want to remove the CSCOcam package, enter 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:
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:
This completes the procedure for removing CAM.
Netscape FastTrack web server is included with CAM and is used by default. It is installed and configured during the CAM installation, however, if you want to customize its installation, use this 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.
|
Note Netscape Navigator is installed on the CSCOcam server during the installation of the CSCOcam package. If you need to install Netscape Navigator on additional UNIX or Windows machines, run the installation executables listed in the in the following table of file locations. Refer to Netscape's documentation, available on the World Wide Web at http://www.netscape.com, for further instructions. |
The following are key file locations used by Netscape FastTrack Server software:
| Software | Directory Location |
|---|---|
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:
|
Note You might need to provide the full domain name for your environment instead of just the host name. For example, cam_server_name.your_company.com in place of cam_server_name. |
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 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:
This completes the procedure for editing the CAM default settings for the Netscape FastTrack Admin Server.
|
Note Certain information in Chapter 4, "Configuring Containers" should be changed in the printed version of the Cisco Access Manager Software Installation and Configuration Guide. (The online versions of this document have already been updated.) |
Replace Table 4-1 on page 4-8 with the following:
Table 2 Access Path Supported Cisco AccessPath Stack Types
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:
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.
|
Note Cisco AccessPath Stacks may not contain a mix of Cisco AS5200 and AS5300 devices. |
Replace the text on page 4-23 with the following:
To configure stack addressing information:
|
Note Certain information in Chapter 5, "Configuring Shelves," of the printed version of the Cisco Access Manager Software Installation and Configuration Guide, should be changed, as follows. (The online versions of this document—on CCO or the Documentation CD—have already been updated.) |
Add the following two paragraphs at the bottom of page 5-3, in the section titled "Modifying a Shelf in a Stack:"
To upgrade an existing Cisco AS5300 shelf to support DMM, use the Modify Shelf function to change Device Type from Cisco AS5300 to AS5300 DMM. You will not need to first delete the AS5300 that you are replacing and then add the new Cisco AS5300 with the DMM. None of the configuration, monitoring, and reporting data associated with the old Cisco AS5300 will be deleted from the CAM database, and all existing reports for the stack that the old Cisco AS5300 belonged to will remain untouched until they are purged.
In the AccessPath-TS3, the 14th dial shelf for an Cisco AS5300 (shelf number 18 in the CAM GUI ) was displaced with an additional patch panel, due to a hardware configuration change to support AS5300Cisco AS5300 DMM. In the case of a stack with both DMM-based Cisco AS5300s and HMM-based Cisco AS5300s, shelf 14 will also be used for the patch panel. To reflect this change, the CAM GUI rearranges the Shelf Number list by placing number 18 (shelf 14) after 25 (shelf 21) if there is a new Cisco AS5300 DMM device in the stack. In the case of a fully loaded extended AccessPath AP-TS3 stack, the cable and addressing scheme for shelf 14 will be used for the 21st dial shelf.
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 5-1 in the Cisco Access Manager Software Installation and Configuration Guide) 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.
Table 3 Create Shelf or Modify Shelf Procedures
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 5-2 of the Cisco Access Manager Software Installation and Configuration Guide and the following table for instructions.)
Table 4
| 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 3 for complete instructions.)
To configure the addresses for the Cisco 2511:
To configure the addresses for the Cisco 3640:
To configure the addresses for the Cisco AS5200:
To configure the addresses for the Cisco AS5300:
To configure the addresses for the Cisco AS5300 with DMM:
To configure the addresses for the Cisco 7206:
To configure the addresses for the Catalyst 5002:
| Step | Description | |
|---|---|---|
| 1. | ||
| 2. | ||
| 3. | Continue with the next section, "Configure the Shelf Configuration Parameters"on page 5-12 of the Cisco Access Manager Software Installation and Configuration Guide |
|
|
Note The information in this section supplements or corrects information in Chapter 8, "Using Tools,"of the printed version of the Cisco Access Manager Software Installation and Configuration Guide. (The online versions of this document have already been updated.) |
Add the following sentence to the bottom of page 8-12 in the "Using the IOS Image Manager" section.
Add the following sentence to the bottom of page 8-30 in the "Using the Modem Firmware Image Manager" section:
|
Note The information in this section replaces the information in Appendix A, "Installing Oracle Software," of all versions of the Cisco Access Manager Software Installation and Configuration Guide (online as well as the printed book). |
This appendix gives detailed instructions for installing Oracle Enterprise Server software Version 8.0.5 on Solaris 2.6 to be used as the relational database management system (RDBMS) component of Cisco Access Manager (CAM) 4.0.
You must install Oracle before you install CSCOcamdb. Also, make sure you install Oracle on a file system with a minimum of 3.0 GB of free disk space (1 GB for the Oracle binaries and 2 GB for the CAM database).
This document only provides basic guidelines for installing Oracle for use with CAM. For a full description of Oracle installation, and to be sure you have the most recent documentation, refer to the documentation that came with your Oracle software or refer to the Oracle Corporation Web site at http://www.oracle.com .
The following topics are covered:
Before you can install Oracle 8.0.5, 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"
6. "Set the Oracle User Environment Variables"
7. "Reserve a Port for the SQL*Net Version 2 Listener"
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 file.
Step 2 Use a text editor (such as vi) to edit the /etc/system file, adding the following statements to the end of it:
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.
|
Note You must reboot your system after you have added these lines to the /etc/system file. Otherwise, the installation program will not be able to complete. |
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.6 does not require them.
Confirm the kernel parameter settings by entering the following command:
To install Oracle 8.0.5, the following Solaris 2.x packages must already be installed on the server:
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:
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 2 Start the Admintool by entering the following command:
Step 3 Choose Browse>Groups, and then Edit>Add.
Step 4 Under Group Name, enter dba. (The Group ID field will be automatically filled with a valid Group ID value.)
Step 5 Click OK.
To manually add the group dba:
Step 2 Check to make sure the 101 group ID (GID) is unassigned by using the grep command:
If you do not receive any output, you can use 101. If you receive output, 101 is in use and you must use a different number. Repeat this step using other group IDs until you find an available one.
Step 3 Using vi or another text edtior, append the following command to the /etc/group file:
This can also be done by entering the following command:
where GID is the group ID 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 2 If the Admintool is not already running, start the Admintool by entering the following command:
Step 3 Select Browse>Users.
Step 4 Select Edit>Add. The Admintool: Modify Users screen appears. (See Figure 5.)
Step 5 Fill out the form as follows:
where mntpoint is the mount point for the Oracle installation that you have determined has at least 3.0 GB of available disk space.
To create the Oracle user manually:
Step 2 Use vi or another text editor to add the following line to the /etc/passwd file:
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 3.0 GB of available disk space.
Step 3 Edit the /etc/shadow file. Append the following line:
Step 4 Create the Oracle user's home directory. Your home directory would be /mntpoint/oracle/product/8.0.5, 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:
where mntpoint is the mount point for the Oracle installation.
The chown command changes the owner of the Oracle directory to the user oracle. The chgrp command changes the group of the Oracle directory to dba.
Step 5 Set the Oracle user password. As the root user, enter the following command:
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:
To set environment variables for the Oracle user:
Step 2 Copy the .cshrc file in the oracle user's home directory to .cshrc.save.
Step 3 Using vi or another text editor, add the following statements to the .cshrc file in the oracle home directory.
|
Note Each setenv statement should be on only one logical line. Although line breaks might occur automatically based on the length of the line; you should not force line breaks by pressing Enter. |
|
Note If you are installing Oracle from an X Window System console, either OpenWindows or CDE, set the ORACLE_TERM variable to the name of the terminal that you will be using, for example vt100. |
where mntpoint is the mount point for the Oracle installation.
Step 4 Use the su command to change your user ID to oracle:
Step 5 Enter the source command to add the environment variables to your current environment:
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:
This completes the preinstallation procedure. Continue with the next section, "Installing the Oracle Server Software."
To install the Oracle Server software, follow the steps in this section.
|
Note The examples and screen captures in this procedure assume that you are not running the X Window System. However, some additional instructions for installations while using the X Window System are provided. |
Step 2 Insert the Oracle 8.0.5 CD-ROM into the system's local CD-ROM drive.
Step 3 Optionally, as the Oracle user, you can check the environment settings by entering the env command:
Step 4 Change directories to the Oracle installation directory on the CD-ROM:
Step 5 Enter the orainst command:
Select Default Install and press Enter.
Step 6 The Install Type screen appears (Figure 6).
Select Default Install, select OK, and press Enter.
Step 7 The Preamble Text screen opens (Figure 7).
Read the message, select OK, and press Enter.
Step 8 The Oracle README.FIRST file is displayed (Figure 8).
Read the file, select OK, and press Enter.
Step 9 The Installation Options screen appears (Figure 9).
Select the second option, Install New Product - Do Not Create DB Objects.
Step 10 The Environmental Variables screen appears (Figure 10).
Step 11 The Summary of Installation Options screen appears (Figure 11).
Check to make sure that all of the Oracle file locations are correct. If they are, select OK and press Enter.
Step 12 The Software Asset Manager screen appears (Figure 12).
Select the following components:
When all of the items listed above are marked for installation, press Enter or click Install.
|
Note Use the mouse (or the spacebar and the arrow keys, if you are not running the X Window System version of the Oracle installer orainst) to navigate and click on an item (or press Tab or Alt-i, if you are not running the X Window System version of orainst) to mark an item for installation. The instructions below assume you are not running the X Window System version of orainst. |
Step 13 The LSM Question screen appears (Figure 13).
Step 14 After 25 to 40 minutes, the Installer Actions Completed screen appears (Figure 14).
Step 15 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 "Post Oracle Installation Procedure."
Login as root user and run the root.sh script. Enter the following commands:
where mntpoint is the mount point for the Oracle installation.
|
Note You might see a message that says, "Please raise the Oracle owner's ulimit as per the IUG." You can ignore this message; it will not affect the usability of the Oracle account or CAM. |
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 enable automatic shut down and start up of the database. To acheive this, add the run-control script CSCOcam_oracle.example to the system and edit the Oracle file /var/opt/oracle/oratab as described below:
To add the run-control script:
Step 2 Enter the following commands:
To edit the /var/opt/oracle/oratab file:
Step 2 Find the entries for all the databases that you want to be started up and shut down automatically. They are identified by the sid in the first field.
Database entries in the oratab file appear in the following form:
where y or n specifies whether you want the database started and shut down 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.
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 installs and configures a database instance for CAM (either local or remote.) 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 installedon the machine on which the CAM server will be running. If the CAM server is the same as the Oracle server, the database is considered to be local. If CAM is installed on a separate machine, the database is considered to be remote.
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 2 Log in as the Oracle user.
Step 3 Edit the appropriate database creation scripts in the following directories:
Step 4 Run the APM_dbcreate.sh utility to create the CAMDB database.
|
Note In the file /opt/CSCOcamdb/Apm.sh, the environment variables
ORACLE_HOME, ORACLE_BASE, and ORACLE_SID must be set to match
your Oracle server configuration and your database instance name. The APM_dbcreate.sh utility will use the the following paths for storing admin and data files: $ORACLE_BASE/oradata/$ORACLE_SID $ORACLE_BASE/admin/$ORACLE_SID |
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 (without the Oracle binaries) 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 controls the location for admin and data files.
As with all databases, your 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 files are created in the directory pointed to by the environment variable $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 data files, you should edit these SQL scripts and specify the locations that are appropriate for your local environment.
In the directory /opt/CSCOcamdb/db/schema, the ApmTablesCom.sql and ApmTablesHist.sql scripts create all the tables and assign them to the appropriate tablespaces. You can edit these scripts to change the tablespace assignments.
The space for the CAM Database is distributed as follows:
The specified table and index sizes are estimates. The actual sizes and extents may be different.
Table 5 Tablespace Sizes for 100,000 Ports
Table 6 Default Historical Table and Index Sizes
| Object Name | MB |
|---|---|
Note that 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 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 variable CAM_DBPATH to $ORACLE_BASE/oradata/$ORACLE_SID
Step 3 Invoke sqlplus:
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:
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:
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.
The default datafile for the apm_data_ts tablespace is apm_data01.dbf. To change the size of the data01.dbf datafile to 1200M do the following:
To create a new 200MB datafile for the apm_index_ts tablespace:
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:
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:
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 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
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 an Oracle UNIX user and DBA group in the CAM server machine in the case of a remote database. You may directly install only Oracle SQL*Plus and SQL*Net software package using the same Oracle CD image used by the Oracle server machine.
The configuration file:/var/opt/oracle/oracle/tnsnames.ora must be configured and the 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 if /var/opt/oracle/oracle/tnsnames.ora is configured as CAMDB = (no domain name associated with tns name), refer to the example in the CSCOcamdb pacakge:
a. CSCOcamdb/reloc/db/admin/tnsnames.ora.example1 before installation
b. /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.)
The Oracle database and listener process automatically start up after system reboot. Usually, if you set up the UNIX system's /etc/rd2.d file for an automatic startup script and the /etc/rd0.d for an automatical shutdown script, the Oracle server will be shut down properly and stared automatically when the UNIX system reboots.
The CSCOcamdb package contains a script for your referece to set up the system so that the Oracle database and listener process will automatically shut down and start up at system reboot time. See CSCOcam/reloc/db/admin/CSCOcam_oracle.example before installation, or /opt/CSCOcam/db/admin/CSCOcam_oracle.example after installation.
The steps for enabling automatic startup and shutdown are as follows:
and make sure it can be executed by the root user.
Step 2 Setup the symblic links so that /etc/rc2.d/S80CSCOcam_oracle points to /etc/init.d/CSCOcam_oracle and /etc/rc0.d/K80CSCOcam_oracle points to /etc/init.d/CSCOcam_oracle.
The listener will take some minutes to start up after the system reboot. The script CSCOcam_oracle will automatically start all database instances which have a "Y" at the end of the listing in the file /var/opt/oracle/oratab.
To create a new database instance after the CSCOcamdb package is installed:
Step 2 Change your user ID to that of the Oracle user:
Step 3 Change directories to the CAM database admin directory:
Step 4 Run the add_dbinstance.sh utility, and answer all the questions:
A log file, /opt/CSCOcamdb/logfiles/add_dbinstance.log, will be created.
To remove a database instance before the CSCOcamdb package is removed:
Step 2 Change directories to the CAM database admin directory:
Step 3 Run the remove_dbinstance.sh utility, and answer all the questions:
A logfile, /opt/CSCOcamdb/logfiles/remove_dbinstance.log, will be created.
Prior to removing the CSCOcamdb package, you must remove all database instances created after the installation of the CSCOcamdb package.The process of removing CSCOcamdb package can only remove one database instance.
Review and understand the full instruction set for migration before starting the procedure.
At each step, please read the complete description for the step before performing the actions. Review the Oracle8 Migration manual provided by Oracle for additional information.
These instructions refer to both the Oracle 7 and Oracle 8 manuals provided by Oracle, so it is essential that you have access to them.
Step 2 Perform a full backup of the CAM database. See the Oracle7 Backup and Recovery manual.
Step 3 Install the Oracle 8 migration utility into the Oracle 7 environment. Refer to the section "Install the Version 8 Migration Utility" section in Chapter 3 of the Oracle Migration manual.
Step 4 Shut down your CAM database and the listener if you have one running on the database machine.
Step 5 As the Oracle user, run the following command:
This will perform space-use calculations without performing a migration. The SPOOL parameter will save the results of the check in the specified location. Review the result of the check. Resolve any problems that may be reported before proceeding.
Refer to your Oracle documentation or contact your Oracle support representative for help if necessary.
Step 6 Again, shut down your CAM database.
Step 7 Run the migration utility as follows:
Check the results after running the migration utility. See the Oracle8 Migration documentation from Oracle, Appendix A, "Migration Utility Messages," for more information. The utility creates a conversion file that contains the information of the version 7 control file. Later in the migration process, the conversion file is used to create a new control file in version 8. The default location for the conversion file is the $ORACLE_HOME/dbs directory. The name of the file is convCAMDB.dbf (where CAMDB is the SID of the CAM database—may be different in your installation if you did not use the default CAM database name).
Step 8 Install Oracle 8.0.5 using the version 8 Installation Utility provided by Oracle. Remove all environment variables that point to your Oracle 7 installation. Choose the "New installation, do not create database objects" when the Installation Utility asks you to select an option.
When the utility asks what products you want to install, select the following items:
Step 9 After installing Oracle 8, verify that the oracle user's environment variables (ORACLE_HOME, LD_LIBRARY_PATH, PATH, and ORACLE_PATH) point to your new Oracle 8 installation and not the old Oracle 7 version. Edit the oracle user's .cshrc or .profile files to make sure the Oracle environment variables are set to Oracle 8. Modify the ORACLE_HOME values in the files /var/opt/oracle/oratab and /var/opt/oracle/listener.ora to point to the new Oracle 8 installation.
Step 10 Copy the file initCAMDB.ora from your Oracle 7 installation to the directory $ORACLE_HOME/dbs in your new Oracle 8 location.
Step 11 Edit the initCAMDB.ora file to adjust configuration parameters for your new Oracle 8 installation, as follows:
Table 7 Configuration Parameters
| Configuration parameter in initCAMD.ora | Action |
|---|---|
If you made any changes to the initCAMDB.ora file created by the original CAM installation, you should make those adjustments to the appropriate init.ora parameters. Refer to Appendix C, "INIT.ORA Changes" in the Oracle document Oracle8 Migration.
Step 12 Rename the Oracle 7 CAMDB control files. In the CAMDB database directory, enter the following :
(The exact location of the control files is specified in first few lines of the initCAMDB.ora file)
Later in the migration process you will create new Oracle8 control files for CAMDB.
Step 13 Copy the convCAMDB.dbf conversion file from the Oracle7 dbs directory into the Oracle 8 dbs directory. From the Oracle 7 dbs directory, run the following command:
Step 14 Refer to the instructions in the section "Migration Steps in the Version 8 Environment" of Chapter 3 in the Oracle document Oracle8 Migration. By now, you will have already performed the migration manual's steps 1 through 9.
Follow the instructions for steps 10 through 21 in the Oracle8 Migration manual.
For step 16 you must first go the directory in which the catalog script resides. Therefore, before executing the CAT8000.sql script, go to the $ORACLE_HOME/rdbms/admin directory.You may skip steps 17 and 18 in the Oracle document, unless Oracle's Advanced Replication and Parallel Server has been installed.
You must start the database prior to performing Oracle's step 21. The command for the full table scan of the CAMDB database is as follows:
Make sure you run this command as the oracle user, and with the environment set up for Oracle8.
If you have interupted the upgrade process to migrate the database, you can return to the upgrade process. See "Mount the CD-ROM" to continue.
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.
|
Note If you are a network administrator and need personal technical assistance with a Cisco product that is under warranty or covered by a maintenance contract, contact Cisco's Technical Assistance Center (TAC) at 800 553-2447, 408 526-7209, or tac@cisco.com. To obtain general information about Cisco Systems, Cisco products, or upgrades, contact 800 553-6387, 408 526-7208, or cs-rep@cisco.com. |
This document is to be used in conjunction with the documents listed in the section "Chapter 1 Updates".
Access Registrar, AccessPath, Any to Any, AtmDirector, Browse with Me, CCDA, CCDE, CCDP, CCIE, CCNA, CCNP, CCSI, CD-PAC, the Cisco logo, Cisco Certified Internetwork Expert logo, CiscoLink, the Cisco Management Connection logo, the Cisco NetWorks logo, the Cisco Powered Network logo, Cisco Systems Capital, the Cisco Systems Capital logo, Cisco Systems Networking Academy, the Cisco Systems Networking Academy logo, the Cisco Technologies logo, ConnectWay, Fast Step, FireRunner, Follow Me Browsing, FormShare, GigaStack, IGX, Intelligence in the Optical Core, Internet Quotient, IP/VC, Kernel Proxy, MGX, MultiPath Data, MultiPath Voice, Natural Network Viewer, NetSonar, Network Registrar, the Networkers logo, Packet, PIX, Point and Click Internetworking, Policy Builder, Precept, ScriptShare, Secure Script, ServiceWay, Shop with Me, SlideCast, SMARTnet, SVX, The Cell, TrafficDirector, TransPath, ViewRunner, Virtual Loop Carrier System, Virtual Service Node, Virtual Voice Line, VisionWay, VlanDirector, Voice LAN, WaRP, Wavelength Router, Wavelength Router Protocol, WebViewer, Workgroup Director, and Workgroup Stack are trademarks; Changing the Way We Work, Live, Play, and Learn, Empowering the Internet Generation, The Internet Economy, and The New Internet Economy are service marks; and ASIST, BPX, Catalyst, Cisco, Cisco IOS, the Cisco IOS logo, Cisco Systems, the Cisco Systems logo, the Cisco Systems Cisco Press logo, Enterprise/Solver, EtherChannel, EtherSwitch, FastHub, FastLink, FastPAD, FastSwitch, GeoTel, IOS, IP/TV, IPX, LightStream, LightSwitch, MICA, NetRanger, Post-Routing, Pre-Routing, Registrar, StrataView Plus, Stratm, TeleRouter, and VCO are registered trademarks of Cisco Systems, Inc. or its affiliates in the U.S. and certain other countries. All other trademarks mentioned in this document are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any of its resellers. (9912R)
Copyright ©1998, 1999, 2000, Cisco Systems, Inc.
All rights reserved.
Posted: Tue Jan 21 00:58:38 PST 2003
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.
