Guest

CiscoWorks CD One

Release Notes for CD One, 5th Edition on Windows 2000

  • Viewing Options

  • PDF (524.3 KB)
  • Feedback
Release Notes for CD One, 5th Edition on Windows 2000

Table Of Contents

Release Notes for CD One, 5th Edition on Windows 2000

New Features

Documentation Roadmap

Additional Information Online

Time Zone Acronyms and Offset Settings

Multi-Homed Machines

Security Enhancement

Operating System Upgrade

Support Information

Known and Resolved 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

Internally-Found Resolved Problems

Customer-Found Resolved Problems

Obtaining Documentation

World Wide Web

Ordering Documentation

Documentation Feedback

Obtaining Technical Assistance

Cisco.com

Technical Assistance Center

Cisco TAC Web Site

Cisco TAC Escalation Center


Release Notes for CD One, 5th Edition on Windows 2000


These release notes are for use with the CD One, 5th edition on a Windows platform.

These release notes provide:

New Features

Documentation Roadmap

Additional Information Online

Time Zone Acronyms and Offset Settings

Multi-Homed Machines

Security Enhancement

Operating System Upgrade

Support Information

Known and Resolved Problems

Obtaining Documentation

Obtaining Technical Assistance

New Features

CD One, 5th edition supports the following new features:

SSH—Secure Shell (SSH) provides secure access between the management server and devices

SSL—Secure Socket Layer encryption provides secure access between the client browser and management server

Apache (1.3.24) with open SSL (0.9.6c) and mod_ssl(2.8.8)

Enhanced installation and runtime system security—To improve the security of the product, you can change your login (Admin or Guest user) and database passwords during install. You can provide your own casuser password to support Windows 2000 enhanced password

Provides link to Cisco Feature Navigator (CFN)— a tool available on http://www.cisco.com/go/fn. It enables you to choose the device images based on the features you would like to run on your networks

Export/Import user information—you can export or import user information from one CD One server to another server. You can create users in one server and import them to all the other servers.

New five-year certificate used to sign JAR files.

New OS support—Solaris 2.8 and Windows2000 with Service Pack 2

Java plug-in 1.3.1

New database—Sybase version is upgraded to ASA 7.0.3 from ASA 6.0.3.

New device support—Support for several new Cisco devices, Cisco IOS extended features, and selected Cisco voice applications. Supports several Cisco products, including: AP340, AP350, AS5350, AS5400, Router 12000 Series, IAD2400, Metro 1500, and URM (1.0), Polycom 7935, Catalyst 2950, Catalyst 3550, Catalyst 4224, VG 248, 6513 (IOS and Cat IOS), DPA 7630, and DPA 7610

CiscoView 5.4—CiscoView 5.4 supports imported device list auditing. After importing the credentials (IP address and SNMP read/write community strings) for a group of devices, the devices are added to the cv.log file.

Documentation Roadmap

This section provides the documentation roadmap for CD One, 5th edition.


Note Although every effort has been made to validate the accuracy of the information in the printed and electronic documentation, you should also review the CD One, 5th edition documentation on Cisco.com for any updates.


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

Installation and Setup Guide for CD One on Windows 2000—This document provides installation instructions, including both server and client side system requirements, steps for installing and uninstalling, and installation troubleshooting information.

User Guide for CiscoWorks2000 Server—This document provides information about setting up, administering, and accessing the CiscoWorks2000 Server, used by all CiscoWorks2000 applications.

Using CiscoView 5.4—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 or later is required.


Use these publications to learn how to install and use CD One, 5th edition:

Installation and Setup Guide for CD One on Windows 2000 (DOC-7814068=)—Installation and Setup Guide for CD One on Windows 2000—This document provides installation instructions, including both server and client side system requirements, steps for installing and uninstalling, and installation troubleshooting information

User Guide for CiscoWorks2000 Server (DOC-7814072=)—Provides information about setting up, administering, and accessing the CiscoWorks2000 Server, used by all CiscoWorks2000 applications

Using CiscoView 5.4 (DOC-78nnnnn=)—Provides information about setting up, administering, and accessing the CiscoWorks2000 Server, used by all CiscoWorks2000 applications

CD One online help—Provides task-oriented and context-sensitive help from every window that contains a Help button. Also contains all of the information available in User Guide for CiscoWorks2000 Server and Using CiscoView 5.4. This ensures you have complete information even if you do not have the manual readily available while using CD One.

Additional Information Online

For information about CD One supported devices, refer to the following URLs, or check the documentation on Cisco.com for the correct location.

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 %NMSROOT%/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

net start crmdmgtd.


Note To look up this topic on Bug Navigator II, use bug ID CSCds84075. For more information on using Bug Navigator II, see the "Known and Resolved Problems" section.


Security Enhancement

CD One, 5th edition supports:

Secure Socket Layer (SSL) and Secure Shell (SSH)

Allows you to change the passwords of casuser, admin and guest users during installation

Allows you to change the database passwords (CMF and ANI) during installation.

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, the casuser account has the following attributes:

Randomized password or a user-specified password

No Windows administrative privileges

During an upgrade to CD One 5th Edition, all currently installed CiscoWorks2000 applications, except CD One, are disabled. Key data from these applications, such as community strings and user and host information, are archived. When the latest versions of the applications are installed, they are re-enabled and the necessary archived data is imported.

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 Installion and Setup Guide for CD One on Windows 2000.

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 "Known and Resolved Problems" section.


Support Information

CiscoWorks2000 supports the following:

