Guest

CiscoWorks Common Services Software

Release Notes for CiscoWorks Common Services 3.1 on Windows

  • Viewing Options

  • PDF (677.5 KB)
  • Feedback
Release Notes for CiscoWorks Common Services 3.1 on Windows

Table Of Contents

Release Notes for CiscoWorks Common Services 3.1 on Windows

New Features

Product Documentation

Time Zone Acronyms and Offset Settings

Multi-homed Machines

Operating System Upgrade

Server and Client Information

Integrating with Third-party Vendors

Known and Resolved Problems

Installation Known Problems

CiscoWorks Home Page Known Problems

Software Center Known Problems

Integration Utility Known Problems

CA-Unicenter Adapter Known Problems

Browser Known Problems

DCR Known Problems

Grouping Services Known Problems

General Known Problems

Internally-Found Resolved Problems

Customer-Found Resolved Problems

Obtaining Documentation, Obtaining Support, and Security Guidelines

Open Source License Acknowledgements

OpenSSL/Open SSL Project

License Issues


Release Notes for CiscoWorks Common Services 3.1 on Windows


This release notes is for CiscoWorks Common Services 3.1 running on a Windows platform.

The release notes contains the following sections:

New Features

Product Documentation

Time Zone Acronyms and Offset Settings

Multi-homed Machines

Operating System Upgrade

Server and Client Information

Integrating with Third-party Vendors

Known and Resolved Problems

Obtaining Documentation, Obtaining Support, and Security Guidelines

Open Source License Acknowledgements

New Features

The new features in CiscoWorks Common Services 3.1 are:

Installation Changes

The Common Services installation framework is enhanced to support installation of multiple applications in one solution bundle. You can install Common Services 3.1 or upgrade the earlier versions to Common Services 3.1, using the single installable bundle image packaged in the LMS 3.0 product DVD.

Common Services 3.1 now provides a cleanup script for both Solaris and Windows. If an installation fails, this script clears the files from the installation directory.

New Default Credentials introduced

You can configure a default credential set comprising primary, secondary, SNMP, HTTP and RxBoot Mode credentials, and store them in DCR. You can also add or import devices into DCR with the default credentials.

Secondary Access Credentials in DCR

DCR allows the applications to store primary device credentials such as Primary Username, Password, and Enable Password. The primary device credentials allows the applications to access the devices and operate on them.

In this release, DCR allows you to add a secondary set of credentials. The secondary credentials serve as an alternative to primary device credentials.

Applications such as Resource Manager Essentials can use the configured secondary credentials as a fallback if they cannot access the devices using the primary credentials.

Enhancements to DCR CLI and Delete Devices Option

The earlier DCR command line (CLI) utility allowed you to delete devices using their device ID.

With the enhanced DCR CLI delete devices option, in both shell and batch modes, you can delete the devices using their own identifiers such as hostname and domain name combination, and display name.

You can also delete devices from DCR as specified in the input CSV file, using the enhanced DCR CLI utility.

The DCR CLI now provides an option to export the device information from DCR to ACS Server.

Security Enhancements

Common Services 3.1 has the following security related changes:

ACS Support

Common Services supports integration of ACS 3.3.4 for Windows Server and Appliance (except ACS 3.3.4 Appliance), and ACS 4.1 for Windows Server and Appliance with CiscoWorks server, in addition to the support for ACS 3.3.3 and ACS 4.0 versions.

This security related enhancement requires the role and task definitions to be revisited. You should register the revised role and task definitions with ACS Server in the ACS mode.

Enhancements to Permissions Report

In the enhanced Permissions Report, the tasks are grouped based on applications and displayed in a tabular form. This allows you to quickly locate a particular task in the report.

You can also sort the display of tasks in alphabetical order or in reverse alphabetical order within a task group.

Super Admin Role in ACS Mode

This is a predefined role introduced in this release. This role has full access rights to perform any task including the administration and approval tasks in CiscoWorks.

You can assign this role to a user only on ACS Server and only when your login module is set to ACS. This role is not available in CiscoWorks local mode and during the local user setup in CiscoWorks Server. The Permissions report does not display information about this role.

CiscoWorks and Microsoft Active Directory Server Integration Changes

Earlier, CiscoWorks supported only distinguished name based authentication to Microsoft Active Directory Server.

In this release, the integration of CiscoWorks Server with Microsoft Active Directory Server is made more flexible.

CiscoWorks now also supports User Principal Name (UPN) based authentication, domain name based authentication, and Security Account Manager (SAM) account based authentication to the Microsoft Active Directory server.

Bulk Addition of Local Users Through CLI

In the earlier releases, Common Services supported adding local users to CiscoWorks Server only through the user interface. Common Services did not support bulk addition of local users.

With the introduction of a script for adding local users, you can add bulk local users through CLI. You can also import the local user information from remote servers of similar version through CLI.

Enhancements to CiscoWorks Home Page

CiscoWorks home page and the application windows that are launched from CiscoWorks home page now contain the name of the CiscoWorks Server along with the browser title.

This feature helps you to identify the server in which the applications are installed. This is particularly useful in a multi-server setup and Single Sign-On (SSO) based setup.

Changes to Device Center Connectivity Tools

Common Services 3.1 provides an enhanced user interface to select a specific SSH protocol version (SSHv1 or SSHv2) for a device using the Management Station to Device tool. This is used to test the protocol connectivity against the chosen device.

Logging Configuration

The new Logging Configuration user interface allows you to enable debug modules in Common Services such as DCR, Software Center, CiscoWorks home page and so on.

You do not need to restart the daemon manager after you have enabled the debugging option for a particular module.

Disk Space Monitoring and Threshold Configuration

You can monitor the disk space availability in your CiscoWorks Server and configure the threshold level of disk space utilization. You can also set an option to notify end users through e-mail when the disk space exceeds the selected threshold level.

Backup-Restore Changes

The Backup-Restore component is enhanced to send you an e-mail on the status of immediate or scheduled backup jobs when they complete.

The e-mail notification is also sent when you schedule a backup job or remove a scheduled backup job.

You should configure one or more e-mail addresses if you want to receive the email notification.

Hostname Change Script

Earlier when you changed the hostname of the CiscoWorks Server, you needed to manually change the hostname related entries in the CiscoWorks directories and files, registry entries, and databases.

Common Services 3.1 provides a script to automatically update the CiscoWorks directories and files, registry entries, and databases, after you have changed your hostname.

IP Address Range Based Device Grouping

Earlier, you could not create a device group for devices within a specified IP Address range.

With the introduction of new range operator, you can group devices within a range of IP Addresses. You can also perform an advanced search of devices within a specified IP Address range.

Support for CiscoWorks LMS Portal and CiscoWorks Assistant

Common Services 3.1 supports new LMS applications namely CiscoWorks LMS Portal and CiscoWorks Assistant that help to improve the usability of existing applications in the LMS bundle.

CiscoWorks LMS Portal helps you to set up a customized home page. The status summary of Common Services jobs, security configurations and other information are available as portlets in the LMS Portal application.

