|
|
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:
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.)
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:
| 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:
| 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 |
If you are experiencing problems with your AccessPath system, you should check the data in the APM Alarms and Traps screen.
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.)
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.)
The information displayed in the Tablespace Usage screen is as follows:
| 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: |
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, useful in troubleshooting APM, include:
| Types | File Names1 | Content |
|---|---|---|
UNIX cron jobs. | ||
$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. | |
Traps that come to the APM workstation from the AccessPath shelves being configured. | ||
Log of the Netscape FastTrack Admin Server and web server installation. | ||
Output of the script that invokes the poller, rollup, and purging activities | ||
Detailed output of poller activity. (The default setting is for this log to minimize details.) | ||
Database rollup and purge activity. | ||
Detailed output of activity on scheduled reports, including information such as whether a report ran and e-mailed without errors. | ||
The most recently completed daily scheduled reports. | ||
APM configuration | Stack and shelf configuration logs, containing the output of the session during which APM connected to the shelf and downloaded Cisco IOS commands. |
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:
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:
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.
Step 6 Enter the following commands:
Step 7 Start HP OpenView:
To facilitate starting up the APM Oracle database, use 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 /export/home0/app/oracle/product/7.3.3/bin/dbstart
echo ""
exit 0
|
|