Table Of Contents
Troubleshooting the Installation
Checking Processes After Installation
Viewing and Changing Process Status
Contacting Technical Assistance Center (TAC)
Understanding Installation Error Messages
Configuring TFTP
Troubleshooting the Installation
This appendix provides troubleshooting information for Common Services installation. It explains:
•
Checking Processes After Installation
•
Viewing and Changing Process Status
•
Contacting Technical Assistance Center (TAC)
•
Understanding Installation Error Messages
•
Configuring TFTP
Checking Processes After Installation
You can run a self test or view process failures from the CiscoWorks Server.
To run a self test, in the CiscoWorks Homepage select
Common Services > Server > Admin > Selftest.
To view process failures, in the CiscoWorks Homepage select
Common Services > Server > Reports > Process Status.
Processes that are not running will be displayed in red color.
Viewing and Changing Process Status
You can view the status of any process by selecting
Common Services > Server > Admin > Processes from the CiscoWorks Homepage.
•
From the browser, only users with administrative privileges can start and stop processes.
•
From the CiscoWorks server, only users with local administrative privileges can start and stop processes.
Step 1
Go to the CiscoWorks Homepage and select Common Services >Server > Admin > Processes
The Process Management page appears.
Step 2
Select the processes that you want to stop from the Process Management page.
Step 3
Click Stop.
If you select specific processes, the dependent processes also stop.
To start processes from the browser:
Step 1
Go to the CiscoWorks Homepage and select Common Services >Server > Admin > Processes
The Process Management page appears.
Step 2
Select the processes from this page that you want to stop.
Step 3
Click Start.
Only the selected processes start. The dependent processes do not start.
To stop all processes from the server, enter:
/etc/init.d/dmgtd stop
To all start processes from the server, enter:
/etc/init.d/dmgtd start
Caution 
Do not start the daemon manager immediately after you stop it. The ports used by daemon manager will be in use for some more time even after the daemon manager is stopped. Wait for a few minutes before you start the daemon manager.
Contacting Technical Assistance Center (TAC)
You can contact the Technical Assistance Center (TAC) if you had problems while installing Common Services.
Before contacting TAC, we recommend that you make that:
•
The system hardware and software requirements are met.
•
The disk space is not full (/ (root), /opt, and /var partitions).
•
The CD-ROM drive is not defective.
If the above conditions are met, and you still have problems, contact the Technical Assistance Center.
TAC representatives may ask you to send them the installation log file. For CS 3.0.5, the default is /var/tmp/Ciscoworks_install_YYYYMMDD_hhmmss.log, where YYYYMMDD denotes the year, month and date of installation and hhmmss denotes the hours, minutes and second of installation.
For CS 3.0.3 it will be as /var/tmp/ciscoinstall.log.
Create a report and email the generated report to TAC.
To generate the report, in the CiscoWorks Homepage, select Common Services > Server > Admin > CollectServerInformation.
Understanding Installation Error Messages
Table A-1 shows messages that might occur during installation and describes the reasons.
Table A-1 Installation Error Messages
Message
|
Reason for Message
|
User Action
|
Access problem with directory.
|
The installation program cannot access product directory that you specified.
|
Check 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.
|
Qos Policy Manager (QPM) is detected on this server. Common Services 3.0.3 cannot co-exist with QPM. We recommend that you either:
• Install Common Services 3.0.3 on a separate server
Or
• Restore the current setup with QPM on a separate server, uninstall QPM on this server, and then install Common Services 3.0.3.
|
Common Services 3.0.3 cannot co-exist with Qos Policy Manager (QPM).
|
Either install Common Services 3.0.3 on a separate server or uninstall QPM and proceed with the upgrade on the same server.
|
The setup program has discovered HP OpenView services running. This will lock some of the CiscoWorks dlls.
Stop all HP OpenView services before installing CiscoWorks.
|
You have installed Device Fault Manager (DFM) on your system, and HP Network Node Manager (HPNNM) or NetView is running on the same system.
|
Stop all HP OpenView services and proceed installing CiscoWorks.
|
Base package did not install. Exiting.
|
The installation program cannot install a required package.
|
Contact your technical support representative.
|
Cannot backup /etc/services, no change will be made.
|
The installation program could not copy /etc/services before modifying it.
|
Make sure there is enough space in /tmp.
|
Cannot become owner of file in directory directory.
|
You cannot become file owner in directory you specified as product root.
|
Check permissions on specified directory.
|
Cannot change ownership of library. Exiting.
|
The installation program could not write to the product root directory.
|
Check permissions on specified directory.
|
Cannot create directory.
|
The installation program could not write to directory you specified.
|
Check permissions on specified directory.
|
Cannot create symlink: ln -s root /opt/CSCOpx.
|
The installation program cannot create link from /opt/CSCOpx to product root directory you specified.
|
Contact your technical support representative.
|
Cannot determine the CiscoWorks Common Services version.
|
Installation disk is corrupted.
|
Contact your technical support representative.
|
Cannot determine the version of product.
|
The installation program was unable to determine product version.
|
Contact your technical support representative.
|
Cannot make list of packages for installation.
|
The installation program suffered a major failure.
|
Contact your technical support representative.
|
Cannot make root dir.
|
You do not have permission to make product directory you gave the program.
|
Check the permissions on the root or select another directory with enough permissions.
|
Cannot upgrade.
|
Upgrade failed.
|
Contact your technical support representative.
|
Copy setupdir to nmsroot failed.
|
Installation program could not write to product root directory.
|
Check permissions on root.
|
Daemon Manager could not start. The port is in use.
|
The operating system has not reallocated the port.
|
Make sure all CiscoWorks processes are terminated (/usr/ucb/ps -ef | grep CSCO). Wait five to ten minutes, then try to restart the daemon manager.
|
Installation in progress.
|
You are already running an installation on this system.
|
Run only one installation program at a time.
|
Missing file file.
|
Installation program could not find file file.
|
Contact your technical support representative.
|
mkdir -p root failed. Exiting.
|
Installation program was not able to create root specified.
|
Check permissions on root.
|
No syslog facility is available.
|
No available Syslog facilities for CiscoWorks Common Services.
|
Make one of the facilities available. To start Syslog, use the following command:
|
Not enough disk space: root.
|
You picked a product root in a file system with insufficient space to load our product.
|
Make at least 2 GB of disk space available on partition on which you install product.
|
OS version less than recommended or supported.
|
The operating system is not a supported version of Solaris.
|
Make sure you are running Solaris 8 or Solaris 9.
|
Package verification failed: pkg aborting.
|
One of the packages loaded incorrectly.
|
• Make sure the package in CD is correct. Use the command pkgchk -d disk/packages packagename
Or
• There may be a network problem, if you are installing over the network using a remotely mounted CD.
|
Required JRE patches are unavailable on the system patch. Product will fail without these patches.
|
The installation program could not find required JRE patches.
|
• Continue installation and install patches after the CiscoWorks Common Services product is installed.
Or
• Stop product installation and install required patches before installing CiscoWorks Common Services.
|
Some files cannot get backed up, datafile missing.
|
During product upgrade, some key files were not found and cannot be restored.
|
Check other directories for the missing files.
|
Syslog is not running.
|
The installation program could not start syslogd on this system.
|
Restart syslogd.
|
The components have dependency errors.
|
The installation suffered a major failure.
|
Contact your technical support representative.
|
There is no table of contents file.
|
Installation disk is corrupted.
|
Contact your technical support representative.
|
You must be logged in as root to install or uninstall this product.
|
You are not logged in as root.
|
Log in as root and enter correct password.
|
Current administration requires that a unique instance of the CSCOpkg package be created.
However, the maximum number of instances of the package that may be supported at one time on the same system has already been met.
|
You are upgrading from previous CD One editions.
|
If this happens, change the property pair to instance=overwrite in the following file: /var/sadm/install/admin/ default for CS 3.0.3. For CS 3.0.5, the default is /var/tmp/Ciscoworks_install_YYYYMMDD_hhmmss.log, where YYYYMMDD denotes the current year, month and date.
|
The installer has discovered a problem with the DNS resolution. The DNS must resolve within 10 seconds for the CiscoWorks Common Services to work properly.
|
The DNS is not being resolved or is not resolving properly.
|
Continue the installation as usual, then correct the DNS resolution problem.
|
/etc/hosts should be readable by all.
|
/etc/hosts should have read permission for all.
|
Continue with the installation. Correct the permissions of /etc/hosts after install.
|
/tmp permission should be 777.
|
/tmp should have read/write permission for all.
|
Install will quit. Change /tmp permission and restart installation.
|
This is not a supported architecture. The product cannot be installed on this server.
|
The server architecture should be 32-bit compatible.
If the server architecture is 64-bit compatible, then 32-bit compatibility libraries should be available in that machine. To check this, you can run the command isainfo -v
It should display:
• 32-bit sparc applications
• 64-bit sparcv9 applications
|
The user has to install the product on a 32-bit compatible server.
If the server architecture is 64-bit compatible, then 32-bit compatibility libraries should be available in that machine.
|
Setup has detected the following product on the destination server.
CWCS Integration Utility - Standalone.
|
CiscoWorks and SNMIM cannot co-exist.
|
Uninstall SNMIM from this system and restart Setup.
|
Permission of /usr/bin/at is $PERMS
The minimum permission required is 4755.
|
Jobs cannot be scheduled if you do not have 4755 permissions for /usr/bin/at.
|
The minimum permission required is 4755. Change it after installation is complete.
|
Configuring TFTP
The TFTP (Trivial File Transfer Protocol) daemon shipped by CiscoWorks Common Services supports TCP (Transmission Control Protocol ) Wrappers.
If the TCP Wrapper support is not configured properly in the server where CiscoWorks is installed, the jobs requiring TFTP may fail.
To ensure that TFTP works properly, check the following configuration files:
•
If /etc/hosts.allow file is present, ensure that the command in.tftpd is given as in.tftpd:ALL If the command is not there in the file at all, add it as in.tftpd:ALL
•
If /etc/hosts.deny file is present, ensure that the command in.tftpd is not there in the file
•
If both the files are not present (/etc/hosts.allow and /etc/hosts.deny), you do not need to make any changes
Note
The TCP Wrapper software extends the abilities of inetd to provide support for every server daemon under its control. It provides logging support, returns messages to connections, permits a daemon to accept only internal connections, etc.