Operating System—CiscoWorks2000 supports both the English and Japanese versions of Windows 2000, Professional and Server, with Service Pack 2.


Note CD One supports only US-English and Japanese versions of Windows OS. Set the default locale to US-English for US-English version and Japanese for Japanese version.


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

Netscape Navigator 4.76 for Solaris 2.6, 2.7, and 2.8 clients

Netscape Navigator 4.77, 4.78, 4.79 for Windows98, Windows 2000 with Service Pack 2, Windows NT, HP-UX 11.0, AIX 4.3.3, and Windows XP.

Internet Explorer 5.5 with Service Pack 2.

Internet Explorer 6.0

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

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 use the correct version of Java.

The supported native JVM versions are as follows:

Microsoft Internet Explorer 5.5—JVM 5.0.0.3802

Microsoft Internet Explorer 6.0—JVM 5.0.0.3805

The supported Java Plug-in version is 1.3.1 for all operating systems.


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


To install the Java Plug-in,

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:


Step 1 Select Tools > Internet Options > Advanced.

Step 2 Click Java Console.

Step 3 To open the console select View > Java Console.

To enable the native JVM console when using Netscape, Select
Preferences > Advanced > Enable Java.

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

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


Step 1 Select Start > Settings > Control Panel.

Step 2 Double-click Java Plug-in.

Step 3 Select Enable Java Console.


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


JSSE is used along with Java Plugin 1.3.1 for SSL support on the clients. When you invoke CiscoWorks2000 for the first time, in SSL mode from the browser:

JSSE jars will be downloaded from the server and will be installed in the plugin installation directory on the client as an add-on.

For the first time, java.policy file will be updated

You will be asked to restart the browser after this.

Known and Resolved Problems

Known problems (bugs) in CD One, 5th edition are graded according to severity level. These release notes contain descriptions of:

All severity level 1 or 2 bugs.

Significant severity level 3 bugs.

All customer-found bugs (regardless of severity level).

You can search for problems using the Cisco Software Bug Toolkit. To access the Software Bug Toolkit:


Step 1 Log into Cisco.com.

Step 2 Select Service & Support > Technical Support Help—Cisco TAC > Tool Index.

Step 3 In the Jump to: links at the top of the page, click the letter S, then select Software Bug Toolkit.


You can also access the Software Bug Toolkit by entering the following URL in your web browser:

http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl.

Tables 1 to 14 describes the problems known to exist in this release; Tables 14 and 15 describes the problems resolved since the last release of CD One.

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

CD One Installation 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

Internally-Found Resolved Problems

Customer-Found Resolved Problems

CD One Installation Known Problems

Table 2 CD One Installation Known Problems 

Bug ID
(Severity)
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.

Workaround:

None

CSCdw18205 (1)

CMF2.1 and URT3.0 cannot coexist

Displays an error during installation:

An error occured during the move data:-115
Component : ess
FIle Group:ess
File:D:\......\tibrv.dll

Also displays the error:

unable to stop RV processes during reinstall and uninstall

Workaround:

CMF 2.1 and URT 3.0 cannot coexist. Please uninstall URT for proper functioning of CMF 2.1

CSCdw93703 (3)

CW2000 LMS/RWAN 2.0 memory and Dr Watson errors on Compaq Servers

Dr Watson error pops up on Compaq servers if Compaq Insight Manager is running on Compaq servers where CW2000 is running.

Workaround:

Restart the daemons. (or)
Shut down Compaq Insight Manager

CSCin05220 (2)

Not able to invoke CW2000 from the browser

When KFTP login module is selected in CMF2.0 and upgraded to CMF 2.1, Login Prompt will not appear in the browser. The following exception will be thrown in java console:

java.lang.Error: miscalculated data length! 
at java.lang.Throwable.<init>(Compiled Code) 
at java.lang.Error.<init>(Compiled Code) 
at com.cisco.nm.cmf.security.jaas.Base64.decode 
(Compiled Code) 
at 
com.cisco.nm.cmf.security.jaas.JaasThreadData.str
ingToObject (Compiled Code) 
at 
com.cisco.nm.cmf.security.jaas.JaasAppletEngine.i
nit(Compiled Code) 
at com.cisco.nm.cmf.security.csLoginPanel.init 
(Compiled Code) 
atcom.cisco.nm.cmf.desktop.csNavigator.showLoginP
anel (Compiled Code) 
at com.cisco.nm.cmf.desktop.csNavigator.start 
(Compiled Code) 
* at 
netscape.applet.DerivedAppletFrame$StartAppletEve
nt.dispatch (Compiled Code) 
at 
java.awt.EventDispatchThread$EventPump.dispatchEv
ents (Compiled Code) 
at java.awt.EventDispatchThread.run (Compiled 
Code) 
at 
netscape.applet.DerivedAppletFrame$AppletEventDis
patchThread.run(Compiled Code)

Workaround:

Remove $NMSROOT/www/classpath/com/cisco/nm/cmf/
security/jaas/JaasConfigModule file and restart the daemon manager.

CSCdx01388 (2)

dmgtd process fails to start during coexistence testing

When CW2000 and CTM are installed on the same machine, Cisco Works daemons does not come up and displays an error:

Error EDSMG0001: Process Manager Control is 
already running

Workaround:

Do not install CTM on the server in which CW2000 is installed as CTM and CW2000 can not coexist.

CSCdw75528 (2)

Install Fails if there is a program file

If there is a blank file with the name of program in the root directory of the installation drive (e.g C or D) and you are installing to the default location, install may fail.

