CiscoWorks Common Services 2.2
Release Notes for CiscoWorks Common Services 2.2 (Includes CiscoView 5.5) on Windows
Downloads: This chapterpdf (PDF - 626.0KB) | Feedback

Release Notes for CiscoWorks Common Services 2.2 (Includes CiscoView 5.5) on Windows

Table Of Contents

Release Notes for CiscoWorks Common Services 2.2 (Includes CiscoView 5.5) on Windows

New Features

CiscoWorks Common Services Documentation

Time Zone Acronyms and Offset Settings

Multi-Homed Machines

Operating System Upgrade

Support Information

Java Support

Installing Java Plug-in

Integrating with Third-Party Vendors

Integration Utility Features

Using the Integration Utility

Documentation Errata

Known and Resolved Problems

Installation Known Problems

Desktop Known Problems

CiscoView Known Problems

Package Support Updater (PSU) Known Problems

Integration Utility Known Problems

CA-Unicenter Adapter Known Problems

Browser Known Problems

General Known Problems

Internally-Found Resolved Problems

Customer-Found Resolved Problems

Obtaining Documentation

Cisco.com

Documentation CD-ROM

Ordering Documentation

Documentation Feedback

Obtaining Technical Assistance

Cisco.com

Technical Assistance Center

Cisco TAC Website

Cisco TAC Escalation Center

Obtaining Additional Publications and Information


Release Notes for CiscoWorks Common Services 2.2 (Includes CiscoView 5.5) on Windows


These release notes are for use with CiscoWorks Common Services 2.2 (formerly CD One) running on a Windows platform.

These release notes provide:

New Features

CiscoWorks Common Services Documentation

Time Zone Acronyms and Offset Settings

Multi-Homed Machines

Operating System Upgrade

Support Information

Integrating with Third-Party Vendors

Documentation Errata

Known and Resolved Problems

Obtaining Documentation

Obtaining Technical Assistance

New Features

CiscoWorks Common Services Release 2.2 contains the following new features:

AAA-ACS mode—The Access Control Server (ACS), that provides Authentication, Authorization, and Accounting (AAA) Security services is used for user authentication and authorization and meets the secured device view requirements.

User Session Management—This feature helps to pass the session data back and forth between two different servlet engines, Tomcat and JRunProxyServer.

Database Password Encryption—This helps to provide confidentiality for database passwords which were earlier stored as plain text.

Report Generation—You can customize your report by selecting the required modules in the Collect Server Info dialog box. By default, reports for all the modules are generated. You can run Collect Server Info for individual modules.

Install—Apart from the existing Typical and Custom installations, a third installation type is introduced—Express. If you choose Express install, you can reduce the number of user interactions during the install process. The Express install is faster compared to the Typical and Custom installations.

MDC Support Utility—The Multi Device Controller (MDC) Support utility collects log files, configuration settings, memory information, complete system information, process status, and host environment information into a deliverable tar file.

The MDC Support Utility also queries the Core Client Registrar (CCR) for any other support utilities registered and also runs them. Other Management Center (MC) applications should register their own support utilities which will collect their relevant data.

MC Application Administration Server (MAAS)—MAAS is used for managing the Management Center (MC) applications. The features available are license management, backup and restore, setting the user preferences, selection of login module, selection of SSL certificate, changing the database credentials and viewing different logs.

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.

Table 1 CiscoWorks Common Services Documentation 

Document Title
Available Formats

Installation and Setup Guide for CiscoWorks Common Services (Includes CiscoView) on Windows

PDF on the product CD-ROM.

On Cisco.com:

a. Log into Cisco.com.

b. Select Products & Services > Network Management CiscoWorks  > CiscoWorks Common Services Software > Technical Documentation > Install Guide Books

Printed document available by order (part number DOC-7815430=).1

User Guide for CiscoWorks Common Services

PDF on the product CD-ROM.

On Cisco.com:

a. Log into Cisco.com.

b. Select Products & Services > Network Management CiscoWorks  > CiscoWorks Common Services Software > Technical Documentation > User Guide Books.

Printed document available by order (part number DOC-7815301=).1

CiscoWorks Common Services Online help

Select an option from the navigation tree, then click Help.

Click the Help button in the dialog box.

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.

Column 1—alphabetically lists the supported CiscoWorks time zone acronyms. Change Audit reports may display time zone information differently.

Column 2—lists the spelled out time zone definition.

Column 3—lists the area covered by the time zone.

Column 4—lists the column's offsets from Greenwich mean time (GMT).

Column 5—lists the time zone setting for that zone's server

Column 6—lists the resulting output in reports.

If you generate reports, the output will vary depending on whether the data has been processed through Perl or Java. Table 2 also provides possible output for either case scenario.

To ensure that time zones are translated correctly—especially when your devices, servers, and clients are in different time zones—follow these guidelines:

When configuring time zones on managed devices, use the acronyms listed in the Time Zone Acronym Setting on Device column. To set time zones on devices, use the command described in the device-specific Command Reference documentation.

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

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


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


Table 2 Supported Server Time Zones 

Time Zone Acronym Setting on Device
Definition
Area Covered (Country/City)
Offset from GMT
Time Zone Setting on Server
Output in Report
GMT
Acronym

ACT

Australia Central Time

Australia/ Darwin

+9:30

Adelaide

GMT +9:30

ACT

AEST

Australia Eastern Standard Time

Australia/ Sydney

+10:00

+11:00 (DST)

Brisbane

GMT +10:00

GMT +11:00 (DST)

AEST

AET

Australia Eastern Time

Australia/ Sydney

+10:00

Brisbane

GMT +10:00

GMT +11:00 (DST)

AET

AHST

Alaska-Hawaii Standard Time

Hawaii/ Honolulu

-10:00

Hawaii

GMT -10:00

HST

ART

Arabic Egypt Standard Time

Africa/Cairo

+2:00

+3:00 (DST)

Cairo

GMT +2:00

GMT +3:00 (DST)

ART

CCT

China Coast Time

Asia/
Shanghai

+8:00

Beijing

GMT +8:00

CST

CDT

Central Daylight Time

United States/ Chicago

-5:00

Central Time

GMT -5:00

CDT (DST)

CST

CET

Central European Time

Spain/Madrid

+1:00

+2:00 (DST)

Madrid

GMT +1:00

GMT +2:00 (DST)

CEST

CST

Central Standard Time

United States/ Chicago

-6:00

Central Time

GMT -6:00

CST

CDT (DST)

CTT

China Taiwan Time

Asia/
Shanghai

+8:00

Beijing

GMT +8:00

CST

EAST

East Australian Standard Time

Australia/ Queens Island

+10:00

Brisbane

GMT +10:00

EAST

ECT

European Central Time

Europe/Paris

+1:00

+2:00 (DST)

Paris

GMT +1:00

GMT +2:00 (DST)

CEST

EDT

Eastern Daylight Time

United States/
New York

-4:00

Eastern Time

GMT -4:00

EST

EDT (DST)

EST

Eastern Standard Time

United States/
New York

-5:00

Eastern Time

GMT -5:00

EST

EDT (DST)

FWT

French Winter Time

France/Paris

+1:00

+2:00 (DST)

Paris

GMT +1:00

GMT +2:00 (DST)

CEST

GMT

GMT Standard Time

Africa/ Casablanca

None

Greenwich Mean Time

GMT +0

GMT

HST

Hawaiian Standard Time

Pacific/ Honolulu

-10:00

Hawaii

GMT -10:00

HST

JST

Japan Standard Time

Asia/Tokyo

+9:00

Tokyo

GMT +9:00

JST

MDT

Mountain Daylight Time

United States/ Denver

-6:00

Mountain Time

GMT -6:00

MDT (DST)

MST

MET

Middle European Time

Spain/Madrid

+1:00

+2:00 (DST)

Madrid

GMT +1:00

GMT +2:00 (DST)

CEST

MEWT

Middle European Winter Time

Spain/Madrid

+1:00

Madrid

GMT +1:00

GMT +2:00 (DST)

CEST

MST

Mountain Standard Time

United States/ Denver

-7:00

Mountain Time

GMT -7:00

MST

MDT (DST)

PDT

Pacific Daylight Time

United States/
Los Angeles

-7:00

Pacific Time

GMT -7:00

PDT (DST)

PST

PST

Pacific Standard Time

United States/
Los Angeles

-8:00

Pacific Time

GMT -8:00

PST

PDT (DST)

UTC

GMT Standard Time

Great Britain/ London

None

Greenwich Mean Time

