Table Of Contents
Release Notes for CiscoWorks Common Services 3.0.5 (Includes CiscoView 6.1.5) on Windows
New Features
Product Documentation
Time Zone Acronyms and Offset Settings
Multi-homed Machines
Operating System Upgrade
Support Information
Server Requirements
Client Requirements
Enabling Java Console
Integrating with Third-party Vendors
Using CiscoView in ACS Mode
CiscoWorks Roles and Privileges
Modifying the CiscoWorks Roles and Privileges
Device-Based Filtering
Known and Resolved Problems
Installation Known Problems
CiscoWorks Homepage 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
CiscoView Known Problems
Known Problems in CiscoView Mini-RMON Manager 2.3
CiscoView Resolved Problems
Internally-Found Resolved Problems
Customer-Found Resolved Problems
Obtaining Documentation
Cisco.com
Product Documentation DVD
Ordering Documentation
Documentation Feedback
Cisco Product Security Overview
Reporting Security Problems in Cisco Products
Product Alerts and Field Notices
Obtaining Technical Assistance
Cisco Technical Support & Documentation Website
Submitting a Service Request
Definitions of Service Request Severity
Obtaining Additional Publications and Information
Open Source License Acknowledgements
OpenSSL/Open SSL Project
License Issues
Release Notes for CiscoWorks Common Services 3.0.5 (Includes CiscoView 6.1.5) on Windows
This release note is for CiscoWorks Common Services 3.0.5 running on a Windows platform.
The release note contains the following sections:
•
New Features
•Product Documentation
•Time Zone Acronyms and Offset Settings
•Multi-homed Machines
•Operating System Upgrade
•Support Information
•Integrating with Third-party Vendors
•Using CiscoView in ACS Mode
•Known and Resolved Problems
•Obtaining Technical Assistance
•Obtaining Additional Publications and Information
•Open Source License Acknowledgements
New Features
The new features in CiscoWorks Common Services Release 3.0.5 are:
•Improved Device Selector with the following features:
–Support for search and advanced search capabilities
–The existing tree view in the device selector (which shows the application based grouping view such as CS@.., RME@...,) changed to a more usable and consistent tree view
–Group Customization and Group Ordering options provided through Device Selector settings
–Enhanced tooltip over devices
•Common Services Home provides:
–Summary on status of recent jobs, backup, and current settings such as AAA mode, DCA mode, and SSO
–Quick links to frequently used features
•LMS Setup Center
Helps you complete the basic system setup for CS and the other LMS applications. The basic system setup consists of Security settings, Cisco.com Account, Proxy, and SMTP settings followed by application specific settings in a flow.
The Setup Center is enabled for LMS only and not for non-LMS bundles. CS provides the framework for Setup Center to the other LMS applications
•Improved performance in listing of available devices or software packages in Software Center.
•Support for MDF 1.12.
Meta Data Framework (MDF) Package defines device types in a uniform way across CiscoWorks applications. MDF Package allows you to add new device types to the existing set of device types defined in CiscoWorks Common Services 3.0.
The MDF package 1.12 is a cumulative package that includes the new device types added after the release of CiscoWorks Common Services 3.0 as well as those defined in Common Services 3.0 and till MDF package version 1.10.
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 1.12 contains the following new device types:
–Cisco SFS 3012 Multifabric Server Switch (1.3.6.1.4.1.6203.3)
–Cisco SFS 7008 InfiniBand Server Switch (1.3.6.1.4.1.6203.18)
–Cisco SFS 7000 InfiniBand Server Switch (1.3.6.1.4.1.6203.17)
–Catalyst Blade Switch 3020 for HP (1.3.6.1.4.1.9.1.748)
–Cisco Catalyst 2960G-48TC Switch (1.3.6.1.4.1.9.1.697)
–Cisco Catalyst 6504-E Switch (1.3.6.1.4.1.9.5.64)
–Cisco Intelligent Gigabit Ethernet Switch Module (1.3.6.1.4.1.9.1.660)
–CiscoWorks 1133 for Wireless LAN Solution Engine (1.3.6.1.4.1.9.1.752)
–Cisco Aironet 1240 AG Access Point (1.3.6.1.4.1.9.1.685)
–Cisco ASA-5505 Adaptive Security Appliance (1.3.6.1.4.1.9.1.745)
Adding new device types through MDF Package 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.0 features see:
http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_common_services_software/3.0/user/guide/overview.html#wp1060149
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.
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 1 of Installation and Setup Guide for CiscoWorks Common Services (Includes CiscoView) on Windows.
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.
Support Information
This section gives details on:
•Server Requirements
•Client Requirements
•Enabling Java Console
Server Requirements
Table 3 shows the minimum system requirements for installing Common Services.
Caution Do not use non-standard Java options through JAVA_OPTIONS environment variable.
Table 3 Server System Requirements1
Requirement Type
|
Minimum Requirements
|
System hardware
|
•IBM PC-compatible system with 1 GHz or faster Pentium processor.
•Color monitor.
•CD-ROM drive.
|
Memory (RAM)
|
512 MB (to install all CiscoWorks Common Services components).
|
Available drive space2
|
•2 GB.
•Paging file space equal to double the amount of memory (RAM). For example, if your system has 512 MB of RAM, you need 1024 MB of page file.
•NTFS file system required for secure operation.
•At least 16 MB in Windows temporary directory (%TEMP%).
|
System software3
|
•ODBC Driver Manager 3.510 or later (in 3.5x).
•Any of the following:
–Windows 2000 Professional with SP3 or SP4.
–Windows 2000 Server with SP3 or SP4.
–Windows 2000 Advanced Server with SP3 and SP4.
–Windows 2003 Server Standard and Enterprise Editions.
–Windows 2003 Server Standard and Enterprise Editions with SP1.
–Windows 2003 Server Standard and Enterprise Editions with SP2.
–Windows 2003 R2 Server Standard and Enterprise Editions.
–Windows 2003 R2 Server Standard and Enterprise Editions with SP2.
Common Services 3.0.5 supports only US-English and Japanese versions of Windows Operating Systems. It does not support any other language version. Installation might proceed normally in other locales but there might be problems in the functionality of CiscoWorks.
|
Additional software
(Optional)
Browsers
|
•Microsoft Internet Explorer 6.0.26 and Microsoft Internet Explorer 6.0.28.
•Java Virtual Machine (JVM) 5.0.0.3802 and later, and Java Plug-in version 1.4.2_08.
To verify JVM:
–From Internet Explorer, select Tools > Sun Java Console.
CiscoWorks Common Services does not require JVM and Java Plug-in. However, some CiscoWorks applications may require these.
•Netscape Navigator 7.2.
•Mozilla 1.7.5.
|
Client Requirements
The minimum system requirements for the client are shown in Table 4.
Table 4 Client System Requirements
Requirement Type
|
Minimum Requirements
|
System hardware and software
|
Client system:
•IBM PC-compatible system with at least a 300 MHz Pentium processor running any of these:
–Windows 2000 Professional with Service Pack 3 or Service Pack 4
–Windows 2000 Advanced Server with Service Pack 3 or Service Pack 4
–Windows XP SP1
–Windows XP SP2
–Windows 2003 Server and Enterprise Edition
–Windows 2003 Server and Enterprise Edition with Service Pack 1
–Windows 2003 R2 server (standard and enterprise versions)
•UltraSPARC 10 running Solaris 8 or Solaris 9.
Color monitor with video card set to 256 colors.
|
Memory (RAM)
|
256 MB.
|
Browser
|
One of these browsers:
On Windows and Windows XP clients:
•Microsoft Internet Explorer 6.0 (version 6.0.2600)
•Internet Explorer 6.0 with Service Pack 1 (version 6.0.2800) for Windows 2000 and Windows XP
•Internet Explorer 6.0.3790.0 for Windows 2003 Server and Windows 2003 Server with Service Pack 1
•Internet Explorer 6.0 with Service Pack 2 (version 6.0.29) supported on Windows XP
•Internet Explorer 6.0 with Service Pack 2 (version 6.0.2900) for Windows XP
•Internet Explorer 6.0 with Service Pack 1 (version 6.0.3790.1830) for Windows 2003 R2
•Java Virtual Machine (JVM) 5.0.0.3802 and later, and Java Plug-in version 1.4.2_10.(optional)1
To verify the JVM:
–From Internet Explorer, select Tools > Sun Java Console.
–From Netscape Navigator, select Tools > Web Development >
Java Console.
–From Mozilla, select Tools > Web Development > Java Console.
CiscoWorks Common Services does not require JVM and Java Plug-in. However, some CiscoWorks applications may require these.
•Netscape Navigator 7.1 and Netscape Navigator 7.2
•Mozilla 1.7.5
On Solaris clients:
•Netscape Navigator 7.0 for Solaris 8 and Solaris 9
•Mozilla 1.7.5 for Solaris 8 and Solaris 9
|
Enabling Java Console
To enable Java Console in Microsoft Internet Explorer:
Step 1 Select Tools > Internet Options > Advanced.
Step 2 Select Java Console in the Microsoft VM section.
Step 3 Restart Internet Explorer.
To enable Java Console in Netscape Navigator:
Step 1 Select Edit > Preferences > Advanced.
Step 2 Check the Enable Java checkbox.
Step 3 Restart Netscape Navigator.
To enable Java Console in Mozilla:
Step 1 Select Edit > Preferences > Advanced.
Step 2 Check the Enable Java checkbox in the Advanced Preferences window.
Step 3 Restart Mozilla.
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 6.4.
•HP OpenView Network Node Manager 7.0.
•HP OpenView Network Node Manager 7.0.1.
•HP OpenView Network Node Manager 7.0.5.
•NetView 7.1.
This utility allows you to launch CiscoView from an SNMP platform even when CiscoView is running on a different machine than the NMS. It also allows you to integrate other applications into NMS menus.
When CiscoView is installed on the same machine as the target NMS, the Integration Utility runs as part of a single CiscoView install.
However, when the target NMS is installed on a different machine, the utility walks you through the steps required to integrate Cisco device information and applications into an SNMP management platform.
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.6.
Using CiscoView in ACS Mode
Before performing any tasks that are described in this section, you must successfully complete configuring Cisco Secure ACS with the CiscoWorks server. The CiscoView application is registered to Cisco Secure ACS.
CiscoWorks login modules allow you to add new users by using a source of authentication other than the native CiscoWorks server mechanism (that is, the CiscoWorks Local login module). You can use the Cisco Secure ACS services for this purpose.
The following topics provide information on how to use CiscoView in the ACS mode:
•CiscoWorks Roles and Privileges
•Modifying the CiscoWorks Roles and Privileges
•Device-Based Filtering
For more information, see the following documents:
•User Guide for Cisco Secure ACS for Windows Server Version 3.3
See this document to understand Cisco Secure Groups, Users, Command Authorization Sets, etc.
•User Guide for CiscoWorks Common Services 3.0.5
See this document to understand the CiscoWorks login modes.
•User Guide for CiscoView 6.1.5
See this document to understand all CiscoView tasks.
CiscoWorks Roles and Privileges
By default, the CiscoWorks server authentication scheme has the following five roles in ACS mode, listed here from least privileged to most privileged:
•Help Desk
•Approver
•Network Operator
•Network Administrator
•System Administrator
Help Desk
A user with this role has the privilege to access network status information from the persisted data. The user does not have the privilege to contact any device or schedule a job that will reach the network.
Approver
A user with this role has the privilege to approve all CiscoView tasks.
Network Operator
A user with this role has the privilege to perform all tasks that involve collecting data from the network. The user does not have write access on the network. The user can also perform all the Help Desk tasks.
Network Administrator
A user with this role has the privilege to change the network. The user can also perform the Network Operator tasks.
System Administrator
A user with this role has the privilege to perform all CiscoWorks system administration tasks. See the Permissions Report on the CiscoWorks server (Common Services > Server > Reports > Permission Report).
Cisco Secure ACS allows you to modify the privileges to these roles. You can also create custom roles and privileges that help you customize Common Services client applications to best suit your business workflow and needs.
•To modify the default CiscoWorks roles and privileges, see Modifying the CiscoWorks Roles and Privileges.
•To create the custom roles and privileges, see Cisco Secure ACS Online help (on Cisco Secure ACS, click Online Documentation > Shared Profile Components > Command Authorization Sets).
Modifying the CiscoWorks Roles and Privileges
If another instance of CiscoView is registered with the same Cisco Secure ACS, your instance of CiscoView will inherit those role settings. Furthermore, any changes you make to CiscoView roles will be propagated to other instances of CiscoView through Cisco Secure ACS.
If you reinstall CiscoView, your Cisco Secure ACS settings will automatically be applied upon CiscoView restart.
Step 1 Select Shared Profile Components > CiscoView and click the CiscoView roles that you want to modify.
Step 2 Specify whether the roles have read-only or read-write privileges.
Step 3 Click Submit.
Device-Based Filtering
Most of the CiscoView tasks are device-centric. The devices listed for you while performing the CiscoView tasks, are based on your role and the associated privileges that are defined in Cisco Secure ACS.
Known and Resolved Problems
Tables 5 to 13 describe the problems known to exist in this release; Tables 17 and 18 describe the problems resolved from Common Services 3.0 onwards.
Note To obtain more information about known problems, access the Cisco Software Bug Toolkit at http://www.cisco.com/pcgi-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 Homepage 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
•CiscoView Known Problems
•Known Problems in CiscoView Mini-RMON Manager 2.3
•CiscoView Resolved Problems
•Internally-Found Resolved Problems
•Customer-Found Resolved Problems
Installation Known Problems
Table 5 describes the known problems related to the installation of Common Services.
Table 5 Installation Known Problems
Bug ID
|
Summary
|
Explanation
|
CSCds90562
|
Daemon Manager fails to run if CiscoWorks home directory is encrypted.
|
CiscoWorks does not support encrypted directories.
Workaround:
None. Do not install CiscoWorks in an encrypted directory.
|
CSCdt32795
|
CiscoWorks malfunctions if operating system is upgraded after installation.
|
CiscoWorks processes do not start normally after Operating System upgrade.
Workaround:
See the "Operating System Upgrade" section.
|
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 errors 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
|
CSCin33739
|
Installation proceeds with errors and applications become inaccessible after installing CiscoWorks.
|
CiscoWorks installation displays the following error messages:
The ordinal 2821 could not be located in
the dynamic link library LIBEAY32.dll
or
The ordinal 2821 could not be located in
the dynamic link library SSLEAY32.dll
After installation, some applications are
not accessible.
Workaround:
1. Backup the following dlls:
–System32\ssleay32.dll
–System32\libeay32.dll
2. Delete these dlls from the System32 directory.
3. Uninstall the current copy of CiscoWorks that is causing the problem and reinstall it.
|
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.
|
CSCsa04369
|
LIBEAY32.dll and SSLEAY32.dll not found errors occur when you try to upgrade after aborting the previous upgrade attempt.
|
The error occurs during the second attempt to ugrade from CiscoWorks Common Services 2.2 to CiscoWorks Common Services 3.0 after you abort the first attempt.
Workaround:
1. If the upgrade fails the first time, clean up the system.
2. Re-install Common Services 3.0.3.
3. Restore the data which was backed up during the failed upgrade.
|
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 4GB (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 4GB on your hard disk.
|
CSCsb80789
|
LMS 2.5 based applications and SPs must not co-exist with LMS 2.5.1 applications, basically CS 3.0.3.
|
Consider the following scenario:
You have LMS 2.5 Bundle and LMS 2.5 Mega patch.
If you install DFM 2.0, you must reinstall LMS 2.5 Mega Patch or install LMS 2.5 Megapatch only for the DFM Updates.
Also, if you have LMS 2.5 Bundle and you install any LMS 2.5.1 application over this, you must install all the other applications of LMS 2.5.1 also.
You should use either LMS 2.5 applications or LMS 2.5.1 applications.
Do not use a combination of LMS 2.5 and LMS 2.5.1 applications.
Workaround:
Do not install LMS 2.5 application over LMS 2.5.1.
If you install LMS 2.5 application over LMS 2.5.1 you must reinstall the related LMS 2.5.1 application.
|
CSCsb87221
|
Uninstall hangs with a message that the system cannot find the file specified.
|
The CPU is full and it does not have memory to load the uninstall GUI.
Workaround:
Close the uninstallation, stop the process that is occupying the memory and try uninstalling. Rebooting the system will also work.
|
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. You must 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.
|
CSCsc69299
|
Automatic backup fails while upgrading from CS 3.0 to CS 3.0.3.
Normal backup will not create the tar archive with the backup files. It displays an error:
Cannot stat: No such file or
directory.
|
This occurs if the customer has installed the third-party OpenSSH for Windows.
The reason is that cygiconv-2.dll and cygwin1.dll are required for the OpenSSH as well.
Since the third party DLLs are loaded into the memory during startup, the tar cannot load its own version of DLLs while creating tar archive.
Workaround:
Uninstall the third-party Open SSH for Windows and continue upgrade (or backup).
|
CSCsc71551
|
During upgrade, after the summary dialog, an error message appears:
NMSROOT\MDC\tomcat\bin\tomca
t.exeAccess is denied
|
During preinstall, when you try to delete the tomcat.exe file, it does not get deleted because of a locking issue.
Workaround:
1. Stop the following windows services:
–Windows Management Instrumentation
–Windows Management Instrumentation Driver Extensions
2. Proceed with the installation.
After the installation completes, reboot the machine. The above services will restart.
|
None.
|
Installing CD One 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.
|
CSCse70497
|
HPOVNetwork Management System (NMS) 7.x and LMS cannot coexist on the same server because of the dependency on Internet Information Services (IIS).
|
If you are using HPOV as your third party NMS application, you would require the IIS service be enabled for HPOV to install and run.
The IIS webserver runs on SSL port 443, which is the default port for LMS webserver.
Since LMS web server and IIS web server conflicting on SSL port 443, Ciscoworks Common Services cannot run on a machine, where IIS is installed and enabled.
Workaround:
The port number conflict between IIS and LMS web servers can be avoided by changing the SSL port number of the LMS web server from 443 to some other available port number.
|
CiscoWorks Homepage Known Problems
Table 6 describes the known problems related to CiscoWorks homepage.
Table 6 CiscoWorks Homepage 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.
|
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 while skipping 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 7 describes the known problems that you might encounter while working with Software Center.
Table 7 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 of 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.
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:
None.
|
CSCsb36651
|
Close button not visible in Scheduled Device Download (immediate) Result pop-up window.
|
This occurs if you have minimized the pop-up progress bar.
In normal flow, the Close button is visible.
Workaround:
None.
|
CSCsc06486
|
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 8 describes the known problems related to the Integration Utility.
Table 8 Integration Utility Known Problems
Bug ID
|
Summary
|
Explanation
|
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 application integration should occur. Instead, 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:
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:
You have already integrated using NMIDB version 1.0.084.
Then 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 9 describes the known problems related to a network management system such as CA-Unicenter.
Table 9 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 -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 10 describes the known problems that you might encounter with web browsers.
Table 10 Browser Known Problems
Bug ID
|
Summary
|
Explanation
|
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 "Support Information" section.
|
CSCef12135
|
Mozilla 1.7 stores session information across separately opened windows.
|
This occurs when the browsers use the same profile name.
Workaround:
Use different profile names for each instance of Netscape.
|
CSCsa09688
|
Software and Device downloads do not work if you block popups in Netscape 7.1.
|
When you block popup windows in Netscape 7.1, you cannot download any Software or Device updates.
Workaround:
Disable the popup block option in the browser.
|
CSCsa20428
|
In Netscape 7.1, a forbidden error message appears when you launch a second Netscape browser with the same CS server.
|
This problem occurs when you:
1. Launch CWHP in a Netscape browser.
2. Launch a second Netscape browser with the same CS server.
The following 403 forbidden error appears:
You don't have permission to access
/cwhp/cwhp.applications.do on this
server.
Workaround:
Do not disable cookies in the browser.
|
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.
|
CSCsb83619
|
Mozilla 1.7.5 displays a warning that the certificate is invalid and that it clashes with the certificate of another server when attempting to perform any operation in CiscoWorks.
|
This happens only when Mozilla 1.7.5 browser is used to launch CiscoWorks.
Workaround:
1. Check if the CiscoWorks server certificate is installed in browser from Edit > Preferences > Privacy & Security > Certificates.
If so, delete the certificate.
2. Clear the browser cache from Edit > Preferences > Advanced > Cache > Clear cache.
3. Restart Mozilla.
|
CSCsb84743
|
Blank white space appears at the bottom of some popup screens in Netscape/Mozilla browsers.
|
This happens when CiscoWorks is launched using Netscape/Mozilla browsers for pop up screens such as CS > Software Center > Device Update > Click on installed products link.
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.
|
CSCsf13735
|
Some buttons displayed in CiscoWorks resize when you move your mouse over them.
|
This happens when the browser cache has some older files.
Workaround:
Clear the browser cache and then invoke CiscoWorks session.
You will get the following warning message to clear the browser cache:
Clear the browser cache and invoke a new session. Otherwise, the buttons may not be displayed properly.
|
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 11 describes the known problems that you might encounter while working with DCR.
Table 11 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.
|
CSCef86829
|
In DCR, Export from File takes longer time than Export from Device Selector.
|
This problem occurs when you try to export many devices using the Export from File option. The time taken to export increases exponentially.
For example, for 5000 devices, it takes 20 minutes and for 10000 devices, it takes 60 minutes.
Workaround:
Use the Export from Device Selector option.
|
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.
|
CSCsa30660
|
Deleting a large number of devices in the Master takes a long time.
|
This occurs when you configure a Master with many Slaves, and delete a large number of devices. The changes appear after some delay.
Workaround:
Do not delete large number of devices at a time in the DCR Master.
|
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.
|
CSCsa39624
|
In RME 4.0, you can see devices directly under /CS@hostname (Common group root) in the Device selector screens.
|
This problem occurs when you import many devices (around 2000 or more) with unknown device type. RME discovers the device type and updates DCR.
Workaround:
Restart RMEOGSServer using pdterm and pdexec commands. If the problem still persists, restart CiscoWorks Daemon Manager.
|
CSCsa39927
|
Wrong error message appears when you invoke DCR CLI in ACS mode.
|
The following error occurs:
init device cache failed.
This problem occurs when:
•More than 4000 devices exist in ACS and DCR.
•Wild card entries exist in the ACS.
Workaround:
None.
|
Grouping Services Known Problems
Table 12 describes the known problems associated with managing groups of devices.
Table 12 Grouping Services Known Problems
Bug ID
|
Summary
|
Explanation
|
CSCsa23339
|
Two different 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 in a remote case 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.
|
CSCsa44642
|
Fewer System Defined Groups appear after multiple mode changes in OGS.
|
This problem occurs when you switch a server from Slave mode to standalone mode many times.
For example:
1. Configure a Master (M) and a Slave (S).
2. Move S to standalone mode and delete a few devices from S.
3. Configure S as a Slave of M, again.
4. Query the CMFOGSServer on S, to get the number of System Defined Groups.
S will now have fewer number of groups and leaf level groups will be missing.
Workaround:
Restart the CMFOGSServer on S to create all the System Defined Groups. To do this:
1. To stop the CMFOGSServer, enter
NMSROOT/bin/pdterm CMFOGServer
2. To start the CMFOGSServer, enter
NMSROOT/bin/pdexec CMFOGServer
|
CSCsc30803
|
Cannot nest OR statements and AND statements such as (Rule OR Rule) AND (Rule OR Rule).
|
Found in Common Services 3.0 > Creating Groups. It works in RME.
Workaround:
None.
|
General Known Problems
Table 13 describes the miscellaneous known problems associated with Common Services (not specific to any module in Common Services).
Table 13 General Known Problems
Bug ID
|
Summary
|
Explanation
|
CSCdw93703
|
CiscoWorks LMS/RWAN memory and Dr Watson errors on Compaq Servers.
|
Dr Watson error appears on Compaq servers if Compaq Insight Manager is running on Compaq servers where CiscoWorks is also running.
Workaround:
•Restart the daemons.
Or
•Shut down Compaq Insight Manager.
|
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.
|
CSCea20284
|
Scheduled Backup does not work.
|
Scheduled Backup displays the following error when the backup directory is more than 24
characters:
Cannot schedule: The command line cannot
exceed 259 characters. Invalid command
Workaround:
1. Use a shorter directory.
2. Use Command line Backup or the Back up Data Now option to backup in longer directories.
|
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.
|
CSCeg26913
|
JDK crashes and Notification Services (NOS) does not receive any NOS messages.
|
When this problem occurs:
•NOS does not receive any NOS messages (however, FH and AAD will continue to work).
•Core file is dumped in /opt/CSCOpx directory.
•A file called hs_err_pid1452.log will be created. After the crash the PID of the NOSServer changes.
For example, the output of pdshow NOSServer will be:
Start = 11/27/04 08:55:28
Core = Core file created.
Info = Application failed or was
registered incorrectly.
Workaround:
Restart the Daemon 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 linkSee the following link:
http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_common_services_software/3.0/user/guide/diagnos.html#wp1078582
|
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
|
CSCin37340
|
The dbRestoreOrig.pl script displays error message.
|
When you run the dbRestoreOrig.pl script the following error message appears:
CreateService - 'EssentialsDbEngine' The
specified service has been marked for
deletion.
CreateService - 'CmfDbEngine' The specified
service has been marked for deletion
This happens if the database is running when the dbRestoreOrig.pl script is run.
Workaround:
Wait for a couple of minutes and then run the dbrestoreOrig.pl script again with the same arguments. If this does not work, reboot the machine and then run the dbrestoreOrig.pl script.
|
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.
|
CSCsa20444
|
Job state changes to Cancelled even after the job is completed successfully.
|
This problem is only seen for periodic jobs, with no job history maintained.
This occurs when you:
1. Create a job.
2. When the job is running click Stop button, but do not press OK in the stop confirmation UI.
3. After the jrm.log confirms the successful completion of the job, press OK.
This changes the state of the job to Cancelled.
Workaround:
None.
|
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:
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 CS 3.0.3. So, application links appear.
Workaround:
Upgrade all applications to the latest available version for proper functionality.
|
CSCsb97406
|
Cannot launch the
Cisco Works screen
(e.g http://server_name:1741).
|
This happens when many threads are opened from the Tomcat environment.
Workaround:
Caution You need to be careful while making these changes since they involve editing the registry.
1. Stop the Daemon Manager (<B> net stop crmdmgtd</B>).
2. Open the registry editor(<B>regedit</B>).
3. Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tomcat\Parameters.
4. Look for the entry which has the value -Xss1m.
5. Change this value to "-Xss64k" and close the registry editor.
6. Start the Daemon Manager (<B> net start crmdmgtd </B>).
|
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.
|
CSCsc71565
|
In CS 3.0, while registering a Test Application, the wrong port number is used.
When you upgrade to CS 3.0.3, the Test Application will not appear under the registered applications.
|
In this scenario, all the xml files under registered-templates have the right port number and protocol, except the Test Application that has the wrong port number.
Even in the case of changing port number or protocol, once the port or protocol is changed, the files under the registered-templates are updated accordingly except for the application with the wrong port number.
Workaround:
None.
|
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.
|
CSCsd40367
|
Software Center scheduled jobs execute 50 minutes before the schedule.
|
Operating System vendors, Microsoft and Sun Microsystems have released patches for changes in Australian daylight savings from March 27, 2006 to April 2, 2006 due to the Common Wealth Games.
It has been found that the java API used to get system time returns one hour less than the actual server time during the affected period.
As a result, the scheduled backup and/or compaction of database are executed with a delay of one hour. Also, the logs and/or reports show incorrect time stamp.
The following time zones are affected:
•Adelaide (GMT +9.30)
•Hobart (GMT+ 10.00)
•Sydney (GMT + 10.30)
Workaround:
Reschedule the jobs by one hour ahead of the actual desirable time from March 27, 2006 to April 02, 2006.
|
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.
|
CSCse90398
|
Extra gray spaces appear in fewapplication screens (for example SWIM workflows), if the number of rows in a table is less than 10.
|
For example, the resulting rows in a table in the following SWIM workflows appears with extra gray space, if less than 10.
•Go to RME > Software Mgmt > Software Repository
a. Click on Add button.
The Add Images dialog box appears.
b. Select any one of the options:
Cisco.com
Device
File System
Network
Out of Sync report
•Go to RME > Software Mgmt > Software Distribution > Upgrade Analysis > Cisco.com
•Go to RME > Software Mgmt > Software Distribution > By devices (Advanced)
Workaround:
None.
|
CiscoView Known Problems
To view the known problems for a specific device package release, see the Readme file provided with that release. Table 14 describes the known problems in CiscoView 6.1.5.
Table 14 Known Problems in CiscoView 6.1.5
Bug ID
(Severity)
|
Summary
|
Explanation
|
CSCin40139
|
Blank Monitoring dialog box appears after Refresh.
|
When you transition from one Monitoring dialog box to another, the dialog box goes blank if you:
1. Select Device > Monitor > IP.
2. Change the Refresh rate to 5 seconds after the dialog box opens,
3. Click the Category box.
4. Wait for the next Refresh to occur before you select a category.
Workaround:
None.
|
CSCsa30779
|
Selected port/module is not completely highlighted.
|
To reproduce the problem:
1. Using Netscape Navigator, launch CiscoViewand open the chassis view for either a Catalyst 3750 or 6000 device.
2. Click either a module or port to select it. Only the left side of the selected module/port is highlighted by a yellow border.
There is no workaround.
This problem does not occur in Internet Explorer.
|
CSCsb67167
|
Newly added devices are not listed in the Device Preferences dialog box.
|
This problem occurs when you:
1. Add devices to the DCR.
2. Launch the Device Preferences dialog box.
The Device Display Name field does not list the devices you just added.
Workaround:
None.
To correct the problem, launch the chassis view for those devices in CiscoView.
|
CSCsb87420
|
Error sometimes occurs when configuring a device.
|
A null point exception error sometimes occurs after making a configuration change to a device within CiscoView.
There is no workaround.
|
CSCse68727
|
The results for Advanced Search are shown in all the open CiscoView windows.
|
Steps to reproduce:
1. Open Advanced Search dialog for device selector in ChassisView
2. Add search criteria and perform Search
3. The results are expected to be shown in the ChassisView page from which the advanced search dialog was launched. However, the search results are shown in all the ChassisView sessions which are open at that time.
Workaround:
None.
|
CSCse83768
|
Viewing all the devices in the CiscoView stack displays an error message on Windows XP and Windows 2003 client systems.
|
This occurs when you:
1. Start StackMaker and click the StackView button from the StackMaker Main Window,
An error message appears, Callback is null or not an object
2. Click OK in the error dialog box to view all the stackable devices.
Workaround:
None
|
Known Problems in CiscoView Mini-RMON Manager 2.3
Table 15 describes the known problems that you might encounter while troubleshooting network availability problems using CiscoView Mini-RMON Manager 2.3.
Table 15 Known Problems in CiscoView Mini-RMON Manager 2.3
Bug ID
|
Summary
|
Additional Information
|
CSCsa70049
|
Devices are sometimes listed twice in the Object Selector.
|
This problem occurs inconsistently and does not affect functionality.
Workaround:
None.
|
CSCsa76938
|
Devices of unknown types are not handled as expected by Object Selector and CiscoView Mini-RMON Manager.
|
This problem occurs when you:
1. Add a device that is supported by CiscoView Mini-RMON Manager in the DCR, but set the device type as Unknown.
2. Launch CiscoView Mini-RMON Manager.
The following happens:
•Object Selector does not display the device under the unknown device type group.
•When you enter the IP address for that device in CiscoView Mini-RMON Manager's Device Selector, the application retrieves its credentials from the DCR and launches the System Configuration page (Setup > System).
Workaround:
Make sure you set the proper device type for any device you add in the DCR.
|
CSCsa82959
|
Able to install CiscoView Mini-RMON Manager device package in CiscoView 6.0 and CiscoView 6.1 without first installing CiscoView 6.1.1 engine patch.
|
Even though you can install the device package, Mini-RMON functionality will be available only if you first install the engine patch.
Workaround:
None.
|
CSCsa94018
|
Pages and dialog boxes or both display no data after device goes down.
|
This problem occurs when you:
1. Launch CiscoView Mini-RMON Manager.
2. Select a new application page or refresh the current one.
If the device being monitored goes down before you open new page or refresh the current page, all subsequent pages and dialog boxes will display no data.
Also, no message appears that the device is down.
Workaround:
To get confirmation that the device is down, close the current session and open a new one for that device.
|
CSCsb00192
|
Browser's status bar does not indicate that the creation of a new alarm is complete.
|
This problem occurs when you:
1. Click the Setup tab.
2. From the Options bar, click Alarms.
3. From the Setup Alarm Thresholds page, click Create.
4. Enter the necessary information and click OK.
A new alarm is created, but the status bar indicates that the process is still running.
Workaround:
Launch another page or click an action button.
|
CSCsb05750
|
Cannot enable statistics collection on some devices.
|
An error message appears when you attempt to enable statistics collection on the following devices:
•Catalyst 2970-24TS
•Catalyst 3550-24MMF
•Catalyst 3750
•Catalyst 4948
Workaround:
Enable statistics collection using the CLI (this does not apply to Catalyst 4948 devices).
For more information, see the corresponding SNMP agent problems: CSCin93032, CSCin93030, CSCin93028, CSCsb05787, and CSCef19988.
|
CSCsb07657
|
Cannot create alarms on some devices.
|
An error message appears when you attempt to create an alarm on Catalyst 1900 and 2820 devices.
Workaround:
None.
See CSCin93036, the corresponding SNMP agent problem, for more information.
|
CSCsb07787
|
Cannot create history entry on Catalyst 5509 device.
|
When attempting to create a history entry from the Statistics page (Setup > Statistics History) on a Catalyst 5509 device, an error message is displayed and the entry is not created.
Workaround:
None.
|
CSCsb07793
|
Sometimes Device Selector does not work as expected.
|
This problem occurs when you:
1. Launch multiple CiscoView Mini-RMON Manager sessions.
2. Expand a folder in the Device Selector of an open session by clicking the plus sign beside it.
Sometimes, instead of the folder expanding, the Device Selector tree collapses and displays only the main folder.
After you expand the main folder, the expandable folders beneath it display a minus sign instead of a plus sign.
Workaround:
Click the minus sign for an expandable folder.
A plus sign appears and the Object Selector works.
|
CSCsc00802
|
Statistics collection and History features are not supported by some devices.
|
The following devices do not support the Statistics collection and History features in CiscoView Mini-RMON Manager 2.0:
•Cisco 2800 Series Integrated Services Routers: Cisco 2801, Cisco 2821, Cisco 2851
•Cisco 3800 Series Integrated Services Routers: Cisco 3825, Cisco 3845
•Cisco 2600 Series Multiservice Routers: Cisco 2610, Cisco 2610XM, Cisco 2611, Cisco 2611XM, Cisco 2612, Cisco 2613, Cisco 2620, Cisco 2620XM, Cisco 2621, Cisco 2621XM, Cisco 2650, Cisco 2650XM, Cisco 2651, Cisco 2651XM
•Cisco 3600 Series Multiservice Routers: Cisco 3620, Cisco 3631Co, Cisco 3640, Cisco 3660, Cisco 3662Dc, Cisco 3662Ac, Cisco 3662AcCo, Cisco 3662DcCo, Cisco 3661Ac, Cisco 3661Dc
•Cisco 3700 Series Multiservice Access Routers: Cisco 3725, Cisco 3745
•Cisco IAD2400 Series Integrated Access Devices: Cisco 2420 IAD, Cisco 2430-24Fxs IAD, Cisco 2431-8Fxs IAD, Cisco 2431-16Fxs IAD, Cisco 2431-1T1E1 IAD, Cisco 2432-24Fxs IAD
Workaround:
None.
|
CiscoView Resolved Problems
Table 16 describes the problems that are resolved in Cisco View 6.1.5.
Note To obtain more information about known problems, access the Cisco SoftwareBug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. (You will be prompted to log into Cisco.com.)
Table 16 Resolved Problems in CiscoView 6.1.5
Bug ID
|
Summary
|
Additional Information
|
CSCsa37848
|
While configuring a device, no message appeared to inform you that changes are being committed to the device.
|
This problem is resolved.
|
CSCsc66769
|
In LMS2.5.1, there was a java.lang.nullpointer exception when the device IP field was blank
|
This problem is resolved.
|
CSCsc93827
|
While launching a device, the full name of the Mib Object is not displayed in the Monitor graph.
|
This problem is resolved.
|
CSCsd40336
|
Sub-level context menus were not working as expected for multiple port selections.
|
This problem is resolved.
|
CSCsd52332
|
When dialog boxes were launched in Mozilla 1.7.5 or Netscape 7.2, on clicking refresh, the scrollbars disappeared.
|
This problem is resolved.
|
CSCsd53947
|
Negative threshold values were not accepted when entered to the Rising and Falling threshold fields in the Mini RMON Manager.
|
This problem is resolved.
|
CSCsd61170
|
When you clicked the mouse button after selecting several ports, the outline of the port disappeared.
|
This problem is resolved.
|
CSCsd85800
|
CiscoView 6.1.4 user guide/online help provided an incorrect section heading.
|
This problem is resolved.
|
CSCse23375
|
Monitoring dialog boxes for Cisco PIX security appliances displayed group charts with incorrect values.
|
This problem is resolved.
|
CSCse58358
|
While generating the stats in Mini RMON Manager, it showed above 400% utilization in GE interface.
|
This problem is resolved.
|
CSCse68694
|
Chassis views displayed by Mozilla and Netscape browsers did not update the status of device components after a change was made.
|
This problem is resolved.
|
Internally-Found Resolved Problems
Table 17 lists the problems that were found internally and have been resolved since the last release of Common Services.
Table 17 Internally-Found Resolved Problems
Bug ID
|
Summary
|
Additional Information
|
CSCsa03531
|
When you restored CS 2.1 data, an error message appeared.
|
This problem has been resolved.
|
CSCsa30274
|
In LMS 2.5, psucli deleted unexpected packages.
|
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.
|
CSCsc71280
|
Peer Server Accounts were not preserved while upgrading to CS 3.0.3.
|
This problem has been resolved.
|
CSCsc71403
|
Changes to some Context Sensitive Online Help (OLH) files did not reflect in the CiscoWorks LMS 2.5 December 2005 Update.
|
This problem has been resolved.
|
Customer-Found Resolved Problems
Table 18 lists the customer-found problems that have been fixed since the last release of Common Services.
Table 18 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
|
Because the creation of 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.
|
CSCsc94079
|
The value of the CrmDnsResolution registry key could not be modified either using 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 he changes were occurring for all the 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.
|
Obtaining Documentation
Cisco documentation and additional literature are available on Cisco.com. This section explains the product documentation res ources that Cisco offers.
Cisco.com
You can access the most current Cisco documentation at this URL:
http://www.cisco.com/techsupport
You can access the Cisco website at this URL:
http://www.cisco.com
You can access international Cisco websites at this URL:
http://www.cisco.com/public/countries_languages.shtml
Product Documentation DVD
The Product Documentation DVD is a library of technical product documentation on a portable medium. The DVD enables you to access installation, configuration, and command guides for Cisco hardware and software products. With the DVD, you have access to the HTML documentation and some of the PDF files found on the Cisco website at this URL:
http://www.cisco.com/univercd/home/home.htm
The Product Documentation DVD is created monthly and is released in the middle of the month. DVDs are available singly or by subscription. Registered Cisco.com users can order a Product Documentation DVD (product number DOC-DOCDVD= or DOC-DOCDVD=SUB) from Cisco Marketplace at the Product Documentation Store at this URL:
http://www.cisco.com/go/marketplace/docstore
Ordering Documentation
You must be a registered Cisco.com user to access Cisco Marketplace. Registered users may order Cisco documentation at the Product Documentation Store at this URL:
http://www.cisco.com/go/marketplace/docstore
If you do not have a user ID or password, you can register at this URL:
http://tools.cisco.com/RPF/register/register.do
Documentation Feedback
You can provide feedback about Cisco technical documentation on the Cisco Technical Support & Documentation site area by entering your comments in the feedback form available in every online document.
Cisco Product Security Overview
Cisco provides a free online Security Vulnerability Policy portal at this URL:
http://www.cisco.com/en/US/products/products_security_vulnerability_policy.html
From this site, you will find information about how to do the following:
•Report security vulnerabilities in Cisco products
•Obtain assistance with security incidents that involve Cisco products
•Register to receive security information from Cisco
A current list of security advisories, security notices, and security responses for Cisco products is available at this URL:
http://www.cisco.com/go/psirt
To see security advisories, security notices, and security responses as they are updated in real time, you can subscribe to the Product Security Incident Response Team Really Simple Syndication (PSIRT RSS) feed. Information about how to subscribe to the PSIRT RSS feed is found at this URL:
http://www.cisco.com/en/US/products/products_psirt_rss_feed.html
Reporting Security Problems in Cisco Products
Cisco is committed to delivering secure products. We test our products internally before we release them, and we strive to correct all vulnerabilities quickly. If you think that you have identified a vulnerability in a Cisco product, contact PSIRT:
•For emergencies only — security-alert@cisco.com
An emergency is either a condition in which a system is under active attack or a condition for which a severe and urgent security vulnerability should be reported. All other conditions are considered nonemergencies.
•For nonemergencies — psirt@cisco.com
In an emergency, you can also reach PSIRT by telephone:
•1 877 228-7302
•1 408 525-6532
Tip We encourage you to use Pretty Good Privacy (PGP) or a compatible product (for example, GnuPG) to encrypt any sensitive information that you send to Cisco. PSIRT can work with information that has been encrypted with PGP versions 2.x through 9.x.
Never use a revoked encryption key or an expired encryption key. The correct public key to use in your correspondence with PSIRT is the one linked in the Contact Summary section of the Security Vulnerability Policy page at this URL:
http://www.cisco.com/en/US/products/products_security_vulnerability_policy.html
The link on this page has the current PGP key ID in use.
If you do not have or use PGP, contact PSIRT to find other means of encrypting the data before sending any sensitive material.
Product Alerts and Field Notices
Modifications to or updates about Cisco products are announced in Cisco Product Alerts and Cisco Field Notices. You can receive Cisco Product Alerts and Cisco Field Notices by using the Product Alert Tool on Cisco.com. This tool enables you to create a profile and choose those products for which you want to receive information.
To access the Product Alert Tool, you must be a registered Cisco.com user. (To register as a Cisco.com user, go to this URL: http://tools.cisco.com/RPF/register/register.do) Registered users can access the tool at this URL: http://tools.cisco.com/Support/PAT/do/ViewMyProfiles.do?local=en
Obtaining Technical Assistance
Cisco Technical Support provides 24-hour-a-day award-winning technical assistance. The Cisco Technical Support & Documentation website on Cisco.com features extensive online support resources. In addition, if you have a valid Cisco service contract, Cisco Technical Assistance Center (TAC) engineers provide telephone support. If you do not have a valid Cisco service contract, contact your reseller.
Cisco Technical Support & Documentation Website
The Cisco Technical Support & Documentation website provides online documents and tools for troubleshooting and resolving technical issues with Cisco products and technologies. The website is available 24 hours a day at this URL:
http://www.cisco.com/techsupport
Access to all tools on the Cisco Technical Support & Documentation website requires a Cisco.com user ID and password. If you have a valid service contract but do not have a user ID or password, you can register at this URL:
http://tools.cisco.com/RPF/register/register.do
Note Use the Cisco Product Identification Tool to locate your product serial number before submitting a request for service online or by phone. You can access this tool from the Cisco Technical Support & Documentation website by clicking the Tools & Resources link, clicking the All Tools (A-Z) tab, and then choosing Cisco Product Identification Tool from the alphabetical list. This tool offers three search options: by product ID or model name; by tree view; or, for certain products, by copying and pasting show command output. Search results show an illustration of your product with the serial number label location highlighted. Locate the serial number label on your product and record the information before placing a service call.
Tip Displaying and Searching on Cisco.com
If you suspect that the browser is not refreshing a web page, force the browser to update the web page by holding down the Ctrl key while pressing F5.
To find technical information, narrow your search to look in technical documentation, not the entire Cisco.com website. On the Cisco.com home page, click the Advanced Search link under the Search box and then click the Technical Support & Documentation.radio button.
To provide feedback about the Cisco.com website or a particular technical document, click Contacts & Feedback at the top of any Cisco.com web page.
Submitting a Service Request
Using the online TAC Service Request Tool is the fastest way to open S3 and S4 service requests. (S3 and S4 service requests are those in which your network is minimally impaired or for which you require product information.) After you describe your situation, the TAC Service Request Tool provides recommended solutions. If your issue is not resolved using the recommended resources, your service request is assigned to a Cisco engineer. The TAC Service Request Tool is located at this URL:
http://www.cisco.com/techsupport/servicerequest
For S1 or S2 service requests, or if you do not have Internet access, contact the Cisco TAC by telephone. (S1 or S2 service requests are those in which your production network is down or severely degraded.) Cisco engineers are assigned immediately to S1 and S2 service requests to help keep your business operations running smoothly.
To open a service request by telephone, use one of the following numbers:
Asia-Pacific: +61 2 8446 7411
Australia: 1 800 805 227
EMEA: +32 2 704 55 55
USA: 1 800 553 2447
For a complete list of Cisco TAC contacts, go to this URL:
http://www.cisco.com/techsupport/contacts
Definitions of Service Request Severity
To ensure that all service requests are reported in a standard format, Cisco has established severity definitions.
Severity 1 (S1)—An existing network is "down" or there is a critical impact to your business operations. You and Cisco will commit all necessary resources around the clock to resolve the situation.
Severity 2 (S2)—Operation of an existing network is severely degraded, or significant aspects of your business operations are negatively affected by inadequate performance of Cisco products. You and Cisco will commit full-time resources during normal business hours to resolve the situation.
Severity 3 (S3)—Operational performance of the network is impaired while most business operations remain functional. You and Cisco will commit resources during normal business hours to restore service to satisfactory levels.
Severity 4 (S4)—You require information or assistance with Cisco product capabilities, installation, or configuration. There is little or no effect on your business operations.
Obtaining Additional Publications and Information
Information about Cisco products, technologies, and network solutions is available from various online and printed sources.
•The Cisco Product Quick Reference Guide is a handy, compact reference tool that includes brief product overviews, key features, sample part numbers, and abbreviated technical specifications for many Cisco products that are sold through channel partners. It is updated twice a year and includes the latest Cisco channel product offerings. To order and find out more about the Cisco Product Quick Reference Guide, go to this URL:
http://www.cisco.com/go/guide
•Cisco Marketplace provides a variety of Cisco books, reference guides, documentation, and logo merchandise. Visit Cisco Marketplace, the company store, at this URL:
http://www.cisco.com/go/marketplace/
•Cisco Press publishes a wide range of general networking, training, and certification titles. Both new and experienced users will benefit from these publications. For current Cisco Press titles and other information, go to Cisco Press at this URL:
http://www.ciscopress.com
•Packet magazine is the magazine for Cisco networking professionals. Each quarter, Packet delivers coverage of the latest industry trends, technology breakthroughs, and Cisco products and solutions, as well as network deployment and troubleshooting tips, configuration examples, customer case studies, certification and training information, and links to scores of in-depth online resources. You can subscribe to Packet magazine at this URL:
http://www.cisco.com/packet
•Internet Protocol Journal is a quarterly journal published by Cisco Systems for engineering professionals involved in designing, developing, and operating public and private internets and intranets. You can access the Internet Protocol Journal at this URL:
http://www.cisco.com/ipj
•Networking products offered by Cisco Systems, as well as customer support services, can be obtained at this URL:
http://www.cisco.com/en/US/products/index.html
•Networking Professionals Connection is an interactive website where networking professionals share questions, suggestions, and information about networking products and technologies with Cisco experts and other networking professionals. Join a discussion at this URL:
http://www.cisco.com/discuss/networking
•"What's New in Cisco Documentation" is an online publication that provides information about the latest documentation releases for Cisco products. Updated monthly, this online publication is organized by product category to direct you quickly to the documentation for your products. You can view the latest release of "What's New in Cisco Documentation" at this URL:
http://www.cisco.com/univercd/cc/td/doc/abtunicd/136957.htm
•World-class networking training is available from Cisco. You can view current offerings at this URL:
http://www.cisco.com/en/US/learning/index.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].
This document is to be used in conjunction with the documents listed in the "Product Documentation" section.
Copyright © 1998-2006, Cisco Systems, Inc.
All rights reserved.
Feedback