Similar problem may be encountered, if there is a file named 'CiscoS' in the installation drive (e.g C or D) and you are installing in a custom path drive:\Cisco Systems.

Workaround:

The file which is causing the problem (e.g 'program' in condition-1 or 'CiscoS' in condition-2), needs to be removed. After removing this, restart install.

CSCdx18854 (4)

Errors in daemons.log after stopping the ESS process

Errors in daemons.log after stopping the ESS process

Workaround:

Before stopping ESS, run pdterm JRunProxyServer and then pdterm ESS
To re-start, first run pdexec ESS and then pdexec JRunProxyServer.

CSCin03525 (4)

Uninstallation of cmf2.1 includes IPM2.4 as one of the component

At the time of uninstallation of CiscoWorks2000, disregard the message that indicates Internetwork Performance Monitor 2.4 will be uninstalled with the other CiscoWorks2000 application. IPM will not be uninstalled as part of CiscoWorks2000 uninstallation

Workaround:

None.

CSCdt73198 (2)

CiscoWorks freezes when machines network connection is removed

CiscoWorks2000 freezes when machine's connection to network is lost either by

Plugging out the ethernet network cable.

Powering down the switch.

Workaround:

Reboot the machine.

CSCin07903(3)

Password change for CMF database may not happen during local upgrade

When you are performing a local upgrade to CD One, 5th edition from CD One, 4th edition, occasionally the password change may not happen for CMF database and may get the message in the install log:

...CMF Password configuration. DSN cmf is 
registered. Calling dbpasswd.pl Unable to Change 
password for DSN cmf 
---end of CMF Password configuration 
----- CMF Password configuration 
The dsn 'cmf' is invalid 
----- end of  CMF Password configuration

Workaround:

After the installation is over, perform the following tasks to change the CMF database password.

1. Stop the daemon manager (net stop crmdmgtd)

2. Go to the <Install Dir>/bin directory

3. Run "perl dbpasswd.pl dsn=cmf"

4. Start the daemon manager (net start crmdmgtd)

CSCin07838 (3)

Not able to invoke CW2000 if you start daemon immediately

Unable to invoke CW2000 after daemon manager restart. This can happen if you stop the daemon manager and retart it immediately.

Workaround:

Do not restart the daemon manager immediately after stopping it. Wait for some time for the ports to be released.
For the list of ports used by CW2000, refer to the "TCP & UDP ports used" section, in Installation and Setup Guide for CD One on Solaris.

CSCds33719 (3)

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.

Workaround:

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 (2)

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

CiscoWorks2000 does not support encrypted directories

Workaround:

None

CSCdt21743 (2)

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.

Workaround:

None

CSCdt32795 (2)

CiscoWorks2000 malfunctions if operating system upgraded after installation.

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

CSCdt63101 (5)

When installing CiscoWorks2000 as non-root user, an error message appear.

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.

Workaround:

Run installation from an administrator's account.

CSCdx29774 (3)

Change password dialog boxes dissapear behind Setup window

Dialogs waiting for user inputs goes behind the setup screen, giving it a hanging appearance. Actually the installation is not hanging. The dialogs [like password change dialogs etc] is appearing behind the setup screen, and waiting for user inputs. This gives an apperance as if the install is hanging.

Workaround:

As instructed by the setup , close all other applications before starting the installation. Do not switch the focus from the install screen, till it gets complete.

CSCin08319 (3)

Java Plugin Shortcut getting displayed after Upgrade

If the user has a shortcut to uninstall CAM client in CDONE 4th Edition and then has performed an upgrade to CDONE 5th edition, the shortcut to uninstall CAM client page gives 404 page not fount error.

Workaround:

The uninstall CAM client is no longer shipped. Delete this shortcut.

CSCin04082 (4)

Pentium IV: java.exe error shown during installation

While installing CD One on a Penitum IV machine, displays the error:

java.exe has generated errors and will be closed 
by windows. You will need to restart the program. 
An error log is being created.

Workaround:

Click the OK button of the message dialog box. Installation will continue even if the message box is ignored. This message does not affect any functionality.

CSCin09458 (4)

Displays error meassage if intergration utility is installed alone.

While installing CD One, 5th edition, if you install Integration Utility alone, the installation displays a message:

Failed to set file permissions 

at the end of Integration Utility installation.

Workaround:

None. This message do not affect the functionality.

CSCdx30443 (4)

Access to file denied dialog box appears with virus scanner on

When the McAfee VirusScan version 5.15.0002 is installed on the machine where CD One, 5th Edition is getting installed, message appears:

Access to file denied" while trying to access 
plugin-131-sparc.tar.gz and jpi131-hpux.tar.gz.

Workaround:

None. This do not affect the functionality. Please click OK to the warning dialog box and the installation proceeds.

CSCdx36376 (2)

Random virus alerts on .gz files under htdocs/plugin at install

Random virus alerts on .gz files under htdocs/plugin at install

Workaround:


CiscoView Known Problems

Table 3 CiscoView Known Problems 

CSCdr33955 (3)

Multiport monitor graphs for device running CiscoView display incorrect values.

Multiport monitor graphs for device running CiscoView display incorrect values.

Workaround:

Generate monitor graphs for individual ports.

CSCds41560 (3)

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

This is observed on NT client running CiscoView in Internet Explorer 5.x.

The 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.

Workaround:

Click Print icon to print chassis view.

CSCdt04355 (4)

CiscoView console buttons cannot be selected with Enter key.

This is observed in CD One, 3rd Edition and later.

