Table of Contents

Troubleshooting

Troubleshooting

This appendix provides troubleshooting information for Resource Manager and contains the following sections:

• Checking Files and Directories After Installation
  
  
• Understanding Installation Error Messages
  
  
• Accessing the Resource Manager Server
  
  
• Stopping and Restarting the Resource Manager Server
  
  
• Setting Up the Browser
  
  
• Adding Device Information
  
  
• Checking the Syslog Configuration
  
  
• Using Software Management
  
  
• Gathering Server Information
  
  

Checking Files and Directories After Installation

If you encountered problems while installing Resource Manager, make sure the following directories have been installed in the /opt/CSCOpx/ directory (or the directory you specified for the installation):

• bin/
  
  
• cgi-bin/ (programs run by the web server)
  
  
• conf/ (configuration files)
  
  
• etc/ (Resource Manager system files)
  
  
• example/ (sample import files)
  
  
• htdocs/ (web server files)
  
  
• lib /
  
• man/ (manual pages)
  
  
• objects/ (Resource Manager subsystems)
  
  
• upgrade/ (MIB upgrades)
  
  

In addition, the following files should have been added to the /etc directory:

• rc2.d/K90dmgtd
  
  
• init.d/dmgtd
  
  

The Resource Manager installation tool installed the following directories in the /opt/CSCOpx/objects directory (or the directory you specified for the installation):

• availability (Availability)
  
  
• inventory (Inventory)
  
  
• sysloga (Syslog Analysis)
  
  
• web (web server process and utilities)
  
  
• swim (Software Management)
  
  
• db (Resource Manager database)
  
  
• dmgt (daemon management)
  
  
• tcltk (web administration)
  
  
• util (utility programs and scripts)
  
  
• perl (Resource Manager perl interpreter and libraries)
  
  
• share (shared program files)
  
  
• data (syslog analysis configuration files)
  
  

Understanding Installation Error Messages

After making sure the correct files were installed, check the /var/tmp/ciscoinstall.log file for installation errors. You might find the following types of messages:

• Information messages, which give you details that you need to know
  
  
• 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 A-1 lists error messages that might occur during installation and describes the reasons for the errors:

Accessing the Resource Manager Server

The Resource Manager server uses the default port 80, which is normally used by web servers. If you receive an error message stating an existing web server is already configured to run on port 80, and the alternative port 1741 is used instead, make sure you enter the correct URL for the server:

http://server_name:1741  
 

(where server_name is the name of the machine where Resource Manager was installed, and 1741 is the alternative port on which Resource Manager is installed if port 80 was already in use). Use the following command to make sure 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 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 set up 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 errors:

• 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 doesn't 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.
  
  

Logging In

If you are logging in as an administrator and you receive an Authorization Failed error message from the browser, you have not entered a valid username or password, or you clicked Cancel on the Username and Password Required dialog box. Click Back on your browser window, and make sure you enter a valid administrator username and password.

Stopping and Restarting the Resource Manager Server

If you need to stop and restart the Resource Manager server, follow these steps:

Step 1 To stop the Resource Manager server, enter the following command as root:

# /etc/init.d/dmgtd stop
 

Step 2 To restart the server, enter the following command as root:

# /etc/init.d/dmgtd start

Setting Up the Browser

If the Resource Manager buttons do not work, you have not enabled Java and JavaScript. Follow these steps to enable Java and JavaScript:

• For Netscape Navigator 3.03, enable Java and JavaScript under
  Options > Network Preference > Languages
  
• For Netscape Navigator 4.03, enable Java and JavaScript under
  Edit > Preferences > Advanced
  
  
• For Microsoft Internet Explorer 3.02 or 4.0, enable Java Programs and Active-X Scripting under View > Options > Security
  

Make sure your cache is not set to zero. If you experience browser problems, increase your cache settings as explained in the "Web Browsers Supported" section. Do not run multiple copies of Netscape Navigator on Solaris.

Do not resize the browser window while the desktop or main page is still loading. This will cause a Java error.

Adding Device Information

If you added a device using Inventory > Add Devices and the Add/Import Status Summary dialog box indicates 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 (Inventory > Import Status), click Update.

Step 2 To check whether the DIServer is running, click Admin, then select System Admin > Process Status. (The DIServer is the process responsible for validating devices and changing their status from pending.)

If the DIServer process has the state running normally, it might be caught in an infinite loop. You need to stop and restart it by following these steps:

To restart the DIServer, follow these steps:

Step 3 Return to the Add/Import Status Summary screen by selecting Inventory > Import Status, then click Update. The device status should change to managed within a couple of minutes.

Checking the Syslog Configuration

If the Resource Manager installation fails while attempting to install Syslog Analysis, make sure you do not have the Cisco DNS/DHCP Manager (CDDM) installed on the same machine as Resource Manager. CDDM, which can be downloaded from CCO, provides syslog and TFTP daemons as part of its product. You cannot run CDDM Syslog or TFTP on the same machine as Resource Manager because they are not compatible. Make sure the server on which you install Resource Manager is not running CDDM Syslog or TFTP.

Using Software Management

If you install Software Management for the first time, and the /tftpboot directory is a remote directory, the following message is displayed during the installation of Software Management:

WARNING: The tftp directory `/tftpboot' appears to be NFS mounted.
Using NFS directories often increases the software transfer time and may cause a failure during distribution of the software to the device.
Contact your local technical support representative to make `/tftpboot' a
local directory.
 

If you have not removed the user bin from the /usr/lib/cron/at.deny file, the following warning message appears during the installation:

ERROR: User 'bin' appears in '/usr/lib/cron/at.deny'. Software Image Manager requires 'bin' to be able to run 'at'. Contact your local technical support representative to edit the file /usr/lib/cron/at.deny and remove the entry for bin.
 

You need to remove bin from the /usr/lib/cron/at.deny file.

Gathering Server Information

Resource Manager contains a utility that can help you troubleshoot problems with the server. You can obtain information about the Resource Manager server in one of two ways:

• Click Admin, then select System Admin > Collect Server Info. The Collect Server Information dialog box appears. Click Finish, and the server information will be collected into the /var/tmp/px_status.info file.
  
  
• Enter the following command:
  

# /opt/CSCOpx/bin/collect.info
 

where /opt is the directory where you installed Resource Manager.

A px_status.info file is created in the /var/tmp directory. If the file is not created, make sure you are logged in as root and that you source the /opt/CSCOpx/etc/install.cshrc or the /opt/CSCOpx/etc/install.profile file. If you did not use the default directory to install Resource Manager, substitute /opt with the directory you specified for the installation.

Send this file to Cisco via e-mail if directed to do so by your technical support representative.