Release Notes for CiscoWorks2000 CD One, 4th Edition on Windows 2000 and Windows NT

Table Of Contents

Release Notes for CiscoWorks2000
CD One 4th Edition on Windows 2000 and Windows NT

New Features

Documentation Roadmap

Additional Release-Specific Information Online

Time Zone Acronyms and Offset Settings

Multi-Homed Machines

Security Enhancement

Operating System Upgrade

Support Information

Documentation Errata

CD One 4th Edition Known Problems

CD One Installation Known Problems

CiscoView Known Problems

Desktop Known Problems

Catalyst Devices Known Problems

Router and Hub Known Problems

General Device Package Known Problems

Package Support Updater (PSU) Known Problems

Integration Utility Known Problems

CA-Unicenter Adapter Known Problems

ANI Server Known Problems

Device/Agent Known Problems Impacting ANI Server

Browser Known Problems

General Known Problems

Obtaining Documentation

World Wide Web

Documentation CD-ROM

Ordering Documentation

Documentation Feedback

Obtaining Technical Assistance

Cisco.com

Technical Assistance Center

Release Notes for CiscoWorks2000
CD One 4th Edition on Windows 2000 and Windows NT

These release notes are for use with the Windows 2000 and Windows NT server version of CiscoWorks2000 CD One 4th Edition.

These release notes provide the following information:

• New Features

• Documentation Roadmap

• Additional Release-Specific Information Online

• Time Zone Acronyms and Offset Settings

• Multi-Homed Machines

• Security Enhancement

• Operating System Upgrade

• Support Information

• Documentation Errata

• CD One 4th Edition Known Problems

• Obtaining Documentation

• Obtaining Technical Assistance

New Features

CD One contains the following new features:

•Scalability—The ANI Server is capable of managing 1500-2000 devices, and 40,000 user-tracking database entries.

•Security enhancement—CiscoWorks2000 applications are now installed using the user casuser. For further information, see the "Security Enhancement" section.

•Support—CiscoWorks2000 contains support for the following:

–AniClient support for Java Plug-in.

–Workflow server and application support.

•VTP server independence—CiscoWorks2000 supports VTP domains with and without a VTP server.

Cisco View, a component of CD One, contains the following new features:

•Device list import—Rapid loading and subsequent accessing of devices.

•Device support enhancements—Both CiscoView and Campus Manager contain device support enhancements for several Cisco Products. For lists of supported devices, see below:

– CiscoView—http://www.cisco.com/kobayashi/sw-center/netmgmt/ciscoview/cvcww-download.shtml.

– Campus Manager— http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/
cw2000/camp_mgr/sup_dev/dev_spt.htm.

•New progress indicator—Provides status feedback on task execution.

•Performance improvements—CiscoView contains performance improvements in the Monitor menu, Configuration menu, and Chassis view.

•Remote upgrade of user preferences and device packages—CiscoView allows for remote upgrades of user preferences and device packages from previous versions of CiscoView.

•Web-based Package Support Updater (PSU)—Scheduled and on-demand device support downloads from CCO.

Documentation Roadmap

The following documents are provided in PDF on your product CD:

•Installing and Setting Up CD One on Windows 2000 and Windows NT—This document provides installation instructions, including both server and client side system requirements, steps for installing and uninstalling, and installation troubleshooting information.

•Getting Started with the CiscoWorks2000 Server—This document provides information about setting up, administering, and assessing the CiscoWorks2000 Server, used by all CiscoWorks2000 applications.

•Using CiscoView 5.3—This document provides information about the use and operation of CiscoView, and also provides descriptions and scenarios for users or prospective users of this management tool.

Note Adobe Acrobat Reader 4.0 is required.

•CiscoView Quick Start Demo—The Quick Start Demo is a multi-media program that walks you through basic features of CiscoView. To get to the Quick Start Demo, click Main Help Contents > Device Manager > CiscoView > Quick Start Demo in the product CD.

•Online Help for CiscoView and CiscoWorks2000 Server.

•Online Help for Package Support Updater.

Note Feedback on any Cisco documentation is always welcome. For instructions on providing feedback, see the "Documentation Feedback" section.

Additional Release-Specific Information Online

For information about CD One 4th Edition supported devices, refer to:

•Device Package Readme Files—Contain information about device, card, and platform support

•Device Package Installation Instructions—
http://www.cisco.com/kobayashi/sw-center/netmgmt/ciscoview/
cvcww-download.shtml

Time Zone Acronyms and Offset Settings

Table 1 shows time zone acronyms supported in the CiscoWorks2000 applications that use the time zone feature. Column 1 alphabetically lists the supported CiscoWorks2000 time zone acronyms. Change Audit reports may display time zone information differently. Column 2 lists the spelled out time zone definition. Column 3 lists the area covered by the time zone. Column 4 lists the column's offsets from Greenwich mean time (GMT). Column 5 lists the time zone setting for that zone's server and column 6 lists the resulting output in reports.

If you generate reports, output will vary depending on whether the data has been processed through Perl or Java. Table 1 also provides possible output for either case scenario.

To ensure that time zones are translated correctly—especially when your devices, servers, and clients are in different time zones—follow these guidelines:

•When configuring time zones on managed devices, use the acronyms listed in the "Time Zone Acronym Setting on Device" column. To set time zones on devices, use the command described in the device-specific Command Reference documentation.

•When configuring time zones on CiscoWorks2000 servers, use the supported values in the "Time Zone Setting on Server" column.

Note Changes made to the system time zone from outside CiscoWorks2000 applications might not be reflected in already-running CiscoWorks2000 applications. After
changing the time zone, restart all CiscoWorks2000 applications.

Table 1 Supported Server Time Zones

Time Zone Acronym Setting on Device

Definition

Area Covered (Country/City)

Offset from GMT

Time Zone Setting on Server

Output in Report

GMT

Acronym

ACT

Australia Central Time

Australia/ Darwin

+9:30

Adelaide

GMT +9:30

ACT

AEST

Australia Eastern Standard Time

Australia/ Sydney

+10:00

+11:00 (DST)

Brisbane

GMT +10:00

GMT +11:00 (DST)

AEST

AET

Australia Eastern Time

Australia/ Sydney

+10:00

Brisbane

GMT +10:00

GMT +11:00 (DST)

AET

AHST

Alaska-Hawaii Standard Time

Hawaii/ Honolulu

-10:00

Hawaii

GMT -10:00

HST

ART

Arabic Egypt Standard Time

Africa/Cairo

+2:00

+3:00 (DST)

Cairo

GMT +2:00

GMT +3:00 (DST)

ART

CCT

China Coast Time

Asia/
Shanghai

+8:00

Beijing

GMT +8:00

CST

CDT

Central Daylight Time

United States/ Chicago

-5:00

Central Time

GMT -5:00

CDT (DST)

CST

CET

Central European Time

Spain/Madrid

+1:00

+2:00 (DST)

Madrid

GMT +1:00

GMT +2:00 (DST)

CEST

CST

Central Standard Time

United States/ Chicago

-6:00

Central Time

GMT -6:00

CST

CDT (DST)

CTT

China Taiwan Time

Asia/
Shanghai

+8:00

Beijing

GMT +8:00

CST

EAST

East Australian Standard Time

Australia/ Queens Island

+10:00

Brisbane

GMT +10:00

EAST

ECT

European Central Time

Europe/Paris

+1:00

+2:00 (DST)

Paris

GMT +1:00

GMT +2:00 (DST)

CEST

EDT

Eastern Daylight Time

United States/
New York

-4:00

Eastern Time

GMT -4:00

EST

EDT (DST)

EST

Eastern Standard Time

United States/
New York

-5:00

Eastern Time

GMT -5:00

EST

EDT (DST)

FWT

French Winter Time

France/Paris

+1:00

+2:00 (DST)

Paris

GMT +1:00

GMT +2:00 (DST)

CEST

GMT

GMT Standard Time

Africa/ Casablanca

None

Greenwich Mean Time

GMT +0

GMT

HST

Hawaiian Standard Time

Pacific/ Honolulu

-10:00

Hawaii

GMT -10:00

HST

JST

Japan Standard Time

Asia/Tokyo

+9:00

Tokyo

GMT +9:00

JST

MDT

Mountain Daylight Time

United States/ Denver

-6:00

Mountain Time

GMT -6:00

MDT (DST)

MST

MET

Middle European Time

Spain/Madrid

+1:00

+2:00 (DST)

Madrid

GMT +1:00

GMT +2:00 (DST)

CEST

MEWT

Middle European Winter Time

Spain/Madrid

+1:00

Madrid

GMT +1:00

GMT +2:00 (DST)

CEST

MST

Mountain Standard Time

United States/ Denver

-7:00

Mountain Time

GMT -7:00

MST

MDT (DST)

PDT

Pacific Daylight Time

United States/
Los Angeles

-7:00

Pacific Time

GMT -7:00

PDT (DST)

PST

PST

Pacific Standard Time

United States/
Los Angeles

