|
|
CiscoWorks 3.0 Release Note (SunOS, Solaris, and HP-UX)
This document discusses the CiscoWorks 3.0 release. It includes information on modifications and improvements to previous CiscoWorks releases and other noteworthy material. Use this document in conjunction with the CiscoWorks Installation and Reference Guide publication.
This release note document describes the following:
CiscoWorks Release 3.0 Features
CiscoWorks 3.0 retains many of the features of CiscoWorks 2.1. In addition, new features were added and some features were removed. CiscoWorks 3.0 includes the following new and improved features:
The Log Manager application is no longer part of CiscoWorks, though some of its functions are performed by other CiscoWorks applications.
For more detailed information on CiscoWorks features and functionality, see the CiscoWorks Installation and Reference Guide publication and the online help system.
CiscoWorks allows you to manage the following Cisco devices:
CiscoWorks Documentation Errata
The CiscoWorks CD Installation Instructions publication contains some errors. Make the following modifications to the information provided in the booklet:
On pages 9 and 12, the CiscoWorks volume names should read:
/cdrom/ciscoworks/SunOS4.1.3
and
/cdrom/ciscoworks/Solaris2.4
"ciscoworks" should be all lower case letters, instead of the upper case letters printed in the booklet.
The CiscoWorks Installation and Reference Guide publication contains some errors. Make the following modifications to the information provided in the manual:
CiscoWorks Release 3.0 Caveats
This section describes the notes and general caveats that apply to CiscoWorks 3.0 on the SunOS operating system, Solaris operating system or HP-UX system. General caveats are noted first, followed by application-specific caveats.
You will need approximately 350 MB of disk space to install CiscoWorks and Sybase on your machine. In addition, SunNet Manager or HP OpenView must be installed on your system before you install CiscoWorks.
CiscoWorks may have problems if it is installed on a multihomed workstation. These problems will only affect applications that initiate SNMP requests that result in the managed device using Trivial File Transfer Protocol (TFTP) to send or 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 for the SNMP request. For TFTP-related requests, the address of the TFTP server (the local CiscoWorks workstation) is included. However, this is not the same as the source Internet Protocol (IP) address in the SNMP packet, as it is an address that is encoded in the varbind list. CiscoWorks examines the configuration of the local workstation and uses the network address of the first interface 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 use this TFTP server address for the TFTP transfer.
A problem occurs 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, perform the following steps:
If CiscoWorks still does not work correctly, you are experiencing a different problem from 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 to shut down all interfaces you do not want used thereby forcing CiscoWorks to select the interface you leave up. You can determine which network address CiscoWorks uses by examining packet traces (SNMP SET requests that initiate the TFTP transfer will include the TFTP server address as an instance ID in the varbind list), or by watching the console on the managed device when you use the application (you will see messages indicating which address the device is trying to contact via TFTP). [CSCdi22313]
Upgrading from CiscoWorks 3.0 Beta Release to CiscoWorks 3.0 FCS Release
Perform the following procedure if you want to upgrade your CiscoWorks installation from the CiscoWorks 3.0 Beta Release to the CiscoWorks 3.0 FCS Release. You can skip this procedure if you did not install the CiscoWorks 3.0 Beta Release.
The Sybase option select into/bulkcopy was not set for the polldb database when CiscoWorks 3.0 Beta Release was shipped, so you cannot create new polling tables with Device Polling. You can, however, continue to use the sample tables distributed with CiscoWorks. If you do want to create your own tables using Device Polling (nmpoll), you need to modify the polldb database. To modify the database, perform the following steps:
Upgrading from CiscoWorks 2.x to CiscoWorks 3.0
The $NMSROOT variable must be set before you start the upgrade; otherwise the upgrade will fail with an error. [CSCdi39702]
When you upgrade from CiscoWorks 2.x to CiscoWorks 3.0, the top-level privilege bit set under Security Manager is removed and no privileges are enabled. To fix this problem, perform the following steps after you complete the upgrade:
[CSCdi39917]
Device names with an embedded slash (/) character are not supported. [CSCdi39314]
Installing CiscoWorks 3.0 on an NIS Client Running SunOS
The installation process on SunOS requires you to run the installation script, modify the kernel configuration file, and run the configuration script. If you want to modify the kernel manually instead of letting the script update it automatically, perform the steps in the section "Manually-Entered Sybase Modifications to the Kernel Configuration File" in the CiscoWorks Installation and Reference publication.
To complete the installation process on your Sun workstation that is also a Network Information Service (NIS) client, perform the following steps:
Your installation and configuration are now complete.
While the cw_enlarge script runs, answer the prompts. This script sets database thresholds for disk space based on your database size.
If you need to create additional space for the databases and transaction log, enter the following command:
Before you validate your installation as explained in the CiscoWorks Installation and Reference publication, verify the NIS sybase users by logging in as root and entering the following command:
This section describes general caveats that apply to CiscoWorks 3.0 on the Solaris operating system.
Migrating from CiscoWorks 3.0 on SunOS to CiscoWorks 3.0 on Solaris
The upgrade procedure is described in the publication, Addendum to the CiscoWorks Installation and Reference on SunOS, Solaris, and HP-UX.
Window System Security for CiscoView
Read the file $NMSROOT/etc/README for information on how to set window system security properly for your CiscoView installation. This file discusses whether to set xauth or nonxauth mode.
The caveats in this section apply to the AutoInstall application.
Enabled Router Even if TFTP Fails
If the TFTP transfer to set the IP helper address to the neighbor router fails during an autoinstall, an error message is displayed 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 installed using AutoInstall. No warning messages appear if you attempt to autoinstall other interface types. [CSCdi24605]
Running the Change Symbol Type Command in HP OpenView
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 CiscoConnect application.
Configuring the Router's Enable Password
If an enable secret password is configured on the router, this password overrides the enable password. When you enter the passwords in CiscoConnect, you must enter the enable secret password, if enable secret is configured on the router. Enter the enable password if enable secret is not configured. Enable secret can be configured on the router for software versions greater than IOS 10.3.
Installing Required Shared Libraries for CiscoConnect
CiscoConnect requires that certain shared libraries be installed on the system where it is running.
The file /usr/lib/libndbm.sl is required on HP-UX systems so the Perl interpreter shipped with CiscoConnect can run. If your HP-UX machine does not have this library, you must install it. The library file should come with the HP-UX system, but some systems may not have it installed.
If you have any problems locating shared libraries for the SunOS, Solaris, or HP-UX platforms, contact Cisco Systems immediately for help. You will know that you do not have the required libraries installed if the CiscoConnect application does not run and the $NMSROOT/log/cc_error_log log file lists the missing file. You will see the following types of errors:
In both cases, xxx is the name of the missing library.
Unable to Allocate or Change Colors
When the X-server cannot allocate colors, nmadmin may return a segmentation fault with the following error message:
When many X-clients are using the same Xdisplay server and its resources are over-utilized (the properties of the Xdisplay server are a factor), Xlibs may return the following error or a segmentation core dump may occur:
Close some of the other x-client applications that are currently running to fix these color problems. [CSCdi39531]
In rare cases, the httpd daemon may refuse to start because it cannot obtain the server name. An error message will instruct you to follow the ServName configuration directive. If you experience this problem, add the following line to the end of the file $NMSROOT/lib/httpd/conf/httpd.conf:
Substitute the name of your CiscoWorks workstation, without the domain name (everything up to the first period) for xxx. [CSCdi40398]
Some CiscoConnect windows may need to be updated manually when you use the Spyglass browser. The Spyglass browser tries to save you time by storing the most recently viewed windows. However, some of the windows change dynamically, and the stored version may not match the most current version. Click on the Reload button to get the most current version. This is the button with three green arrows pointing in a circle, similar to the common recycling symbol. If you use the hypertext links rather than clicking on the Home, Forward, and Back icons in the browser, you will find this to be less of a problem.
The caveats in this section apply to the Configuration Management application.
Database to Device Operation Fails
The Database to Device command will fail in the following cases:
If this occurs, the following error message appears:
The error occurs because the application times out while waiting for the SET operation to complete. [CSCdi40473]
The Configuration Management online help topic "Copying the Configuration File to the Database Using nmconfig" is erroneously titled and also contains errors in its text. It should be titled as follows: "Getting the Current Configuration File Using nmconfig". The text should read as follows:
You can use the nmconfig command to get the current device configuration file into the log directory with the -l option. The following is an example of the nmconfig command:
Device Polling and Polling Summary
The caveats in this section apply to the Device Polling, the Polling Summary application, or both.
Activate Changes Does Not Always Succeed in Device Polling or Polling Summary
You may see the following error message when you select Activate Changes in Device Polling or Polling Summary:
There are two workarounds to this problem:
To restart the nmpolld daemon, perform the following steps:
[CSCdi37450]
Configuration Summary Report Timestamp Incorrect
The timestamp on the Configuration Summary Reports run from Polling Summary uses Greenwich Mean Time (GMT) time instead of the local time. [CSCdi40004]
If you receive the following error message, the Sybase server is not running or the Sybase login failed:
Check to see if the Sybase server is running and that you are able to log in to Sybase. Restart the Sybase server if it is not running. [CSCdi33832]
Displaying Polling Summary Reports in Other Fonts
By default, Polling Summary (nmsummary) reports are displayed with fixed-width fonts in Browser windows. The report tables may not be aligned properly if you set the reports to be displayed with fonts that are not fixed-width. [CSCdi39118]
In the Export Data window, device selection has the following restrictions:
Privileges Not Needed to Run Device Polling and Polling Summary
These two applications can be run by all users, even if they do not have the appropriate privileges set. [CSCdi40179]
Specifying Instances for a Device-Variable Pair
The Instance field in the Device Polling window does not clear when you select the Apply button after you specify an instance for a device-variable pair. Be sure to clear the field before you enter new text in the Instance field when you are setting a device-variable pair. See the nmpoll man page or Device Polling online help for information on how to specify instances. [CSCdi40170, CSCdi40174]
User Name Changes in Device Polling and Polling Summary
If you try to change the currently authorized user in Device Polling and Polling Summary, the username will change even if the attempt fails, and the new user is not the currently authorized user. [CSCdi40181]
The /tmp directory can run out of space if you leave the nmpolld daemon running and frequent changes are activated from Device Polling (nmpoll) or Polling Summary (nmsummary). This daemon logs status information in the file /tmp/nmpolldxxxx, where xxxx is the process ID of nmpolld. [CSCdi33754]
The caveats in this section apply to Device Software Manager.
Changing Password Encryption Configuration
If you set service password-encryption configuration to On and then later set it to Off, you must reconfigure all the passwords (line and enable). Device Software Manager (nmdevswman) parses the configuration file to retrieve these passwords. If the passwords are not reconfigured, the application will retrieve incorrect passwords. If the passwords are incorrect, you will see the following error message when you select the Upgrade command:
[CSCdi36385]
Unable to Upgrade 2500 Series Routers
Device Software Manager (nmdevswman) cannot upgrade 2500 series routers that have dual flash banks. The dual flash 2500 series routers must be upgraded manually. [CSCdi37793]
The caveats in this section apply to the HyperHelp online help for CiscoWorks.
The CiscoWorks installation puts the X resource file for HyperHelp in the /usr/lib/X11/app-defaults directory. Because different systems have different types of X Windows installations, the CiscoWorks applications do not always read this resource file. When the resource file is not read, the text may be unreadable. Use one of the following options to make sure this resource file is read:
[CSCdi40309]
The caveats in this section apply to the PathTool application.
HP OpenView SNMP Agent Problems
Due to strange behavior in the HP SNMP agent, the Path Tool application may not work properly. This 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 in completing its algorithm. [CSCdi24511]
Network Numbers in Source and Destination List
Network numbers appear in the source and destination list while you are using the resolv+ library. CiscoWorks does not support resolv+. To work around this problem, use a different name resolver with CiscoWorks. [CSCdi16541]
The caveats in this section apply to Software Library Manager.
Releases Supported by Software Library Manager
The following tables indicate the Cisco IOS releases and the Cisco Systems products that are supported by Software Library Manager.
Software Library Manager supports all Cisco IOS releases for the 25xx (Run-From-Flash models) routers that use the Flash Image Manager scripts.
Table 1 : 25xx (Run-From-RAM models) and 3000 (Run-From-RAM models)
Table 2 : 4000 Model
Table 3 : 4500 Model
Table 4 : 7000/7010 Models
Table 5 : AGS+ Model
This application cannot support all Cisco IOS releases due to the following problems:
If you see the following message when you run the SunNet Manager grapher from CiscoWorks Real-Time Graphs or from Health Monitor, check to see if the device is in the SunNet Manager map.
[CSCdi39551]
The caveats in this section apply to Sybase 10 and database administration.
Changing the Number of Available Devices in the SQL Server
The number of devices in an SQL server is preconfigured. To change this value, you must reboot the SQL server. If there are enough unused devices in an SQL server to configure a new database, the database configure script runs to completion. Otherwise, the user is informed that the server needs to be reconfigured to allow for additional devices. The target server needs to create a device for every device that was being used by the source database. [CSCdi38739]
Choosing Partition Size for Sybase
Sybase 10 does not support partitions that are larger than 2 gigabits. If you install Sybase on a partition that is larger than 2 gigabits, you will see an error indicating that there is not enough space for Sybase. While this is not true, you need to install Sybase on a smaller partition.
The Sybase server is started as root from nmstartup. Exercise caution while creating devices in the Sybase server as this will cause the file to be overwritten by the Sybase server. [CSCdi35798]
The caveats in this section apply to the Sync w/Sybase application.
Application Exit After libc Modifications (SunOS only)
The Sync w/Sybase application may exit 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 another name resolver. [CSCdi23676]
Cisco Information Online (CIO) is Cisco Systems' primary, real-time support channel. Maintenance customers and partners can self-register on CIO to obtain additional content and services.
Available 24 hours a day, 7 days a week, CIO provides a wealth of standard and value-added services to Cisco's customers and business partners. CIO services include product information, software updates, release notes, technical tips, the Bug Navigator, configuration notes, brochures, descriptions of service offerings, and download access to public and authorized files.
CIO 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 CIO (called "CIO 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 CIO provides richly formatted documents with photographs, figures, graphics, and video, as well as hyperlinks to related information.
You can access CIO in the following ways:
For a copy of CIO's Frequently Asked Questions (FAQ), contact If you are a network administrator and need personal technical assistance with a Cisco product that is under warranty or covered by a maintenance contract, contact Cisco's Technical Assistance Center (TAC) at 800 553-2447, 408 526-7209, or
Copyright 1988-1996 © Cisco Systems Inc.
#
cd /cdrom/ciscoworks/SunOS4.1.3
#
./extract_unbundled
-c /cdrom_install_directory
-c
option, the /cdrom directory is used as the default.
#
pkgadd -d /cdrom/ciscoworks/Solaris2.4
1 CSCOcw CiscoWorks 3.0
2 CSCOsyb CiscoWorks 3.x Sybase 10 Server
% bin/isql -Usa -P -SMYSYBASE10
1> sp_dboption polldb,"select into/bulkcopy",true
2> go
Database option `select into/bulkcopy' turned ON for database `polldb'.
1> checkpoint
2> go
% isql -Usa -P<your sa password>
1> use nms
2> go
3> setuser "SAnms"
4> go
5> select app_id,authority_ck from applications
6> go
% source $NMSROOT/etc/install.cshrc
cp vmunix vmunix.save
cd /usr/etc
mv ypbind ypbind.origin
#
cd /cdrom
#
./extract_unbundled
-c /cdrom_install_directory
#
reboot
login:
root
password:
rootpassword
#
#
/usr/tmp/unbundled/cwconfigure
#
cd /
#
umount /cdrom
#
eject /dev/
device_filename
#
/usr/nms
/etc/cw_enlarge
ypcat passwd | grep sybase
/usr/sbin/userdel
ld.so: lib
xxx
.so.1: not found
/lib/dld.sl: Can't open shared library: /usr/lib/lib
xxx
.sl
Warning: Cannot allocate colormap entry for xxxxxx
Color cannot be changed.
ServName
xxx
Confman error in Device to Database.
Toolkit storing running configuration error.
Timeout waiting for peer to respond.
Please check system setup and community string.
nmconfig -d device -s community_string -l logdir -D cw_domain -o getconf -U username -P password
Unable to activate changes. Please check if the nmpolld process running.
# kill -HUP nmpolld process_id
Sybase SQL error: Bad findmaxvalue SQL statement for the polls table
Device foo.cisco.com not found in pollgroup
XXX
.
Toolkit get config register Operation is not allowed.
xrdb -merge /usr/lib/X11/app-defaults/HyperHelp
IOS 10.0
IOS 10.2
IOS 10.3
Flash to TFTP
Yes
Yes
Yes
Load Flash
Yes
Yes
Yes
Get Config file
Yes
Yes
10.3(3)
IOS 10.0
IOS 10.2
IOS 10.3
Flash VPP Status
10.0(9)+
10.2(5)+
10.3(2)+
Flash to TFTP
Yes
Yes
Yes
Load Flash
Yes
Yes
Yes
Get Config file
Yes
Yes
10.3(3)+
IOS 10.0
IOS 10.2
IOS 10.3
Flash VPP Status
N/A
10.2(5)+
10.3(2)+
Flash dir Status
N/A
10.2(6)+
Yes
Flash to TFTP
N/A
Yes
Yes
Load Flash
N/A
Yes
Yes
Get Config file
N/A
Yes
10.3(3)+
IOS 10.0
IOS 10.2
IOS 10.3
Flash VPP Status
Yes
Yes
Yes
Flash to TFTP
Yes
10.2(5)+
10.3(1)+
Load Flash
Yes
10.2(8)+
10.3(5)+
Get Config file
Yes
Yes
10.3(3)+
IOS 10.0
IOS 10.2
IOS 10.3
Flash VPP Status
Yes
Yes
Yes
Flash to TFTP
Yes
10.2(5)+
10.3(1)+
Load Flash
Yes
Yes
Yes
Get Config file
Yes
Yes
10.3(3)+
Success: timestamp = 810946175.78399
cannot dispatch request (Fatal error: cannot find group:
"lsystemCPUload" in default schema: "snmp-mibII")
http://www.cisco.com.
cio.cisco.com.
ciohelp@cisco.com.
For additional information, contact
cioteam@cisco.com.
tac@cisco.com.
To obtain general information about Cisco Systems, Cisco products, or upgrades, contact 800 553-6387, 408 526-7208, or
csrep@cisco.com.