Workaround:

Use mouse or spacebar to activate selection instead of Enter key.

CSCdt43794 (5)

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

This is 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 the main CiscoView chassis window.

Workaround:

Open configuration dialog by double-clicking component. The Configure window will launch automatically and be properly displayed.

CSCdv51906 (2)

Unable to launch CiscoView 5.3 on AIX 4.3.3 clients running Navigator 4.78 with Java Plug-in 1.3.0.9 enabled.

This is observed on AIX 4.3.3 clients with both CiscoWorks2000 LAN Management Solution 2.0 and Netview 6.0.2 installed.

This problem occurs:

1. When attempting to launch CiscoView 5.3 from Netview 6.0.2; or

2. When attempting to launch CiscoView 5.3 from CiscoWorks2000.

Workaround:

None

CSCdt79469 (4)

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

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

Workaround:

None


Desktop Known Problems

Table 4 Desktop Known Problems 

ID
Summary
Explanation

CSCdw92538 (3)

CPU Utilization peaks when SSL Initializes

In SSL mode, you are redirected to http mode and then after SSL initialization, the user is again redirected back to https mode. During this time, the CPU utilization on the Client machine might go upto 100%. But it will stabilize after sometime
The browser hangs, when the redirection from "http to https mode and vice versa" happens several times in the same browser session.

Workaround:

Restart the browser.
It is advisable to minimize the number of redirections in the same browser session.
1. Do not refresh or reload index.html page of the same server successively. After SSL Initialization has happened once for a particular server in a browser session, successive access (refresh/reload if required) can be done directly through "https://server:port/login.html" instead of index.html.

2. Do not change the CiscoWorks2000 Servers, being accessed repeatedly in the same browser session.

CSCdw04601 (3)

Page can not be displayed error during navigation

When SSL in enabled, during navigation a message appears:

This page contains both secure and non secure 
items. Do you want to continue.

Whether you select yes or no, an error is displayed:

page cannot be displayed

Workaround:

Refresh the browser or Start the work from the first step (Clicking in the left tree)

CSCdw11344 (3)

Telnet succeeds when TCP fails

The commands tcp/udp small servers works only for IOS and they are disabled by default since the IOS version 12.0M.

Workaround:

None

CSCdx37840 (3)

SSL only: resizing the browser resets the CMF desktop

While resizing the Netscape browser on Solaris clients after enabling SSL, the desktop content is to set to its original state.

Workaround:

Do not resize the browser.

CSCin02932 (3)

Job succeeds but its shows failed in job details window

When debug is enabled in the device, the job will be successful, but will show as Unsuccessful.

Workaround:

Disable debug in the device and run the job

CSCdv22620 (4)

Two Help windows comes when no plugin was installed on the client

Two help windows appear when no plug-in is installed on the client machine.

Workaround:

None.

CSCin06195 (4)

Browser version should be changed according to the client

Windows 2000 clients will be shown as Windows NT 5.0.
When Windows 2000 clients are used the version is detected by Javascript standard function call navigator.appVersion. This returns Windows NT 5.0 instead of Windows 2000.
Microsoft internally refers Windows 2000 as Windows NT 5.0.

Workaround:

None

CSCdw64365 (4)

Inconsistent Tree Structure

Inconsistent Tree Structure in the browser. The order of About The Server, Setup, Diagnostics, Administration folders will not be consistent.
The inconsistent tree structure will appear before and after enabling System, Network Services. This may appear when you enable / disable SSL also.

Workaround:

None.

CSCin07663 (3)

CPU hog by javaw.exe

Occasionally javaw.exe hogs cpu when CiscoWorks2000 server is run for a long time.

Workaround:

Stop the daemon manager. If the process still hogs kill the process or reboot the machine.

CSCdw61688 (5)

JOS:Character circle-c corrupted with Japanese font

In all platforms, at the bottom of each Help window, "Copyright (c) 2001, Cisco Systems, Inc. All rights reserved." has corrupted character for (c) (cmf01.bmp)

Workaround:

You can display correct character by choosing English encoding of the browser.

CSCin00669 (2)

EDS-filter is not working through CLI

Do not use the Windows telnet application for invoking GUI through CLI. For example, Host-Unix to digital. 'eds -filter' and 'eds -display' works fine when 'reflection X' is used.

CSCdw67986 (1)

Can not load CD One login page in Netscape Navigator 4.7x

Always enable Javascript. Select the Enable Javascript check box in
Edit > Preferences > Advanced dialog box

CSCdx28719 (3)

Netscape on AIX crashes intermittently for no apparent reason

Netscape Navigator on AIX client crashes intermittently with Segmentation fault error.

Workaround:

Kill the browser session and restart it again.

CSCin03389 (3)

Adhoc template failed for some catalyst devices

When debug is enabled in the device, the job will be successful, but will be shown as unsuccessful.

Workaround:

Disable debug in the device and run the job.

CSCin10591 (4)

Java Plug-in 1.3.1_xx versions are not supported

If JPI1.3.1 and 1.3.1_03 are installed on a client machine, and if we try to launch the CW2000 home page, then login panel never shows up for both Internet Explorer and Netscape Navigator. This is a compatibility issue.
JPI 1.3.1_xx versions are not supported

Workaround:

Uninstall all JPI's on the client and invoke CiscoWorks2000. This will guide you to install JPI1.3.1.


Catalyst Devices Known Problems


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


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

ID
Summary
Explanation

CSCdm63758 (3)