-8:00

Pacific Time

GMT -8:00

PST

PDT (DST)

UCT

GMT Standard Time

Great Britain/ London

None

Greenwich Mean Time

GMT +0

GMT

ZP4

Zone 3

Russia/
Moscow

+4:00

Not Supported

GMT +4:00

ZP4

Multi-Homed Machines

A multi-homed machine is a machine that has multiple NIC cards, each configured with different IP addresses. To run CD One on a multi-homed machine, there are two requirements. First, all IP addresses must be configured in DNS. Second, because of restrictions with CORBA, only one IP address can be used by the client/browser to access the server. You must select one IP address as the external address, with which the client will login to the CiscoWorks2000 server.

To select an IP address, modify the gatekeeper file located in opt/CSCOpx/lib/vbroker/gatekeeper.cfg. Replace every instance of "<external-IP-address>" with the external IP address you choose, and remove the "#" character, from the following:

•#vbroker.gatekeeper.backcompat.callback.host=<external-IP-address>

•#vbroker.se.exterior.host=<external-IP-address>

•#vbroker.se.iiop_tp.host=<external-IP-address>

•#vbroker.se.interior.host=<external-IP-address>

After modifying the gatekeeper file, restart the Daemon Manager by entering /etc/init.d/dmgtd start.

Note To look up this topic on Bug Navigator II, use bug ID CSCds84075. For more information on using Bug Navigator II, see the "CD One 4th Edition Known Problems" section.

Security Enhancement

To address a CiscoWorks2000 security issue, CD One and other related applications will no longer be installed under the user bin. Beginning with CD One, 4th Edition, CiscoWorks2000 applications will be installed under the new user casuser, which belongs to the new group casusers. The role of casuser is to provide day-to-day product administration and maintenance without root privileges.

In Windows 2000 and Windows NT, the casuser account has the following attributes:

•Randomized password

•No Windows administrative privileges

During an upgrade to CD One 4th Edition, the following occurs: all currently installed CiscoWorks2000 applications, with the exception of CD One, are disabled. File permissions are transferred to the user casuser, which is created along with the group casusers. Key data from these applications, such as community strings and user and host information, are archived. As the latest versions of the applications are installed, they are re-enabled and the necessary archived data is imported.

Caution Do not give a login shell or create a password for the user casuser. To do so will affect accountability in CiscoWorks2000. If a user is not a member of the group casusers, and wants to run CiscoWorks2000 commands from a shell prompt, add that user to casusers.

Note To look up this topic on Bug Navigator II, use bug ID CSCdj26280. For more information on using Bug Navigator II, see the "CD One 4th Edition Known Problems" section.

Operating System Upgrade

If an operating system upgrade is done after CD One is installed, you must re-install CD One.

Re-installing CD One will allow the installation process to check for required service packs. Install any service packs that are found missing. For a list of required service packs, see Chapter 1 of Installing and Setting Up CD One on Windows 2000 and Windows NT.

If CiscoWorks2000 does not operate properly after installing all necessary service packs, check the permissions on the directory <install-directory>\objects\dmgt\ready. Administrators and casusers must have full access. If the permissions are incorrect, stop the daemon manager, change the permissions, and start the daemon manager again.

Caution If CD One is run without the required service packs, it will not function properly.

Note To look up this topic on Bug Navigator II, use bug ID CSCdt32795. For more information on using Bug Navigator II, see the "CD One 4th Edition Known Problems" section.

Support Information

CiscoWorks2000 supports the following:

•Operating System—CiscoWorks2000 supports both the English and Japanese versions of the following operating systems:

–Windows 2000, Professional and Server, with Service Pack 1.

–Windows NT 4.0 with Service Pack 6a.

•Browser—CiscoWorks2000 supports both the English and Japanese versions of the following browsers:

–Netscape 4.75.

–Internet Explorer 5.5 with Service Pack 1.

•Hardware—CiscoWorks2000 supports IBM PC-compatible computer with an Intel Pentium III or Pentium IV processor.

Note Previous editions of CiscoWorks2000 will not support Pentium IV processors.

•Java—CiscoWorks2000 uses two types of Java. Certain applications use the browser's native Java Virtual Machine (JVM), while others use Sun's Java Plug-in. In order for CiscoWorks2000 to function correctly, you must be using the correct version of Java.

The supported native JVM versions are as follows:

–Microsoft Internet Explorer 5.5—JVM 5.0.0.3186 or later.

–Netscape 4.75—the correct version of JVM is installed.

The supported Java Plug-in versions are as follows:

–Windows 9x, NT, and 2000—Java Plug-in 1.3.0.

–Solaris—Java Plug-in 1.3.0.

–AIX—Java Plug-in 1.3.0.

–HP-UX—Java Plug-in 1.2.2.

Note The Plug-in version is independent of the browser used.

To install the Java Plug-in, follow the steps below:

–Internet Explorer—When you attempt to launch any CiscoWorks2000 application that uses the Java Plug-in for the first time, Internet Explorer will automatically install the correct Java Plug-in version for you.

–Netscape—When you attempt to launch any CiscoWorks2000 application that uses the Java Plug-in for the first time, CiscoWorks2000 will redirect you to a page from which you can download and install the correct Java Plug-in version.

–Manual Installation—To manually install the Java Plug-in, refer to Chapter 3 of Getting Started with the CiscoWorks2000 Server.

Note CiscoWorks2000 only supports the Java Plug-in versions mentioned above. Installing a different version, including a newer version, can cause CiscoWorks2000 to malfunction.

To see Java related messages, look in the the Java console. To do this, enable and then open the Java console. There are two Java consoles involved: the native JVM's Java console and the Java plug-in's Java console.

To enable the native JVM console when using Internet Explorer:

a. Select Tools > Internet Options > Advanced.

b. Click Java Console.

c. To open the console select View > Java Console.

To enable the native JVM console when using Netscape:

a. Select Preferences > Advanced > Enable Java.

b. To open the console select Communicator > Tools > Java Console.

To enable the Java Plug-in console when using Windows 98, NT, or 2000:

a. Select Start > Settings > Control Panel.

b. Double-click Java Plug-in.

c. Select Enable Java Console.

To enable the Java Plug-in console when using Solaris, AIX, or HP-UX:

a. Run the program <Pathname to your Java 2 runtime environment installation directory>/bin/ControlPanel.

b. Select Show Java Console.

Note The Java Plug-in console will automatically open when you launch an application that uses it.

Documentation Errata

The following are areas in which documentation may be inaccurate or have become outdated:

•Disregard references to Event Query which appear in some copies of the Getting Started Guide with the CiscoWorks2000 Server. The option is no longer available.

•Disregard the section in Getting Started Guide with the CiscoWorks2000 Server which reads,

"Microsoft Windows Systems—CiscoWorks2000 must be installed by the administrator and is installed as the user casuser. The user casuser is created at install time and will prompt for a password."

The section can be found in the "Files, File Ownership, and Permissions" section of Appendix B. It should read,

"Microsoft Windows Systems—CiscoWorks2000 must be installed by the administrator and is installed as the user casuser.

–If it is a new installation, the system displays a Yes/No message box asking whether to proceed creating the user casuser with a 14-character randomized password.

–If it is not a new installation, the system displays a Yes/No message box asking whether to proceed with resetting the password to a randomized 14-character password."

Note For more information on the role of the user casuser, see the "Security Enhancement" section

•Disregard substep b of the "Typical Installation" section, found in Chapter 2 of Installing and Setting up CD One on Solaris. This step should read,

"Select the adapter from the list of available adapters, or select other to choose an adapter that is not listed (you will be prompted to enter the path name of the adapter) and click Next.
If you select none, go to Step 5."

CD One 4th Edition Known Problems

Known problems are unexpected behaviors or defects in CiscoWorks2000 CD One software releases. They are graded according to severity level. These release notes contain information for severity level 1 and 2 known problems, as well as any severity level 3 known problems that are customer found.

You can search for known problems on the Cisco bug tracking system tool, called Bug Navigator II.

To access Bug Navigator II, enter http://www.cisco.com/support/bugtools in your web browser or log into Cisco.com and select Service & Support > Technical Assistance Center > Tools > Software Bug Toolkit > Bug Navigator II.

The CD One known problems are broken down into the following sections:

• CD One Installation Known Problems

• CiscoView Known Problems

• Desktop Known Problems

• Catalyst Devices Known Problems

• Router and Hub Known Problems

• General Device Package Known Problems

• Package Support Updater (PSU) Known Problems

• Integration Utility Known Problems

• CA-Unicenter Adapter Known Problems

• ANI Server Known Problems

• Device/Agent Known Problems Impacting ANI Server

• Browser Known Problems

• General Known Problems

CD One Installation Known Problems

One problem of note is CSCdt26215. Installing CD One on a Pentium 4 machine results in two errors regarding configuring JRE2 and testing for JIT options. These errors are harmless. Click OK when both errors appear to allow installation to continue.

Table 2 CD One Installation Known Problems