CiscoWorks Assistant is a web-based tool that provides workflows to help you to overcome network management and LMS deployment challenges. Using CiscoWorks Assistant you can easily deploy multiple LMS server and maintain device credentials.

See the User Guide for CiscoWorks LMS Portal 1.0 and User Guide for CiscoWorks Assistant 1.0 for more information.

Support for MDF 1.18

Meta Data Framework (MDF) Package defines device types in a uniform way across CiscoWorks applications. This package contains new device types, new device type definitions, new device icons, and solutions to some problems in earlier MDF packages.

This package contains new device types, new device type definitions, new device icons, and solutions to some problems in earlier MDF packages.

The MDF package version 1.18 contains the following new device types:

Cisco 5720 Integrated Encryption Router (1.3.6.1.4.1.9.1.820)

Cisco 5740 Integrated Encryption Router (1.3.6.1.4.1.9.1.833)

Cisco 5750 Integrated Encryption Router (1.3.6.1.4.1.9.1.731)

Cisco 7855I Media Convergence Server (1.3.6.1.4.1.9.1.588)

Cisco 7865I Media Convergence Server (1.3.6.1.4.1.9.1.589).

When you add new device types through MDF Package, it does not guarantee support for these device types in all the CiscoWorks applications.

Device support has to be provided by individual applications, such as DFM, RME and Campus Manager. For a list of supported device types, see the relevant Product Documentation at the following URLs:

http://www.cisco.com/en/US/products/sw/cscowork/ps2421/products_device_support_tables_list.html

http://www.cisco.com/en/US/products/sw/cscowork/ps2073/products_device_support_tables_list.html

http://www.cisco.com/en/US/products/sw/cscowork/ps563/products_device_support_tables_list.html

For details on Common Services 3.1 features, see:

http://www.cisco.com/en/US/products/sw/cscowork/ps3996/products_user_guide_list.html

Product Documentation


Note We sometimes update the printed and electronic documentation after original publication. Therefore, you should also review the documentation on Cisco.com for any updates.


Table 1 describes the CiscoWorks Common Services documentation that is available.

Table 1 Product Documentation 

Document Title
Available Formats

Release Notes for CiscoWorks Common Services 3.1 on Windows (this document)

PDF on:

Product DVD

LMS 3.0 Documentation CD-ROM.

On Cisco.com at:

http://cisco.com/en/US/products/sw/cscowork/ps3996/
prod_release_notes_list.html
(part number OL-11779-01)

User Guide for CiscoWorks Common Services 3.1

PDF on:

Product DVD

LMS 3.0 Documentation CD-ROM.

On Cisco.com at:

http://cisco.com/en/US/products/sw/cscowork/ps3996/products_user_guide_list.html (part number OL-11776-01)

User Guide for CiscoWorks Integration Utility 1.7

PDF on:

Product DVD

LMS 3.0 Documentation CD-ROM.

On Cisco.com at:

http://cisco.com/en/US/products/sw/cscowork/ps3996/products_user_guide_list.html (part number OL-13627-01)

Context-sensitive Online help

Click Help from the page you are on for context-sensitive help.


Time Zone Acronyms and Offset Settings

Table 2 shows time zone acronyms supported in the CiscoWorks applications that use the time zone feature.

Column 1—Alphabetically lists the supported CiscoWorks 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.

Column 6—Lists the resulting output in reports.

If you generate reports, the output will vary depending on whether the data has been processed through Perl or Java. Table 2 also provides possible outputs 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.

The device should be configured to send Syslogs with the appropriate timezone acronym that indicates whether daylight savings is in effect at the time of sending the Syslog. This is to ensure that the Syslog analyzer or Essentials uses the correct acronym for time conversion.

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

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

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

UTC

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 CiscoWorks Common Services on a multi-homed machine, there are two requirements.

All IP addresses must be configured in DNS.

Owing to restrictions in CORBA, only one IP address can be used by the client or browser to access the server. You must select one IP address as the external address, with which the client will login to the CiscoWorks server.

To select an IP address:


Step 1 Modify the gatekeeper file located in NMSROOT\lib\vbroker\gatekeeper.cfg

where NMSROOT is the directory in which CiscoWorks is installed.

Step 2 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

Step 3 After modifying the gatekeeper file, restart the Daemon Manager. To do this, first stop the Daemon Manager by entering:

net stop crmdmgtd

Step 4 Start the Daemon Manager by entering:

net start crmdmgtd


Operating System Upgrade

While installing CiscoWorks Common Services, the installation process checks for required patches.

For a list of required service packs, see Chapter 2 of Installing and Getting Started with CiscoWorks LAN Management Solution 3.0 at: http://www.cisco.com/en/US/products/sw/cscowork/ps2425/prod_installation_guides_list.html.

If CiscoWorks does not operate properly after installing all necessary service packs, check the permissions in the directory install-directory\objects\dmgt\ready. Local administrators group and casusers group must have full access. If the permissions are incorrect, stop the Daemon Manager, change the permissions, and start the Daemon Manager again.


Caution If CiscoWorks Common Services is run without the required service packs, it will not function properly.

Server and Client Information

For information on server and client requirements for the system and browser, see the Prerequisites chapter of Installing and Getting Started With CiscoWorks LAN Management Solution 3.0.

Integrating with Third-party Vendors

Use the Integration Utility to integrate Cisco device information and Cisco applications into SNMP management platforms like:

HP OpenView Network Node Manager 7.5 (on Windows and Solaris 9 only)

NetView 7.1.5 (on both Windows and Solaris)


Note HP OpenView Network Node Manager is not supported on a Solaris 10 platform.


See User Guide for CiscoWorks Common Services 3.1 and the online help for information about importing devices.

You might need to run the Integration Utility to:

Change your Cisco.com login information.

Change your CiscoWorks server location.

Register a new application.

Change the NMS with which you wish to integrate your Cisco applications.

For more information on Integration Utility, see User Guide for CiscoWorks Integration Utility 1.7.

Known and Resolved Problems

Tables 3 to 11 describe the problems known to exist in this release, Tables 12 and 13 describe the problems resolved from Common Services 3.1 onwards.


Note To obtain more information about known problems, access the Cisco Software Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl (You will be prompted to log onto Cisco.com.).


The CiscoWorks Common Services known problems are broken down into the following sections:

Installation Known Problems

CiscoWorks Home Page Known Problems

Software Center Known Problems

Integration Utility Known Problems

CA-Unicenter Adapter Known Problems

Browser Known Problems

DCR Known Problems

Grouping Services Known Problems

General Known Problems

Internally-Found Resolved Problems

Customer-Found Resolved Problems

Installation Known Problems

Table 3 describes the known problems related to the installation of Common Services.

Table 3 Installation Known Problems 

Bug ID
Summary
Explanation

CSCsh48602

Icons appear in the Add/Remove Programs even after the installation aborts.

This happens when you abort the installation soon after the Summary window. Aborting installation at this point is however not recommended.

Workaround:

Perform a manual cleanup in the directory structure and registry.

CSCds90562

Daemon Manager does not run if CiscoWorks home directory is encrypted.

CiscoWorks does not support encrypted directories.