GMT +0

GMT

ZP4

Zone 3

Russia/
Moscow

+4:00

Not Supported

GMT +4:00

ZP4


Multi-Homed Machines

A multi-homed machine is a machine that has multiple NIC cards, each configured with different IP addresses. To run CiscoWorks Common Services on a multi-homed machine, there are two requirements.

First, all IP addresses must be configured in DNS.

Second, because of 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 NMSROOT\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

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. Install any service packs that are found missing. 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. Administrators and casusers must have full access. If the permissions are incorrect, stop the daemon manager, change the permissions, and start the daemon manager again.


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


Note To look up this topic on Bug Navigator II, use bug ID CSCdt32795. For more information on using Bug Navigator II, see the "Known and Resolved Problems" section.


Support Information

CiscoWorks supports the following:

Operating System—CiscoWorks supports both the English and Japanese versions of Windows Professional and Server, with Service Pack 3.


Note CiscoWorks Common Services 2.2 supports only US-English and Japanese versions of Windows 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.


Browser—CiscoWorks supports both the English and Japanese versions of the following browsers:

Netscape Navigator 4.76 for Solaris 7, and Solaris 8 clients.

Netscape Navigator 4.78, and 4.79 for Windows 2000 with
Service Pack 3, and Windows XP with Service Pack1.

Internet Explorer 6.0 (version 6.0.2600.0000).

Internet Explorer 6.0 with Service Pack 1 (version 6.0.2800.1106).

Hardware—CiscoWorks supports IBM PC-compatible system with an Intel Pentium III or Pentium 4 processor.

Java Support

CiscoWorks uses two types of Java. 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 be using the correct version of Java.

The supported native JVM versions are:

Microsoft Internet Explorer 6.0—JVM 5.0.0.3802 or later


Note As part of Microsoft settlement agreement with Sun, Microsoft will stop including the Microsoft VM in new releases of Windows. For details, refer to the following URL:
http://www.microsoft.com/windowsxp/pro/evaluation/news/jre.asp

This has an impact on CiscoWorks because it requires Java environment to operate. If your Windows clients have not been upgraded, CiscoWorks will continue to work. Windows XP clients with Service Pack 1A or later, will not work. However, Windows XP clients with Service Pack 1 will not be affected.
Cisco is investigating alternate solutions for inclusion in future releases.


Netscape Navigator 4.7x—the correct version of JVM is installed.

The supported Java Plug-in version is 1.3.1 for both Solaris and Windows. The Plug-in version is independent of the browser used.

Installing Java Plug-in

You can install the Java Plug-in either on Internet Explorer or on Netscape Navigator. You can also manually install it.

Internet Explorer—When you attempt to launch any CiscoWorks application that uses the Java Plug-in for the first time, Internet Explorer will automatically install the correct Java Plug-in version for you.

Netscape Navigator—When you attempt to launch any CiscoWorks application that uses the Java Plug-in for the first time, CiscoWorks will redirect you to a page from which you can download and install the correct Java Plug-in version.

Manual Installation—To manually install the Java Plug-in, refer to Chapter 3 of Getting Started with the CiscoWorks Server.


Note CiscoWorks supports only the Java Plug-in versions mentioned above. Installing a different version, including a newer version, can cause CiscoWorks to malfunction.


To see Java related messages, look in the Java console. To do this, enable and then open the Java console. The two Java consoles involved are:

Native JVM's Java console.

Java Plug-in's Java console.

To enable the native JVM console when using Internet Explorer:


Step 1 Select Tools > Internet Options > Advanced.

Step 2 Click Java Console.

Step 3 Select View > Java Console to open the console.


To enable the native JVM console when using Netscape Navigator:


Step 1 Select Preferences > Advanced > Enable Java.

Step 2 Select Communicator > Tools > Java Console to open the console.


To enable the Java Plug-in console when using Windows:


Step 1 Select Start > Settings > Control Panel.

Step 2 Double-click Java Plug-in.

Step 3 Select Enable Java Console.

The Java Plug-in console will automatically open when you launch an application that uses it.


JSSE is used along with Java Plug-in 1.3.1 for SSL support on the clients. When you invoke CiscoWorks for the first time, in SSL mode from the browser:

JSSE jars will be downloaded from the server, and will be installed in the Plug-in installation directory on the client, as an add-on.

For the first time, java.policy file will be updated.

You will be asked to restart the browser after this.

Integrating with Third-Party Vendors

Use the Integration utility to integrate Cisco device information and Cisco applications into SNMP management platforms such as HP OpenView Network Node Manager. 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.

The following topics are described next:

Integration Utility Features

Using the Integration Utility

Integration Utility Features

Use the Integration utility to:

Download the NMIDB (Network Management Integration Data Bundle) from Cisco.com.

Prompt for additional configuration information that might not be available to register each application. This information is used to integrate the Cisco applications with the NMS console menu. In some cases, the NMS allows you to double-click on the device icon in the topology map of the NMS console to invoke an application.

Run an adapter script to integrate the icons, MIBs, and applications into the NMS. You can select an adapter script from the list of NM adapters provided with this utility. New NM adapters can be downloaded and added to the list.

Using the Integration Utility

You can perform certain tasks using the Integration utility, as described in Table 3.

Table 3 Integration Utility Tasks 

Task
Description

Starting the utility

Depending on your platform, you can start the Integration utility:

From a UNIX platform:

a. Use a Telnet utility to open a connection to the system on which the Integration utility is installed.

b. Navigate to the CiscoWorks /bin directory.

c. Set the X display environment on your X server.

Start the utility by entering ./nmic.sh on the command line.

From a Windows platform:

Click Start > Programs > Change Integration Options.

or

From the command line, navigate to the CiscoWorks /bin directory.

Enter the following script on the command line:

.\nmic.exe.

Downloading the Data Bundle

The Network Management Integration Data Bundle (NMIDB) contains the icons and configuration files specific to a Cisco device platform. NMIDB also contains MIBs and the application registration information used to register Cisco applications into the NMS. You can download an NMIDB from a file on your local machine, from Cisco.com, or from another system, or use an already downloaded file.

Registering the Applications

The application registration information is used to integrate Cisco applications with the NMS console menu. The Applications Registration dialog box displays user applications that are to be integrated into the NMS menu. This information is then extracted from the NMIDB. There is one tab for each application.

Running the Adapter Script

The Adapter scripts integrate icons, MIBs, and applications with NMS. The Choose Adapter dialog box provides both the Adapters available and their descriptions. The Adapter script checks whether the NMS exists on the machine before integration.


For more information about Integration utility, refer to the online help.


Note NM integration runs automatically when you download a device package through the Package Support Updater.


Documentation Errata

When reading the "Adding and Deleting Device Support" topic in the CiscoView 5.5 online help, note that Step 4 in the "CiscoWorks UNIX users" section should read: From your CiscoView server, choose Start > Programs > CiscoWorks for Windows [or] CiscoWorks > Package Support Updater.


Note For more information on Package Support Updater, refer to the "Package Support Updater" section in Using CiscoView 5.5.


Known and Resolved Problems

Tables 4 to 11 describe the problems known to exist in this release; Tables 12 and 13 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/cgi-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

Desktop Known Problems

CiscoView Known Problems

Package Support Updater (PSU) Known Problems

Integration Utility Known Problems

CA-Unicenter Adapter Known Problems

Browser Known Problems

General Known Problems

Internally-Found Resolved Problems

Customer-Found Resolved Problems

Installation Known Problems

Table 4 Installation Known Problems 

Bug ID
Summary
Explanation

None

Installing CD One returns an error message stating that there is not enough space on the C: drive to complete the process.

Installation requires 15 MB of space in Windows temporary directory: C:\temp on most systems.

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

Workaround:

Increase the space allotted.

CSCin39041

Login Panel is not displayed for nonnumeric TACACS value during installation.

Login Panel is not displayed for nonnumeric TACACS value during installation.

Workaround:

1. Change the value of TACACS+ port in JaasConfig.xml or
Change the login module to CiscoWorksLocal in JaasConfigModule

2. Restart the daemon manager.

CSCin35996

Administration folder under VPN / Security Management Solution is missing.

After you upgrade from CD One, 5th Edition or CD One, 4th Edition to CiscoWorks Common Services 2.2, the Administration folder under
VPN / Security Management Solution might be missing. This occurs only if you install a Management Center (MC) application in the system, before the upgrade. An error message appears in the install log.

Workaround:

Enable Core services manually. In the command prompt enter following commands:

