Table Of Contents
Release Notes for CiscoWorks Common Services 3.0 (Includes CiscoView 6.1) on Solaris
Critical Upgrade Information
Running the Script
New Features
New Features for CiscoView
CiscoWorks Common Services Documentation
Time Zone Acronyms and Offset Settings
Multi-homed Machines
Operating System Upgrade
Support Information
Java Support
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
General Known Problems
CiscoView Known Problems
Internally-Found Resolved Problems
Customer-Found Resolved Problems
Obtaining Documentation
Cisco.com
Ordering Documentation
Documentation Feedback
Obtaining Technical Assistance
Cisco Technical Support Website
Submitting a Service Request
Definitions of Service Request Severity
Obtaining Additional Publications and Information
Release Notes for CiscoWorks Common Services 3.0 (Includes CiscoView 6.1) on Solaris
This release note is for CiscoWorks Common Services 3.0 running on a Solaris platform.
The release note contains the following sections:
•
Critical Upgrade Information
•New Features
•New Features for CiscoView
•CiscoWorks Common Services 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 Documentation
•Obtaining Technical Assistance
•Obtaining Additional Publications and Information
Critical Upgrade Information
If you have upgraded from CD One, 4th Edition to CD One, 5th Edition or CiscoWorks Common Services 2.2 and now want to upgrade to CiscoWorks Common Services 3.0, you should run the script check_pkg_errors.sh, for the upgrade to be successful. This script is available at:
http://www.cisco.com/pcgi-bin/tablebuild.pl/cw2000-cd-one
Caution If you upgrade to CiscoWorks Common Services 3.0 without running the script, upgrade fails with a package verification failure in CSCOnmcs package in Solaris.
Running the Script
You can download the check_pkg_errors.sh script from
http://www.cisco.com/pcgi-bin/tablebuild.pl/cw2000-cd-one
To run the script:
Step 1 Enter the following command to check and display package errors.
sh dir/check_pkg_errors.sh
where dir is the directory to which you downloaded the script.
Step 2 Enter the following command to fix the package errors:
sh dir/check_pkg_errors.sh -c
The script logs the output to the /var/tmp/ciscoinstall.log file.
New Features
The new features in CiscoWorks Common Services Release 3.0 are:
•The CiscoWorks Homepage
Provides launch points for the CiscoWorks products and other resources. The HTML-based CiscoWorks homepage replaces the Java applet-based desktop and login.
•Device and Credential Repository (DCR)
Provides a central place for managing devices and their credentials that the different applications can use. Enables sharing of devices and credentials for common administration.
•Device Center
Allows you to troubleshoot a device. It gives you a summary of the device and the various tools, reports, and tasks that can be performed on a selected device.
•Groups
Allows applications to create shared device groups. It provides grouping facility based on various attributes in Device and Credentials Repository.
•Software Center
Enables you to download software patches and device packages, and deploy device packages.
•Enhanced security to support SNMPv3 authNoPriv
Provides packet level security, integrity protection, and replay protection. However, it does not encrypt the packets.
•Single Sign-On
On enabling Single Sign-On (SSO), you can use your browser session to transparently navigate to multiple CiscoWorks Servers without authenticating to each of them.
•Enhanced restore framework.
Enables Common Services and its applications to restore backed up data from an earlier version.
•Security mechanisms for managing security in Single-Server and Multi-Server scenarios. Granular role based access.
•New utilities for diagnosing problems with CiscoWorks server and managing log files.
•New licensing framework.
•Support for Internet Protocol version 6 (IPv6) Phase 1.
•HTML and Javascript based Online help.
New Features for CiscoView
CiscoView 6.1 contains the following new features:
•IPv6 functionality. When the IPv6 device package is installed, CiscoView manages IPv6 functionality using Telnet/SNMP over IPv4 transport using dual stacks.
Note For a list of devices on which CiscoView supports IPv6 functionality, see the IPv6 device package readme file on Cisco.com.
•Device list and credentials from a common database.
•SNMP version 3 (SNMPv3) support.
•HTML-based client. CiscoView provides a lightweight, HTML-based client with added support for Netscape, Mozilla, and SSL.
•Integration with Access Control Server (ACS) for finer granularity in user roles.
•Integration with Software Center.
Note The functionality provided by Software Center was provided in previous releases of CiscoWorks Common Services by Package Support Updater (PSU).
•New user interface.
CiscoWorks Common Services 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 and
•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 with CORBA, only one IP address can be used by the client/browser to access the server. You must select one IP address as the external address, with which the client will login to the CiscoWorks server.
To select an IP address, modify the gatekeeper file located in /opt/CSCOpx/lib/vbroker/gatekeeper.cfg.
Replace every instance of external-IP-address with the external IP address you choose, and remove the "#" character, from the following:
•#vbroker.gatekeeper.backcompat.callback.host=external-IP-address
•#vbroker.se.exterior.host=external-IP-address
•#vbroker.se.iiop_tp.host=external-IP-address
•#vbroker.se.interior.host=external-IP-address
After modifying the gatekeeper file, restart the Daemon Manager by entering
/etc/init.d/dmgtd start
Operating System Upgrade
If you upgrade the operating system after CiscoWorks Common Services is installed, you must re-install CiscoWorks Common Services.
Re-installing CiscoWorks Common Services will allow the installation process to check 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
CiscoWorks supports the following:
•Operating System—CiscoWorks Common Services 3.0 supports only US-English and Japanese versions of Solaris Operating Systems. It does not support any other language version. Set the default locale to US-English for US-English version and Japanese for Japanese version.
–Solaris 2.8 and Solaris 2.9.
Note We recommend that you install the Solaris Operating System in entire distribution mode.
•Browser—CiscoWorks supports both the English and Japanese versions of the following browsers:
–On Windows and Windows XP clients—Microsoft Internet Explorer 6.0 (version 6.0.2600.0000) or Internet Explorer 6.0 with Service Pack 1 (version 6.0.2800.1106), Netscape Navigator 7.1, and Mozilla 1.7.1
–On Solaris clients—Netscape Navigator 7.0 for Solaris 2.8 and 2.9, and Mozilla 1.7 for Solaris 2.8 and 2.9.
•Hardware:
–For Server system—CiscoWorks Common Services supports Sun UltraSPARC10.
It also supports Ultra SPARC II, IIi, and IIe and Ultra SPARC III and III Cu machines.
–For Client system—CiscoWorks supports IBM system with at least a 300 MHz Pentium processor running Windows (Professional and Server), or Windows XP SP1.
It also supports UltraSPARC 10 running Solaris 2.8 or 2.9.
•Memory (RAM):
–For Server system—512 MB (to install all CiscoWorks Common Services components).
–For Client system—256 MB.
Java Support
Certain applications use the browser's native Java Virtual Machine (JVM), while others use Sun's Java Plug-in. In order for CiscoWorks to function correctly, you must use the correct version of Java.
The supported native JVM versions are:
•JVM 5.0.0.3802 or later
•Java Plug-in version 1.4.2_04
Note Java Plug-in 1.4.2_04 might allow an untrusted applet to change the user privileges including read and write permissions. This problem has been fixed in Java plugin 1.4.2_06. For more details, see Sun Alert ID: 57591.
You can modify your CiscoWorks installation to use Sun Java Plug-in 1.4.2_06. For more details, see the Using Sun Java Plug-in 1.4.2_06 section Installation and Setup Guide for Campus Manager 4.0 on Solaris or Installation Guide for Internetwork Performance Monitor 2.6 as applicable.
To verify 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.
To enable the native 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 Select Enable Java checkbox.
Step 3 Restart Netscape Navigator.
To enable Java Console in Mozilla:
Step 1 Select Edit > Preferences > Advanced.
Step 2 Select Enable Java checkbox in the Advanced Preferences window
Step 3 Restart Mozilla.
Note CiscoWorks Common Services does not require JVM and Java Plug-in. However, some CiscoWorks applications may require these.
Integrating with Third-party Vendors
Use the Integration Utility to integrate Cisco device information and Cisco applications into SNMP management platforms like:
•HP Network Node Manager 6.4.
•HP Network Node Manager 7.0.
•HP 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 ensure that you have successfully completed configuring Cisco Secure ACS with the CiscoWorks server. If you have installed CiscoView after configuring the CiscoWorks Login Module to ACS mode, then CiscoView users are not granted any permissions. However, the CiscoView application is registered to Cisco Secure ACS.
CiscoWorks login modules allow you to add new users 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
Note For more information, see the following documents:
•User Guide for Cisco Secure ACS for Windows Server 3.2—See this document to understand Cisco Secure Groups, Users, Command Authorization Sets, etc.
•User Guide for CiscoWorks Common Services 3.0—See this document to understand the CiscoWorks login modes.
•User Guide for CiscoView 6.1—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
User with this role has the privilege to access network status information from the persisted data. User does not have the privilege to contact any device or schedule a job that will reach the network.
Approver
User with this role has the privilege to approve all CiscoView tasks.
Network Operator
User with this role has the privilege to perform all tasks that involve collecting data from the network. User does not have write access on the network. User can also perform all the Help Desk tasks.
Network Administrator
User with this role has the privilege to change the network. User can also perform the Network Operator tasks.
System Administrator
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 Online help for CiscoView 6.1, note the following:
•All references to Device and Credentials should read Device and Credential.
•In the CiscoWorks Server topic:
–The first bullet should read CiscoWorks Home Page.
–The seventh bullet should read Groups.
•The third sentence in the Device Management topic should read:
CiscoView displays the device list using the Groups feature, which determines the membership of a group by interpreting and applying the rule associated with a group of devices.
On page 1-11 of User Guide for CiscoView 6.1 and in the Using the Object Selector Online help topic, note the following:
•Step 2 should read: (Optional) Enter a partial IP address in the provided field and click Filter. The list is filtered to show only devices containing the string you entered. In the Object Selector screenshot, the button should read Filter, not Go.
Known and Resolved Problems
Tables 3 to 8 describe the problems known to exist in this release; Tables 10 and 11 describe the problems resolved since the last release of CiscoWorks Common Services.
Note To obtain more information about known problems, access the Cisco Software Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl (You will be prompted to log into 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
•General Known Problems`
•CiscoView Known Problems
•Internally-Found Resolved Problems
•Customer-Found Resolved Problems
Installation Known Problems
Table 3 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 CWCS 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. Abort the installation.
2. Copy the image locally.
3. Re-start installation.
|
CSCsa06021
|
Installation may fail if the CD-ROM is mounted incorrectly.
|
When you use Volume Management, Volume daemon (vold) mounts the CD-ROM as /cdrom/cdrom0, where cdrom0 is a link to volume label of the CD-ROM.
In normal circumstances, the link gets cleared after the CD-ROM is ejected. If it does not clear when you mount another CD-ROM, it is mounted as /cdrom/cdrom0. This is then linked to cdone3_0#1. This # character causes problem during installation.
To verify whether the directory name has a # character appended to its name, navigate to the /cdrom/cdrom0 directory, and check the present working directory using the pwd command.
Workaround:
1. Unmount the CD drive using umount command.
2. Eject the CD-ROM using eject command.
3. Stop the vold by entering /etc/init.d/volmgt stop.
4. Start the vold by entering /etc/init.d/volmgt start.
5. Delete the contents of /cdrom0 directory.
The CD-ROM will now mount normally.
|
CiscoWorks Homepage Known Problems
Table 4 CiscoWorks Homepage Known Problems
Bug ID
|
Summary
|
Explanation
|
CSCin39993
|
Java Plug-in 1.4.2_04 installation modifies directory owner permissions.
|
Java Plug-in tar file is copied into a temporary location (/tmp) and tar xvf plugin-14204-sparc.tar is executed.
The ownership permissions of the directory /tmp change, causing problems in the product functioning.
Workaround:
•Use a sub-folder under /tmp to un-tar.
or
•Use /usr/sbin/tar xvfo plugin-14204-sparc.tar to un-tar the file.
|
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 choosing 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 5 Software Center Known Problems
Bug ID
|
Summary
|
Explanation
|
CSCdt04070
|
No error message appears when network connection is lost during the download of device packages.
|
An error message does not appear if the network connection is lost when you download device packages from Cisco.com.
Workaround:
None.
|
CSCsb01970
|
Software Center framework does not sanctify application registration and un-registration
|
Inconsistent and unexpected behavior observed in Common Services > Software Center flows.
This includes Internal Server Error, which appears when you launch the screens.
This is observed after various combinations of uninstallation, reinstallation, and upgrade of Ciscoworks Applications (like IPM).
Workaround:
1. Open: $NMSROOT\lib\classpath\com\cisco\nm\xms\
psu\conf\tag.properties file
where $NMSROOT is the CiscoWorks installed directory
2. Remove additional empty lines between entries, if any.
3. Remove duplicate entries manually.
4. Restart the Daemon Manager
Or
Install Common Services 3.0 Service Pack 2.
CS 3.0 SP 2 is available at:
http://www.cisco.com/pcgi-bin/tablebuild.pl/cw2000-cd-one
|
CSCsa39122
|
Inconsistent behaviour when you install inter-dependant packages. from GUI.
|
This problem occurs when you:
1. Install a package that depends on another package of a different product.
2. Do not select the package of a different product.
Workaround:
1. Download the packages to a server side directory through CLI or GUI.
2. Install the packages.
3. In the GUI, select the required dependant package.
Or
Install Common Services 3.0 Service Pack 2.
CS 3.0 SP 2 is available at:
http://www.cisco.com/pcgi-bin/tablebuild.pl/cw2000-cd-one
|
CSCsa30274
|
In LMS 2.5, psucli.sh/psucli.exe deletes some 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.
|
CSCin66811
|
Inaccurate scheduling occurs if Time zone is not set.
|
This occurs when the takes the default Time zone when it is not set properly.
Workaround:
Ensure that the TZ environment is accurate.
|
CSCsa30580
|
Software Center does not accept Cisco.com login credentials with white spaces characters.
|
Software Center will not accept the customer's Cisco.com password if it contains white spaces 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, you will see the list of available packages.
–In Internet Explorer, you will see the default screen.
The device package headers will be downloaded to temporary folder.
Workaround:
To cleanup the temporary download location explicitly:
1. Stop the Daemons services:
–In Solaris, enter /etc/init.d/dmgtd stop.
–In Windows, enter net stop crmdmgtd.
2. Remove the contents of the directory under NMSROOT/ temp/psu.
3. Restart the Daemon services.
–In Solaris, enter /etc/init.d/dmgtd start.
–In Windows, enter net start crmdmgtd.
|
CSCsa89029
|
Proxy settings require a username and password to be set.
|
Common Services > Software Center does not allow download to proceed, if a non authenticating proxy server is configured in Server > Security > Proxy Settings UI.
This will happen only if you configure a non authenticated proxy server.
Workaround:
Enter dummy characters for the proxy username and password fields.
Or
Install Common Services 3.0 Service Pack 2.
CS 3.0 SP 2 is available at:
http://www.cisco.com/pcgi-bin/tablebuild.pl/cw2000-cd-one
|
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 6 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 and IBM 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, your 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.
|
Browser Known Problems
Table 7 Browser Known Problems
Bug ID
|
Summary
|
Explanation
|
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.
|
None.
|
If you have a popup-blocker enabled in your browser, popups will not appear.
|
For popups to appear, you have to 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.
|
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.
|
General Known Problems
Table 8 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.
|
CSCsa41274
|
CiscoWorks processes that use Core Client Registry (CCR) API crashes.
|
Processes like JRM crash with the following exceptions in the log file.
class com.cisco.nm.cmf.jrm.Authentication
Service :: Returning role F
An unexpected exception has been detected
in native code outside the VM.
Unexpected Signal:10 occurred at
PC=0xff0c4aa4
Library=/usr/lib/libc.so.1
at JNICCRInterface.isStale(Native Method)
at com.cisco.core.ccr.CCRInterface.
isStale(CCRInterface.java:26)
at com.cisco.core.mice.cam.CoreAdminFactory
.getModeCoreAdminFactory.java:57)
at com.cisco.core.mice.cam.CoreAdminFactory
.Produce(CoreAdminFactory.java:164)
at
com.cisco.nm.cmf.jrm.AuthenticationService.
checkTask(AuthenticationService.java:229)
at
com.cisco.nm.cmf.jrm.JrmServiceManagerImpl.
getJobHandle(JrmServiceManagerImpl.java:34)
at
com.cisco.nm.cmf.jrm.JrmServiceManagerPOA
._invoke(JrmServiceManagerPOA.java:72)
at
com.cisco.nm.cmf.jrm.JrmServiceManagerPOA
._invoke(JrmServiceManagerPOA.java:56)
0x10000 /opt/CSCOpx/bin/cwjava
0xff3a0000 /usr/lib/libdl.so.1
===========================================
Using the gdb utility on the core dump, the
stack trace is:
#0 0xff0c4aa4 in set_zone_context () from
|
CSCsa41274 (contd.)
|
CiscoWorks processes that use Core Client Registry (CCR) API crashes.
|
#1 0xff0c3ed8 in localtime () from
/usr/lib/libc.so.1
#2 0xfef045e0 in
__1cCosSreport_fatal_error6FpnMoutputStream
_pCi_v_ ()from /opt/CSCOpx/MDC/jre/lib
/sparc/client/libjvm.so
#3 0xfef049a4 in
__1cCosbBhandle_unexpected_exception6FpnGTh
read_ipCpv_v_ () from /opt/CSCOpx/MDC/jre
/lib/sparc/client/libjvm.so
#4 0xfef07fa0 in JVM_handle_solaris_signal
() from /opt/CSCOpx/MDC/jre/lib/spac/client
/libjvm.so
#5 0xff375b14 in __sighndlr () from
/usr/lib/libthread.so.1
#6 0xff36f80c in call_user_handler () from
/usr/lib/libthread.so.1
#7 <signal handler called>
#8 0xff0c4aa4 in set_zone_context () from
/usr/lib/libc.so.1
#9 0xff0c3ed8 in localtime () from
/usr/lib/libc.so.1
#10 0xff0b9cf8 in ctime () from
/usr/lib/libc.so.1
#11 0xf382e970 in
_ZN3CCR10CCRProcess11getModifiedEv
(this=0xf32a0) at CCRProcess.cpp:314
#12 0xf382ea18 in
_ZN3CCR10CCRProcess7isStaleEv
(this=0xf32a0) at CCRProcess.cpp:323
#13 0xf3828b10 in
_ZN3CCR12CCRInterface7isStaleEv
(this=0xf32a0) at CCRInterface.cpp:53
#14 0xfb697a34 in
Java_JNICCRInterface_isStale__
(environment=0x40a204, object=0xf2cff3dc)
at JNICCRInterface.cpp:44
Workaround:
Restart the process (and its dependent processes) using pdexec command.
|
CSCsa47100
|
Logout from a CS server is an Authentication Server fails when accessed using domain name.
|
Accessing the server in SSO AS mode with fully qualified domain name (example http://hostname.cisco.com:1741), log out does not happen.
Workaround:
1. If PX_HOST property at NMSROOT/lib/classpath/md.properties is configured with fully qualified domain name, accessing the server with fully qualified domain name will work.
But, if the PX_HOST property at NMSROOT/lib/classpath/md.properties is configured as hostname, you have to access the server without using domain name in the url you specify.
2. Close the browser window.
|
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
|
CSCsa12929
|
CS 3.0 Solaris backup fails, displaying message that the database file does not exist.
|
If the database size of any applications crosses 2 Gb, backup fails in Solaris.
Workaround:
Either:
•Reduce the size of database to less then 2 Gb, by deleting some unwanted data (if any) through the respective options in the applications.
Or
•Install Common Services 3.0 Service Pack 2.
CS 3.0 SP 2is available at:
http://www.cisco.com/pcgi-bin/tablebuild.pl/cw2000-cd-one
|
CSCsa24624
|
Apache fails to 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, Packet Capture status window appears displays wrong messages. This occurs if packet capture time is less.
Workaround:
Do a 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.
|
CSCin60293
|
SNMPv3 API accepts unsupported mode information.
|
This unexpected library behaviour occurs when noAuthNoPriv or authPriv is chosen as SNMPv3 mode.
Workaround:
Choose authNoPriv as the mode.
|
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 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.
|
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.
|
CSCin41971
|
Authentication from NMS fails for valid users.
|
This occurs when the following conditions are met:
•CWCS is installed in a multi-homed device.
•ACS/T+ server is configured as login module (through PAM).
•The primary IP address of the NMS is not configured as a client in ACS.
Workaround:
The primary IP address of the NMS should be configured 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. When the job is running click Stop button, but do not press OK in the stop confirmation UI.
3. After the jrm.log confirms the successful completion of the job, press OK.
This changes the state of the job to Cancelled.
Workaround:
None.
|
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 completion of job.
Workaround:
Stop the job again to see the proper error message.
|
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.
|
CSCin63122
|
Management to Station GUI cannot handle special characters as input for SNMPv3 parameters.
|
Errors occur when you give special characters as input for SNMPv3 parameters in the Management to Station GUI.
Workaround:
Do not enter special characters as input for SNMPv3 parameters.
|
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 option, 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 occurs when you try to export many devices using the export from file option. The time taken to export increases exponentially.
For example, for 5000 devices, it takes 20 minutes and for 10000 devices, it takes 60 minutes.
Workaround:
You can use export from device selector option.
|
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.
When there are two DCR domains, M1 with
Slaves S11 and S12, and M2 with slaves S21
and S22. Now, 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.
|
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.
|
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.
|
CSCsa13198
|
Modified RoleDefinition does not get updated to ACS when you register an application for the second time with ACS.
|
This problem occurs when you:
1. Register an application with ACS.
2. Modify the RoleDefinition by editing the RoleDefinition.xml file.
3. Unregister the application.
4. Register the application again.
The changes made to the roles will not be visible from the ACS. The ACS server maintains the RoleDefinition of the first registration.
Workaround:
Either:
•Manually edit the required roles and tasks through ACS.
Or
•Use a new ACS server with which the application has not registered before.
|
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
|
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.
|
CSCsa29023
|
If you give 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.
|
CSCsa30660
|
Deletion of a large number of devices in the master takes a lot of time.
|
This occurs when you configure a master with many slaves, and then delete a large number of devices. The changes appear after some delay.
Workaround:
None. Do not delete large number of devices at a time in the DCR master.
|
CSCsa31336
|
Exceptions occur in DCR CLI when Daemon Manager is down.
|
When Daemon Manager is down, the DCR CLI will give exceptions and authentication failure.
Workaround:
None.
|
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 will cause problems.
Workaround:
Do not include JavaScripts and special characters in the UDF labels.
|
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.
|
CSCsa40726
|
DCR accepts hostnames with periods.
|
When you add or edit devices in DCR, it accepts hostnames with periods.
Workaround:
None.
Do not enter hostnames with periods.
|
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.
|
CSCsa43396
|
DSBU 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. Now 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.
|
CSCsa38647
|
Event Services Software (ESS) fails to start.
|
This 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
|
CSCsa44158
|
DCR device selector shows only first level groups in User Defined groups.
|
This problem occurs when you create groups, under User Defined Groups, with empty rules in a hierarchal manner.
Workaround:
None.
|
CSCsa44642
|
Fewer System Defined Groups 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. Once again, configure S as a slave of M.
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 it, enter
NMSROOT/bin/pdterm CMFOGServer
2. To start it, enter
NMSROOT/bin/pdexec CMFOGServer
|
CSCsa44801
|
Devices of a group with INCLUDELIST in their rule do not appear in the DCR device selector.
|
If you create groups with a Rule Expression and an INCLUDELIST, the devices in the INCLUDELIST do not appear in the DCR device selector.
However, if the rule contains only INCLUDELIST, without any rule expressions, this problem does not occur.
Workaround:
None.
|
CSCsa44615
|
Errors appear when you change the DCR mode from slave to standalone.
|
Occasionally fatal errors occur in CMFOGSServer due to the DCR event parsing.
Workaround:
None.
|
CSCsa44161
|
Updation of group with empty rules in CS 3.0 do not appear in application Group Admin screen.
|
When you create groups with empty rules in Common Services and then edit their details, the updated changes do not appear in applications.
Workaround:
None.
|
CSCsa45024
|
Deletion of a large number of devices in the DCR GUI takes a lot of 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.
|
CSCsa44940
|
Devices do not appear in a slave when you restore from CS 2.1 and CS 2.2.
|
When you restore from CS 2.1 and CS 2.2, devices do not appear in the DCR or Group Admin UI.
Workaround:
1. Open NMSROOT/MDC/tomcat/webapps/cwhp/
WEB-INF/classes/trans.properties file.
2. Change the transaction id to -1.
3. Restart the CMFOGSServer. To do this:
To stop it, enter
NMSROOT/bin/pdterm CMFOGServer
To start it, enter
NMSROOT/bin/pdexec CMFOGServer
|
CSCeg26913
|
JDK crashes and Notification Services (NOS) does not receive any NOS messages.
|
When this problem occurs:
•NOS will not receive any NOS messages.
•Core file will be 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.
Work around:
Restart the daemon manager.
|
CSCsa47654
|
On import, devices do not show up in DCR device selector in DCR page.
|
This happens when you import devices to DCR in batches of 1000 devices consecutively, with Auto sync feature from DCR to RME enabled.
Workaround:
1. Open NMSROOT/MDC/tomcat/webapps/cwhp/
WEB-INF/classes/trans.properties file.
2. Change the transaction ID to -1.
3. Restart the CMFOGSServer. To do this:
To stop it, enter
NMSROOT/bin/pdterm CMFOGServer
To start it, enter
NMSROOT/bin/pdexec CMFOGServer
|
CSCsa82899
|
Tomcat is not running because of CCR exception.
|
The exception is detected in native code outside the VM. Check the NMSROOT/MDC/tomcat/logs/stdout.log for details.
Workaround:
None.
|
CSCsa83440
|
Cannot resize the columns in HTML scrolling tables.
|
This is the UI behavior.
Workaround:
Place the cursor on top of the text (do not click). The entire text present in the column will show up.
|
CSCsa89294
|
Setting a proxy may break certain applications.
|
Applications such as Campus Manager and Device Center may not work properly. Device Center may show a blank screen, and Campus Manager applications may fail to connect to ANIServer.
This can happen if a proxy server is configured within CiscoWorks and you run any Common Services Software Center download operation.
Workaround:
Remove the proxy server configuration, and restart CiscoWorks Daemon Manager.
Or
Install Common Services 3.0 Service Pack 2.
CS 3.0 SP 2is available at:
http://www.cisco.com/pcgi-bin/tablebuild.pl/cw2000-cd-one
|
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.
•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 9 CiscoView Known Problems
Bug ID
|
Summary
|
Explanation
|
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. During the restart, CiscoView loads all installed device packages.
Workaround:
None.
|
CSCea61377
|
Scrollbar does not appear when you open a Monitoring dialog box in Internet Explorer.
|
This problem occurs if you:
1. Have a device open in CiscoView
2. Right-click the chassis view
3. Select Monitor to open a Monitoring dialog box.
A scrollbar does not appear 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 the Monitoring dialog box do not appear as required.
|
Observed on AP1200 device. 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. Also, incremental Y-axis values are inconsistent.
•udpOutDatagrams: Y-axis interval values are congested.
Workaround:
None.
|
CSCin45650
|
DynAPI error occurs after right-clicking a component that is not associated with a menu.
|
When you right-click a component that is not associated with a menu a DynAPI error occurs.
Workaround:
None.
|
CSCin40139
|
Blank Monitoring dialog box is 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. After the dialog box opens, change the refresh rate to 5 seconds.
3. Click the Category box.
4. Wait for the next refresh takes place before you select a category.
Workaround:
None.
|
CSCin35001
|
Multiple selection function does not work as expected.
|
This problem occurs when:
•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.
Workaround:
Hold down the Ctrl key when making multiple selections and right-click on these selections.
•You hold down the Ctrl key with a port already selected and select a second port.
The first port is deselected.
Workaround:
Hold down Ctrl key before selecting the first component in a multiple selection.
|
CSCdz86911
|
Apply button is enabled in read-only dialog boxes.
|
This problem is observed on AS5400 device. It occurs when you:
1. Right-click and then select Configure > System Software after selecting a device
Although the dialog box does not contain read-write objects, the Apply button is enabled.
2. Click Apply and the status bar displays the message Modification Success.
Workaround:
None.
|
CSCsa25335
|
Cannot launch CiscoView.
|
While working in CiscoView, you may find that your CiscoWorks session has timed out or that your network has temporarily gone down.
When you start a new CiscoWorks session, launch CiscoView, this error message is added to the Tomcat server process log:
action: Looking for Action instance for class com.cisco.nm.cvw.guiservlet.CvGuicontroller EXCEPTION in GUIController.perform: java.lang.NullPointerException
Workaround:
Start a new CiscoWorks session, restart all daemons, and then launch CiscoView.
|
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.
|
CSCdu71257
|
Cannot modify read-write MIB variables in ATM RM IF Config dialog box through CiscoView 5.3.
|
This problem occurs when you:
1. Launch CiscoView 5.3 and open the chassis view for a Catalyst 8500 device.
2. Right-click the chassis view and select Configure > ATM RM Interface > ATM RM IF Config.
3. Modify any of the following read-write MIB variables and then click OK:
–rmIfOutPacingRateRequested
–mIfLinkDistance
–rmIfBestEffortLimit
The changes are not applied to these variables.
Workaround:
Modify the values for these MIB variables using SNMP.
|
CSCin40470
|
Problems with GUI elements in Syslog Configuration dialog box.
|
This problem occurs when you:
1. Launch CiscoView 6.0 and open the chassis view for a device.
2. Right-click the chassis view and select Configure > Syslog Configuration.
The Log Size and Logging Level fields are wide enough to display only one character.
Also, the check boxes and buttons in this dialog box are improperly aligned.
Workaround:
None.
|
CSCin44398
|
Code column entries in VoIP Peer Configuration dialog box are not fully displayed.
|
This problem occurs when you:
1. Launch CiscoView and open the chassis view for a Router 1700 device.
2. Right-click the chassis view and select Voice Configuration > Dial-Peer Configuration > VoIP Peer Configuration.
The Code column is not wide enough to fully display entries in that column.
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 then click OK.
The icon used to indicate whether IPv6 is enabled on an interface is not updated as expected. Thus, the correct icon does not appear.
Workaround:
Close and then reopen the dialog box.
|
CSCsa30779
|
Selected port/module is not completely highlighted.
|
This problem occurs when you:
1. Using Netscape Navigator, launch CiscoView and open the chassis view for either a Catalyst 3750 or 6000 device.
2. Click either a module or port to select it.
Only the left side of the selected module/port is highlighted by a yellow border.
Workaround:
None.
This problem does not occur in Internet Explorer.
|
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 via Software Center.
Workaround:
None. Although you can install the IPv6 device package in CiscoView 6.0, IPv6 functionality will be available only if CiscoView 6.1 is running.
|
CSCsa37082
|
Object Grouping Services (OGS) exception listed in stdout.log file.
|
After opening a new chassis view or refreshing a chassis view that is already open in CiscoView, the following exception is added to the stdout.log file:
java.io.FileNotFoundException log/OGSClient.log (No such file or directory)
at java.io.FileOutputStream.openAppend
Native Method)
at java.io.FileOutputStream.<init>
FileOutputStream.java177)
at java.io.FileOutputStream.<init>
FileOutputStream.java102)
at java.io.FileWriter.<init>
FileWriter.java61)
at org.apache.log4j.FileAppender.setFile
(FileAppender.java284)
at org.apache.log4j.RollingFileAppender.
setFile(RollingFileAppender.java198)
at org.apache.log4j.FileAppender.
activateOptions(FileAppender.java)
Workaround:
None. This does not degrade CiscoView functionality in any way.
|
CSCsa38535
|
CiscoView 6.1 displays IP address instead of device name in Device Name/IP field.
|
With the chassis view for a device open in CiscoView, the Device Name/IP field displays the IP address for that device, even if a name has been entered in the DCR.
Workaround:
None. This does not degrade CiscoView functionality in any way.
|
CSCin79203
|
CiscoView sometimes displays partial table values.
|
When the length of a table value exceeds the width of its column, CiscoView displays the first part of that value and appends it with an ellipsis (...).
Workaround:
To view the entire table value, place the cursor over the ellipsis at the end of the desired entry.
A tool tip that displays the entire value appears.
|
CSCsa35308
|
CiscoWorks server performance decreases after opening multiple Monitoring dialog boxes.
|
This problem occurs when you:
1. Open multiple Monitoring dialog boxes (10 on a low-end server; 15 on a high-end server) for a CiscoWorks server from clients with multiple CiscoWorks and CiscoView sessions active.
The dialog boxes refresh properly and the server performs normally.
2. Open additional Monitoring dialog boxes.
Server performance decreases and some of the dialog boxes stop refreshing. The following message is displayed:
Action Cancelled. The requested page may not be available. Try refreshing the browser.
Workaround:
Refresh the browser by typing either Ctrl+R or F5. The Monitoring dialog boxes will now refresh properly.
|
CSCsa39302
|
Partial discovery of device occurs.
|
This problem occurs when you:
1. Launch CiscoView and open the chassis view for a device.
2. While CiscoView is discovering the device, change its SNMP credentials.
CiscoView does not complete the discovery of the device. As a result, an incomplete chassis view appears.
In addition, any configuration changes or menu selections made result in an error.
Workaround:
Close and then reopen the chassis view.
|
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.
•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.
|
Internally-Found Resolved Problems
Table 10 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 try to restore after a backup operation.
|
This problem has been resolved.
|
CSCeb44684
|
PIX MC pages were not displayed.
|
This problem has been resolved.
|
CSCeb46559
|
MICE/CAM did not communicate with ACS3.2 via HTTPS.
|
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 threw invalid error message.
|
This problem has been resolved.
|
CSCdz03228
|
Many log files did not print timestamp within Ciscoworks.
|
This problem has been resolved.
|
Customer-Found Resolved Problems
Table 11 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.
|
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/univercd/home/home.htm
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
Ordering Documentation
You can find instructions for ordering documentation at this URL:
http://www.cisco.com/univercd/cc/td/doc/es_inpck/pdi.htm
You can order Cisco documentation in these ways:
•Registered Cisco.com users (Cisco direct customers) can order Cisco product documentation from the Ordering tool:
http://www.cisco.com/en/US/partner/ordering/index.shtml
•Nonregistered Cisco.com users can order documentation through a local account representative by calling Cisco Systems Corporate Headquarters (California, USA) at 408 526-7208 or, elsewhere in North America, by calling 1 800 553-NETS (6387).
Documentation Feedback
You can send comments about technical 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.
Obtaining Technical Assistance
For all customers, partners, resellers, and distributors who hold valid Cisco service contracts, Cisco Technical Support provides 24-hour-a-day, award-winning technical assistance. The Cisco Technical Support Website on Cisco.com features extensive online support resources. In addition, Cisco Technical Assistance Center (TAC) engineers provide telephone support. If you do not hold a valid Cisco service contract, contact your reseller.
Cisco Technical Support Website
The Cisco Technical Support 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, 365 days a year, at this URL:
http://www.cisco.com/techsupport
Access to all tools on the Cisco Technical Support 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 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 TAC 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 TAC 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, and logo merchandise. Visit Cisco Marketplace, the company store, at this URL:
http://www.cisco.com/go/marketplace/
•The Cisco Product Catalog describes the networking products offered by Cisco Systems, as well as ordering and customer support services. Access the Cisco Product Catalog at this URL:
http://cisco.com/univercd/cc/td/doc/pcat/
•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
•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
•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
Copyright © 2005, Cisco Systems, Inc.
All rights reserved.