Workaround:

None. Do not install CiscoWorks in an encrypted directory.

CSCdt63101

When installing CiscoWorks as non-root user, an error message appears.

When installing CiscoWorks under a non-administrator account on Windows 2000, the following message appears:

Setup Initialization Error 
Setup has detected that unInstallshield is in 
use. Please close unInstallshield and restart 
setup. 
Error432.

When you click the OK button, installation terminates.

Workaround:

Run installation from a local administrator's account.

CSCdx71019

You cannot uninstall CiscoWorks Common Services if disk space is insufficient.

CiscoWorks Common Services cannot be uninstalled if disk space is insufficient. This is because the installer cannot allocate sufficient temporary space.

Workaround:

Delete the CSCOpx folder and clean the registry, manually.

CSCdz34376

Reinstallation aborts and displays a message that the jpishare.dll is locked.

Reinstallation aborts after displaying messages that the files jpishare.dll and jpins32.dll are locked.

Workaround:

Close all the browser sessions and the Java Plug-in instances that are running in the server and restart the installation.

CSCea18129

Uninstallation or installation displays incorrect error message.

Uninstallation or installation displays the following error message even if there is no other installation running:

[un]installation is already running

This happens when you are not a member of the local Administrators group.

Workaround:

Install or uninstall as a user who is a member of the local Administrators group.

CSCeb03515

When you uninstall, resintall or upgrade, an error message,
Verify Stopped Processes
appears.

This error occurs when a Java-Plugin is running or browsers using Java-Plugins are running.

The error message states that the wizard will verify whether the CW2K files are being used by other running processes.

When you click Yes, the wizard lists a process that still uses CW2K files. You must stop these process.

Workaround:

Close all the browsers and Java-Plugins when the error occurs.

CSCin23546

Installing Common Services deletes previous web server entry.

This problem occurs when CiscoWorks registers its webserver with the default name Apache in Windows services. This also overwrites the previously installed Apache service that has the same name.

Workaround:

The other standalone Apache webserver can be started from the command line. It can also be registered as a service that has a different name using:

apache -i -n "Service Name"

See documentation on the Apache Website for more details. However, we recommend that you do not have other webservers on the machine where CiscoWorks is installed.

CSCin32988

Cannot login after installation.

This occurs when the non standard java options -Xbootclasspath is set with '.' using _JAVA_OPTIONS as the environment variable, before installing the product.

Workaround:

1. Copy the cwpass file from NMSROOT\lib\classpath\com\cisco\nm\cmf\
servlet\orig\cwpass to NMSROOT\lib\classpath\com\cisco\nm\
cmf\servlet\cwpass.

2. Restart the Daemon Manager. To do this:

a. Stop the Daemon Manager by entering:

net stop crmdmgtd

b. Start the Daemon Manager by entering:

net start crmdmgtd

CSCsa04303

All files in the temporary directory are not cleaned by CiscoWorks Common Services after installation.

During installation, the files are placed in the setup directory under TEMP.

After installation some of these files are not removed from the directory.

Workaround:

Delete all the files under: %TEMP%\_ISTMPx.DIR, where x is one or two digits.

CSCsa04407

Uninstallation exits when the drive is full.

When you uninstall by selecting Start > Program Files > CiscoWorks > Uninstallation, an error message appears if the drive is full.

Workaround:

Free up some space and then start uninstallation.

CSCsa16542

Installation fails if the install path is long.

If installation directory path length exceeds 1024 characters the installation will fail.

Workaround:

Specify a short custom path.

CSCsa22674

CWCS 3.0 installation on IPv6 configured machine fails without a warning.

When you install CWCS 3.0 on a IPv6 configured machine, setup.exe aborts immediately.

Workaround:

Reconfigure the machine for IPv4, then install CWCS 3.0.

CSCsa26294

Installing Ciscoworks IDU returns an error message stating that there is not enough space on the drive to extract the package.

When installing CiscoWorks IDU, this error message appears:

There is not enough space on drive c:\ to extract 
this package.

This error message appears when the available hard disk size is a multiple of 4 GB (For example, say 8GB, 20GB, or 68GB, etc.)

Workaround:

Download, add or delete files on your computer so that you do not have a multiple of 4 GB on your hard disk.

CSCsb87221

Uninstall hangs with a message that the system cannot find the file specified.

The CPU is full and it does not have the memory to load the uninstall GUI.

Workaround:

Close the uninstallation, stop the process that is occupying the memory and try uninstalling.

You can also reboot the system.

CSCsc57493

If some files are being used by other processes during installation, the installation program displays the Stop All Programs dialog box.

The dialog box lists all the files that are currently being used by other running process.

Workaround:

1. Stop all processes corresponding to the listed files before you proceed with the installation.

To detect the process corresponding to the locked files, you can use Process Explorer utility available for download from http://www.sysinternals.com.

2. After the processes are stopped, click Next in the Stop All Programs dialog box and proceed with the installation.

When you click Next and proceed with the installation, you will get a message box titled Verify Stopped Processes.

3. Click Yes and proceed with the verification. The installation will end abruptly, if you click No.

None.

Installing LMS 3.0 displays an error message that there is not enough space on the drive to complete the process.

Installation requires 16 MB of space in the Windows temporary directory.

This error occurs if the destination path is not the default, and the drive where temp directory resides does not have the required space.

Workaround:

Increase the disk space in windows temporary directory.


CiscoWorks Home Page Known Problems

Table 4 describes the known problems related to CiscoWorks homepage.

Table 4 CiscoWorks Home Page Known Problems 

Bug ID
Summary
Explanation

CSCdw11344

Telnet succeeds when TCP fails.

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

Workaround:

None.

CSCdw61688

JOS:Character circle-c corrupted with Japanese font.

In all platforms, at the bottom of each Help window, the statement,

Copyright (c) 2005, Cisco Systems, Inc. All rights reserved.

has corrupted character for (c).

Workaround:

Display the correct character by selecting the English encoding of the browser.

CSCeh72568

Cannot launch the CiscoWorks home page when machine has no network connection.

Cannot login to the CiscoWorks home page after the machine's network connection is unplugged.

Workaround:

Restart the Daemon Manager after the network connectivity is lost or disabled.

CSCin03389

Adhoc template fails for some catalyst devices.

Adhoc template fails for some catalyst devices. A successful jobs appears as Unsuccessful.

Workaround:

Disable debug in the device and run the job.

CSCin26518

Cannot list files in a drive through file selector.

You cannot list files in a drive through file selector. This occurs only when you map the drive using IP address.

Workaround:

Map the drive using hostname.

If the machines are in different domains, you have to set up proper trust between the domains before mapping the drive using hostname.

CSCsa04318

You can login to CiscoWorks bypassing the security alert.

When you login and click No in the security alert box you can proceed to CiscoWorks homepage.

Conditions:

The server must be in non-SSL mode.

Workarounds:

Close the browser after clicking the No button.

Or

Run the server in SSL mode.


Software Center Known Problems

Table 5 describes the known problems that you might encounter while working with Software Center.

Table 5 Software Center Known Problems 