1. Run net stop crmdmgtd. The following message appears:

The CiscoWorks Daemon Manager service 
is stopping...The CiscoWorks Daemon 
Manager service was stopped 
successfully.

2. Navigate to NMSROOT\conf\cmf\bin directory.

3. perl CMFEnable.pl -force Core,System which tells you core is enabled.

4. Run net start crmdmgtd

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. Copy the cwpass file from NMSROOT/lib/classpath/com/cisco/nm/cmf/
servlet/\ orig/cwpass to NMSROOT/lib/classpath/com/cisco/nm/cmf/
servlet/cwpass

2. Restart JRunProxyServer using NMSROOT/bin/pdterm RunProxyServer NMSROOT/bin/pdexec JRunProxyServer

CSCin31900

The Back button does not work properly.

Installation requires you to enter the password for the casuser. However, you cannot return to this dialog box from the subsequent screens.

Normally, only Express and Typical installations prompt you to enter the password for casuser. This happens only if the system rejects the random password generated by the installation.

Workaround:

1. Click Back to return back to Setup Type.

2. Select Custom installation as it allows you to enter the casuser password again.

This resets all settings (such as Admin password, or component selection) that you might have entered before switching to Custom installation.

Normally, you do not have to enter the password of the casuser. This is used internally by CiscoWorks to run the processes that do not require Administrator privileges.

CSCin27603

ACS configuration is lost on upgrading.

This problem occurs if the previous version was configured to use ACS, and later if you moved to local authentication, and then upgraded to the newer version.

Workaround:

Login to CiscoWorks as Admin, and change the security settings as required.

To configure ACS, enter ACS parameters.

CSCin26986

Reference to point patches exists even after upgrade.

Even after upgrading to the newer version of the product, the patches that had been applied to previous version are listed in the Application and Versions page.

Workaround:

The information, though misleading, does not impact the functioning of the packages.

CSCin23546

Installing Essentials deletes previous web server entry.

This problem occurs because of the Apache webservers that come with CiscoWorks registers itself as a service with the default name Apache. 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, it is recommended not to have other webservers on the machine in which CiscoWorks is installed.

CSCin21880

Installation does not accept special characters in passwords.

Installation does not accept special characters in passwords. Only digits and characters are allowed.

Workaround:

Set the password using the administration UI of the product, after installation.

CSCin21811

Uninstallation does not remove all files and directories.

Uninstallation of CiscoWorks Common Services 2.2 and Essentials 3.5 does not remove the following files:

NMSROOT\conf\bg2rigel\rme\r05001sa.txt

NMSROOT\dbupdate\CSCOdbupdate.log

NMSROOT\lib\classpath\com\cisco\nm\sysloga\
savedfilters

Workaround:

Remove the files and the directories, manually.

CSCin08319

Java Plug-in Shortcut getting displayed after Upgrade.

If you use a shortcut to uninstall CAM client in
CD One, 4th Edition and then upgrade to CiscoWorks Common Services 2.2, the shortcut displays:

404 page not found

Workaround:

Delete the shortcut.

CSCin07903

Password change for CD One database may not happen during local upgrade.

When you are performing a local upgrade to
CD One, 5th edition from CD One, 4th edition, occasionally the password change may not happen for CiscoWorks database. The following message may appear in the install log:

...CMF Password configuration. DSN cmf is 
registered. Calling dbpasswd.pl Unable to 
Change password for DSN cmf 
---end of CMF Password configuration 
----- CMF Password configuration 
The dsn 'cmf' is invalid 
----- end of  CMF Password configuration

Workaround:

After the installation is over, perform the following tasks to change the CD One database password.

1. Stop the daemon manager:

net stop crmdmgtd

2. Go to the Install dir/bin directory

3. Run perl dbpasswd.pl dsn=cmf

4. Start the daemon manager:

net start crmdmgtd

CSCea22858

You can run two installations at the same time launching them from two Terminal Server clients.

This happens on a system that runs Terminal Services (in Remote Administration mode), with two concurrent sessions initiated by two clients.

Workaround:

When installing a product from Terminal Services client, verify whether other sessions are running. Make sure that only one of them launches CiscoWorks installation.

CSCea19866

Error in install.log during reinstallation.

In Windows 2000, when CiscoWorks Common Services 2.2 is reinstalled in Custom mode, the following error message appears in the install log:

Service "CiscoWorks Web Server" is already 
installed!
----- end of Installing Apache service...

Workaround:

None. The error message can be ignored.

CSCea18129

Uninstallation (or installation) displays inappropriate error message.

Uninstallation (or installation) displays the following error message when there is no other installation running:

[un]installation is already running

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

Workaround:

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

CSCdz79929

Misleading message at the end of Installation.

At the end of installation, the installation framework displays the following message:

CiscoWorks is now running

CiscoWorks daemon manager starts only after you click OK in the message box.

Workaround:

At the end of installation, click OK in the message box. The CiscoWorks daemon manager will be started.

CSCdz34376

Reinstallation aborts and displays a message saying 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 Plug-in instances that are running in the server and restart the installation.

CSCdy71772

After uninstallation, some files and directories might be left under the uninstallation directory.

Uninstallation removes the files that belong to one of the CiscoWorks components.

Workaround:

None.

CSCdy04158

No recovery procedure for CiscoWorks, when CD One, 5th Edition upgrade fails.

If you are upgrading to CD One, 5th Edition and it fails, there is no procedure to recover the CiscoWorks installation.

Workaround:

You can do any of the following:

Remove all CiscoWorks applications manually, reinstall CD One, 4th Edition, and previously installed CiscoWorks applications, then restore data from a CiscoWorks backup.

Remove all CiscoWorks applications manually, install CD One, 5th Edition, and the corresponding CiscoWorks application. In this case, the CiscoWorks backup done with CD One, 4th Edition cannot be restored.

Rebuild the machine, and restore from system backup.

CSCdx71019

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

CiscoWorks Common Services cannot be uninstalled if disk space is less, as installer cannot allocate sufficient temp space.

Workaround:

Delete the CSCOpx folder and clean the registry, manually.

CSCdx36376

Random virus alerts on .gz files under htdocs/plugin at install.

Random virus alerts on .gz files under htdocs/plugin at install.

Workaround:

None.

CSCdx01388

dmgtd process fails to start during coexistence testing.

When CiscoWorks and CTM are installed on the same machine, Cisco Works daemons do not come up. It displays an error:

EDSMG0001: Process Manager Control is 
already running

Workaround:

Do not install CTM on the server in which CiscoWorks is installed. CTM and CiscoWorks cannot coexist.

CSCdw75528

Installation fails if there is a program file.

If there is a blank file with the name program in the root directory of the installation drive (for example, C or D) and you are installing in the default location, the installation may fail.

You may encounter a similar problem if there is a file named CiscoS in the installation drive (for example, C or D) and you are installing in a custom path drive:\Cisco Systems.

Workaround:

1. Remove the file that is causing the problem (for example, program in condition-1 or CiscoS in condition-2).

2. Restart installation.

CSCdw18205

CiscoWorks Common Services and URT3.0 cannot coexist.

Displays an error during installation:

An error occurred during the move data:-115 
Component : ess 
FIle Group:ess 
File:D:\......\tibrv.dll

Also displays the error:

Unable to stop RV processes during 
reinstall and uninstall

Workaround:

CiscoWorks Common Services and URT 3.0 cannot coexist. Uninstall URT for proper functioning of CiscoWorks.

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 an administrator's account.

CSCdt32795

CiscoWorks malfunctions if operating system is upgraded after installation.

CiscoWorks processes fail to 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.

CSCeb37909

Temporary directories are not removed after installation.

The directories are found in the TEMP folder, and are named _ISTMPxx.DIR, where xx is 0 to 99. There could be a subdirectory named priv that has encrypted files containing passwords assigned by installation.

Workaround:

The problem will be resolved if you install CiscoWorks Bundle Update 1, available on CCO. Bundle stands for The problem will be resolved if you install CiscoWorks Bundle Update 1, available on CCO. Bundle stands for LMS1.3/LMS2.2/RWAN1.3/VMS2.2.

Remove files with sensitive data, and possible leftovers from previous installations. Ensure that installation is not running while you remove the files.


Desktop Known Problems

Table 5 Desktop Known Problems 

Bug ID
Summary
Explanation

CSCin31137

Java Applets do not work on Internet Explorer 6.0.x and you are unable to login to CiscoWorks, since the login panel remains blank.

