Table of Contents

System Requirements for CW2000

Essentials System Configuration Recommendations

Determining Minimum System Configuration
Improving Essentials Server Performance
Improving Essentials User Report Response Time

CWSI Campus System Configuration Recommendations

Installation Notes

Essentials Installation Notes

Aborting Essentials Installation Procedure
Package Failures During Installing and Uninstalling
Uninstalling Essentials
Uninstalling Does Not Remove Packages If It Fails to Terminate dmgtd
Uninstalling Does Not Remove All Configuration Directories
Files Deleted After Uninstalling
Upgrade causes Error Logging on stderr Instead of isqllog.log
Upgrade Might Continue if Cisco Resource Manager 1.1 Process Fails to Stop
Upgrade from Cisco Resource Manager 1.1 to Essentials 2.0 Disables CWSI 2.1.1
Installation Requirement for /opt Directory or Link
Unable to Log In After Stopping System

CWSI Campus Installation Notes

Patch Requirement for JRE 1.1.6 on Solaris 2.5.1
Patch Requirement for Sun XServer Software
Increasing Swap Space
Reinstalling CWSI Campus 2.2
Starting CWSI Campus 2.2

Upgrading from CWSI 2.1.1 to CWSI Campus 2.2
Uninstalling CWSI Campus

Resource Manager Essentials

Supported Device Import Software
Essentials Supported Devices
Using Essentials with Token Ring Switching Products

Catalyst Software Versions Supported
Cisco IOS Versions Supported

Essentials Release Notes and Caveats

Server Caveats
Browser Caveats
Desktop Caveats
Administrator Caveats
Inventory Caveats
Device Configuration Caveats
cwconfig Command Caveats
Import Caveats
Software Management Caveats
Syslog Analysis Caveats
Case Management Caveats
Device Navigator Caveats

CWSI Campus

CWSI Campus Application Compatibility
Startup Information
X Terminal Access Not Officially Supported
Browser Support for CWSI Campus Online Help
Year 2000 Compliance
Online Help
CWSI Campus Error Messages
CWSI Campus Network Map

New Features for CWSI Campus Network Map
Important Notes and Caveats for CWSI Campus Network Map

VlanDirector

New Features for VlanDirector
Important Notes and Caveats for VlanDirector

UserTracking

New Features in UserTracking
Important Notes and Caveats for UserTracking

TrafficDirector

New Features for TrafficDirector
Important Notes and Caveats for TrafficDirector

AtmDirector

New Features for AtmDirector
Important Notes and Caveats for AtmDirector

CiscoView

New Features in CiscoView
Cisco IOS Information
Incrementally Installing Device Packages
Caveats Fixed in This Release
Troubleshooting
Installation Notes and Caveats
General Notes and Caveats

Troubleshooting

Asynchronous Network Interface (ANI)
Database Engine
CORBA Agent
RTPoller
Event Channel
Stopping and Starting CWSI Campus Daemons
When CWSI Campus Cannot Log Into AniServer

Documentation and Additional Resources
Service and Support
Cisco Connection Online

Release Notes for CW2000 (Solaris)

These release notes describe the new features and caveats for the components of the CiscoWorks2000 family of products:

• Cisco Resource Manager Essentials

• CWSI Campus

This document contains the following sections:

• System Requirements for CW2000     2

• Installation Notes     6

• Resource Manager Essentials     13

• CWSI Campus     43

• Documentation and Additional Resources     96

• Service and Support     97

• Cisco Connection Online     97

System Requirements for CW2000

The system requirements for Essentials and Essentials and CWSI Campus combined products are listed in Table 1.

http://www.cisco.com/kobayashi/sw-center/netmgmt/cw2000.

CWSI Campus requires patch 103640-17.tar or later for Java Runtime Environment 1.1.6 on Solaris 2.5.1. Refer to the Patch Requirement for JRE 1.1.6 on Solaris 2.5.1 section for additional information.

Note the following browser information:

• No browser is required for the Essentials server system. Client systems must have a supported browser installed. Refer to Installing Resource Manager Essentials and CWSI Campus on Solaris for more information.

• Set your browser with "accept all cookies" enabled.

• For browsers running on a PC, set your desktop to use small fonts and set your desktop color map to 256, 32768, or 65536 colors.

• Netscape Navigator version 4.05 can be downloaded from CCO at http://www.cisco.com/kobayashi/sw-center/netmgmt/cw2000.
  You can also access ftp://archive:oldies@archive.netscape.com/archive/index.html.

• Essentials is supported on the browsers shown in Table 2.

Essentials System Configuration Recommendations

This section provides more information to help you select a system that best meets your specific needs.

Determining Minimum System Configuration

Three major considerations can help you to determine your minimum system configuration requirements:

1. Consider the number of managed devices to be polled by Availability.

2. Consider the number of Syslog messages expected daily.

3. Consider the number of managed devices expected in Inventory and
Device Configuration.

Availability is the primary consideration, after which you can then consider syslog messages and managed device expectations and determine your needs accordingly.

Improving Essentials Server Performance

To improve system performance for Essentials, consider the following options:

• Reduce the number of managed devices polled by Availability.

• Increase the interval used by Availability to poll managed devices.

• Reduce the number of syslog messages saved to the CW2000 database.

• Increase the interval used by Device Configuration to collect information for managed devices.

Improving Essentials User Report Response Time

Table 3 lists system recommendations for Solaris running Essentials only.

CWSI Campus System Configuration Recommendations

For CWSI Campus, use a system configuration that supports the number of devices you want to manage using CWSI Campus and the number of end hosts you plan to manage using UserTracking. Select a configuration that will support the application with the higher requirement. For example, if you have 82 devices and 2500 end hosts, select the Ultra 10 or better. See Table 4 for recommended minimum system configurations. See Table 4 for the CWSI Campus recommended system configurations.

Installation Notes

Review the information in this section carefully before installing the product.

Essentials Installation Notes

The following sections contain information about installing the Essentials product.

Aborting Essentials Installation Procedure

If you abort the Essentials installation procedure before it completes, not all required components are installed, and Essentials will not operate successfully. To recover from an aborted installation, start the Essentials installation procedure from the beginning. [CSCdj64037]

Package Failures During Installing and Uninstalling

If you send any signal to setup.sh, the default signal handler (exit) is invoked. This behavior is intended to allow you to terminate the install at any time. If a CNTL-C (SIGINT) or other signal is sent to setup.sh during the package install phase, some packages do not install properly. It is recommended that you terminate the installation before the packages are added or after the packages are added.

In some cases, the uninstall fails during the CSCOxrts package. This failure indicates that the CSCOxrts and CSCOmd packages cannot be uninstalled. The workaround is to delete the /var/sadm/pkg/CSCOxrts/install/preremove file and run the uninstallation. The uninstallation will then run to completion. [CSCdk52988]

Uninstalling Essentials

If you install Essentials and CWSI Campus on the same machine, you cannot uninstall Essentials without first uninstalling CWSI Campus. Refer to Installing Resource Manager Essentials and CWSI Campus on Windows NT for more information.

Software Management stores images that are not removed by the Essentials uninstallation procedure. If you want to permanently remove Essentials, you must manually remove these files from /opt/CSCOpx/files/sw_images.

If you uninstall Essentials and restart the Windows NT system, the installation directory, /opt/CSCOpx, remains on the system. The following directories also remain:

• MS

• lib

• www

• objects

• vbroker

You can manually remove these directories after performing the uninstall procedure, or keep them on your system for future reference. [CSCdj74400]

Uninstalling Does Not Remove Packages If It Fails to Terminate dmgtd

If you run /opt/CSCOpx/bin/unintall.sh, the script exits quickly and a message is displayed that indicates dmgtd is terminated with SIGKILL.

The workaround is to run uninstall.sh again. [CSCdk48753]

Uninstalling Does Not Remove All Configuration Directories

Uninstalling Essentials does not remove all Device Configuration related directories in /var/adm/CSCOpx/files. To remove all Device Configuration related files, remove the /var/adm/CSCOpx/files/archive directory. [CSCdk50635]

Files Deleted After Uninstalling

If you move the configuration archive directory to a new location, for example, newDir, the Essentials uninstallation script deletes all files with the following extensions:

newDir/config/any_subdirectory/*running.cfg

newDir/config/any_subdirectory/*startup.cfg

newDir/config/any_subdirectory/*running.dfr

newDir/config/any_subdirectory/*running.dfc

newDir/config/any_subdirectory/*running.cmt

If you created your own files with these extensions, you must move them to a different directory before uninstalling Essentials.

Upgrade causes Error Logging on stderr Instead of isqllog.log

At the beginning of the database upgrade from Cisco Resource Manager 1.1 to Essentials, the upgrade program displays the messages "INFO: Database upgrade in progress," "INFO: View /opt/CSCOpx/dbupgrade/CSCOupgradedb.log," and INFO: /opt/CSCOpx/dbupgrade/sql/isqllog.log for details."

The file /opt CSCOpx/dbupgrade/sql/isqllog.log is empty. This information is logged in the product install log at /var/tmp/ciscoinstall.log. [CSCdk26802]

Upgrade Might Continue if Cisco Resource Manager 1.1 Process Fails to Stop

During the upgrade, the setup.sh waits up to 10 minutes for all Cisco Resource Manager 1.1 daemons to stop. After 10 minutes, it should exit and display a message; however, it does not exit. Instead, it prompts you with a request to continue the upgrade.

On a system where the Cisco Resource Manager 1.1 daemons do not stop, answer No to the continue prompt and exit/abort the install. Contact the TAC for further instruction. [CSCdk32626]

Upgrade from Cisco Resource Manager 1.1 to Essentials 2.0 Disables CWSI 2.1.1

If you have Cisco Resource Manager 1.1 and CWSI 2.1.1 installed, after the upgrade of Cisco Resource Manager 1.1 to Essentials 2.0, you can not to run CWSI 2.1.

You must continue the upgrade from CWSI 2.1 to CWSI Campus 2.2 to run CWSI Campus successfully.

Installation Requirement for /opt Directory or Link

Essentials must either install itself or a link to itself in the /opt directory. Without write access to the /opt directory, you cannot install Essentials. [CSCdk03648]

Unable to Log In After Stopping System

After performing a "stop system" request from the web, the browser disables the system to the point where you cannot restart the system using the browser.

You must log in to the server, and at the command prompt, enter the pdsys start command to restart the Essentials system. [CSCdk26767]

CWSI Campus Installation Notes

The following sections contain information about installing the CWSI Campus product. Review the following information before installing CWSI Campus 2.2.

Patch Requirement for JRE 1.1.6 on Solaris 2.5.1

Before installing CWSI Campus, you must install a patch for the Java Runtime Environment (JRE) 1.1.6 for Solaris 2.5.1 and reboot your system. To do this, follow these steps:

1. Go to the Sun Microsystems website for Solaris 7 Product Line, Java Runtime Environment (JRE) for Solaris 2.5.1 at the following URL:

http://www.sun.com/solaris/jre/index.html

2. Click Download JRE 1.1.6 for Solaris Production Release.

3. Click Submit to download the following default selections:

Version = JRE 1.1.6v3 Production Release (8/24/98)

Platform = Solaris 2.5.1/2.6 Sparc Edition JDK (Native Threads)

License Agreement = I have read and agree to the License terms.

4. Complete the personal information form and click Submit.

5. Under Download, click Patches for Solaris 2.5.1/2.6.

6. When the security warning is displayed, verify that the sparc_jdk_patches_tar.Z file name is displayed as the file that will be downloaded and click OK.

7. After the file has been downloaded to your system, enter the following command to untar the file:

# zcat sparc_jdk_patches_tar.Z | tar xvf -
 

8. Four files are decompressed from this tar file: 105490-04.tar, 103566-25.tar, 103640-17.tar, and 105280.tar. Each file contains a Solaris patch. For Solaris 2.5.1 and CWSI Campus, you must install 103640-17.tar or later.

9. Enter the following command:

# tar -xvf patch_filename
 

where patch_filename is the patch file, in this case 103640-17.tar.

10. Change to the patch_filename directory and follow the instructions in the Install.info file to install the patch.

11. Reboot your system.

Patch Requirement for Sun XServer Software

XServer software occasionally crashes when CWSI Campus topology is displayed. This might be related to the presence of a specific (but undetermined) device in the ANI database. This is a bug in the Sun XServer software, which is fixed by patch 105790 from Sun.

Increasing Swap Space

CWSI Campus performance is greatly affected by the performance of the virtual memory subsystem in Solaris. Therefore, increase your swap size to 300 MB.

Reinstalling CWSI Campus 2.2

If you have installed CWSI Campus 2.2, and you need to reinstall it, you must manually stop all running processes manually by entering the following commands:

ps -ef|grep CSCOcwsi
kill -9 process_id
 

Reinstall CWSI Campus 2.2. [CSCdk32436]

Starting CWSI Campus 2.2

After installing CWSI Campus 2.2, wait approximately 5 minutes before starting the product. If you attempt to start the product too soon, the following error message is displayed:

osagent could not find the object object_name.
ANI server
 

Click OK, wait a few minutes, and then start the product again. This error does not affect product operation.

Upgrading from CWSI 2.1.1 to CWSI Campus 2.2

To upgrade from CWSI 2.1.1 to CWSI Campus 2.2, follow these steps:

Step 1 If you have CWSI Campus 2.2 (beta version), you must uninstall this version before installing the released CWSI Campus 2.2. version.

Step 2 Close all CWSI Campus windows before upgrading and reinstalling CWSI Campus. Otherwise, the install process aborts while trying to overwrite files that are in use.

Step 3 Start the install process using the installation guide.

The install process looks for any previous CWSI Campus installation and its version.

Step 4 You are prompted to confirm that you want to preserve the database and the data files. If you click No, these data files are overwritten. If you click Yes, a backup directory is created under the CWSI Campus installation directory.

The CWSI Campus database cwsi.db and the data files (ani.properties, atmd.properties, and communities.dat) are copied into this directory. These files are copied back to their original locations when the installation is complete.

The system displays information about the previous installation of CWSI: the installation folder, the database folder, the seed device, and the components that are installed (CiscoView, TrafficDirector and AtmDirector) if any.

In Solaris, the path of the web browser is also displayed.

The CiscoView devices directory is deleted to allow you to install the latest version of the device packages and avoid the possible incompatibility with the shared device files. You must select the previously installed packages in addition to the new packages.

Step 5 Reinstall and select all the optional CWSI Campus components (TrafficDirector, AtmDirector, and CiscoView) that were installed previously.

Step 6 Terminate the previously running dvtrapd process (a process used by TrafficDirector) by entering the following commands:

# ps -ef | grep dvtrapd
# kill process_id

Uninstalling CWSI Campus

Note the following caveats:

• Before uninstalling CWSI Campus, close all CWSI Campus windows.

• After uninstalling CWSI Campus, some directories and files might remain. If this is the case, delete these directories and files manually. If you are unable to delete them, and the message "the file is in use" appears, reboot your machine. You should be able to delete the remaining files.

• Although TrafficDirector and CiscoView are stand-alone products, they cannot be uninstalled separately from the CWSI campus package because they share components with CWSI Campus.

You can uninstall CWSI Campus if necessary by entering the following commands:

cd /opt/CSCOcwsi/bin
./uninstall.sh

Resource Manager Essentials

This section contains information, notes, and caveats for Resource Manager Essentials.

Supported Device Import Software

Essentials lets you import device information from both local and remote network management databases identified in Table 5.

Essentials can be installed on the same machine as HP OpenView, OpenView Professional Suite, CiscoWorks 4.0, and CWSI Campus without any compatibility problems.

For remote device imports, the remote server must be a Solaris, HP-UX, or AIX machine. Essentials does not support remote device imports from Windows NT machines.

Essentials Supported Devices

Essentials supports the devices listed in Table 6 through Table 10. See the "Cisco IOS Versions Supported" section for information on the supported Cisco IOS versions. See the "Using Essentials with Token Ring Switching Products" section for the devices the Essentials Software Management module supports.

It is possible to insert an ATM Signal Processor (ASP) card into slot 13 of a Catalyst 5500 chassis. Other LS1010 cards might also be inserted in the chassis. Due to hardware limitations, the supervisor card in the Catalyst 5500 cannot accurately detect the presence or status of these cards. As a result, Essentials inventory will not display this hardware correctly in certain reports, and available slots might be inaccurate. Hardware enhancements have been proposed to address this problem.

Table 6: Inventory Manager Supported Devices

Product Family	Devices Supported
Cisco CS500	CS500
Cisco/CiscoPro 7xx	751, 752, 753, 761, 762, 765, 766, 771, 772, 775, 776
Cisco/CiscoPro 10xx	1000, 1003, 1004, 1005, 1020
Cisco/CiscoPro 16xx	1601, 1602, 1603, 1604, 1605
Cisco 2xxx	2000, 2102, 2202
Cisco/CiscoPro 25xx	2500, 2501, 2502, 2503, 2504, 2505, 2506, 2507, 2508, 2509, 2510, 2511, 2512, 2513, 2514, 2515, 1516, 2517, 2518, 2519, 2520, 2521, 2522, 2523, 2524, 2525, 2501CF, 2502CF, 2501LF, 2502LF
Cisco 26xx	2601, 2610, 2611
Cisco/CiscoPro 3xxx	3000, 3101, 3102, 3103, 3104, 3202, 3204, 3620, 3640,
Cisco switching access concentrator	MC3810
Cisco/CiscoPro 4xxx	4000, 4000-M, 4500, 4500-M, 4700, 4700-M
Cisco 25xx access servers	2509RJ, 2511RJ
Cisco AS5xxx access servers	AS5200, AS5300, AS5800
Cisco 7xxx	7000, 7010, 7204, 7206, 7505, 7506, 7507, 7513
Viper Switch	CPW16, ESP2015
Catalyst	1220, 1600, 1700, 1800, 1900, 1912, 2200, 2600, 2800, 2820, 2828, 2900, 2908XL, 2916M-XL, 2924XL, 2924CXL, 2926, 3000, 3001, 3011, 3011 router, 3100, 3200, 3500, 3600, 3900, 3920, 5000, 5002, 5500, 5505, 5509, 5CRSM, 8510
CiscoPro EtherSwitch	10/100, 1100, 1200, 1220,1220&L, 1400, 1402, 1408, 1420, 1422, 1428, 1442, 1448, 1601, Pro 16, 1900, 1900L, 2200
ATM switch	Light Stream 1010, 1015, 2020
Multiservice switch	BPX 8620, BPX 8650, IGX 8410, IGX 8420, IGX 8430, MGX 8220, IPX 8xxx
SwitchProbe	WS-PB7-4ETH-32, WS-PB7-8ETH-32, WS-PB7-12ETH-64, WS-PB6-1ETH-8, WS-PB6-1ETH-16, WS-PB6-2ETH-16, WS-PB6-1TR-8, WS-PB6-1TR-16, WS-PB6-2TR-16, WS-PB6-ETHTR-16, WS-PB6-1WANETH-8, WS-PB6-1WANETH-16, WS-PB6-1WANTR-8, WS-PB6-1WANTR-16, WS-PB7-2WANTR-32, WS-PB7-3WANTR-32, WS-PB7-4WANTR-32, WS-PB7-HSSIETH-32, WS-PB8-DFDDIETH-32, WS-PB8-ATM3ETH-32, WS-PB8-1FEHD-TX-32, WS-PB8-1FEFD-TX-32, WS-PB8-2FEHD-TX-32, WS-PB8-1FEHD-FX-32, WS-PB8-1FEFD-FX-32, WS-PB8-2FEHD-FX-32
Workgroup concentrator	1000, 1100, 1400
FastHub	300, 100+, 316T, 3116, 316C, 2116, 216T, 116T, 116C, 1116
MicroHub	1502, 1503, 1516
General SNMP devices	Most MIB II compliant

Table 10: Software Management Supported Devices

Product Family	Devices Supported
Cisco/CiscoPro 7xx	760 series, 770 series
Cisco/CiscoPro 10xx	1000, 1003, 1004, 1005
Cisco/CiscoPro 16xx1	1601, 1602, 1603, 1604
Cisco/CiscoPro 25xx2	2500, 2501, 2502, 2503, 2504, 2505, 2506, 2507, 2508, 2509, 2510, 2511, 2512, 2513, 2514, 2515, 1516, 2517, 2518, 2519, 2520, 2521, 2522, 2523, 2524, 2525, 2501CF, 2502CF, 2501LF, 2502LF
Cisco 26xx	2601, 2610, 2611
Cisco/CiscoPro 3xxx	3620, 36403
Cisco switching access concentrator	MC3810
Cisco/CiscoPro 4xxx	4000, 4000-M, 4500, 4500-M, 4700, 4700-M
Cisco 25xx access servers4	2509RJ, 2511RJ
Cisco AS5xxx access servers5	AS5200, AS5300, AS5800
Cisco 7xxx, 7500 RSP series routers6	7000, 7010, 7204, 7206, 7505, 7506, 7507, 7513, including CIPs
Catalyst7	29008, 2926, 5000, 5002, 5005, 5500, 5505, 5509, 8500, 8510, C5RSM, Catalyst 5000 modules supported: NMP, TR, FDDI, CDDI, ATM
ATM switch	LightStream 1010, 1015

1Dual Flash bank and single Flash bank. 2Dual Flash bank and single Flash bank. 3MICA modem upgrades supported. 4Dual Flash bank and single Flash bank supported. 5Dual Flash bank and single Flash bank on AS5200 supported; MICA modem upgrades on AS5200 and AS5300 supported; Microcom 56K firmware upgrade on AS5200 and AS5300 supported. 6Cisco 7000 series; 7200 series router upgrades supported; no slave RSP upgrade available; CIP card microcode upgrades supported on 7000 and 7500 series devices running Cisco IOS Version 11.1(1) or later. 7Supervisor I, II, III, ATM, FDDI, CDDI, and Token Ring switch modules on Catalyst 5000 and 5500 series devices. 8Catalyst 2900XL devices are not supported.

Using Essentials with Token Ring Switching Products

When using Essentials with Token Ring switching products, verify you have installed the firmware revisions as noted in Table 11.

Catalyst Software Versions Supported

Table 12 lists platform-specific software supported when using Essentials on Catalyst devices:

Cisco IOS Versions Supported

Support is provided for devices running Cisco IOS Versions 10.3 to 11.3 only. Unless your devices are running Cisco IOS Version 10.3 or later, not all MIB values may be supported. As a result, devices running versions of Cisco IOS earlier than 10.3 might not provide all device details in the inventory reports.

Essentials Release Notes and Caveats

This section contains the notes and general caveats that apply to Essentials on the Solaris 2.6 and 2.5.1 operating systems. It consists of the following sections:

• Server Caveats     22

• Browser Caveats     22

• Desktop Caveats     25

• Administrator Caveats     26

• Inventory Caveats     28

• Device Configuration Caveats     29

• cwconfig Command Caveats     31

• Import Caveats     32

• Software Management Caveats     33

• Syslog Analysis Caveats     39

• Case Management Caveats     41

• Device Navigator Caveats     42

Server Caveats

Using the Apache http server to support software not installed by Essentials is not supported.

Browser Caveats

If a graph looks awkward, or if text scrolls off a screen, reload or refresh the browser page. Usually, if you reload or refresh the page, the problem corrects itself.

Some e-mails sent to users contain URL links that wrap to more than one line. The workaround is to log in to Essentials, then use the Essentials tree control to perform the operation.

Printing Does Not Work Reliably

To print an exact copy of an Essentials screen, use the Print Screen or Capture Screen function on your machine.

Browser Accepts Only Certain Cookies

When using Netscape Navigator or Internet Explorer, you might encounter a situation in which Essentials returns you to the Login screen when you select an option. If this occurs, configure your browser to accept all cookies (Netscape: Edit > Preferences > Advanced > Accept all cookies; Internet Explorer: View > Internet Options > Advanced, select Cookies). [CSCdk17516]

The login dialog is not shown after you upgrade your version of Internet Explorer. The workaround is to flush your browser cache. [CSCdk18245]

The following administrator options have been found to sometimes cause the Internet Explorer browser to hang:

• Admin > Device Configuration > General Setup > Netsys Setup > Schedule

• Admin > Device Configuration > General Setup > Change Probe Setup >
  Config Retrieval Schedule

Installing the Internet Explorer 4.0 Service Pack 1 eases the problem, but the browser still might hang occasionally. [CSCdk32462]

When trying to print Device Configuration or Syslog (Java-based) reports from Internet Explorer running on Windows 95, you get a system error.

The workaround is to save the HTML version of the report to your local disk, then print the report from your local machine. [CSCdk26130]

Essentials depends on cookies to transmit permission-related information. If multiple copies of Internet Explorer are opened for use with Essentials on the same desktop by launching them from the Start > Programs > Internet Explorer interface or from an icon on the desktop, Internet Explorer generates incorrect authorization failures when you are correctly logged in.

The workaround is to start new browser windows using the New option from within the browser. [CSCdk33035]

Using Internet Explorer 4.x on a machine with an installation of Microsoft J++ might cause some Admin >Device Configuration tasks to fail with a NullPointerException or a InvalidClassException. Installation of Microsoft J++ installs different versions of the Java JDK 1.1 class files which are used by Internet Explorer. [CSCdk31703]

A server error message is displayed on the lower frame of the Exceptions Summary Report in Change Audit > Exceptions Summary, but only under the following conditions:

• When using the Netscape browser to view the reports

• When you select all days of the week to generate the Exceptions Summary Report

The workarounds include:

• Using Internet Explorer to view the Exceptions Summary Report

• Selecting an option other than all days of the week to generate the Exceptions Summary Report

If you are using Netscape and you select all days of the week to generate the report, after the server error message is displayed, you can resize the report window or the lower frame of the report. This removes the error message and display the report successfully. [CSCdk44743]

Netscape 4.0x does not display the correct month and day for GMT time zones containing offset minutes [CSCdk34547]

Netscape does not always display the date in the correct time zone or with the correct date on the Collect Server Info and Self Test pages.

The workaround is to use Microsoft Internet Explorer 4.01. [CSCdk44551]

The Navigator 4.05 right mouse button pop-up menu offers the Open Frame in New Window option. If you select this option while in Essentials, the right frame of the Essentials desktop appears, but the navigation tree does not. To avoid this, complete all tasks in Essentials windows. [CSCdj50947]

On Solaris, HP-UX, and AIX, Navigator 4.05 does not dynamically update the Reachability Dashboard (Tasks > Availability > Reachability Dashboard) when devices change state. To update the information in the Reachability Dashboard, click the Navigator Reload button. [CSCdj55007]

If you access the Glossary (Help > Glossary) with Navigator 4.05, clicking the Back button in the help window might take you to the help contents page instead of the beginning of the glossary section. To return to the Glossary, click Glossary. [CSCdj57449]

Desktop Caveats

JavaScript Error When Clicking Back from CCO Web Site

When using the online help file Help > Contents > CCO and Device Management > Case Management > Cisco Web Site link, if you select the Back button, an error message appears. [CSCdk27845]

You can ignore this message, because the device selector works normally. [CSCdk07201]

Administrator Caveats

Install.cshrc File Contains Extra Character

The file /opt/CscOpx/etc/install.cshrc contains an extra "\" in the line

if ($\?MANPATH) then. 
 

The workaround is to remove the extra "\" from this line, and the script works as designed for CSH users. [CSCdk52695]

When the database is down, if you click Admin > Inventory > Schedule Collection, a blank page is displayed. [CSCdj60419]

# /etc/init.d/dmgtd start
 

Click Admin > Troubleshooting > Collect Server Info link to collect server information, then call your technical support representative. [CSCdk37124]

If the Event Channel Admin screen hangs or reports the system is down, verify the EDS process is running using the Process Status screen (Admin > System Admin > Process Status). If running, check the daemons log (/var/adm/CSCOpx/log/daemons.log) for process failures or errors in EDS, SyslogAnalyzer, or ChangeAudit. EDS and the dependent processes might need to be restarted if failures are found. [CSCdk09614]

Some proxy or firewall products require users to be authenticated before accepting or forwarding connections. The Essentials proxy function does not provide authentication information to these proxy servers and requires per-user authentication information itself. [CSCdk05720]

[CSCdk12362]

When you add or import a device or change device information, avoid using angle brackets (< or >) in the User or Serial Number fields. When some browsers encounter these characters, they might interpret the information incorrectly. [CSCdj24567]

Inventory Caveats

Export to File Can Overwrite Existing System Files

When you select Admin > Inventory > Export to File and specify the filename to which the device information is to be exported, if the filename already exists, the system will overwrite the existing file and no warning or reconfirmation message appears. Caution should be used when specifying a filename, as it could potentially overwrite important files. [CSCdk48937]

In the Chassis Slot Details reports for Access devices (AS5200s and AS5300s) and RSMs, the number of available slots displays a negative number; however, the same information is displayed correctly in the Detailed Device Report. [CSCdk52231]

For Year 2000 compliance and Software Version Reports generated by Resource Manager 1.1, the EPROM revision is blank for software version 5.3(5) or greater; however, versions less than 5.3(5) are in the report. [CSCdj91789]

The workaround is to go to the device and configure the modem for use, then reacquire the inventory data for the device. [CSCdk35153]

The workaround is to run the Detailed Device Report, which shows details about each Flash partition that was discovered when the router was added to inventory. [CSCdk10221]

The workaround is to remove any unwanted commas that might cause data to be placed in separate fields when they should be placed in a single field. [CSCdk25851]

Device Configuration Caveats

In order for the configuration archive to successfully gather the ATM and RSM module configurations, these modules must have the same Telnet passwords as that of the supervisors for the Catalyst 5000 family of devices.

JRunProxyServer Leaks File Handles Due to Configuration Archive CORBA

If Tasks > Device Configuration > Update Archive is used frequently, or if running or startup configuration files are retrieved frequently from the configuration reports that provide access to these configuration files, after weeks or months of use, the Essentials product stops working correctly because it has run out of file descriptors.

The workaround is to perform the following steps:

On UNIX---Enter kill -HUP WebServer pid. The pid on the WebServer can be determined by running the command /opt/CSCOpx/bin/pdshow WebServer. [CSCdk54194]

If the log files created by Netsys under $ECSP_DATA/tmp/ do not have write permission to "All," other users cannot create the baseline. The log file permissions depend on the umask of the user. If the permissions are not set correctly, users will receive the error message, "Unable to create baseline." To workaround this problem, change the permission of the log files. [CSCdk52137]

If you delete a device from the Essentials inventory, the corresponding Netsys report for that device is not removed. The old report remains, but is not updated. [CSCdk51481]

http://<RME_server_hostname>/CSCOnm/servlet/JSServlet

Click the Unload All Clients option. The page will be refreshed after the clients are unloaded. Then click the Load All Clients option. [CSCdk52938]

The error message "Connection with remote device lost. Try again." appears in the Partially Failed Running Configuration Device Summary for the Catalyst 5000 family of devices. This failure reason is shown even when Configuration Archive is successful in receiving the device configuration. The workaround is to check the archived configuration file. [CSCdk50736]

Partial failure for getting module configurations for Catalyst devices results in error strings being shown as part of the raw configuration, as well as raw diff. [CSCdk49749]

cwconfig Command Caveats

Access Restrictions and File Permissions

On UNIX, cwconfig is a set-userid program owned by root and belongs in the bin group. However, as soon as the program is launched, (internally) cwconfig sets userid to bin. The groupid of the process remains the same as the invoking user's groupid. Consequently, all files created by cwconfig - exported configurations and log files - are owned by bin and belong in the same group as the invoking user. The files have Read-Write permissions for both owner and group. [CSCdk44589]

When a cwconfig session has multiple syntax errors, only the first error detected by the tool is reported; the others remain unlisted. Currently, there is no workaround. [CSCdk12667]

Currently, cwconfig cannot validate the syntax of configuration files uploaded to the device via the import command. Consequently, the cwconfig import process reports success even if a configuration file with invalid contents is attempted to be written to the device. The configuration update does not succeed on the device, but cwconfig cannot detect this failure. [CSCdk18495]

If the cwconfig commands get, start2run, or import are performed on too many devices in a single command, you might get an exception "java.lang.NoClassDefFoundError: org/omg/CORBA/INITIALIZE". As a workaround, change the operating system's configuration to increase the number of open file descriptors allowed per process. [CSCdk53421]

Import Caveats

Need a Way to Shut Off DNS Resolution

Essentials import of IP addresses will sometimes hang if DNS resolution of the IP address does not work.

The workaround is:

1. Add IP addresses in the local hosts file.

2. Fix the DNS so that reverse name lookups work.

[CSCdk01464]

The workaround is to upgrade Cisco IOS to 11.2(14)P or higher. Cisco IOS versions 11.3(2) and 11.2(9) also exhibit bug symptoms; Cisco IOS versions 11.3(3) and 11.2(13) contain fixes. [CSCdj60284]

The workaround is to verify that TACACS information is properly configured, or delete TACACS information completely for such devices. [CSCdk31318]

Software Management Caveats

Supervisor III History Is Not Showing Correct Data Under Image Entity

In the Browse History Report page for Catalyst devices, the Image Entity column displays extra text after the image name as in Supervisor.1/system SW. This extra text after the "/" character is incorrect and should be ignored. [CSCdk50175]

If you are not upgrading the Supervisor module in a Catalyst distribution job, but upgrading some other modules, do not select the "Backup current running image" job option. Selecting this option, which upgrades Catalyst modules other than Supervisor, can cause the Software Management application to incorrectly import the current running Supervisor image as the module (ATM, FDDI, CDDI, Token Ring) image in the software library. [CSCdk51236]

Ignore this message. [CSCdk52400]

The Work Order Report displayed during the Distribute Images job creation process for Catalyst switches incorrectly displays that the image will be copied to the software library at the time of distribution for ATM, FDDI, and Token Ring modules. Ignore this message because it does not affect the software distribution on these modules. [CSCdk51176]

Before proceeding with module software upgrades, manually verify that the Catalyst switch is running a compatible Supervisor software version. [CSCdk50317]

In the Recommend Image Upgrade screen, verify from the software version numbers whether the new target image supports all the features you wish to deploy. Software Management does not check if all current configured features in the ATM module are present in the new image. [CSCdk40327]

If the 4.2(x) image is selected as the target image during Image Distribution from CCO, then you should also use the Browse Library > Edit Image Attributes screen to edit the version number. [CSCdk50101]

Software Management supports only the combined format files (for example, mcom-modem-code-xx.bin) but it does not support the separate firmware and dsp code files. These files cannot be imported to the software library. [CSCdk27380]

Rename the image file to cat5000-sup8m.<ver-no> (for example, cat5000-sup8m.3-2-1b.bin for Supervisor 8MB 3.2(1b) image), then add the image to the library using the "Add Image to Library" option. [CSCdk22546]

As a workaround, you should select less than 50 devices if they have a slower link to the Internet. [CSCdk32490]

If you import images that require more than 20 minutes to complete, the browser might time out and display a message that says, "Document contains no data." Decrease the number of images you import at one time to ensure the import process requires less than 20 minutes. [CSCdj25733]

If you import an image from CCO when the temporary directory's file system is full, you might receive server errors when running other Essentials functions. To avoid these errors, keep the temporary directory clear of unneeded files. [CSCdj44161]

For Supervisor III modules on Catalyst 5000 and 2900 devices, the baseline and synchronization options are supported only when the modules are running software version 4.1 or later. [CSCdk06556]

Syslog Analysis Caveats

NullPointerException Error

For all Netscape browsers, the "All Syslog Messages" report from Device Center does not work. You will get a null pointer exception message. The internal cause of this is due to the "title" not being set for this report. There is no workaround at this time. [CSCdk52585]

[CSCdk49695]

..%CIP4-6-MSG: %MSG802-6-LLC.START: Starting LLC-2...
 

%MSG802 6 LLC_START Starting LLC-2...
 

where MSG802 is the facility, 6 is the severity, LLC_START is the mnemonic, and the remaining text is the description. The first part (CIP4-6-MSG) is not used. Only the second part of the CIP message is stored. [CSCdj16580]

Syslog reports do not have Cisco IOS explanations for some messages. Refer to the latest Cisco IOS reference manual for additional information on reported messages. [CSCdj61218]

For Windows 95 and Internet Explorer users who access the Resource Manager server over ISDN, the Syslog Analyzer reports might be blank the first time the reports are generated. To workaround this problem, retry the task to generate the syslog report. [CSCdk33214]

Case Management Caveats

The following subsections describe issues with Case Management (Tools > Case Management).

Case Management Query Does Not Show All Open Cases

Case Management Query (Tools > Case Management > Case Query/Update) might not show all open cases. This occurs when there is more than one contract associated with your CCO User ID because CCO uses the contract number as the validation key for the Case Query operation.

To work around this situation, request via e-mail to cco-team@cisco.com that all your contracts be added to the Additional Contracts field in your CCO user profile. [CSCdj50287]

If you open a case with CCO via e-mail after unsuccessfully trying to open a case using Essentials (Tools > Case Management > Case Open), processing of the e-mail might take a while. The Technical Assistance Center (TAC) is usually able to process these requests within an hour, but it could take longer. Until the case is processed, the case is not available via Case Query/Update (Tools > Case Management > Case Query/Update). [CSCdj50294]

Case Management cannot gather configuration information from a router running TACACS when the router is configured for TACACS login but is not configured for the enable secret password. To correct this situation, enter the enable password in the Enable Secret Password field for the device (Admin > Inventory > Change Device Attributes). [CSCdj82514]

Internet Explorer does not open a second window with collection details when you click on the Pass or Fail link in the "Inventory and Telnet Collection Status" window. [CSCdk32038]

$IosTelnet::Timeout = 30;

$IosTelnet::Timeout = 90;
 

Keep incrementing this value until the process completes successfully. [CSCdk50702]

Device Navigator Caveats

Catalyst 1924EN Software Version 8.0.4 Supports Web Browsing

Catalyst 1900 devices are not supported by Device Navigator in this release. [CSCdk43726]

The Device Navigator help currently includes a help window that displays multiple button panels only. The workaround is to close the help window and view that help topic manually through the Help Contents window. [CSCdk11625]

CWSI Campus

The CWSI Campus components are as follows:

• CWSI Campus Network Map

• VlanDirector

• UserTracking

• TrafficDirector

• AtmDirector

• CiscoView

This section contains information that applies to all of these components. Notes and caveats for the individual components are described in these release notes in the sections about the specific component.

CWSI Campus Application Compatibility

Table 14 shows the Cisco devices that CWSI Campus applications support and the minimum software version required on the device.

Startup Information

You can select and start up both CiscoView and TrafficDirector applications from HP OpenView (HP-OV) manager or SunNet Manager (SNM). The additional CWSI Campus functions, including the CWSI Campus topology mapping services, VlanDirector, AtmDirector, and UserTracking applications, must be started from the main CWSI Campus interface, which is started from Solaris as part of the normal start-up procedures for CWSI Campus.

TrafficDirector and CiscoView are device-focused applications and are easily started from HP-OV and SNM based upon the device discovery process within HP-OV and SNM. The additional CWSI Campus functions require more detailed network-wide topology data than HP-OV and SNM can provide. The CWSI Campus discovery and database services must be running for these additional applications to function, which means you need to start these services from the CWSI Campus Network Map window.

X Terminal Access Not Officially Supported

Using an X terminal to access and control CWSI Campus 2.2 applications is not officially supported.

Many X terminal systems might appear to run some of the CWSI Campus functions satisfactorily. However, there is a known problem when running a CWSI Campus client to an X display on a non-Solaris workstation. JavaSoft's Java Runtime Engine (JRE) does not function properly because fonts are specified that are not available on many X11 servers. The result is that the X server on the remote system refuses to establish the session and exits.

A possible workaround is to delete (or rename) the /opt/CSCOcwsi/lib/font.properties file on the CWSI Campus client machine (that is, the Solaris machine where AniServer is running). The X terminal will revert to its default fonts and an X session can be established. The workaround is known to work with one exception when displaying on the following platforms:

• SunOS

• NCD X terminal

• Reflection X on Windows

• Exceed on Windows

The exception to the workaround is that some TrafficDirector screens are truncated, resulting in some fields and buttons not being displayed or accessible.

The above procedure is a workaround and is not supported by Cisco.

Browser Support for CWSI Campus Online Help

If you decide to use Netscape as your browser, and it has not already been installed, you can install it at any time. Starting CWSI Campus Help does not provide the interaction for you to view and accept the Netscape licensing information. You must start Netscape at least once before starting CWSI Campus help so that you can accept the Netscape licensing information. If you do not start Netscape before starting CWSI Campus help, CWSI Campus help will not start.

Year 2000 Compliance

All CWSI Campus 2.2 components are Year 2000 compliant.

Online Help

To run CWSI Campus redirected to another system (setting $DISPLAY to redirect the output to a different system) and have online help available, you must install the help files on each system where CWSI Campus will be used. [CSCdk49311]

CWSI Campus Error Messages

Some of the error messages do not have online help. The Help button on the error message window is unavailable (grayed-out).

CWSI Campus Network Map

This section describes new features and provides important notes and caveats for the CWSI Campus network map.

New Features for CWSI Campus Network Map

CWSI Campus Network Map provides the following new features:

• Support for the Netflow Feature Card (NFFC) on Catalyst 5000 switches. The CWSI Campus Network map shows the NFFC on Catalyst 5000 switches. The attributes report also has new fields that describe this card.

• Display of Multi-Layer Switches (MLS) and components (Switch Engines and Route Processors) with the ability to highlight logical relationships between devices such as flow masks and shortcuts.

• Topology discovery and display for Catalyst 8510 switches.

Important Notes and Caveats for CWSI Campus Network Map

This section provides important notes and caveats about the CWSI Campus Network Map.

Catalyst 3000

Moving ports between virtual local area networks (VLANs) will fail on Catalyst 3000 switches running software versions prior to Release 2.2(2).

Routers

Not all modules are shown in the Node Attributes window. You can access the Node Attributes window by selecting the device and clicking the right mouse button. [CSCdj40028, CSCdj40030]

LAN Emulation

The following are LAN Emulation (LANE) issues:

• On Catalyst 3000 switches, LANE client (LEC) and LANE server/Broadcast and Unknown server (LES/BUS) components that do not bind with VLANs will not be discovered by CWSI Campus. As a result, ATM VLANs consisting of these LANE components will not be discovered. [CSCdj28689, CSCdj06709]

• Because of the agent inconsistency (lecsLesConfigTable MIB walk skips LES instances) that exists in Cisco IOS Release 11.1(X) and Catalyst 5000 ATM image 3.2(4) (and earlier), CWSI Campus is not able to discover some emulated LANs (ELANs). This inconsistency has been resolved in Cisco IOS Release 11.2 and Catalyst 5000 ATM image 3.2(5). [CSCdj24857]

• If a Catalyst 5000 switch appears as an ATM cloud on the CWSI Campus map, make sure that the switch has sufficient memory. The Catalyst 5000 switch comes with 16 MB of memory, however this might be insufficient depending on the number of protocols the switch is running. Insufficient memory might prevent the supervisor agent and the LANE card from being connected. Without the connection, the ifEntries related to the LANE card will be missing from the ifTable and the device will show up as an ATM cloud on the topology.

Starting Applications

The following are issues related to starting CWSI Campus applications:

• Starting multiple instances of CWSI Campus applications terminates the currently launched instance of the application or produces a memory error. If you do start multiple instances of a CWSI Campus application, terminate all instances and then start only one instance. [CSCdk31567]

• When you attempt to start the TrafficDirector application either from the CWSI Campus topology or from CiscoView, you may get the following error message:

"Error accessing agent domain rmon while retrieving ETSTATS error: entry or group not present in agent"
 

This situation might be caused by one of the following conditions:

• RMON is not enabled on the device.

• The incorrect community string has been specified in Config Manager.

• If you start CiscoView from CWSI topology by double clicking a device and then change the device to another one within CiscoView, starting VlanDirector and trying to highlight VLAN ports in CiscoView might result in the following error messages:

"invalid command name "Sess0"
"bad window path name ".en"
 

The workaround is to acknowledge these error messages by clicking the OK button. No functionality is affected by these error messages. [CSCdk29907]

Discovery

The discovery process is unable to discover Catalyst 5505 switches with OC-12 dual port modules running release 4.12. This problem also occurs with the release that supports MPOA. [CSCdk23407]

VlanDirector

This section describes new features and provides notes and caveats for the VlanDirector application.

New Features for VlanDirector

The VlanDirector application provides the following new features:

Important Notes and Caveats for VlanDirector

This section provides important notes and caveats about the VlanDirector application:

• When an ATM-VLAN is deleted and recreated, the next discovery cycle will not associate the newly created ATM-VLAN to the appropriate Ethernet VLAN.

The workaround is to stop the server (stopcwsiserver) and then start it again (startcwsiserver). [CSCdj59620]

• Creating more than one configuration server at a time does not work properly. The workaround is to create only one configuration server at a time. [CSCdj63616]

• Configuring a configuration server or configuring the default ATM-VLAN might cause the following message to be displayed:

Failed to assign auto ATM address of LE config server on port <port name> of device <ip Address>. <snmp error message: COM.cisco.nm.mojo.comm.snmp.SnmpValueException: SnmpResponseBadValue
on <ipAddress> > 
 

The following are possible causes:

• Wrong community strings

• Wrong device image

• Command already exists in the running configuration file of the LANE module (lane config auto-config-atm-address or lane config config-atm-address)

The workaround is to remove the line from the configuration file and remove the database association from the particular interface (remove the line that says lane config database xxx) and try again. [CSCdk31419]

• VLAN configuration sometimes fails on Catalyst 5000 switches (with SMP Release 3.1.1, 3.2.1, 3.2.2, and 4.1). The workaround is to enter the clear config all command on the device to return the device to its working state. [CSCdk27572]

• Deleting a backup LES deletes ATM-VLAN. The workaround is to rediscover the network after deleting the LE server. This should discover the ELAN again (provided the master LES is operational). [CSCdk32280]

• Deleting the master LECS results in deleting all ATM-VLANs from CWSI Campus. The workaround is to make sure there is a backup LECS before deleting the master LECS. The backup LECS will become the master. After rediscovery, all ATM-VLANs should be found and displayed. [CSCdk32372]

• Selecting Map Highlighting>VTP Trunks from the CWSI Campus Network Map might not reflect the actual trunking links. To see the actual trunking links you need to select View>Refresh Map and then click on the VTP Trunks. [CSCdk31351]

UserTracking

This section describes new features and provides note and caveats about the UserTracking application.

New Features in UserTracking

The UserTracking application provides the following new features:

• Discovery and display of Token Ring NIC addresses in the table.

• Replication of cells. You can replicate a single cell in a single column into one or more contiguous cells adjoining the cell being replicated. You might use this feature to replicate the VTP Domain name or VLAN name into one or more cells.

You can replicate cells only in columns whose cells can be edited. To select the cells to replicate, move the cursor over the cell you want to replicate and while pressing the left mouse button, drag the cursor up or down in the column until you have highlighted all of the cells into which you want to replicate. You can also make an initial selection of the cell you want to replicate and then while holding down the Shift key, single click the furthest cell into which you want to replicate. To replicate the cell, select Edit> Replicate.

You can replicate cells only in one column at a time. The UserTracking application reports an error if you have cells in more than one column selected when you select Replicate.

You can replicate cells only in columns that can be edited, such as Mac Address, VLAN, VTP Domain, User Name, Notes, and Port State. The source value is written only into cells in rows whose VLAN type is Ethernet. If you replicate cells in the VTP Domain column, the UserTracking application sets the cells in the corresponding VLAN column to blanks. When the UserTracking application completes the replication, you must set the VLAN names for those cells. You can set the names by doing another replication. When you replicate in the VLAN column, UserTracking does not ensure that the VLAN being stored is a VLAN in the VTP domain for that row.

• Support for Token-Ring networks. The UserTracking application provides the capability to locate end-users on Token-Ring networks.

• Three new columns (VLAN Type, Ring, and trBRF VLAN) have been added to the UserTracking screen display.

Important Notes and Caveats for UserTracking

This section provides important notes and caveats about the UserTracking application.

UserTracking Table

• Sometimes, when you delete rows in the UserTracking application, the application terminates with a thread dump. Currently there is no workaround. You must restart the UserTracking application. (When this occurs, the CWSI client is not affected, even if you started the UserTracking client from CWSI.) [CSCdk41893]

• Sometimes, when you click on a cell in the VLAN, VTP Domain, or Port State columns in UserTracking, the UserTracking client might become inaccessible. You must terminate the UserTracking client and restart it. [CSCdk42144]

TFTP Server and UserTracking

• If you change the IP address of a TFTP server in a VMPS server's environment (through CiscoView or through the CLI), UserTracking discovers the new IP address of the TFTP server (as part of the next ANI discovery), but UserTracking does not delete the old entry. Subsequent downloads of the TFTP file for that VTP domain from UserTracking will download to the old TFTP server as well as to the new one. [CSCdk35147]

• If you change the IP address of a TFTP server in a VMPS server's environment (through CiscoView or through the CLI) to an unreachable destination might cause the UserTracking client to hang for an extended period of time. [CSCdk30396]

• In the TFTP Configuration window, do not modify the entry that specifies the VTP domain serviced by this VMPS server (vmps domain <DomainName>). If you change this line, the VMPS server might no longer be recognized by UserTracking.

UserTracking Discovery

• When subnet discovery of user nodes is initiated, the devices in that subnet are marked for discovery. Because switches support multiple VLANs, the discovery could span more than the desired subnet. Therefore, UserTracking could discover additional end user nodes that are not in the selected subnet.

• The UserTracking discovery process takes information from the router and switch CAM tables and displays the results as the state of the end user nodes on the network or subnet in the Last Seen field. Because these devices work in various VLANs and subnets and collect their information at different times, the information they have may not always be the most current. Therefore, the information displayed in the Last Seen field does not always reflect the most current state of the network or subnet.

• Occasionally, the UserTracking table might include rows that do not correspond to end-user nodes in your network.

This situation occurs intermittently. It is most likely to occur if a UserTracking discovery begins before ANI completes its first discovery after you have installed CWSI or restored the CWSI database to its initial state.

To avoid this situation, before manually invoking a UserTracking discovery, look at the CWSI Campus Network map to verify whether the first ANI discovery has been completed.

If this situation arises, you can delete the undesired rows in UserTracking by selecting Action>Delete Rows.

TrafficDirector

This section describes new features and provides notes and caveats for the TrafficDirector application.

New Features for TrafficDirector

The TrafficDirector application includes the following new major features and enhancements:

• Support for ATM monitoring. The TrafficDirector software supports the ATM SwitchProbe device, where ATM counters are mapped to Etherstats group counters to generate ATM-specific, real-time data. The ATM SwitchProbe device allows standard TrafficDirector applications, including Segment Details, Segment Zoom, Traffic Monitor, and Trend Reporter, to display ATM statistics.

• Support for learning and roving VLANs on Catalyst 5000 switches. You can switch the display listing between ports and VLANs within Configuration Manager to track the status of a particular Catalyst-based VLAN. To support the roving capability between VLANs and capture up-to-date statistics from a selected entity, you can also reinitialize the counters on demand.

• Transmission Control Protocol (TCP) and User Datagram Protocol (UDP) domain creation. The Domain Editor has been modified to simplify the creation of domains based on TCP and UDP port numbers. Two new domain types (TCPAPP and UDPAPP) are provided as dialog box options to speed the configuration process for the most commonly created protocol domains.

• Generic domain port mode support. Generic domains can be analyzed on a per-port basis to capture either TCP or UDP traffic, or both types of traffic. A Port option has been added to the Host Address Mode panel in the New Generic Domain dialog box, enabling traffic to be displayed for each port address in a generic domain.

• Enhanced display for ASCII conversation history and summary reports. Conversations between hosts (in both directions) can now be displayed on a single line. This feature is turned off by default. To activate this feature, change the value to 0 in following line in the default.dvp file:

map-conversations:1 
 

• Protocol decode improvements. The Protocol Decode application can now display both source and destination port numbers for TCPs and UDPs in the summary screen.

• New syntax for automatically generating reports. The Auto Report scheduler for the Trend Reporter application has been modified to reflect a more intuitive file-naming syntax so that report information is grouped and stored logically by agent information, report type, and creation date. To use this feature, set the output file or Append File name to the keyword AUTO.

• Enhanced Media Access Control (MAC) address support. Up to 4096 MAC address entries are now supported with the Protocol Decode application. You can configure this number by modifying the $NSHOME/usr/nsconfig.cfg file.

• Larger number of default domains. To ease the configuration process, more than 60 default domains are now shipped with the product. Default domain information is included to support the improved TCP and UDP port-to-name mapping.

• Default properties file enhancements. The TrafficDirector application now supports a new default properties file-naming convention. The default properties file is called fwxxprop where xx represents the release level of the firmware.

The new property file is shipped with logging enabled on 10 standard domains: RMON, ATALK, DECNET, IP, IPX, NETB, NFS, SNA, VINES, and XNS. This feature allows you to take advantage of standard reporting features within the TrafficDirector application without first learning all the details of the TrafficDirector Configuration Manager utility.

• New logging defaults. The new standard logging feature described in the previous paragraph (logging for 10 standard domains) is configured with standard logging intervals for the following reports:

  • Segment History

  • Segment Summary

  • Multi Segment History Mix

  • Protocol Usage History

  • Protocol Distribution Summary

  • Host Summary

  • DLCI Usage Summary

  • WAN Usage History

Domain statistics are logged every 15 minutes, and the IP domain logs the top 50 hosts every hour. For Frame Relay agents, the IP domain logs the top 50 hosts every hour to support the data-link connection identifier (DLCI) usage report.

• Support for the Network Analysis Module, including automated discovery of the module as a roving agent, and port and VLAN roving to the module.

• Support for the Catalyst 2908, Catalyst 2916, and Catalyst 2924 devices (each supporting mini-RMON and roving RMON).

• Support for the Multiport T1/E1 WAN SwitchProbe device.

Important Notes and Caveats for TrafficDirector

This section provides note and caveats about the TrafficDirector application.

IOS Support

The TrafficDirector 5.3 application does not support the creation of Alarms and Events for any device running IOS 11.1 or greater. The TrafficDirector application assumes that the RMON statistics group is always supported, which is not the case for IOS.

Configuration Manager

In Configuration Manager, when specifying the analyzer port number for a roving agent, use the exact port number (port name or module/port number including leading zeros) learned by the TrafficDirector application and displayed in the ports window or the switch .swp file.

Ping

The TrafficDirector application ships with the default pingoff file. This file is required for successful pings on selected agents if you are running either the Solaris or TCP/Pro TCP/IP stacks. For pings to be performed successfully when you are running any other TCP/IP stack, delete the $NSHOME/usr/pingoff file.

Integration Issues

To integrate the TrafficDirector application with other network management system (NMS) platforms, see "Integrating Traffic Director with Other Managers" in Appendix C of the Using the Campus TrafficDirector Application publication.

Specifying Property File Types

Table 15 describes when a shared property file or a custom property file is used when you configure a specific property for agent or switch type.

Table 16 lists the devices supported by the TrafficDirector application.

AtmDirector

This section describes new features and provides notes and caveats for the AtmDirector application.

New Features for AtmDirector

The AtmDirector application provides the following new features:

• ATM-RMON feature in fabric and ATM-VLAN maps is now available.

• Discovery and display of unknown UNI devices.

• Enhancement to SPVC-provisioning capability.

• Tooltip support in AtmDirector maps.

Important Notes and Caveats for AtmDirector

This section provides notes and caveats about the AtmDirector application.

Main Window

While editing the fabric name on the tree structure in the main window, the old name is not completely cleared from the display when the new name is being entered. The new name is displayed clearly after you press Return.

Online Help

If you launch and close the Netscape browser many times, sometimes AtmDirector help cannot be launched. If this happens, close Netscape (and AtmDirector if necessary) and wait for few seconds. Then try again.

ATM Fabric Map

The following caveats apply to the ATM fabric map:

• During SPVP/SPVC setup using Advanced Parameters, selecting an incorrectly configured ABR table displays the following message

Traffic Type not understood 
 

To resolve this, add a new row for the ABR traffic with the appropriate traffic parameters and apply it towards the SPVP/SPVC setup.

• If AtmDirector displays unknown devices that are no longer present in the network, follow these steps to remove them from the map.

  (a) Reset the interface on the LS1010 switch to which the unknown device is connected. This will clear the unknown device entry in CISCO-ATM-ADDR-REG table.

  (b) Delete the link between the LS1010 switch and the unknown device, after it is appears as broken line on the ATM fabric map.

  The unknown device is deleted from the map after the link is deleted.

• AtmDirector might display more than one fabric (for one single physical ATM fabric) in cases where 1483 encapsulation is being used. [CSCdj67021]

ATM-VLAN Map

• In some cases, while displaying the Control Connection VCs, the Destination Host name field is blank. This situation is caused by the host name not being correctly resolved from the ATM Address.

• TopN and Call failure features on the ATM-VLAN maps might not display accurate data for LANE clients on LS-1010 switches.

PNNI

The following caveats apply to the PNNI function in the AtmDirector application:

• The addition of a new reachable address from AtmDirector will not be immediately reflected in the dialog box when reinvoked. After the next discovery cycle, the new address in Reachable Address dialog box is displayed.

• In the PNNI topology view, configuring new PNNI routes on PNNI nodes will result in the following error message:

ORB DB Error. 
 

[CSCdk28870]

• The Modify button in the Reachable Addresses dialog is currently disabled for this release. You can modify the existing reachable address by deleting the existing one using the Delete button and adding the desired one using the Add button.

After deleting and adding the PNNI reachable address, you need to exit from the AtmDirector application for those addresses to be updated on the database on the client.

• After deleting and adding the PNNI summary address, you need to exit from the AtmDirector application for those addresses to be updated on the database on the client.

• On the PNNI topology map, sometimes there are no links displayed between the PNNI nodes. This situation was introduced in the LS1010 release 11.2(8)WA03(03). The fix will be in next LS1010 maintenance release. [CSCdk47194]

Community String

You can change the community string for a device using CWSI Campus. However, if you want to change the community string for a device on which you have already performed an SNMP operation using AtmDirector, you must change the community string, exit AtmDirector and then restart AtmDirector.

LANE Client Support

AtmDirector does not support multiple LANE clients for the same ELAN on the same device.

TopN/Traffic Between/Call Failure Graphs

• Clicking Any Interval on the trend graph displays the values for that interval (until the mouse is released).

• Graphs do not show the sample interval on the graph.

• Printing a graph with a scroll bar prints data beyond axis scale.

CiscoView

This section describes new features and provides notes and caveats for the CiscoView application.

New Features in CiscoView

The CiscoView application provides the following new features:

• Expanded community string management and functionality.

  • You can more conveniently manage all your devices' community strings: You can enter, modify, or delete community strings for all your devices before you manage any of the devices.

  • You can optionally save defined community strings for future CiscoView sessions.

  • You can specify community strings for submodule hosts (for example, for a board within a router).

  • If you attempt to access a submodule device when its community string is not defined, CiscoView uses the parent device's community string instead (if known). If the parent's community string is not known or does not work, CiscoView uses the default community strings, "public" and "private." If these strings fail, you are prompted to enter the correct strings.

  • If you attempt to access any device when its community string is not defined, CiscoView uses the default community strings "public" and "private" instead. If the default strings fail, you are prompted to enter the correct strings.

• Full support for 64-bit counters. If you are running CiscoView over an NMS, contact your NMS vendor to determine if your NMS also supports 64-bit counters.

• User preferences (as defined in the Options>Properties dialog) saved across CiscoView sessions.

• The CVSecurity patch (previously released as a PSMU for CiscoView 4.0) fully integrated into CiscoView. Now you can easily install CVSecurity as part of the CiscoView installation.

CVSecurity takes effect only when CiscoView and CiscoWorks are installed on the same UNIX machine. (CVSecurity is not available for PC platforms.) When installing CiscoView on a UNIX machine, if CiscoWorks is already present you are prompted to specify whether or not to install CVSecurity.

CVSecurity allows you to restrict CiscoView functionality for specified groups of users. When you attempt to launch CiscoView from CiscoWorks, you must enter a username/password which determines your level of CiscoView access. There are three levels of access:

• You cannot launch CiscoView.

• You can launch CiscoView and use it to view device configuration and to monitor devices, but cannot use CiscoView to configure any device.

• You have full CiscoView privileges---you can launch CiscoView and use it to both monitor and configure devices.

• Support of the following:

  • HP OpenView 4.11, 5.0, and 5.01 (on Solaris 2.5.1 and 2.6 only the CiscoView engine is supported)

  • Solaris Site Manager 2.3/Domain Manager 2.3/Enterprise Manager 2.0 (Solaris 2.5.1, and 2.6)

• Support for the following upgrade paths:

  • Upgrade from CiscoView 3.2, 4.0, and 4.1

  • Coexistence with CiscoWorks 3.2 and 4.0.

  • Upgrade CiscoView within CiscoWorks for Switched Internetworks 1.3 (CWSI 1.3)

• Availability of CiscoView as part of the WAN Manager 9.1 (formerly StrataView+) bill of materials. WAN Manager 9.1 launches CiscoView as a device management application for the BPX/IGX/MGX devices.

Because WAN Manager currently runs with HP OpenView on the Sun/Solaris, the BPX, IGX, and MGX (formerly AXIS) package files have been tested only on these platforms. Please refer to the BPX, IGX, or MGX device package release notes for the most up-to-date information on the operating system versions supported as the versions will vary from release to release.

For additional information about WAN Manager platform availability and support, see the CiscoView Upgrade Planner page on CCO at http://www.cisco.com/kobayashi/library/netmanage/cview/ and click the "What's Hot for CiscoView and CiscoWorks Windows" link.

• Support for the devices listed in Table 17.

• Support for other applications listed in Table 18

• The CiscoView devices packages included in this release are shown in Table 19 (following).

Note that there are additional device packages not included on the CiscoView CD-ROM, but which are available for download from CCO at http://www.cisco.com/kobayashi/library/netmanage/cview/.

In particular, device packages for the multi-service switching devices BPX 8600, IGX 8400, and MGX 8220 (formerly AXIS) are available only from CCO.

Refer to the package readme files for details on the supported versions. Readme files are available at the same location on CCO as the device packages. For more information about selecting and downloading device packages, see the section "Incrementally Installing Device Packages."

Cisco IOS Information

This section contains the latest Cisco IOS (Internetwork Operating System) software version information at the time of printing.

CiscoView supports Cisco IOS software Releases 10.0 through 11.3. Note the following restrictions:

• Access servers require a minimum of Cisco IOS software Release 10.2.

• Cisco 3600 devices require Cisco IOS software Release 11.1 or later.

• Cisco 4000 series devices require Cisco IOS software Release 10.3 or later.

• Cisco AS5800 devices require Cisco IOS software Release 11.3(3)AA.

• Cisco uBR7246 devices require Cisco IOS software Release 11.3(2)XA.

• Not all device packages support all Cisco IOS versions. If you are uncertain which Cisco IOS version is supported, you can check your device package readme file.

New devices and further specifics on Cisco IOS support will be updated as devices become supported. For the online release notes, refer to one of the following:

• Cisco Connection Online (CCO) in the Cisco Connection Documentation section (continually updated)

• Cisco Connection Documentation, Enterprise Series CD (formerly called UniverCD)

Incrementally Installing Device Packages

There are several ways to add (or incrementally install) support for new devices to CiscoView 4.2(1). Direct customers should refer to the section "Cisco Connection Online" at the end of this release note for information about accessing CCO. Partner-initiated customers should refer to the section "Partner Initiated Customer Accounts."

Downloading Device Packages from CCO

You can add new devices to CiscoView from the CiscoView Upgrade Planner page on CCO at http://www.cisco.com/kobayashi/library/netmanage/cview/. On this page, go to the section "Download CiscoView Software Updates" and click "CiscoView 4.x Packages." From the "CiscoView 4.x Packages" page, you can download packages for all supported devices. For more information, refer to the "Downloading Device Packages" chapter in Getting Started with CiscoView. A quick reference version exists in the CiscoView CD Installation Instructions booklet.

Determining Which Package to Download

In general, multiple devices within the same product family share a single device package. If you have a specific device in mind, look for the device package for the device's family.

To determine if your particular device is supported, look at the readme for the device package (available on the same webpage listed in the previous section).

For Solaris

Do not use the pkgadd command for installation. Instead, use the setup.sh command. See the CiscoView CD Installation Instructions booklet for the most up-to-date version of install.

Partner Initiated Customer Accounts

http://www.cisco.com/acs/info/pica.html

You can also refer to the "Downloading Device Packages" chapter in Getting Started with CiscoView.

Caveats Fixed in This Release

Table 20 (following) lists caveats in CiscoView 4.1(1) that are fixed in CiscoView 4.2(1). Only the most serious caveats resolved in CiscoView 4.2(1) are listed.

Applet and device package caveats that have been fixed since the previous release are described in the respective applet and device package readme files. (These readme files are available from the CiscoView Upgrade Planner:

http://www.cisco.com/kobayashi/library/netmanage/cview)

Troubleshooting

If you cannot open a device in CiscoView 4.2(1), a message appears indicating that the device is unmanageable for one of the following reasons:

• The Simple Network Management Protocol (SNMP) agent is not running in the device.

You can still ping the device from the management station.

• You have entered an incorrect community string in the File>Open Device window.

• The management station cannot access or successfully ping the device. This could be caused because the request timed out or because there was a noSuchName condition.

If the request timed out, you can try increasing the timeout period, verifying the write community string, or checking that the device is reachable.

If there was a noSuchName condition, verify the write community string.

• You are missing the device package.

If you try to access a device when the device package is not installed in CiscoView, CiscoView displays the following error message:

CiscoView is unable to open devicename because you do not have the appropriate device package installed on your machine. You can download the latest device package from the CiscoView Upgrade Planner:

http://www.cisco.com/kobayashi/library/netmanage/cview

If you receive this error message, you should access the specified URL, and download and install the correct device package.

• You have an obsolete version of a device package.

Check your device package and compare the date with the version on CCO at http://www.cisco.com/kobayashi/library/netmanage/cview. Upgrade your device package to the latest version, if required.

Installation Notes and Caveats

This section contains installation notes and caveats for CiscoView.

setenv SNMHOME /opt/SUNWconn/snm
set path=($path /opt/SUNWconn/snm/bin)
 

SNMHOME=/opt/SUNWconn/snm
export SNMHOME
PATH=$PATH:/opt/SUNWconn/snm/bin
export PATH
 

line 27: Unknown record name 'component.cisco-c8510'
line 27: Cannot initialize field value component.cisco-c8510
failed in loading /opt/SUNWconn/snm/struct/Cat5500.schema
 

  line 46: syntax error
  line 49: syntax error
  failed in loading /opt/SUNWconn/snm/struct/Cat3900.schema
 

General Notes and Caveats

This section contains general notes and caveats. They are divided into five sections:

• Notes and Caveats for Enterprise Network Management Products 79

• Notes and Caveats for Workgroup Products 82

• Notes and Caveats for Access Products 89

• Notes and Caveats for High-End Business Products 90

• Notes and Caveats for WanBU/NSMBU Devices 92

• Notes and Caveats for Online Help 93

Notes and Caveats for Enterprise Network Management Products

line 27: Unknown record name 'component.cisco-c8510'
line 27: Cannot initialize field value component.cisco-c8510
failed in loading /opt/SUNWconn/snm/struct/Cat5500.schema
 

line yyy: Duplicate attribute name <attrname>
line xxx: Duplicate error code <errcod>
failed in loading /opt/SUNWconn/snm/agents/CISCO-STACK-MIB.schema.
 

Notes and Caveats for Workgroup Products

Notes and Caveats for Access Products

Notes and Caveats for High-End Business Products

Notes and Caveats for WanBU/NSMBU Devices

WanBU/NSMBU device packages are available to be downloaded from CCO.

If you run CiscoView from HP OpenView and use WAN package files, and you are not using WAN Manager, CiscoView has the following limitations:

• CiscoView will not launch from topology maps or pull-down menus.

• Ciscoview does not support topology discovery with automatic icon identification.

• CiscoView does not support MIB and Trap integration.

These limitations exist because WAN Manager will eventually replace the existing Equipment Manager GUI with CiscoView, and the WAN package files have been designed to integrate with WAN Manager.

For additional information about platform availability and support, see the CiscoView Upgrade Planner page on CCO at http://www.cisco.com/kobayashi/library/netmanage/cview/, and click the "What's Hot for CiscoView and CiscoWorks Windows" link.

Notes and Caveats for Online Help

• Find Tab. Because of the way a master CiscoView contents file is used by the software when multiple CiscoView device package help files are present, the list of files to include when setting up a customized find operation contains multiple items called CiscoView. [CSCdj62089]

• Online Help Intermittent Display Problem. There is a problem with the online help viewer, HyperHelp, intermittently displaying the Help topic window when opening Help>Contents.

When you first open a help topic using Help>Contents and click the Back button, the HyperHelp viewer might display a blank window. This is a HyperHelp bug. [CSCdi04758]

Troubleshooting

Before providing troubleshooting procedures, this section describes the CWSI Campus daemons and their interactions with clients.

Asynchronous Network Interface (ANI)

Asynchronous Network Interface (ANI or AniServer) is a multithreaded Java program. ANI is responsible for the discovery of the network for both devices and users. ANI is also responsible for all communication with the clients.

Database Engine

The database engine (dbeng50) is responsible for checkpointing all ANI information into the database and for storing historical data for the UserTracking application. For ANI, this is a checkpoint only. ANI performs all of its operations from the data stored in memory. The database stores user-entered information and allows ANI to load its data model quickly into memory upon a subsequent restart. (The CRM database engine has the same name, so your system should be running two processes with this name.)

CORBA Agent

The CORBA agent (osagent) is responsible for interprocess communication messages. All servers must register with the osagent. All clients looking for service can find it with the help of the osagent. The CWSI Campus login window is used to indicate the name of the ANI server that the osagent should locate.

You can enter a command to view all servers registered with CORBA. However, before executing this command, you must make sure that the environment variable for the OSAGENT_PORT is set to 42342. To do this, enter the following command:

/setenv OSAGENT_PORT 42342
 

Then to see all servers registered with CORBA, and where they are located, enter:

/opt/CSCOpx/lib/visigenics/bin/osfind
 

RTPoller

RTPoller is used to obtain real-time data for graphing in the AtmDirector application.

Event Channel

The event channel (EventChannel) is used to send events to all servers and clients who have registered with it.

Stopping and Starting CWSI Campus Daemons

The following command-line scripts control the CWSI Campus daemons:

• stopcwsiserver stops the CWSI Campus daemons.

• startcwsiserver starts the CWSI Campus daemons.

To use these scripts, log in as Super User and enter the $CWSIROOT/bin directory. Open a shell window Command Prompt window. Enter stopcwsiserver to stop the CWSI Campus server processes. When the shell prompt returns, all the daemons have been stopped. Wait a few moments for all processes to stop before restarting. To restart the processes, enter startcwsiserver and wait until the shell prompt returns. Wait a few minutes to allow the processes to start and get into a steady state before starting CWSI Campus.

After running osfind, if you see that the AniServer or one of the other servers is missing, or you see in the processes lookup that your database engine is missing, stop the CWSI Campus servers and start them again.

When CWSI Campus Cannot Log Into AniServer

If you have just rebooted your machine and are unable to log in to AniServer, ANI may not yet be ready to receive messages. Wait five minutes, then try again.

If you are still unable to log in, run the osfind program to verify that AniServer has registered with the OSAgent. If so, verify that the name of AniServer in the login box is the same name as the name registered with OsAgent.

If you do not find AniServer, run the stopcwsiserver script (see "Stopping and Starting CWSI Daemons," earlier in this section), and then run the startcwsiserver script. Run osfind again. If AniServer is there, log into CWSI. If AniServer is still not registered, you might have a corrupt database.

You will need to reinitialize the corrupt database, which will delete all current data in the database. To do this, follow these steps:

1. Log in as Super User.

2. Go to the $CWSIROOT/bin directory.

3. Run reinitdb.

Documentation and Additional Resources

In addition to these release notes and online help, the CWSI Campus documentation set includes the following documents:

• Installing Resource Manager Essentials and CWSI Campus on Solaris

• Getting Started with Resource Manager Essentials

• Getting Started with CWSI Campus

• Using the Campus VlanDirector Application

• Using the Campus UserTracking Application

• Using the Campus TrafficDirector Application

• Using the Campus AtmDirector Application

• Getting Started with CiscoView

• Manual pages for Essentials located in the /opt/CSCOpx/man/man1 directory

Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM, a member of the Cisco Connection Family, is updated monthly. Therefore, it might be more up to date than printed documentation. To order additional copies of the Documentation CD-ROM, contact your local sales representative or call customer service. The CD-ROM package is available as a single package or as an annual subscription. You can also access Cisco documentation on the World Wide Web at http://www.cisco.com, http://www-china.cisco.com, or http://www-europe.cisco.com.

If you are reading Cisco product documentation on the World Wide Web, you can submit comments electronically. Click Feedback on the toolbar, and then select Documentation. After you complete the form, click Submit to send it to Cisco. We appreciate your comments.

A CCO web page for Essentials contains links to marketing and technical documentation and includes the latest downloadable Essentials packages. To find the latest Essentials information, point your web browser to the following location:

http://www.cisco.com/kobayashi/sw-center/netmgmt/cw2000

Service and Support

For service and support for a product purchased from a reseller, contact the reseller. Resellers offer a wide variety of Cisco service and support programs, which are described in the section "Service and Support" in the Information Packet that shipped with your product.

For service and support for a product purchased directly from Cisco, use CCO.

Cisco Connection Online

Cisco Connection Online (CCO) is Cisco Systems' primary, real-time support channel. Maintenance customers and partners can self-register on CCO to obtain additional information and services.

Available 24 hours a day, 7 days a week, CCO provides a wealth of standard and value-added services to Cisco's customers and business partners. CCO services include product information, product documentation, software updates, release notes, technical tips, the Bug Navigator, configuration notes, brochures, descriptions of service offerings, and download access to public and authorized files.

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 supports Zmodem, Kermit, Xmodem, FTP, and Internet e-mail, and it 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.

You can access CCO in the following ways:

• WWW:  http://www.cisco.com

• WWW:  http://www-europe.cisco.com

• WWW:  http://www-china.cisco.com

• Telnet:  cco.cisco.com

• Modem:  From North America, 408 526-8070; from Europe, 33 1 64 46 40 82. Use the following terminal settings: VT100 emulation; databits: 8; parity: none; stop bits: 1; and connection rates up to 28.8 kbps.

For a copy of CCO's Frequently Asked Questions (FAQ), contact cco-help@cisco.com. For additional information, contact cco-team@cisco.com.

Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM, a member of the Cisco Connection Family, is updated monthly. Therefore, it might be more current than printed documentation. To order additional copies of the Documentation CD-ROM, contact your local sales representative or call customer service. The CD-ROM package is available as a single package or as an annual subscription. You can also access Cisco documentation on the World Wide Web at http://www.cisco.com, http://www-china.cisco.com, or http://www-europe.cisco.com.

If you are reading Cisco product documentation on the World Wide Web, you can submit comments electronically. Click Feedback in the toolbar and select Documentation. After you complete the form, click Submit to send it to Cisco. We appreciate your comments.

Posted: Thu Sep 30 12:25:27 PDT 1999
Copyright 1989-1999©Cisco Systems Inc.