ID

Summary

Explanation

None.

Installing CD One returns an error message stating that there is not enough space on the C: drive to complete the process.

Installation requires 20 MB of space in Windows temporary directory: C:\Temp on most systems. If destination path is other than default and drive where \Temp directory resides does not have required space, error occurs.

CSCds07866

Unable to access ODBC Database.

If ODBC Driver Manager installed on machine is an earlier version than 3.51, ODBC database access will fail.

Problem caused by version mismatch of Sybase ODBC driver and ODBC Driver Manager. Sybase v6 requires ODBC Driver Manager 3.51 or later.

To correct problem, download MDAC 2.5 Service pack or later, which includes proper ODBC Driver Manager, from http://www.microsoft.com/data/, and install it as instructed.

CSCds33712

Re-installation of CD One fails when IPM installed on same machine.

If IPM is installed on machine that has RWAN bundle, re-installation of CD One may fail due to a shared library being locked. Problem also occurs when CiscoWorks2000 and IPM installations exist on same machine and you install or upgrade other CiscoWorks2000 components.

To work around problem:

1. Run ipm stop

2. Run ipm cw2ksetup uninstall

3. Re-install CD one

4. Run ipm cw2ksetup install

5. Run ipm start

The first two steps remove IPM's dependency on the shared library and the last two steps integrate IPM with CiscoWorks2000.

CSCds90562

Daemon manager fails to run if CiscoWorks2000 home directory is encrypted.

CiscoWorks2000 does not support encrypted directories.

CSCdt21743

Configuration files in Trivial File Transfer Protocol (TFTP) boot directory not secure.

The configuration files, stored in the TFTP boot directory during the TFTP operation, have permission for everyone, though files are owned by the user casuser. Situation only exists for a short time while download in progress.

No workaround is available at this time.

CSCdt31121

Cisco Voice Manager processes need to be stopped before upgrading to CD One, 4th Edition.

To stop Cisco Voice Manager processes:

(Windows NT/2000 clients)

At command line prompt, enter:
net stop "CVM Server and Poller Service"

(Solaris clients)

At command line prompt, enter:
/etc/init.d/cvm stop

CSCdt32795

CiscoWorks2000 malfunctions if operating system upgraded after installation.

For further information, including how to work around problem, see the "Operating System Upgrade" section.

CSCdt63101

When installing CiscoWorks2000 as non-root user, improper message occurs.

When installing CiscoWorks2000 under a non administrator account on Windows 2000, the following message occurs:
Setup Initialization Error Setup has detected that unInstallshield is in use. Please close unInstallshield and restart setup. Error432.

When the OK button is clicked, installation is terminated.

To work around problem, run installation from an administrator's account.

CiscoView Known Problems

Table 3 CiscoView Known Problems

ID

Summary

Explanation

CSCdr33955

Multiport monitor graphs for device running CiscoView display incorrect values.

To avoid problem, generate monitor graphs for individual ports.

CSCdr67552

Chassis window does not repaint properly after being resized.

Problem observed in HP-UX clients running CD One 3rd Edition and later.

To work around problem, close and relaunch CiscoView.

CSCdr88151

Chassis view cannot be printed from HP-UX clients running CiscoView 5.3.

With chassis view open, click Print icon and blank pages are printed.

To work around problem, print screen captures of chassis view.

CSCds41560

Printing chassis view from CiscoView running in Internet Explorer 5.x returns error.

Observed on NT client running CiscoView in Internet Explorer 5.x. Following actions result in problem:

1. Open a device and bring up chassis view.

2. Select File > Print to print chassis view and error message is returned.

To avoid problem, click Print icon to print chassis view.

CSCds73008

Bean Control window is sometimes displayed after selecting "Import Device List" from CiscoWorks2000 desktop.

Problem observed in CD One 3rd Edition and later running in Internet Explorer.

To work around problem, close and relaunch CiscoWorks2000.

CSCdt04355

CiscoView console buttons cannot be selected with Enter key.

Problem observed in CD One 3rd Edition and later.

To work around problem, use mouse or spacebar to activate selection instead of Enter key.

CSCdt11838

When launching application, user not prompted to install Java Plug-in.

For further information, refer to CSCdt11838 in the "CD One Installation Known Problems" section.

CSCdt22462

Delay when downloading Java applets on Win2K.

For a detailed explanation of this problem, refer to CSCdt22462 in the "General Known Problems" section.

CSCdt43794

Configure window displayed behind main chassis window in CiscoView 5.x, Japanese Edition.

Problem observed in CiscoView 5.x, Japanese Edition, running in Navigator 4.75 on Windows 2000 Professional client. Select Configure from context (right-click) menu and Configure window is displayed behind main CiscoView chassis window.

To avoid problem, open configuration dialog by double-clicking component. Configure window will launch automatically and be properly displayed.

CSCds53413

Shortcuts in the My Shortcuts folder cannot be deleted.

No workaround is available at this time.

CSCdt79469

Button labels not completely displayed in CiscoView running in Navigator on HP-UX client.

With CiscoView running in Navigator on HP-UX client, button labels in main window and other dialog boxes are truncated and displayed with ellipsis.

To work around problem:

•Change display resolution on your monitor to a higher value; or

•Select a different category and click OK to apply any changes made in previous category.

Desktop Known Problems

Table 4 Desktop Known Problems

ID

Summary

Explanation

CSCds82867

Device Center inaccessible for Catalyst 6500 device.

When a Catalyst 6500 device is added to RME 3.1 Inventory Manager 3.2, it is not visible in Device Center.

To work around problem, access Device Center from RME instead of from Campus Manager.

Catalyst Devices Known Problems

Note If you have problems using the online help, download the latest device packages from CCO.

Table 5 Catalyst Devices Known Problems (2900, 4000, 5000, 5500, 6000, 8800)

ID

Summary

Explanation

CSCdr34879

All ports on WS-X6608-T1 are shown as green on a Catalyst 6000 device running CiscoView.

Only ports that are configured and connected should be shown as green.

Problem caused by lack of mapping between MIB elements in agent and colors of ports on the board.

No workaround is available at this time.

CSCds72290

Running CiscoView 5.x on device with Cisco IOS 12.1(2)E installed returns error.

Problem observed on Catalyst 2612 and Catalyst 6509 devices with Cisco IOS 12.1(2)E installed running CiscoView 5.x.

Following error is displayed: Failed to refresh chassis. Refer to error log for details.

No workaround is available at this time.

CSCds78228

Contents of Catalyst 5000 device package readme file is different from what is listed in Package Details window.

Select Device Manager > View Installed Packages from CiscoWorks2000 desktop, then click Details icon for Catalyst 5000 device package to bring up Package Details window.

Although text in readme file link states "Readme file for Cat5000 (1.2)," click link and "Catalyst 5000 (1.3) Installation" instructions are displayed instead.

Router and Hub Known Problems

Table 6 Router and Hub Known Problems

ID

Summary

Explanation

CSCdr39315

2524 device running Cisco IOS 12.05T and CiscoView 5.x does not display SM25-T1 card. A blank slot is shown instead.

No workaround is available at this time.

CSCds55193

Incorrect formula used to calculate interface error percentage is listed in CiscoView online help.

CiscoView online help lists following as formula used to calculate interface error percentage: [ifInErrors /(ifInUcastPkts + IfInNUcastPkts)] *100.

Correct formula is: [ifInError /(ifInUcastPkts + IfInNUcastPkts + ifInError+ifInUnknownProtos)] * 100.

CSCds86109

CiscoView 5.x, running on Cisco 1600 and 4000 series devices, displays a high number of collisions.

No workaround is available at this time.

CSCdt02050

Flash (PCMCIA) card is not displayed on Cisco 7000 series device running CiscoView.

No workaround is available at this time.

CSCdt07445

Unable to configure ports on Cisco7000 series device with Cisco 7200 device package installed.

Following actions result in problem:

1. Launch CiscoView and open device.

2. With a port selected, open Configure dialog box.

3. Make changes to port settings and internal error is displayed.

No workaround is available at this time.

CSCdt26857

Cannot retrieve ATM statistics for ATM ports on devices with Cisco 7000 device package installed.

At present, only Interface statistics and several categories of SONET statistics can be retrieved.

No workaround is available at this time.

General Device Package Known Problems

Table 7 General Device Package Known Problems

ID

Summary

Explanation

CSCdr94291

In CiscoView, NEMI configuration dialog box for Metro 1500 device displays N/A as Subnet mask value.

NEMI configuration dialog box should display 255.255.255.0 as Subnet mask value.

No workaround is available at this time.

CSCdr96333

HP OpenView topology map displays generic icon for Metro 1500 device.

Following actions result in problem:

1. Install HP OpenView and then CiscoView 5.1.

2. Run NMIM integration.

3. Using Device Support Utility, install Metro 1500 device package version 1.2.

4. Launch HP OpenView.

5. Select Edit > Add Object > Cisco FastHub > Metro 1500.

6. Click on Metro 1500 icon and drag it into topology map.

