|
|
This document discusses CiscoWorks on AIX release 3.0.3. Use this document in conjunction with the CiscoWorks on AIX Installation and Reference Guide.
This release note contains the following sections:
CiscoWorks 3.0 retains most of the features of CiscoWorks 2.1. In addition, new features were added. 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 provided by other CiscoWorks applications.
For more detailed information on CiscoWorks features and functionality, see the CiscoWorks on AIX Installation and Reference Guide and the online help system. (The comprehensive online help system makes a printed user guide unnecessary.)
CiscoWorks requires the following hardware:
CiscoWorks requires the following software and conditions.
The Program Temporary Fix (PTF) list in the Software Requirements Checklist of the CiscoWorks on AIX Installation and Reference Guide is incomplete. The correct list follows. Your host requires the most recent IBM Program Temporary Fix (PTF) that resolves each of the following IBM authorized program analysis reports (APARs).
| AIX Version | IBM APAR | Most Recent IBM PTF as of Jan. 31, 1996 |
|---|---|---|
3.2.5 | IX44409 | U435114 |
| IX46381 | U435180 | |
| IX45547 | U440529 | |
| IX45257 | U435178 | |
| IX38605 and IX43714 | U434997 | |
| 4.1.x | IX49139 | U436874 |
Although Workgroup Director is now part of CiscoWorks, the Workgroup Director User Guide shipped with CiscoWorks describes it as a separately installable product. When you use Workgroup Director with CiscoWorks, ignore the following parts of the guide:
| Actual NetView Menu Location | NetView Menu Described in Online Help |
|---|---|
| Administer> CW - CiscoConnect | Administer> CiscoWorks System> CW - CiscoConnect |
| Monitor> Description> CW - Contacts | Tools> Contacts |
| Administer> CW - Software Images> CW - Device Software Manager | Administer> CiscoWorks Devices> CW - Device Software Manager |
| Administer> CW - Security> CW - SA Password | Administer> CiscoWorks System> CW - SA Password |
| Administer> CW - Security> CW - Security Manager | Administer> CiscoWorks System> CW - Security Manager |
When you are using the System Management Interface Tool (SMIT) to install the CiscoWorks software from the CD-ROM onto the AIX 3.2.5 system, and you reach the Multi-Select List dialog on page 3-10 of the CiscoWorks on AIX Installation and Reference Guide (or page 7 of the CiscoWorks CD Installation Instructions), follow the instructions carefully.
| **before**Click the individual object names that you want to install, but do not click the Select All button at the bottom of the dialog window. The Select All button activates a SMIT software bug.@@before@@ | Caution **after**Click the individual object names that you want to install, but do not click the Select All button at the bottom of the dialog window. The Select All button activates a SMIT software bug.@@after@@ |
This section describes notes and general caveats that apply to CiscoWorks 3.0. General caveats are noted first, followed by application-specific caveats which are listed alphabetically.
The web browser shipped with CiscoConnect is Netscape Navigator 1.12 (not Spyglass Mosaic as indicated on page 1-3 of the CiscoWorks on AIX Installation and Reference Guide). Each customer is licensed to use Netscape on the same AIX host on which CiscoWorks is installed.
After each user runs Netscape for the first time, a preferences file appears in his or her home directory. Use a text editor change the HOME_DOCUMENT entry in each user's ~/home/.netscape-preferences file to read:
http://localhost:tcpport/CiscoConnect/Index:shtml?username
localhost is the host on which CiscoWorks is installed, as reported by the AIX hostname command.
tcpport is a value from the CiscoConnect configuration dialog in SMIT. To ascertain that value:
Step 1 Log in as the root user and start SMIT.
Step 2 Click Communications Applications and Services, then click Cisco Network Management Applications fort AIX, then click CiscoWorks 3.0, then click Configure, then click CiscoConnect.
Step 3 On the CiscoConnect dialog, leave the Modify Aliases field as no, then click Do.
Step 4 On the CiscoConnect characteristics dialog, note the value in the TCP port number field.
Step 5 Terminate SMIT by pressing F12 or by clicking Exit SMIT on the Exit menu.
username is the user's AIX username, which must have been entered into the Product Group Users field in the CiscoWorks configuration dialog of SMIT. To verify that a username is in the Product Group Users list:
Step 1 Log in as the root user.
Step 2 On the command line, type:
Step 3 Verify that username appears in the set of names.
If you want to run CiscoConnect without having logged in as a Ciscoworks Product Group User, you must have an additional environment variable called NMS_CC_USER. The procedure for setting this variable depends on each user's shell. Follow a procedure like the one under "Use of PostScript Printer," and substitute a variable named NMS_CC_USER with a value of username.
Do not set NumLock on the keyboard while using CiscoWorks. The NumLock key disables certain mouse operations.
CiscoWorks requires a PostScript printer. By default, it assumes its printer to be the host's default printer. If the host's default is not a PostScript device, and if you do not want to change the default printer to be your PostScript printer, perform the following procedure for each user before starting CiscoWorks.
Step 1 Log in as the root user.
Step 2 Determine the shell each CiscoWorks user is using by entering a command like the following. The following command is for user william:
cd /users/william
ls .kshrc .cshrc
For the K shell, AIX responds
.kshrc
For the C shell, AIX responds
.cshrc
Step 3 For a user using the K shell, use a text editor to add the following line to the .kshrc file.
PSqueuename
For a user using the C shell, use a text editor to add the following line to the .cshrc file.
PSqueuename
where PSqueuename is a PostScript device queue name.
Step 4 For a user using the K shell, enter the following command to ensure that the changes made to the .kshrc file become a part of the user's active environment:
. .kshrc
source .cshrc
Step 5 Verify that the changes to the .kshrc or .cshrc file are active by viewing all active environment variables.
For the K shell, type
For the C shell, type
printenv | more
Be sure that the $LPDEST variable appears in the set of displayed variables.
Each user's default printer is unchanged, but CiscoWorks prints to the device named by the $LPDEST variable.
The $NMSROOT variable must be set before you start the upgrade or 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 procedure after the upgrade is completed: [CSCdi39917]
Step 1 Log in to your Sybase 4.9.2 server using the following commands:
The above commands produce a list of the CiscoWorks application's names followed by a number 1 or a 0. A zero (0) indicates that you have not set privileges for that application, and a one (1) indicates that you have set privileges.
Step 2 Exit the Sybase server.
Step 3 Perform the following command:
This command sets the environment for CiscoWorks 3.0
Step 4 Start Security Manager and set the CiscoWorks application's privileges using the output of the previous isql commands.
From the output, choose the applications that had a one (1). These applications previously had privileges set in Security Manager. Once you have re-created privileges for applications that have a one (1), your application group and domain privileges will be as they were before your upgrade.
Device names with an embedded slash (/) character are not supported. [CSCdi39314]
The following caveats apply to individual applications in the CiscoWorks package.
The caveats in this section apply to the AutoInstall application.
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]
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 NetView 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.
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. The enable password must be entered if enable secret is not configured. Enable secret can be configured on the router for Cisco IOS Release 10.3 and later.
When the X server cannot allocate colors, nmadmin may return a segmentation fault with the following error message:
Warning: Cannot allocate colormap entry for xxxxxx
When many X clients are using the same X display server and its resources are over-utilized (the properties of the X display server are a factor), Xlibs may return the following error or a segmentation core dump may occur:
Color cannot be changed.
Close some of the other X-client applications you are currently running to fix these color problems. [CSCdi39531]
In rare circumstances, 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:
ServName xxx
Substitute the name of your CiscoWorks workstation, without the domain name (everything up to the first period) for xxx. [CSCdi40398]
Some CiscoConnect screens may need to be updated manually when you use the Netscape browser. The Spyglass browser tries to save time by storing the most recently viewed screens, but some of the screens change dynamically, so the stored version may not match the most current version. Therefore, you will need to click on the Reload button to get the most current version. This is the button with three green arrows pointing into a circle. 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.
The Database to Device operation will fail when:
If this occurs, the following error message appears:
Confman error in Device to Database. Toolkit storing running configuration error. Timeout waiting for peer to respond. Please check system setup and community string.
The error occurs because the application times out while waiting for the SET operation to complete. [CSCdi40473]
These caveats apply to either or both of the Device Polling and Polling Summary applications.
You may receive the following error message when you select Activate Changes in Device Polling or Polling Summary:
Unable to activate changes. Please check if the nmpolld process running.
There are two workarounds to this problem:
To restart the nmpolld daemon:
Step 1 Enter the following as root:
Step 2 Check to see if you have any other nmpolld daemon processes running on your system because you can have multiple daemons running.
Step 3 Perform Step 1 for every nmpolld daemon you find.
[CSCdi37450]
The timestamp on Configuration Summary Reports run from Polling Summary uses Greenwich Mean Time (GMT) instead of the local time. [CSCdi40004]
If you receive the following error message:
Sybase SQL error: Bad findmaxvalue SQL statement for the polls table
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]
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 non-fixed-width fonts. [CSCdi39118]
In the Export Data window, device selection has the following restrictions:
Device host.cisco.com not found in pollgroup XXX.
These two applications can be run by all users, even if they do not have the appropriate privileges set. [CSCdi40179]
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]
If you try to change the currently authorized user in Device Polling and Polling Summary, the username will change even if the attempt failed, 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.
If you set service password-encryption configuration to On and then set it to Off later, 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:
Toolkit get config register Operation is not allowed.
[CSCdi36385]
Device Software Manager (nmdevswman) is unable to upgrade Cisco 2500 series routers that have dual flash banks. The dual flash Cisco 2500 series routers must be upgraded manually. [CSCdi37793]
The caveats in this section apply to the online help system for CiscoWorks.
The CiscoWorks installation puts the X resources file for HyperHelp in the /usr/lib/X11/app-defaults directory. As different systems have different types of X-Window installations, the CiscoWorks applications do not always read this resource file. When the resource file is not read, the text is sometimes unreadable. Here are options for how to make sure this resource file is read:
[CSCdi40309]
The caveats in this section apply to the PathTool application.
Network numbers appear in the source and destination list while you are using the resolv+ library. CiscoWorks does not support resolv+, so use a different name resolver with CiscoWorks. [CSCdi16541]
Some Cisco devices appear in the graphical display as non-Cisco devices. [CSCdi43449]
The caveats in this section apply to Software Library Manager.
The following tables indicate the combinations of Cisco IOS releases and Cisco products that are supported by Software Library Manager.
Software Library Manager supports all Cisco IOS releases for the Cisco 2500 series (Run-From-Flash models) routers that use the Flash Image Manager scripts.
| 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)+ |
This application is unable to support all Cisco IOS releases due to the following problems:
The caveats in this section apply to Sybase 10 and database administration.
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]
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]
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:
http://www.cisco.com.
cio.cisco.com.
For a copy of CIO's Frequently Asked Questions (FAQ), contact cio-help@cisco.com. For additional information, contact cio-team@cisco.com.
tac@cisco.com. To obtain general information about Cisco Systems, Cisco products, or upgrades, contact 800 553-6387, 408 526-7208, or cs-rep@cisco.com.
|
|