Troubleshooting

This chapter presents some scripts and procedures that might prove useful in troubleshooting and maintaining your Cisco Access Manager (CAM) software. The following topics are covered:

Troublesho oting the CAM Installation

If CAM is not functioning correctly just after installation, you can determine if the CAM package has been installed, by entering one of the following commands:

For local CAM executable and database installations (CSCOcam and CSCOcamdb on same machine):
For remote CAM Oracle database installations (CSCOcam and CSCOcamdb on different machines):

Log Files

Table 9-1 lists the log files that can be useful in troubleshooting CAM.

Table 9-1: Log Files in CAM
Types File Names¹ Content

UNIX

/var/cron/log

UNIX cron jobs.

CAM log file

CAM.log

Overall log files for all the User Interface transactions to the CAM server. CAM is the name specified in the apm.ini file.

CAM Oracle database

$CAM_DBPATH ²/sql/output/database_install.log

Created during CSCOcam and CSCOcamdb installation.

$CAM_DBPATH/sql/output/schema_update.log

Created during CSCOcam and CSCOcamdb installation upgrades. Contains the log of any update operation that is performed on the CAM database.

$CAM_DBPATH/sql/output/database_status.log

Latest status of the Oracle database.

Netscape

ns_install.log

Log of the Netscape FastTrack Admin Server and Web server installation.

CAM database polling and rollups

CSCOcam.poll.log

Output of the script that invokes the poller, rollup, and purging activities.

ApmCronPoller.log

Log of Cisco AccessPath system poller activity.

ApmPoller.log

Log of Cisco AccessPath system poller activity.

ApmCronPoller5800.log

Log of System Controller poller activity.

ApmPoller5800.log

Log of System Controller poller activity.

ApmPollerFTP.log

Log for FTP of files from System Controller.

CSCOcam.rollup.log

Database rollup and purge activity.

Scheduler log files

ApmCron.log

Log of all user scheduled jobs.

ApmCronIn.log

Log of all internal tasks.

ApmCronReport.log

Log of all scheduled reports.

CAM reports

CSCOcam.report.log

Detailed output of activity on scheduled reports, including information such as whether a report ran and e-mailed without errors.

CSCOcam.report.ran

The most recently completed daily scheduled reports.

CAM configuration

logStackAdd.pid³

logStackModify.pid

logStackModify.pid.exelog

logStackDelete.pid

logStackDelete.pid.exelog

logShelfAdd.pid

logShelfAdd.pid.exelog

logShelfModify.pid

logShelfModify.pid.exelog

logShelfDelete.pid

logShelfDelete.pid.exelog

logShelfRestore.pid

logShelfRestore.pid.exelog

shelf ⁴-con.log

Stack and shelf configuration logs containing the output of the session during which CAM connected to the shelf and downloaded Cisco IOS commands.

¹Unless otherwise indicated, these log files are located in the /opt/CSCOcam/etc/log directory.
²$CAM_DBPATH = The path of your CAM Oracle database. This variable is set during the Oracle installation. To find out the value of this variable, log in as the Oracle user and enter the env command.
³pid = Process ID, the unique identifier for a UNIX process.
⁴shelf = The name of the Cisco AccessPath system shelf.