No workaround is available at this time.

Package Support Updater (PSU) Known Problems

Table 8 Package Support Updater (PSU) Known Problems

ID

Summary

Explanation

CSCdt04070

No error message is displayed when network connection is lost during the download of device packages from CCO.

No workaround is available at this time.

CSCdt24701

No error message is displayed after an unsuccessful attempt to uninstall nmidb packages.

After unsuccessful attempt to uninstall nmidb packages, no error message is displayed stating that process failed. Also, in View History window, completed successfully is displayed under status tab when failed should be displayed instead.

No workaround is available at this time.

CSCdt35177

PSU is displayed without a banner and left frame in browser.

To avoid problem, make sure your browser's caching policy is not set to "Never". Set caching policy to "Every visit to the page" in Internet Explorer browsers and "Every time" in Netscape browsers.

CSCdt36869

Installing same device package from CCO using multiple PSU sessions results in errors.

Errors are returned when device packages are downloaded and installed from CCO using PSU web interface and standalone PSU (psu, xpsu) at the same time.

To avoid problem, do not use PSU web interface and standalone PSU simultaneously to download device packages from CCO.

CSCdt73771

Error message displayed when multiple PSU web clients install/uninstall device packages at the same time.

When multiple PSU web clients install/uninstall device packages at the same time, following error message is displayed: Could not connect to JRun Connector Proxy. Please contact the system administrator for this web site.

To work around problem, click on "Click here to view list of all CiscoWorks2000 client sessions" link to send broadcast message which informs all active clients of a server restart. Link is accessible from Confirmation package selection page for installation/uninstallation.

Integration Utility Known Problems

Note Windows NT users with NTFS: The file NMIDBOptions.properties contains CCO passwords, in an encoded form, and is accessible only to root/admin users or any member of the casusers group. Root/Admin Access to the host needs to be restricted if CCO password security is a concern.

Windows NT users with FAT file system: The file NMIDBOptions.properties is not protected from general access. If CCO password security is a concern, users should disable the CCO update option, and manually download the nmidb.*.zip file from the CCO location ftp.CCO in the directory /cisco/netmgmt/ciscoview/5.0/packages.

Table 9 Integration Utility Known Problems

ID

Summary

Explanation

None.

The integration currently done with Network Node Manager (NNM) 6.0 to integrate MIBs, icons, and application registration will not be visible to web clients of NNM, and is not supported in Integration Utility.

If you access NNM through a Web browser, you might not see integrated information.

No workaround is available at this time.

None.

Changing the browser used by one application changes the browser used by all applications registered through the Integration Utility.

In Application Registration screen, change browser used by an application - CiscoView, for example. Now click tab for another application, like Essentials, and you will notice that its browser has also changed.

CSCdm61980

Cannot launch CiscoView by double-clicking device icons in NMS after integration.

Some NMS adapters do not support double-clicking device icons from topology map, even if CiscoView is set as default application (using Change Integration Options).

No workaround is available at this time.

CSCdm91445

If you run the utility to change only application registration information (such as browser, server, and port number), a full integration occurs.

If you change only application registration information, only application integration should occur. Instead, full integration occurs.

No workaround is available at this time.

CSCdp17559

Login screen appears every time CiscoView is started from the Network Management Platform (e.g. HP OpenView) using Internet Explorer.

No workaround is available at this time.

CSCdr38931

Error messages may be displayed when running Change Integration Options on a system with insufficient disk space.

After integration, when you run Change Integration Options, your system extracts NMIDB. If there is not enough disk space to extract NMIDB, extraction fails.

To work around problem, clear up some disk space and relaunch Change Integration Options. For Windows NT, if FAT file system is in place, make sure you have at least 190 MB of free disk space. For other file and operating systems, make sure you have at least 25 MB of free disk space.

CSCdr80401

Uninstallation of CiscoView 4.2 removes all Cisco icons from HP OpenView.

Cisco icons added by CD One 4th Edition installation removed from HP OpenView after following actions:

1. Install HP OpenView 6.0.

2. Install CiscoView 4.2 and integrate with HP OpenView.

3. Install CD One 4th Edition and integrate with HP OpenView.

4. Uninstall CiscoView 4.2.

To work around problem, run nmic and run integration with HP OpenView again.

CSCds19672

Only one subset of Cisco traps is loaded into the NMS by the Integration Utility.

Integration Utility only loads one subset of Cisco traps into NMS using trapd.41x file. File does not include many Cisco traps that can be found in newer Cisco MIBs. HP OpenView and Tivoli NetView integrations are impacted.

To work around problem, manually add/define traps using Event configuration GUI provided by NMSs.

CA-Unicenter Adapter Known Problems

Table 10 CA Unicenter Adapter Known Problems

ID

Summary

Explanation

None.

CA-Unicenter adapter does not integrate icons and MIBs.

CA-Unicenter adapter does not use MIBs or device icons from Cisco NMIDB. Adapter uses its own icons for Cisco devices on TNG maps.

CSCdp17554

Reintegration with CA-Unicenter adapter does not work.

Using Integration utility, integrate with CA-Unicenter adapter. If you try reintegration after changing parameters, adapter warns that applications have previously been registered. Consequently, changes in application parameters are not reflected.

To work around problem, you must unintegrate, then reintegrate:

1. From DOS command line, enter:
C:\program files\cscopx\bin\nmic.exe -u

2. Select Start > Programs > CiscoWorks2000 > Change Integration Options and reenter adapter information.

Note You will receive numerous popup menus. Click OK each time to continue.

CSCdp17571

Numerous popup messages appear during CA-Unicenter adapter execution.

When you integrate with CA-Unicenter adapter in Windows NT 4.0, many popup messages ask for confirmation. Also occurs while running Integration Utility with -u option set. This is expected behavior for TNG adapter and does not affect integration of TNG with CiscoWorks2000. Click OK to continue.

Note Always use the same repository name in the Select Repository dialog box.

ANI Server Known Problems

Table 11 ANI Server Known Problems

ID

Summary

Explanation

CSCdj60832

All configuration changes lost when device accidently shut down, if device running Cisco IOS software image.

Configuration changes are only applied to device's running configuration. Because the changes are not stored in start-up configuration, if device is accidentally shut down all changes are lost.

To avoid problem, open Telnet session to device, and save configuration changes by entering write mem from command line interface.

CSCdm48015

An ATM trunk port is shown as belonging to a VLAN, even if there is no corresponding LANE client associated with that VLAN.

In VLAN-to-port association, all ATM ports on switches (except ATM switches) belonging to VLAN will be displayed.

Ignore ATM ports in VLAN-to-port association.

CSCdm58624

LANE trunks are not considered when determining a VTP disconnected domain discrepancy.

Ignore discrepancy.

Note If VTP domain spans across ATM cloud and default ATM-VLAN is configured to carry VTP advertisements across cloud, domain is still displayed as disconnected domain discrepancy due to lack of support.

CSCdp41757

An empty virtual circuit list is returned by two LS1010 devices, even when a virtual circuit exists between those devices.

Running SNMP query on ciscoAtmSvcAddrTable returns empty table for devices. Problem observed in LS1010 devices running Cisco IOS Release 12.0.

No workaround is available at this time.

CSCdp76410

Campus client cannot connect to server using proxies.

CSCdr84799

Applications not functioning across Network Address Translator (NAT).

No workaround is available at this time.

CSCdt20329

ATM switches, for which Remote Monitoring (RMON) is enabled, not highlighted when Show Enabled Devices selected.

Following actions result in problem:

1. Select Topography Services

2. Highlight an ATM fabric under Managed Domains/ATM Domains

3. Select Display View

4. Select devices, and click Tools->RMON Data Collection->Show Enabled Devices

No workaround is available at this time.

CSCdt56346

Discovery filter does not permit discovery of single device.

Specifying single device for example, in ANI Discovery Filter section does not work. The filter string will be accepted, but ANI will not discover device.

To work around problem, specify a wildcard: To specify a wildcard, replace last part of IP address with the character *. For example, if IP address is 209.165.200.224, wildcard is 209.165.200.*.

Device/Agent Known Problems Impacting ANI Server

Table 12 Device/Agent Known Problems Impacting ANI Server

ID

Summary

Explanation

CSCdm91634

In Campus Manager device report, number of ports in a device's ATM module are incorrectly displayed as zero.

Problem, observed in Catalyst 5000 device running Catalyst operating system version 4.3(1a), is caused by missing ifEntry for device ATM module. ANI Server depends on ifEntry to determine number of ports in a particular module.

No workaround is available at this time.

CSCdp00593

SNMP report displays
wrong HwVersion and HwVersionMinor for LS1010 device.

To avoid problem, enter show hardware in command line interface of LS1010 device.

Browser Known Problems

Table 13 Browser Known Problems

ID

Summary

Explanation

CSCds89236

With "No" selected in Swing-based confirmation dialog boxes, hit Enter key and "Yes" is applied instead.