Bug ID
Summary
Explanation

CSCdt04070

No error message appears when network connection is lost while downloading device packages.

An error message does not appear if the network connection is lost during the download of device packages from Cisco.com.

Workaround:

None.

CSCsa22443

Cannot stop downloading the Software Center device package headers to temporary folder when you click Cancel.

This problem occurs when you:

1. Go to Device Updates > Get Updates.

2. Click Next in the first screen of the wizard.

3. Click Cancel in the second screen.

In Netscape, you will see the list of available packages.

In Internet Explorer, you will see the default screen.

The device package headers will be downloaded to temporary folder.

Workaround:

To clean up the temporary download location explicitly:

1. Stop the Daemon Manager:

Enter net stop crmdmgtd.

2. Remove the contents of the directory under NMSROOT/temp/psu.

3. Restart the Daemon Manager:

Enter net start crmdmgtd.

CSCsa30580

Software Center does not accept Cisco.com login credentials with space between characters.

Software Center does not accept the customer's Cisco.com password if it contains space between characters or even if it contains any special characters.

Workaround:

Change the Cisco.com password.

CSCsb34780

When you download Device Updates or Software Updates, the GUI screens show operation was successful.

However, the destination directory does not show that any updates were downloaded.

The destination directory does not have sufficient disk space to hold the downloaded updates.

Workaround:

Change the destination folder that has more space or clear space in selected folder.

CSCsc06486

A blank screen appears when you download a small device package (approximately 4 KB).

When you download a small device package from Software Center, the progress bar is not displayed. Instead, a blank screen appears. This screen does not close after the download has completed.

Workaround:

Click the Close button to terminate the blank screen.


Integration Utility Known Problems

For Windows users, 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 users, the file NMIDBOptions.properties is not protected from general access.

If Cisco.com password security is a concern, you should disable the Cisco.com update option, and manually download the zip file from the Cisco.com location:

For Internet Explorer: http://ftp.cisco.com/cisco/netmgmt/ciscoview/5.0/packages/nmidb.n.zip

where n is the version number.

For Netscape Navigator:

ftp://username@ftp.cisco.com/cisco/netmgmt/ciscoview/5.0/packages/nmidb.n.zip

Table 6 describes the known problems related to the Integration Utility.

Table 6 Integration Utility Known Problems 

Bug ID
Summary
Explanation

CSCsd75232

Cannot find Cisco related traps in the event configuration window after integrating LMS with HPOV.

Also, the Cisco alarm category is not listed in the OV alarm browser.

The affected NMIDB Version is 1.0.087. The additional traps added as part of NMIDB 1.0.087 version were the probable cause for the trap conflicts.

Workaround:

Please contact Cisco TAC.

CSCdm61980

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

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

Workaround:

To change this behaviour from NNM:

1. Right-click and select symbol properties.

2. Change the action from Expand to Execute.

3. Choose CVWEB application for execution.

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 the application registration information, only an application integration should occur. Instead, a full integration occurs.

Workaround:

None.

CSCdp17559

Login screen appears every time CiscoView is started from the Network Node Manager (NNM) (for example, HP OpenView) using Internet Explorer.

Login screen appears every time you start CiscoView from the Network Management Platform (for example, HP OpenView), using Internet Explorer.

Workaround:

None.

CSCdr38931

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

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

Workaround:

Free up some disk space and relaunch Change Integration Options. Make sure you have at least 25 MB of free disk space.

CSCin08471

Integration with third party NMS should be performed after installing CiscoWorks in a specific scenario.

If you enable CiscoWorks server for SSL mode after installation, integration with third party NMS should be performed later.

Workaround:

If SSL mode is enabled for the CiscoWorks server, we recommend that you perform integration with a third-party NMS after installing CiscoWorks.

This is necessary because any change in protocol requires a reintegration.

CSCin23798

Cannot upgrade to latest NMIDB by clicking Get NMIDB in Integration Utility GUI in rare scenarios.

This problem occurs if the Integration Utility process was terminated or the local machine was rebooted during the previous NMIDB extraction.

If you click Get NMIDB in the Integration Utility GUI, this message appears erroneously:

NMIDB is up to date

Workaround:

Remove VersionInfo.properties file from the following directory:

CiscoWorks installation directory\nmim\

CSCin32985

Cannot integrate with Netview 6.x/7.x adapter.

This problem occurs if you use NMIDB 1.0.067 or later and:

1. Perform integration with Netview 6.x/7.x adapter.

A dialog box that displays only the OK button appears.

2. Attempt to close this dialog box.

It does not close and Integration stops.

Workaround:

Download the latest Netview adapters from Cisco.com and use them for integration.

CSCsa38861

Installation proceeds before integration is completed in NMIM 1.6.

During integration with NMS, if you click once or twice on the DOS window, the installation proceeds before integration gets completed.

Workaround:

Do not click on the DOS window during installation.

CSCsb21911

Two entries of CiscoView(CiscoView 5.x and CiscoView) are seen following an integration with later version of NMIDB, i.e. after NMIDB 1.0.084.

Consider this scenario:

Assume you have already integrated using NMIDB version 1.0.084.

If you download and integrate with the new NMIDB, the menu entry CiscoView 5.x is not removed since the new registry file name in the new NMIDB is different.

As a result, both the menu items, one for CiscoView and another for CiscoView 5.x, appear.

Workaround:

To see the correct CiscoView entry after integration:

1. Unintegrate ('nmic -u' which would do application unregistration).

2. Download the latest NMIDB version to do an integration again.


CA-Unicenter Adapter Known Problems

Table 7 describes the known problems related to a network management system such as CA-Unicenter.

Table 7 CA-Unicenter Adapter Known Problems 

Bug ID
Summary
Explanation

CSCdp17554

Reintegration with CA-Unicenter adapter does not work.

Using Integration Utility, integrate with CA-Unicenter adapter.

If you try reintegration after changing parameters, the adapter warns that the applications have been registered earlier. Consequently, changes in application parameters are not reflected.

Workaround:

You must unintegrate, then reintegrate:

1. At the command line, enter:

C:\program files\cscopx\bin\nmic.exe -u

2. Select Start > Programs > CiscoWorks > Change Integration Options and re-enter adapter information.

Numerous popup menus appear.

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

It also occurs while running Integration Utility with the -u option set.

Workaround:

This is expected behavior for TNG adapter and does not affect integration of TNG with CiscoWorks. Click OK to continue.

Use the same repository name in the Select Repository dialog box.

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.

Workaround:

None.


Browser Known Problems

Table 8 describes the known problems that you might encounter with web browsers.

Table 8 Browser Known Problems 

Bug ID
Summary
Explanation

CSCsh21917

In the PSU device download operation, the Close button in the Job Details URL does not work.

When Mozilla is used as the Client bowser, the window launched for the Job Details URL during the PSU device download operation does not close.

Workaround:

Either:

Use supported Internet Explorer browsers such as IE 6 or 7.

Or

In MOzilla Install location\all.js where MOzilla Install location is the Mozilla installed location, change pref("dom.allow_scripts_to_close_windows", false) into pref("dom.allow_scripts_to_close_windows", true)

