 Feedback
|
Table Of Contents
Release Notes for CiscoWorks Common Services 3.0 (Includes CiscoView 6.1) on Windows
CiscoWorks Common Services Documentation
Time Zone Acronyms and Offset Settings
Integrating with Third-party Vendors
CiscoWorks Roles and Privileges
Modifying the CiscoWorks Roles and Privileges
Documentation Errata for CiscoView
CiscoWorks Homepage Known Problems
Software Center Known Problems
Integration Utility Known Problems
CA-Unicenter Adapter Known Problems
Internally-Found Resolved Problems
Customer-Found Resolved Problems
Obtaining Technical Assistance
Cisco Technical Support Website
Definitions of Service Request Severity
Obtaining Additional Publications and Information
Release Notes for CiscoWorks Common Services 3.0 (Includes CiscoView 6.1) on Windows
This release note is for CiscoWorks Common Services 3.0 running on a Windows platform.
The release note contains the following sections:
•
CiscoWorks Common Services Documentation
•
•
•
•
•
New Features
The new features in CiscoWorks Common Services Release 3.0 are:
•
Provides launch points for the CiscoWorks products and other resources. The HTML-based CiscoWorks Homepage (CWHP) replaces the Java applet-based desktop and login.
•
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.
•
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.
•
Allows applications to create shared device groups. It provides grouping facility based on various attributes in Device and Credentials Repository (DCR).
•
Enables you to download software patches and device packages, and deploy device packages.
•
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.
•
Provides packet level security, integrity protection, and replay protection. However, it does not encrypt the packets.
•
Enables Common Services and its applications to restore backed up data from an earlier version.
•
•
•
•
•
New Features for CiscoView
CiscoView 6.1 contains the following new features:
•
Note
•
•
•
•
•
Note
•
CiscoWorks Common Services Documentation
Note
Table 1 describes the CiscoWorks Common Services documentation that is available.
Table 1 CiscoWorks Common Services Documentation
Installation and Setup Guide for CiscoWorks Common Services (Includes CiscoView) on Windows
•
•
http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt
/cw2000/cw2000_d/comser30/ig_win/index.htm•
User Guide for CiscoWorks Common Services
•
On Cisco.com at: http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/
cw2000/cw2000_d/comser30/usrguide/index.htm•
User Guide for CiscoWorks Integration Utility 1.6
•
http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/
cw2000/cw2000_d/comser30/nmim_ug/index.htmUser Guide for CiscoView 6.1
•
•
http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/
cw2000/cw2000_d/comser30/cv_ug/index.htm•
Release Notes for CiscoWorks Common Services 3.0 (this document)
•
•
CiscoWorks Common Services Online help
•
•
1 See the "Obtaining Documentation" section.
Time Zone Acronyms and Offset Settings
Table 2 shows time zone acronyms supported in the CiscoWorks applications that use the time zone feature.
•
•
•
•
•
•
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:
•
•
•
Note
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.
•
•
To select an IP address, modify the gatekeeper file located in NMSROOT\lib\vbroker\gatekeeper.cfg
where NMSROOT is the directory (opt/CSCOpx by default) in which CiscoWorks is installed.
Replace every instance of external-IP-address with the external IP address you choose, and remove the "#" character, from the following:
•
•
•
•
After modifying the gatekeeper file, restart the Daemon Manager. To do this, first stop the Daemon Manager by entering:
net stop crmdmgtd
Now, start the Daemon Manager by entering:
net start crmdmgtd
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 the required service packs. If you are running Windows, make sure Service Pack 3 or Service Pack 4 is installed.
For a list of required service packs, see Chapter 1 of Installation and Setup Guide for CiscoWorks Common Services (Includes CiscoView) on Windows.
If CiscoWorks does not operate properly after installing all necessary service packs, check the permissions on the directory install-directory\objects\dmgt\ready. Local administrators group and casusers groups must have full access. If the permissions are incorrect, stop the daemon manager, change the permissions, and start the daemon manager again.
Caution
Support Information
CiscoWorks supports the following:
•
–
–
–
–
–
•
–
–
•
–
–
It also supports UltraSPARC 10 running Solaris 2.8 or 2.9.
•
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 have to use the correct version of Java.
The supported native JVM versions are:
•
•
Note
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 in 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:
•
•
•
To enable the native Java console in Microsoft Internet Explorer:
Step 1
Step 2
Step 3
To enable Java Console in Netscape Navigator:
Step 1
Step 2
Step 3
To enable Java Console in Mozilla:
Step 1
Step 2
Step 3
The Java Plug-in console will automatically open when you launch an application that uses it.
Note
Integrating with Third-party Vendors
Use the Integration Utility to integrate Cisco device information and Cisco applications into SNMP management platforms like:
•
•
•
•
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:
•
•
•
•
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:
•
•
Note
•
•
•
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.
•
•
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
Step 2
Step 3
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:
•
•
–
–
•
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 9 describe the problems known to exist in this release; Tables 11 and 12 describe the problems resolved since the last release of CiscoWorks Common Services.
Note
The CiscoWorks Common Services known problems are broken down into the following sections:
•
•
•
•
•
•
Installation Known Problems
Table 3 Installation Known Problems
None
Installing CD One displays an error message that there is not enough space on the drive to complete the process.
Installation requires 15 MB of space in the Windows temporary directory.
This error occurs if the destination path is not the default, and the drive where temp directory resides does not have the required space.
Workaround:
Increase the disk space in windows temporary directory.
CSCin32988
Unable to login after installation.
This occurs when the non standard java options -Xbootclasspath is set with '.' using _JAVA_OPTIONS as environment variable, before installing the product.
Workaround:
1.
servlet\orig\cwpass to NMSROOT\lib\classpath\com\cisco\nm\
cmf\servlet\cwpass.2.
a.
net stop crmdmgtd
b.
net start crmdmgtd
CSCin23546
Installing Common Services deletes previous web server entry.
This problem occurs when CiscoWorks registers its webserver with the default name Apache in Windows services. This also overwrites the previously installed Apache service that has the same name.
Workaround:
The other standalone Apache webserver can be started from the command line. It can also be registered as a service that has a different name using:
apache -i -n "Service Name"See documentation on the Apache Website for more details. However, we recommended that you do not have other webservers on the machine where CiscoWorks is installed.
CSCea18129
Uninstallation (or installation) displays incorrect error message.
Uninstallation (or installation) displays the following error message even if there is no other installation running:
[un]installation is already runningThis happens when you are not a member of the local Administrators group.
Workaround:
Install or uninstall as a user who is a member of the local Administrators group.
CSCdz34376
Reinstallation aborts and displays a message that the jpishare.dll is locked.
Reinstallation aborts after displaying messages that the files jpishare.dll and jpins32.dll are locked.
Workaround:
Close all the browser sessions and the Java Plug-in instances that are running in the server and restart the installation.
CSCdx71019
You cannot uninstall CiscoWorks Common Services if disk space is insufficient.
CiscoWorks Common Services cannot be uninstalled if disk space is insufficient. This is because the installer cannot allocate sufficient temporary space.
Workaround:
Delete the CSCOpx folder and clean the registry, manually.
CSCdt63101
When installing CiscoWorks as non-root user, an error message appears.
When installing CiscoWorks under a non administrator account on Windows 2000, the following message appears:
Setup Initialization Error Setup has detected that unInstallshield is in use. Please close unInstallshield and restart setup. Error432.When you click the OK button, installation terminates.
Workaround:
Run installation from a local administrator's account.
CSCdt32795
CiscoWorks malfunctions if operating system is upgraded after installation.
CiscoWorks processes do not start normally after Operating System upgrade.
Workaround:
See the "Operating System Upgrade" section.
CSCds90562
Daemon manager fails to run if CiscoWorks home directory is encrypted.
CiscoWorks does not support encrypted directories.
Workaround:
None. Do not install CiscoWorks in an encrypted directory.
CSCeb03515
When you uninstall, resintall or upgrade, an error message,
Verify Stopped Processes appears.This error occurs when a Java-Plugin is running or browsers using Java-Plugins are running.
The error message states that the wizard will verify whether the CW2K files are being used by other running processes.
When you click Yes, the wizard lists a process that still uses CW2K files. You must stop these process.
Workaround:
Close all the browsers and Java-Plugins when the errors occurs.
CSCsa04303
All files in the temporary directory are not cleaned by CWCS after installation.
During installation, the files are placed in the setup directory under TEMP.
After installation some of these files are not removed from the directory.
Workaround:
Close all the files under: %TEMP%\_ISTMPx.DIR, where x is one or two digits.
CSCsa04369
LIBEAY32.dll and SSLEAY32.dll not found errors occur when you try to upgrade after aborting the previous upgrade attempt.
The error occurs during the second attempt to ugrade from CWCS 2.2 to CWCS 3.0 after you abort the first attempt.
Workaround:
During the first upgrade attempt, backup the system. If the upgrade fails or stops, restore the data from the backup.
CSCsa22674
CWCS 3.0 installation on IPv6 configured machine fails without a warning.
When you install CWCS 3.0 on a IPv6 configured machine, setup.exe aborts immediately.
Workaround:
Reconfigure the machine for IPv4, then install CWCS 3.0.
CSCsa26294
Installing Ciscoworks IDU returns an error message stating that there is not enough space on the drive to extract the package.
When installing CiscoWorks IDU, this error message appears:
There is not enough space on drive c:\ to extract this package.This error message appears when the available hard disk size is a multiple of 4GB (For example, say 8GB, 20GB, or 68GB, etc.)
Workaround:
Download, add or delete files on your computer so that you do not have a multiple of 4GB on your hard disk.
CSCsa16542
Installation fails if the install path is long.
If installation directory path length exceeds 1024 characters the installation will fail.
Workaround:
Specify a short custom path.
CSCsa04407
Uninstallation exits when the drive is full.
When you uninstall by selecting Start > Program Files > CiscoWorks > Uninstallation, an error message appears if the drive is full.
Workaround:
Free up some space and then start uninstallation.
CiscoWorks Homepage Known Problems
Software Center Known Problems
Integration Utility Known Problems
For Windows users, the file NMIDBOptions.properties contains Cisco.com passwords, in an encoded form, and is accessible only to root/admin users or any member of the casusers group. Root/admin access to the host needs to be restricted if Cisco.com password security is a concern.
For Windows users, the file NMIDBOptions.properties is not protected from general access.
If Cisco.com password security is a concern, you should disable the Cisco.com update option, and manually download the zip file from the Cisco.com location:
•
where n is the version number.
•
ftp://username@ftp.cisco.com/cisco/netmgmt/ciscoview/5.0/packages/nmidb.n.zip
CA-Unicenter Adapter Known Problems
Browser Known Problems
Table 8 Browser Known Problems
None.
If you have a popup-blocker enabled in your browser, popup dialog boxes will not appear.
For popups to appear, you have to disable the popup-blocker, if you have installed any.
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.
CSCsa09688
Software and Device downloads do not work if you block popups in Netsscape 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 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.
In such case a blank screen appears.
Workaround:
Install Java Plug-in manually. For more information regarding the Java Plug-in, see the "Support Information" section.
CSCef12135
Mozilla 1.7 stores session information across separately opened windows.
This occurs when the browsers use the same profile name.
Workaround:
Use different profile names for each instance of Netscape.
General Known Problems
Table 9 General Known Problems
CSCin37340
The dbRestoreOrig.pl script displays error message.
When you run the dbRestoreOrig.pl script the following error message appears:
CreateService - 'EssentialsDbEngine' The specified service has been marked for deletion.orCreateService - 'CmfDbEngine' The specified service has been marked for deletionThis happens if the database is running when the dbRestoreOrig.pl script is run.
Workaround:
Wait for a couple of minutes and then run the dbrestoreOrig.pl script again with the same arguments. If this does not work, reboot the machine and then run the dbrestoreOrig.pl script.
CSCec013271
Restore fails when migrating data to other server.
Wen you restore the backup taken from a CS 2.2 server on a CS 3.0 server, restore might fail if the backup archive has any file or folder with a long path name.
The following error message appears:
ERROR: Restore cannot proceed. Seems you are hitting the bug CSCec01327Workaround:
You have to install the patch cmf2.2-win-CSCec013271.tar on the CS 2.2 server. The patch is available at:
http://www.cisco.com/pcgi-bin/tablebuild.pl/cw2000-cd-one
You should install the patch on the CS 2.2 server before taking the backup.
CSCsa47100
Logout from a CS server in an Authentication Server (AS) fails when you access using domain name.
When you access the server in SSO AS mode with fully qualified domain name (example http://hostname.cisco.com:1741), log out does not happen.
Workaround:
1.
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.
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:
CSCin33739
Installation proceeds with errors and applications become inaccessible after installing CiscoWorks.
CiscoWorks installation displays the following error messages:
The ordinal 2821 could not be located in the dynamic link library LIBEAY32.dllor
The ordinal 2821 could not be located in the dynamic link library SSLEAY32.dllAfter installation, some applications are not accessible.Workaround:
1.
–
–
2.
3.
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.
CSCin07682
Default button inactive in Java Plug-in Security warning window.
The Java Plug-in Security Warning window which is displayed just before the launch of the Cisco Works home page, has the Grant this Session button as the default button and it is highlighted.
However, if you press Enter it does not affect this button.
Workaround:
Use the mouse to select this button.
CSCea20284
Scheduled Backup does not work.
Scheduled Backup displays the following error when the backup directory is more than 24
characters:Cannot schedule: The command line cannot exceed 259 characters. Invalid commandWorkaround:
1.
2.
CSCdz55483
Many processes die soon after you start daemon manager.
Several processes terminate soon after you start daemon manager on a machine that has dual boot configurations, with options of Windows Professional and Windows Server.
Workaround:
None.
CSCdy47479
Database Configuration accepts 1741 as its port.
Currently there is no port availability checking implemented on Windows.
Workaround:
None.
CSCdy46071
Port availability and port occupancy are not checked properly.
If you access the URL
http://hostname:1741 through browser, it launches local web application, instead of CiscoWorks.This occurs when another webserver is using the port 1741.
Workaround:
Modify the settings of the other webserver to use a different port or uninstall the other webserver.
CSCdw93703
CiscoWorks LMS/RWAN 2.0 memory and Dr Watson errors on Compaq Servers.
Dr Watson error appears on Compaq servers if Compaq Insight Manager is running on Compaq servers where CiscoWorks is also running.
Workaround:
•
Or
•
CSCeb34151
Accessing CiscoWorks applications using Internet Explorer results in a 403 forbidden error.
This happens if you open multiple MC Application windows and access a link under Common Services folder.
This may also occur if you open all the MC Application windows in a specific order.
This is an issue specific to Internet Explorer and does not happen with Netscape Navigator.
Workaround:
Log out of CiscoWorks and log in again.
CSCsa25128
CRMLogger loses messages when it recieves1000 or more syslog messages in milliseconds.
CRMLogger can collect 1000 messages in a second that are coming over a span of 1 second.
When 1000 syslogs are pumped in a millisecond with maximum length, CRMLogger is unable to receive all of them.
Workaround:
None.
If 1000 or more messages are received in milliseconds, there is no workaround.
CSCin63973
CRMLogger loses syslog messages from the device.
This error occurs when debug is enabled or the system is under heavy load.
Workaround:
Disable debug from registry and restart CRMLogger.
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 may become unreachable in the topology.
This is caused by the way IOS responds when it has a community defined with no view for it.
Workarounds:
•
•
•
CSCed10462
Import Devices from Access Control Server (ACS) feature adds non-Cisco devices into DCR.
This occurs when ACS has non-Cisco devices in its list.
Workaround:
Delete the non-Cisco devices from DCR after importing.
CSCee71246
Cannot import files from mapped drive on windows server.
When you import a file located in a mapped drive the following events can occur:
•
•
Invalid file format.
•
Logon failure:- The user has not been granted the requested logon type at this computer.The mounted drive is configured with read/write permission for everyone. This includes the domain user and not the casuser.
Workaround:
Copy the file from the mounted file sytem to the local system and then import.
CSCsa13971
Export feature does not use devices selected in the Device Management screen.
This occurs when you:
1.
2.
3.
4.
Popup window does not have the selected devices.
Workaround:
DCR Export Screen provides a device selector which allows you to select the device to be exported.
CSCin41971
Authentication from NMS fails for valid users.
This occurs when the following conditions are met:
•
•
•
Workaround:
The primary IP address of the NMS should be configured as a client in ACS.
CSCsa03531
When you restore CS 2.1 data an error message appears.
The following error appears:
Unable to copy from backup archive folder to temporary folder.This occurs under the following conditions:
•
•
Workaround:
Either:
•
Or
•
a.
b.
c.
d.
e.
f.
g.
The restore will now work.
CSCsa04368
Automatic backup fails when you upgrade from CS 2.1 or CS 2.2 to CS 3.0. This occurs if you cancel the previous attempt to upgrade during the backup.
This occurs only during upgrade.
Workaround:
•
or
•
CSCsa04022
Cannot access CiscoWorks Server when you restart DaemonManager.
When you restart DaemonManager, all the processes take some time to come up. This causes a delay in accessing the CiscoWorks Server.
Workaround:
Wait for a few minutes. Now run the process status command pdshow.
CSCsa34882
Ethereal or Windump show two SNMP packets in the trace when only one packet is sent out.
This occurs when the following interfaces are found:
•
•
These interfaces are listed as two interfaces although it is one interface.
Workaround:
None.
CSCsa06695
CS 3.0 CRMLogger will not dynamically detect the log File name change as CS 2.2.
Some registry keys are not picked up dynamically.
Workaround:
Restart CRMLogger if the log file name is changed.
CSCsa36841
Add/Remove operation can occur automatically when you Create/Edit groups in the Group Admin UI.
When you Add/Remove devices in the Membership page and refresh the browser, the next device will also be added or removed.
Workaround:
None. Repeat the Add/Remove operation.
CSCsa20444
Job state changes to Cancelled even after the job is completed successfully.
This problem is only seen for periodic jobs, with no job history maintained.
This occurs when you:
1.
2.
3.
The run state of the succeeded job to Cancelled.
Workaround:
None.
CSCsa26875
Error messages appear when you stop jobs.
When you stop jobs before their completion, some error messages appear such as:
Cannot stop job 1064.14.The problem occurs when the you try to stop the job just milliseconds before the 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.
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.
CSCsa34105
Upgrade from CS 2.1/CS 2.2 to CS 3.0 fails during backup.
The backup fails and the backup.log generates errors. This problem occurs if Daemon Manager does not run during backup.
Workaround:
Start the Daemon Manager and start the upgrade again.
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:
Customer 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.
For example: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.
2.
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.
CSCsa22443
Cannot stop downloading of Software Center device package headers to temporary folder when you click Cancel.
This problem occurs when you:
1.
2.
3.
–
–
The device package headers will be downloaded to temporary folder.
Workaround:
To cleanup the temporary download location explicitly:
1.
–
–
2.
3.
–
–
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.
2.
The following 403 forbidden error appears:
ForbiddenYou 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.
2.
3.
4.
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:
•
Or
•
CSCin22086
JRM does not schedule jobs properly when you change the system time manually.
JRM time does not reset when you change the system time manually.
Workaround:
Restart Daemon Manager. To do this:
1.
net stop crmdmgtd
2.
net start crmdmgtd
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:
•
For example, udf..attribute.•
For example, .udf_attribute.•
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 DCR master takes a lot of time.
This occurs when you configure a DCR 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 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:
•
•
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.
2.
1.
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.
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.
2.
3.
4.
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.
NMSROOT/bin/pdterm CMFOGServer2.
NMSROOT/bin/pdexec CMFOGServerCSCsa44801
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 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.
WEB-INF/classes/trans.properties file.2.
3.
To stop it, enter
NMSROOT/bin/pdterm CMFOGServerTo start it, enter
NMSROOT/bin/pdexec CMFOGServerCSCsa45039
DCR Export does not finish if filepath has spaces.
This problem occurs if the filepath is long or the filename has spaces in between.
For example:
1.
The export does not occur.
Workaround:
Use short forms (8.3 DOS filenames) instead of filenames with spaces.
For example:
You can use C:\progra~1\cscopx instead of C:\Program files\cscopx
Or,
Install Common Services 3.0 Service Pack 2.
CS 3.0 SP 2 is available at:
CSCeg26913
JDK crashes and Notification Services (NOS) does not receive any NOS messages.
When this problem occurs:
•
•
•
For example, the output of pdshow NOSServer will be:
Process= NOSServerState = Failed to runPid = 0RC = 0Signo = 6Start = 11/27/04 08:55:28Stop= 11/28/04 04:37:52Core = Core file created.Info = Application failed or was registered incorrectly.Workaround:
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.
WEB-INF/classes/trans.properties file.2.
3.
To stop it, enter
NMSROOT/bin/pdterm CMFOGServerTo start it, enter
NMSROOT/bin/pdexec CMFOGServerCSCsa82899
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.
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.
Install Common Services 3.0 Service Pack 2.
CS 3.0 SP 2 is available at:
CSCsa66745
Issues while restoring the backup data in the Windows machine.
The system call from perl, which calls the tar.exe executable, is not releasing the directory immediately after system call ends. Hence the subsequent attempt to rename the directory fails.
Workaround:
Install Common Services 3.0 Service Pack 2.
CS 3.0 SP 2 is available at:
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.
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.
2.
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:
•
•
•
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:
•
•
The following time zones are affected:
•
•
•
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
Internally-Found Resolved Problems
Customer-Found Resolved Problems
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:
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:
•
http://www.cisco.com/en/US/partner/ordering/index.shtml
•
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-9883We 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
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-2447For 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.
•
http://www.cisco.com/go/marketplace/
•
http://cisco.com/univercd/cc/td/doc/pcat/
•
•
•
http://www.cisco.com/go/iqmagazine
•
•
http://www.cisco.com/en/US/learning/index.html
This document is to be used in conjunction with the documents listed in the "CiscoWorks Common Services Documentation" section.
CCSP, CCVP, the Cisco Square Bridge logo, Follow Me Browsing, and StackWise are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, and iQuick Study are service marks of Cisco Systems, Inc.; and Access Registrar, Aironet, ASIST, BPX, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Empowering the Internet Generation, Enterprise/Solver, EtherChannel, EtherFast, EtherSwitch, Fast Step, FormShare, GigaDrive, GigaStack, HomeLink, Internet Quotient, IOS, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, LightStream, Linksys, MeetingPlace, MGX, the Networkers logo, Networking Academy, Network Registrar, Packet, PIX, Post-Routing, Pre-Routing, ProConnect, RateMUX, ScriptShare, SlideCast, SMARTnet, StrataView Plus, TeleRouter, The Fastest Way to Increase Your Internet Quotient, and TransPath are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or Website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0502R)
Copyright © 2005, Cisco Systems, Inc.
All rights reserved.