Problem observed in Solaris clients running CD One 3rd Edition and later in Netscape.

To avoid problem, use mouse or spacebar to activate selection instead of Enter key.

CSCdt05102

Netscape crashes if you resize browser window while applet is loading.

Problem exists within Netscape.

No workaround is available at this time.

CSCdt06518

Unable to launch a second instance of CiscoView in Internet Explorer while the first instance is waiting for user input.

Observed in CD One 3rd Edition and later running in Internet Explorer.

Following actions result in problem:

1. Launch CiscoView.

2. Open a device. CiscoView will prompt for community strings.

3. Without entering community strings, launch a second instance of CiscoView, and it freezes.

To work around problem, enter community strings before launching second instance of CiscoView.

CSCdt11838

When launching application, user not prompted to install Java Plug-in.

If RealJukeBox NS Plug-in is installed before Java Plug-in is installed, users will not be prompted to install Java Plug-in software when attempting to launch application. Blank screen is displayed.

To work around problem, install Java Plug-in manually. For more information regarding the Java Plug-in, see the "Support Information" section.

CSCdt26464

Unable to install Java Plug-in when using Netscape 4.73 on Windows 2000.

When launching CiscoWorks2000 application that requires Java Plug-in, Netscape 4.73 does not redirect to Java Plug-in installation on-line help page.

CiscoWorks2000 does not support Netscape 4.73. For further information on supported browsers, see "New Features" section.

General Known Problems

Table 14 General Known Problems

ID

Summary

Explanation

CSCdr97090

CiscoWorks fails if Oracle, Ingres, or Informix installed on same systems.

When Oracle, Ingres, or Informix are installed on a system with CiscoWorks2000, these tools use resources CiscoWorks2000 expects to have available.

To work around problem, tune kernel according to situation. Consult your operating system vendor for instructions on tuning the kernel.

CSCds71189

Remote Software Image Management (SWIM) upgrade of 2948G router fails when subnet contains 3COM devices.

To work around problem, use Trivial File Transfer Protocol (TFTP) to upgrade 2948G router when subnet contains 3COM devices.

CSCds75572

CiscoWorks2000 database grows too quickly.

CiscoWorks2000 database (cmf.db) grows several Mb per day, reaching above 20Gb within 5 weeks. System becomes slow, with jre.exe eating 90% of CPU.

To work around problem, do not enable Event Logging.If Event Logging already enabled, disable it by performing the following steps:

1. Select Server Configuration > Administration > Event Management > Event Consumer Admin.

2. Set EventLogger to None, and click Apply.

CSCds90118

If two users create private views with same name, error occurs.

No workaround is available at this time.

CSCdt16895

JRunProxyServer crashes when Netconfig invoked.

When opening Netconfig, the following error occurs:
Unable to retrieve message from catalog for message ID 300 Message Catalog is Null

No workaround is available at this time.

CSCdt22462

Delay when downloading Java applets on Win2K.

On some Windows 2000 systems, the initial download of large Java applets (or subsequent downloads of the same applets that are not cached locally) might take longer than expected (up to six minutes in some instances). After the applet has been loaded and cached locally, the problem no longer occurs.

The delay is caused by client side filtering mechanisms such as virus scanning. Some virus scanners are configured to automatically scan content downloaded by browsers. Scanning consumes a lot of memory and results in disk paging on most systems.

Because of this, downloading is significantly slower than expected. (The effect is less on systems with large amounts of RAM and virtual memory.)

To work around this problem, disable the automatic scanning of all downloaded files, and instead enable the scanning of program files only (specified by file extension).

Exact instructions vary depending on the virus scanner installed on your system.

For more information, see the following article:
http://support.microsoft.com/support/kb/articles/q240/3/09.asp.

CSCdt50353

Unable to access help files for user-created management connections after reinstallation/upgrade of CiscoWorks2000.

After reinstallation/upgrade, CiscoWorks2000 fails to launch help files for user-created management connections that existed prior to reinstallation/upgrade.

To work around problem, access help files directly. For example: to access help for a connection with folder name xyz, enter following URL in browser: http://<CiscoWorks2000host:port>/help/extern/xyz.html.

CSCdt59720

Crmtftp fills Windows Event Viewer with messages.

Windows Event Viewer fills with Informational and Error messages sent by crmtftp service. These messages indicate that a file is being transferred or a file was not found.

To work around problem, delete crmtftp events from Windows Event Viewer so they do not fill with messages.

CSCdt73198

CiscoWorks2000 freezes when machine's connection to network is lost.

CiscoWorks2000 is a network intensive application, and as such the recovery period from a network outage is substantial.

There is no need to attempt a workaound. CiscoWorks2000 will come back by itself. When tested, it has come back within half an hour.

CSCdt83908

When using PSU in "Scheduled Download" mode, and using GMT time zone, download happens one hour earlier than scheduled time.

No workaround is available at this time.

Obtaining Documentation

The following sections provide sources for obtaining documentation from Cisco Systems.

World Wide Web

You can access the most current Cisco documentation on the World Wide Web at the following sites:

•http://www.cisco.com

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

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

Documentation CD-ROM

Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM is updated monthly and may be more current than printed documentation. The CD-ROM package is available as a single unit or as an annual subscription.

Ordering Documentation

Cisco documentation is available in the following ways:

•Registered Cisco Direct Customers can order Cisco Product documentation from the Networking Products MarketPlace:

http://www.cisco.com/cgi-bin/order/order_root.pl

•Registered Cisco.com users can order the Documentation CD-ROM through the online Subscription Store:

http://www.cisco.com/go/subscription

•Nonregistered Cisco.com users can order documentation through a local account representative by calling Cisco corporate headquarters
(California, USA) at 408 526-7208 or, in North America, by calling
800 553-NETS(6387).

Documentation Feedback

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

You can e-mail your comments to bug-doc@cisco.com.

To submit your comments by mail, for your convenience many documents contain a response card behind the front cover. Otherwise, you can mail your comments to the following address:

Cisco Systems, Inc.
Document Resource Connection
170 West Tasman Drive
San Jose, CA 95134-9883

We appreciate your comments.

Obtaining Technical Assistance

Cisco provides Cisco.com as a starting point for all technical assistance. Customers and partners can obtain documentation, troubleshooting tips, and sample configurations from online tools. For Cisco.com registered users, additional troubleshooting tools are available from the TAC website.

Cisco.com

Cisco.com is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information and resources at anytime, from anywhere in the world. This highly integrated Internet application is a powerful, easy-to-use tool for doing business with Cisco.

Cisco.com provides a broad range of features and services to help customers and partners streamline business processes and improve productivity. Through Cisco.com, you can find information about Cisco and our networking solutions, services, and programs. In addition, you can resolve technical issues with online technical support, download and test software packages, and order Cisco learning materials and merchandise. Valuable online skill assessment, training, and certification programs are also available.

Customers and partners can self-register on Cisco.com to obtain additional personalized information and services. Registered users can order products, check on the status of an order, access technical support, and view benefits specific to their relationships with Cisco.

To access Cisco.com, go to the following website:

http://www.cisco.com

Technical Assistance Center

The Cisco TAC website is available to all customers who need technical assistance with a Cisco product or technology that is under warranty or covered by a maintenance contract.

Contacting TAC by Using the Cisco TAC Website

If you have a priority level 3 (P3) or priority level 4 (P4) problem, contact TAC by going to the TAC website:

http://www.cisco.com/tac

P3 and P4 level problems are defined as follows:

•P3—Your network performance is degraded. Network functionality is noticeably impaired, but most business operations continue.

•P4—You need information or assistance on Cisco product capabilities, product installation, or basic product configuration.

In each of the above cases, use the Cisco TAC website to quickly find answers to your questions.

To register for Cisco.com, go to the following website:

http://www.cisco.com/register/

If you cannot resolve your technical issue by using the TAC online resources, Cisco.com registered users can open a case online by using the TAC Case Open tool at the following website:

http://www.cisco.com/tac/caseopen

Contacting TAC by Telephone

If you have a priority level 1(P1) or priority level 2 (P2) problem, contact TAC by telephone and immediately open a case. To obtain a directory of toll-free numbers for your country, go to the following website:

http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml

P1 and P2 level problems are defined as follows:

•P1—Your production network is down, causing a critical impact to business operations if service is not restored quickly. No workaround is available.

•P2—Your production network is severely degraded, affecting significant aspects of your business operations. No workaround is available.