On Catalyst 4000 and 6000 devices running CiscoView, click Create in Ether Channel Configuration dialog box and new table entries are not added.

Functionality of Create button in Ether Channel Configuration dialog box differs from functionality of Create button in other dialog boxes. For this particular dialog box, each port is assigned a table entry. Rather than creating or deleting a table entry, you can enable, disable, or modify an existing entry by clicking Create and changing its administrative status.

CSCdr34879 (2)

All ports on WS-X6608-T1 module 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.

CSCds78228 (3)

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 display 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.

CSCdv16373 (3)

Dialog boxes available in Catalyst OS version of the Catalyst 6000 device package are not available in Cisco IOS version of the same device package.

Missing dialog boxes are not supported by latest release of Cisco IOS.

This problem will be addressed in the next release of Catalyst 6000 IOS device package.

CSCdw38266 (2)

CiscoView does not support RPS LED on Catalyst 2948G and 2980G devices.

Support for chassisPs2Type MIB object will be available in release 1.9 of Catalyst 4000 device package, which is targeted for use with Catalyst OS version 7.2(1).

CSCdx09882 (3)

With release 1.5 of Catalyst 5000 device package running in CiscoView 5.3, WS-X5114 module incorrectly displays six ports.

WS-X5114 module should display 12 ports, as illustrated at the following URL:

http://www.cisco.com/univercd/cc/td/doc/product/
lan/cat5000/hardware/modules/04ether.htm#
xtocid996110

Problem will be addressed in release 1.6 of Catalyst 5000 device package.


Router and Hub Known Problems

Table 6 Router and Hub Known Problems 

ID
Summary
Explanation

CSCdt26857 (3)

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

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

Workaround:

None


General Device Package Known Problems

Table 7 General Device Package Known Problems 

ID
Summary
Explanation

CSCds13156 (3)

On Cisco MC3810 device running CiscoView, NullptrException error is returned after attempting to launch a monitoring dialog box with both a T1/E1 port and any other port selected.

When you:

1. Select a T1/E1 port and any other port while holding down the Control key.

2. Right-click to display context menu and select Monitor.

NullptrException is displayed twice, and a monitoring dialog box is not launched.

Workaround:

None

CSCdx50367 (3)

When DISPLAY variable for Solaris client is set to a remote machine, chassis view for device with large chassis does not launch.

To reproduce problem:

1. Set DISPLAY variable of Solaris client to a remote Solaris machine. For example, on your local machine enter setenv DISPLAY <remote-machine> at the command line.

2. Launch CiscoView.

3. Open a device with a large chassis (for example, a Catalyst 6000 device). The chassis view does not launch as expected.

Note Problem occurs only when a device with a large chassis is the first device accessed after launching CiscoView.

Workaround:

Resize the browser window. Chassis view will be displayed properly.


Package Support Updater (PSU) Known Problems

Table 8 Package Support Updater (PSU) Known Problems 

ID
Summary
Explanation

CSCdt04070 (4)

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

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

Workaround:

None

CSCdt24701 (4)

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.

Workaround:

None

CSCdt36869 (4)

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

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

Workaround:

Do not use PSU web interface and standalone PSU simultaneously to download device packages from Cisco.com.

CSCdt83908 (4)

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

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

Workaround:

None.


Integration Utility Known Problems

For Windows 2000 users with NTFS, the file NMIDBOptions.properties contains Cisco.com 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 Cisco.com password security is a concern.

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

Table 9 Intergration Utlity Known Problems 

ID
Summary
Explanation

None.

The integration currently done with Network Node Manager (NNM) 6.0 and later 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.

Workaround:

None.

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, such as Essentials, and you will notice that its browser has also changed.

CSCdm61980 (2)

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).

Workaround:

None.

CSCdm91445 (3)

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.

Workaround:

None.

CSCdp17559 (3)

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

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

Workaround:

None.

CSCdr38931 (3)

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.

Workaround:

Free 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.

CSCds19672 (3)

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

Integration Utility loads only 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 affected.

Workaround:

Manually add/define traps using Event configuration GUI provided by NMSs.

CSCin08471 (3)

User should be recommended to integrate later for server with SSL

It should be recommended to the user, that if the CiscoWorks server will be enabled for SSL, it is better to integrate with 3rd party NMS later rather than during install. This is necessary because one is required to reintegrate if any change in protocol happens.

Workaround - None.

CSCin08472 (3)

SSL enable/disable, notification required to reintegrate NMS

After the integration, while enabling or disabling SSL in CiscoWorks2000 Server, cannot launch any CiscoWorks2000 application from third party NMSs like HPOV,Netview,..etc.

Workaround:

You must perform the integration again whenever you enable or disable SSL in the CiscoWorks2000 Server. This is required to update the application registration in NMS.


CA-Unicenter Adapter Known Problems

Table 10 CA-Unicenter Adapter Known Problems

Bug ID
(Severity)
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 (3)

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.

Workaround:

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 (3)

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

CSCdt69570 (3)

Permissions report should be more specific

Current Permission report provides permissions at the module level and not at task level

Workaround : None

CSCdu70168 (3)

Device Synchronization to Essentials not working if server not specified

In CD One 4th Edition on Solaris, Select Server Configuration > Setup > ANI Server Admin > Device Synchronization, and select Synchronizeto Essentials. When you click on the Apply button, if the "Essentials Server" boxes are left blankdisplays an error "Essentials Config: exception com.cisco.nm.ani.share.idl.AniBaseModule.AuthoritationFailure {
java.lang.String details="no 'cmd' parameter received"

