|
|
Troubleshooting CiscoWorks Errors
This appendix contains the following sections:
Each error message covered includes an explanation of what may cause the error and a description of how to resolve the problem.
For information on all Cisco device error messages logged in the CiscoWorks centralized log file, refer to the Router Products Configuration and Reference publication if you have Cisco Systems Software Release 8.3 or earlier. If you have Release 9.0 or later, refer to the System Error Messages, Release 9.0.
For information on Sybase errors, refer to the Sybase documentation packaged with CiscoWorks.
For UNIX and platform-specific error messages, refer to the appropriate documentation.
Running CiscoWorks Applications from the Command Line
You can run CiscoWorks from a supported graphical user interface or from the UNIX command line. If you experience problems using the graphical user interface, you may prefer to use the command line to bring up the applications. This section describes the command line syntax used to bring up all the CiscoWorks applications.
To start CiscoWorks applications from the command line, perform the following steps:
For example, to start the Contacts application, enter the following:
CiscoWorks has six levels of error messages as described in Table C-1.
Table C-1 : CiscoWorks Error Messages Levels
This section describes severe and critical error messages for the CiscoWorks applications, including the installation and configuration scripts. They are organized alphabetically and include an explanation and recommended action for each error message.
In the error messages, the expressions <string> and <number> represent the characters or digits each CiscoWorks application replaces as part of the error message. For example, the error message "Device: <string> (id=<string>) changes status to <string>" may be viewed by the user as "Device: drogg@cisco.com (id=drogg@cisco.com) changes status to up." If you cannot locate an error message alphabetically, return to the beginning of the error messages and check under the error messages that begin with string.
% cd $NMSROOT/bin
The files can be located in either $NMSROOT/bin or $NMSROOT/etc.
[-v]---Device Management application
[-v][-d][ -l
logfile][-L
redundant_logfile]---Device Monitor daemon (SunNet Manager only)
[-v]
device community string---Environmental Monitor application (needs envmonitor 2.0 or later)
[-v]
device community string---Real-Time Graphs application (must have NMS platform running)
device community string---Health Monitor application
[-v] [-D] [source] [destination]---Path Tool application
[
-v
]
device community_string
[option]---Show Commands application
[-v][-l][-D domain_name][-h host_name]---Sync w/Sybase application
% nmcontacts
The Contacts window appears.
Error Level
CiscoWorks Usage
Example
debug
Level 5 (lowest priority)
Disabling device poll: <string> (id=<string>).
information
Level 4
CiscoWorks Version 1.0.
Copyright (c) 1990, 1991, 1992 by Cisco Systems Inc. All rights reserved.warning1
Level 3
File <string> is read-only.
error
Level 2
Unknown host xxxxx. Could not connect to Sybase server.
fatal
Level 1
Prints error and exits application. Unknown catastrophic error.
bug
Level 0 (highest priority)
Cannot find device poll group - <string> (id=<string>) - to remove it.
1 By default, only messages level 3 or higher are actually logged during the normal running of the application.
<string> is an unknown device.
The name of the device cannot be resolved to an IP address.
<string>, log closed - <string>
The logger has experienced some sort of error from which it cannot recover. (There is probably an error message previous to this one indicating the unrecoverable error.) The logger is now aborting.
<string>(<string>) returned a null data type
The SNMP agent at <string> returned a null value for attribute <string>.
<string>(<string>) returned an unspecified data type
The SNMP agent at <string> returned an unspecified value for attribute <string>.
<device> -config files in /tftpboot must have RW permission.
The /tftpboot directory must have read/write permission for the user.
Already at first record.
You have attempted to use the Previous command, but are at the beginning of the list of rows.
Attr <string> (id=<number>), using datatype from mib: <string>
The specified data type (retrieved from the MIB) is being used for attr <string> rather than the data type specified by the database.
Authorization check failed: <string>
You may not be authorized to use the Device Monitor application.
Bad poll rate: <string>, for poll group <string> (id=<number>)
The poll rate is invalid.
Can't ARP for <string>
Application is trying to create an ARP cache entry for <string>.
Cannot create configuration boot file <string>. Cannot complete uploading
process.
The upload is not complete because Configuration Management cannot open a temporary file. The system may be out of disk space. This is a UNIX system error message.
Cannot create temporary configuration file <string>. System error
<<string>>.<<string>> Cannot Complete Uploading Process.
The upload is not complete because Configuration Management cannot open a temporary file. The system may be out of disk space. This is a UNIX system error message.
Cannot delete configuration file for : Device (<string>) Version(<string>). It
has already been opened for editing.
This file is already open for editing. It cannot be deleted.
Cannot determine IP address for the device.
Indicates an attempt to add a device into the database using Initialize.
Cannot find an IP address for the specified device.
The IP address for the device you are trying to find is unavailable.
Cannot find data repository table <tablename>
The specified table does not exist in the Sybase directory.
Cannot fork the program.
Indicates an attempt to run a database form program without enough memory/swap space or the kernel configuration file is set such that a maximum number of processes have been defined and reached.
On SunOS, run /etc/pstat -s to find out how much swap space is left.
On Solaris, run /etc/swap -s to find out how much swap space is left.
On HP-UX, run /etc/swapinfo to find out how much swap space is left.
If there is not enough memory, close some applications, then start the database form program again.
Cannot get the version string from the device.\"sysDescr\" variable is not
defined in MIB database.
The toolkit cannot find the MIB object variable, or you have an invalid MIB object variable.
Cannot get the version string from the device.\"sysDescr\" variable is not
supported by the device.
This variable is not supported by the device. The device may be non-Cisco, because Cisco supports this MIB variable.
Cannot make a temporary file.
CiscoWorks is unable to create a temporary file for printing.
Cannot map SNM variable name: <string> (attr id=<number>) to an object id
Cannot look up the object ID for the variable.
Cannot open lock file: path/snm+lock: permission denied.
path refers to the directory name. This message appears if you try to launch SunNet Manager (SNM) when you are logged in as a user, and the directory with the snm+lock file and other files are owned by the superuser.
# chown -R username directory name
To remove the snm+lock file, enter the following command:
# rm snm+lock
The snm+lock file is created when you launch SNM.
Cannot open syslog ConFile <string>, errno = <number>
The Log daemon is trying to open the syslog file that is defined in /etc/syslog.conf and was not able to open the file.
Cannot open temporary configuration file <string>. Cannot complete uploading
process.
The upload is not complete because Configuration Management cannot open a temporary file. The system may be out of disk space. This is a UNIX system error message.
Cannot poll this variable - do not know what it is.
The specified variable cannot be identified.
Cannot read Snm oid directory: <string>
Cannot read the file.
Cannot start Snm oid file: <string>
Cannot find or read the directory.
Cannot write to <directory path>!
The permissions for the specified directory are read-only.
Checksum error.
The UNIX tar file became corrupt.
Configuration comments file for :Device (<string>) Version (<string>) has already
been opened for editing.
When a file is open for editing, you cannot open it with another editor.
Could not allocate memory space: <string>
Your system may need more swap space.
Could not connect to Sybase server.
Indicates an attempt to access the database.
Could not discover desired path via SNMP or any other means
The Path Tool could not locate your device via SNMP or any other means.
Could not execute program
This error depends on many factors, but may indicate there is no memory.
Could not lookup object id for attr id: <number>, so using stored id: <number>
Cannot look up the object ID for the attribute using the previously stored object ID.
Could not run snm_cmd
Cannot locate the snm_cmd file in /usr/snm/bin (on SunOS or HP-UX) or /opt/SUNWconn/snm/bin (on Solaris) directory. You may have customized your directory names, and CiscoWorks cannot locate this file.
Could not send Data Report to SunNet Manager Console.
The Real-Time Graphs application could not send a Data Report on the SNM Console.
Could not write to Sybase, check transaction log.
The Sybase transaction log may be full and cannot accept additional data.
Couldn't start xterm for editor. System error <2> <No such file or directory>.
The xterm variable must be included in your PATH.
Data type mismatch for <string> (id=<number>) : database claims <string>
while mib claims <string>
The CiscoWorks MIB database (mib.bin) claims one data type, while your NMS platform claims another. The data type claimed by the NMS is assumed to be correct.
Database is full - cannot store any more records.
The system may have inadequate disk space for storing database records or the database size is set to be too small.
Database server has disappeared.
The database server may have stopped working.
Datum error on <string>(<string>): <string>
An error was encountered while trying to retrieve this datum.
Delete doesn't delete data from the database.
When you delete a vendor from the vendors table, the vendor is deleted from the Vendors window, but the information continues to exist in the People window.
Delete this record?
This message is confirmation for deleting a record from a database table.
Device <string> does not have an Environmental Controller queryable via
SNMP (requires firmware 2.0 or newer)
The device you are trying to monitor does not have the environmental monitor card necessary for CiscoWorks to query for environmental data.
Device <string> is not a Cisco Systems device
The device you are trying to monitor is not a Cisco device. The Health Monitor only monitors Cisco devices.
Device <string> not responding to SNMP.
The device <string> does not respond to SNMP queries.
Device has too many interfaces
The device has more than 200 interfaces.
Device is running software which does not Support SNMP Initiated
Configuration File-Loading.
The device is running a software release earlier than 8.2.
Device is unreachable. SNMP server may not be enabled.
A system timeout has occurred because the SNMP server is not reachable.
Device is unreachable. The assigned community string may be invalid.
The device community string may be invalid.
Device Poll <string> (id=<number>) cannot find device id in database.
The specified device no longer exists within the Devices table in Sybase.
Device Poll <string> (id=<number>) cannot map name to address - disabling itself
Cannot look up an IP address for the device.
Device Poll <string> (id= < number>) can't find previous stop record to
update it - disabling itself.
There is a consistency problem in the start_stop table in Sybase.
% ps -vax | grep nmpolld
On Solaris:
% ps -ef | grep nmpolld
On HP-UX:
% ps -ef | grep nmpolld
Identity the process ID number for nmpolld.
% kill -HUP
process ID number
Device poll: <string> <string> desired poll rate: <number> secs, actual poll
rate: <number>
Device Polling cannot maintain polling at the desired poll rate.
Device "xxxx" is Running Software Which Does Not Support SNMP Initiated
Configuration File-Loading Or the Device Is Unreachable.
The device software is not compatible with the SNMP standard, or the Cisco Systems device software is not at Software Release 8.2 or later.
Device name resolution error. Check device domain.
Indicates an attempt to add a device into the database using Initialize.
<directory> does not contain a valid CiscoWorks 1.0!
During upgrade installation, you are asked for the directory path for the old software. This error message indicates that the software in the specified directory path cannot be upgraded.
<directory path> is not a directory!
The specified directory is either a file or does not exist.
End of Results.