This chapter presents some scripts and procedures that might prove useful in troubleshooting and maintaining your Cisco AccessPath Manager (APM) software. Sections include:
If APM is not functioning correctly just after installation, you can determine if the APM package has been installed, by entering one of the following commands:
For local APM executable and database installations (CSCOapm):
% pkginfo -l CSCOapm
For remote APM Oracle database installations (CSCOapmdb):
% pkginfo -l CSCOapmdb
System Status
To view APM system status:
Step 1 Click APM System.
Step 2 Click System Status.
Step 3 Click Execute. The System Status screen appears. (See Figure 8-1.)
Figure 8-1 System Status Screen
Step 4 (Optional.) Click Refresh to update the display.
Step 5 (Optional.) Double-click on any entry in the System Status dialog to view detailed information on its current status.
This panel provides a summary of APM system status. The information displayed in the APM System Status screen is as follows:
Table 8-1 APM System Status Fields
Field
Description
Process Name
Name of the process
Status
Status of this process
PID
UNIX system's process ID for this process
Description
Description of this process
For example, if you are running HP OpenView, your first three processes should always be the following:
Table 8-2 HP OpenView Standard Processes
Process Name
Status
Process ID (PID)
Description
OVsPMD
UP
UNIX system-derived value
HP OpenView Process Management Daemon
ovtrapd
UP
UNIX system-derived value
Receives and buffers SNMP traps
APMovRecTraps
UP
UNIX system-derived value
Logs SNMP traps from Cisco devices
Alarms and Traps
If you are experiencing problems with your AccessPath system, you should check the data in the APM Alarms and Traps screen.
Note The Alarms and Traps screen displays Simple Network Management Protocol
(SNMP) traps received from Cisco devices. Looking at the original SNMP messages might
help you diagnose system problems. Note that no filtering of the SNMP data is done by
stack or shelf.
The application APMovRecTraps must be running for Alarms and Traps to work. See Appendix B, "HP OpenView Integration," for additional information about the APMoveRecTraps application and other HP OpenView integration issues.
To view Alarms and Traps:
Step 1 Click APM System.
Step 2 Click Alarms and Traps.
Step 3 Click Execute. The Alarms and Traps screen appears. (See Figure 8-2.)
Figure 8-2 Alarms and Traps Screen
Tablespace Usage
It is critical that you have enough APM Oracle database tablespace for your network. Periodically, you should monitor your tablespace usage with the Tablespace Usage screen.
Tablespace usage information will be of most use to your Oracle Database Administrator. APM provides this information to help you manage your Oracle database, but most of your Oracle management will be done using your Oracle database tools.
Please see your Oracle documentation or Oracle's web site (http://www.oracle.com/) for additional clarification on any Oracle-specific terms such as tablespace, datafile, and rollback segment.
To view tablespace usage information for the APM Oracle database:
Step 1 Click APM System.
Step 2 Click Tablespace.
Step 3 Click Execute. The Tablespace Usage screen appears. (See Figure 8-3.)
Figure 8-3 Tablespace Usage Screen
The information displayed in the Tablespace Usage screen is as follows:
Table 8-3 Tablespace Usage Data
Field
Description
Tablespace
Name of the tablespace.
DATA_TS
Largest tablespace by far, DATA_TS contains APM data such as polled devices, lists of stacks and shelves, and historical data.
INDEX_TS
Index tablespace, used to increase the performance of queries into the DATA_TS tablespace.
RBS_TS
Tablespace for rollback segments.
SYSTEM
Automatically created by Oracle, this tablespace contains the data dictionary tables for the entire database.
TEMP_TS
Tablespace used only for sort segments. No permanent objects reside in a temporary tablespace.
USER_TS
Tablespace for users of the APM database.
File ID
Unique file descriptor assigned by Oracle. The file_id differentiates the rows in case the Oracle Database Administrator decides to create more than one datafile for a tablespace.
Total (MB)
Amount of diskspace (in MB) available to this tablespace.
Used (MB)
Amount of diskspace (in MB) that this resource is currently using.
Free (MB)
Amount of diskspace (in MB) that remains for this tablespace.
%Used
Percentage of the diskspace that remains for this tablespace:
(Used * 100)
%Used = ---------------
Total
APM, Netscape FastTrack, and Oracle Shutdown Script
When shutting down your system, use the following script to ensure that APM, the Netscape FastTrack Admin Server, and Oracle are terminated in an orderly fashion:
#!/usr/bin/sh # # Copyright (c) 1996, by Cisco Systems, Inc. # All Rights Reserved # # Description: This script shuts down the Cisco AccessPath Manager # Netscape FastTrack and Oracle database, locally installed, before # the Solaris system shut downs. # BASE=/opt/CSCOapm # NAME=apm_server_name # # Stop Fast Track Admin program and Fast Track Server # echo "Shutting down Cisco Access Path Manager FastTrack web server... \c" /$BASE/ns-home/httpd-$NAME/stop >$BASE/etc/log/apm_shutdown.log 2>&1 /$BASE/ns-home/stop-admin >>$BASE/etc/log/apm_shutdown.log 2>&1 # # stop DB server # # echo "Shutting down Cisco Access Path Manager Oracle Database Server... \c" su - oracle -c /$BASE/oracle/admin/database_stop.sh exit 0
Log Files
Log files, useful in troubleshooting APM, include:
Table 8-4 APM Log Files
Types
File Names1
Content
UNIX
/var/cron/log
UNIX cron jobs.
APM Oracle database
$APM_DBPATH2/sql/output/database_install.log
Created during CSCOapm and CSCOapmdb installation.
$APM_DBPATH/sql/output/schema_update.log
Created during CSCOapm and CSCOapmdb installation upgrades. Contains the log of any update operation that is performed on the APM database.
$APM_DBPATH/sql/output/database_status.log
Latest status of the Oracle database.
HP OpenView
APMtrap.log
Traps that come to the APM workstation from the AccessPath shelves being configured.
Netscape
ns_install.log
Log of the Netscape FastTrack Admin Server and web server installation.
APM database polling and rollups
CSCOapm.poll.log
Output of the script that invokes the poller, rollup, and purging activities
poller.log
Detailed output of poller activity. (The default setting is for this log to minimize details.)
CSCOapm.rollup.log
Database rollup and purge activity.
APM reports
CSCOapm.report.log
Detailed output of activity on scheduled reports, including information such as whether a report ran and e-mailed without errors.
CSCOapm.report.ran
The most recently completed daily scheduled reports.
APM configuration
logStackAdd.pid3
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
shelf4-con.log
Stack and shelf configuration logs, containing the output of the session during which APM connected to the shelf and downloaded Cisco IOS commands.
1Unless otherwise indicated, these log files are located in the /opt/CSCOapm/etc/log directory.
2$APM_DBPATH = The path of your APM 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.
3pid = Process ID, the unique identifier for a UNIX process.
If you change the IP address of the APM server, you need to modify the APM environment file as follows:
Step 1 Log in as the APMadmin user.
Step 2 Edit the /opt/CSCOapm/www/cgi-bin/env file. Change WS_IP=x.x.x.x to reflect the new IP address of the APM workstation.
Step 3 Edit the /opt/CSCOapm/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 Make sure there are no spaces after your IP address in the ns-admin.conf
file.
If you are using HP OpenView, refer to your HP OpenView documentation and reconfigure HP OpenView as follows:
Step 4 Log in as root and enter the following commands:
# /opt/OV/bin/ovstop # cd /etc/opt/OV/share/conf
Step 5 Edit the files ovw.auth and ovwdb.auth, adding the new IP address of your system to the end of both of them.