Workaround:

Specify the credentials (Host, port, Username, passwd) and specify the mode . Click Apply.

CSCdv52495 (2)

VP tunnels not discovered properly

VP tunnels will not be shown with proper link attributes.

Workaround:

None

CSCdv55105 (3)

anisnmp.conf should allow name wildcarding

If you have the following set-up:
Switches: RO public, RW private
Routers: RO hello, RW goodbye
All switches have names that start with S and sll routers have names that start with R.

If you need to set up the SNMP Settings in the following manner:
S*:public::::::private
C*:hello::::::goodbye

Workaround:

None

CSCdw05781 (3)

switches are placed in NO_VTP domain inproperly

Inconsistency exists in the map display of some of the switches (non-VTP aware ones)under the VTP domain category.They are placed in NO_VTP domain while they have neighbors in normal VTP domain AAA.

CSCdw68571 (3)

Device Synchronization does not support sysNames.

ANI to RME device import only looks for the hostname or IP address. sysNames are not supported. The IP address will be used as Device Name even though the sysName was successfully discovered.

Workaround:

This problem is due to the java DNS caching problem. Java caches negative lookup which caused the problem in the customer's scenario. Hence a property
sun.net.inetaddr.ttl=0 is used to set the JVM not to cache the DNS lookup.

The above property is used to start the ANI JVM not to use the cache and to use a new lookup each time when queried for DNS resolution.

Enter the following:

1. #pdreg -u ANIServer

2. #pdreg -r ANIServer -e /opt/CSCOpx/bin/cwjava -d EDS,ANIDbEngine -f

"-cp:a^/opt/CSCOpx/lib/classpath/servlet.
jar^-Dvbroker.orb.gcTimeout=90^-Dsun.n
et.inetaddr.ttl=0^-mx512m^com.cisco.nm.an
i.server.frontend.AniMain"

CSCdx00913 (2)

Device Synchronization from RME to ANI not sending any devices

Device Synchronization from RME to ANI is not supposed to send devices, only credentials.

Workaround:

None

CSCin03204 (3)

Device sync between 2 SSL enabled servers not supported

Device sync is not supported for the following combinations:
1) Between two separate SSL Servers ( one running ANI and other running RME); however if both ANI and RME are in same box running in SSL mode , The device sync is supported.

2) From a non-SSL ANI server to SSL enabled RME, CMF should provide API for transferring the certificates. Currently no such service exists.

WorkAround: Disable SSL and then run device sync.

CSCdj60832 (2)

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 (3)

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 (3)

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.

CSCdp76410 (3)

Campus client cannot connect to server using proxies.

CD One does not support proxies.

Workaround:

None

CSCdr84799 (3)

Applications not functioning across Network Address Translator (NAT).

Applications not functioning across Network Address Translator (NAT).

Workaround:

None

CSCdt20329 (3)

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

Following actions result in problem:

1. Select Topology 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

Workaround:

None

