|
|
Troubleshooting CiscoWorks Errors
This appendix provides information and suggestions for troubleshooting CiscoWorks errors. It contains the following sections:
For information on all Cisco device error messages that are 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 manual set packaged with CiscoWorks.
For UNIX and SunNet Manager error messages, refer to the appropriate Sun manuals.
CiscoWorks Release 1.0(3) Caveats
This section lists notes and restrictions that apply to CiscoWorks Release 1.0(3). If a caveat applies only to CiscoWorks Release 1.0 or 1.0(2), it is noted in the description of the caveat.
These caveats are arranged according to the CiscoWorks application to which they apply. Caveats are presented in alphabetical order. General caveats are presented first, followed by CiscoWorks applications caveats.
For caveats associated with CiscoWorks installation and configuration, see the "Error Messages" appendix in the CiscoWorks Getting Started Guide.
This section describes general caveats associated with CiscoWorks applications.
To change the device to which you back up files, remove the log file $NMSROOT/DBMS_backup.log and enter the backup_nms command string. [CSCdi03734]
Increasing Transaction Log Size
When CiscoWorks is shipped, the disk space allocated to database functions leaves about 6 MB of free space to record table information and polling and 4 MB of free space for the transaction log. However, 4 MB of disk space might be inadequate for the transaction log.
When you delete a Sybase table or specific portions of the database, the deleted database is copied to the transaction log. If the deleted information is larger than 4 MB, the deletion process is aborted, and a Sybase error message is displayed.
Increase the size of the transaction log to allow the Sybase database to be copied to the log. The $NMSROOT/etc/enlarge_nms script included in CiscoWorks Release 1.0(3) enables you to increase the size of the transaction log. After adding space to the database, the script asks you if you want to use the new space for the transaction log. If you answer yes, the new disk space is allocated to the transaction log.
For detailed instructions on how to increase the size of the transaction log, refer to the section "Enlarging the Transaction Log Space" in the "Database Administration" chapter. [CSCdi08179]
If you change the host name for the system running the Sybase dataserver, you will be unable to use the interfaces file for Sybase. To correct this problem, update the interfaces file by following the instructions in your Sybase documentation or run the $NMSROOT/etc/setaddress script. [CSCdi07688]
Keys for Interfaces in Choices Window
SNM uses instances and keys synonymously to indicate interfaces for a device. For example, to graph MIB object data for a device, you can click on a device in the Results Browser window and choose the Graph option, or select Choices from the Graph pull-down menu.
The Choices window displays the attributes and the keys in two columns. The keys indicate the interfaces for the device. The first key indicates the first interface, the second key indicates the second interface, and so on. The interfaces are listed in the order of the keys. To identify the interface associated with the key in the Choices window (for example, it could be Ethernet, serial, and so on), you might need to refer to the interfaces displayed by the Instances option in the Device Polling window or with the Show Commands. You could also perform a quick dump of the Cisco MIB variables ifTable. When you identify the desired interface, you can select the appropriate key from the Choices window. [CSCdi08171]
Listing the Host Name in the Hosts File
If the /etc/hosts table is larger than 190 KB, and the host name of your system is not listed at the top of the hosts file, Sybase might be unable to resolve the name and refuse to start. This is caused by a name resolution bug in Sun libc file. Make sure that the host name of your system is listed at the beginning of the /etc/hosts file. [CSCdi07681]
noSuchName Response for SET Error
Some older versions of SNMP agents (including the Cisco agent) return a noSuchName error for SET requests on a read-only variable. CiscoWorks will incorrectly generate an error indicating that the reply was invalid. What displays is dependent upon the CiscoWorks application you are using, but generally CiscoWorks will indicate that the reply is invalid in some way, when the actual error is something different. [CSCdi11578]
Running the $NMSROOT/sybase/bin/dwb Script
This caveat applies to Cisco routers, but is pertinent to CiscoWorks users.
When defining a community string for a router, enter the community string without quotation marks around it. For example, to define the community string as "public," enter the following command:
Sybase-Related Log Daemon Error
The Log daemon (nmlogd) establishes a connection with the Sybase server. If the Sybase dataserver dies, nmlogd attempts to reestablish the connection with the Sybase dataserver once every 60 seconds until it succeeds. If nmlogd is unable to connect to the Sybase dataserver after continuous attempts, it displays a Sybase error message that explains the reason for the error.
A typical example of an error message follows:
Nmlogd: Sybase error_handler: General SQL server error: Check messages from SQL error.
For an explanation of the Sybase error, refer to your Sybase documentation and follow the instructions for eliminating the Sybase error. The nmlogd error message will not appear again. [CSCdi08183]
Turning off CiscoWorks Daemons
If you shut down the Sybase dataserver and the Log daemon (nmlogd), you might need to shut down all CiscoWorks daemons and restart them because you will no longer be able to turn off the Event Logger daemon (nmeventd) and the Device Monitor daemon (nmdevmond) from the Process Manager window.
The following steps describe how to identify the process ID number for a CiscoWorks daemon and remove it. Repeat these steps for each CiscoWorks daemon, substituting the appropriate daemon name and process ID number.
Step 1: Enter the following commands at the UNIX prompt to identify the process identification numbers (PID) for the Log daemon (nmlogd).
# ps -vax | grep nmlogd
Step 2: Enter the following command to remove the nmlogd process:
hostname# kill -9 process-id-number
Step 3: Repeat these steps for each of the CiscoWorks daemons: the Polling daemon (nmpolld), the Event Logger daemon (nmeventd), and the Device Monitor daemon (nmdevmond). [CSCdi08220]
The caveats in this section apply to the Configuration Management application. Make sure you review the "Troubleshooting Configuration Management" section if you encounter problems with the Configuration Management application.
Troubleshooting Configuration Management
If the Configuration Management application fails or you are unable to use commands in this application, verify the following:
snmp-server community your_community_string RW
You must use the same community string in the Configuration Management application that you use for polling functions. The community string for the Configuration Management application must be ReadWrite (RW). [CSCdi01416]
Downloading Configuration Files (Syntax Errors)
It is possible to download a configuration file containing syntax errors. If you suspect this is the case, log onto the router console and initiate a TFTP configuration file download from the router. The errors will be displayed on your Console screen. [CSCdi02187]
File Dialog Box in Configuration Management
When you display the File Selection window by selecting File to Database from the Configuration Management window, the path displayed in the Path field is your current home directory. To change the path, place the cursor in the Path field, enter the new path over the existing path, and press Return. [CSCdi08321]
Updated Devices in Configuration Management
If a ReadWrite (RW) community string was assigned to the device in the Devices window, you can select a device in the Configuration Management window and execute a database-related command such as Database to Device, Device to Database, or Compare Configs. If you select a command for a device that is not assigned with a RW community string, a popup window appears and prompts you to supply the RW community string.
If you enter a community string other than RW, the database-related command fails. If this problem occurs, perform the following steps:
Step 1: Deselect the device and select it again.
Step 2: Click on the appropriate command button (for example, Database to Device).
Step 3: When prompted for the community string, enter the RW community string and click OK.
The requested command should execute correctly. [CSCdi08890]
The caveats in this section apply to the Device Monitor application.
Device Monitor Message on IP Address Information
If an IP address is assigned to an interface that did not previously have an IP address, the Device Monitor daemon (nmdevmond) generates the following type of message in the Log Manager window:
IP address went from 0.0.0.0. to 130.109.22.5
If a device interface already has an IP address, and it was removed from the configuration file, nmdevmond generates the following type of message in the Log Manager window:
IP address went from 130.109.22.5 to 0.0.0.0
[CSCdi09975]
Interface Status on Unreachable Devices
The Device Monitor application monitors the interfaces of each device by checking each interface. However, if the device cannot be reached, the Device Monitor application cannot determine the status of the interfaces or provide information about the interfaces. It does not generate an event when the interface status of a device is unknown. To obtain information about the status of devices, use SNM. For information on automatic node management, refer to your SunNet Manager 2.0 Reference Guide. [CSCdi09634]
The caveats in this section apply to the Device Polling application.
Destroying Polling Tables in isql
If you use isql to destroy a device polling table that is being actively polled, the CiscoWorks Device Polling daemon (nmpolld) displays a series of error messages in the Log manager window. Device Polling is unable to continue, and the poll group in the table remains disabled until you restart nmpolld. [CSCdi08292]
Entering Poll Rate and Device Name Manually
If you manually enter the polling interval in the Poll Rate field or a device name in the Device field and click on the Apply button, the information you entered is not accepted by the Device Polling application. To avoid this problem, select from the available polling interval rates or device names and click on the Apply button. [CSCdi09006]
Incorrect Query in Sybase for nmpolld
If you have more than one Device Polling daemon (nmpolld) process, you may need to delete one of the processes for polling to occur. As part of nmstartup, the kernel may create a new process identification number (PID). This may cause nmpolld to assume an incorrect poller id (based upon the process id problems) and thus not poll the poll groups it should. [CSCdi10777]
Log Filenames Must be Full Path Names
In nmpolld, the filenames specified with the -l, -L, or -D options that do not contain an absolute path are created relative to the root directory (/), rather than the current working directory. For example, if your current working directory was /usr/nms and you ran nmpolld -l log, you would expect the log file to be created as /usr/nms/log. However, it is created as /log.
The workaround is to always specify absolute path names when using these options. For example, enter nmpolld -l /usr/nms/log. [CSCdi12654]
Selecting Interfaces in Device Polling
When you select an interface from the Instance pick menu in Device Polling, select a device, and then click on the Apply button, the interface is applied to the object that is selected in the Objects window. [CSCdi08264]
The caveats in this section apply to the Log Manager application.
When you click on the Delete All button to delete messages displayed in the CiscoWorks Release 1.0.x Log Manager window, these messages are saved in the transaction log and then deleted. If the transaction log contains inadequate space for the messages, the deletion process is aborted.
There are several ways to prevent this problem:
Highlighting Messages in the Log Manager Window
When you select one or more messages in the Log Manager window, the messages are selected, but not highlighted. This occurs infrequently after scrolling the window by clicking on the up and down arrows for the window. If this occurs, refresh the screen with the Utilities, Refresh option and try again. [CSCdi08157]
When you select a message in the Log Manager window, the message might not appear grayed out, which would indicate that the item was selected. Generally, this problem occurs after you use the scroller to scroll up and down and then click on a message.
To correct this problem, use the OpenWindows Utilities, Refresh option to refresh your screen monitor. All selected messages are grayed out. [CSCdi08157]
When running the Log Manager application, the following message might appear repeatedly:
OPEN LOOK Toolkit Warning in application "nmlogman":
Scrollbar - Bad proportion Length resource value, set to default
Ignore this message. [CSCdi08145]
Resetting Hit Count in the Log Manager Window
When you click on the Delete All button in the Log Manager window, all the entries are deleted, but the Hit Count field is not reset to 0. To reset the Hit Count field to 0, use the OpenWindows Utilities, Refresh option. [CSCdi08178]
Traps Are Not Associated with Interfaces
SNMP traps that are received by the Log Manager application are displayed in the Log Manager window. Occasionally, the interfaces associated with the traps might not be displayed in the Log Manager window. [CSCdi08827]
The caveats in this section apply to the Path Tool application.
Empty Source/Destination Field Error
On SunOS 4.1.3 systems, if you leave the source or destination field in the Source/Destination form of the Path Tool window blank and click on the OK button, the Path Tool does not notify you that the source or destination field is an unknown host. The Path Tool application will fail. [CSCdi12401]
Failure to Remove Trailing or Leading Spaces
Path Tool does not remove trailing or leading spaces in the fields on the Source/Destination form. The following error messages display when this occurs:
Path Source is an unknown host Path Destination is an unknown host
Remove the spaces in the host names and retry the application. [CSCdi09978]
When you use the Path Tool application to display the route between two devices on a Token Ring network, the path displays correctly. However, the icons used to indicate the devices might be incorrect. [CSCdi09016]
No Support for CiscoWorks NetView PCA Icon
Path Tool does not support the CiscoWorks NetView Interface Protocol Conversion Application (PCA) icon. If a workstation that runs NetView is using the PCA icon, Path Tool substitutes a router icon instead of a workstation icon. [CSCdi09990]
Use of Interfaces by Path Tool
When the Path Tool application displays a link between two devices, the line speed is obtained from the outbound interface of the first device it displays. For example, if it displays the link between a Sun workstation and a router, the speed of the interface on the Sun workstation is displayed with the link. [CSCdi09016]
The caveats in this section apply to the Polling Summary application.
Removing an Extra Data Entry in the Polling Summary Window
If a device restarts (for example, a router reboots) while it is being polled, an extra data entry might appear and disappear in the Polling Summary window. Follow these steps to resolve this problem:
Step 1: Quit the Polling Summary application.
Step 2: Select the Tools menu on the SNM console and pull down to Polling Summary to restart the application.
The problem should not occur again. If the problem does occur again, follow these steps:
Step 1: In the Device Polling window, select the Poll Rate field and pull down the pick menu to select a poll rate of 0.
Step 2: Select Activate Changes from the Options menu to send the changes to the device polling daemon.
Step 3: Select Quit from the File menu to quit from Device Polling.
Step 4: Select the Tools menu on the SNM console and pull down to Device Polling to restart the application.
The extra data entry will not appear in the Polling Summary window. [CSCdi09606]
Specifying an Attribute and a Key
To specify the attribute and a key for a MIB object, perform the following steps:
Step 1: Select a group you want to poll from the Poll Groups scroll window in the Polling Summary window.
Step 2: In the Data scroll window, select the data report that you want to poll.
Step 3: Select the Options pull-down menu from the SNM console and pull down to Browse Data.
Step 4: In the Results Browser window, select the appropriate data report and click on it to display the Streams window.
Step 5: In the Streams window, select Graph.
Step 6: In the Graph window, select Choices.
Step 7: In the Choices window, select one attribute and one key.
If you select the key and do not select an attribute, the following error message might appear at the bottom of the Polling Summary window:
localhost: RPC: Unable to receive errno = Connection reset by peer.
In addition, a core dump might occur, and you might be unable to access the Health Monitor and nmgraph applications.
To resolve this problem, select Grapher from the Tools menu and then quit from the Grapher window. [CSCdi09252]
When you set up a polling table in Device Polling and access the Polling Summary window to view the poll group, the Data scroller might display two timestamps instead of one. These extra entries may occur when a device restarts or the Device Polling daemon is restarted. To remove any extra polling intervals, use the $NMSROOT/contrib/nmpollpurge utility. For more details on how to use this utility, refer to the nmpollpurge.README file located in the same directory. [CSCdi08066]
The following caveat applies to the Security Manager application.
When you enter the names of users or groups with an underline to represent a space (for example, Charles_Rockwell), the name displays without the underline. However, the underline does exist within the name. [CSCdi07847]
The following caveat applies to the Show Commands application.
Incorrect Show Version Information
Show Version returns incorrect information when identifying the difference between a CSC3 and CSC4 card. [CSCdi10561]
The caveats in this section apply to the Sync w/Sybase application.
Host IP Address Identification
If your SNM map contains glyphs whose host names are represented by IP addresses, executing the Sync w/Sybase application does not result in the display of these IP addresses in the devices table. To resolve this problem, make sure that hosts whose host names are represented by IP addresses are listed at the beginning of the /etc/hosts file. As a result, Sync w/Sybase will resolve the host name for these hosts. [CSCdi09061]
Due to a conflict in the number of supported bits between the router (32 bits) and the Sybase database (31 bits), when data collected on ifInOctets or ifOutOctets exceeds the 31-bit limit, the numbers stored in the Sybase database become negative. [CSCdi12372]
When using Sync w/Sybase or adding a device from Device Management, devices whose fully qualified domain names (FQDNs) contain more than two periods may fail to be initialized. The following error message displays: [CSCdi11554]
ERROR: Unknown host <FQDN> displays.
Sun Software Caveats and Patches
This section describes caveats and patches that apply to Sun software used by CiscoWorks. The caveats, which apply to OpenWindows, SunNet Manager (SNM), and the SunOS, may affect the performace of the CiscoWorks applications. Patches may be obtained by contacting Sun Microsystems, Inc. See the appropriate description for more information.
This section describes caveats associated with OpenWindows. It also describes the patch from Sun Microsystems that you can use to resolve some caveats.
CiscoWorks is compiled on a SunOS Version 4.1.3. If you are running an older version of SunOS (prior to release 4.1.2), the following message will appear when you start any of the CiscoWorks applications:
ld.so: warning: /usr/lib/libc.so.x.y has older revision than expected 8
In the example,
x.y
indicates the version number of the libc library that you currently have installed on your system. To deceive the system into thinking that it has Version 1.8 of the library, link your existing library to a version 1.8 library. Become the root user and enter the following at the UNIX prompt (#):
# ln -s /usr/lib/libc.so.x.y /usr/lib/libc.so.1.8 # ln -s /usr/lib/libc.sa.x.y /usr/lib/libc.sa.1.8
Substitute your current version number of your libc library for x.y.
Use this workaround with caution. Deceiving the system may also deceive other users and system administrators of this system. [CSCdi11801]
When using CiscoWorks, you might occasionally encounter an X error. A typical example of an X error follows:
X Error of failed request
When an X error occurs, the CiscoWorks application disappears. If you see an X error, restart the appropriate CiscoWorks application. If you are unable to access the CiscoWorks application or the X error occurs repeatedly, call Cisco Technical Support.
The Sun Microsystems OpenWindows Patch (ID 100451-30) corrects a number of OPENLOOK bugs and eliminates the display of unwanted red color from push buttons and scroll bars. Obtain this patch and install it in the /usr/openwin directory on the system that is running CiscoWorks.
If you install this patch in a different directory or a directory with a different name (for example, /usr/openwin3), create a symbolic link between /usr/openwin and the directory where you installed this patch.
SunNet Manager Caveats and Patch
Some SunNet Manager (SNM) bugs might impact how CiscoWorks Release 1.0(3) functions. Table B-1 provides the SNM bug numbers and a brief description of each bug. For detailed information on these bugs, refer to your SNM manuals or call Sun Technical Support.
Table B-1 : SNM Bugs That Impact CiscoWorks
| SNM Bug ID Number |
Description/Error Message |
|---|---|
| 1087679 | New Results Grapher might appear when graphing. |
| 1087683 | Headers and information columns are misaligned on Requests window. |
| 1088920 | The Console does not redraw all glyphs properly under standards X11. |
| 1089605 | There is no easy way to figure out why a glyph has changed state. |
| 1089607 | There is not a way to find selected devices on the Console map. |
The maximum number of objects in an SNM map is 1024. You can create more components, but you cannot exceed 1024 objects.
When plotting delta values in a graph, some counter variables might wrap around. As a result, incorrect data might be plotted in the delta graph. You might see unexpected peaks in the data when the counter variables are wrapped around. If so, try quitting the application and restarting again.
The SNM 2.0 Patch Release (Patch ID 100770-04) corrects a number of SNM bugs that might impact CiscoWorks. These corrected bugs are different from the bugs described in Table B-1. For information on how to obtain this patch, contact Sun Microsystems.
This patch also resolves the following bugs associated with CiscoWorks Release 1.0(2):
Some SunOS bugs might impact how CiscoWorks Release 1.0(3) functions. If you see the following error message, "System error: Unable to verify session ID," it may be a SunOS problem. Refer to the "Common Error Messages" section for a description of a workaround. For information on how to obtain the SunOS patch (Patch ID 100981), contact Sun MicroSystems.
Running CiscoWorks Applications from the Command Line
If you experience problems using the graphical user interface (GUI), you may need to use the command line to bring up the applications. This section describes the command line syntax to bring up all the CiscoWorks applications.
To start CiscoWorks applications from the command line, perform the following steps:
Step 1: To access the applications, commands, or daemons, change directories. The files can be located in either $NMSROOT/bin or $NMSROOT/etc. Enter the following at the command line to change to the bin directory:
hostname% cd $NMSROOT/bin
Step 2: To start any CiscoWorks application, command, or daemon, enter the appropriate command described in the following list:
dwb
---Sybase Data Workbench (DWB)
nmadmin
---Security Manager
n
mconfman---Help
nmcontacts
---Contacts
[
-v
]
---Device Management
[-v
]
[
-d
]
[
-l
logfile
]
[
-L
redundant_logfile
]
---Device Monitor daemon
[
-v
]
device community string---Environmental Monitor
[
-v
]
device community string---Real-Time Graphs
[
-v
]
[
-D
]
[
source
]
[
destination
]
---Path Tool
[
-v
]
device community string
[
option
]
---Show Commands
[
-v
]
---Sync w/Sybase
hostname% nmcontacts
CiscoWorks has six levels of error messages.Table B-2 describes these levels.
Table B-2 : CiscoWorks Error Messages Levels
| 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." |
This section describes the error messages for the CiscoWorks applications. They are organized alphabetically and include an explanation and recommended action for each error message.If you do not find the error message in this appendix, refer to your Sun documentation to check if it is a Sun error message.
In the following error messages, such expressions as <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 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 you have encountered, be certain to check for the message alphabetically based on such variables as <device>, <directory>, <number>, <string>, or <tablename>.
You have attempted to use the Previous command, but are at the beginning of the list of rows.
None.
The specified data type (retreived from the MIB) will be assumed for attr <string> rather than the data type specified by the database.
Compare MIB files to schema files to ensure that data types match.
You may not be authorized to use the Device Monitor application.
Check the Security Manager application to ensure you have privileges to use the Device Monitor application.
An invalid poll rate is specified for this poll group.
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.
The upload is not complete because the Configuration Mgmt application cannot open a temporary file. The system could be out of disk space. This is a UNIX system error message.
Try to verify the system problem from an xterm window or a cmdtool window. Consult the UNIX system administrator.
The upload is not complete because Configuration Mgmt cannot open the temporary file. The system could be out of disk space. This is a UNIX system error message.
Try to verify the system problem from an xterm window or a cmdtool window. Consult the UNIX system administrator.
This file is already open for editing. It cannot be deleted.
To delete the file, first close the editor window for the selected configuration file.
Indicates an attempt to add a device into the database via Initialize.
Make sure the device IP address is in /etc/hosts.
The IP address for the device that you are trying to find is unavailable.
Check the /etc/hosts file, the Domain Name System (DNS) server, or the NIS server (whichever is applicable) to find out if the IP address is listed for the device.
The specified table does not exist in the Sybase directory.
Use Device Polling to recreate the poll group.
Indicates an attempt to run a database form program without enough memory/swap space.
Run the command dmesg | grep mem to find out how much memory is available. In most cases, at least 1.5 MB of memory is needed for a database form program.
Run the command pstat -2 to find out how much swap space is left.
If there is not enough memory, close some applications, then start the db form program again.
The toolkit cannot find the MIB object variable or you have an invalid MIB object variable.
Verify the MIB library.
This variable is not supported by the device. The device may be a non-Cisco device because Cisco supports this MIB variable.
Contact the vendor who supplied the device.
CiscoWorks is unable to create a temporary file for printing.
Check the UNIX system. Verify the /tmp directory. Make sure it has space and it is
Cannot look up the object ID for the variable.
Check your SNM schema and oid files.
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.
To transfer the ownership of the directory and the files that belong to the superuser to a user, enter the following command at the UNIX prompt (#):
Remove the snm+lock file:
The snm+lock file is created when you launch SNM.
Either nmlogd was trying to open the syslog file that is defined in /etc/syslog.conf and was not able to do so, or logpurg was trying to open the logfile that is defined in /etc/syslog.conf and was unable to do so.
Refer to the error number (indicated as <number> above) for debugging.
The upload is not complete because the Configuration Mgmt application cannot open a temporary file. The system could be out of disk space. This is a UNIX system error message.
Try to verify the system problem from an xterm window or a cmdtool window. Consult the UNIX system administrator.
The specified variable could not be identified.
Ensure that an entry for this variable exists in a .oid file in the $SNMHOME/agents directory.
Cannot read the file.
Check file permissions.
Cannot find or read the directory.
Check permissions.
If your system is running CiscoWorks and you change the host name for your system, Sybase might not function because it continues to use the old host name.
Add the new host name to the $NMSROOT/sybase/interfaces file and restart Sybase. For example, if the new host name for your system is tassle, the entries in the interfaces file should be as follows:
The permissions for the specified directory are read-only.
Application is trying to create an ARP cache entry for <string>.
Check the ARP cache on the local system via the arp command. Check the routing table on the local system via the restart -r command.
When a file is open for editing, you cannot open another editor for it.
Locate the editing window and complete your edits.
Your system may need more memory.
Try deselecting some device you are currently monitoring and retry your request. Stop the CiscoWorks processes and install more memory.
Indicates an attempt to access the database.
Make sure $SYBASE is set properly, and that the database server is alive by observing the output ps -ajx | grep dataserver at the server machine.
The Path Tool could not locate your device via SNMP or any other means.
Check SNMP and IP on the last device the Path Tool tried to access.
This error depends on many factors, but may indicate there is no memory.
Check your Sybase database. Refer to "Verifying Available Database Space" in the "Database Administration" chapter.
Could not look up the object ID for the attribute using the previously stored object ID.
Check the SNM oid and schema files for the existence of this attribute.
Cannot locate the snm_cmd file in /usr/snm/bin. You may have customized your directory names and CiscoWorks cannot locate this file.
Check your SNM directory structure, or set the environment variable SNMHOME properly.
The Real-Time Graphs application could not send a Data Report on the SNM Console.
Make sure the SNM Console is running. Also, check the shell where the SNM Console was started for additional Sun error messages.
The Sybase transaction log may be full and cannot accept additional data.
Check the transaction log to determine if it is full. Refer to "Enlarging the Transaction Log Space" in the "Database Administration" chapter for more information.
Xterm must be included in your PATH.
If you are using Open Windows, xterm is in $OPEN WINHOME/demo. Include it in your PATH or set a symbolic link to it. If you are using the X11 tape distributed by Cisco, xterm is in /usr/bin/X11/xterm directory. Include it in your PATH or set a symbolic link to it.
The system might have inadequate disk space for storing database records.
Use the $NMSROOT/etc/enlarge_nms script to enlarge your database. For instructions, refer to the section "Enlarging the Database," in the "Database Administration" chapter.
The database server might have stopped working.
Access the Process Manager application and check to see if the On button for the database server is grayed out. If it is not, run the $NMSROOT/etc/nmstartup script to start all processes required for CiscoWorks.
The CiscoWorks MIB database (mib.bin) claims one data type, while the SNM schema claims another. The data type claimed by SNM will be assumed to be the correct one.
Correct the CiscoWorks MIB database or the SNM schema file, whichever is in error.
An error was encountered while trying to retrieve this datum.
Contact your TAC representative.
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.
Access the People window and delete the information for the appropriate vendor.
This message is confirmation for deleting a record from a database table.
Click OK to delete the record, or No to cancel.
The /tfpboot directory must have read/write permission for the user.
Change the file permission to RW (read/write).
The device has greater than 200 interfaces.
Reduce the number of device interfaces to under 200.
The device is running a software version earlier than 8.2.
Reload the device with a software version that is 8.2 or later.
A system timeout has occurred because the SNMP server is not reachable.
Use Telnet to make sure the device is up. Then check to see that SNMP is turned on, and you have a read/write community string defined in the configuration.
The device community string may be invalid.
Using Telnet, access the device to determine the community string. Then check the Device Management application to see if the community string is correct.
Indicates an attempt to add a device into the database via Initialize.
Make sure the device IP address is in /etc/hosts.
Device Polling is unable to maintain polling at the desired poll rate.
Adjust your desired poll rate to a reasonable poll rate between 0 and 2684354 seconds.
The specified device no longer exists within the Devices table in Sybase.
Use the Device Management application to ensure that the device still exists. If not, create it. Use Device Polling to recreate the poll group that was polling this device.
Cannot look up an IP address for the device.
Check the name resolution.
There is a consistency problem in the start_stop table in Sybase.
Use the Process Manager window to restart Device Polling, or obtain the process ID number for the nmpolld process and send it a HUP signal.
Step 1: To obtain the process ID number for nmpolld, enter the following command:
Step 2: Send the HUP signal by entering the following command:
The device you are trying to monitor does not have the environmental monitor card necessary for CiscoWorks to query for environmental data.
Check to make sure the device you want to monitor for environmental data is an AGS+ with a Rev. 4 ENVM card (Microcode Version 2.0 or later).
The current device you are attempting to monitor is not a Cisco Systems device. The Health Monitor only monitors Cisco Systems devices.
Use other CiscoWorks tools to get device information.
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.
Verify that the device can support SNMP. Verify that Cisco Systems Software Release 8.2 or later is installed.
The device <string> does not respond to SNMP queries.
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.
The specified directory is either a file or it does not exist.
Specify a valid directory path.
You have attempted the Next command, but are at the end of the list of rows of data.
None.
You did not set the environment variable to NMSROOT during the installation and configuration process.
To set your environment variable to NMSROOT enter the following command at the user prompt in your shell:
Sybase DWB needs this environment variable to be set.
At the command line, enter set term=x11 before you run DWB.
The applications table in the database is corrupted.
Run isql. Truncate the applications tables. Run nmadmin again.
There is a problem saving data into the database.
Check your log segment and data segment in the database to make sure they are not full. Sometimes Sybase will report the data segment full even if there is 1 MB of space available.
The most likely causes are an unknown device, an incorrect community string, or CiscoWorks is unable to resolve the host name.
Check the spelling of the device, verify the community string, and check your name resolution software. Try any common utility (Telnet, ping, and so on) to verify accessibility of the device.
The device 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.
Indicates an attempt to add a device into the database via Initialize.
Make sure the device IP address is in /etc/hosts.
Already at first record.
Attr <string> (id=<string>), using datatype from mib: <string>
Authorization check failed: <string>
Bad poll rate: <string>, for poll group <string> (id=<string>)
Cannot create configuration boot file <string>. Cannot complete uploading
process.
Cannot create temporary configuration file <string>. System error
<<string>>.<<string>> Cannot Complete Uploading Process.
Cannot delete configuration file for : Device (<string>) Version(<string>). It
has already been opened for editing.
Cannot determine IP address for the device.
Cannot find an IP address for the specified device.
Cannot find data repository table <tablename>
Cannot fork the program.
Cannot get the version string from the device.\"sysDescr\" variable is not
defined in MIB database.
Cannot get the version string from the device.\"sysDescr\" variable is not
supported by the device.
Cannot make a temporary file.
read/write enabled to the user.
Cannot map SNM variable name: <string> (attr id=<string>) to an object id
Cannot open snm+lock file: path: permission denied.
# chown -R username directory name
# rm snm+lock
Cannot open syslog ConFile <string>, errno = <number>
Cannot open temporary configuration file <string>. Cannot complete uploading
process.
Cannot poll this variable - do not know what it is.
Cannot read Snm oid directory: <string>
Cannot start Snm oid file: <string>
Cannot touch nmstartup.
SYBASE
query tcp sun-ether tassle 8000
master tcp sun-ether tassle 8000
console tcp sun-ether tassle 8001
Can't ARP for <string>
Configuration comments file for :Device (<string>) Version (<string>) has
already been opened for editing.
Could not allocate memory space: <string>
Could not connect to Sybase server.
Could not discover desired path via SNMP or any other means
Could not execute program
Could not lookup object id for attr id: <string>, so using stored id: <string>
Could not run snm_cmd
Could not send Data Report to SunNet Manager Console.
Could not write to Sybase, check transaction log.
Couldn't start xterm for editor. System error <2> <No such file or directory>.
Database is full - cannot store any more records.
Database server has disappeared.
Data type mismatch for <string> (id=<string>): database claims <string>, while
mib claims <string>
Datum error on <string>(<string>): <string>
Delete doesn't delete data from the database.
Delete this record?
<device> -config files in /tftpboot must have RW permission.
Device has too many interfaces
Device is running software which does not Support SNMP Initiated Configuration
File-Loading.
Device is unreachable. SNMP server may not be enabled.
Device is unreachable. The assigned community string may be invalid.
Device name resolution error. Check device domain.
Device poll: desired poll rate: secs, actual poll rate:
Device Poll <string> (id=<string>) cannot find device id in database.
Device Poll <string> (id=<string>) cannot map name to address - disabling itself
Device Poll <string> (id=<string>) can't find previous stop record to update it
- disabling itself.
hostname% ps -aux
hostname% kill -HUP process ID number
Device <string> is not a Cisco Systems device
Device<string> is Running Software Which Does Not Support SNMP Initiated Con
figuration File-Loading Or the Device Is Unreachable.
Device <string> not responding to SNMP.
<directory path> is not a directory!
End of Results.
Environment variable NMSROOT is not set
hostname% NMSROOT pathname
Error encounter at verifying applications table.
Error encountered while saving configuration. You may need to enlarge your
database segments.
Error obtaining information about the device.
Error obtaining SNMP values from device.
<string>
does not respond to SNMP queries.
Error resolving device name.
Failed to retrieve any data for <device name> - no data stored to database.