Cisco Resource Policy Management System 2.0.1 Troubleshooting Guide
Chapter 1: Cisco RPMS 2.0.1 System and Solution Troubleshooting
Downloads: This chapterpdf (PDF - 180.0KB) The complete bookPDF (PDF - 1.22MB) | Feedback

Cisco RPMS 2.0.1 System and Solution Troubleshooting

Table Of Contents

Cisco RPMS 2.0.1 System and Solution Troubleshooting

Overview: Troubleshooting

Overview: Basic System Information

Verifying the Operating System Release

Verifying the Solaris Patches

Verifying the Oracle Database Release

Verifying the Cisco RPMS Release

Overview: Basic System Status

Checking the Oracle Database Connectivity

Checking the Oracle Database Connectivity, Example 1

Checking the Oracle Database Connectivity, Example 2

Verifying that the TNS Listener is Running

Verifying that All Cisco RPMS Processes are Running

Sample output of "showrpms"


Cisco RPMS 2.0.1 System and Solution Troubleshooting


Topics in this chapter include:

Overview: Troubleshooting

Overview: Basic System Information

Verifying the Operating System Release

Verifying the Solaris Patches

Verifying the Oracle Database Release

Verifying the Cisco RPMS Release

Overview: Basic System Status

Checking the Oracle Database Connectivity

Verifying that the TNS Listener is Running

Verifying that All Cisco RPMS Processes are Running

Overview: Troubleshooting

This guide describes issues you may encounter while using the Cisco Resource Policy Management System (Cisco RPMS) software, and how best to solve them.


Note With Release 2.0, Cisco Resource Pool Manager Server is now referred to as Cisco Resource Policy Management System to emphasize its increased functionality.


Topics in this guide include:

Cisco RPMS internal software architecture

Basic system status

What to do if the basic system is not working

Cisco RPMS system start and stop procedures

Cisco RPMS debugging

Universal gateway IOS debugging

Sample call traces

Common problems and workarounds

The guide should be used as a troubleshooting guide, but is not intended as an exhaustive solutions guide. If you need technical assistance with the Cisco RPMS system, see the "Obtaining Technical Assistance" section on page -xiii for information on contacting the Cisco TAC Center.

For more information on Cisco RPMS, refer to the Cisco Resource Policy Management System 2.0 Installation Guide, and the Cisco Resource Policy Management System 2.0.1 Configuration and Solutions Guides.

Overview: Basic System Information

This section describes the basic system information for Cisco RPMS 2.0.1. To ensure that Cisco RPMS operates correctly, you must ensure that the correct operating system, Solaris patches, Cisco RPMS and Oracle database versions are installed. This section describes how to verify the versions for each component.

For more information on the system requirements, refer to Chapter 1, "Installation Requirements" in the Cisco Resource Policy Management System 2.0 Installation Guide.

Verifying the Operating System Release

For more information on the Sun Solaris operating system requirements, refer to the "Overview: Software Requirements" section on page 1-2 in the Cisco Resource Policy Management System 2.0 Installation Guide.

The following example displays a Solaris operating system version:

host# uname -a
SunOS <hostname> 5.6 Generic_105181-23 sun4u sparc SUNW,<hardware>

Note The number in italics indicates the Solaris version used; in this example, that is Solaris version 2.6.


Verifying the Solaris Patches

Cisco RPMS 2.0.1 has been verified to work with Solaris 2.6, 2.7 and 2.8 in combination with concomitant Oracle 8.x and Web Browsers. Patches necessary for Solaris 2.6 and 2.7 are as follows; as yet, there are no special patches for Solaris 2.8. For more informations on Solaris patch requirements, refer to the "Required Solaris Patches" section on page 1-2 in the Cisco Resource Policy Management System 2.0 Installation Guide.

The following example displays the Solaris patches that are currently installed:


host# showrev -p
Patch: 105642-02 Obsoletes:  Requires:  Incompatibles:  Packages: 
SUNWkvmPatch: 105181-23 Obsoletes: 105214-01, 105636-01, 105776-01, 
106031-02, 106308-01, 106048-07, 105222-03, 105604-09, 109415-01 
Requires:  Incompatibles:  Packages: SUNWkvm, SUNWcsu, SUNWcsr, 
SUNWcar, SUNWheaPatch: 105642-08 Obsoletes:  Requires:  Incompatibles:  
Packages: SUNWkvmPatch: 105757-01 Obsoletes:  Requires:  
Incompatibles:  Packages: SUNWcsuPatch: 105755-03 Obsoletes:  
Requires:  Incompatibles:  Packages: SUNWcsuPatch: 105746-01 
Obsoletes:  Requires:  Incompatibles:  Packages: SUNWcsu 