CSCsh49922

Cannot use Telnet to connect to a device from Ciscoworks > DeviceCenter > Telnet.

This occurs when Internet Explorer 7 is used as the Client browser.

Workaround:

The following can be done:

Use Firefox as the Client browser

Or

Use Internet Explorer 6

Or

Add the following entry to registry:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_DISABLE_TELNET_PROTOCOL] "iexplore.exe"=dword:00000000 and then restart the browser.

CSCdt11838

While launching an application, you are not prompted to install Java Plug-in.

If you install RealJukeBox Netscape Plug-in before you install Java Plug-in, you are not prompted to install Java Plug-in software when you launch an application. A blank screen appears.

Workaround:

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

CSCsa31202

Tooltips in UII get truncated in Netscape and Mozilla browsers.

If the tooltip for the data cell within HTML scrolling table is large, Netscape and Mozilla browsers truncate the last few characters.

This does not occur for Internet Explorer 6.0.

Workaround:

None.

CSCsc19380

Cannot select the contents of certain pages.

For example, you cannot select the contents of Results page after a PSU operation.

Copying the contents of a page is not possible when using Netscape/Mozilla browsers.

Workaround:

Use IE when the contents of the page need to be copied.

None.

If you have a popup-blocker enabled in your browser, popup dialog boxes will not appear.

Popups do not appear.

Workaround:

Disable the popup-blocker, if you have installed any.


DCR Known Problems

Table 9 describes the known problems that you might encounter while working with DCR.

Table 9 DCR Known Problems 

Bug ID
Summary
Explanation

CSCed10462

Import Devices from Access Control Server (ACS) feature adds non-Cisco devices into DCR.

This occurs when ACS has non-Cisco devices in its list.

Workaround:

Delete the non-Cisco devices from DCR after importing.

CSCee71246

Cannot import files from mapped drive on windows server.

When you import a file located in a mapped drive the following events can occur:

When you list files under the mapped drive, no files will be listed.

When you enter the filename, it displays an error:

Invalid file format.

When you connect to the remote machine with casuser credentials, it displays an error:

Logon failure:- The user has not been granted 
the requested logon type at this computer.

The mounted drive is configured with read/write permission for everyone. This includes the domain user and not the casuser.

Workaround:

Copy the file from the mounted file sytem to the local system and then import.

CSCsa13971

Export feature does not use devices selected in the Device Management screen.

This occurs when you:

1. Login to CiscoWorks.

2. Go to Common Services > Device & Credential Admin > Device Management.

3. Select few devices.

4. Click Export.

Popup window does not have the selected devices.

Workaround:

DCR Export Screen provides a device selector which allows you to select the device to be exported.

CSCsa21220

During DCR Slave configuration no error messages appear when you duplicate devices.

When a Standalone DCR server is configured to be Slave with Add current devices to master, it does not display duplicate devices error messages similar to device import/export screen.

Workaround:

None.

A warning message appears before you make the actual configuration change.

CSCsa32420

Errors occur when you include some special characters and JavaScripts in the User Defined Field (UDF) labels.

When RME reports display these UDF labels, the JavaScripts causes problems.

Workaround:

Do not include JavaScripts in the UDF labels.

CSCsa37597

Wrong error messages appear when you create groups with User Defined Fields (UDF) names with some special characters, in DCR Admin page.

Wrong error messages appear if the UDF labels:

Contain two consecutive periods.
For example, udf..attribute.

Begin with a period.
For example,.udf_attribute.

End with a period.
For example, udf_attribute.

Workaround:

Do not enter special characters in the UDF names.


Grouping Services Known Problems

Table 10 describes the known problems associated with managing groups of devices.

Table 10 Grouping Services Known Problems 

Bug ID
Summary
Explanation

CSCsa23339

Two users cannot create private groups with the same name.

Error messages appear when two different users create private groups with the same name in User Defined Groups.

Workaround:

Create a separate folder with any name and then create the private groups.

CSCsa36841

Add/Remove operation can occur automatically when you Create/Edit groups in the Group Admin UI.

When you Add/Remove devices in the Membership page and refresh the browser, the next device will also be added or removed.

Workaround:

None. Repeat the Add/Remove operation.

CSCsa43873

In LMS 2.5, groups are copied in backup-restore from Master to Master.

Additional shared groups appear after you backup or restore from a Master of one domain to a Master of another domain.

This problem appears only where a common Slave exists for two different Masters.

For example:

There are two DCR domains, M1 with Slaves S11 and S12, and M2 with slaves S21 and S22.

If you restore after you take a backup in M1 and make S12 a slave of M2, S12 will become the common slave of M1's backup and M2.

The groups of M1 and S11 remain in M2 instead of being removed.

Workaround:

1. Change the mode of Master to Standalone. This will remove all the remote shared groups (groups from other machines) in M2's DCR domain.

2. Reconfigure the Master/Slave in DCR UI.


General Known Problems

Table 11 describes the miscellaneous known problems associated with Common Services (not specific to any module in Common Services).

Table 11 General Known Problems 

Bug ID
Summary
Explanation

CSCsi66749

Device authorization fails in ACS mode though the devices are displayed in DCR Administration and in application pages.

When CiscoWorks is in ACS mode, device authorization fails for some of the IP addresses of devices.

This happens when you enter multiple IP addresses of devices with the total length exceeding 4096 characters, during AAA client configuration in ACS.

This is because ACS does not support more than 4096 characters in the IP Address field for a AAA client configuration.

Device authorization fails for devices whose IP addresses are entered after the 4096th character.

Workaround:

Add multiple IP Addresses with the total length not exceeding 4096 characters.

CSCsi87682

Cannot launch LMS 3.0 on Internet Explorer 6.x after LMS 3.0 is installed.

When LMS 3.0 is uninstalled and then installed again on an LMS configured server using Internet Explorer 6.x, the product does not launch.

Workaround:

In Internet Explorer 6.x, enable the Use TLS1.0 option in Tools > Internet Options > Advanced > Security.

CSCsh24651

Improper connection to database caused by no disk space leads to indefinite waiting.

When there is no free space available in the NMSROOT drive, the database server will be slow as it performs operations on the temporary files created by Sybase.

Workaround:

Restart Daemon Manager after freeing up some disk space.

CSCsg84927

Error or warning messages opens in a new tab.

Any notification window (error or a warning message) opens in a new tab instead of a new window.

Workaround:

Launch the application links using <a href=[url]/>.

CSCsg84924

In Firefox 2.0, any link opens in a new tab instead of a new page.

If you select an item from the Table of Contents items for an application in the CiscoWorks page, it opens in a new tab instead of a new page.

Workaround:

Use Options > Tabs > Open in a new window, to activate this option.

CSCsg84938

In Firefox 2.0, the minimise button should be disabled for all notification windows.

A notification window that requires an action from you, must not have an optin to minimize it. However, such an option is available in Firefox 2.0.

Workaround:

None.

CSCsg76593

Some popup windows are seen with address bar.

If you launch some screens in IE 7.0 using Firefox 2.0, an address bar appears. This should not appear in any of the popup screens as the contents of the popup may not been shown correctly beacuse of this.