The problem occurs only in Internet Explorer 5.x or later. The problem seems to be caused by a date counter overflow in the Microsoft Java Virtual Machine.

Workaround:

1. Reboot the client machine on which the browser shows the problem.

2. Ensure that the security settings of Internet Explorer under Tools > Internet Options > Security are set to Default Level.

CSCin30837

Login Panel does not appear.

Java Console displays the error:

miscalculated data length

A different version of CiscoWorks may be running on the Client, and the CiscoWorks classes are in CLASSPATH. There might be other conflicting classes in the client, in CLASSPATH.

Workaround:

Unset CLASSPATH variable in the Client machine (My Computer > Properties >
Advanced > Environment Variable...) and invoke CiscoWorks again. This problem occurs in Internet Explorer only.

CSCin29952

File Browser not working properly for all security settings.

File browser, used to select files or directories in the server, shows files even when the user does not have sufficient permissions.

Workaround:

Give the proper permission for the files or directories.

CSCin29610

Internet Explorer browser version is not shown properly.

When Internet Explorer is used as the client browser, the minor version is not shown accurately.

For example, if the version of the browser is 6.0.26, CiscoWorks pages will show it as 6.0.

Workaround:

None.

CSCin28220

Unable to logout from CiscoWorks desktop.

The problem occurs because CiscoWorks uses two webservers with different certificates.

This occurs when you enable SSL for CiscoWorks and navigate to any window under VPN/Security Management Solution directory.

If you click the Logout button, you will not be able to logout. An exception log is displayed in Java Console.

Workaround:

1. Go to VPN/Security Management Solution > Administration > Configuration > Certificate.

2. Select the radio button labeled CiscoWorks Certificate.

3. Click Finish.

The message Certificate was successfully updated appears.

4. Restart the daemon manager.

CSCin26579

JRun proxy server hogs memory.

JRun hogs CPU when checking the status of a process from CiscoWorks Common Services desktop. The size of syslog.log is huge.

Workaround:

1. Restart the JRunProxyServer.

2. Run pdshow from the command line to get the process status.

CSCin26518

Unable to list files in a drive through file selector.

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

Workaround:

Map the drive using hostname.

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

CSCin24808

Internet Explorer crashes on connecting to CiscoWorks, if you enable Java Plug-in 1.3.1

This problem occurs when you select Tools > Internet Option > Advanced > Use Java 2 option in the client Internet Explorer browser.

Workaround:

1. Deselect the above mentioned option.

2. Close all the browser instances.

3. Restart the browser.

CSCin17642

Multiple security alert messages appear when navigating the Common Services GUIs after enabling SSL.

This occurs only when SSL is enabled on CiscoWorks Common Services 2.2 and when Common Services uses Common Services Certificate.

Workaround:

After enabling SSL, configure the certificate on Common Services to use CiscoWorks Certificate.

It can be configured at VPN/Security Management Solution > Administration > Configuration > Certificate.

CSCin10591

Java Plug-in 1.3.1_xx versions are not supported.

If Java Plug-in 1.3.1 and 1.3.1_03 are installed on a client machine, and if we try to launch the CiscoWorks home page, the login panel does not appear for either Internet Explorer or Netscape Navigator.

This is a compatibility issue since Java Plug-in 1.3.1_xx versions are not supported.

Workaround:

Uninstall all Java Plug-ins on the client and invoke CiscoWorks. This will guide you to install Java Plug-in 1.3.1.

CSCin07663

CPU hog by javaw.exe.

Occasionally, javaw.exe hogs CPU if CiscoWorks server is run for a long time.

Workaround:

Stop the daemon manager. If the process still hogs CPU, terminate the process or reboot the machine.

CSCin06195

Browser version should be changed according to the client.

Windows 2000 clients will be shown as
Windows NT 5.0.
When Windows 2000 clients are used, the version is detected by Javascript standard function call navigator.appVersion. This returns
Windows NT 5.0 instead of Windows 2000.

Microsoft internally refers to Windows 2000 as Windows NT 5.0.

Workaround:

None.

CSCin03389

Adhoc template fails for some catalyst devices.

When you enable debug on the device, the job will be successful, but will be shown as Unsuccessful.

Workaround:

Disable debug in the device and run the job.

CSCin02932

Job succeeds but it shows failed in job details window.

When debug is enabled in the device, the job will be successful, but will show Unsuccessful.

Workaround:

Disable debug in the device and run the job.

CSCea59420

The interface link in the Management Station to Device screen is broken if the client uses the hostname to access the server.

If the hostname of the server is used, clicking on the interface link results in a 403: forbidden error.

Workaround:

Use the IP address of the server to access CiscoWorks.

CSCea00268

Login panel does not show up.

The login panel does not show up after you login and logout continuously at short intervals. This problem occurs in CD One, 5th Edition and
CD One, 4th Edition.

Workaround:

Restart the daemon manager.

CSCdy76938

Common Services Applets are displayed as blank, grey boxes.

When the CiscoWorks Server is running in non-SSL mode, Common Services Applets under VPN/Security Management Solution > Administration > Common Services / Configuration are displayed as blank, grey boxes.

This is observed in other Tomcat based applets also (Example: Topology Groups in
Campus Manager).

The problem occurs only in the following browser versions:

Internet Explorer 6.0 with SP1

Internet Explorer 5.5 with SP2 and rollup patch Q323759.

The output in the Java Console contains IOExceptions when these applets are invoked.

Workaround:

There are two workarounds. They are given as Option 1 and Option 2. Option 1 has two sections, Option 1-A and Option 1-B

Option 1-A:

If SSL is not enabled on the CiscoWorks Server, do the following:

1. Invoke CiscoWorks Server and then select any of the Common Services Applets.
If the server uses a self-signed Certificate, the dialog box displays the following message:

Certificate is issued by an untrusted 	
site. Do you want to Proceed?

2. Select View Certificate.

CSCdy76938

(Continued)

Common Services Applets are displayed as blank, grey boxes.

3. In the Certificate dialog box, select Install Certificate.

4. In the Certificate Import Wizard, select the default options.

5. Close the browser and invoke the CiscoWorks Server again.

Option 1-B

If the Common Services WebServer Certificate is not valid, has expired, or has a HostName different from what is used to invoke the CiscoWorks server, modify the Common Services WebServer Certificate as follows:

1. Go to NMSROOT\lib\web (in a Windows server) or NMSROOT/objects/web/bin (in a Solaris server).

2. Run SSLUtil.pl (NMSROOT\bin\perl SSLUtil.pl)

3. Select Modify Common Services Certificate.

4. Give the correct Host Name. If the Host is not in DNS, give the IP address.

5. Restart the daemon manager and follow the steps given in Option 1-A.

Option 2:

1. Enable SSL on the CiscoWorks Server (Server Configuration > Administration > Security Management > Enable/Disable SSL GUI).

2. Invoke Common Services Applets.

CSCdx37840

SSL only: resizing the browser resets the CiscoWorks Common Services desktop.

While resizing the Netscape Navigator browser on Solaris clients after enabling SSL, the desktop content is to set to its original state.

Workaround:

Do not resize the browser.

CSCdw92538

CPU Utilization peaks when SSL Initializes.

In SSL mode, you are redirected to http mode. After SSL initialization, you are redirected back to https mode.

During this time, the CPU utilization on the Client machine might go upto 100 percent. However, it will stabilize after sometime.

The browser hangs, when the redirection happens several times in the same browser session.

Workaround:

Restart the browser.
You must minimize the number of redirections in the same browser session.

1. Do not refresh or reload index.html page of the same server successively.
After SSL Initialization occurs once for a particular server in a browser session, successive access (refresh/reload if required) can be done directly through https://server:port/login.html instead of index.html.

2. Do not change the CiscoWorks Servers, being accessed repeatedly in the same browser session.

CSCdw67986

Cannot load CD One login page in Netscape Navigator 4.7x.

CD One login page does not load in Netscape Navigator 4.7x.

Workaround:

Always enable Javascript. Select the Enable Javascript check box in
Edit > Preferences > Advanced dialog box.

CSCdw64365

Inconsistent Tree Structure.

Inconsistent Tree Structure in the browser. The order of About The Server, Setup, Diagnostics, and Administration folders is not consistent.

The inconsistent tree structure will appear before and after enabling System, Network Services. This may appear when you enable or disable SSL.

Workaround:

None.

CSCdw61688

JOS:Character circle-c corrupted with Japanese font.

In all platforms, at the bottom of each Help window,
Copyright (c) 2003, Cisco Systems, Inc. All rights reserved.
has corrupted character for (c) (cmf01.bmp)

