|
|
This appendix provides troubleshooting information for Resource Manager and contains the following sections:
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):
In addition, the following files should have been added to the /etc directory:
The Resource Manager installation tool installed the following directories in the /opt/CSCOpx/objects directory (or the directory you specified for the installation):
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:
Table A-1 lists error messages that might occur during installation and describes the reasons for the errors:
| Error Message | Reason for Error | User Action |
|---|---|---|
| <sub-package> did not install. | The specified package did not install correctly. | Verify you have enough disk space and reinstall Resource Manager as explained in "Installing Resource Manager." |
| Missing <sub-package> should exist in :<directory> | The specified package could not be found. Your system might be having trouble reading the Resource Manager CD. | Contact your technical support representative. |
| Error: base package: <name> did not install. Exiting. | Something prevented the base package from installing. | Contact your technical support representative. |
| pkgchk <pkg_name> failed. | The Solaris package validation tool (pkgchk) found a problem with the specified directory. | Reinstall Resource Manager. Contact your technical support representative if you still encounter this error. |
| <dir_name> not found. No additional packages installed. | No application directory was found. Your system might be having trouble reading the Resource Manager CD. | Contact your technical support representative. |
| cd <dir_name> failed. Applications not installed. | Program could not cd to the application directory. | Contact your technical support representative. |
| 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 Solaris install. Exiting. | You did not log in as root. The installation is terminated. | Log in as root and specify the correct root password. |
| ERROR: Missing directory CSCOpx in $PWD. | The installation program could not find the required directory, CSCOpx. | Contact your technical support representative. |
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:
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.
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
If the Resource Manager buttons do not work, you have not enabled Java and JavaScript. Follow these steps to enable Java and JavaScript:
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.
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:
(a) To stop the DIServer, click Stop Process in the System Admin folder. The Stop Process dialog box appears.
(b) Click the Process radio button.
(c) In the Process Name field, select DIServer, then click Finish.
To restart the DIServer, follow these steps:
(a) From the System Admin folder, click Start Processes. The Start Process dialog box appears.
(b) Click the Process radio button.
(c) In the Process Name field, select DIServer, then click Finish.
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.
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.
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.
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:
#/opt/CSCOpx/bin/collect.info
Send this file to Cisco via e-mail if directed to do so by your technical support representative.
|
|