Workaround:

See the Supported Version link in the login page.

CSCse01118

Registration of any application from a remote server fails.

If you add a remote server's certificate in the peer server certificate setup, the registration fails and an error message appears.

Workaround:

None.

CSCsa63026

Page not found error appears when installing new device packages.

When adding new device packages through RME > Software Center > Device Update, the Daemon Manager script, dmgtd restarts.

The browser attempts to access a URL on the server but the page does not load because dmgtd has restarted. Instead, it displays a Page Not Found error.

Workaround:

None.

CSCsh27565

When Syslog is more than 4 GB, the crmlog service does not start.

During start-up when the crmlog process loads the syslog.log for writing, if the file is more than 4GB, the file loading fails.

Workaround:

The syslog needs to cleared or rotated when it is more than 4 GB.

CSCsg76235

Portlets do not appear if you launch the server before some application is registered.

This problem occurs when the Portal engine is not started and ready. However, Tomcat and other deamons are started.

When Tomcat or the deamons are restarted, the application will get registered with the portal engine and if you try to launch the server before this then the application will not appear.

Workaround:

Wait for sometime and the portlets will appear.

CSCsi52867

Cannot access some portlets until you refresh the screen.

Some portlets display messages such as
You do not have the required role to access this portlet
although you may have System Administrator privileges.

This problem could occur when you have opened multiple sessions.

Workaround:

Refresh the screen to view the details.

CSCsg54946

If you configure mail.yahoo.com or http:// in IFrame and click Back, it launches in a full window.

After configuring the URL, if you click Back, the screen occupies the entire window.

Workaround:

Use the following URL to remove all the IFrame portlets in the view protocol://servername:portno/cwportal/c/portal/RemoveIFrame.

CSCsh94522

Portlet menu options may not appear correctly

In this case even if the portlets appear, the submenu options may not appear.

This can occur if the browser's cache has stale data for the server in question.

Since the portal web pages do not specify any caching pragmas, the browsers will cache the content.

Workaround:

Clear the browser cache.

CSCsi96540

Some portlets are missing in Functional view after Remote Migration.

After you migrate, some portlets do not appear in the Functional View.

For instance, if you have installed an application, some portlets will not appear in the Functional View.

Workaround:

Unregister the missing application and re-register the application.

To re-register the application do the following:

Go to CS > Server> Home page Admin >Application Register > Register.

CSCsh79993

After applying the Microsoft Hotfix for MS06-040, Java applications that requires large memory (e.g. the Tomcat VM) does not start.

When running the Java command manually, the following error appears:

Error occurred during the initialization of VM
Could not reserve enough space for the object heap

Workaround:

Ensure to use the fix available in www.microsoft.com to solve the memory reservation problem and then run the Java command.

CSCdy46071

Port availability and port occupancy are not checked properly.

If you access the URL
http://hostname:1741 through browser, it launches local web application, instead of CiscoWorks.

This occurs when another webserver is using the port 1741.

Workaround:

Modify the settings of the other webserver to use a different port or uninstall the other webserver.

CSCdz55483

Many processes terminate soon after you start Daemon Manager.

Several processes terminate soon after you start Daemon Manager on a machine that has dual boot configurations, with options of Windows Professional and Windows Server.

Workaround:

None.

CSCec82508

When multiple community string support is enabled on Campus Manager, the devices may become unreachable in the topology.

This is caused by the way IOS responds when it has a community defined with no view for it.

Workarounds:

If a separate community string is used for traps from RO/RW communities, then manually add the trap community to the config with an ACL to deny all.

Use the same community strings for traps already configured in the router for RO access.

Do not include the trap community string in the list for multiple community strings in Campus Manager.

CSCin07838

Cannot invoke CiscoWorks if you start Daemon Manager immediately.

Cannot invoke CiscoWorks if you stop the Daemon Manager and restart it immediately.

Workaround:

Do not restart the Daemon Manager immediately after stopping it. You must wait for some time for the ports to be released.

CSCin16992

EDS displays errors when you change the hostname.

The errors appear if you change the hostname without restarting the daemons.

Workaround:

See the following link:

http://cisco.com/en/US/products/sw/cscowork/ps3996/products_user_guide_list.html

CSCin22086

JRM does not schedule jobs properly when you change the system time manually.

JRM time does not reset when you change the system time manually.

Workaround:

Restart Daemon Manager. To do this:

1. Stop the Daemon Manager by entering:

net stop crmdmgtd

2. Start the Daemon Manager by entering:

net start crmdmgtd

CSCin41971

Authentication from NMS fails for valid users.

This problem occurs when:

CWCS is installed in a multi-homed device.

ACS/TACACS+ server is configured as login module (through Pluggable Authentication Modules).

The primary IP address of the NMS is not configured as a client in ACS.

Workaround:

Configure the primary IP address of the NMS as a client in ACS.

CSCin59328

CatOS returns the engine parameters only when you initiate two requests.

CatOS returns the SNMP engine ID, boots, and time values only when you initiate two requests.

Workaround:

None.

CSCin63973

CRMLogger loses Syslog messages from the device.

This error occurs when debug is enabled or the system is under heavy load.

Workaround:

Disable debug from registry and restart CRMLogger.

CSCsa03531

When you restore CS 2.1 data an error message appears.

The following error appears:

Unable to copy from backup archive folder to 
temporary folder.

This occurs under the following conditions:

When you restore from CS 2.1.

If you do not apply the patch CSCdy52905 before taking backup.

Workaround:

Either:

Before taking a backup, apply the patch CSCdy52905.

Or

Manually add permissions to the required backup archive files as below:

a. Open Windows Explorer.

b. Right click the generation folder (c:\backup-real\cmf21\0) and select Properties.

c. Click the Security tab.

d. Select or deselect the Allow/Deny boxes so that you have permission to read.

e. Click the Advanced button.

f. Enable the Reset permissions on all child objects check boxes.

g. Click Apply.

h. Click OK.

The restore will now work.

CSCsa04022

Cannot access CiscoWorks Server when you restart DaemonManager.

When you restart DaemonManager, all the processes take some time to come up. This causes a delay in accessing the CiscoWorks Server.

Workaround:

Wait for a few minutes. Now run the process status command pdshow.

CSCsa04366

If you send two SNMP queries when there is congestion, the response for the second request fails.

This occurs when the device is flooded with heavy traffic or when it is busy.

Workaround:

None.

CSCsa04368

Automatic backup fails when you upgrade from CS 2.1 or CS 2.2 to CS 3.0. This occurs if you cancel the previous attempt to upgrade during the backup.

This occurs only during upgrade.

Workaround:

If there is a proper backup for the first install, there is no need to backup in the second install. You can restore from the successful backup taken earlier.

or

If the backup is not taken during first install or if the backup fails during first install, you can restore from the previous backups.

CSCsa06695

CS 3.0 CRMLogger will not dynamically detect the log File name change as CS 2.2.

Some registry keys are not picked up dynamically.

Workaround:

Restart CRMLogger if the log file name is changed.