Workaround:

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

CSCdw11344

Telnet succeeds when TCP fails.

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

Workaround:

None.

CSCdw04601

Error displayed during navigation.

When SSL in enabled, during navigation a message appears:

This page contains both secure and non 
secure items. Do you want to continue.

Whether you select yes or no, an error appears:

Page cannot be displayed

Workaround:

Refresh the browser or start work from the first step.

CSCdv22620

Two Help windows are displayed when no Plug-in is installed on the client.

Two Help windows appear when no Plug-in is installed on the client machine.

Workaround:

None.


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 6 CiscoView Known Problems 

Bug ID
Summary
Explanation

None.

Runtime error messages are displayed when viewing the CiscoView Quick Start Demo in Internet Explorer.

When you view the CiscoView Quick Start Demo in Internet Explorer, you may encounter runtime error messages.

Workaround:

Disable script debugging. To do so:

1. From the Internet Explorer main menu, select
Tools > Internet Options.

2. Click the Advanced tab.

3. In the Browsing section, make sure that the Disable script debugging checkbox is selected.

CSCdz79848

Not prompted to install Java Plug-in after launching CiscoView.

This problem is observed on Solaris clients running Netscape Navigator 4.76 without Java Plug-in already installed.

It occurs if you:

1. Launch CiscoWorks.

2. When prompted to install Java Plug-in after clicking certain links, such as Import Device List, click No.

3. Click the CiscoView link.
A blank page is displayed and you are not prompted to install the Plug-in.

Workaround:

Close and relaunch CiscoWorks.

This problem does not occur if you click Yes the first time you are prompted to install the Plug-in.

CSCdz53375

Configuration dialog box is sometimes hidden when launched.

This problem is observed on Windows 2000 clients running Netscape Navigator 4.79.

To reproduce problem:

1. Open chassis view for a device.

2. Right-click the device and select Configure.

Configuration dialog box is launched behind chassis view and may be hidden if the chassis view window is maximized.

Workaround:

Minimize the chassis view window.

This problem does not occur on Windows 2000 clients running Internet Explorer or Solaris clients running Netscape Navigator 4.76.

CSCdx43581

Unable to import device list when IP address is used to specify source device.

This problem occurs if you:

1. Use the following URL to launch CiscoWorks: http://localhost:1741

2. Select Device Manager > Administration > CiscoView Server > CiscoView Device List > Import Device List.

3. Select the Campus or RME radio button.

4. In the Host Name field, type the IP address of the device you wish to import from.

5. Click Import. The following error message is displayed:

Device import software is not present on 
this server.

Workaround:

Use either localhost or the appropriate host name to specify the source device when the previously mentioned URL is used to launch CiscoWorks.


Package Support Updater (PSU) Known Problems

Table 7 Package Support Updater (PSU) Known Problems 

Bug ID
Summary
Explanation

CSCdt36869

Installing the same device package from Cisco.com using multiple PSU sessions results in errors.

If you download and install device packages from Cisco.com using both PSU web interface and standalone PSU (psu, xpsu), errors appear.

Workaround:

Do not use the PSU web interface and standalone PSU simultaneously to download device packages from Cisco.com.

CSCdt24701

No error message is displayed after an unsuccessful attempt to uninstall NMIDB packages.

After an unsuccessful attempt to uninstall NMIDB packages, you do not see an error message that process failed.

Also, in View History window, Completed Successfully appears instead of Failed .

Workaround:

None.

CSCdt04070

No error message is displayed when network connection is lost.

No error message is displayed when network connection is lost during the download of device packages from Cisco.com.

Workaround:

None.


Integration Utility Known Problems

For Windows 2000 users with NTFS, 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 2000 users with a FAT file system, 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 nmidb.*.zip file from the Cisco.com location ftp.Cisco.com in the directory /cisco/netmgmt/ciscoview/5.0/packages.

Table 8 Integration Utility Known Problems 

Bug ID
Summary
Explanation

None.

Changing the browser used by one application changes the browser used by all applications registered through the Integration Utility.

This problem occurs if you:

1. Change the browser used by an application in the Application Registration; for example, CiscoView.

2. Click tab for another application, such as Essentials.

The browser will be changed.

Workaround:

None.

CSCin32985

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

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

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

A dialog box that displays only the OK button appears.

2. Attempt to close this dialog box.

It does not close and Integration stops.

Workaround:

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

CSCin23798

Cannot upgrade to latest NMIDB by clicking Get NMIDB in integration utility GUI.

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

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

NMIDB is up to date.

Workaround:

Remove VersionInfo.properties file from the following directory:
CiscoWorks installation directory\nmim\

CSCin08471

Integration with third-party NMS should be performed after installation of CiscoWorks.

After installation of CiscoWorks, you have to perform integration with third-party NMS.

Workaround:

If SSL will be enabled for the CiscoWorks server, we recommend that you perform integration with a third-party NMS after the installation of CiscoWorks.

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

CSCdr38931

Error messages may be displayed 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.

For Windows NT, if FAT file system is in place, make sure you have at least 190 MB of free disk space.

For other file and operating systems, make sure you have at least 25 MB of free disk space.

CSCdp17559

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

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

Workaround:

None.

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:

None.


CA-Unicenter Adapter Known Problems

Table 9 CA-Unicenter Adapter Known Problems

Bug ID
Summary
Explanation

None.

CA-Unicenter adapter does not integrate icons and MIBs.

CA-Unicenter adapter does not use MIBs or device icons from Cisco NMIDB. Adapter uses its own icons for Cisco devices on TNG maps.

Workaround:

None.

CSCdp17571

Numerous popup messages appear during CA-Unicenter adapter execution.

When you integrate with CA-Unicenter adapter in Windows NT 4.0, many popup messages ask for confirmation.

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

Workaround:

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

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

CSCdp17554

Reintegration with CA-Unicenter adapter does not work.

Using Integration utility, integrate with CA-Unicenter adapter.

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

Workaround:

You must unintegrate, then reintegrate:

1. From the command line, enter:

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

2. Select Start > Programs > CiscoWorks > Change Integration Options and reenter adapter information.

Numerous popup menus appear. Click OK each time to continue.


Browser Known Problems

Table 10 Browser Known Problems 

Bug ID
Summary
Explanation

CSCsa65648

CiscoWorks Online Help Table of Contents and Index do not appear in Internet Explorer 6.0 with Service Pack 1.

This occurs if you have installed Microsoft update KB890175 on your Windows system.

The Microsoft security update KB890175 (MS05-001) released on 1/12/05 disables the HTML Help ActiveX control. This affects all applications that use Cisco's Version 1 Online help system (used in CiscoWorks Common Services 2.2). If this update is installed on your machine, the CiscoWorks Online Help Table of Contents and Index do not appear in Internet Explorer 6.0 with Service Pack 1. However, this problem does not occur if you use Netscape Navigator.

Workaround:

Follow the instructions on editing the registry in the Microsoft security bulletin: http://www.microsoft.com/technet/security/bulletin/ms05-001.mspx

Scroll down and expand the FAQ for more information. You can find additional information about the registry at: http://support.microsoft.com/kb/892675

CSCin06210

Non-Admin users of Client Machines not able to download JSSE jars.

You are unable to invoke CiscoWorks application when logged in as a non-admin user in the client machine for Windows.

Workaround:

1. Login as administrator and access the application which will download the necessary jar files in the client system so that non-admin users could also access the server from it.

2. Also change the permission (give full permission) of the Java Plug-in directory.

CSCin00944

Plug-in 1.3.1 not recognized properly by Solaris Netscape clients.

This problem occurs when you invoke CiscoWorks on the following Netscape and Plug-in versions:

Client Platform: Solaris
Netscape Navigator versions: 4.77, 4.78, 4.79
Java Plug-in : 1.3.1
Solaris Netscape (versions 4.77, 4.78, 4.79)

In this case CiscoWorks does not recognize the Java Plug-in already installed on the client. It prompts you to install the Plug-in again. This is caused by a bug on Solaris Netscape (4.77 or later).

Workaround:

For Solaris Clients, use only Netscape Navigator 4.76.

This problem occurs when you invoke CiscoWorks on the following Netscape and Plug-in versions:

Client Platform: Windows
Netscape Navigator versions: 4.78, 4.79
Java Plug-in: 1.3.1

This problem occurs only if the Java Plug-in option is enabled in Netscape Navigator preferences. The cookies get disabled when you invoke CiscoWorks on Netscape Navigator when Java Plug-in is enabled and you cannot login to CiscoWorks.