AccessPath, AtmDirector, Browse with Me, CCDA, CCDE, CCDP, CCIE, CCNA, CCNP, CCSI, CD-PAC, CiscoLink, the Cisco NetWorks logo, the Cisco Powered Network logo, Cisco Systems Networking Academy, the Cisco Systems Networking Academy logo, Discover All That's Possible, Fast Step, Follow Me Browsing, FormShare, FrameShare, GigaStack, IGX, Internet Quotient, IP/VC, iQ Breakthrough, iQ Expertise, iQ FastTrack, the iQ Logo, iQ Net Readiness Scorecard, MGX, the Networkers logo, Packet, PIX, RateMUX, ScriptBuilder, ScriptShare, SlideCast, SMARTnet, TransPath, Voice LAN, Wavelength Router, WebViewer are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, Empowering the Internet Generation, are service marks of Cisco Systems, Inc.; and Aironet, ASIST, BPX, Catalyst, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, the Cisco IOS logo, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Enterprise/Solver, EtherChannel, EtherSwitch, FastHub, FastSwitch, IOS, IP/TV, LightStream, MICA, Network Registrar, Post-Routing, Pre-Routing, Registrar, StrataView Plus, Stratm, SwitchProbe, TeleRouter, and VCO are registered trademarks of Cisco Systems, Inc. or its affiliates in the U.S. and certain other countries.
All other brands, names, or trademarks mentioned in this document or Web site are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0101R)
Release Notes for CiscoWorks2000 CD One 4th Edition on Windows 2000 and Windows NT
Copyright � 2001, Cisco Systems, Inc.
All rights reserved.

Time Zone Acronym Setting on Device	Definition	Area Covered (Country/City)	Offset from GMT	Time Zone Setting on Server	Output in Report
					GMT	Acronym
ACT	Australia Central Time	Australia/ Darwin	+9:30	Adelaide	GMT +9:30	ACT
AEST	Australia Eastern Standard Time	Australia/ Sydney	+10:00 +11:00 (DST)	Brisbane	GMT +10:00 GMT +11:00 (DST)	AEST
AET	Australia Eastern Time	Australia/ Sydney	+10:00	Brisbane	GMT +10:00 GMT +11:00 (DST)	AET
AHST	Alaska-Hawaii Standard Time	Hawaii/ Honolulu	-10:00	Hawaii	GMT -10:00	HST
ART	Arabic Egypt Standard Time	Africa/Cairo	+2:00 +3:00 (DST)	Cairo	GMT +2:00 GMT +3:00 (DST)	ART
CCT	China Coast Time	Asia/ Shanghai	+8:00	Beijing	GMT +8:00	CST
CDT	Central Daylight Time	United States/ Chicago	-5:00	Central Time	GMT -5:00	CDT (DST) CST
CET	Central European Time	Spain/Madrid	+1:00 +2:00 (DST)	Madrid	GMT +1:00 GMT +2:00 (DST)	CEST
CST	Central Standard Time	United States/ Chicago	-6:00	Central Time	GMT -6:00	CST CDT (DST)
CTT	China Taiwan Time	Asia/ Shanghai	+8:00	Beijing	GMT +8:00	CST
EAST	East Australian Standard Time	Australia/ Queens Island	+10:00	Brisbane	GMT +10:00	EAST
ECT	European Central Time	Europe/Paris	+1:00 +2:00 (DST)	Paris	GMT +1:00 GMT +2:00 (DST)	CEST
EDT	Eastern Daylight Time	United States/ New York	-4:00	Eastern Time	GMT -4:00	EST EDT (DST)
EST	Eastern Standard Time	United States/ New York	-5:00	Eastern Time	GMT -5:00	EST EDT (DST)
FWT	French Winter Time	France/Paris	+1:00 +2:00 (DST)	Paris	GMT +1:00 GMT +2:00 (DST)	CEST
GMT	GMT Standard Time	Africa/ Casablanca	None	Greenwich Mean Time	GMT +0	GMT
HST	Hawaiian Standard Time	Pacific/ Honolulu	-10:00	Hawaii	GMT -10:00	HST
JST	Japan Standard Time	Asia/Tokyo	+9:00	Tokyo	GMT +9:00	JST
MDT	Mountain Daylight Time	United States/ Denver	-6:00	Mountain Time	GMT -6:00	MDT (DST) MST
MET	Middle European Time	Spain/Madrid	+1:00 +2:00 (DST)	Madrid	GMT +1:00 GMT +2:00 (DST)	CEST
MEWT	Middle European Winter Time	Spain/Madrid	+1:00	Madrid	GMT +1:00 GMT +2:00 (DST)	CEST
MST	Mountain Standard Time	United States/ Denver	-7:00	Mountain Time	GMT -7:00	MST MDT (DST)
PDT	Pacific Daylight Time	United States/ Los Angeles	-7:00	Pacific Time	GMT -7:00	PDT (DST) PST
PST	Pacific Standard Time	United States/ Los Angeles	-8:00	Pacific Time	GMT -8:00	PST PDT (DST)
UCT	GMT Standard Time	Great Britain/ London	None	Greenwich Mean Time	GMT +0	GMT
ZP4	Zone 3	Russia/ Moscow	+4:00	Not Supported	GMT +4:00	ZP4

ID	Summary	Explanation
None.	Installing CD One returns an error message stating that there is not enough space on the C: drive to complete the process.	Installation requires 20 MB of space in Windows temporary directory: C:\Temp on most systems. If destination path is other than default and drive where \Temp directory resides does not have required space, error occurs.
CSCds07866	Unable to access ODBC Database.	If ODBC Driver Manager installed on machine is an earlier version than 3.51, ODBC database access will fail. Problem caused by version mismatch of Sybase ODBC driver and ODBC Driver Manager. Sybase v6 requires ODBC Driver Manager 3.51 or later. To correct problem, download MDAC 2.5 Service pack or later, which includes proper ODBC Driver Manager, from http://www.microsoft.com/data/, and install it as instructed.
CSCds33712	Re-installation of CD One fails when IPM installed on same machine.	If IPM is installed on machine that has RWAN bundle, re-installation of CD One may fail due to a shared library being locked. Problem also occurs when CiscoWorks2000 and IPM installations exist on same machine and you install or upgrade other CiscoWorks2000 components. To work around problem: 1. Run ipm stop 2. Run ipm cw2ksetup uninstall 3. Re-install CD one 4. Run ipm cw2ksetup install 5. Run ipm start The first two steps remove IPM's dependency on the shared library and the last two steps integrate IPM with CiscoWorks2000.
CSCds90562	Daemon manager fails to run if CiscoWorks2000 home directory is encrypted.	CiscoWorks2000 does not support encrypted directories.
CSCdt21743	Configuration files in Trivial File Transfer Protocol (TFTP) boot directory not secure.	The configuration files, stored in the TFTP boot directory during the TFTP operation, have permission for everyone, though files are owned by the user casuser. Situation only exists for a short time while download in progress. No workaround is available at this time.
CSCdt31121	Cisco Voice Manager processes need to be stopped before upgrading to CD One, 4th Edition.	To stop Cisco Voice Manager processes: (Windows NT/2000 clients) At command line prompt, enter: net stop "CVM Server and Poller Service" (Solaris clients) At command line prompt, enter: /etc/init.d/cvm stop
CSCdt32795	CiscoWorks2000 malfunctions if operating system upgraded after installation.	For further information, including how to work around problem, see the "Operating System Upgrade" section.
CSCdt63101	When installing CiscoWorks2000 as non-root user, improper message occurs.	When installing CiscoWorks2000 under a non administrator account on Windows 2000, the following message occurs: `Setup Initialization Error Setup has detected that unInstallshield is in use. Please close unInstallshield and restart setup. Error432.` When the OK button is clicked, installation is terminated. To work around problem, run installation from an administrator's account.

ID	Summary	Explanation
CSCdr33955	Multiport monitor graphs for device running CiscoView display incorrect values.	To avoid problem, generate monitor graphs for individual ports.
CSCdr67552	Chassis window does not repaint properly after being resized.	Problem observed in HP-UX clients running CD One 3rd Edition and later. To work around problem, close and relaunch CiscoView.
CSCdr88151	Chassis view cannot be printed from HP-UX clients running CiscoView 5.3.	With chassis view open, click Print icon and blank pages are printed. To work around problem, print screen captures of chassis view.
CSCds41560	Printing chassis view from CiscoView running in Internet Explorer 5.x returns error.	Observed on NT client running CiscoView in Internet Explorer 5.x. Following actions result in problem: 1. Open a device and bring up chassis view. 2. Select File > Print to print chassis view and error message is returned. To avoid problem, click Print icon to print chassis view.
CSCds73008	Bean Control window is sometimes displayed after selecting "Import Device List" from CiscoWorks2000 desktop.	Problem observed in CD One 3rd Edition and later running in Internet Explorer. To work around problem, close and relaunch CiscoWorks2000.
CSCdt04355	CiscoView console buttons cannot be selected with Enter key.	Problem observed in CD One 3rd Edition and later. To work around problem, use mouse or spacebar to activate selection instead of Enter key.
CSCdt11838	When launching application, user not prompted to install Java Plug-in.	For further information, refer to CSCdt11838 in the "CD One Installation Known Problems" section.
CSCdt22462	Delay when downloading Java applets on Win2K.	For a detailed explanation of this problem, refer to CSCdt22462 in the "General Known Problems" section.
CSCdt43794	Configure window displayed behind main chassis window in CiscoView 5.x, Japanese Edition.	Problem observed in CiscoView 5.x, Japanese Edition, running in Navigator 4.75 on Windows 2000 Professional client. Select Configure from context (right-click) menu and Configure window is displayed behind main CiscoView chassis window. To avoid problem, open configuration dialog by double-clicking component. Configure window will launch automatically and be properly displayed.
CSCds53413	Shortcuts in the My Shortcuts folder cannot be deleted.	No workaround is available at this time.
CSCdt79469	Button labels not completely displayed in CiscoView running in Navigator on HP-UX client.	With CiscoView running in Navigator on HP-UX client, button labels in main window and other dialog boxes are truncated and displayed with ellipsis. To work around problem: •Change display resolution on your monitor to a higher value; or •Select a different category and click OK to apply any changes made in previous category.

