|
|
This appendix provides troubleshooting information for Campus Manager (Campus) installation and setup.
This appendix contains:
If the Login Manager dialog box on the CiscoWorks2000 desktop does not appear correctly when you attempt to log in for the first time after upgrading, clear your browser cache as follows, then reenter the server URL in your browser.
For Microsoft Internet Explorer:
Step 2 Select the General tab.
Step 3 Click Delete Files, then click OK in the Delete Files dialog box.
For Netscape Navigator:
Step 2 Select Advanced>Cache.
Step 3 Click Clear Memory Cache, then click OK in the Memory Cache dialog box.
Step 4 Click Clear Disk Cache, then click OK in the Disk Cache dialog box.
After verifying that the correct files are installed, check the /var/tmp/ciscoinstall.log file for installation errors.
The following types of installation error messages might appear:
Table A-1 shows error messages that might occur during installation and describes the reasons for the errors:
| Message | Reason for Message | User Action |
|---|---|---|
Access problem with <directory>. | The installation program cannot access the product <directory> that you specified. | Check the permissions on the directory <directory>. |
Bad installation root dir. | You are trying to install the product in an unusable directory. | Install the product on a different directory. |
Base package did not install. Exiting. | The installation program cannot install a package required for the product. | Contact your technical support representative. |
Cannot backup /etc/services, no change will be made. | The installation program could not make a copy of /etc/services prior to modifying it. | Make sure that there is enough space in /tmp. |
Cannot become owner of file in directory <directory>. | You cannot become the owner of a file in the directory you specified as the product root. | Check the permissions on the directory you specified. |
Cannot change ownership of library. Exiting. | The installation program could not write to product root directory. | Check the permissions on the directory you specified. |
Cannot create <directory>. | The installation program could not write to the directory you specified. | Check the permissions on the directory you specified. |
Cannot create symlink: ln -s <root> /usr/CSCOpx. | The installation program cannot create a link from /usr/CSCOpx to the product root directory you specified. | Contact your technical support representative. |
Cannot determine the CD One version. | The installation disk is corrupted. | Contact your technical support representative. |
Cannot determine the version of <product>. | The installation program was unable to determine the product version. | Contact your technical support representative. |
Cannot make list of packages for installation. | The installation has suffered a major failure. | Contact your technical support representative. |
Cannot upgrade. | Upgrade failed. | Contact your technical support representative. |
Copy <setupdir> to <nmsroot> failed. | The installation program could not write to product root directory. | Check the permissions on the root. |
Installation in progress. | You are already running an installation on this machine. | Run only one installation program at a time. |
Missing file <file>. | The installation program could not find the <file> file. | Contact your technical support representative. |
No syslog facility is available. | There are no available syslog facilities. | Make one of the facilities available. |
Not enough disk space: <root>. | You have picked a product root in a file system with insufficient space to load the product. | Make at least 2 GB of disk space available on the partition on which you install the product. |
Package verification failed: <pkg> aborting. | While attempting to load the packages on the machine, one of the packages loaded incorrectly. | Contact your technical support representative. |
Syslog is not running. | The installation program was unable to start syslogd on this machine. | Restart syslogd. |
The components have dependency errors. | The installation program suffered a major failure. | Contact your technical support representative. |
User must be root. | You must be root to install the product. | Log in as root and enter the correct password. |
Wrong OS. | This operating system is not AIX or not a supported version of AIX. |
If you try to remove Campus but the uninstallation program fails to delete a package, try running the uninstallation program again. Several circumstances can cause a package not to uninstall successfully. Running the uninstallation program again will usually remove it.
The CiscoWorks2000 server uses port 80 by default. This port is normally used by web servers. If you receive an error message that an existing web server is already configured to run on port 80, and the alternative port 1741 is used instead, verify that you entered the correct URL for the server:
http://server_name:1741
where server_name is the name of the machine on which CiscoWorks2000 was installed and 1741 is the alternative port on which CiscoWorks2000 is installed if port 80 is in use.
If you still cannot access the server, enter 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, you will get proxy errors if you configured the proxy to ignore requests to a certain machine, set of machines, or domain.
You specify a proxy server in Netscape Navigator under Edit>Preferences>Advanced>Proxies and in Internet Explorer under Tools>Internet Options>Connections>LAN Settings.
Your proxy is set up incorrectly if:
To improve system performance for Campus, consider downloading the Client Application Manager, to install Java classes on your local machine. Refer to "Optimizing Performance with CAM (Optional)" section.
Posted: Wed May 17 02:31:11 PDT 2000
Copyright 1989 - 2000©Cisco Systems Inc.