Table Of Contents
Troubleshooting CiscoWorks 2000
Objectives
Introduction
Troubleshooting Information for CiscoWorks 2000 Installation and Setup
Required Server Software Installation Troubleshooting
Essentials Troubleshooting Tools
Logging in After Upgrading
Checking Files and Directories After Installation
Understanding Installation Error Messages
Accessing the Essentials Server
Setting Up the Browser
Adding and Importing Device Information
Gathering Server Information
Essentials Daemon Manager and CWSI Campus
Cannot Log in to AniServer
Testing Connection to the Database
Methods for Evaluating and Troubleshooting RME Problems
Error Message Format
Process Status Features
Troubleshooting a Process Problem
Starting a Process
Stopping a Process
Troubleshooting Suggestions
Information for Troubleshooting CWSI (CiscoWorks for Switched Internetworking) Campus
Understanding CWSI Campus Background Processes
Enabling trace or debug
Stopping and Starting CWSI Campus Processes
Losing the Connection to EventChannel
Starting CWSI Campus
Identifying a Corrupt Database
Replacing a Corrupt Database
Using the Same Database on Multiple Workstations
Using Multiple Copies of CWSI Campus
Improving CWSI Campus Performance
Entering Valid Community Strings
Which Community Strings Are Valid?
What Happens If I Enter an Invalid Write Community String?
Working with Discovery
Why Do Links Appear as Dashed Lines?
Why Do Devices Appear with a Red X?
Why Do Devices Appear as an Empty Box with a Red X?
Why Does Discovery Take a Long Time?
How Can Discovery Be Disabled?
How Can Devices Be Deleted?
Why Does the ATM Network Appear as a Cloud?
Why Do Some Ethernet Links Not Include Speed?
Why Do the Wrong Devices or Connections Appear?
Why Do Some Unknown Devices Appear with an OID As the Device Name?
Why Are Frame Relay CDP Links Not Discovered?
Displaying Discrepancy Reports
Interpreting the Discrepancy Report
Customizing the Discrepancy Report
Troubleshooting Information for Applications Included in CWSI Campus
Troubleshooting VlanDirector
Does VTP Need To Be Enabled?
If There Are Multiple VTP Servers in a VTP Domain, Which VTP Server Does VlanDirector Make the Changes To?
Can VLANs in Different VTP Domains Have the Same Name?
Can You Drag Ports from One VLAN to Another on VTP Transparent Switches?
Will VlanDirector Display VLAN Information for a Switch That Is in Transparent Mode?
Why Is the Switch Highlighted When Any VLAN Is Selected?
Why Is There a Lighting Bolt on the Port?
Configuring LANE Services
Troubleshooting AtmDirector
Logging Messages
Analyzing the Log
Checking the Status of Devices and Links
Checking ATM Networks
Checking ATM-VLAN Networks
Checking PNNI Networks
Collecting Data for Troubleshooting
Problem Solving
Troubleshooting TrafficDirector
Ensuring Access to SwitchProbe Devices
NetFlow and Resource Monitor Options—SwitchProbe Devices
NetFlow Option—Network Analysis Module
SwitchProbe and Network Analysis Module Security
Network Access to SwitchProbe Devices
Testing Agents, Switches, and Frame Relay Agents
Interpreting Test Agent Messages
Interpreting Switch Agent Test Messages
Troubleshooting CiscoView
The Cvinstall.cshrc and the Cvinstall.sh Files and System Performance Issue
Fixing Display Problems
Identifying Device Problems (Dashboard Monitor)
Before Calling Cisco Systems' TAC Team
Additional Sources
Troubleshooting CiscoWorks 2000
Objectives
The main objective of this chapter is to present troubleshooting information for problems commonly encountered when installing and using CiscoWorks 2000 (RME 2.2 and CWSI 2.4). It contains the following sections:
•
Introduction to the Network Management Products Family CiscoWorks 2000
•Troubleshooting Information for CiscoWorks 2000 Installation and Setup
•Methods for Evaluating and Troubleshooting RME Problems
•Information for Troubleshooting CiscoWorks for Switched Internetworking (CWSI) Campus
•Troubleshooting Information for Applications Included in CWSI Campus (VlanDirector, AtmDirector, TrafficDirector, and CiscoView)
Introduction
CiscoWorks 2000 is a family of management products that combines the best of enterprise router and switch management functionality with easy-to-access deployment of web-based technologies. CiscoWorks 2000 offers a new model of network-management solutions for large, fast-changing enterprise networks. Resource Manager Essentials and CWSI Campus make up the foundation of the CiscoWorks 2000 family, This new generation of management tools leverages the power of the Internet to bring network-accessible knowledge to the management process, and to give users standard web-browser access to management functionality. The CiscoWorks 2000 products integrate switch and router management, provide management application integration via the browser-based Cisco Management Connection, and share common services between functional modules.
Cisco delivered its first Internet-based product when it shipped Resource Manager in 1997, and it integrated several separate applications into a single suite called CiscoWorks for switched Internetworks (CWSI). CiscoWorks 2000 takes these products a step further. Cisco has added management functionality that crosses switches and routers, has dramatically increased web-accessible features, and has integrated existing products onto a common management foundation to leverage a single set of background services.
CWSI Campus offers sophisticated traffic management, ATM management, VLAN management, and device configuration to CiscoWorks 2000. It complements the Resource Manager Essentials automated software upgrade, inventory, and configuration management features. The two applications share some back-end processes, which allows Resource Manager Essentials to run on a standalone basis but requires that CWSI Campus be installed with Resource Manager Essentials as a base to build upon.
The network-management product CiscoWorks Classic was replaced by CiscoWorks 2000 Resource Manager Essentials. For those who want to know the details of migrating from CiscoWorks Classic to Essentials, please refer to the CCO link, at www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/cw2000/cw2000e/rme_ltu/ug_appb.htm. CiscoWorks 2000 has four different versions that correspond to four different operating system flavors: CW2000 on NT, CW 2000 on Solaris, CW 2000 on HPUX, and CW 2000 on AIX. In this chapter, if not specifically pointed out, the troubleshooting information should apply to all flavors of CW 2000.
Troubleshooting Information for CiscoWorks 2000 Installation and Setup
The following subsections are presented in this section:
•Required Server Software Installation Troubleshooting
•Essentials Troubleshooting Tools
•Logging in After Upgrading
•Checking Files and Directories After Installation
•Understanding Installation Error Messages
•Accessing the Essentials Server
•Setting Up the Browser
•Adding and Importing Device Information
•Gathering Server Information
•Essentials Daemon Manager and CWSI Campus
•Cannot Log in to AniServer
•Testing Connection to the Database
Required Server Software Installation Troubleshooting
CiscoWorks 2000 for Windows NT version's installation requires Windows NT 4.0 Option Pack components be installed. If you did not install one of the following required components of the Windows NT 4.0 Option Pack during initial installation, you can install them later:
•Internet Service manager
•Microsoft Management Console
•Windows Scripting Host
To install one or more of these components after initial installation, follow these steps:
Step 1 Select Start; Program; Windows NT 4.0 Option Pack; Windows NT 4.0 Option Pack setup. The Windows NT 4.0 Option Pack Setup dialog box appears.
Step 2 Click Next. A dialog box appears in which you can select Add/Remove or Remove All Installation program options.
Step 3 Select Add/Remove. The Select Components dialog box appears.
Step 4 Select the missing required components.
Step 5 Click Next. The Completing Installation dialog box appears.
Step 6 Click Finish to complete the installation.
Essentials Troubleshooting Tools
Essentials provides several troubleshooting options that are accessible from the navigation tree. To access these tools, select Admin; Troubleshooting.
1. Collecting server information—You can gather troubleshooting information about the status of the server using the Collect Server Info option. To collect server information, follow these steps:
Step 1 Select Admin; Troubleshooting; Collect Server Info. The Collect Server Info dialog box appears.
Step 2 Select a report from the Reports history list.
Step 3 Click Display. The report displays, showing information such as the product database, the operating system, and disk utilization statistics.
Step 4 To create a new report, click Create. The new report appears in the Reports history list.
Step 5 Note: It might take up to 5 minutes to collect the information.
Step 6 To delete reports, select them from the Reports history list, and then click Delete.
2. Viewing process failures—You can check for potential failures of the back-end server processes using the Process Failures option. The Process Failures table provides you with only two possible states for the failure.
3. Failed to run—The process exited or sent a failed message.
4. Administrator has shut down the server—The administrator or another program has shut down the process.
To view process failures, follow these steps:
Step 1 Select Admin; Troubleshooting; Process Failures. Table 24-1 describes the columns that the Process Failures table displays.
Table 24-1 Viewing Process Failures
Column
|
Description
|
Process Name
|
Name of the process.
|
State
|
Process status: "Failed to run" or "Administrator has shut down this server."
|
Pid
|
Process ID. A unique key by which the operating system identifies all running programs.
|
RC
|
Return code. "0" indicates normal program operation. Any other number typically represents an error. Refer to the error log.
|
Signo
|
Signal number. "0" indicates normal program operation. Any other number is the last signal delivered to the program before it terminated.
|
Start Time
|
Time and date that the process was started.
|
Stop Time
|
Time and date that the process was stopped.
|
Core
|
"Not applicable" means that the program is running normally. "CORE FILE CREATED" means that the program is not running normally and that the operating system has created a file called a core file. The core file contains important data about the process failures.
|
Information
|
Reason for the failure. "Not applicable" means that the program is not running normally.
|
Step 2 Click any process name to see details. The Process Details table appears. Click Back to return to the Process Failures table.
Step 3 Click any process state to see the System Log. The System Log appears. Click Back to return to the Process Failures table.
Step 4 Click Update at any time to refresh the fields.
5. Collecting self-test information—You can rerun self-tests and generate a report with the results using the SelfTest option. To collect self-test information, follow these steps:
Step 1 Select Admin Troubleshooting SelfTest. The Server Selftest Info dialog box appears.
Step 2 Click Run Tests to rerun self-tests and generate a report. The tests are run and a report appears in the Reports history list.
Step 3 Note: It might take up to 5 minutes to run the tests.
Step 4 Select the report from the Reports history list.
Step 5 Click Display. The report is displayed, showing whether the tests passed or failed.
Step 6 You can delete reports by selecting them from the Reports history list and then clicking Delete.
Logging in After Upgrading
After upgrading from Cisco Resource Manager 1.1 to Essentials 2.1, or from Essentials 2.0 to Essentials 2.1, or from Essential 2.1 to Essential 2.2, you might need to clear your browser cache to log into Essentials.
If the Login Manager dialog box on the Essentials desktop does not appear correctly when you attempt to log in for the first time after upgrading, clear your browser cache as follows, and then re-enter the Essentials server URL in your browser.
For Microsoft Internet Explorer, follow these steps:
Step 1 Select View Internet Options. The Internet Options dialog box appears.
Step 2 Select the General tab.
Step 3 Click Delete Files.
For Netscape Navigator, follow these steps:
Step 1 Select Edit Preferences. The Preferences dialog box appears.
Step 2 Select Advanced Cache.
Step 3 Click Clear Memory Cache, and then click OK in the Memory Cache dialog box.
Step 4 Click Clear Disk Cache, and then click OK in the Disk Cache dialog box.
Checking Files and Directories After Installation
If you encountered problems while installing Essentials, make sure that the following directories are installed in the right directories.
For CW 2000 installation on NT, the following directories should be installed in the C:\Program Files\CSCOpx directory (or the directory that you specified for the installation):
•bin
•cgi-bin (programs run by the web server)
•collect
•conf (configuration files)
•etc (Essentials system files)
•example (sample import files)
•htdocs (web server files)
•lib
•man
•objects (Essentials subsystems)
•selftest
•www
•upgrade (MIB upgrades)
•setup (setup information)
•shared (system files)
•temp (temporary files)
•tftpboot (files exported by tftpboot)
•dbupgrade
•files
•log (log files)
•proxy (temporary files)
The Essentials installation tool installed the following directories in the C:\Program Files\CSCOpx\objects directory (or the directory that you specified for the installation):
•availability (availability)
•cmf (Common Management Framework)
•config (configuration management)
•data (syslog analysis configuration files)
•db (Essentials database)
•inventory (inventory)
•mngconnection (Management Connection)
•perl5 (Essentials perl interpreter and libraries)
•proxy (proxy server information)
•share (shared program files)
•swim (Software Management)
•sysloga (syslog analysis)
•web (web server process and utilities)
For CW 2000 installation on Solaris, HPUX and AIX, make sure that the following directories have been installed in the /opt/CSCOpx/, /opt/CSCOpx/, and /usr/CSCOpx/ directories, respectively:
•bin
•cgi-bin (programs run by the web server)
•collect
•conf (configuration files)
•etc (Essentials system files)
•example (sample import files)
•htdocs (web server files)
•lib
•man
•objects (Essentials subsystems)
•selftest
•www
Also, the Essentials installation tool installed the following directories in the /opt/CSCOpx/objects, /opt/CSCOpx/objects, and /usr/CSCOpx/objects directories, respectively on Solaris, HPUX, and AIX:
•availability (availability)
•cmf (Common Management Framework)
•config (configuration management)
•data (syslog analysis configuration files)
•db (Essentials database)
•dmgt (daemon management)
•inventory (inventory)
•mngconnect (Management Connection)
•perl (Essentials perl interpreter and libraries)
•share (shared program files)
•swim (Software Management)
•tcltk (web administration)
•util (utility programs and scripts)
•web (web server process and utilities)
Note There are no config (configuration management) or util (utility programs and scripts) directories on AIX.
In addition, the following files should have been added to the /etc directory on Solaris:
•rc2.d/K90dmgtd
•init.d/dmgtd
•rc3.d/S10dmgtd
•rc.config.d/CiscoRMCtrl
On HPUX, the following files should be added:
•/sbin/rc2.d/K90dmgtd
•/sbin/init.d/dmgtd
•/sbin/rc3.d/S10dmgtd
•/eetc/rc.config.d/CiscoRMCtrl
On AIX, the file rc.dmgtd should be added in the /etc directory.
Understanding Installation Error Messages
After verifying that the correct files are installed, check the c:\rme_in001.log file (or the log file with the highest number, such as rme_in003.log) for installation errors on NT, or check the /var/tmp/ciscoinstall.log file for installation errors on Solaris, HPUX, and AIX. You might find the following types of messages:
•Information messages, which give you important details
•Warning messages, which indicate that something might be wrong with a particular process, but the process will complete
•Error messages, which indicate that a particular process could not complete
Table 24-2 shows error messages that might occur during installation on NT and describes the reasons for the errors.
Table 24-2 Installation Error Messages on NT
Error Message
|
Reason for Error
|
User Action
|
Administrator privileges are needed to install or uninstall this package. Please log in as administrator and try again.
|
The user is not logged on to Windows NT with administrator privileges.
|
Log on to Windows NT with administrator privileges, and try installing again.
|
Decompression failed on <file. The error was for <error code per CompressGet.
|
If Essentials was downloaded, a transmission error might have occurred. Otherwise, the installation media is damaged.
|
Retry the download. If you install from product CD, check the media to make sure that it's not damaged.
|
General file transmission error. Please check your target location and try again. Error number: <error code>.
|
If Essentials was downloaded, a transmission error might have occurred.
|
Retry the download.
|
Unable to write <infoFile or Unable to create <infoFile.
|
A file write operation failed.
|
Run the file system checking utility, and then repeat the installation.
|
Cannot stop service <servicename>.
|
The Essentials installation (or reinstallation) tried to stop the service <servicename>, but the service did not stop.
|
Select Control Panel; Services, and try to stop the service <servicename> manually. Then proceed with (un)installing.
|
UseDLL failed for <dll>.
|
<dll> is supposed to be available at any time for any process, but NT failed to load it.
|
Check permissions on Windows NT System 32. If the <dll> is secure.dll, check the product installation media for errors or Reinstall Windows NT.
|
<function> failed: DLL function not found.
|
<dll> is supposed to be available at any time for any process, but NT failed to load it.
|
Check permissions on Windows NT System 32. If the <dll> is secure.dll, check the product installation media for errors or Reinstall Windows NT.
|
OpenFile failed: <pathname>.
|
A file open operation failed.
|
Run the file system checking utility. Then repeat the installation.
|
ProtectFile failed: <file>: error. WWW admin security may be incomplete.
|
Setting the file permissions failed because the user might not be allowed to change them.
|
Log in as administrator.
Note: If you are installing on a FAT file system, Essentials cannot provide file security.
|
Installing in root directory is not allowed. Please choose nonroot directory.
|
You attempted to install Essentials in the root directory of a drive (for example, c:\ or d:\), which is not supported.
|
Choose a nonroot directory in which to install Essentials.
|
Resource Manager Essentials can be installed only on NT Workstation or NT Server. It is not supported on PDC/BDC.
|
The installation program determined one of the following:
Windows NT is not installed on the system.
The system is configured as a primary domain controller (PDC) or a backup domain controller (BDC).
|
Install Essentials on a Windows NT 4.0 Workstation or Windows NT 4.0 Server system that is not configured as a PDC or a BDC.
|
You have less than 1 M free space on <drive name>. Please free up some space and try again.
|
There is insufficient drive space for temporary installation files.
|
Make more drive space available, and then rerun the installation program.
|
This program requires to run on Window NT.
|
You attempted to install on a system that does not have Windows NT 4.0 installed.
|
Install Essentials on a Windows NT 4.0 Workstation or Windows NT 4.0 Server system that is not configured as a PDC or a BDC.
|
Unable to determine the type of operating system. Resource Manager Essentials can be installed only on NT Workstation or NT Server.
|
The installation program could not determine which operating system is running on the system.
|
Install Essentials on a Windows NT 4.0 Workstation or Windows NT 4.0 Server system that is not configured as a PDC or a BDC.
|
Physical memory is <...>M Paging File Size is: <...>M(initial), <...>M(max). It is recommended that initial paging file size is bigger than physical memory and that max paging file size is at least twice bigger than physical memory.
|
The paging file size is smaller than recommended.
|
Finish the installation, and then increase the paging file size.
|
The Resource Manager Essentials installation found the IIS/PWS v2/v3. Internet Information Server 4.0 is required.
|
IIS or PWS version 2 or 3 is installed on the system, but version 4.0 is required.
|
Install IIS or PWS 4.0 and the other required Microsoft software. Then rerun the installation program. Refer to the Essentials installation manual for more information.
|
The Resource Manager Essentials installation could not find Windows Scripting Host. Windows Scripting Host is required for IIS 4.0.
|
The Windows scripting host is not installed on the system.
|
Install the Windows Scripting Host (and any other required components of the Windows NT 4.0 Option Pack). Then rerun the installation program.
|
Downgrade to FCS version is not supported. If you wish to revert to FCS, back up your data, then uninstall the current version and do a new install of this version. Exiting.
|
The installation program detected that some Essentials patches or upgrades are installed. In this case, you cannot downgrade to the FCS version of the product using the installation program.
|
To revert back to the FCS version of the product, follow these steps:
1. Back up your Essentials data files.
2. Uninstall Essentials.
3. Install the FCS version of Essentials again.
4. Restore the backed-up data.
|
There is not enough space available on the disk <drive>: This drive has <...> bytes in a cluster. Total required <...> clusters (<...> bytes), only <...> clusters (<...> bytes) available. Please free up some space and rerun installation.
|
There is insufficient disk space available on drive <drive to install the product.
|
Create additional free space on the drive, or install the product on a different drive.
|
INFO: You must now install Campus CWSI 2.3 to continue using CWSI.
|
No error is indicated; this is information only. This appears only if a previous version of CWSI is installed.
|
If you want to use CWSI Campus, you must install it after installing Essentials.
|
You must now install CWSI 2.3 if you want to use the Campus product. CWSI 2.1 will not work correctly with Essentials 2.1.
|
No error is indicated; this is information only. This appears only if a previous version of CWSI is installed.
|
If you want to use CWSI Campus, you must install it after installing Essentials.
|
You have CWSI 2.1 installed and will need to upgrade to CWSI 2.3 when Resource Manager Essentials install completes to continue to use CWSI.
|
No error is indicated; this is information only. This appears only if a previous version of CWSI is installed.
|
If you have CWSI 2.1 installed, you need to upgrade to CWSI Campus 2.3 after installing Essentials to continue to use the CWSI/Campus product.
|
Cannot determine the local Administrators group.
|
The installation program cannot find one of the built-in Windows NT user groups. This prohibits the setup of Essentials security.
|
Check the Windows NT operating system. Reinstall Windows NT, if necessary, and then rerun the Essentials installation program.
|
Cannot determine the local Everyone group.
|
The installation program cannot find one of the built-in Windows NT user groups. This prohibits the setup of Essentials security.
|
Check the Windows NT operating system. Reinstall Windows NT, if necessary, and then rerun the Essentials installation program.
|
Failed to set file permissions.
|
The installation program is incapable of setting file permissions. These are most likely caused by the following:
The account that you used to log into the system has insufficient permissions.
The drive on which you are installing the product has a FAT file system.
|
Fix the cause of the permission setting problem, and then rerun the installation program.
|
Unable to uninstall Resource Manager Essentials because the following components are shared: CWSI 2.x. You need to uninstall these dependent applications then run the Resource Manager Essentials uninstallation again.
|
You cannot uninstall Essentials while CWSI or CWSI Campus is installed.
|
Uninstall CWSI or CWSI Campus from the system. Then you can uninstall Essentials.
|
FSSupportsACLs failed: <OS error message>.
|
You attempted to install on a non-NTFS file system. This prohibits Essentials from using file-level security.
|
Install Essentials on an NTFS file system if you want the file-level security enabled.
|
<...> is already running! Wait for it to finish and press the OK button below.
|
One of the installation subtasks is still running.
|
Wait for the installation subtask to finish running, and then click the OK button to proceed.
|
Unable to create/open log file.
|
The installation program was incapable of creating or opening the installation log file (located in the root directory of the drive on which you are installing, named rme_inxxx.log, where xxx is a sequential number start from 001).
|
Determine why the file could not be created or opened, fix the problem, and then rerun the installation program. Common causes of this problem include lack of disk space or write protection on the file.
|
Web Server Configuration Failed, see installation log.
|
The configuration of the web server failed.
|
Check the installation log file (rme_inxxx.log,) for more information.
Try uninstalling the Windows NT 4.0 Option Pack, and then reinstall it and rerun the Essentials installation program.
|
Error creating user bin <... more info here>. See the troubleshooting section in user manual.
|
The installation program could not create the user account bin.
|
Fix the problem that caused the failure to create the user account bin, and then rerun the installation program.
|
Setup detected a previously installed version of CiscoWorks... Please uninstall the previous version and restart Setup.
|
The TrafficDirector application was installed after a CWSI/CWSI Campus installation.
|
Install the TrafficDirector application as part of the CWSI Campus installation.
|
INFO: ComponentError returned the following data transfer error... Setup will now abort. Media Name:... Component:... File Group:... File:... Error Number...
|
Some TrafficDirector applications are still running, so the files still in use cannot be installed or upgraded.
|
Ensure that all the TrafficDirector application windows and applications are closed, and ensure that all executables—including database processes—are stopped.
|
Table 24-3 shows error messages that might occur during installation on UNIX and describes the reasons for the errors.
Table 24-3 Installation Error Messages on Solaris, HPUX, and AIX
Error Message
|
Reason for Error
|
User Action
|
<sub-package> did not install.
(This message doesn't apply to AIX platform installation.)
|
The specified package did not install correctly.
|
Verify that you have enough disk space. and reinstall Essentials as explained in the Installing Essentials manual on CCO.
|
pkgchk <pkg_name> failed.
(This message doesn't apply to AIX platform installation.)
|
The UNIX package validation tool (pkgchk) found a problem with the specified directory.
|
Reinstall Essentials.
|
WARNING: RAM in system is $RAM. $MIN_RAM recommended.
|
Your system has less than the recommended memory.
|
Add memory to your system.
|
WARNING: SWAP in system is less than 2x RAM.
|
Your system has less than the recommended swap space, which is two times the RAM.
|
Increase swap space.
|
ERROR: You must be root to run Unix install. Exiting.
|
You did not log in as root. The installation is terminated.
|
Log in as root and enter the correct root password.
|
Insufficient disk space in /var/adm.
|
/var/adm must have at least 5 MB of available disk space.
|
Make at least 5 MB of disk space available on /var/adm, and then run the installation program again.
|
Insufficient disk space in /var/tmp.
|
/var/tmp must have at least 1 MB of available disk space.
|
Make at least 1 MB of disk space available on /var/tmp, and then run the installation program again.
|
Insufficient disk space on any local volume.
|
The installation program requires a local volume with sufficient disk space on which to install the product.
|
Make at least 250 MB of disk space available on a local disk volume.
|
ERROR: The patch bos.libpthreads4.3.0.2 has to be installed for the product to work correctly. Install bos.libpthreads patch 4.3.0.2 and retry installation. Exiting.
(This applies to the AIX platform only.)
|
The patch bos.libpthreads 4.3.0.2, which is required on AIX 4.3 systems, is not installed on the system.
|
Install the patch bos.libpthreads 4.3.0.2, and then rerun the installation program. Refer to the Installing Essentials manual on CCO for more information.
|
WARNING: The patch x1C.rte3.1.4.8 has to be installed for the product to work correctly.
(This applies to the AIX platform only.)
|
The patch x1C.rte3.1.4.8 is not installed. This might cause Essentials to work incorrectly.
|
Complete the installation program, and then install the patch x1C.rte3.1.4.8. Refer to the Installing Essentials manual on CCO for more information.
|
Accessing the Essentials Server
The Essentials server uses the port 1741. Make sure that you enter the correct URL when accessing the server:
http://server_name:1741
Here, server_name is the name of the Essentials server.
If you still cannot access the server, enter the following command at a DOS prompt to make sure that your server is running:
ping server_name
If you get a message that the server is "alive" and get a proxy error when you try to connect to the server, make sure that the proxy is set up correctly. If your server is configured to use a proxy server outside the firewall (specified in Netscape Navigator under Options; Network Preferences; Proxies), you will get proxy errors if you have incorrectly configured the proxy to ignore requests to a certain machine, set of machines, or domain.
Your proxy is set up incorrectly if you encounter any of the following:
•You receive an error message that you are using a proxy outside the firewall.
•The proxy server recognizes www-int as an internal server, so it does not proxy requests to that server.
•You set up a new internal server, www-nms, but when you make a request to the proxy server, it does not recognize www-nms as an internal server and proxies the request.
•The proxy server outside the firewall tries to request data from a server inside the firewall, and the request is blocked.
•You get a "Connection Refused" error from the proxy server.
Setting Up the Browser
If the Essentials buttons do not work, you have not enabled Java and JavaScript. Enable Java and JavaScript as described in the Installing Essentials manual on CCO, in the "Configuring Client Systems" section. Ensure that your cache is not set to zero. If you experience browser problems, increase your cache settings, as explained in the same section in the Installing Essentials manual on CCO.
Do not resize the browser window while the desktop or main page is still loading. This can cause a Java error.
Adding and Importing Device Information
This subsection describes some problems that might occur when you attempt to add or import device information.
1. Adding device information—If you added a device using Admin; Inventory; Add Devices, and the Add/Import Status Summary dialog box shows that the device status has not changed from pending within 15 minutes, check the status of all processes to ensure that they are running normally, as explained in the following steps:
Step 1 To view the latest device status information, in the Add/Import Status Summary dialog box (Admin; Inventory; Import Status), click Update.
Step 2 To determine whether the DIServer process is running, select Admin; System Admin; Process Status. (The DIServer is the process responsible for validating devices and changing their status from pending.)
Even if the DIServer process shows the state "Running Normally," it might be in an error state. You need to stop and restart it by following these steps:
To stop the DIServer process, select Admin; System Admin; Stop Process. The Stop Process dialog box appears. Click the Process radio button.
In the Process Name field, select DIServer and then click Finish.
To restart the DIServer process, follow these steps:
From the System Admin folder, click Start Processes. The Start Process dialog box appears.
Click the Process radio button.
In the Process Name field, select DIServer, and then click Finish.
Step 3 Return to the Add/Import Status Summary screen by selecting Inventory; Import Status, and then click Update. The device status should change to managed within a couple of minutes.
2. Importing Device Information—If you have difficulty importing device information, try the following solutions:
–Increase the SNMP timeout setting. Refer to the online help for more information.
–Verify that you have correct read community strings entered for the devices.
Gathering Server Information
Essentials contains a utility that can help you troubleshoot server problems. You can obtain information about the Essentials server in one of two ways:
Select Admin; Troubleshooting; Collect Server Info. The Collect Server Information dialog box appears. Click Display to collect information about the server. After the information has been collected, the dialog box tells you how to view the server information in your web browser.
From the server, enter the following command from the command window:
collect.info filename.html
Here, filename is a filename of your choice.
If collect.info is not recognized as a command, add the following path name to your PATH system variable:
On NT: C:\Program Files\CSCOpx\cgi-bin\admin\perl
On Solaris and HPUX: /opt/CSCOpx/bin
On AIX: /usr/CSCOpx/bin
On UNIX machines, the server information will be collected into the /var/tmp/px_status.info file. Send this file to Cisco via e-mail if directed to do so by your technical support representative.
Essentials Daemon Manager and CWSI Campus
CWSI Campus relies on the Essentials Daemon Manager. Therefore, the Essentials Daemon Manager must be running for CWSI Campus to run. If the Essentials Daemon Manager has stalled, you must stop and restart the Essentials Daemon Manager.
On Windows NT, to stop the Essentials Daemon Manager from the GUI, follow these steps:
Step 1 From the Windows NT menu, select Start; Settings; Control Panels.
Step 2 Double-click Services.
Step 3 In the dialog box, select Essentials Daemon Manager.
Step 4 Click Stop.
To restart the Essentials Daemon Manager from the GUI, follow these steps:
Step 1 From the Windows NT menu, select Start; Settings; Control Panels.
Step 2 Double-click Services.
Step 3 In the dialog box, select Essentials Daemon Manager.
Step 4 Click Start.
To stop and start the Essentials Daemon Manager from the command-line interface, follow these steps:
Step 1 Log in as administrator.
Step 2 Open a command prompt or shell window.
Step 3 Stop the server by entering the following command at the prompt:
Start the server by entering the following command at the prompt:
Step 4 net start crmdmgtd
On a Solaris system, to stop and restart the Essentials Daemon Manager, follow these steps:
Step 1 Log in as root.
Step 2 Open a command prompt or shell window.
Step 3 Stop the server by entering the following command at the prompt:
Step 4 Start the server by entering the following command at the prompt:
# /etc/init.d/dmgtd start
Cannot Log in to AniServer
If you have just restarted your computer and cannot log in to <Hostname>AniServer, the ANI server might not be ready to receive messages. Wait a few minutes, and then try to log in again.
If you still cannot log in, follow these steps:
Step 1 Open a command prompt or shell window.
Step 2 Check to see if the daemons are running using the command-line utility pdshow in C:\Program Files\CSCOpx\bin (on Windows NT), or /opt/CSCOpx/bin (on Solaris).
This will show whether OSAgent and AniServer are running, and whether AniServer is connected to the database.
Step 3 Run osfind.
Set the OSAGENT_PORT environment variable to 42342. This is the port used by OSAgent in Essentials.
Set OSAGENT_PORT=42342 (on Windows NT)
# setenv OSAGENT_PORT 42342 (on Solaris)
Run osfind. This verifies whether AniServer has registered with the OSAgent. This tool is located in C:\Program Files\CSCOpx\lib\visigenics\bin (on Windows NT), or /opt/CSCOpx/lib/visigenics/bin (on Solaris).
If <Hostname>AniServer is registered with the OSAgent, verify that the name of <Hostname>AniServer in the login box is the same name as the name registered with OsAgent.
If <Hostname>AniServer is registered, retry to log in to CWSI Campus.
If <Hostname>AniServer is not registered, you must stop and restart CWSI Campus.
Step 4 Enter the following command to stop the CWSI Campus processes.
When the prompt returns, all daemons have been stopped.
Step 5 Enter the following command to start the CWSI Campus processes.
Wait until the prompt returns.
Step 6 Run osfind.
If <Hostname>AniServer is registered, retry to log in to CWSI Campus.
If <Hostname>AniServer is not registered, continue to next step.
Step 7 Check to see if the <Hostname>AniServer was properly registered with the daemon manager during installation using the utility pdreg.
This verifies whether AniServer is registered with Essentials Daemon Manager.
If AniServer is registered with Essentials Daemon Manager but is not running, check the ani.log to see how far the initialization has proceeded.
If AniServer is not registered, the following error message appears:
ERROR AniServer is not a registered server name.
If AniServer is not registered with Essentials Daemon Manager, it will not be capable of initializing itself. Contact your Cisco TAC representative for additional assistance.
Testing Connection to the Database
You can run a utility to determine if you can connect to the CWSI Campus database. To run the utility, follow these steps:
Step 1 Locate the testdbconn utility in the <CWSIROOT>\bin directory, where <CWSIROOT> is the directory in which you installed CWSI Campus.
Step 2 Run the testdbconn utility.
If the program finishes and the prompt returns, the database connection is fine.
Methods for Evaluating and Troubleshooting RME Problems
Essentials provides you with methods for evaluating and troubleshooting problems.
The following sections are presented in this section:
•Error Message Format
•Process Status Features
•Troubleshooting a Process Problem
Error Message Format
Essentials displays two types of error messages:
•Interface error messages
•Back-end error messages stored in the syslog
Interface error messages are displayed in dialog boxes with descriptions of the probable causes and recommended corrective actions, if any.
Three types of interface error messages are available:
•USER—Indicates a user error or invalid input
•SYSTEM—Indicates a system failure
•INTERNAL—Indicates a product code issue
Some interface error messages include a Details button. Click Details for additional information and recommended corrective action. An informational dialog box appears.
Back-end error messages result from problems that occur in processes running on the Essentials server. Back-end error messages are stored in the syslog.
Refer to the appropriate Essentials installation guide for the location of the error message logs. Figure 24-1 shows the syslog error message format.
Figure 24-1 Syslog Error Message Format
Process Status Features
Two interfaces are available for viewing and troubleshooting process problems:
•Essentials desktop (navigation tree)
•Command-line interface (CLI)
Use the Process Status, Start Process, and Stop Process System Admin options to view process status and troubleshoot process problems. Use the CLI for processes that cannot be monitored through the desktop interface (for example, syslogd).
Table 24-4 shows the process features available in the desktop interface and their command-line equivalents.
Table 24-4 Process Features
Essentials Desktop
|
Command-line Equivalents
|
Process Status
|
pdshow
|
Start Process
|
pdexec
|
Stop Process
|
pdterm
|
For a complete description of the desktop interface processes, refer to the RME online help.
Several events can cause a process to fail. For example, the database engine might fail for one of the following reasons:
•On UNIX systems, the database uses a small amount of space in the /tmp file system. If this space fills up, the database can no longer accept connections from client code and fails.
•The file system containing the database file is full.
•If an application process fails, examine your system to see whether either of these conditions or any others has occurred, and attempt to correct them.
Troubleshooting a Process Problem
The Process Failures table gives you information about potential process failures. It tells you that the process has failed or that an administrator has shut down the process.
If a process behaves in an unexpected way and you want to know the possible cause, to troubleshoot a process, perform the following steps:
Step 1 Select Admin; Troubleshooting; Process Failures.
Step 2 Click on the process name to display the Process Details table.
Step 3 Click Back to return to the Process Failures table.
Step 4 Click any process state to display the System Log.
Step 5 Click Back to return to the Process Failures table.
Step 6 Click Update at any time to refresh the fields.
Starting a Process
Scenario: You check process status and notice that the DbServer process in the Process Status table shows a state of "Failed to run." You attempt to restart the process.
For the desktop interface, to attempt a process restart using the navigation tree, perform the following steps:
Step 1 Select Admin; System Admin; Start Process.
The Start Process dialog box appears.
Step 2 Click Process, select DbServer in the Process Name drop-down list box, and then click Finish.
The Process Status table appears. If the status now reads "Running normally," you have solved the problem.
If the process is still not running normally, you may need collect more server and process information to further troubleshooting.
For the command-line interface, to restart a process using the CLI, perform the following steps:
Step 1 Enter pdexec DbServer.
Step 2 Enter pdshow DbServer again to see whether the process is operating properly.
If the process is operating properly, the following message appears:
Start = 19:16:15 06/02/1999
Info = Data server (dbeng50) invoked
If the process is still not running normally, check the error log for further troubleshooting.
Stopping a Process
Scenario: You want to back up all data that you have stored on your hard drive, so you shut down the DbServer process.
On the desktop interface, to stop the DbServer process using the navigation tree, perform the following steps:
Step 1 Select Admin; System Admin; Stop Process.
Step 2 The Stop Process dialog box appears.
Step 3 Click the Process radio button.
Step 4 Select DbServer from the Process Name drop-down list box, and then click Finish.
The process stops, and the Process Status table displays the message "Administrator has shut down this server."
On the command-line interface, to stop the DbServer process using the CLI, perform the following steps:
Step 1 Enter pdterm DbServer.
Step 2 Enter pdshow DbServer.
The following status message appears, showing that the process has been stopped.
State = Administrator has shut down this server
Start = 19:16:15 06/02/97
Troubleshooting Suggestions
Table 24-5 lists troubleshooting suggestions. If the action items suggested do not resolve the error, check the release notes supporting your platform for possible workarounds.
Table 24-5 Troubleshooting Suggestions
Error Message
|
Possible Reasons
|
Actions
|
Admin: unable to log on to Essentials (Windows NT only)
|
An incompatible Microsoft Internet Information Server (IIS) is installed.
|
Check installation instructions, unload old Microsoft IIS, and then load the correct Microsoft IIS, if necessary.
|
Authorization required. Please log in with your username and password.
|
An incompatible browser is causing cookie failure (unable to retrieve cookie).
|
Refer to the installation documentation for supported version of Internet Explorer/Netscape Navigator software.
|
Database: inaccessible.
This can appear by Process status showing one of the following:
ICServer not running
DIServer not running
AvLoader not running
DbMonitor not running
DbServer not running
EssentialsOSG not running
Alternatively, the error message "failed to get complete list of domains" could appear on an Add Device operation.
|
Server cannot connect to the database, which is corrupt or inaccessible.
|
1. Log in to Essentials as admin.
2. Select Admin; Troubleshooting Process; Failures to get a list of Essentials backend processes that have failed.
3. Select Admin; Troubleshooting; Self Test.
4. Click Create to create a report.
5. Click Display to display the report.
6. Select Admin; Troubleshooting; Collect Server Info.
7. Click the Product Database Status link to get detailed database status.
|
Database: ODBC error with Essentials (Windows NT only)
|
The ODBC resource .dll and the ODBC driver manager are different versions.
|
Install ODBC from Windows NT CD (selecting SQL server).
|
Device Configuration: archive cannot retrieve the configuration module for Catalyst devices.
|
Incorrect password was given when adding or importing the device.
|
Enter the correct Telnet and enable passwords for the Catalyst devices in the Essentials database.
The configuration archive uses Telnet to gather module configurations for Catalyst devices.
For the configuration archive to successfully gather the ATM and RSM module configurations, these modules must have the same Telnet passwords as that for the supervisors of the Catalyst 5000 Family of devices.
See Essentials online help for more information on entering passwords.
|
Device Configuration: archive cannot retrieve the running configuration for a device.
|
Incorrect read and write community strings were given when adding or importing the device.
|
Enter the correct read and write community strings in the Essentials database.
Change the order of the protocols used to retrieve the configuration. (The configuration archive downloads configurations from devices using three different transport protocols—TFTP, Telnet, and RCP, normally in that order).
See Essentials online help for more information on setting the transport protocol order used for gathering configurations.
|
Device Configuration: archive cannot retrieve the startup configuration for a device.
|
Incorrect password was given when adding or importing the device.
|
Enter the correct Telnet and enable passwords for the device in the Essentials database.
If the device is configured for TACACS authentication, add the TACACS username and password (not the Telnet password) in the Essentials database when you import the device.
If the device is configured for local user authentication, add the local username and password in the Essentials database.
If the device is configured for Telnet authentication, ensure that you use the Telnet password, enable password, enable secret (if configured), and local username and password (if configur |
