Table Of Contents
Release Notes for CiscoWorks Common Services 3.0.3 (Includes CiscoView 6.1.2) on Solaris
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
Documentation Errata for CiscoView
Known and Resolved Problems
Installation Known Problems
CiscoWorks Homepage Known Problems
Software Center Known Problems
Integration Utility 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.0
CiscoView Resolved Problems
Internally-Found Resolved Problems
Customer-Found Resolved Problems
Resolved Problems in CS 3.0 Service Pack 2
Resolved Problems in CS 3.0 Service Pack 1
Obtaining Documentation
Cisco.com
Product Documentation DVD
Ordering Documentation
Documentation Feedback
Cisco Product Security Overview
Reporting Security Problems in Cisco Products
Obtaining Technical Assistance
Cisco Technical Support & Documentation Website
Submitting a Service Request
Definitions of Service Request Severity
Obtaining Additional Publications and Information
Release Notes for CiscoWorks Common Services 3.0.3 (Includes CiscoView 6.1.2) on Solaris
This release note is for CiscoWorks Common Services 3.0.3 running on a Solaris 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
•Documentation Errata for CiscoView
•Known and Resolved Problems
•Obtaining Technical Assistance
•Obtaining Additional Publications and Information
New Features
The new features in CiscoWorks Common Services Release 3.0.3 are:
•The AcsRegCli.pl command line script that allows you to register individual applications with ACS without affecting the registration status of other applications.
•Conflict resolution option in dcrcli overwrites Device and Credential Repository (DCR) data from import source.
•Software Center CLI allows you to display the list of dependent packages for a specified package.
•Support for Java Plug-in version 1.4.2_08.
•Enhancements in Device and Credential Repository (DCR):
–Support for HTTP related credentials and attributes
–Support for CNS Configuration Engine and CNS Managed devices
See the application documentation for details on the application version that supports these features.
Note CS 3.0.3 does not support a DCR Master-Slave setup with a mix of CS 3.0 and CS 3.0 SP1/CS 3.0 SP2/CS 3.0.3 servers.
•Enhancements in Software Center:
–Prompt for Cisco.com credentials while selecting, scheduling, and downloading software and device updates
–Prompt for Proxy credentials while selecting, scheduling, and downloading software and device updates if you have configured Proxy settings
•Support for CiscoSecure ACS 3.3.3 Appliance and CiscoSecure ACS 3.3.3 for Windows Server.
•Enhancements in Audit Log.
Audit Log provides information on:
–CiscoWorks Local user addition
–CiscoWorks Local user modification
–CiscoWorks Local user deletion
–CiscoWorks login failures.
•Support for MDF 1.6.
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.6 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.5. 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.6 contains the following new device types:
–Cisco CSS 11503 Content Services Switch(1.3.6.1.4.1.9.9.368.4.5)
–Cisco CSS 11506 Content Services Switch(1.3.6.1.4.1.9.9.368.4.6)
–Cisco 1803 Integrated Services Router(1.3.6.1.4.1.9.1.640)
–Cisco 7604 Router(1.3.6.1.4.1.9.1.658)
–Cisco 851 Integrated Services Router(1.3.6.1.4.1.9.1.566)
–Cisco 871 Integrated Services Router(1.3.6.1.4.1.9.1.571)
–Cisco 876 Integrated Services Router(1.3.6.1.4.1.9.1.568)
–Cisco 878 Integrated Services Router(1.3.6.1.4.1.9.1.570)
–Cisco ME 2400-24TS-A Switch(1.3.6.1.4.1.9.1.734)
–Cisco ME 3400-24TS-A Switch(1.3.6.1.4.1.9.1.736)
–Cisco IDS 4220 Sensor(1.3.6.1.4.1.9.1.741)
–Cisco IDS 4230 Sensor(1.3.6.1.4.1.9.1.742)
Note Addition of 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.
For details on Common Services 3.0 features see:
http://www.cisco.com/en/US/products/sw/cscowork/ps3996/products_user_guide_chapter09186a00801fc600.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 output for either case scenario.
To ensure that time zones are translated correctly—especially when your devices, servers, and clients are in different time zones—follow these guidelines:
•When configuring time zones on managed devices, use the acronyms listed in the Time Zone Acronym Setting on Device column. To set time zones on devices, use the command described in the device-specific Command Reference documentation.
•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.
Note 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/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 /opt/CSCOpx/lib/vbroker/gatekeeper.cfg.
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 by entering
/etc/init.d/dmgtd start
Operating System Upgrade
While installing CiscoWorks Common Services, the installation process checks for required patches. Install any missing solaris patches.
For a list of required patches, see Chapter 1 of Installation and Setup Guide for CiscoWorks Common Services (Includes CiscoView) on Solaris.
Caution If CiscoWorks Common Services is run without the required patches, 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.
Table 3 Server System Requirements 1
Requirement Type
|
Minimum Requirements
|
System hardware
|
•Sun UltraSPARC10.2
•Color monitor.
•CD-ROM drive.
|
Memory (RAM)
|
512 MB (to install all Common Services components).
|
Available drive space
|
•2 GB on the partition on which you install the product (The default is /opt).
•Minimum 1024 MB Swap space.
|
System software
|
Solaris 8 and Solaris 9.
Common Services 3.0.3 supports only US-English and Japanese versions of Solaris 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.
We recommend that you install the Solaris Operating System in any of the following modes:
•Entire Distribution
•Entire Distribution plus OEM support
•End User System Support
|
Additional software (Optional)
Browsers
|
•Netscape Navigator 7.0.
•Mozilla 1.7.5.
|
Caution Do not use non standard java options through JAVA_OPTIONS environment variable.
To verify the amount of available disk space in each of the specified partitions and directories, enter:
where directory is the partition or directory for which you want to check the available disk space.
Client Requirements
Table 4 shows the minimum system requirements for a client system.
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 the following:
–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.
•Sun UltraSPARC 10 running Solaris 8, Solaris 9.
Color monitor with video card set to 24 bits color depth.
|
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).
•Java Virtual Machine (JVM) 5.0.0.3802 and later, and Java Plug-in
version 1.4.2_08.(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 for Windows.
•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 the 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 Enable Java check box.
Step 3 Restart Netscape Navigator.
To enable Java Console in Mozilla:
Step 1 Select Edit > Preferences > Advanced.
Step 2 Check Enable Java check box 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.
•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.3
See this document to understand the CiscoWorks login modes.
•User Guide for CiscoView 6.1.2
See this document to understand all CiscoView tasks.
CiscoWorks Roles and Privileges
By default, the CiscoWorks server authentication scheme has five roles in ACS mode. They are listed here from least privileged to most privileged:
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.
Documentation Errata for CiscoView
When you go through the CiscoView 6.1.2 User Guide, note that the URLs provided on pages ix through xi of the Preface are incorrect and should read as follows:
Known and Resolved Problems
Tables 6 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/cgi-bin/Support/Bugtool/home.pl (You will be prompted to log onto Cisco.com.).
The CiscoWorks Common Services known problems are broken down into the following sections:
•Installation Known Problems
•CiscoWorks Homepage Known Problems
•Software Center Known Problems
•Integration Utility 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.0
•CiscoView Resolved Problems
•Internally-Found Resolved Problems
•Customer-Found Resolved Problems
•Resolved Problems in CS 3.0 Service Pack 2
•Resolved Problems in CS 3.0 Service Pack 1
Installation Known Problems
Table 6 Installation Known Problems
Bug ID
|
Summary
|
Explanation
|
CSCin30836
|
CiscoWorks Common
Services installation hangs on Solaris.
|
This happens when you reinstall or upgrade over a broken installation.
Workaround:
Clean up the broken installation and then install CiscoWorks Common Services.
|
CSCin26986
|
Reference to point patches exists even after upgrade.
|
Even after you upgrade to the newer version of the product, the patches that were applied to previous version are listed when you select the product in the Software Centre page.
Workaround:
The information though misleading, does not impact the proper functioning.
|
CSCin21594
|
Installation hangs or slows down when you install CiscoWorks Common Services on a mounted path.
|
Installation on a mounted path may slow down or hang because of the slow response of the remote server.
Workaround:
1. Stop the installation.
2. Create a directory where you want to copy the contents of the network image by entering:
mkdir /opt/image dir
Make sure that this directory has enough space to hold the entire contents of the image.
3. Enter:
tar cpf - . | (cd /opt/image dir && tar -xpf - )
This command preserves all attributes including the timestamp.
4. Re-start installation.
|
CSCsc36054
|
Solaris linker patch causes LMS applications to fail.
|
This occurs after installing patch 109147-39 for Solaris 8 or 112963-24 for Solaris 9.
Workaround:
Downgrade to patch 109147-38 (or earlier) on Solaris 8 or 112963-23 (or earlier) on Solaris 9.
|
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 LM S2.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.
|
CSCsc71280
|
Peer Server Accounts are not preserved while upgrading to CS 3.0.3.
|
1. Install CS 3.0.
2. Add Peer Server accounts.
3. Upgrade to CS 3.0.3.
Previously added Peer Server Accounts will be lost.
However, System Identity Account is preserved.
Workaround:
Add the Peer Server Accounts again to CiscoWorks.
|
CSCsc66462
|
The Event Log displays device package install failure as an error, without giving exact cause.
|
This error appears when only one device package is selected for install and it fails to get installed.
Workaround:
None.
|
CiscoWorks Homepage Known Problems
Table 7 CiscoWorks Homepage Known Problems
Bug ID
|
Summary
|
Explanation
|
CSCin22157
|
The DiskWatcher popup message does not appear.
|
The DiskWatcher popup message does not appear when the free disk space goes below 20 percent.
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 a corrupted character for (c).
Workaround:
Display the correct character by selecting the English encoding of the browser.
|
CSCdw11344
|
Connectivity Tools > Management Station reports that 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.
|
CSCsa03383
|
Collect Server Info shows errors in PACKAGE INFO.
|
Collect Server Info shows pkgchk errors in PACKAGE INFO section. This happens when the directory/file characteristics (such as checksum, permissions) change during runtime.
Workaround:
None. This does not affect the functionality.
|
Software Center Known Problems
Table 8 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 when you download device packages from Cisco.com.
Workaround:
None.
|
CSCin66811
|
Inaccurate scheduling occurs if Time Zone is not set.
|
This occurs when the environment Time Zone is not set properly.
Workaround:
Ensure that the TZ environment is accurate.
|
CSCsa30274
|
In LMS 2.5, psucli deletes unexpected packages.
|
This occurs in CLI when you use the Multiple Product option. When different products have the same device package name, Software Center deletes some packages.
Workaround:
If the same package name exists in multiple products, do not use the multiple product option in CLI.
Instead select the required product.
|
CSCsa30580
|
Software Center does not accept Cisco.com login credentials with spaces between characters.
|
Software Center does not accept the customer's Cisco.com password if it contains spaces between characters.
Workaround:
Change the Cisco.com password.
|
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, the list of available packages appears.
–In Internet Explorer, the default screen appears.
The device package headers are downloaded to a temporary folder.
Workaround:
To cleanup the temporary download location explicitly:
1. Stop the Daemon Manager by entering /etc/init.d/dmgtd stop.
2. Remove the contents of the directory under NMSROOT/ temp/psu.
3. Restart the Daemon Manager by entering /etc/init.d/dmgtd start.
|
CSCsc43429
|
PSU adapter package does not get installed.
|
This problem occurs when the PSU adapter package is installed without any device package through GUI or CLI.
There are no errors or exceptions or warnings displayed in the GUI or in the log.
Workaround:
Install the adapter with some corresponding device packages. For example, CMFAdapter can be installed with some other device packages.
|
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.
|
CSCsb87463
|
Installation of a Device Package does not succeed. A message appears,
Base package check failed.
although the base package is available in the source location.
|
Consider the following scenario:
•Device package A is about to be installed and is dependent on Package X.
•Higher version of Package X is already installed.
•Lower version of Package X is available in the same source location as Package
Under these conditions, if you try to install Package A, it fails.
Workaround:
Delete the source location package X. Installation proceeds for Package A.
|
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.
|
Integration Utility Known Problems
The file NMIDBOptions.properties contains Cisco.com passwords, in an encoded form, and is accessible only to root users. Root access to the host needs to be restricted if Cisco.com password security is a concern.
Table 9 Integration Utility Known Problems
Bug ID
|
Summary
|
Explanation
|
CSCef04708
|
In NIS+ server, CiscoWorks Integration Utility installation fails if casuser(s) do not exist.
|
Integration Utility fails and displays the following errors:
> ERROR: The /etc/group is not used by the
system.
> ERROR: Add casusers entry in /etc/group
won't take effect.
> ERROR: Either add files entry in
/etc/nsswitch.conf,
> ERROR: or add casusers entry in NIS/NIS+
database.
> ERROR: Contact your system administrator
for detail.
Workaround:
Create user casuser and group casusers, and add casuser in the group.
|
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\
|
CSCin08716
|
Cannot launch CiscoWorks applications from third-party NMS after reinstalling CD One.
|
Third-party NMS application links do not reflect changes made to SSL settings after reinstalling CD One.
Workaround:
Perform the integration again. This is required to update the application registration in NMS.
|
CSCin08472
|
Cannot launch CiscoWorks applications from third-party NMS after enabling or disabling SSL.
|
After you enable or disable SSL in CiscoWorks server, you cannot launch CiscoWorks applications from a third-party NMS, such as HP OpenView Network Node Manager and Netview.
Workaround:
You must perform the integration each time you enable or disable SSL in the CiscoWorks server. This is required to update the application registration in NMS.
|
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.
|
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.
|
CSCdp90728
|
When you run the Update Cisco Device Support task from the Network Node Manager (NNM), generated messages do not appear.
|
If you run the Update Cisco Device Support task from any Network Node Manager (for example, HP OpenView NNM), generated messages do not appear.
Workaround:
View the generated messages in the windows where you started HP Openview.
|
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.
|
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.
|
CSCdp89704
|
Uninstallation of Integration Utility does not restore completely.
|
Uninstallation of Integration Utility does not restore Cisco device icons back to generic device icons.
Workaround:
None.
|
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 new NMIDB, the menu entry CiscoView5.x is not removed since the new registry file name in the new NMIDB is different.
In this way both menu items 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.
|
Browser Known Problems
Table 10 Browser Known Problems
Bug ID
|
Summary
|
Explanation
|
None.
|
If you have a popup-blocker enabled in your browser, popups do not appear.
|
Popups do not appear
Workaround
Disable the popup-blocker, if you have installed any.
|
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.
|
CSCdt11838
|
While launching an application, you are not prompted to install the 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.
|
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.
|
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.
|
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.
2. If so, delete the certificate.
3. Clear the browser cache from Edit > Preferences > Advanced > Cache > Clear Cache.
4. Restart Mozilla.
|
CSCsc19380
|
Cannot select the contents of certain pages. For example, 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 a page need to be copied.
|
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.
|
DCR Known Problems
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.
|
CSCsa32420
|
Errors occur when you include some special characters and JavaScripts in the User Defined Fields (UDF) labels.
|
When RME reports display these UDF labels, the JavaScripts causes problems.
Workaround:
Do not include JavaScripts and special characters in the UDF labels.
|
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 do the actual configuration change.
|
CSCef86829
|
In DCR, export from file takes longer time than the export from device selector.
|
This problem occurs if 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 added.
Workaround:
Launch the chassis view for those devices in CiscoView.
|
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.
|
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.
|
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.
|
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.
|
CSCsa37988
|
In DCR, the IP address field accepts broadcast and multicast address.
|
In Device and Credentials > Device Management > Device property screen, the IP address field accepts broadcast and multicast addresses.
Workaround:
None.
Enter only valid class A, B and C IP addresses.
|
CSCsa45024
|
Deleting a large number of devices in the DCR GUI takes a long time.
|
It takes a long time for you to delete a large number of devices (> = 5000) in the DCR GUI.
Workaround:
Delete devices in batches of 1000 or 2000.
|
CSCsb90144
|
Importing devices from ACS fails, if the ACS server HTTPS protocol mentioned in AAA mode setup is different from the ACS server used for import.
|
This error is seen under the following conditions:
•Server > Security > AAA Mode Setup > Connect to ACS in HTTPS mode checkbox is selected and ACS server used is in HTTPS mode.
Or
•Checkbox is unselected but ACS server is in HTTPS mode.
Workaround:
Make sure that the ACS protocol mentioned in AAA Mode Setup is the same as the ACS Server used for import.
|
CSCsa43396
|
DSBU cluster does not retain parent-child relationship in the presence of a duplicate device.
|
This problem occurs when you configure a slave.
For example:
1. Let M be a master with DSBU cluster C1 and member M1.
2. Let S be standalone with DSBU cluster C1 and member M2.
1. Make S a slave of M allowing its devices to be added to M.
Here, C1 under S is taken as a duplicate and will not be added. However M2 is added without any change in its parent-dsbu-id.
M2 retains an invalid device-id as parent id.
Workaround:
Make sure that there are no duplicate DSBU clusters or members between the master and slave, before slave configuration.
|
Grouping Services Known Problems
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.
|
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.
Workaround:
None.
|
General Known Problems
Table 13 General Known Problems
Bug ID
|
Summary
|
Explanation
|
CSCin07838
|
Cannot invoke CiscoWorks if you start Daemon immediately.
|
Cannot invoke CiscoWorks if you stop the Daemon Manager and restart it immediately.
Workaround:
Do not restart the Daemon Manager immediately after stopping it. You must wait for some time for the ports to be released.
|
CSCin16992
|
EDS displays errors when you change the hostname.
|
The errors appear if you change the hostname without restarting the daemons.
Workaround:
See the following link:
http://cisco.com/en/US/products/sw/cscowork/ps3996/products_user_guide_chapter09186a008017b74c.html#wp1078582
|
CSCsa24624
|
Apache does not start after installation, if the kernel parameters are not configured,
|
If the kernel parameters are not configured, Apache process does not start and results in a core dump.
This occurs when the shmget system call fails.
Workaround:
Configure the semaphore and shared memory-related kernal parameters in /etc/system file.
|
CSCsa24921
|
Packet capture status displays wrong messages if the packet capture time is less.
|
When device IP is not reachable, the Packet Capture status window displays wrong messages. This occurs if packet capture time is less.
Workaround:
Do packet capture for a longer time.
|
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.
|
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.
|
CSCec82508
|
When multiple community string support is enabled on Campus Manager, the devices become unreachable in topology.
|
This problem 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.
|
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.
|
CSCsa12204
|
Cannot restore if you take backup on a mounted directory from GUI.
|
Restore displays the following error:
Cannot find the generation in the backup
directory [<backup Directory>].
Verify the backup directory and the
generation.
This occurs under the following conditions:
1. When backup is taken in one server (Server A).
2. Restore in another server (Server B).
3. Backup directory of Server A is mounted in Server B, which is used for restore.
Workaround:
Give read permission to Backup Director for Others in the Backup Server (Server A).
|
CSCsa24015
|
Evaluation license expires few hours before the default 90 days period.
|
This problem occurs when the Time Zone TZ value in /etc/TIMEZONE is set as GMT+5 then CiscoWorks applications installed in Evaluation mode will expire 5 hours before 90 days.
Workaround:
Set the time zone opposite to the one that is actually required and restart the machine.
For example, if GMT+5 is the required time zone then set the time zone to GMT-5.
|
CSCsa03997
|
Shortcuts to links are not preserved after upgrade.
|
The shortcuts that you create in CS 2.2, are not preserved when you upgrade to CS 3.0.
Workaround:
None.
|
CSCsa38716
|
Management Statement To Device picks up the altered port value from the etc/services file.
|
This occurs when the third-party SNMP agent changes the standard SNMP port value. The Management Statement To Device picks up this altered port value, queries the device and fails.
Workaround:
Make sure that the SNMP port value is 161.
|
CSCsa20444
|
Job state changes to Cancelled even after the job is completed successfully.
|
When you stop successfully completed jobs the status of these jobs change to Cancelled.
This occurs when you:
1. Create a job.
2. Click Stop while the job is running 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.
|
CSCsa26875
|
Error messages appear when you stop jobs.
|
When you stop jobs before their completion, some error messages with codes 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.
|
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 by entering /etc/init.d/dmgtd start
|
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.
|
CSCsa38647
|
Event Services Software (ESS) does not start.
|
This problem can occur when a machine is configured to access NIS.
Workaround:
Remove the NIS entry for services in the /etc/nsswitch.conf file.
Modify the services entry to services: files
|
CSCeg26913
|
JDK crashes and Notification Services (NOS) does not receive any NOS messages.
|
When this problem occurs:
•NOS does not receive any NOS messages.
•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.
|
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 present in the column will be displayed.
|
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.
|
CSCsc24337
|
RME uses 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.
|
CSCsc38627
|
JRM failed to run, JRM core dump created under NMSROOT.
|
While creating jobs in RME, JRM fails to run and JRM core dump is created.
This is not consistent.
Workaround:
Restart the Daemons.
|
CSCsc38669
|
While running backup.pl and restorebackup.pl, the following error appears:
ERROR: Please specify the full path name of this script.
|
This error appears only if the product was installed on the custom path and backup.pl and restorebackup.pl was run using this custom NMSROOT.
Workaround:
Use /opt/CSCOpx, instead of using custom NMSROOT.
|
CSCsc61349
|
After an upgrade from LMS 2.2 to LMS 2.5.1, some of the processes do not function correctly.
|
The EDS process does not function properly. This causes its dependant processes also to not run properly.
Sockets are not released properly after daemons are shut down.
This is an issue with Visibroker and happens rarely.
Workaround:
Run the following tool to change the EDS port:
NMSROOT/bin/perl NMSROOT/bin/ChangeOSAGENT.pl
free port no
|
CSCsc69758
|
Changing login mode to Non-ACS Pluggable Authentication Modules (PAM) after restore from CS 3.0 displays Internal Server Error.
|
This error appears when you:
1. Restore from a CS Non-ACS 3.0 machine to a CS 3.0 machine.
2. Change the Login Mode to Non-ACS PAMs.
Internal Server Error is displayed.
Any subsequent upgrade or restore carried out from this machine to a CS 3.0.3 machine causes the same error.
Workaround:
1. Change the Login Mode to ACS.
2. Click Apply.
3. Change Login Mode to any Non-ACS Mode of authentication.
|
CSCsc71272
|
Internal server error appears when re-registering applications with ACS when AAA Mode is ACS.
|
This error appears when you:
•Configure Cisco Works for ACS AAA Mode.
•Create Custom roles in ACS.
•Log into CiscoWorks as ACS user with Customized role.
•Re-register applications with ACS.
Internal Server error is thrown.
Workaround:
While doing application registration in ACS mode, make sure that the logged in user has default role (non-customized role) in ACS (i.e. Group Setup > CiscoWorks in ACS server).
|
CSCsc71565
|
In CS 3.0, while registering a Test Application with CMIC, 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 CMIC.
|
In this scenario, all the xml files under registered-templates have the right port number and protocol, except for the Test Application which 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.
|
CSCsc71403
|
Changes to some Context Sensitive Online Help (OLH) files do not reflect in the CiscoWorks LMS 2.5 December 2005 Update.
|
Changes do not reflect in the following files, when you launch the OLH for CiscoWorks Common Services 3.0.3 in the CiscoWorks LMS 2.5 December 2005 Update:
•What's New in This Release (Launch Context Sensitive Online Help from CiscoWorks Homepage and go to the Common Services Online Help. Select What's new in this release from the Table Of Contents).
•Context Sensitive Online Help for Modifying Security Certificates (Common Services> Server Security Multi-Server Trust Management Peer Server Certificate Setup).
•Context Sensitive Online Help for Setting Up Browser-Server Security Mode (Server Security Single-Server Management Browser-Server Security Mode Setup).
Workaround:
The updated information for these OLH files are available in the PDF of the User Guide for CiscoWorks Common Services.
(contd.)
|
CSCsc71403
(contd.)
|
Changes to some Context Sensitive Online Help (OLH) files do not reflect in the CiscoWorks LMS 2.5 December 2005 Update.
|
To launch the PDF file:
1. Launch the Context Sensitive Online Help from CiscoWorks Homepage.
2. Select the Online Help for CiscoWorks Common Services.
3. Click View User Guide (Book PDF) from the Table Of Contents.
Read the following sections:
•For What's New in this release:
See the New Features section in Chapter 1 Overview.
•For Modifying Security Certificates:
See the Creating Self Signed Certificate section in Chapter 3 Configuring the Server.
•For Setting Up Browser - Server Security Mode:
See the Setting up Browser-Server Security section in Chapter 3 Configuring the Server.
See the User Guide for CiscoWorks Common Services 3.0.3 at
http://cisco.com/en/US/products/sw/cscowork/ps3996/products_user_guide_list.html
for all the latest updated information.
|
CSCsd21327
|
CMF database fails to run and throws the following Sybase Assertion error message:
*** ERROR *** Assertion
failed: 100909 (9.0.0.1383).
100909 is the Assertion ID.
|
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. The reason is, 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.
|
CSCsd40375
|
Australian day light settings affect the API to return time.
|
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 jobs are executed with a delay of one hour. Also, the logs and/or reports show incorrect time stamp.
The following jobs are affected:
•PSU Device Downloads.
•DCR Import/Export.
•Sample job through jobcli.
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.
|
CiscoView Known Problems
Note To view the known problems for a specific device package release, refer to the Readme file provided with that release.
Table 14 Known Problems in CiscoView 6.1.2
Bug ID
|
Summary
|
Explanation
|
None.
|
CiscoView does not support SNMPv3 credentials.
|
Since Cisco Transport Manager (CTM) does not implement a call back function for SNMPv3 credentials, this release of CiscoView cannot provide SNMPv3 support.
|
CSCea61377
|
Scrollbar is not displayed after monitoring dialog box is opened in Internet Explorer.
|
This problem occurs when you:
1. Right-click the chassis view with a device open in CiscoView
2. Select Monitor to open a monitoring dialog box.
No scrollbar appears even if the resulting dialog box is not wide enough to fully display its contents.
Workaround:
Either reduce the size of the dialog box or hide the Windows taskbar.
This problem does not occur in Netscape Navigator or Mozilla.
|
CSCea89084
|
Graphs in monitoring dialog box do not work as expected.
|
This problem occurs on AP1200 devices.
There are problems with the graphs for the following objects in the UDP monitoring dialog box (Monitor > Device > UDP):
•udpNoPorts: Y-axis interval values repeat. In addition, incremental Y-axis values are inconsistent.
•udpOutDatagrams: Y-axis interval values are congested.
Workaround:
None.
|
CSCin35001
|
Multiple selection function do not work as expected.
|
The following problems occur after making a multiple selection and right-clicking the selection, the following message is displayed:
Please select a component.
The selection you made is no longer active.
A problem also occurs if you
1. Hold down the Ctrl key when making multiple selections and right-clicking on these selections.
2. With a port already selected, you hold down Ctrl key and select a second port.
The first port is deselected.
Workaround:
Hold down the Ctrl key before selecting the first component in a multiple selection.
|
CSCdz86911
|
Apply button is enabled in read-only dialog boxes.
|
This problem occurs on AS5400 device.
1. With device selected, right-click and then select Configure > System Software.
Although the dialog box does not contain read-write objects, the Apply button is available.
2. Click Apply.
The status bar displays the message Modification Success.
Workaround:
None.
|
CSCin61471
|
Pie chart in CiscoView 6.0 monitoring dialog box displays the same color for different MIB objects.
|
When a pie chart is displayed by a monitoring dialog box in CiscoView 6.0, the MIB objects within that dialog box should be indicated by different colors.
Instead, the same color is used to indicate the various MIB objects.
Workaround:
None.
|
CSCin50997
|
JavaScript error occurs after PIX Device Manager (PDM) is launched in CiscoView 6.0.
|
This problem occurs when you:
1. Launch CiscoView 6.0 and open the chassis view for a PIX device.
2. Launch PDM.
A JavaScript error message, in addition to the authentication dialog box, appears.
Workaround:
None.
|
CSCsa33676
|
Correct icon for IPv6-enabled interfaces is not displayed.
|
This problem occurs when you:
1. Launch CiscoView and open the chassis view for a device.
2. Right-click the chassis view and select IPv6 > IPv6 System Information.
3. Click Interface Details.
4. Select a slot and an interface and click OK.
The icon that indicates whether IPv6 is enabled on an interface is not updated and the correct icon is not displayed.
Workaround:
Close and then reopen the dialog box.
|
CSCsa30779
|
Selected port/module is not completely highlighted.
|
This problem occurs when you:
1. Launch CiscoView, using Netscape Navigator and open the chassis view for either a Catalyst 3750 or 6000 device.
2. Click either a module or a port to select it.
Only the left side of the selected module/port is highlighted by a yellow border.
Workaround:
None.
This problem does not occur in Internet Explorer.
|
CSCsa39302
|
Partial discovery of device occurs.
|
This problem occurs when you:
1. Launch CiscoView and open the chassis view for a device.
2. Change the SNMP credentials of the device, while CiscoView is discovering it.
CiscoView does not complete the discovery of the device.
As a result, an incomplete chassis view is displayed. If you make any configuration changes or select any menus, errors appear.
Workaround:
Close and then reopen the chassis view.
|
CSCin76816
|
Able to install IPv6 device package in CiscoView 6.0.
|
Since IPv6 is supported only by CiscoView 6.1, you should not be able to install the IPv6 device package if you are running CiscoView 6.0. However, you can do so using Software Center.
Workaround:
None.
Although you can install the IPv6 device package in CiscoView 6.0, IPv6 functionality is available only if CiscoView 6.1 is running.
|
CSCsa35308
|
CiscoWorks server performance decreases after opening multiple monitoring dialog boxes.
|
Enhancements were made to increase server performance.
Workaround:
Refresh the browser through Ctrl+R or F5.
|
CSCsa28414
|
All installed CiscoView device packages are loaded during a Tomcat startup.
|
On a low-end machine (for example, one with a 600 MHz CPU and 512 MB of RAM), a Tomcat restart takes around 2-3 minutes.
While restarting, CiscoView loads all installed device packages.
Workaround:
None.
|
CSCin40139
|
Blank monitoring dialog box was displayed after a 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.
|
CSCsb88722
|
Cannot install packages in Solaris Server through GUI.
|
This problem occurs while installing device packages if there is insufficient RAM space.
Workaround:
None.
|
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:
Launch the chassis view for those devices in CiscoView.
|
Known Problems in CiscoView Mini-RMON Manager 2.0
Table 15 Known Problems in CiscoView Mini-RMON Manager 2.0
Bug ID
|
Summary
|
Additional Information
|
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.
|
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.
|
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.
|
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.
|
CSCsa76938
|
Devices of unknown type 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.
|
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.
|
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.
|
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.
|
CSCsb07791
|
Cannot modify history entry on Catalyst 2916MXL device.
|
When attempting to modify a history entry from the Statistics page (Setup > Statistics History) on a Catalyst 2916MXL device, an error message appears and the entry is not modified.
Workaround:
None.
See CSCin93091, the corresponding SNMP agent problem, for more information.
|
CSCsa70049
|
Devices are sometimes listed twice in the Object Selector.
|
This problem occurs inconsistently and does not affect functionality.
Workaround:
None.
|
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 Resolved Problems in CiscoView 6.1.2
Bug ID
|
Summary
|
Additional Information
|
CSCsa38535
|
CiscoView 6.1 displayed IP address instead of device name in Device Name/IP field.
|
This problem has been resolved.
|
CSCin79203
|
CiscoView sometimes displayed partial table values.
|
This problem has been resolved.
|
CSCin44398
|
Code column entries in VoIP Peer Configuration dialog box were not fully displayed.
|
This problem has been resolved.
|
CSCsa37082
|
Grouping Services exception was listed in stdout.log file.
|
This problem has been resolved.
|
CSCsb05748
|
Could not modify alarms on some devices.
|
This problem has been resolved.
|
Internally-Found Resolved Problems
Table 17 Internally-Found Resolved Problems
Bug ID
|
Summary
|
Additional Information
|
CSCin36414
|
Installation or uninstallation aborted during dependency check.
|
This problem has been resolved.
|
CSCin24499
|
dbRestoreOrig.pl could not validate the values for dsn and dmprefix parameters.
|
This problem has been resolved.
|
CSCdz84877
|
TIB/Rendezvous (Tibco) process used lot of memory space.
|
This problem has been resolved.
|
CSCdx28510
|
Uninstallation of CS 2.2 did not remove some directories under /opt/CSCOpx.
|
This problem has been resolved.
|
CSCea59420
|
The interface link in the Management Station to Device screen broke if the client used the hostname to access the server.
|
This problem has been resolved.
|
CSCeb49238
|
Tomcat heap size shortage.
|
This problem has been resolved.
|
CSCdz53375
|
Configuration dialog box was sometimes hidden when launched.
|
This problem has been resolved.
|
CSCea14488
|
Common Services did not function if host name changed.
|
This problem has been resolved.
|
CSCin41906
|
CiscoWorks applications that used Java Plug-in could not be launched from NNM 6.4 web console.
|
This problem has been resolved.
|
CSCin44573
|
The database password changed when you tried to restore after a backup operation.
|
This problem has been resolved.
|
CSCeb44684
|
PIX MC pages were not displayed.
|
This problem has been resolved.
|
CSCeb08489
|
Login panel displayed the username of the previous user and inherited the privileges of this user.
|
This problem has been resolved.
|
CSCeb08436
|
The ESS process of CiscoWorks broadcasted on UDP port 42350.
|
This problem has been resolved.
|
CSCea49922
|
Error occured after clicking and then right-clicking on AS5400 device component.
|
This problem has been resolved.
|
CSCea63238
|
Could not change administrative status when multiple ports were selected.
|
This problem has been resolved.
|
CSCin36951
|
CiscoView attempted to set values for read-only objects.
|
This problem has been resolved.
|
CSCin35050
|
Monitoring dialog box for multiple port selection in CiscoView 6.0 displayed incorrect values.
|
This problem has been resolved.
|
CSCin38886
|
Device view was not shown if Object Selector was closed before a device was opened.
|
This problem has been resolved.
|
CSCin50995
|
Monitoring dialog box for multiple ports did not act as expected.
|
This problem has been resolved.
|
CSCea89091
|
Updates to display string objects in System Information dialog box were not applied.
|
This problem has been resolved.
|
CSCin04752
|
Could not launch StackMaker Online Help from CiscoView.
|
This problem has been resolved.
|
CSCin17978
|
Daemon Manager pdterm displayed an invalid error message.
|
This problem has been resolved.
|
CSCdz03228
|
Many log files did not print timestamp within Ciscoworks.
|
This problem has been resolved.
|
CSCsa31336
|
Exceptions occured in DCR CLI when Daemon Manager is down.
|
This problem has been resolved.
|
CSCsa41274
|
CiscoWorks processes that used Core Client Registry (CCR) API crashed.
|
This problem has been resolved.
|
CSCin63122
|
Management to Station GUI could not handle special characters as input for SNMPv3 parameters.
|
This problem has been resolved.
|
CSCsa13198
|
Modified RoleDefinition did not get updated to ACS when you register ed an application for the second time with ACS.
|
This problem has been resolved.
|
CSCsa06021
|
Installation might fail if the CD-ROM is mounted incorrectly.
|
This problem has been resolved.
|
CSCsa44801
|
Devices of a group with INCLUDELIST in their rule did not appear in the DCR device selector.
|
This problem has been resolved.
|
CSCsa44161
|
Updation of group with empty rules in CS 3.0 did not appear in application Group Admin screen.
|
This problem has been resolved.
|
CSCsa44158
|
DCR device selector displayed only first level groups in User Defined groups.
|
This problem has been resolved.
|
CSCsa82899
|
Tomcat did not run because of CCR exception.
|
This problem has been resolved.
|
Customer-Found Resolved Problems
Table 18 Customer-Found Resolved Problems
Bug ID
|
Summary
|
Additional Information
|
CSCdt18555
|
CD One did not have the option of configuring a remote mail gateway if sendmail was not running on UNIX platforms where CiscoWorks was installed.
|
This problem has been resolved.
|
CSCdy04158
|
No recovery procedure for CiscoWorks, when CD One, 5th Edition upgrade failed.
|
This problem has been resolved.
|
CSCin50393
|
The CiscoWorks Common Services SSH Client did not connect to some devices.
|
This problem has been resolved.
|
CSCdt52492
|
Applications did not always launch from NMS menu if a browser was not already running.
|
This problem has been resolved.
|
CSCdt73198
|
CiscoWorks froze when network connection was removed.
|
This problem has been resolved.
|
CSCdy78441
|
CiscoWorks did not have the capability to perform the basic diagnostic functions.
|
This problem has been resolved.
|
CSCdy79475
|
Backup.pl would execute only when you stopped the Daemon Manager.
|
This problem has been resolved.
|
CSCea62163
|
CiscoWorks ticker window did not work when proxy was configured on network.
|
This problem has been resolved.
|
CSCsa96543
|
Log permissions set incorrectly during installation.
|
This problem has been resolved.
|
CSCsb18734
|
Ciscoworks Application registration with ACS failed.
|
This problem has been resolved.
|
CSCsb19476
|
Transfer of files greater than 32MB using TFTP did not work while:
•Copying from RME server to device.
•Copying from device to RME server.
|
This problem has been resolved.
|
CSCsb47462
|
Online help displayed the incorrect location for collect server info. files.
|
This problem has been resolved.
|
CSCsb82228
|
Restriction for maximum time-out value in SNMP library needed to be removed.
|
This problem has been resolved.
|
CSCsb01832
|
dcrcli did not work when invoked within a script.
|
This problem has been resolved.
|
CSCsb04470
|
Ciscoworks update utility continued to list the updates that were already installed.
|
This problem has been resolved.
|
CSCdt43248
|
Install did not prompt you whether or not you should restart Daemon Management while installing CiscoWorks components.
|
This problem has been resolved.
|
CSCsa53026
|
RME dmprefix and database engine names were incorrect in dbRestoreOrig.pl.
|
This problem has been resolved.
|
CSCei06602
|
DCRServer process did not start because of corrupted regdaemon.xml file.
|
This problem has been resolved.
|
CSCsb48713
|
The SNMP Walk utility within CiscoWorks' Device Center truncated results output at 1024 Kilo Bytes.
|
This problem has been resolved.
|
CSCsa56357
|
CS 3.0. upgrade failed while upgrading from cdone 2.0 > cdone 2.1/cdone 2.2 > CS 3.0.
|
This problem has been resolved.
|
CSCsb07777
|
cwcli displayed an error message such as log4j:ERROR setFile(null,true) call failed.
|
This problem has been resolved.
|
CSCsb56273
|
OGS needed a provision to delete groups created by other users.
|
This problem has been resolved.
|
CSCsa86425
|
Could not apply SMTP, RCP User, and proxy settings in LMS 2.5.
|
This problem has been resolved.
|
CSCsb29116
|
enhance runme.sh should have reported error if owner is not casuser.
|
This problem has been resolved.
|
CSCsb91496
|
Could not add or edit user defined groups under Group Admin.
|
This problem has been resolved.
|
CSCsb92143
|
User Defined fields could not be exported/imported.
|
This problem has been resolved.
|
CSCsa89279
|
Buttons at the bottom of the Bulk Import window in DCR were not visible.
|
This problem has been resolved.
|
CSCsa90119
|
LMS 2.5 installation/uninstallation hung because of numerous yes.sol processes occupying CPU.
|
This problem has been resolved.
|
CSCsb37604
|
Message for mismatch of applications in LMS2.5 needed to be modified.
|
This problem has been resolved.
|
CSCsb63266
|
When Import from Remote NMS failed, RME reported the reason for failure incorrectly.
|
This problem has been resolved.
|
CSCsb97079
|
Audit log did not reflect unsuccessful login attempts.
|
This problem has been resolved.
|
CSCsa93458
|
CiscoWorks processes that used CCR APIs displayed an error and crashed because the Core Client Registry (CCR) API crashed.
|
This problem has been resolved.
|
CSCsb39085
|
Applications such as Campus Manager that use the Java Plug-in could not be installed as normal (non-root or non-Administrator) users.
|
This problem has been resolved.
|
CSCsa99960
|
Could not add username with fewer than five characters in LMS 2.5.
|
This problem has been resolved.
|
CSCsa52301
|
Discovery went into an infinite loop when Multiplexing and Multiple community were enabled.
|
This problem has been resolved.
|
CSCsb05729
|
Java Plug-in 1.4.2_06-sparc.tar.gz pam.sh did not have execute permission.
|
This problem has been resolved.
|
CSCsa56067
|
Configuring Microsoft SMTP Server with a valid name or IP address failed on CiscoWorks Server.
|
This problem has been resolved.
|
CSCsb07694
|
Custom roles in ACS were overwritten on application/SP installation.
|
This problem has been resolved.
|
CSCsa83444
|
dcrcli did not allow import data to overwrite existing DCR values.
|
This problem has been resolved.
|
CSCsb29106
|
Needed to upgrade Java Plug-in version.
This was caused by a security vulnerability in the implementation of JRE in the Java Plug-in shipped by Common Services.
|
This problem has been resolved.
|
CSCsa89029
|
Proxy settings required a username and password to be set.
|
This problem has been resolved.
|
CSCsa89294
|
Setting up a proxy broke other applications.
|
This problem has been resolved.
|
CSCeh70483
|
Management Station to Device had the domain field populated for all devices with Cisco.com.
|
This problem has been resolved.
|
CSCsa91963
|
Using community string with special characters failed in Management Station.
|
This problem has been resolved.
|
CSCsa71689
|
LWMS called System.exit() if cookie validation failed.
|
This problem has been resolved.
|
Resolved Problems in CS 3.0 Service Pack 2
Table 19 Resolved Problems in CS 3.0 Service Pack 2
Problem
|
Description
|
Explanation
|
Backup and Restore Related Resolved Problems
|
CSCsb02717
|
Restore failed while restoring certificate.
|
This problem has been resolved.
|
CSCsa38245
|
XML maintree and EDS filter needed to be removed from Backup and Restore.
|
This problem has been resolved.
|
Security Related Resolved Problems
|
CSCsb01881
|
User management operations for CiscoWorks Local user needed to be logged in Audit logs.
|
This problem has been resolved.
|
DCR Related Resolved Problems
|
CSCsa85415
|
Incorrect device icons used for security devices.
|
This problem has been resolved.
|
CSCsa48533
|
Device tree is missing after initialization.
|
This problem has been resolved.
|
CSCsa62916
|
Import from ACS fails if device does not have IP address.
|
This problem has been resolved.
|
CSCeh53870
|
Incorrect spelling in import status error message.
|
This problem has been resolved.
|
CSCeh78389
|
JOS DCR Scheduled Import jobs caused internal server error.
|
This problem has been resolved.
|
CSCsa96498
|
DCR logging had to be changed for Start and Stop services and events.
|
This problem has been resolved.
|
CSCsa78299
|
If the number of device groups in DCR device selector increased, it took a long time to select the root node.
|
This problem has been resolved.
|
Install Related Resolved Problems
|
CSCsb07645
|
Prompt needed to be removed while changing casuser attributes.
|
This problem has been resolved.
|
Process Management Related Resolved Problems
|
CSCsa64386
|
DM warning had to be changed during startup.
|
This problem has been resolved.
|
Software Center Related Resolved Problems
|
CSCsa39122
|
Inconsistent behavior if dependent packages across applications were not selected for download through Software Center > Software Updates.
|
This problem has been resolved.
|
CSCsa73676
|
Software Center did not automatically pick the dependent packages.
|
This problem has been resolved.
|
CSCsa73649
|
Incorrect version reported for missing base package(s) of device updates.
|
This problem has been resolved.
|
CSCsa80117
|
Software Center did not report failed installation of packages on the UI.
|
This problem has been resolved.
|
CSCsa70667
|
Software Center CLI did not have the option to display the list of dependent packages for a specified psu package.
|
This problem has been resolved.
|
CSCsa88729
|
Software Center > Device Update operation failed when attempting large updates.
|
This problem has been resolved.
|
CSCsa93475
|
Notification needed to inform you to manually install Software update.
|
This problem has been resolved.
|
CSCsb01970
|
Sanctify application registration / unregistration with Software Center.
|
This problem has been resolved.
|
CSCsb17998
|
Software Updates did not work as expected in CiscoView.
|
This problem has been resolved.
|
SNMP Related Resolved Problems
|
CSCin88982
|
Did not resolve hostnames containing ''-'' in IP address.
|
This problem has been resolved.
|
JRM Related Resolved Problems
|
CSCsa86805
|
Canceling a running periodic job remained in the GettingCanceled state for ever.
|
This problem has been resolved.
|
CSCsb41959
|
Error while locking and unlocking JRM.
|
This problem has been resolved.
|
Resolved Problems in CS 3.0 Service Pack 1
Table 20 Resolved Problems in CS 3.0 Service Pack 1
Problem
|
Description
|
Explanation
|
Admin Related Resolved Problems
|
CSCsa88296
|
Proxy server port validation needed to be set in the range 1-65535.
|
This problem has been resolved.
|
DCR Related Resolved Problems
|
CSCsa16158
|
Auto Update Server (AUS) device addition did not have Username, Password, and Enable Password.
|
This problem has been resolved.
|
CSCsa23143
|
Support for CNS Configuration Engine and CNS Devices was not provided.
|
This problem has been resolved.
|
CSCsa52333
|
Needed to prompt for HTTP credentials in Device and Credential Repository (DCR) GUI.
|
This problem has been resolved.
|
Software Center Related Resolved Problems
|
CSCsa52966
|
Needed to prompt for Cisco.com and Proxy credentials when performing software downloads.
|
This problem has been resolved.
|
CSCsa55959
|
MDF-PSU Adapter code did not remove MDF cache.
|
This problem has been resolved.
|
CSCsa70185
|
Software Center detected only Readme files that had .README extension.
|
This problem has been resolved.
|
CSCeh38707
|
During validation of the Cisco.com credentials, an attempt was made to connect to www.cisco.com/en/US/partner site.
|
This problem has been resolved.
|
Event Services Related Resolved Problems
|
CSCeg62066
|
Tibco did not support publishing or subscribing to MapMessages.
|
This problem has been resolved.
|
CSCsa42779
|
Minor issues while receiving jms messages.
|
This problem has been resolved.
|
CSCsa59368
|
CS needed to enable LWMS gateway on Tomcat startup.
|
This problem has been resolved.
|
JRM Related Resolved Problems
|
CSCsa37866
|
JobType needed display value.
|
This problem has been resolved.
|
CSCsa49724
|
Could not connect to JRM; tasks such as List Jobs hung.
|
This problem has been resolved.
|
Install Related Resolved Problems
|
CSCsa63439
|
CS Service Packs did not support uninstallation.
|
This problem has been resolved.
|
Backup and Restore Related Resolved Problems
|
CSCsa12929
|
PERL applications in CiscoWorks that required fork() emulation or large file support did not work.
|
This problem has been resolved.
|
Security Related Resolved Problems
|
CSCsa50470
|
Authorization error in DBreader when logged into any Common Services server with Fully Qualified Domain Name (FQDN).
|
This problem has been resolved.
|
General Resolved Problems
|
CSCef95618
|
Common Services should have compiled and shipped with JDOM 1.0 instead of beta8.
|
This problem has been resolved.
|
CSCsa52301
|
Discovery went into an infinite loop when Multiplexing and Multiple community were enabled.
|
This problem has been resolved.
|
Obtaining Documentation
Cisco documentation and additional literature are available on Cisco.com. Cisco also provides several ways to obtain technical assistance and other technical resources. These sections explain how to obtain technical information from Cisco Systems.
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
Cisco documentation and additional literature are available in the Product Documentation DVD package, which may have shipped with your product. The Product Documentation DVD is updated regularly and may be more current than printed documentation.
The Product Documentation DVD is a comprehensive library of technical product documentation on portable media. The DVD enables you to access multiple versions of hardware and software installation, configuration, and command guides for Cisco products and to view technical documentation in HTML. With the DVD, you have access to the same documentation that is found on the Cisco website without being connected to the Internet. Certain products also have .pdf versions of the documentation available.
The Product Documentation DVD is available as a single unit or as a subscription. Registered Cisco.com users (Cisco direct customers) can order a Product Documentation DVD (product number DOC-DOCDVD=) from Cisco Marketplace at this URL:
http://www.cisco.com/go/marketplace/
Ordering Documentation
Beginning June 30, 2005, registered Cisco.com users may order Cisco documentation at the Product Documentation Store in the Cisco Marketplace at this URL:
http://www.cisco.com/go/marketplace/
Nonregistered Cisco.com users can order technical documentation from 8:00 a.m. to 5:00 p.m. (0800 to 1700) PDT by calling 1 866 463-3487 in the United States and Canada, or elsewhere by calling 011 408 519-5055. You can also order documentation by e-mail at tech-doc-store-mkpl@external.cisco.com or by fax at 1 408 519-5001 in the United States and Canada, or elsewhere at 011 408 519-5001.
Documentation Feedback
You can rate and provide feedback about Cisco technical documents by completing the online feedback form that appears with the technical documents on Cisco.com.
You can send comments about Cisco documentation to bug-doc@cisco.com.
You can submit comments by using the response card (if present) behind the front cover of your document or by writing to the following address:
Cisco Systems
Attn: Customer Document Ordering
170 West Tasman Drive
San Jose, CA 95134-9883
We appreciate your comments.
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 can perform these tasks:
•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 and notices for Cisco products is available at this URL:
http://www.cisco.com/go/psirt
If you prefer to see advisories and notices as they are updated in real time, you can access a Product Security Incident Response Team Really Simple Syndication (PSIRT RSS) feed from 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 might have identified a vulnerability in a Cisco product, contact PSIRT:
•Emergencies — 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 non emergencies.
•Non emergencies — 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 to encrypt any sensitive information that you send to Cisco. PSIRT can work from encrypted information that is compatible with PGP versions 2.x through 8.x.
Never use a revoked 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.
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 (CPI) tool to locate your product serial number before submitting a web or phone request for service. You can access the CPI tool from the Cisco Technical Support & Documentation website by clicking the Tools & Resources link under Documentation & Tools. Choose Cisco Product Identification Tool from the Alphabetical Index drop-down list, or click the Cisco Product Identification Tool link under Alerts & RMAs. The CPI 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.
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)—Your 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 operation 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 your network is impaired, but 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.
•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 Cisco Systems technical user magazine for maximizing Internet and networking investments. 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 access Packet magazine at this URL:
http://www.cisco.com/packet
•iQ Magazine is the quarterly publication from Cisco Systems designed to help growing companies learn how they can use technology to increase revenue, streamline their business, and expand services. The publication identifies the challenges facing these companies and the technologies to help solve them, using real-world case studies and business strategies to help readers make sound technology investment decisions. You can access iQ Magazine at this URL:
http://www.cisco.com/go/iqmagazine
or view the digital edition at this URL:
http://ciscoiq.texterity.com/ciscoiq/sample/
•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 for networking professionals to 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
•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
This document is to be used in conjunction with the documents listed in the "Product Documentation" section.
Copyright ©1998-2005, Cisco Systems, Inc.
All rights reserved.
