Table of Contents
Troubleshooting CiscoWorks Errors
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 publication for your release.
For information on Sybase errors, refer to the Sybase documentation packaged with CiscoWorks.
For AIX and NetView error messages, refer to the appropriate documentation.
You can run CiscoWorks from NetView or from the AIX command line. If you experience problems running it from NetView, 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:
- Step 1 To change directories to access the CiscoWorks applications, commands, or daemons, enter the following command:
% cd $NMSROOT/bin
- The files can be located in either $NMSROOT/bin or $NMSROOT/etc.
- Step 2 To start any CiscoWorks application, command, utility, or daemon, enter the appropriate command from the following list:
- nmautoinst---AutoInstall Manager application
- logpurg---Log Purge program
- nmadd [-v][-h][-n device][-d domain_name] [-r commstring][ -w rw_commstring]---Add to database application
- nmadmin---Security Manager application
- ciscoconnect---[-v cwuser]CiscoConnect application
- nmccsendtest---Sends CiscoConnect test message
- nmccreconfig---Reconfigure CiscoConnect
- nmcccasequery---Request updates case status information
- nmcview---CiscoView application
- nmconfig [-v][-h][-d device][-U user][-P password][-O option][-D group][-m maillist][-l logdir][-c commandfile][-s community string][-g group][-dom domain]--- Configuration Management Batch Program
- nmconfman---[-v] Configuration Management application
- nmcontacts---[-v] Contacts application
- nmdevman
[-v]---Device Management application
- nmdevswman---Device Software Manager application
- nmdomain [-v][-h ][-G domain]---Domain Manager application
- nmenv
[-v]
device community string---Environmental Monitor application (needs ENVM card with Microcode Version 2.0 or later)
- nmgcmd [-v][-h][-G domain]---Global Command Manager application
- nmgraphs
[-v]
device community string---Real-Time Graphs application (must have NetView running)
- nmhealth [-v]
device community string---Health Monitor application
- nminventory---Software Device Inventory application
- nmlogin---[-v] Login application
- nmlogout---[-v] Logout application
- nmpccmd [-v]---Configuration Snap-In Manager application
- nmpath
[-v] [-D] [source] [destination]---Path Tool application
- nmpoll---[-v] Device Polling application
- nmproc---[-v] Process Manager application
- nmsanms---[-v] Default Account program
- nmscheduler [-U cw_user_name][-N my_global_cmd]---Global Commands Scheduler
- nmshow
[
-v
]
device community_string
[option]---Show Commands application
- nmsummary---[-v] Polling Summary application
- nmswman---[-v] Software Library Manager application
- nmsync
[-v][-l][-D domain_name][-h host_name]---Sync w/Sybase application
- nmtacacs---[-v][-h][-t] name [-n][-x] TACACS Manager application
- nmversion---Version Command
- start_httpd---Starts HTTPD server for CiscoConnect
- stop_httpd---Stops HTTPD server for CiscoConnect
For example, to start the Contacts application, enter the following:
% nmcontacts
The Contacts window appears.
Note If you experience difficulty with a CiscoWorks application, contact a TAC representative. Make sure you know your system configuration and current version of CiscoWorks.
CiscoWorks has six levels of error messages, as described in Table B-1.
Table B-1 CiscoWorks Error Messages Levels
| 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. |
| warning(1) |
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 to the log during the normal running of the application.
Note The applications, commands, and error messages in this appendix are CiscoWorks application error messages. Do not confuse these messages with router error messages.
This section presents severe and critical error messages for the CiscoWorks applications, including the installation and configuration scripts. They are listed alphabetically and include an explanation and recommended action for each error message.
Note For information on any errors relating to maps, graphing, snapshots, and so on, refer to the NetView documentation.
In the error messages presented here, 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>" might appear to you 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 list and check under the error messages that begin with string.
Error Message
<string> is an unknown device.
Explanation The name of the device cannot be resolved to an IP address.
Recommended Action Check DNS, NIS, /etc/hosts file, or name resolution method.
Error Message
<string>, log closed - <string>
Explanation 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 abnormally terminating.
Recommended Action Check for other logger error messages to determine the cause.
Error Message
<string>(<string>) returned a null data type
Explanation The SNMP agent at <string> returned a null value for attribute <string>.
Recommended Action Check your SNMP agent.
Error Message
<string>(<string>) returned an unspecified data type
Explanation The SNMP agent at <string> returned an unspecified value for attribute <string>.
Recommended Action Check your SNMP agent.
Error Message
<device> -config files in /tftpboot must have RW permission.
Explanation The /tftpboot directory must have read/write permission for the user.
Recommended Action Change the file permission to read/write.
Error Message
Already at first record.
Explanation You have attempted to use the Previous command, but are at the beginning of the list of rows.
Recommended Action None.
Error Message
Attr <string> (id=<number>), using datatype from mib: <string>
Explanation The specified data type (retrieved from the MIB) is being used for attr <string> rather than the data type specified by the database.
Recommended Action Compare MIB files to schema files to ensure that data types match.
Error Message
Bad poll rate: <string>, for poll group <string> (id=<number>)
Explanation The poll rate is invalid.
Recommended Action Ensure that the poll rate for this poll group is an unsigned number between 0 and 2684354 seconds (maximum valid poll rate). Use the Device Polling application to check the poll rate.
Error Message
Can't ARP for <string>
Explanation Application is trying to create an ARP cache entry for <string>.
Recommended Action Check the ARP cache on the local system using arp. Check the routing table on the local system using netstat -r.
Error Message
Cannot create configuration boot file <string>. Cannot complete uploading
process.
Explanation The upload is not complete because Configuration Management cannot open a temporary file. The system may be out of disk space. This is an AIX system error message.
Recommended Action Try to verify the system problem from an xterm window or a cmdtool window. Consult the AIX system administrator.
Error Message
Cannot create temporary configuration file <string>. System error
<<string>>.<<string>> Cannot Complete Uploading Process.
Explanation The upload is not complete because Configuration Management cannot open a temporary file. The system may be out of disk space. This is an AIX system error message.
Recommended Action Try to verify the system problem from an xterm window or a cmdtool window. Consult the AIX system administrator.
Error Message
Cannot delete configuration file for : Device (<string>) Version(<string>). It
has already been opened for editing.
Explanation This file is already open for editing. It cannot be deleted.
Recommended Action To delete the file, first close the editor window for the selected configuration file.
Error Message
Cannot determine IP address for the device.
Explanation You attempted to add a device into the database using Initialize.
Recommended Action Check the /etc/hosts file, the Domain Naming System (DNS) server, or the NIS server (whichever is applicable) to find out if the IP address is listed for the device.
Error Message
Cannot find an IP address for the specified device.
Explanation The IP address for the device you are trying to find is unavailable.
Recommended Action Check the /etc/hosts file, the Domain Naming System (DNS) server, or the NIS server (whichever is applicable) to find out if the IP address is listed for the device.
Error Message
Cannot find data repository table <tablename>
Explanation The specified table does not exist in the Sybase directory.
Recommended Action Use Device Polling to recreate the poll group.
Error Message
Cannot fork the program.
Explanation You attempted to run a database form program without enough memory/swap space, or the kernel configuration file is set so that a maximum number of processes have been defined and reached.
Recommended Action Run lsps -a to diagnose AIX paging space, and lscfg | grep mem for diagnostic information about memory. If there is not enough memory, close some applications, then start the database form program again.
Error Message
Cannot get the version string from the device.\"sysDescr\" variable is not
defined in MIB database.
Explanation The toolkit cannot find the MIB object variable, or you have an invalid MIB object variable.
Recommended Action Verify the MIB database. Refer to showmib, described in the "MIB Files and Objects" appendix.
Error Message
Cannot get the version string from the device.\"sysDescr\" variable is not
supported by the device.
Explanation This variable is not supported by the device. The device may be non-Cisco, because Cisco supports this MIB variable.
Recommended Action Contact the vendor who supplied the device.
Error Message
Cannot make a temporary file.
Explanation CiscoWorks is unable to create a temporary file for printing.
Recommended Action Check the AIX system. Verify the /tmp directory. Make sure it has space and is read/write enabled to the user.
Error Message
Cannot open syslog ConFile <string>, errno = <number>
Explanation 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.
Recommended Action Refer to the error number <number> for debugging.
Error Message
Cannot open temporary configuration file <string>. Cannot complete uploading
process.
Explanation The upload is not complete because Configuration Management cannot open a temporary file. The system may be out of disk space. This is an AIX system error message.
Recommended Action Try to verify the system problem from an xterm window or a cmdtool window. Consult the AIX system administrator.
Error Message
Cannot poll this variable - do not know what it is.
Explanation The specified variable cannot be identified.
Recommended Action Add the necessary MIB to the CiscoWorks MIB database using the makemib script.
Error Message
Cannot write to <directory path>!
Explanation The permissions for the specified directory are read-only.
Recommended Action Using chmod, change the permissions for the specified directory to RW (read/write) or specify a different directory.
Error Message
Could not allocate memory space: <string>
Explanation Your system may need more swap space.
Recommended Action Deselect a device you are currently monitoring and retry your request. If this does not work, stop the CiscoWorks processes and configure more swap space, or shut down existing processes.
Error Message
Could not connect to Sybase server.
Explanation You attempted to access the database.
Recommended Action Make sure $SYBASE is set properly. Make sure that the database server is operational by observing the output of ps -ef | grep dataserver and by verifying that $DSQUERY is set to the name of the Sybase data server.
Error Message
Could not discover desired path via SNMP or any other means
Explanation The Path Tool could not locate your device via SNMP or any other means.
Recommended Action Check SNMP and IP on the last device the Path Tool tried to access.
Error Message
Could not execute program
Explanation This error depends on many factors, but may indicate that there is no memory.
Recommended Action Check your Sybase database. Refer to the online help section "Verifying Available Database Space."
Error Message
Could not lookup object id for attr id: <number>, so using stored id: <number>
Explanation Cannot look up the object ID for the attribute using the previously stored object ID.
Recommended Action Add the necessary MIB to the CiscoWorks MIB database using the makemib script.
Error Message
Could not run xnmgraph
Explanation Cannot locate the snm_cmd file in /usr/snm/bin directory. You may have customized your directory names, and CiscoWorks cannot locate this file.
Recommended Action Check your SNM directory structure, or verify that $PATH includes /usr/ov/bin.
Error Message
Could not write to Sybase, check transaction log.
Explanation The Sybase transaction log may be full and cannot accept additional data.
Recommended Action Check the transaction log to determine if it is full. Refer to the CiscoWorks online help section "Database Administration" for information on enlarging transaction log space.
Error Message
Couldn't start xterm for editor. System error <2> <No such file or directory>.
Explanation The xterm variable must be included in your PATH.
Recommended Action If you are using Open Windows, xterm is in $OPEN WINHOME/demo. Include it in your PATH variable or set a symbolic link to it. If you are using the X11 distributed by Cisco Systems, xterm is in the /usr/bin/X11/xterm directory. Include it in your PATH variable or set a symbolic link to it.
Error Message
Data type mismatch for <string> (id=<number>) : database claims <string>
while mib claims <string>
Explanation The CiscoWorks MIB database (mib.bin) claims one data type, while the NetView database claims another. The data type claimed by the NetView is assumed to be correct.
Recommended Action Correct the CiscoWorks MIB database or the NetView database, whichever is in error.
Error Message
Database is full - cannot store any more records.
Explanation The system may have inadequate disk space for storing database records, or the database size is set to be too small.
Recommended Action Use SMIT (or the $NMSROOT/etc/enlarge_nms script) to enlarge your database. For instructions, refer to the online help section "Database Administration."
Error Message
Database server has disappeared.
Explanation The database server may have stopped working.
Recommended Action Access Process Manager and check to see if the On button for the database server is grayed out. If not, use SMIT (or the $NMSROOT/etc/nmstartup script) to start all processes required for CiscoWorks.
Error Message
Datum error on <string>(<string>): <string>
Explanation An error was encountered while trying to retrieve this datum.
Recommended Action Contact the TAC.
Error Message
Delete doesn't delete data from the database.
Explanation 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.
Recommended Action Access the People window and delete the information for the appropriate vendor.
Error Message
Delete this record?
Explanation This message is confirmation for deleting a record from a database table.
Recommended Action Click on OK to delete the record, or No to cancel.
Error Message
Device <string> does not have an Environmental Controller queryable via
SNMP (requires firmware 2.0 or newer)
Explanation The device you are trying to monitor does not have the environmental monitor card necessary for CiscoWorks to query for environmental data.
Recommended Action Check that the device you want to monitor for environmental data is an AGS+ with a Revision 4 ENVM card (Microcode Version 2.0 or later).
Error Message
Device <string> is not a Cisco Systems device
Explanation The device you are trying to monitor is not a Cisco device. The Health Monitor only monitors Cisco devices.
Recommended Action Use other CiscoWorks tools to get device information.
Error Message
Device <string> not responding to SNMP.
Explanation The device <string> does not respond to SNMP queries.
Recommended Action Make sure the device is an SNMP client and that the database is set properly. Also, make sure the SNMP properties sheet for the device has the correct community strings.
Error Message
Device has too many interfaces
Explanation The device has more than 200 interfaces.
Recommended Action Reduce the number of device interfaces to under 200.
Error Message
Device is running software which does not Support SNMP Initiated
Configuration File-Loading.
Explanation The device is running a software release earlier than Release 8.2.
Recommended Action Reload the device with Software Release 8.2 or later.