Note The patches in italics indicate the Solaris patches installed. You may also see information about whether the patches are obsolete, if they require other patches to be installed, and patches with which they may be incompatible.


Verifying the Oracle Database Release

Cisco RPMS uses an Oracle database to store and retrieve system data. Cisco recommends installing the Oracle database on a machine separate from the Cisco RPMS server. For more information on Oracle database requirements, refer to the "Oracle Database Requirements" section on page 1-3 in the Cisco Resource Policy Management System 2.1 Installation Guide.

The following example displays the Oracle database release that is installed:

host# rlogin localhost -l oracle
host# cd <Oracle_home_dir>
host# bin/svrmgrl
Oracle Server Manager Release 3.0.5.0.0 - Production
(c) Copyright 1997, Oracle Corporation.  All Rights Reserved.
Oracle8 Enterprise Edition Release 8.0.5.0.0 - Production
PL/SQL Release 8.0.5.0.0 - Production
SVRMGR> quit

Note The Oracle8 Enterprise Edition Release 8.0.5.0.0 in italics indicates that Oracle release installed.


Verifying the Cisco RPMS Release

The following example displays the Cisco RPMS release that is installed:

host# <RPMS_home_dir>/sbin/crpms-info

VERSION:2.0.1
NAME:Cisco Resource Policy Management System
VENDOR:Cisco Systems, Inc.
INSTALLED DATE:Mon Nov 12 14:13:58 PST 2001
INSTALLED DIR:/export/home/crpms
EMAIL:cs-rpms@cisco.com
CONFIGURATION:
CRPMS System Admin User:root
Database:Oracle 8.0.x

Components and Port Information
                DBServer Port:8800
                RMI Port:1099
                Acme Port:9095

RPMS component is installed

PROXY component is installed
                RADIUS Authorization Port:1812
                RADIUS Accounting Port:1813

Note The VERSION 2.0.1 in italics indicates that Cisco RPMS release 2.0.1 is installed.


Overview: Basic System Status

This section describes the processes used by Cisco RPMS 2.0.1. It describes the commands you need to verify that these processes are running correctly, and displays specific examples of those commands.

Checking the Oracle Database Connectivity

If you experience problems with the Oracle database, ensure that it is connected, and communicating with Cisco RPMS by using the following commands:

rlogin localhost -l oracle

cd <Oracle_home_dir>/bin

./tnsping <TNS_name>

./sqlplus rpmsuser/<password>@<TNS_name>


Note You can use either the TNS Ping utility to check the connectivity, or the SQL*Plus utility. Use only one command (./tnsping <TNS_name> or ./sqlplus rpmsuser/<password>@<TNS_name>) to check.


Checking the Oracle Database Connectivity, Example 1

This example shows how to verify the Oracle database connectivity by using the TNS Ping utility.

rlogin localhost -l oracle
cd <Oracle_home_dir>/bin
./tnsping <TNS_name>
TNS Ping Utility for Solaris: Version 8.0.5.0.0 - Production on 
12-JUL-01 16:23:02 
(c) Copyright 1997 Oracle Corporation.  All rights reserved.
Attempting to contact 
(ADDRESS=(PROTOCOL=TCP)(Host=epicurus)(Port=1521))
OK (10 msec)


Note In this example, the OK (10 msec) in italics tells you that the Oracle database is connected.


Checking the Oracle Database Connectivity, Example 2

This example shows how to verify the Oracle database connectivity by using the SQL*Plus utility.

./sqlplus rpmsuser/<password>@<TNS_name> 

SQL*Plus: Release 8.0.5.0.0 - Production on Thu Jul 12 16:25:31 2001
(c) Copyright 1998 Oracle Corporation.  All rights reserved.

Connected to:
Oracle8 Enterprise Edition Release 8.0.5.0.0 - Production
PL/SQL Release 8.0.5.0.0 - Production

SQL> quit


Note In this example, the
Connected to: Oracle8 Enterprise Edition Release 8.0.5.0.0 - Production
PL/SQL Release 8.0.5.0.0 - Production in italics tells you that the Oracle database is connected.


Verifying that the TNS Listener is Running

The TNS Listener is a service bundled with the Oracle database, and allows applications like Cisco RPMS to remotely communicate with the database by using TNS. The Oracle server can contain many database instances, each identified by its SID. A TNS entry acts an identifier for a database on separate host.

The TNS Listener sits between the Oracle database and the Cisco RPMS application. In order for the Cisco RPMS installation to succeed, the TNS Listener must be correctly defined and running.

You can verify that the TNS Listener is running by using the command:

./lsnrctl status