CSCsa24921

Packet Capture status displays wrong messages if the Packet Capture time is short.

When device IP is not reachable, the Packet Capture status window displays wrong messages. This occurs if Packet Capture time is short.

Workaround:

Perform Packet Capture for a longer time.

CSCsa25128

CRMLogger loses messages when it receives 1000 or more Syslog messages in milliseconds.

CRMLogger can collect 1000 messages in a second that are coming during a time span of 1 second.

When 1000 Syslogs are pumped in a millisecond with maximum length, CRMLogger is unable to receive all of them.

Workaround:

None.

If 1000 or more messages are received in milliseconds, there is no workaround.

CSCsa26875

Error messages appear when you stop jobs.

When you stop jobs before their completion, some error messages appear such as:

Cannot stop job 1064.14.

The problem occurs when the you try to stop the job just milliseconds before the job completes.

Workaround:

Stop the job again to see the proper error message.

CSCsa29023

If you enter wrong SNMPv3 credentials when Multiple Community String (MCS) is enabled, SNMPv1/v2 credentials are not taken into consideration.

Multiple community string is not applicable only to SNMPv3. This is available only for SNMPv1/v2.

Workaround:

None.

CSCsa34882

Ethereal or Windump show two SNMP packets in the trace when only one packet is sent out.

This occurs when the following interfaces are found:

Broadcom NetXtreme Gigabit Ethernet for hp.

Broadcom NetXtreme Gigabit Ethernet for hp Deterministic Network Enhancer Miniport.

These interfaces are listed as two interfaces although it is one interface.

Workaround:

None.

CSCsa83440

Cannot resize the columns in HTML scrolling tables.

This is the UI behavior.

Workaround:

Place the cursor on top of the text (do not click). The entire text in the column appears.

CSCsb54879

The format in which the document appears after PDF export in a report is improper.

When you export data to a PDF filein a report, the following inconsistencies appear:

If the last row in a table appears on a new page, the table header does not appear for that row.

In some of the tables, even if there is enough blank space on a page, only the table header appears. The body rows do not appear.

In some of the tables, the table header appears twice on the same page.

Workaround:

None.

CSCsb71591

Application links appear after upgrading to CS 3.0.3 from CS 3.0.

Applications are not disabled during an upgrade from CS 3.0 to a higher version. So, application links appear.

Workaround:

Upgrade all applications to the latest available version for proper functionality.

CSCsc19929

Error appears:

"dbmonitor.exe-Application Error" "-The application failed to initialize properly."

This will happen if the customer has installed any ActivePerl after the LMS installation.

Workaround:

Manually remove the ActivePerl paths from the PATH Environment variable and reboot the machine.

CSCsc24337

RME uses the send mail application interface of CS for sending mails.

All RME jobs fail with a message
Unable to Send Mail.

This happens because the port (25) is blocked.

Workaround:

Set the option given below:

Start > Network Associates > VirusScan Console > Access Protection > Uncheck the Prevent Mass Mailing Worm From Sending Mail checkbox.

CSCsd21327

CMF database does not run and displays the following Sybase Assertion error message:

*** ERROR *** Assertion failed: 
100909 (9.0.0.1383). 

100909 is the Assertion ID.

The following are the scenarios where Assertion Error might appear:

1. If you use any third-party backup software to back up a live, running database, the Assertion Error might be thrown.

This is because some of the database pages that have been modified will be in the database server cache, so the database file will be in an inconsistent state.

2. If you use any anti-virus software.

This is because Adaptive Server Anywhere performs many reads and writes other than the normal I/O operations, which contribute to the good performance of Adaptive Server Anywhere.

However, anti-virus software might detect this as a potential problem and quarantine the file. This becomes hazardous if the .log or temporary files are quarantined, and it may cause corruption by interfering with the normal functions of the database.

Poor performance can also occur if the anti-virus software is checking all I/O operations performed by the database server.

Workaround:

We recommend that you do not use third-party backup software for backing up a running database.

We also recommend that you configure your anti-virus software so that it must not scan the NMSROOT/databases directory.

NMSROOT is the directory where you have installed CiscoWorks.

CSCsd79317

PSU screens in the Summary window allow you to edit values while installing device packages.

The Summary window allows you to right-click and select the window contents for cut, paste, and delete operations after you select the products for which you want to check for device updates.

Workaround:

Use Mozilla or Netscape family of browser.

CSCea63903

On a Windows 2000 server, Tacac+ security login module did not prompt password expiry.

This login module did not recognize to prompt for a new password that is valid for only 90 days.

Workaround:

None.


Internally-Found Resolved Problems

Table 12 lists the problems that were found internally and have been resolved since the last release of Common Services.

Table 12 Internally-Found Resolved Problems 

Bug ID
Summary
Additional Information

CSCsc02058

You could not see the contents using the Dual Column Selector in the Internet Explorer, if you had to scroll down.

This problem has been resolved.

CSCsd50385

The Selector component did not display names clearly when the name was very long.

This problem has been resolved.

CSCsa03531

When you restored CS 2.1 data, an error message appeared.

This problem has been resolved.

CSCsa37988

In DCR, the IP address field accepted broadcast and multicast address.

This problem has been resolved.

CSCsa43396

DSBU cluster did not retain parent-child relationship if there was a duplicate device.

This problem has been resolved.

CSCsa45024

Deleting a large number of devices in the DCR GUI took a long time.

This problem has been resolved.

CSCsb87463

Installation of a Device Package did not succeed. A message appears,
Base package check failed.
although the base package was available in the source location.

This problem has been resolved.

CSCsb90144

Importing devices from ACS failed, if the ACS server HTTPS protocol entered in AAA mode setup was different from the ACS server used for import.

This problem has been resolved.

CSCsc30244

Dll files lock error occurred during reinstall or upgrade.

This problem has been resolved.

CSCsc43429

PSU adapter package did not get installed.

This problem has been resolved.

CSCsc66462

The Event Log displayed device package install failure as an error, without giving the exact cause.

This problem has been resolved.

CSCsc69758

Changing login mode to Non-ACS Pluggable Authentication Modules (PAM) after restore from CS 3.0 displayed Internal Server Error.

This problem has been resolved.

CSCsc71272

Internal server error appeared when re-registering applications with ACS when AAA Mode was ACS.

This problem has been resolved.

CSCsf13735

Some buttons displayed in CiscoWorks resized when you moved your mouse over them.

This problem has been resolved.

CSCef86829

In DCR, Export from File took longer time than Export from Device Selector.

This problem has been resolved.

CSCsa30660

Deleting a large number of devices in the Master took a long time.

This problem has been resolved.

CSCsc71565

In CS 3.0, while registering a Test Application, the wrong port number was used.

When you upgraded to CS 3.0.3, the Test Application had not appeared under the registered applications.

This problem has been resolved.

CSCse90398

Extra gray spaces appeared in some application screens (for example SWIM workflows), if the number of rows in a table was less than 10.

This problem has been resolved.


Customer-Found Resolved Problems

Table 13 lists the customer-found problems that have been fixed since the last release of Common Services.