Table 9-1: **Log Files in CAM**
Types	File Names¹	Content
UNIX	/var/cron/log	UNIX cron jobs.
CAM log file	CAM.log	Overall log files for all the User Interface transactions to the CAM server. CAM is the name specified in the apm.ini file.
CAM Oracle database	$CAM_DBPATH ²/sql/output/database_install.log	Created during CSCOcam and CSCOcamdb installation.
$CAM_DBPATH/sql/output/schema_update.log	Created during CSCOcam and CSCOcamdb installation upgrades. Contains the log of any update operation that is performed on the CAM database.
$CAM_DBPATH/sql/output/database_status.log	Latest status of the Oracle database.
Netscape	ns_install.log	Log of the Netscape FastTrack Admin Server and Web server installation.
CAM database polling and rollups	CSCOcam.poll.log	Output of the script that invokes the poller, rollup, and purging activities.
ApmCronPoller.log	Log of Cisco AccessPath system poller activity.
ApmPoller.log	Log of Cisco AccessPath system poller activity.
ApmCronPoller5800.log	Log of System Controller poller activity.
ApmPoller5800.log	Log of System Controller poller activity.
ApmPollerFTP.log	Log for FTP of files from System Controller.
CSCOcam.rollup.log	Database rollup and purge activity.
Scheduler log files	ApmCron.log	Log of all user scheduled jobs.
ApmCronIn.log	Log of all internal tasks.
ApmCronReport.log	Log of all scheduled reports.
CAM reports	CSCOcam.report.log	Detailed output of activity on scheduled reports, including information such as whether a report ran and e-mailed without errors.
CSCOcam.report.ran	The most recently completed daily scheduled reports.
CAM configuration	logStackAdd.pid³ logStackModify.pid logStackModify.pid.exelog logStackDelete.pid logStackDelete.pid.exelog logShelfAdd.pid logShelfAdd.pid.exelog logShelfModify.pid logShelfModify.pid.exelog logShelfDelete.pid logShelfDelete.pid.exelog logShelfRestore.pid logShelfRestore.pid.exelog shelf ⁴-con.log	Stack and shelf configuration logs containing the output of the session during which CAM connected to the shelf and downloaded Cisco IOS commands.

Changing the IP Address of the CAM Server

If you need to change the IP address of the CAM server, you need to:

Step 1 Log in as the CAMadmin user root and shut down the CAM daemons such as poller and cron:

cd /opt/CSCOcam/admin

su

./CAM_shutdown

Step 2 Change the IP address of the CAM Server on the UNIX machine.

Step 3 Run the APM Data shell program:

cd /opt/CSCOcam/db/schema

./ApmData.sh db_user_id db_user_password

where db_user_id and db_user_password are your database id and password.

Step 4 Start the CAM daemons such as poller and cron:

cd /opt/CSCOcam/admin

./CAM_startup

Step 5 Edit the /opt/CSCOcam/ns-home/admserv/ns-admin.conf file and restart the Netscape FastTrack Admin Server. For multiple addresses, use this format:

(A.B.C.D|x.x.x.x)

Note

CAM Oracle Database Startup Script

To start up the CAM Oracle database, run the following script:

#!/bin/sh

# Copyright (c) 1996, by Cisco Systems, Inc.

# All Rights Reserved

#

# Start Oracle Server 

#

echo "Cisco Access Path Manager Oracle Database Server starting...  \c"

su - oracle -c $ORACLE_HOME/bin/dbstart

echo ""

exit 0

Handling Large Files in CAM

Configuration files and template files larger than 28K cannot be edited or saved using CAM. If you try to edit or save a configuration or template file larger than 29K, one of the following error messages is returned:

"my_temp too large. Please edit `/tmp/my_temp' on CAM server then import it again"
"my_cfg too large. Please edit `/tmp/my_cfg.xxx' on CAM server then import it again"

: where xxx is shelf state ID number of the listed configuration file.

To edit and save a configuration or template file that is larger than 28K:

Step 1 Telnet to the CAM server running on the UNIX machine.

Step 2 Use an editor, such as vi or emacs, to edit the configuration or template file that is in the /tmp directory.

Step 3 (Optional.) Rename the configuration or template file. The filename used on the server for this file will be used by the CAM Configuration Manager and Template Manager. However, to use the same name in the Configuration manager or Template manager, you must delete it from the CAM GUI first.

Note

Step 4 Import the newly modified configuration or template file from CAM server.

Step 5 Remove your file from /tmp directory after you have completed the import and no longer need the file. The import function in CAM will not delete the file from the CAM server.

Step 6 Disconnect from the CAM server.

Table of Contents