ID	Summary	Explanation
CSCdr34879	All ports on WS-X6608-T1 are shown as green on a Catalyst 6000 device running CiscoView.	Only ports that are configured and connected should be shown as green. Problem caused by lack of mapping between MIB elements in agent and colors of ports on the board. No workaround is available at this time.
CSCds72290	Running CiscoView 5.x on device with Cisco IOS 12.1(2)E installed returns error.	Problem observed on Catalyst 2612 and Catalyst 6509 devices with Cisco IOS 12.1(2)E installed running CiscoView 5.x. Following error is displayed: Failed to refresh chassis. Refer to error log for details. No workaround is available at this time.
CSCds78228	Contents of Catalyst 5000 device package readme file is different from what is listed in Package Details window.	Select Device Manager > View Installed Packages from CiscoWorks2000 desktop, then click Details icon for Catalyst 5000 device package to bring up Package Details window. Although text in readme file link states "Readme file for Cat5000 (1.2)," click link and "Catalyst 5000 (1.3) Installation" instructions are displayed instead.

ID	Summary	Explanation
CSCdr39315	2524 device running Cisco IOS 12.05T and CiscoView 5.x does not display SM25-T1 card. A blank slot is shown instead.	No workaround is available at this time.
CSCds55193	Incorrect formula used to calculate interface error percentage is listed in CiscoView online help.	CiscoView online help lists following as formula used to calculate interface error percentage: [ifInErrors /(ifInUcastPkts + IfInNUcastPkts)] 100. Correct formula is: [ifInError /(ifInUcastPkts + IfInNUcastPkts + ifInError+ifInUnknownProtos)] 100.
CSCds86109	CiscoView 5.x, running on Cisco 1600 and 4000 series devices, displays a high number of collisions.	No workaround is available at this time.
CSCdt02050	Flash (PCMCIA) card is not displayed on Cisco 7000 series device running CiscoView.	No workaround is available at this time.
CSCdt07445	Unable to configure ports on Cisco7000 series device with Cisco 7200 device package installed.	Following actions result in problem: 1. Launch CiscoView and open device. 2. With a port selected, open Configure dialog box. 3. Make changes to port settings and `internal error` is displayed. No workaround is available at this time.
CSCdt26857	Cannot retrieve ATM statistics for ATM ports on devices with Cisco 7000 device package installed.	At present, only Interface statistics and several categories of SONET statistics can be retrieved. No workaround is available at this time.

ID	Summary	Explanation
CSCdr94291	In CiscoView, NEMI configuration dialog box for Metro 1500 device displays N/A as Subnet mask value.	NEMI configuration dialog box should display 255.255.255.0 as Subnet mask value. No workaround is available at this time.
CSCdr96333	HP OpenView topology map displays generic icon for Metro 1500 device.	Following actions result in problem: 1. Install HP OpenView and then CiscoView 5.1. 2. Run NMIM integration. 3. Using Device Support Utility, install Metro 1500 device package version 1.2. 4. Launch HP OpenView. 5. Select Edit > Add Object > Cisco FastHub > Metro 1500. 6. Click on Metro 1500 icon and drag it into topology map. No workaround is available at this time.

ID	Summary	Explanation
CSCdt04070	No error message is displayed when network connection is lost during the download of device packages from CCO.	No workaround is available at this time.
CSCdt24701	No error message is displayed after an unsuccessful attempt to uninstall nmidb packages.	After unsuccessful attempt to uninstall nmidb packages, no error message is displayed stating that process failed. Also, in View History window, completed successfully is displayed under status tab when failed should be displayed instead. No workaround is available at this time.
CSCdt35177	PSU is displayed without a banner and left frame in browser.	To avoid problem, make sure your browser's caching policy is not set to "Never". Set caching policy to "Every visit to the page" in Internet Explorer browsers and "Every time" in Netscape browsers.
CSCdt36869	Installing same device package from CCO using multiple PSU sessions results in errors.	Errors are returned when device packages are downloaded and installed from CCO using PSU web interface and standalone PSU (psu, xpsu) at the same time. To avoid problem, do not use PSU web interface and standalone PSU simultaneously to download device packages from CCO.
CSCdt73771	Error message displayed when multiple PSU web clients install/uninstall device packages at the same time.	When multiple PSU web clients install/uninstall device packages at the same time, following error message is displayed: Could not connect to JRun Connector Proxy. Please contact the system administrator for this web site. To work around problem, click on "Click here to view list of all CiscoWorks2000 client sessions" link to send broadcast message which informs all active clients of a server restart. Link is accessible from Confirmation package selection page for installation/uninstallation.

ID	Summary	Explanation
None.	The integration currently done with Network Node Manager (NNM) 6.0 to integrate MIBs, icons, and application registration will not be visible to web clients of NNM, and is not supported in Integration Utility.	If you access NNM through a Web browser, you might not see integrated information. No workaround is available at this time.
None.	Changing the browser used by one application changes the browser used by all applications registered through the Integration Utility.	In Application Registration screen, change browser used by an application - CiscoView, for example. Now click tab for another application, like Essentials, and you will notice that its browser has also changed.
CSCdm61980	Cannot launch CiscoView by double-clicking device icons in NMS after integration.	Some NMS adapters do not support double-clicking device icons from topology map, even if CiscoView is set as default application (using Change Integration Options). No workaround is available at this time.
CSCdm91445	If you run the utility to change only application registration information (such as browser, server, and port number), a full integration occurs.	If you change only application registration information, only application integration should occur. Instead, full integration occurs. No workaround is available at this time.
CSCdp17559	Login screen appears every time CiscoView is started from the Network Management Platform (e.g. HP OpenView) using Internet Explorer.	No workaround is available at this time.
CSCdr38931	Error messages may be displayed when running Change Integration Options on a system with insufficient disk space.	After integration, when you run Change Integration Options, your system extracts NMIDB. If there is not enough disk space to extract NMIDB, extraction fails. To work around problem, clear up some disk space and relaunch Change Integration Options. For Windows NT, if FAT file system is in place, make sure you have at least 190 MB of free disk space. For other file and operating systems, make sure you have at least 25 MB of free disk space.
CSCdr80401	Uninstallation of CiscoView 4.2 removes all Cisco icons from HP OpenView.	Cisco icons added by CD One 4th Edition installation removed from HP OpenView after following actions: 1. Install HP OpenView 6.0. 2. Install CiscoView 4.2 and integrate with HP OpenView. 3. Install CD One 4th Edition and integrate with HP OpenView. 4. Uninstall CiscoView 4.2. To work around problem, run nmic and run integration with HP OpenView again.
CSCds19672	Only one subset of Cisco traps is loaded into the NMS by the Integration Utility.	Integration Utility only loads one subset of Cisco traps into NMS using trapd.41x file. File does not include many Cisco traps that can be found in newer Cisco MIBs. HP OpenView and Tivoli NetView integrations are impacted. To work around problem, manually add/define traps using Event configuration GUI provided by NMSs.

ID	Summary	Explanation
None.	CA-Unicenter adapter does not integrate icons and MIBs.	CA-Unicenter adapter does not use MIBs or device icons from Cisco NMIDB. Adapter uses its own icons for Cisco devices on TNG maps.
CSCdp17554	Reintegration with CA-Unicenter adapter does not work.	Using Integration utility, integrate with CA-Unicenter adapter. If you try reintegration after changing parameters, adapter warns that applications have previously been registered. Consequently, changes in application parameters are not reflected. To work around problem, you must unintegrate, then reintegrate: 1. From DOS command line, enter: C:\program files\cscopx\bin\nmic.exe -u 2. Select Start > Programs > CiscoWorks2000 > Change Integration Options and reenter adapter information. Note You will receive numerous popup menus. Click OK each time to continue.
CSCdp17571	Numerous popup messages appear during CA-Unicenter adapter execution.	When you integrate with CA-Unicenter adapter in Windows NT 4.0, many popup messages ask for confirmation. Also occurs while running Integration Utility with -u option set. This is expected behavior for TNG adapter and does not affect integration of TNG with CiscoWorks2000. Click OK to continue. Note Always use the same repository name in the Select Repository dialog box.