Workaround:

Turn off (uncheck) the Java Plug-in option from Edit > Preference > Advanced.

CSCdx04645

Blank window is sometimes displayed after launching online help.

This problem occurs on Solaris clients running CiscoView in Navigator 4.76.

If you click Help in any dialog box, a blank window appears, although the status bar displays Document: Done.

Workaround:

Click Reload and the appropriate online help is displayed.

CSCdt11838

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

If RealJukeBox Netscape Plug-in is installed before Java Plug-in is installed, you will not be prompted to install Java Plug-in software when attempting to launch application.

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.

CSCdt06518

Unable to launch a second instance of CiscoView in Internet Explorer while the first instance is waiting for user input.

The problem occurs if you:

1. Launch CiscoView.

2. Open a device. CiscoView will prompt for community strings.

3. Without entering community strings, launch a second instance of CiscoView.

Workaround:

Enter community strings before launching the second instance of CiscoView.

CSCdt05102

Netscape Navigator crashes if you resize the browser window while the applet loads.

This problem exists in Netscape Navigator.

Workaround:

None


General Known Problems

Table 11 General Known Problems 

Bug ID
Summary
Explanation

None.

Local machine configuration is used when performing a remote upgrade.

There are two possible sources for configuration information:

Local machine

Remote machine

Of these two sources, the configuration information for the remote machine has precedence, and it is this information that is used during a remote upgrade.

None.

CiscoView log file resides in a new location.

For CiscoView, the cv.log file is now located in the following directory:

Windows Server: NMSROOTlog\
cv.log

For example, c:\Program Files\CSCOpx\
log\cv.log

Solaris Server: /var/adm/CSCOpx/log/cv.log

CSCec013271

Restore fails when migrating data to other server.

When you restore the backup taken from a CS 2.2 machine, on another CS 2.2 machine, restore might fail if the backup archive has any file or folder with a long path name.

The following error message appears:

ERROR(801): tar 
C:\Temp\restore\0\rme\filebackup.tar exited 
abnormnally !! 

Workaround:

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/cgi-bin/tablebuild.pl/cw2000-cd-one

You should install the patch on the CS 2.2 machine before taking the backup.

Also, you should install the patch on the CS 2.2 server on which you need to restore the backed up data.

CSCin37340

Running the dbRestoreOrig.pl script displays error message.

Running the dbRestoreOrig.pl script displays the following error message:

CreateService - 'EssentialsDbEngine' The 
specified service has been marked for 
deletion.
or
CreateService - 'CmfDbEngine' The specified 
service has been marked for deletion

This happens if the database is running when the dbRestoreOrig.pl script is run.

Workaround:

Wait for a couple of minutes and then Run the dbrestoreOrig.pl script again with the same arguments. If this does not work, reboot the machine and then rerun the dbrestoreOrig.pl script.

CSCin35746

EDS- GCF and JRM processes hog CPU, makes system unusable.

This problem could be caused by:

Network outage.

Gatekeeper not starting.

Machine having multiple NIC cards.

Workaround:

1. If the reason for the problem is network outage, reboot the machine.

2. If gatekeeper is not starting, NMSROOT\log\EDS.log shows a fatal error. If this is seen, please do the following:

a. Run net stop crmdmgtd.

b. Wait for a few minutes to make sure all ports have been freed (output of netstat -na should not return ports used by CiscoWorks).

c. Run net start crmdmgtd.

3. If the server in which Cisco Works is installed has multiple NIC cards, modify the NMSROOT\lib\vbroker\gatekeeper.cfg file accordingly.

CSCin33739

Installation proceeds with errors and applications become inaccessible after installing CiscoWorks.

CiscoWorks installation displays the following error messages:

The ordinal 2821 could not be located in 
the dynamic link library LIBEAY32.dll

or

The ordinal 2821 could not be located in 
the dynamic link library SSLEAY32.dll

After installation, some applications are 
not accessible.

Workaround:

1. Backup the following dlls:

System32\ssleay32.dll

System32\libeay32.dll

2. Delete these dlls from the System32 directory.

3. Uninstall the current copy of CiscoWorks that is giving the problem and reinstall it.

CSCin29004

CiscoWorks desktop is not accessible after you enable SSL.

This problem occurs rarely on Windows (especially on Windows Advanced Server) after you enable SSL and restart daemons.

This problem is caused by some stray javaw.exe process that remains after you stop daemons. This stray process interferes with CiscoWorks desktop daemons when you restart the daemon.

Workaround:

Reboot the machine.

This is needed because you cannot terminate the stray javaw.exe process from the Windows Task manager.

However, if you have MKS toolkit installed on the machine, you can terminate the stray javaw.exe process from the command line using the
kill -9 pid command.

CSCin28069

The message in the Backup job Result window is not fully visible.

With Solaris Netscape 4.76 as client browser, if you perform a backup operation, the Backup job result window appears. The message in this window is only partly visible.

Workaround:

Resize the message window.

CSCin28019

The MC Application Administration Server (MAAS) Sync jobs are not executed when system date is changed

MAAS sync jobs are performed at 00:00 everyday.

In Windows, if you change the system date manually, the sync job is not executed immediately. The sync job is executed only in the next instance of the scheduled time.

Workaround:

None.

CSCin27753

The AAA Server GUI does not load properly if login mode is changed.

If you change the login mode, navigate to the AAA server GUI (VPN/Security Management
Solution > Administration > Common Services > AAA Server), and click Synchronize, the AAA Server GUI is not displayed properly.

This is a Netscape Navigator specific problem.

Workaround:

Reload the GUI.

CSCin27032

The process EDS-GCF goes down.

This happens when daemons are restarted very frequently.

Workaround:

1. Stop the daemons.

2. Make sure all ports are free.

3. Restart the daemons.

CSCin22027

The SSL Information collected during installation is not retained.

This happens because there are two Apache Webservers in CiscoWorks Common Services 2.2.

The details provided for the certificate generation during installation are not retained for creating self-signed certificates for CiscoWorks Common Services Webserver.

Workaround:

None.

CSCin21677

The focus is not restored on the folder selection window.

If you enter an invalid directory path in the Licensing Information/Backup Database/Restore Database GUIs and click Enter, the following error message appears:

Invalid directory or file

If you again click Enter to close the error message, it disappears.

However, the focus is not restored on the folder selection window. Instead, the focus remains on the Select button. This problem is seen only in Netscape Navigator.

Workaround:

Instead of clicking Enter to close the error message, get the focus to the File Browser to continue file browser operations.

CSCin17971

When JRM is restarted, no Jobs are displayed in the Job Management UI.

This happens if more than one CiscoWorks Server is running on the network.

Workaround:

If you restart JRM, you must restart EDS and JRunProxyServer. Then invoke Job Management UI.

CSCin07838

Not able to invoke CiscoWorks if you start daemon immediately.

Unable to 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.

CSCea26728

All dbsrv7 processes can be killed by any authorized user, from the Windows Task Manager.

All dbsrv7 processes can be terminated by any authorized user, from the Windows Task Manager.

Workaround:

Do the following:

1. Start > Run > regedit to bring up the windows registry.

2. Click HKEY_LOCAL_MACHINE >
SYSTEM > Current Control Set > Services > ASANYs_SqlCoreDB > Parameters.

3. Double-click Parameters.

4. Enter -hs at the beginning of the Value data field.

5. Click OK and restart the daemon manager.

CSCea20284

Scheduled Backup does not work.

Scheduled Backup displays the following error when the backup directory is more than 24
characters:

Cannot schedule: The command line cannot 
exceed 259 characters. Invalid command

Workaround:

1. Use a shorter directory.

2. Use Command line Backup or the Back up Data Now option to backup in longer directory.

CSCea14488

Common Services does not function if hostname is changed.

If you change the hostname of a machine, Common Services does not work.

Workaround:

1. Change the HOST_NAME and CMF_HOST_NAME values in the following file:
CSCOpx/MDC/tomcat/mdc/WEB-INF/web.xml

2. Change HostName entry in the CCR. For this do the following:

Set LD_LIBRARY_PATH on Solaris:
setenv LD_LIBRARY_PATH /opt/CSCOpx/MDC/lib

Navigate to NMSROOT/MDC/bin where NMSROOT is the location of CiscoWorks.

Remove HostName containing old host name by entering:

ccraccess -removeResource Core 
Custom Custom "" "" HostName

Add new HostName entry with new host name by entering:

ccraccess -addResource Core Custom 
Custom NewHostName "" HostName

Check the new HostName entry from CCR:

ccraccess -addResource Core Custom 
Custom "" "" HostName

CSCdz83987

The javaw.exe process spawned by JRun is not terminated when daemon manager is stopped.

This happens when there are 4000 devices in the inventory database.

Workaround:

Terminate the javaw process manually or reboot the machine.

CSCdz55483

Many processes die soon after daemon manager is started.

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.

Accessing the URL http://hostname:1741 through browser 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:

Restart the daemons.

or

Shut down Compaq Insight Manager.

CSCdw61684

JOS:Apache generates the following error message:

localeinfo_ja_jp.properties 
not exist

These error messages appear when you invoke Resource Manager Essentials > Availability Dashboard > Device 
Center > Reachability Trend.

These messages are logged only when you invoke the application from a client for the first time.

Workaround:

None. This will not affect the functionality.

CSCdt73198

CiscoWorks freezes when the network connection of the system is removed.

CiscoWorks freezes when the system's connection to network is lost either by

Plugging out the ethernet network cable.

or

Powering down the switch.

Workaround:

Reboot the machine.

CSCdt22462

Delay when downloading Java applets on Win2K.

On some Windows 2000 systems, the initial download of large Java applets (or subsequent downloads of the same applets that are not cached locally) might take longer than expected (up to six minutes in some instances).

After the applet has been loaded and cached locally, the problem no longer occurs.

The delay is caused by client side filtering mechanisms such as virus scanning.

Some virus scanners are configured to automatically scan content downloaded by browsers. Scanning consumes a lot of memory and results in disk paging on most systems.

Because of this, downloading is significantly slower than expected. (The effect is less on systems with large amounts of RAM and virtual memory.)

Workaround:

Disable the automatic scanning of all downloaded files, and instead enable the scanning of program files only (specified by file extension).

Exact instructions vary depending on the virus scanner installed on your system.

CSCdt21743

Configuration files in Trivial File Transfer Protocol (TFTP) boot directory not secure.

The configuration files, stored in the TFTP boot directory during the TFTP operation, have permission for everyone, though files are owned by the user casuser.

This problem occurs only for a short time while downloading.

Workaround:

None.

CSCds90118

If two users create private views with same name, error occurs.

If two users create private views with same name, it results in an error.

Workaround:

None.

CSCin41906

CiscoWorks applications that use Java Plug-in cannot be launched from NNM 6.4 web console.

HP OpenView NNM6.4 requires Java Plug-in 1.4.x to be installed, when invoked from a web browser. There are known compatibility issues when invoking applications that use different Java Plug-in versions, in the same browser sessions.

CiscoWorks applications use Java Plug-in 1.3.1 Since this is not the Java Plug-in version used by HP OpenView NNM 6.4, CiscoWorks applications cannot be invoked from NNM 6.4 web console.

Workaround:

None.

CSCds75572

CiscoWorks database grows too quickly.

CiscoWorks database (cmf.db) grows several MB each day, reaching above 20 GB within 5 weeks. This causes the system to slow down, since jre.exe uses 90% of CPU.

Workaround:

Do not enable Event Logging. If Event Logging is already enabled, disable it by performing the following steps:

1. Select Server Configuration >
Administration > Event Management > Event Consumer Admin.

2. Set EventLogger to None, and click Apply.

CSCdp48276

Essentials cannot backup to network drive.

If you try to backup Essentials using
Admin > System Admin > Back Up Data Now, to a network drive, an error message displayed says that the specified Backup Directory does not exist.

Also, if you try Schedule Backup you get the following message:

mkdir G:\backup: Permission denied at 
C:\PROGRA~1\CSCOpx/bin/backup.pl line 62 in 
dbbackup.log

even if the backup directory exists.

Workaround:

Set the CiscoWorks user to have permissions to write to the network drive. See Installation and Setup Guide for CiscoWorks Common Services (Includes CiscoView) on Windows for details.

CSCdx74061

The scheduling fields do not automatically select the displayed value.

If you try to schedule a Backup or Compact job, the scheduling fields do not automatically select the displayed value.

The affected panels are:
VPN / Security Management Solution > Administration > Common Services > Compact Database
and
VPN / Security Management Solution > Administration > Common Services > Backup Database.

The values are not selected if they are not highlighted before you click Finish.

Workaround:
The problem will be resolved if you install CiscoWorks Bundle Update 1, available on CCO. Bundle stands for The problem will be resolved if you install CiscoWorks Bundle Update 1, available on CCO. Bundle stands for LMS1.3/LMS2.2/RWAN1.3/VMS2.2

CSCeb21179

The VPN / Security Management Solution page does not list the folder names available.

The VPN / Security Management Solution page does not list the folder names available. Though the folder names are not visible, you can launch the application if you click the icon.

The problem occurs in Netscape Navigator 7 with the default Java Plug-in version JPI1.4.1

Workaround:

Install JPI 1.4.1_02 and point
Netscape Navigator 7 to the new JPI.

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.

CSCeb08489

Login panel shows the username of the previous user and inherits the privileges of this user.

This problem occurs because the client browser talks to the server through a NAT. When this happens, the HOST header of the HTTP request does not get translated and hence provides the wrong information.

During logout, the header information is used to open a connection to the webserver. Since the host information is wrong, the connection fails, and the user is not properly logged out.

Workaround:

The problem will be resolved if you install CiscoWorks Bundle Update 1, available on CCO. Bundle stands for The problem will be resolved if you install CiscoWorks Bundle Update 1, available on CCO. Bundle stands for LMS1.3/LMS2.2/RWAN1.3/VMS2.2

CSCin46525

CMF Self Test Fails for ODBC Versions

The CMF self test gives an error in the odbc.pl part of the test. This occurs because the test does not have knowledge of the MSDE SP3 ODBC drivers installed by CSA MC. MSDE SP3 drivers are dated later than those expected by the CMF self test.

CSCin53880

The Contents and Index panels in the online help appear blank.

This happens when you use Internet Explorer 6.0.26 on Windows 2000 Professional or Server with Service Pack 4 and Java Plug-in 1.4.1_02.

Workaround:

Use Internet Explorer 6.0 with Service Pack 1 on Windows 2000 Professional or Server with Service Pack 4.

CSCeb08436

The ESS process of CiscoWorks broadcasts on UDP port 42350.

Broadcast packets are seen on the local subnetwork even though CiscoWorks applications use ESS only for intra-machine messaging.

Workaround:

The problem will be resolved if you install CiscoWorks Bundle Update 1, available on CCO. Bundle stands for The problem will be resolved if you install CiscoWorks Bundle Update 1, available on CCO. Bundle stands for LMS1.3/LMS2.2/RWAN1.3/VMS2.2

CSCeb15839

Apache Webserver supports the TRACE / TRACK methods.

Servers supporting this method are subject to cross-site-scripting attacks, dubbed XST for 'Cross-Site-Tracing', when used in conjunction with various weaknesses in browsers. An attacker may use this flaw to trick your legitimate web users to get their credentials.

Workaround:

The problem will be resolved if you install CiscoWorks Bundle Update 1, available on CCO. Bundle stands for The problem will be resolved if you install CiscoWorks Bundle Update 1, available on CCO. Bundle stands for LMS1.3/LMS2.2/RWAN1.3/VMS2.2

CSCeb13529

Possible security hole in
Apache mod_jk module.

The problem may occur if the Server uses
Apache mod_jk module versions prior to 1.2.1. There is a bug in these versions that may allow an attacker to use chunked encoding requests to desynchronize Apache and Tomcat, and therefore prevent the remote web site from working properly.

Workaround:

The problem will be resolved if you install CiscoWorks Bundle Update 1, available on CCO. Bundle stands for The problem will be resolved if you install CiscoWorks Bundle Update 1, available on CCO. Bundle stands for LMS1.3/LMS2.2/RWAN1.3/VMS2.2

CSCeb44684

PIX MC pages not displayed.

PIX MC pages does not come up because unnecessary jars were set to the CLASSPATH in tomcat.sh.

Workaround:

The problem will be resolved if you install CiscoWorks Bundle Update 1, available on CCO. Bundle stands for The problem will be resolved if you install CiscoWorks Bundle Update 1, available on CCO. Bundle stands for LMS1.3/LMS2.2/RWAN1.3/VMS2.2

CSCeb46559

MICE/CAM to communicate via HTTPS with ACS3.2.