Table 13 Customer-Found Resolved Problems 

Bug ID
Summary
Additional Information

CSCsa66596

Information on how to change the hostname or IP address of the CiscoWorks Server was incorrect in the CiscoWorks Common Services 2.2 User Guide.

This problem has been resolved.

CSCsa86468

When you generated the Detailed Device Inventory report using the Report Generator of RME and exported the generated report to a PDF file, some of the tabular output was unreadable.

This problem has been resolved.

CSCsa98068

E-mail option was not available for configuration in a device export job.

This problem has been resolved.

CSCsb16407

Since creating groups based on SystemLocation and SystemContact was case-sensitive in Campus Manager, groups configured with a combination of uppercase and lowercase names became invalid.

This problem has been resolved.

CSCsb62366

In CS 3.0, if you entered only the filename and did not specify the complete path when you exported device credentials from DCR to a file, the export file was not saved in the intended directory.

This problem has been resolved.

CSCsc61067

In CS 3.0.2, when you selected or downloaded updates from Software Center, the list of available Software Updates for a selected product took a long time to appear.

This occurred regardless of the application or the number of applications you selected.

This problem has been resolved.

CSCin33739

Installation proceeded with errors and applications became inaccessible after installing CiscoWorks.

This problem has been resolved.

CSCsc94079

The value of the CrmDnsResolution registry key could not be modified, using either CLI or GUI.

This problem has been resolved.

CSCsd65784

Export using CLI failed in a busy network when the response from ACS server was slower than that expected by the CiscoWorks Server.

This problem has been resolved.

CSCsd72563

When you created a new User Defined Group, CS allowed you to choose a parent group that the user had no access to.

This problem has been resolved.

CSCsd84314

An error message was displayed when you saved the SMTP server name from the System Preferences dialog box.

This problem has been resolved.

CSCsd91126

The jobs requiring TFTP might have failed because the TFTP (Trivial File Transfer Protocol) daemon shipped by CiscoWorks Common Services supported TCP (Transmission Control Protocol) Wrappers.

This problem has been resolved.

CSCsd97403

In CS 3.0.4, an error message was displayed when you scheduled a DCR import job for importing devices in bulk mode using Local NMS and Remote NMS options using the DCA interface.

This problem has been resolved.

CSCse06918

When you selected multiple devices in DCR to edit common credentials, it was difficult to determine whether the changes occurred for all selected devices.

This problem has been resolved.

CSCse07757

The verification message displayed when you installed any of the LMS applications needed to be modified.

This problem has been resolved.

CSCse27951

The Activity Log page did not appear when the name of the product was null.

This problem has been resolved.

CSCse42607

CiscoWorks granted access to users when the Radius server was configured to reply with Access-Challenge. This happened even if the password field was left blank.

This problem has been resolved.

CSCse46363

When you sorted the Event Log page by date, the entries spanning over months did not appear in the correct chronological order.

This problem has been resolved.

CSCse52206

The rules on CiscoWorks usernames and passwords did not allow uniform usernames to be configured across the different enterprise elements, such as Active Directory, ACS, and so on.

This problem has been resolved.

CSCse54091

From the Software Updates page, when you clicked the product name links to view the Applications and Packages Installed with the Product page, Internal Server Error appeared.

This problem has been resolved.

CSCse56727

Internal Server Error appeared when you launched the Software Updates page if Network Management Integration Module (NMIM) was installed.

This problem has been resolved.

CSCse64662

In SNMP Peer Manager, if an SNMP engine ID for a peer was configured with an improper length or an improper ID sequence, an exception occured.

Any SNMP operation hung because the SNMP library queried the device with an invalid IP address.

This problem has been resolved.

CSCse75855

Adding device IP address and username using the crmrsh addrhost command failed for casusers.

This problem has been resolved.

CSCea20284

Scheduled Backup failed.

This problem has been resolved.

CSCsb97406

Could not launch the Cisco Works screen
(e.g http://server_name:1741).

This problem has been resolved.


Obtaining Documentation, Obtaining Support, and Security Guidelines

For information on obtaining documentation, obtaining support, providing documentation feedback, security guidelines, and also recommended aliases and general Cisco documents, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:

http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html

Open Source License Acknowledgements

The following acknowledgements pertain to this software license.

OpenSSL/Open SSL Project

This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/).

This product includes cryptographic software written by Eric Young (eay@cryptsoft.com).

This product includes software written by Tim Hudson (tjh@cryptsoft.com).

License Issues

The OpenSSL toolkit stays under a dual license, i.e. both the conditions of the OpenSSL License and the original SSLeay license apply to the toolkit. See below for the actual license texts. Actually both licenses are BSD-style Open Source licenses. In case of any license issues related to OpenSSL please contact openssl-core@openssl.org.

OpenSSL License:

© 1998-1999 The OpenSSL Project. All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

1. Redistributions of source code must retain the copyright notice, this list of conditions and the following disclaimer.

2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions, and the following disclaimer in the documentation and/or other materials provided with the distribution.

3. All advertising materials mentioning features or use of this software must display the following acknowledgment: "This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit. (http://www.openssl.org/)"

4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact openssl-core@openssl.org.

5. Products derived from this software may not be called "OpenSSL" nor may "OpenSSL" appear in their names without prior written permission of the OpenSSL Project.

6. Redistributions of any form whatsoever must retain the following acknowledgment:

"This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/)"

THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT "AS IS"' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECT OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

This product includes cryptographic software written by Eric Young (eay@cryptsoft.com). This product includes software written by Tim Hudson (tjh@cryptsoft.com).

Original SSLeay License:

© 1995-1998 Eric Young (eay@cryptsoft.com). All rights reserved.

This package is an SSL implementation written by Eric Young (eay@cryptsoft.com).

The implementation was written so as to conform with Netscapes SSL.

This library is free for commercial and non-commercial use as long as the following conditions are adhered to. The following conditions apply to all code found in this distribution, be it the RC4, RSA, lhash, DES, etc., code; not just the SSL code. The SSL documentation included with this distribution is covered by the same copyright terms except that the holder is Tim Hudson (tjh@cryptsoft.com).

Copyright remains Eric Young's, and as such any Copyright notices in the code are not to be removed. If this package is used in a product, Eric Young should be given attribution as the author of the parts of the library used. This can be in the form of a textual message at program startup or in documentation (online or textual) provided with the package.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

1. Redistributions of source code must retain the copyright notice, this list of conditions and the following disclaimer.

2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.

3. All advertising materials mentioning features or use of this software must display the following acknowledgement:

"This product includes cryptographic software written by Eric Young (eay@cryptsoft.com)".

The word `cryptographic' can be left out if the routines from the library being used are not cryptography-related.

4. If you include any Windows specific code (or a derivative thereof) from the apps directory (application code) you must include an acknowledgement: "This product includes software written by Tim Hudson (tjh@cryptsoft.com)".

THIS SOFTWARE IS PROVIDED BY ERIC YOUNG "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

The license and distribution terms for any publicly available version or derivative of this code cannot be changed. i.e. this code cannot simply be copied and put under another distribution license [including the GNU Public License].