ID	Summary	Explanation
CSCdj60832	All configuration changes lost when device accidently shut down, if device running Cisco IOS software image.	Configuration changes are only applied to device's running configuration. Because the changes are not stored in start-up configuration, if device is accidentally shut down all changes are lost. To avoid problem, open Telnet session to device, and save configuration changes by entering write mem from command line interface.
CSCdm48015	An ATM trunk port is shown as belonging to a VLAN, even if there is no corresponding LANE client associated with that VLAN.	In VLAN-to-port association, all ATM ports on switches (except ATM switches) belonging to VLAN will be displayed. Ignore ATM ports in VLAN-to-port association.
CSCdm58624	LANE trunks are not considered when determining a VTP disconnected domain discrepancy.	Ignore discrepancy. Note If VTP domain spans across ATM cloud and default ATM-VLAN is configured to carry VTP advertisements across cloud, domain is still displayed as disconnected domain discrepancy due to lack of support.
CSCdp41757	An empty virtual circuit list is returned by two LS1010 devices, even when a virtual circuit exists between those devices.	Running SNMP query on ciscoAtmSvcAddrTable returns empty table for devices. Problem observed in LS1010 devices running Cisco IOS Release 12.0. No workaround is available at this time.
CSCdp76410	Campus client cannot connect to server using proxies.
CSCdr84799	Applications not functioning across Network Address Translator (NAT).	No workaround is available at this time.
CSCdt20329	ATM switches, for which Remote Monitoring (RMON) is enabled, not highlighted when Show Enabled Devices selected.	Following actions result in problem: 1. Select Topography Services 2. Highlight an ATM fabric under Managed Domains/ATM Domains 3. Select Display View 4. Select devices, and click Tools->RMON Data Collection->Show Enabled Devices No workaround is available at this time.
CSCdt56346	Discovery filter does not permit discovery of single device.	Specifying single device for example, in ANI Discovery Filter section does not work. The filter string will be accepted, but ANI will not discover device. To work around problem, specify a wildcard: To specify a wildcard, replace last part of IP address with the character . For example, if IP address is 209.165.200.224, wildcard is 209.165.200..

ID	Summary	Explanation
CSCdm91634	In Campus Manager device report, number of ports in a device's ATM module are incorrectly displayed as zero.	Problem, observed in Catalyst 5000 device running Catalyst operating system version 4.3(1a), is caused by missing ifEntry for device ATM module. ANI Server depends on ifEntry to determine number of ports in a particular module. No workaround is available at this time.
CSCdp00593	SNMP report displays wrong HwVersion and HwVersionMinor for LS1010 device.	To avoid problem, enter show hardware in command line interface of LS1010 device.

ID	Summary	Explanation
CSCds89236	With "No" selected in Swing-based confirmation dialog boxes, hit Enter key and "Yes" is applied instead.	Problem observed in Solaris clients running CD One 3rd Edition and later in Netscape. To avoid problem, use mouse or spacebar to activate selection instead of Enter key.
CSCdt05102	Netscape crashes if you resize browser window while applet is loading.	Problem exists within Netscape. No workaround is available at this time.
CSCdt06518	Unable to launch a second instance of CiscoView in Internet Explorer while the first instance is waiting for user input.	Observed in CD One 3rd Edition and later running in Internet Explorer. Following actions result in problem: 1. Launch CiscoView. 2. Open a device. CiscoView will prompt for community strings. 3. Without entering community strings, launch a second instance of CiscoView, and it freezes. To work around problem, enter community strings before launching second instance of CiscoView.
CSCdt11838	When launching application, user not prompted to install Java Plug-in.	If RealJukeBox NS Plug-in is installed before Java Plug-in is installed, users will not be prompted to install Java Plug-in software when attempting to launch application. Blank screen is displayed. To work around problem, install Java Plug-in manually. For more information regarding the Java Plug-in, see the "Support Information" section.
CSCdt26464	Unable to install Java Plug-in when using Netscape 4.73 on Windows 2000.	When launching CiscoWorks2000 application that requires Java Plug-in, Netscape 4.73 does not redirect to Java Plug-in installation on-line help page. CiscoWorks2000 does not support Netscape 4.73. For further information on supported browsers, see "New Features" section.

ID	Summary	Explanation
CSCdr97090	CiscoWorks fails if Oracle, Ingres, or Informix installed on same systems.	When Oracle, Ingres, or Informix are installed on a system with CiscoWorks2000, these tools use resources CiscoWorks2000 expects to have available. To work around problem, tune kernel according to situation. Consult your operating system vendor for instructions on tuning the kernel.
CSCds71189	Remote Software Image Management (SWIM) upgrade of 2948G router fails when subnet contains 3COM devices.	To work around problem, use Trivial File Transfer Protocol (TFTP) to upgrade 2948G router when subnet contains 3COM devices.
CSCds75572	CiscoWorks2000 database grows too quickly.	CiscoWorks2000 database (cmf.db) grows several Mb per day, reaching above 20Gb within 5 weeks. System becomes slow, with jre.exe eating 90% of CPU. To work around problem, do not enable Event Logging.If Event Logging already enabled, disable it by performing the following steps: 1. Select Server Configuration > Administration > Event Management > Event Consumer Admin. 2. Set EventLogger to None, and click Apply.
CSCds90118	If two users create private views with same name, error occurs.	No workaround is available at this time.
CSCdt16895	JRunProxyServer crashes when Netconfig invoked.	When opening Netconfig, the following error occurs: `Unable to retrieve message from catalog for message ID 300 Message Catalog is Null` No workaround is available at this time.
CSCdt22462	Delay when downloading Java applets on Win2K.	On some Windows 2000 systems, the initial download of large Java applets (or subsequent downloads of the same applets that are not cached locally) might take longer than expected (up to six minutes in some instances). After the applet has been loaded and cached locally, the problem no longer occurs. The delay is caused by client side filtering mechanisms such as virus scanning. Some virus scanners are configured to automatically scan content downloaded by browsers. Scanning consumes a lot of memory and results in disk paging on most systems. Because of this, downloading is significantly slower than expected. (The effect is less on systems with large amounts of RAM and virtual memory.) To work around this problem, disable the automatic scanning of all downloaded files, and instead enable the scanning of program files only (specified by file extension). Exact instructions vary depending on the virus scanner installed on your system. For more information, see the following article: http://support.microsoft.com/support/kb/articles/q240/3/09.asp.
CSCdt50353	Unable to access help files for user-created management connections after reinstallation/upgrade of CiscoWorks2000.	After reinstallation/upgrade, CiscoWorks2000 fails to launch help files for user-created management connections that existed prior to reinstallation/upgrade. To work around problem, access help files directly. For example: to access help for a connection with folder name xyz, enter following URL in browser: http://<CiscoWorks2000host:port>/help/extern/xyz.html.
CSCdt59720	Crmtftp fills Windows Event Viewer with messages.	Windows Event Viewer fills with Informational and Error messages sent by crmtftp service. These messages indicate that a file is being transferred or a file was not found. To work around problem, delete crmtftp events from Windows Event Viewer so they do not fill with messages.
CSCdt73198	CiscoWorks2000 freezes when machine's connection to network is lost.	CiscoWorks2000 is a network intensive application, and as such the recovery period from a network outage is substantial. There is no need to attempt a workaound. CiscoWorks2000 will come back by itself. When tested, it has come back within half an hour.
CSCdt83908	When using PSU in "Scheduled Download" mode, and using GMT time zone, download happens one hour earlier than scheduled time.	No workaround is available at this time.

Table Of Contents

Release Notes for CiscoWorks2000CD One 4th Edition on Windows 2000 and Windows NT

New Features

Documentation Roadmap

Additional Release-Specific Information Online

Time Zone Acronyms and Offset Settings

Multi-Homed Machines

Security Enhancement

Operating System Upgrade

Support Information

Documentation Errata

CD One 4th Edition Known Problems

CD One Installation Known Problems

CiscoView Known Problems

Desktop Known Problems

Catalyst Devices Known Problems

Router and Hub Known Problems

General Device Package Known Problems

Package Support Updater (PSU) Known Problems

Integration Utility Known Problems

CA-Unicenter Adapter Known Problems

ANI Server Known Problems

Device/Agent Known Problems Impacting ANI Server

Browser Known Problems

General Known Problems

Obtaining Documentation

World Wide Web

Documentation CD-ROM

Ordering Documentation

Documentation Feedback

Obtaining Technical Assistance

Cisco.com

Technical Assistance Center

Contacting TAC by Using the Cisco TAC Website

Contacting TAC by Telephone

All other brands, names, or trademarks mentioned in this document or Web site are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0101R)

Release Notes for CiscoWorks2000 CD One 4th Edition on Windows 2000 and Windows NTCopyright � 2001, Cisco Systems, Inc.All rights reserved.

Release Notes for CiscoWorks2000
CD One 4th Edition on Windows 2000 and Windows NT

Release Notes for CiscoWorks2000 CD One 4th Edition on Windows 2000 and Windows NT
Copyright � 2001, Cisco Systems, Inc.
All rights reserved.