Currently the MICE/CAM component of Common Services communicates with remote ACS server via HTTP mode. Since ACS 3.2 now runs in HTTPS mode, MICE/CAM should be enhanced to communicate via HTTPS.

Workaround:

The problem will be resolved if you install CiscoWorks Bundle Update 1, available on CCO. Bundle stands for The problem will be resolved if you install CiscoWorks Bundle Update 1, available on CCO. Bundle stands for LMS1.3/LMS2.2/RWAN1.3/VMS2.2

CSCeb45532

Apache child process crashes

Apache child process crashes and Apache parent process restarts the child process.

Workaround:

The problem will be resolved if you install CiscoWorks Bundle Update 1, available on CCO. Bundle stands for The problem will be resolved if you install CiscoWorks Bundle Update 1, available on CCO. Bundle stands for LMS1.3/LMS2.2/RWAN1.3/VMS2.2

CSCea56786

System memory gets corrupted.

String size change in License.dll corrupts system memory.

Workaround:

The problem will be resolved if you install CiscoWorks Bundle Update 1, available on CCO. Bundle stands for The problem will be resolved if you install CiscoWorks Bundle Update 1, available on CCO. Bundle stands for LMS1.3/LMS2.2/RWAN1.3/VMS2.2

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.

CSCsd43112

Changes in Australian day light settings affect scheduled backup and/or compaction.

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 backup and/or compaction of database by one hour ahead of the actual desirable time from March 27, 2006 to April 02, 2006.

CSCsd40394

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 12 Internally-Found Resolved Problems 

Bug ID
Summary
Additional Information

CSCin09458

Error message displayed if integration utility was installed alone.

This problem has been resolved.

CSCdx29774

Change password dialog boxes disappeared behind Setup window.

This problem has been resolved.

CSCdt50353

Unable to access help files for user-created management connections after direct upgrade of CiscoWorks.

This problem has been resolved.

CSCds33719

Reinstallation of CD One failed when IPM was installed on same machine.

This problem has been resolved. However, an upgrade from a previous version might fail if you have IPM installed on the same machine. In that case, do the following:

1. Run ipm cw2kseup uninstall

2. Upgrade to CiscoWorks Common Services 2.2.

3. Upgrade IPM.

4. Run ipm cw2kseup install


Customer-Found Resolved Problems

Table 13 Customer-Found Resolved Problems 

Bug ID
Summary
Additional Information

CSCdz03633

SSH implementation in CiscoWorks encrypted SSH packets that should not have been encrypted.

This problem has been resolved.

CSCdx84744

CD One, 5th Edition upgrade from LMS 2.0 failed on Windows 2000 with SP2, during the file copy operation.

This problem has been resolved.

CSCds74983

C drive backup.pl file could not be restored to a different drive backup restore.

This problem has been resolved.


Obtaining Documentation

Cisco provides several ways to obtain documentation, 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 on the World Wide Web at this URL:

http://www.cisco.com/univercd/home/home.htm

You can access the Cisco website at this URL:

http://www.cisco.com

International Cisco websites can be accessed from this URL:

http://www.cisco.com/public/countries_languages.shtml

Documentation CD-ROM

Cisco documentation and additional literature are available in a Cisco Documentation CD-ROM package, which may have shipped with your product. The Documentation CD-ROM is updated regularly and may be more current than printed documentation. The CD-ROM package is available as a single unit or through an annual or quarterly subscription.

Registered Cisco.com users can order a single Documentation CD-ROM (product number DOC-CONDOCCD=) through the Cisco Ordering tool:

http://www.cisco.com/en/US/partner/ordering/ordering_place_order_ordering_tool_launch.html

All users can order monthly or quarterly subscriptions through the online Subscription Store:

http://www.cisco.com/go/subscription

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 Networking Products MarketPlace:

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, U.S.A.) at 408 526-7208 or, elsewhere in North America, by calling 800 553-NETS (6387).

Documentation Feedback

You can submit comments electronically on Cisco.com. On the Cisco Documentation home page, click Feedback at the top of the page.

You can e-mail your comments 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

Cisco provides Cisco.com, which includes the Cisco Technical Assistance Center (TAC) website, as a starting point for all technical assistance. Customers and partners can obtain online documentation, troubleshooting tips, and sample configurations from the Cisco TAC website. Cisco.com registered users have complete access to the technical support resources on the Cisco TAC website, including TAC tools and utilities.

Cisco.com

Cisco.com offers a suite of interactive, networked services that let you access Cisco information, networking solutions, services, programs, and resources at any time, from anywhere in the world.

Cisco.com provides a broad range of features and services to help you with these tasks:

Streamline business processes and improve productivity

Resolve technical issues with online support

Download and test software packages

Order Cisco learning materials and merchandise

Register for online skill assessment, training, and certification programs

To obtain customized information and service, you can self-register on Cisco.com at this URL:

http://tools.cisco.com/RPF/register/register.do

Technical Assistance Center

The Cisco TAC is available to all customers who need technical assistance with a Cisco product, technology, or solution. Two types of support are available: the Cisco TAC website and the Cisco TAC Escalation Center. The type of support that you choose depends on the priority of the problem and the conditions stated in service contracts, when applicable.

We categorize Cisco TAC inquiries according to urgency:

Priority level 4 (P4)—You need information or assistance concerning Cisco product capabilities, product installation, or basic product configuration. There is little or no impact to your business operations.

Priority level 3 (P3)—Operational performance of the network is impaired, but most business operations remain functional. You and Cisco are willing to commit resources during normal business hours to restore service to satisfactory levels.

Priority level 2 (P2)—Operation of an existing network is severely degraded, or significant aspects of your business operations are negatively impacted by inadequate performance of Cisco products. You and Cisco will commit full-time resources during normal business hours to resolve the situation.

Priority level 1 (P1)—An existing network is "down," or there is a critical impact to your business operations. You and Cisco will commit all necessary resources around the clock to resolve the situation.

Cisco TAC Website

The Cisco TAC website provides online documents and tools to help troubleshoot and resolve technical issues with Cisco products and technologies. To access the Cisco TAC website, go to this URL:

http://www.cisco.com/tac

All customers, partners, and resellers who have a valid Cisco service contract have complete access to the technical support resources on the Cisco TAC website. Some services on the Cisco TAC website require a Cisco.com login ID and password. If you have a valid service contract but do not have a login ID or password, go to this URL to register:

http://tools.cisco.com/RPF/register/register.do

If you are a Cisco.com registered user, and you cannot resolve your technical issues by using the Cisco TAC website, you can open a case online at this URL:

http://www.cisco.com/tac/caseopen

If you have Internet access, we recommend that you open P3 and P4 cases online so that you can fully describe the situation and attach any necessary files.

Cisco TAC Escalation Center

The Cisco TAC Escalation Center addresses priority level 1 or priority level 2 issues. These classifications are assigned when severe network degradation significantly impacts business operations. When you contact the TAC Escalation Center with a P1 or P2 problem, a Cisco TAC engineer automatically opens a case.

To obtain a directory of toll-free Cisco TAC telephone numbers for your country, go to this URL:

http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml

Before calling, please check with your network operations center to determine the Cisco support services to which your company is entitled: for example, SMARTnet, SMARTnet Onsite, or Network Supported Accounts (NSA). When you call the center, please have available your service agreement number and your product serial number.

Obtaining Additional Publications and Information

Information about Cisco products, technologies, and network solutions is available from various online and printed sources.

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://www.cisco.com/en/US/products/index.html

Cisco Press publishes a wide range of networking publications. Cisco suggests these titles for new and experienced users: Internetworking Terms and Acronyms Dictionary, Internetworking Technology Handbook, Internetworking Troubleshooting Guide, and the Internetworking Design Guide. For current Cisco Press titles and other information, go to Cisco Press online at this URL:

http://www.ciscopress.com

Packet magazine is the Cisco quarterly publication that provides the latest networking trends, technology breakthroughs, and Cisco products and solutions to help industry professionals get the most from their networking investment. Included are networking deployment and troubleshooting tips, configuration examples, customer case studies, tutorials and training, certification information, and links to numerous in-depth online resources. You can access Packet magazine at this URL:

http://www.cisco.com/go/packet

iQ Magazine is the Cisco bimonthly publication that delivers the latest information about Internet business strategies for executives. 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/en/US/about/ac123/ac147/about_cisco_the_internet_protocol_journal.html

Training—Cisco offers world-class networking training. Current offerings in network training are listed at this URL:

http://www.cisco.com/en/US/learning/le31/learning_recommended_training_list.html