Troubleshooting. Troubleshooting the CAM Installation CHAPTER

Transcription

1 CHAPTER 9 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: Troubleshooting the CAM Installation section on page 9-1 Log Files section on page 9-2 Changing the IP Address of the CAM Server section on page 9-4 CAM Oracle Database Startup Script section on page 9-5 Handling Large Files in CAM section on page 9-5 Troubleshooting 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): % pkginfo -l CSCOcam % pkginfo -l CSCOcamdb For remote CAM Oracle database installations (CSCOcam and CSCOcamdb on different machines): % pkginfo -l CSCOcam (On CAM Server machine) % pkginfo -l CSCOcamdb (On Oracle Server machine) Troubleshooting 9-1

2 Log Files 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 1 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 2 /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 Scheduler log files CSCOcam.poll.log ApmCronPoller.log ApmPoller.log ApmCronPoller5800.log ApmPoller5800.log ApmPollerFTP.log CSCOcam.rollup.log ApmCron.log ApmCronIn.log ApmCronReport.log Output of the script that invokes the poller, rollup, and purging activities. Log of Cisco AccessPath system poller activity. Log of Cisco AccessPath system poller activity. Log of System Controller poller activity. Log of System Controller poller activity. Log for FTP of files from System Controller. Database rollup and purge activity. Log of all user scheduled jobs. Log of all internal tasks. Log of all scheduled reports. 9-2 Cisco Access Manager Software Installation and Configuration Guide

3 Log Files Table 9-1 Log Files in CAM (Continued) Types File Names 1 Content CAM reports CSCOcam.report.log Detailed output of activity on scheduled reports, including information such as whether a report ran and ed without errors. CSCOcam.report.ran The most recently completed daily scheduled reports. CAM configuration logstackadd.pid 3 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 4 -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. 1 Unless otherwise indicated, these log files are located in the /opt/cscocam/etc/log directory. 2 $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. 3 pid = Process ID, the unique identifier for a UNIX process. 4 shelf = The name of the Cisco AccessPath system shelf. Troubleshooting 9-3

4 Changing the IP Address of the CAM Server 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 Step 3 Change the IP address of the CAM Server on the UNIX machine. Run the APM Data shell program: cd /opt/cscocam/db/schema./apmdata.sh db_user_id db_user_password Step 4 where db_user_id and db_user_password are your database id and password. 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 file. Make sure there are no spaces after your IP address in the ns-admin.conf 9-4 Cisco Access Manager Software Installation and Configuration Guide

5 CAM Oracle Database Startup Script 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 Step 2 Step 3 Telnet to the CAM server running on the UNIX machine. Use an editor, such as vi or emacs, to edit the configuration or template file that is in the /tmp directory. (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 Do not disconnect from the CAM server at this time. Troubleshooting 9-5

6 Handling Large Files in CAM Step 4 Step 5 Step 6 Import the newly modified configuration or template file from CAM server. 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. Disconnect from the CAM server. 9-6 Cisco Access Manager Software Installation and Configuration Guide