Here is an example using the command to check the TNS Listener status:

./lsnrctl status
LSNRCTL for Solaris: Version 8.0.5.0.0 - Production on 22-JUL-01 
17:43:30

(c) Copyright 1997 Oracle Corporation.  All rights reserved.

Connecting to (ADDRESS=(PROTOCOL=IPC)(KEY=epicurus))
STATUS of the LISTENER
------------------------
Alias                     LISTENER
Version                   TNSLSNR for Solaris: Version 8.0.5.0.0 - 
Production
Start Date                22-JUL-01 17:30:49
Uptime                    0 days 0 hr. 12 min. 41 sec
Trace Level               off
Security                  OFF
SNMP                      OFF
Listener Parameter File   
/opt/app/oracle/product/8.0.5/network/admin/listener.o
ra
Listener Log File         
/opt/app/oracle/product/8.0.5/network/log/listener.log
Services Summary...
  epicurus              has 1 service handler(s)
  extproc               has 1 service handler(s)
The command completed successfully

Verifying that All Cisco RPMS Processes are Running

To verify that all Cisco RPMS processes are running, use the command:


RPMS_home_dir>/bin/showrpms

Once you have run the command, ensure that there is a sub-entry for each software process, including the:

Oracle Database Server


Note This will not display if Oracle is running on different server.


FastTrack Server

Cisco RPMS Server

Cisco RPMS DBServer

Cisco RPMS Acme Servlets

Sample output of "showrpms"

Oracle Database Server:
oracle   411     1  0 10:11:31 ?        0:00 
/opt/oracle/product/8.0.5/bin/tns
lsnr LISTENER -inherit
  oracle   397     1  0 10:11:06 ?        0:00 ora_pmon_rpms
  oracle   399     1  0 10:11:06 ?        0:00 ora_dbw0_rpms
  oracle   401     1  0 10:11:06 ?        0:00 ora_lgwr_rpms
  oracle   403     1  0 10:11:06 ?        0:00 ora_ckpt_rpms
  oracle   405     1  0 10:11:06 ?        0:00 ora_smon_rpms
  oracle   407     1  0 10:11:06 ?        0:00 ora_reco_rpms

Note There are no listings under `Oracle Database Server' if the Oracle database is running on different server.


RPMS Acme Servlets:
     UID   PID  PPID  C    STIME TTY      TIME CMD
    root   668   657  0 10:12:22 pts/2    0:03 
/export/home/crpms/java/bin/sparc
/native_threads/jre -ms16m -mx64m -Drpms.based
FastTrack Server:
     UID   PID  PPID  C    STIME TTY      TIME CMD
  nobody   730   727  0 10:13:23 ?        0:00 ./ns-httpd -d 
/export/home/crpms/
ns-home/httpd-lipizzan-33.cisco.com/config
  nobody   728   727  0 10:13:23 ?        0:00 ./ns-httpd -d 
/export/home/crpms/
ns-home/httpd-lipizzan-33.cisco.com/config
    root   707   705  0 10:12:23 ?        0:00 
/export/home/crpms/ns-home/admser
v/ns-admin -d /export/home/crpms/ns-home/admse
  nobody   731   727  0 10:13:23 ?        0:00 ./ns-httpd -d 
/export/home/crpms/
ns-home/httpd-lipizzan-33.cisco.com/config
    root   705     1  0 10:12:23 ?        0:00 
/export/home/crpms/ns-home/admser
v/ns-admin -d /export/home/crpms/ns-home/admse
  nobody   729   727  0 10:13:23 ?        0:00 ./ns-httpd -d 
/export/home/crpms/
ns-home/httpd-lipizzan-33.cisco.com/config
  nobody   727     1  0 10:13:23 ?        0:00 ./ns-httpd -d 
/export/home/crpms/
ns-home/httpd-lipizzan-33.cisco.com/config
 
RPMS DBServer:
     UID   PID  PPID  C    STIME TTY      TIME CMD
    root   619   611  0 10:12:20 pts/2    1:01 
/export/home/crpms/java/bin/sparc
/native_threads/jre -ms10m -mx64m -Drpms.based
 
RPMS Server:
     UID   PID  PPID  C    STIME TTY      TIME CMD
    root   654   641  0 10:12:22 pts/2   74:21 
/export/home/crpms/jre1.2/bin/../
bin/sparc/native_threads/java -Xms16m -Xmx2048
 
Proxy Server:
     UID   PID  PPID  C    STIME TTY      TIME CMD
    root   666   648  0 10:12:22 pts/2   71:08 
/export/home/crpms/jre1.2/bin/../
bin/sparc/native_threads/java -Xmx2048m -Xms16