|
|
This document discusses the CiscoWorks 2.1 Release (support for HP OpenView for SunOS and
HP-UX), including information on modifications and improvements to previous CiscoWorks releases, as well as other noteworthy material.
This release note document describes the following:
The CiscoWorks Software Release 2.1 reinforces much of the functionality of the CiscoWorks 2.0.2 release, including the following:
Errata to the documentation follow. This information was unavailable at the time of printing. The documentation set on Cisco Connection Documentation CD-ROM will contain updates in the next released version.
The CiscoWorks Administration and Installation Guide contains the following errata.
The CiscoWorks Administration and Installation Guide incorrectly states that the default name for the CiscoWorks group is CscWorks. The default name is cscworks. [CSCdi32788]
The CiscoWorks User Guide contains the following errata.
An additional feature, called User Command, has been added to the Configuration Snap-In Manager application. This feature allows you to enter any UNIX or router command. This feature includes a README file.
The section "Upgrading Cisco Run-From-Flash Devices" has the following changes:
The section, "Invoking Sybase DWB from the Command Line," includes several menu selections that are reversed. For example, the text reads "Select Run>Report" and it should be "Select Report>Run."
This section lists notes and restrictions that apply to CiscoWorks Software Release 2.1.
General caveats are noted first, followed by application-specific caveats listed alphabetically. General caveats are those that may not map to a specific application.
This section describes general caveats associated with CiscoWorks applications. These caveats include database issues.
AutoInstall Manager, Software Inventory Manager, Software Library Manager, and Device Software Manager do not currently support the Cisco 4500. To upgrade Cisco 4500 software, refer to your Router Products documentation and manually upgrade the software. [CSCdi24142]
In addition, the Cisco 4500 may be displayed as a Cisco generic router after discovery. To assign the correct icon, use the Change Symbol Type command.
Before you install the Sybase software, either separately or by using the Sybase software supplied with CiscoWorks software, the network interface on your system must be present. For example, a system might have an Ethernet network interface.
On the Sun workstation, 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]
Under the Motif window manager (mwm), certain CiscoWorks applications display behind the OV window. This behavior is seen only in applications which have a popup window that displays before the application displays. For example, the message on a popup may be "Connecting to Sybase." The popup displays in the front, then disappears; then the application displays in front of the HP OpenView window and instantly retreats to the background. This windowing problem occurs on both Sun and HP machines. [CSCdi24207]
The Cisco 2500 may display as a Cisco 3000 in the Software Inventory Manager application and on your network map. This occurs when Cisco 2500 routers are running software releases before 9.21. If your Cisco 2500 has version 9.21 or later, your device displays correctly. To correct this problem, upgrade your router to 9.21 or later, or use the Change Symbol Type command on HP OpenView to correctly display the device as a Cisco 2500. [CSCdi20033] [CSCdi24603]
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 commands 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]
On Sun workstations, if the workstation hostname appears after the 200th line in /etc/hosts file, the Sun C library (libc) cannot resolve the hostname to an Internet Protocol (IP) address. This is caused by a name resolution bug in the Sun libc file. This may result in problems during the installation of HP OpenView. Ensure that the hostname of your network management system is listed at the beginning of the /etc/hosts file and includes the domain name for the host. This is a problem related to using the SunOS on HP OpenView. [CSCdi07681]
CiscoWorks may have some problems if it is installed on a multihomed workstation. These problems will only affect applications which initiate Simple Network Management Protocol (SNMP) requests resulting in the managed device using Trivial File Transfer Protocol (TFTP) to send/receive a file to or from the CiscoWorks workstation, for example, Device Software Manager or Configuration Manager. The problem lies in how CiscoWorks chooses a local network address to put in the SNMP request. For TFTP-related requests, the address of the TFTP server (the local CiscoWorks workstation) is included (note: this is not the same as the source IP address in the SNMP packet, but is an address that is encoded in the varbind list). CiscoWorks examines the configuration of the local workstation and will use the network address of the first interface it finds, that is currently up and not in loopback mode. For multihomed workstations, this may not be the same address that is used for the IP source address in the SNMP packet. The managed device will then use this TFTP server address in an attempt to perform the TFTP transfer.
The problem exists if there is no route from the managed device to the specified TFTP server network address. The CiscoWorks application will report that the TFTP transfer failed.
If you believe you might have this problem, follow these steps:
If CiscoWorks does not work correctly, you are experiencing some problem other than the one described here. Currently, the only workarounds are to ensure that your managed devices have routes to the workstation address that CiscoWorks uses, or shutdown all interfaces you don't want used (forcing CiscoWorks to select the interface you leave up). You can determine which network address CiscoWorks uses by examining packet traces (SNMP SET requests which initiate the TFTP transfer will include the TFTP server address as an instance ID in the varbind), or by watching the console on the managed device when you use the application (there will be messages indicating which address the device is trying to TFTP to). [CSCdi22313]
If your attempt to run nmlogreset when your transaction log is full, nmlogreset fails. The script may only partially remove some or no entries. However, if your transaction log is not full, the script will run successfully. You can clear the transaction log manually using the following isql command procedure at the UNIX prompt:
# $SYBASE/bin/isql -Usa -P 1 dump tran nms with no_log 2 go 1 use nms 2 go 1 checkpoint 2 go 1 use master 2 dump tran master with no_log 3 go 1 checkpoint 2 go 1 quit
[CSCdi23922]
CiscoWorks 2.1 is based on the OSF/Motif windowing system and therefore requires Motif key mapping. During SunOS 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, the Log daemon attempts to reestablish the connection with the Sybase dataserver once every 60 seconds until it succeeds. If the Log daemon 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]
If an entry for a TFTP user already exists in the /etc/passwd file, the current installation does not check to ensure the TFTP directory has write permission. Ensure that the entry resembles the following line:
tftp:*:100:56:tftp server:/usr/tftpdir:/bin/false
. In addition, ensure the directory permissions for the /usr/tftpdir or /usr/tftpboot are set to 777.
On HP-UX when you open an text editor window using xterm -e vi, the window does not display the initial 20 lines. If your environment variable EDITOR is set to vi, and you attempt to edit a file on your HP-UX machine, you will see this behavior. Resize the window by dragging the upper or lower edge of the window frame. This makes vi learn the window size properly and the whole file becomes fully visible.
The caveats in this section apply to the AutoInstall Manager application.
If a device exists in the HP OpenView database in one or more maps, the device must be removed from the database before the AutoInstall Manager application can be used. If you attempt to autoinstall the device while it resides in an OpenView map, the following error message displays:
Device hostname or IP address not unique
. Remove the device from all maps in which it exists. [CSCdi24503]
If the TFTP transfer to set the IP helper address to the neighbor router fails during an autoinstall, an error message displays warning of the TFTP failure. The enabled status of the router does not change to disabled, even though the helper address could not be set using the AutoInstall Manager. [CSCdi24607]
Only devices attached to Serial interfaces can be autoinstalled. No warning messages appear if you attempt to autoinstall other interface types. [CSCdi24605]
The autoinstall feature requires IP forward protocol to be added to a remote router configuration. If you already have an IP forward protocol statement, such as UDP <port number> (a non-default port), on the remote router, CiscoWorks is not aware of it and adds another IP forward protocol statement to the router.
The previous forward-protocol UDP statement is lost and the router stops forwarding UDP packets destined for port xxx to the helper address. The AutoInstall Manager overrides the neighbor device configuration file in the following manner:
ip forward-protocol udp 285 --> Original configuration of the neighbor device ip forward-protocol udp --> Ciscoworks sticks this in the config file.
This effectively nullifies the first command. To resolve this problem, once the new device is up and running, Telnet to the neighbor device and manually remove the command
ip forward-protocol udp
. [CSCdi22012]
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 AGS+, but AutoInstall Manager may use an MGS icon to represent the device because AutoInstall Manager cannot distinguish between an AGS+ and an MGS. To confirm that your network is displaying the correct icon, use the HP OpenView Change Symbol 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 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 the umask correctly in your UNIX account, the Configuration Snap-In Manager may not be able to read the temporary files it generates. Consequently, the application cannot download the partial configuration file after you click 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 may display the previous error message after you click DoItNow. 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. To restore the window to its full size, 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, check 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.
The Device Management forms may fail after you attempt to add entries into several forms randomly. The Device Management application will work properly when you restart it. [CSCdi22123]
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 Polling application follow.
After a new CiscoWorks on HP OpenView installation, if you select Monitor>Device Polling>Options>Activate Changes, the Device Polling daemon, nmpolld, fails. To restart the daemon, select Administer>System>Process Manager. When the Process Manager window displays, click on Off to disable the Device Polling daemon. Then click on On to enable the Device Polling daemon. [CSCdi23097]
The Device Polling daemon fails if the database is full and you select the Activate Changes option. Use the SQL command, alter database, to increase the disk space for the database. [CSCdi23182}
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 the Device Polling daemon. [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 caveats for Flash Image Manager application also appear in this section.
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]
The Device Software Manager application uses the Flash Image Manager to upgrade run-from-Flash devices (for example, a Cisco 2500). The Flash Image Manager requires the last hop address for the interface which is used for upgrading the image on the device. When the Flash Image Manager runs trace on the router, it may not find the last hop address for the interface selected.
If only one route exists from the router to the TFTP server (workstation), then the last hop address is determined by the Flash Image Manager. If multiple routes exist from the router to the TFTP server, then the last hop address is determined only 50% of the time. If the application is unable to determine the last hop address, it requires you to manually enter the information. [CSCdi24097]
The software upgrade performed by the Device Software Manager may be unable to locate the software image. This may occur when you upgrade the run-from-Flash device software. The Flash Image Manager first looks for the software image (specified in the "Upgrade Image File Name" in the entry box) in the $NMSROOT/software directory. This is the directory used by Software Library Manager to store all the images. If this image is present in the above directory, it copies it to the TFTP directory usually /tftpboot (SunOS) or /usr/tftpdir (HP-UX) and continues with the upgrade. If the image is not present in the above directory, it looks for it in the TFTP directory. If it is not present in the TFTP directory, an error displays that the image was not found. [CSCdi24509]
When the Device Software Manager application collects critical information for upgrading the device software, it uses the first VTY line password found in the configuration file. When a device has several VTY lines, you need to ensure that all VTY line passwords are the same (since CiscoWorks cannot differentiate between lines). The console line does not have to have the same password as the VTY password. [CSCdi24455]
A caveat for the Environmental Monitor application follows.
The window title of the Environmental Monitor is designed to display the full name of the device being monitored. If the device name is too long and the font for the window title is too large, the text for the device name is truncated in the window. To resolve this issue, you can specify that a smaller font be used for the window title. For instructions on changing window fonts, refer to your CiscoWorks User Guide. [CSCdi22121]
A caveat for the Global Command Scheduler application follows.
When using an HP-UX machine, an unauthorized user can use the Scheduler to send commands. An error message appears that indicates the user is not authorized, but the Scheduler window still displays. [CSCdi22740]
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 Release 2.1.
On Sun workstations, if the workstation hostname appears after the 200th line in /etc/hosts file, the Sun C library (libc) cannot resolve the hostname to an IP address. This is caused by a name resolution bug in the Sun libc file. This may result in problems during the installation of HP OpenView. It may also cause Sybase installation problems. Ensure that the hostname of your network management system is listed at the beginning of the /etc/hosts file and includes the domain name for the host. This is an HP OpenView Sun bug. [CSCdi07681][CSCdi24735]
If you are moving from SNM to HP OpenView and the cscworks username is already present in the /etc/passwd file, your installation may not work properly. If the Group ID for the cscworks user is not the same as the cscworks group ID, do the following:
During installation, the following files are installed into the /usr/lib directory if they are not already there: /X11R5/libXmu.sl, /X11R5/libXaw.sl, /libC.sl, /libC.ansi.sl. These files require less than 0.9 MB of disk space on the device which has /usr/lib mounted on it. Ensure that the device or partition where /usr/lib is located has enough disk space for these files.
The CiscoWorks Administration and Installation Guide incorrectly states that the default name for the CiscoWorks group is CscWorks. The default name is cscworks. [CSCdi32788]
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
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 will be lost:
# rm /tmp/interfaces
# rm $SYBASE/install/FIFO_config
# rm $SYBASE/interfaces
# umask 0
# /usr/tmp/unbundled/ncsconfigure
If the Device Polling daemon (nmpolld) is running after a new installation and you attempt to activate changes, the daemon stops. To resolve this problem, access the Process Manager application (Administer>System>Process Mgr) and turn the Device Polling daemon off by clicking Off. Then turn the daemon back on by clicking the On button. [CSCdi22950]
If the hostname of a HP-UX machine is longer than 8 characters, Sybase cannot be installed. Set the hostname to any string no longer than 8 characters to avoid this problem. Consult your system administrator on how to change the hostname.
If the DSQUERY environment variable is set, you will encounter installation problems while creating "nms" database. To avoid installation errors, unset this variable by entering
unsetenv DSQUERY
in C-Shell or set it to SYBASE by entering
setenv DSQUERY SYBASE
. [CSCdi23960]
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]
The caveats in this section apply to the Log Manager application.
Log Manager may display duplicate records after you rearrange columns in the Log Manager window. If you experience this problem, restart the Log Manager. [CSCdi20624}
If the Sybase dataserver is stopped and restarted after you start the Log Manager application, the Refresh button does not display new messages. The Log Manager does not reestablish the connection to the database once it has been stopped. Restart the Log Manager application to connect to the database. [CSCdi20853]
The caveats in this section apply to the Path Tool application.
You may experience a looping problem on the Path Tool application if the routers in your path have their routing tables misconfigured. The Path Tool detects a cyclic path in this situation and displays an error message requesting that you check the router routing configurations. This is a known SNMP agent bug. To resolve this issue, upgrade your router software to version 10.0. [CSCdi21237]
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]
Due to some strange behavior in the HP SNMP agent, the Path Tool application may not work properly. This behavior occurs when Path Tool tries to find a local route from an HP workstation. To fix this problem, add static default routes instead of using the workstation's address as the default route in the routing table. This will assist Path Tool is completing its algorithm. [CSCdi24511]
The caveats in this section apply to the Polling Summary application.
In the Export Data window, device selection has the following restrictions:
Device foo.cisco.com not found in pollgroup XXX
.
You may experience unusual behavior while using Device Polling and Polling Summary applications in the following situations:
This behavior occurs when the database transaction log segment is full. No error message appears to indicate the log is full. To resolve this issue, exit the application and increase the size of the transaction log segment by running $NMSROOT/etc/enlarge_nms. For more information on enlarge_nms, refer to the CiscoWorks User Guide. [CSCdi23922]
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:
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 Polling Summary 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]
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 application supports only one software image per platform per software version. Cisco recommends importing the enterprise image into the library. Enterprise images include a -k in the release name. If you attempt to import duplicate versions/platform images, the Software Library Manager will request you to confirm the image deletion from the library. [CSCdi23795]
The File>Import from Disk command is not present in the CiscoWorks HP-UX release. The
HP-UX machine does not support diskettes. [CSCdi23428]
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]
A caveat for the Sync w/Sybase application follows.
On Sun OS, you may experience the Sync w/Sybase application exiting abnormally. This may be due to modifications you have made to include the resolv+ library to libc. The current release of CiscoWorks software does not support resolv+. To resolve this problem, use some other name resolver. [CSCdi23676]
Caveats for HP OpenView on a Sun workstation follow. These caveats are provided for your information. Contact Hewlett Packard technical support for more information.
On Sun workstations, if the workstation hostname appears after the 200th line in /etc/hosts file, the Sun C library (libc) cannot resolve the hostname to an IP address. This is caused by a name resolution bug in the Sun libc file. This may result in problems during the installation of HP OpenView. It may also cause Sybase installation problems. Ensure that the hostname of your network management system is listed at the beginning of the /etc/hosts file and includes the domain name for the host. This is an HP OpenView Sun bug. [CSCdi07681][CSCdi24735]
Caveats for the HP-UX workstation follow. These caveats are provided for your information. Contact Hewlett Packard technical support for more information.
The nmconfig -c command file option will work only if all the command file parameters are correct. Please refer to the CiscoWorks User Guide for the correct syntax of command file arguments. [CSCdi24939]
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 commands:
# 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 running Configuration Snap-In Manager, the right section of the Command Set editing window may appear as a separate empty pane. To restore the window to its full size, use the size box in the lower-right corner to resize the window. This OpenWindows problem has been reported to its developer. [CSCdi15378]
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.
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]
Caveats for SunOS and the patch information follow.
If you are using SunOS Version 4.1.3 and OpenWindows Version 3.0 in combination with CiscoWorks Release 2.1, 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.
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
This section contains some frequently asked questions about CiscoWorks issues. 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
For technical assistance, call 800 553-2447 or 408 526-7209. You can also send e-mail to tac@cisco.com. To obtain general information about Cisco, Cisco's products, or upgrades, call
800-553-6387 or 408-526-7208. You can also send e-mail to cs-rep@cisco.com.
Cisco Connection Online (CCO) provides online information and electronic services to Cisco customers and business partners. Basic CCO services include general Cisco information, product announcements, brochures, descriptions of service offerings, and download access to public and authorized files. Customers with maintenance contracts receive a much broader offering, including technical tips, software updates, the Bug Navigator, configuration notes, release notes, and e-mail access to Cisco Technical Assistance Centers. CCO serves a wide variety of users through two interfaces that are updated and enhanced simultaneously: a character-based version and a multimedia version that resides on the World Wide Web (WWW). The character-based CCO (called "CCO Classic") supports Zmodem, Kermit, Xmodem, FTP, Internet e-mail, and fax download options, and is excellent for quick access to information over lower bandwidths. The WWW version of CCO provides richly formatted documents with photographs, figures, graphics, and video, as well as hyperlinks to related information.
To access CCO:
WWW: http://www.cisco.com
Telnet: cio.cisco.com (198.92.32.130)
Modem North America 408 526-8070; Europe 33 1 64 46 40 82
(vt100, N81, up to 14.4 kbps applicable to both North America and Europe)
Maintenance customers and partners can self-register to obtain full access.
For a copy of CCO's Frequently Asked Questions, send e-mail to cio-help@cisco.com. For additional information, send e-mail to cio-team@cisco.com.
|
Copyright 1988-1995 © Cisco Systems Inc.