CSCdt56346 (30

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.

Workaround:

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 (2)

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.

Workaround:

None

CSCdp00593 (2)

SNMP report displays
wrong HwVersion and HwVersionMinor for LS1010 device.

SNMP report displays
wrong HwVersion and HwVersionMinor for LS1010 device.

Workaround:

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

CSCin05978 (4)

ANI upgrade failure

ANI upgrade failure message appears when upgrading ANI in machines with CD One and RME installed as the ANI server is not active and no data is available for ANI upgrade.

Workaround:

None. This error message do not affect ANI functionality


Browser Known Problems

Table 13 Browser Known Problems 

ID
Summary
Explanation

None

When CiscoWorks2000 is invoked in http mode ( http://server:port/ ), displays: "Java Plug-in Security Warning" message box.

When CiscoWorks2000 is invoked in http mode (http://server:port/ ), it displays:

Java Plug-in Security Warning message, asking whether to Grant or Deny permission for a signed applet to run.

Even if the User chooses Deny, the login page is displayed. This will not affect the functionality.

The applet requires special access to run only in "https" mode. In HTTP mode, it merely redirects to the login page. So even if the permission is denied for the applet to run, the login page is displayed.

CSCdt05102 (2)

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

Problem exists within Netscape.

Workaround:

None

CSCdt06518 (2)

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:

Launch CiscoView.

Open a device. CiscoView will prompt for community strings.

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

Workaround:

Enter community strings before launching second instance of CiscoView.

CSCdx04645 (5)

Blank window is sometimes displayed after launching online help.

Problem observed on Solaris clients running CiscoView 5.4 in Navigator 4.76.

Click Help in any dialog box and blank window is sometimes returned, even though status bar displays Document: Done.

Workaround:

Click Reload and the appropriate online help is displayed.

CSCdt11838 (2)

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.

Workaround:

Install Java Plug-in manually. For more information regarding the Java Plug-in, see the "Support Information" section.

CSCin05664 (3)

Essentials hangs when Logout button is pressed in AIX client.

Symptom: Browser hangs when Logout button is pressed in AIX client.

Condition: The same condition has been tested with the previous versions of Netscape and only in the latest versions of Netscape the problem occurs. ==>Same page is working fine with confirm() method of JavaScript instead of alert() method which is used in the page.

Workaround:

Kill the browser session and restart it again

CSCin00944 (2)

Plugin 1.3.1 not reconginzed properly by Solaris Netscape clients

When CiscoWorks2000 is invoked on Solaris clients (netscape and plugin version given below):

Client Platforms : Solaris
Netscape versions: 4.77, 4.78, 4.79
Java Plugin : 1.3.1
Solaris Netscape (versions 4.77,4.78,4.79) does not recognize the Java plugin already installed on the client and keeps prompting to install plugin again. This is due to a bug on Solaris Netscape (4.77 or later)

Workaround:

For Solaris Clients, use only Netscape Navigator 4.76.

When invoking CiscoWorks2000 from Netscape (versions and platform given below)
Client Platforms : Windows, HPUX, AIX
Netscape Versions: 4.78, 4.79
Java Plugin : 1.3.1

This problem is observed only if Java Plugin option is Enabled in Netscape preferences.Cookies get disabled when invoking the CiscoWorks2000 on Netscape when Java Plugin is enabled and you will not be able to login to CiscoWorks2000.

WorkAround: Always turn off (uncheck) the Java Plugin option from
Edit > Preference > Advanced

CSCin06210 (3)

Non-Admin users of Client Machines not able to download JSSE jars

Unable to invoke CiscoWorks 2000 application when logged in as a non-admin user in the client machine for Windows.

Workaround:

Login as a administrator and access the application which will download the necessary jar files in the client system so that non-admin users could also access the server from it. Also change the permission (give full permission) of the Java Plugin directory.


General Known Problems

Table 14 General Known Problems 

ID
Summary
Explanation

None.

Local machine configuration is used when performing a remote upgrade.

There are two possible sources for configuration information: the local machine and a remote machine. Of these two sources, the configuration information for the local machine has precedence, and it is this information that is used during a remote upgrade.

None.

CiscoView log file resides in a new location.

For CiscoView 5.4, the cv.log file is now located in the following directory:

Windows 2000 clients: CiscoWorks2000-installation-directory\log\
cv.log

For example, c:\Program Files\CSCOpx\
log\cv.log

Solaris clients: /var/adm/CSCOpx/log/cv.log

CSCin07682 (4)

Default button inactive in Java-Plugin Security warning window

The "Java Plugin Security Warning" window which is displayed just before the launch of the Cisco Works home page, has 'Grant this Session' button as the default button and it is highlighted. But pressing enter key has no effect on this button.

Workaround:

Use the mouse and click on `Grant this Session' button.

CSCdw61684 (4)

JOS:Apache generates error message localeinfo_ja_jp.properties n

These error messages are found to be logged when we invoke RME >Availability Dashboard > Device Center > Reachability Trend. They are logged only at the first time the application is invoked from a client (succeeding invocation at the same client does not generate the error message).

Workaround:

None. This do not affect functionality.

CSCdx20593 (5)

During device list import, unable to navigate to a CSV format file using Up One Level icon.

Problem observed on HP-UX clients running CiscoView 5.4.

To reproduce problem:

Launch CiscoWorks2000.

Select Device Manager > Administration > CiscoView Server > CiscoView Device List > Import Device List.

Select CSV format file button, and then click Browse.

From Choose File dialog box, click Up One Level icon. Nothing happens.

Workaround:

Use the list box to navigate to the desired file.

CSCdx41954 (3)

CiscoView user preferences are not imported during remote upgrade.

After entering import_cdone.pl at command line to perform remote upgrade, CiscoView user preferences are not imported.

To work around problem:

Stop the CiscoWorks2000 daemon.

Solaris clients: At command line, enter /etc/init.d/dmgtd stop

Windows 2000 clients: At command line, enter

net stop crmdmgtd

Solaris clients: Copy all files from $NMSROOT/rigel/cmf/CV/wwww/classpath/
cvuserprefs directory to $NMSROOT/www/
classpath/cvuserprefs directory.

Windows 2000 clients: Copy all files from $NMSROOT\rigel\cmf\CV\wwww\classpath\
cvuserprefs directory to $NMSROOT\www\
classpath\cvuserprefs directory.

Restart the CiscoWorks2000 daemon.

Solaris clients: At command line, enter /etc/init.d/dmgtd start

Windows 2000 clients: At command line, enter net start crmdmgtd

CSCdr97090 (3)

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.

Workaround:

Tune kernel according to situation. Consult your operating system vendor for instructions on tuning the kernel.

CSCds75572 (2)

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.

Workaround:

Do not enable Event Logging.If Event Logging already enabled, disable it by performing the following steps:

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

Set EventLogger to None, and click Apply.

CSCds90118 (3)

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

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

Workaround:

None

CSCdt22462 (2)

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 (3)

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

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

Workaround:

None.

CSCdx32018 (3)

JOS:JRM occasionally stopped

When DFM is installed on top of CDOne, DFM 1.2 causes JRM to stop, on a Japanese OS Windows 2000 machine. pdshow of JRM says "Administartor has shutdown the process".

Workaround:

None


Internally-Found Resolved Problems

Table 15 Internally-Found Resolved Problems 

Bug ID
(Severity)
Summary
Additional Information

CSCdr67552 (2)

Chassis window does not repaint properly after being resized.

This problem has been resolved.

CSCdr88151 (3)

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

This problem has been resolved.

CSCds73008 (3

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

This problem has been resolved.

CSCdt02050 (3)

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

This problem has been resolved.

CSCdr94291 (2)

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

This problem has been resolved in version 2.0 of Metro 1500 device package.

CSCdr96333 (2)

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

This problem has been resolved in version 2.0 of Metro 1500 device package.

CSCdt73771 (3)

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

This problem has been resolved.

CSCdr80401 (3)

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

This problem has been resolved.

CSCds89236 (4)

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

This problem has been resolved.

CSCdr31691(3)

ANI doesnt handle mis-formated SNMP config file properly

This problem has been resolved.

CSCds82909 (3)

Device attribute not showing voice daughter card on Cat 6k

This problem has been resolved.

CSCds33712 (3)

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

This problem has been resolved.

CSCds07866 (2)

Unable to access ODBC Database.

This problem has been resolved.

CSCdt31121

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

This problem has been resolved.

CSCdp41757 (3)

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

This problem has been resolved.


Customer-Found Resolved Problems

Table 16 Customer-Found Resolved Problems 

Bug ID
(Severity)
Summary
Additional Information

CSCds72290 (2)

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

This problem has been resolved.

CSCdr39315 (2)

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

This problem has been resolved

CSCds55193 (3)

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

This problem has been resolved in version 8.0 of Router 7000 Series device package.

CSCds86109 (2)

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

This problem has been resolved.

CSCdt07445 (2)

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

Problem cannot be reproduced on AIX and HP-UX clients.

CSCdt35177 (4)

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

This problem has been resolved.

CSCdt14047 (2)

2900/3500XL lacks support for data/voice VLAN

This problem has been resolved.

CSCdt25544 (3)

Campus should highlight the exact portion of desc in details repo

This problem has been resolved

CSCdv89293 (3)

Portnames not in Usertracking for one card

This problem has been resloved.

CSCdw25129 (3)

Discrepancy Reports assumes too much regarding VTP configuration

This problem has been resolved.

CSCdw04754 (2)

Cannot add/delete lines in Discovery Settings on Solaris Netscape

This problem has been resolved

CSCdu33523 (2)

Edit SNMP Settings should do error checking

This problem has been resolved

CSCds82867 (3)

Device Center inaccessible for Catalyst 6500 device.

This problem has been resloved.

CSCds71189 (3)

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

This problem has been resolved.


Obtaining Documentation

The following sections explain how to obtain documentation from Cisco Systems.

World Wide Web

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

http://www.cisco.com

Translated documentation is available at the following URL:

http://www.cisco.com/public/countries_languages.shtml

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, elsewhere in North America, by calling
800 553-NETS (6387).

Documentation Feedback

If you are reading Cisco product documentation on Cisco.com, you can submit technical comments electronically. Click Feedback at the top of the Cisco Documentation home page. After you complete the form, print it out and fax it to Cisco at 408 527-0730.

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

To submit your comments by mail, use the response card behind the front cover of your document, or write to the following address:

Cisco Systems
Attn: 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 by using the Cisco Technical Assistance Center (TAC) Web Site. Cisco.com registered users have complete access to the technical support resources on the Cisco TAC Web Site.

Cisco.com

Cisco.com is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information, networking solutions, services, programs, and resources at any time, from anywhere in the world.

Cisco.com is a highly integrated Internet application and a powerful, easy-to-use tool that provides a broad range of features and services to help you to

Streamline business processes and improve productivity

Resolve technical issues with online support

Download and test software packages

Order Cisco learning materials and merchandise

Register for online skill assessment, training, and certification programs

You can self-register on Cisco.com to obtain customized information and service. To access Cisco.com, go to the following URL:

http://www.cisco.com

Technical Assistance Center

The Cisco TAC is available to all customers who need technical assistance with a Cisco product, technology, or solution. Two types of support are available through the Cisco TAC: the Cisco TAC Web Site and the Cisco TAC Escalation Center.

Inquiries to Cisco TAC are categorized according to the urgency of the issue:

Priority level 4 (P4)—You need information or assistance concerning Cisco product capabilities, product installation, or basic product configuration.

Priority level 3 (P3)—Your network performance is degraded. Network functionality is noticeably impaired, but most business operations continue.

Priority level 2 (P2)—Your production network is severely degraded, affecting significant aspects of business operations. No workaround is available.

Priority level 1 (P1)—Your production network is down, and a critical impact to business operations will occur if service is not restored quickly. No workaround is available.

Which Cisco TAC resource you choose is based on the priority of the problem and the conditions of service contracts, when applicable.

Cisco TAC Web Site

The Cisco TAC Web Site allows you to resolve P3 and P4 issues yourself, saving both cost and time. The site provides around-the-clock access to online tools, knowledge bases, and software. To access the Cisco TAC Web Site, go to the following URL:

http://www.cisco.com/tac

All customers, partners, and resellers who have a valid Cisco services contract have complete access to the technical support resources on the Cisco TAC Web Site. The Cisco TAC Web Site requires a Cisco.com login ID and password. If you have a valid service contract but do not have a login ID or password, go to the following URL to register:

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

If you cannot resolve your technical issues by using the Cisco TAC Web Site, and you are a Cisco.com registered user, you can open a case online by using the TAC Case Open tool at the following URL:

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

If you have Internet access, it is recommended that you open P3 and P4 cases through the Cisco TAC Web Site.

Cisco TAC Escalation Center

The Cisco TAC Escalation Center addresses issues that are classified as priority level 1 or priority level 2; these classifications are assigned when severe network degradation significantly impacts business operations. When you contact the TAC Escalation Center with a P1 or P2 problem, a Cisco TAC engineer will automatically open a case.

To obtain a directory of toll-free Cisco TAC telephone numbers for your country, go to the following URL:

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

Before calling, please check with your network operations center to determine the level of Cisco support services to which your company is entitled; for example, SMARTnet, SMARTnet Onsite, or Network Supported Accounts (NSA). In addition, please have available your service agreement number and your product serial number.