|
|
CiscoWorks 2.0(2) Release Note
This document discusses the CiscoWorks 2.0(2) Maintenance Release, including information on modifications and improvements to CiscoWorks 2.0(1), as well as other noteworthy material that applies to both releases.
This release note document describes the following:
The features and updates applicable to CiscoWorks Software Release 2.0 follow:
This section provides information on CiscoWorks features and functionality that became available after the CiscoWorks 2.0 documentation was printed.
When updating alias information for a device, you can edit the alias field directly from the Software Library Manager by just selecting its name and then entering a new one.
The CiscoWorks User Guide provides instruction on adding space to the transaction log and using the sp_logdevice command to transfer the space to the transaction log that already exists on the specified device. As an alternative to creating and transferring disk space, you can enter the following command at the Unix prompt to extend the transaction log that already exists:
use nms
go
sp_extendsegment logsegment, nmslog
go
To define the look of your text editor window, you must add the following command to the .Xdefaults file, substituting the appropriate options:
The CiscoWorks User Guide incorrectly specifies the command as nmconfman.EditorFormat. Enter an asterisk (*) in place of nmconfman.
Similarly, to specify the emacs editor in /usr/local/bin, add the following line to the .Xdefaults file:
The CiscoWorks User Guide incorrectly specifies the command as nmconfman.EditorFormat. Enter an asterisk (*) in place of nmconfman.
To enable boot file generation, you must edit the .Xdefaults file to specify the "on" state by adding the following line to the .Xdefaults file in your home directory:
*Bootfile:on
The CiscoWorks User Guide incorrectly shows this line beginning with Nmconfman. Enter the command exactly as shown in the preceding example, beginning with an asterisk (*).
Your CiscoWorks Log Manager checks the database for new log messages periodically. The default frequency is 900 seconds. If there are new records in the database, the background of the refresh button is set to red. You can customize the frequency of this process by modifying the .Xdefaults file. To change the refresh interval of the Log Manger window, perform the following steps:
vi $HOME/.Xdefaults
XCiscoworks*refreshInterval:new interval in seconds
XCiscoWorks*refreshInterval:450
Run the following command to update the internal database of the X server with the newly specified defaults:
If you modify the /etc/group file, do not insert any blank lines to separate group names. CiscoWorks group names are added at the end of the /etc/group file, and inserting a blank line may cause the entries that follow it to be ignored.
CiscoWorks 2.0 redefines how user-group associations were treated in earlier (1.x) versions of CiscoWorks. After upgrading, you must redefine your user-group associations and reset the user-permissions settings for your protected CiscoWorks applications. File Ownership is also treated differently than in earlier versions of CiscoWorks. So, prior to the upgrade, you should consider relocating files or directories that you have installed in the $NMSROOT directory not belonging to CiscoWorks.
Also, be aware that if you upgrade CiscoWorks, the comments field of the Software Manager application will be cleared. To preserve the comments prior to upgrading, you need to develop and maintain a separate log.
Each CiscoWorks 2.0 user must belong to only one group.
If you are upgrading from an existing version of CiscoWorks (in which users may have belonged to more than one group), the installation script presents a message advising you that any existing user-to-multiple-group associations will be disconnected. If you proceed with the upgrade, you must use the Security Manager application to reconnect each user to only one group, and then add the group to a domain. Any existing one-user-to-one-group associations will be preserved during the upgrade.
When upgrading to CiscoWorks 2.0, any existing user permissions (restrictions placed on the degree to which users can access an application) from the Release 1.x are removed. If you restricted access in this way, you must reset user permissions after you upgrade.
Until you turn on the authentication checking in the CiscoWorks Security Manager application, anyone can access any CiscoWorks application without a username or password. Authentication checking requests that users prove their identity by entering a valid CiscoWorks username and, optionally, a password. If you do not possess a valid username and password, you will be denied access.
When you upgrade, the ownership and the permission of all files under the $NMSROOT directory are automatically modified. Ownership is automatically modified to either of the following users: cscworks or root. Permissions are automatically modified in uncertain ways, depending on the files, so you should move any files or directories not belonging to CiscoWorks to another directory before the upgrade. After upgrading, you can move the non-CiscoWorks files back to $NMSROOT.
All of the X resources used by CiscoWorks applications are customizable, including colors and fonts. By overwriting the default resources used in CiscoWorks, you can customize the colors and fonts to meet your needs. To use your own colors and fonts for CiscoWorks, perform one of the following procedures:
You can add or modify TACACS information directly from the Details People window of the Device Management application. From the Details People window, you can create a new TACACS username or modify an existing one by performing the following steps:
If you add a new UNIX user to a system where CiscoWorks is already installed, but do not add the user to the CscWorks group, the user will encounter sporadic errors caused by lack of UNIX permissions to access certain files. The user will generally see a message on the terminal that says "permission denied." To fix this problem, log in as root and edit the /etc/group file. Find the line that starts with CscWorks and add the name of the new user to the end of the list of users on this line. [CSCdi16859]
In the CiscoWorks User Guide, the window depicting Global Command Scheduler does not match the one displayed in the software. The window printed in the manual represents an older version that precedes the one you see in the software. Although the window in the software appears slightly different than what is printed in the manual, the documented instructions for managing the window are correct. Note that the Command field of the scheduler window is editable, so you can change the name of the command without having to return to the Global Command Manager window.
This section lists notes and restrictions that apply to CiscoWorks Release 2.0. General caveats are noted first, followed by application-specific caveats listed alphabetically.
This section describes general caveats associated with CiscoWorks applications.
Before you install the Sybase software, either separately or by using the Sybase software supplied with CiscoWorks Release 1.0(2) or later, the network interface on your system must be present. For example, a system might have an Ethernet network interface.
When you install the CiscoWorks and Sybase software by running the ./extract_unbundled script, an interfaces file is created. This file specifies the network interface used by your system.
Do not manually edit the interfaces file before configuring the CiscoWorks software. If you change this interfaces file before configuring CiscoWorks, the Sybase dataserver is not activated. [CSCdi08816]
The Cisco 2500 is not fully supported for use with CiscoWorks 2.0(2). If you manage a Cisco 2500 with CiscoWorks 2.0(2), note these three conditions of support: First, if you run the Sync w/Sybase application on a Cisco 2500, the Cisco 2500 is displayed on your network map as a communication server. To correct this problem, use the Change Type command to correctly display the device as a Cisco 2500. Second, when using the Software Inventory Manager application, the Cisco 2500 is displayed as a communication server. Third, the Device Software Manager application does not support the Cisco 2500 software upgrade. [CSCdi20033]
When working with CiscoWorks 2.x, you can open more than one Snapshot window. Although selecting the Snapshot window opens another instance of that window instead of correctly bringing the first open window to the front, the printing functionality is not affected. This problem will be fixed in a subsequent release of CiscoWorks. [CSCdi19582]
The minimum system requirements specified in the CiscoWorks Administrator and Installation Guide have been updated. To achieve the CiscoWorks performance requested by most users, confirm that your system meets the requirements in Table 1.
Table 1 General System Requirements for CiscoWorks 2.0
Operating System |
Free Hard Disk Space | RAM(1) |
Swap Space |
Free Root Partition Needed for CiscoWorks |
|---|---|---|---|---|
| Solaris 1.x (SunOS 4.1.2 or4.1.3) | 1000 MB(2) | 64 MB | 110 MB (minimum) 128 MB (recommended) |
5 MB |
The memory and swap space requirements of CiscoWorks ultimately depend on such factors as which applications you want to run, the number of applications you want to run concurrently, and the number of network devices that you want to manage with CiscoWorks. Depending on your particular network management needs, you may need to increase the swap space beyond the general minimum requirements.
The following sample configuration represents the system requirements used by a network manager who ran six common CiscoWorks applications on top of SunNet Manager in order to manage five network devices. Table 2 lists the swap space requirements of this sample network.
Table 2 Swap Space Used to Manage Five Network Devices
| CiscoWorks Network Management Components | Swap Space Usage |
|---|---|
| CiscoWorks daemons (collective processes that perform the specific functions of CiscoWorks) | 9580 KB(1) |
| Sybase database | 2682 KB |
| SunNet Manager | 1815 KB |
| Sun Operating System | 30,720 KB |
| Configuration Snap-In Manager | 19,865 KB |
| Process Manager | 3174 KB |
| Configuration Management | 6963 KB |
| Device Management | 3906 KB |
| Global Command Manager | 6355 KB |
| Sync w/Sybase | 4311 KB |
| Total | 89371 KB or 87.3 MB(2) |
The collective swap space used by the CiscoWorks daemons (9580 KB) in Table 2 reflects what is used by the four significant CiscoWorks daemons as they manage five devices. As more devices are added, the swap space requirements increase as shown in Table 3.
Table 3 Swap Space Used by Daemons to Manage Five Network Devices
| CiscoWorks Daemons That Use Significant Swap Space |
Swap Space Usage | Swap Space Required for Each Additional Device |
|---|---|---|
| nmlogd | 585 KB(1) | No adjustments |
| nmpolld | 5085 KB | 300 KB |
| nmeventd | 1828 KB | No adjustments |
| nmdevmond | 2082 KB | No adjustments |
Total |
9580 KB or 9.4 MB(2) |
300 KB of swap space for each new device managed by CiscoWorks |
While using any of the database-related applications, such as the Configuration Management application, the following message may occasionally appear:
Confman Init Error! Unable to verify user login. Unable to login as <nms> No database table named domains
To correct this problem, stop Sybase and then restart it. Although restarting the database will solve the immediate problem, the Init Error message suggests that you are running out of user connections. The maximum number of connections is currently set to 100. If you need more connections, increase the number by using the sp_configure command. For example, to increase the number of user connections to 150, enter the following command at the UNIX prompt:
isql -Usa -P
sp_configure user 150
go
reconfigure
go
To make the additional user connections available, restart CiscoWorks using the shutdown_nms and nmstartup commands. [CSCdi18996]
SunNet Manager 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 select 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]
If you are using SunOS Version 4.1.3 and OpenWindows Version 3.0 in combination with CiscoWorks Release 2.0, windows may seem to refresh too slowly, or windows may incorrectly overlap each other. In some cases, if you click your mouse in a window that is being refreshed, all open applications may suddenly close; a core file is dumped into your home directory; and you are required to log in again. To correct this problem, upgrade to SunOS Version 4.1.3_U1. This version contains OpenWindows 3.0_U1, which fixes the specified window display problems. Contact Sun Microsystems for this upgrade version.
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 the Sun libc file. Make sure that the host name of your system is listed at the beginning of the /etc/hosts file. [CSCdi07681]
The following CiscoWorks applications are setuid programs (setuid bit is enabled) for the CiscoWorks group CscWorks: Path Tool, Global Command Manager, and Global Command Scheduler. These applications perform high-level network changes that require root privileges. In order to use these applications with root privileges, you must belong to the CscWorks group. Or, if you do not belong to the CscWorks group, you can edit the /etc/group file to add a specified UNIX username to CscWorks.
CiscoWorks 2.0 is based on the OSF/Motif windowing system and therefore requires Motif key mapping. During installation, a message will advise you that you need Motif key mapping. The installation script then offers to update the XKeysymDB (key mapping) file for you in case you are using a different platform, such as OPEN LOOK. If necessary, you also can manually update the XKeysymDB file by appending it with $NMSROOT/etc/XKeysymDB. [CSCdi15390]
Depending on your particular system configuration, you may note some changes in the performance of some CiscoWorks applications. In general, you can expect an increase in performance as you increase the memory allocation and swap space of your system. [CSCdi15368]
When the Sybase script dwb in the $NMSROOT/sybase/bin directory is run, it uses a System V command to invoke the Sybase Data Workbench. If System V extensions are not installed on your Sun workstation, the script fails when it is run. [CSCdi08660]
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:
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 MIB (Management Information Base) variables exceeds the 31-bit limit, the numbers stored in the Sybase database become negative. Note that the exporting feature of the Polling Summary application recovers the unsigned 32-bit values even when they appear negative in Sybase. [CSCdi12372]
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.
Refer to your Sybase documentation for an explanation of the Sybase error message and for instructions on how to prevent this message from reappearing. [CSCdi08183]
The caveat in this section applies to the AutoInstall Manager application.
In some isolated cases, AutoInstall Manager cannot determine the correct device type upon installation. As a result, the device icon in your network map may not correspond to the actual device type. For example, the network device may be an MGS, but AutoInstall Manager may use an IGS icon to represent the device because AutoInstall Manager cannot distinguish between an IGS and an MGS. To confirm that your network is displaying the correct icon, use the SNM Change Type command to specify the proper device type for each icon in your network map. [CSCdi15678]
The caveats in this section apply to the Configuration Management application.
The community string for the Configuration Management application must be ReadWrite (RW). [CSCdi01416]
It is possible to download a configuration file containing syntax errors. If you suspect this is the case, log in to the router Console, then initiate a TFTP (Trivial File Transfer Protocol) configuration file download from the router. The errors will be displayed on your router Console screen. [CSCdi02187]
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 directory. To change the path, place the cursor in the Path field, enter the new path over the existing path, and press Return. [CSCdi08321]
Caveats for the Configuration Snap-In Manager application follow.
If you did not set umask correctly in your UNIX account, the Configuration Snap-In Manager may not be able to read temporary files generated by itself.Consequently, the application cannot download the file by clicking on the DoItNow button. If you try this operation, you might see an error message in the status window saying "Invalid file" and tftp failed. In order to run the Configuration Snap-In Manager correctly, add the following line to your .cshrc file:
umask 2
Without this line in your .cshrc file, Configuration Snap-In Manager may not execute properly and display the error message after you click on the DoItNow button. You may find that other values, besides umask 2, will make Configuration Snap-In-Manager execute properly; however
umask 2
is usually the default recommended value. [CSCdi20386]
When running Configuration Snap-In Manager, the right section of the Command Set editing window may appear as a separate empty pane; however, all the window components are in the visible part of the window. To restore the window to its full size, just use the size box in the lower-right corner to resize the window. This OpenWindows problem has been reported to its developer. [CSCdi15378]
When downloading a partial configuration file to a router, an error message list may appear. The following error message list may appear when you create a partial command, select a router, and then click on the DoItNow button to download the partial configuration file:
Toolkit getting configuration error.
TFTP Transfer failed
Possible errors:
Tftp server is not running.
Directory protection error.
No RW community string.
Please check tftp server setup
and community string.
If you see this message for an incorrect reason, you can get past the problem by checking the router to see if the configuration has already been updated; otherwise, repeat the downloading procedure. [CSCdi16790]
If you download a file to a router running Cisco Systems Software Release 8.3 or earlier, the original banner in the router configuration is removed. To avoid the problem, upgrade your software to Release 9.x or later. [CSCdi16927]
Caveats for the Device Management application follow.
By using the Find command from the Search menu, you can locate a specified network device and then remove it permanently by clicking on the Delete button. If you use this method to delete a network device, the following message appears: No records found that match the search pattern xxxx. Although the command you issued was "delete" not "search," the selected device is deleted successfully. [CSCdi15678]
The Device Management application provides many windows for entering or accessing information. The windows are related to each other just as network devices are related to each other and to the people who maintain them. Many Device Management fields are filled in with information supplied by the forms windows. So, you should first enter the data required in the windows from the Forms menu (People, Vendors, Contacts, Location, and so forth); then, fill in the remainder of the Device Management windows. For a graphical representation of these relationships, refer to Appendix C, "CiscoWorks Database Tables," in the CiscoWorks User Guide. [CSCdi17318]
The Device Information window contains specific data obtained from the network device or database, as well as what is physically entered by a network administrator. As such, not all the fields in the Device Information window are editable. If you want to edit data in the Device Information window and find that a field is not immediately editable, use the Options or Edit menu to find the source of the editable data. [CSCdi17321]
Caveats for the Device Monitor application follow.
When working with Device Monitor, event messages are frequently displayed on your SunNet Manager Console to help you understand the status of a particular operation. Table 4 lists event messages and their corresponding meanings.
Table 4 Device Monitor Event Messages
| Event Message | Meaning |
|---|---|
| [Device]:[Interface]: DOWN on device [Device] | [Interface] on [Device] is down. |
| [Device]: [Interface]: in TEST mode on device [Device] | [Interface] on [Device] is in test mode. |
| [Device]: Interfaces no longer match previous indices | The index assigned to the [Interface] is changed. |
| [Device]: [Interface]: description changed from [Previous Interface] | The description of the [Interface] is changed. |
| [Device]: [Interface]: Admin. status went from [Previous Status] to [New Status] | The desired interface status is changed. The status can be one of following: UP, DOWN, or TESTING. |
| [Device]: [Interface]: Oper. status went from [Previous Status] to [New Status] | The current operational interface status is changed. The status can be one of following: UP, DOWN, TESTING, or DORMANT. |
| [Device]: [Interface]: IP address went from [Previous IP] to [New IP] | The IP address for the [Interface] is changed. |
| [Device]: [Interface]: Subnet mask went from [Previous Mask] to [New Mask] | The subnet mask for the [Interface] is changed. |
| [Device]: WARNING! Air flow appears marginal. | Air flow temperature is above normal 55°F but below 60°F. |
| [Device]: WARNING! Air flow appears shutdown. | The temperature of the exhaust air flow of the router is above 60°F. The cooling peripheral might be down. |
| [Device]: +5 Voltage measures [f.f] | The measured value of the +5 volt line to the power supply on the router is below 4.8 or above 5.2 volts. |
| [Device]: +12 Voltage measures [f.f] | The value of the +12 volt line to the power supply on the router is below 11.8 or above 12.2 volts. |
| [Device]: --5 Voltage measures [f.f] | The value of the --5 volt line to the power supply on the router is below --5.2 or above --4.8 volts. |
| [Device]: --12 Voltage measures [f.f] | The value of the --12 volt line to the power supply on the router is below --12.2 or above --11.8 volts. |
| [Device]: [Interface]: brought up by the AutoInstall Manager | The [Interface] on [Device] is brought up by the AutoInstall Manager. |
[CSCdi17328]
If a device interface is assigned an IP address for the first time, the CiscoWorks Device Monitor application displays a message advising you that the IP address has changed from 0.0.0.0 to the newly assigned address. The IP address will be assigned without any setbacks, even though the message should indicate a change from having no IP address, rather than 0.0.0.0, to having one. [CSCdi09975]
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 SunNet Manager. For information on automatic node management, refer to your SunNet Manager 2.0 Reference Guide. [CSCdi09634]
Caveats for the Device Polling application follow.
When using the Global Commands Scheduler application to schedule Device polling, make sure that you specify when to stop, as well as start, polling. Otherwise, polling will continue indefinitely and, consequently, will occupy disk space for the storage of polled data. When you finish device polling, always set the poll rate to zero to terminate polling. To automate the process, use the Global Commands Scheduler to create two distinct poll commands: one to start polling and another one to stop polling. (Stop polling by resetting the polling table poll rate to zero.)
To start and stop polling within the Global Command Scheduler window, enter the nmpollactivate command in the Cmd Name field. To automate the process of setting up poll scheduling, select the Schedule Polling command from the Tools menu of the Polling Summary application.
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]
The Export Data user interface does not properly acknowledge duplicate columns in a polling table. As a result, the interface does not allow the duplicate column to be deselected in the columns list. To deselect the duplicate column, remove the column data from the file after the column data is exported. [CSCdi16915]
Caveats for the Device Software Manager application follow.
The Device Software Manager application cannot find the fully qualified device (FQD) name in the database if the device name was added incorrectly. If you use FQD, make sure the network entity (device name) can respond to the domain name MIB object. In other words, if you use a domain name in the database, make sure the network entity is configured with a domain name. To correctly add a device so that it can be recognized by the database, enter the following command:
ip domain-name name.com
After you correctly add the FQD, you should run the Sync w/Sybase application to copy the device name to the CiscoWorks database. [CSCdi15358]
Based on your particular router, the Device Software Manager application requires a corresponding system software version. Before trying to run Device Software Manager, confirm that your router meets the software requirement as defined in Table 5.
Table 5 Router and Software Requirements for Use with Device Software Manager
| Cisco Router Type | Router System Software Requirement |
|---|---|
| Cisco 3000 | Software Release 9.1(7.5) or later, or 9.1(8) or later |
| Cisco AGS+ | Software Release 9.1(7.5) or later, or 9.1(8) or later |
| Cisco 4000 | Software Release 9.14(3.4) or later, or 9.14(4) or later |
| Cisco 7000 | Software Release 9.17(5.2) or later, or 9.17(6) or later |
| All Cisco routers (collection of Cisco 3000, AGS+, Cisco 4000, or Cisco 7000 routers) | Software Release 9.21(0.26) or later; 9.21(1) or later; or 9.1(8) or later |
| Cisco 7000 routers on which you want to perform microcode upgrades | Software Release 9.17(5.2) or later; 9.17(6) or later; 9.21(0.32) or later; or 9.21(1) or later |
A caveat for the Health Monitor application follows.
The top panel of the Health Monitor window displays three CPU dials: Now, 1 Min, and 5 Min. Each of these dials is designed to display the CPU load over time. However, in some isolated cases, the 1 Min dial continuously displays 0. This known deficiency is expected to be fixed in a subsequent release. [CSCdi17641]
The caveats in this section apply to the installation of CiscoWorks Releases 1.0(3) and 2.0.
If you run ncsconfigure, and the message, "FIFO_config: Permission denied" appears, your installation fails. The root umask setting on your system caused the configuration script to not allow other users, in this case the Sybase user, to read the configuration files. To remove the files with the incorrect privileges and rerun the installation correctly, perform the following steps.
The following steps should be run as root and in sequence, without logging out or changing to superuser, or the umask setting (from the umask command) will be lost:
If you are performing a new CiscoWorks installation, and a Sybase user entry is already in the
/etc/passwd file, the sybconfig utility will require that the $SYBASE variable be set to the home directory given in the /etc/passwd entry. If this condition is not met, the sybconfig utility will exit. The sybconfig utility will cause load_nms, and consequently ncsconfigure, to fail on a new installation. The workaround is to remove the Sybase user entry from the /etc/passwd file when installing CiscoWorks and replace it after the installation. [CSCdi16864]
If your CiscoWorks installation fails, or a given application seems to be malfunctioning, look at the log file to see if an error was generated that you can correct. If the error condition is unusual, you may want to supply the log file to a technical support representative in order to verify and resolve the condition.
You can obtain a complete log file during installation by entering the following commands:
%./extract_unbundle |& tee /usr/tmp/unbundled/.install/extract.log
% /usr/tmp/unbundled/ncsconfigure |& tee /usr/tmp/unbundled/.install/ncsconfigure.log
A caveat for the Login Manager application follows.
When invoking the Change User command within Login Manager, an incorrect login record may appear in the logins table. [CSCdi13536]
A caveat for the Path Tool application follows.
Network numbers appear in the source and destination list while you are using the resolv+ library. CiscoWorks does not support resolv+. To get past this problem, use a different name resolver with CiscoWorks. [CSCdi16541]
The caveats in this section apply to the Polling Summary application.
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:
If the problem does occur again, follow these steps:
To specify the attribute and a key for a MIB object, perform the following steps:
In order to run reports using the Polling Summary, the tables being polled must be valid, meaning they must contain all the needed MIB objects required to run a specified report. The polling tables used in report generating were created when you initially set up Device Polling.
If you attempt to run a report from the command line, you might encounter an error if the polling table is invalid. Try running reports from the graphical user interface where the various reports are listed in the Tools menu. If the menu item is enabled, the polling table is valid, so the report can be run. If the menu item is disabled, the polling table is invalid. In this case, you must first add the needed MIB objects to the polling table by using the Device Polling application. [CSCdi17323, CSCdi17324, and CSCdi17325]
If you move a line to a new interface, the database will not immediately recognize devices on that interface. For example, you may have moved the telephone line that leads to a remote site, from Serial1 to Serial3. If you move a line and want to accurately poll its devices, first run Sync w/Sybase to acknowledge the new devices in the database, then retry the polling operation. [CSCdi17326]
A caveat for the Real-Time Graphs application follows.
When using Real-Time Graphs to graph MIB objects, the following message appears: line 7: Error: Unable to obtain grapher port number. This message appears if the SNM Results Grapher is terminated improperly, such as killing the process id from the command line. If you encounter this problem, try invoking the SNM grapher from the Tools menu and then use Real-Time Graphs to graph the MIB objects again. [CSCdi17317]
Caveats for the Software Library Manager application follow:
The Software Library Manager and Device Software Manager applications require the following minimal disk space in order to run properly: at least 6 MB (6144 KB) of free space for the /tmp directory and 6MB (6144 KB) of free space for the /tftpboot directory. To confirm that your system meets the minimal requirements, perform the following steps:
% df
Filesystem kbytes used avail capacity Mounted on /dev/sd0a 24207 12115 9672 56% / /dev/sd0g 506046 167788 287654 37% /usr /dev/sd1b 62031 13230 42598 24% /tmp /dev/sd1g 1175742 730206 327962 69% /tue
The Software Library Manager does not keep a historical record of the comments field. Consequently, you see only the most recently saved comments field when you open the Software Library Manager window. If you want permanent record of all the data entered in the Comments field, you need to develop and maintain a separate log. [CSCdi20041]
Caveats for the Sync w/Sybase application follow.
When the Sybase--->SNM command determines that a network entity cannot be determined, the Sync w/Sybase application creates an icon for the new device as specified by the X resource XCiscoWorks*defaultIcon. The default is the router icon. To correctly designate the device icon, use the SNM Change Type command.
You can also modify the default icon by specifying a different value in $HOME/.Xdefaults file. For example, the following line specifies the default icon to be a workstation:
XCiscoWorks*defaultIcon:workstation
[CSCdi16819]
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. Sync w/Sybase will then resolve the host name for these hosts. [CSCdi09061]
Caveats for the OpenWindows platform and descriptions of patches from Sun Microsystems that you can use to resolve some caveats follow.
CiscoWorks is compiled on a SunOS Release 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 following example, x.y indicates the version number of the libc library that is currently 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 Release 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 the 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 an X error appears, restart the appropriate CiscoWorks application. If you are unable to access the CiscoWorks application or if the X error occurs repeatedly, contact a technical support representative.
The Sun Microsystems OpenWindows Patch (ID 100451-30) corrects a number of OPEN LOOK 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 in 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.
Some SunNet Manager (SNM) bugs might impact how CiscoWorks functions. Table 6 provides the SNM bug numbers and brief descriptions. For detailed information on these bugs, refer to your SNM documentation or call Sun MicroSystems Technical Support.
Table 6 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 no way to find selected devices on the Console map. |
The SNM 2.0 Patch Release (Patch ID 100770-06) corrects a number of SNM bugs that might impact CiscoWorks. These corrected bugs are different from the bugs described in Table 6. 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):
The maximum number of objects in an SNM map is 1024. You can create more components, but you cannot exceed 1024 objects.
Whenever you upgrade or modify your existing version of SunNet Manager, CiscoWorks files may get removed. To restore the CiscoWorks-specific files, confirm that your environment variable NMSROOT is set properly, then log in as root and run the following command:
$NMSROOT/etc/cw_install_snm
[CSCdi18282]
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]
Some SunOS bugs might impact how CiscoWorks functions. If the following error message appears, it may be a SunOS problem: System error: Unable to verify session ID.
Follow these steps to verify the problem caused by the error message and to eliminate the problem:
Determine whether a core dump occurred. Also contact Sun Microsystems and report this error message.
ps -ajx
CiscoWorks Release 2.0(2) contains the following new feature and modifications to CiscoWorks Release 2.0(1) and 1.0(3).
If you are performing a new installation only, the installation script of CiscoWorks 2.0(2) allows you to specify the disk partition on which you want to install Sybase and the corresponding transaction log, or to accept the default $NMSROOT. Depending on your needs, you can even share the Sybase installation across several disk partitions. In addition to choosing a location, you can also specify the size of your database and transaction log.
Because the size of your particular database can vary, the installation program now prompts you for the amount of space you want to allocate for Sybase and for the corresponding transaction log. For Sybase, you must specify a size that is at least 6 MB, or you can accept the default size of 50 MB. For the transaction log, you must specify a size that is at least 4 MB, or you can accept the default size of 10 MB.
After you specify a size and location for the disk partition, the CiscoWorks 2.0(2) installation script automatically checks to make sure you have the specified disk space before installing the database. If you do not have the disk space you requested, CiscoWorks automatically prompts you to select other partitions. [CSCdi16861]
If you are performing a new installation of CiscoWorks on a server that already contains a version of Sybase, you can now choose to install the CiscoWorks database on that server, rather than install another copy of Sybase exclusively for CiscoWorks. To install the CiscoWorks database on an existing database server perform the following steps:
CiscoWorks 2.0(2) provides the following modifications to CiscoWorks Release 2.0(1) and 1.0(3):
May 11 15:43:56 nmgt03 nmpolld: [ERROR] Device Poll cmpr137 (id=60) can't find previous stop record to update it - disabling itself
enlarge_nms -D tempdb
This section contains some frequently asked questions about CiscoWorks and SNM issues that impact CiscoWorks. Before contacting a technical support representative, read this section to see if your questions are addressed.
select text1+text2+text3+text4 from ciscolog
where netaddr = z
and (text1+text2+text3+text4 like %x% or text1+text2+text3+text4 like %y%)
and timestamp = (select max (timestamp) from ciscolog)
where netaddr = z
and (text1+text2+text3+text4 like %x% or (text1+text2+text3+text4 like %y%))
This SQL generates the most recent link state message for a particular interface.
Unable to add user to syslogins table. Implicit conversion from datatype INT to VARCHAR is not allowed. Use CONVERT function to run query.
Cisco Systems' Customer Information Online (CCO) system provides online information and electronic services to Cisco direct customers and business partners. Basic CCO services include general Cisco information, product announcements, descriptions of service offerings, and download access to public and authorized files, including release notes and software. Maintenance customers receive a much broader offering, including technical notes, the bug database, and electronic mail access to the TAC. (Maintenance customers must have authorization from their Cisco contract administrators to receive these privileges.)
For dialup or Internet users, CCO supports Zmodem, Kermit, Xmodem, FTP PUT, Internet e-mail, Telnet, rlogin, and fax download options. Internet users also can retrieve files from CCO using FTP.
Registration for CCO is handled on line. To reach CCO via the Internet, use Telnet or FTP to
cio.cisco.com
(131.108.89.33). To reach CCO by dialup, use 415 9038070 (Mountain View, California) or 33 1 6446 4082 (Paris, France).
|
Copyright 1988-1995 © Cisco Systems Inc.