Home | Skip to Content | Skip to Search | Skip to Navigation | Skip to Footer |
Worldwide [change] |Register |About Cisco
Guest

Hierarchical Navigation

CiscoWorks VPN/Security Management Solution

Readme for CiscoWorks VMS 2.2 Update 1

Downloads

Table Of Contents

Readme for CiscoWorks VMS 2.2 Update 1

Description

CiscoWorks VMS 2.2 Documentation

Hardware and Software Requirements

Changes in Browser Support

Changes in Java Support

General Recommendations on Java Plug-in 1.4.1_02

Prerequisites for CiscoWorks VMS 2.2 Update 1

Downloading VMS 2.2 Update 1

Installing VMS 2.2 Update 1

Installing CiscoWorks VMS 2.2 Update 1 on Windows

Installing CiscoWorks VMS 2.2 Update 1 on Solaris

Known Problems

CiscoWorks Common Services SP2: Known Problems

Java Plug-in 1.4.1_02: Known Problems

Resource Manager Essentials 3.5 Update 1: Known Problems

VPN Monitor 1.2.1 Known Problems

Resolved Problems


Readme for CiscoWorks VMS 2.2 Update 1

This document contains the following sections:

• Description

• CiscoWorks VMS 2.2 Documentation

• Hardware and Software Requirements

• Prerequisites for CiscoWorks VMS 2.2 Update 1

• Downloading VMS 2.2 Update 1

• Installing VMS 2.2 Update 1

• Known Problems

• Resolved Problems

Description

CiscoWorks VPN/Security Management Solution (VMS) 2.2 Update 1 contains:

•CiscoWorks Common Services 2.2 Service Pack 2 (includes CiscoView 5.5 Update 1 and CiscoWorks Common Services 2.2 Service Pack 1)

•Resource Manager Essentials 3.5 Update 1

•VPN Monitor and Monitoring Center for Security (Security Monitor) updates

CiscoWorks VMS 2.2 Update 1 provides new support for:

•Java Plug-in 1.4.1_02

•Netscape Navigator 7.1 (Windows)

•Netscape Navigator 7.0 (Solaris)

•Secure Shell 1.99

•Windows 2000 Service Pack 4 (SP4) (client and server)

•Windows XP Service Pack 1a (SP1a) (client)

VMS 2.2 Update 1 also contains resolutions to known problems in VMS 2.2 applications. See the "Known Problems" section for details.

CiscoWorks VMS 2.2 Documentation

For information about installing, troubleshooting, and using VMS 2.2, consult the Quick Start Guide for the VPN/Security Management Solution 2.2 as described in Table 1.

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 VMS 2.2 Documentation

Document Title
Available Formats

Quick Start Guide for the VPN/Security Management Solution 2.2

•Printed document that was included with the product.

•On Cisco.com:

a. Log into Cisco.com.

b. Select Products & Services > Network Management CiscoWorks  > CiscoWorks VPN/Security Management Solution > Technical Documentation > Quick Start.


Hardware and Software Requirements

Hardware and software requirements are the same as those needed for initial CiscoWorks VMS 2.2 installation, with the following additions:

•VMS 2.2 does not support Japanese OS versions.

•Specific updates to browser support (see the "Changes in Browser Support" section)

•Specific updates to Java support (see the "Changes in Java Support" section)

•Support for Service Pack 4

Caution If you have other CiscoWorks bundles installed, you must install those bundle updates in addition to VMS 2.2 Update 1 for your network to function properly.

For a listing of the basic hardware and software requirements, see the Quick Start Guide listed in the "CiscoWorks VMS 2.2 Documentation" section.

Changes in Browser Support

All VMS components support Internet Explorer 6.0 with Service Pack 1 on Windows platforms. Table 2 identifies Netscape Navigator support by individual components where these requirements differ from VMS as a whole.

Table 2 Netscape Navigator Support 

Component
Windows Browser Requirements
Solaris Browser Requirements

CiscoWorks Common Services (CWCS)

•Netscape Navigator 4.79

•Netscape Navigator 7.1

•Netscape Navigator 4.76

•Netscape Navigator 7.0

Management Center for Firewalls (Firewall MC)

•Netscape Navigator 7.1

•Netscape Navigator 7.0

Auto Update Server (AUS)

•Netscape Navigator 7.1

•Netscape Navigator 7.0

Management Center for IDS Sensors (IDS) and Security Monitor

•Netscape Navigator 4.79

•Netscape Navigator 4.76

Management Center for VPN Routers (Router MC)

•Netscape Navigator 7.1

•Netscape Navigator 7.0

Management Center for Cisco Security Agents (CSA MC)

•Netscape Navigator 7.1

•Netscape Navigator 7.0

Resource Manager Essentials (RME)

•Netscape Navigator 4.79

•Netscape Navigator 7.1

•Netscape Navigator 4.76

•Netscape Navigator 7.0

VPN Monitor

•Netscape Navigator 7.1

•Netscape Navigator 7.0


Caution Do not select the option Edit > Preferences > Advanced > Enable Java Plug-in in Netscape Navigator 4.7x, if available. Some CiscoWorks applets might not load properly if this option is selected.

Changes in Java Support

In response to the removal of the Microsoft Virtual Machine (VM) from new Microsoft products going into distribution, the version of CiscoWorks Common Services 2.2 contained in this Update provides Java Plug-in 1.4.1_02 support for those who prefer to continue using Internet Explorer as their browser.

This support is provided as an alternative to the Microsoft VM, not as a replacement for it. If the Microsoft VM is still present in the version of Internet Explorer you use, you can choose to continue using it. If no browser VM is present, CiscoWorks applets will use Java Plug-in 1.4.1_02 as the default.

Providing support for Java Plug-in 1.4.1_02 ensures that CiscoWorks Common Services and the applications it supports remain stable across all current browsers, browser versions, and operating systems. It affects only those CiscoWorks applications that use Java applets, such as CiscoView and Netconfig.

You might see special behaviors the first time you use the updated version of CiscoWorks Common Services 2.2 on Internet Explorer or Netscape Navigator. These behaviors will vary with the operating system, browser, browser version, and Java VM you are currently using.

Table 3 summarizes the conditions under which you will see these behaviors and the actions you should take in each case. Please also refer to the "General Recommendations on Java Plug-in 1.4.1_02" section.

Sun has issued an Alert Notification for Java Plug-in 1.4.1_02. To learn more about this Alert Notification see http://sunsolve.sun.com/pub-cgi/retrieve.pl?doc=fsalert/56380. If you plan to use Java Plug-in 1.4.1_05, see also the "Using Sun Java Plug-in 1.4.1_05" section.

Note In Internet Explorer, a dummy applet gets loaded before the login page. This is to detect whether the browser has a Java VM or not. As a result you might notice a slight delay in getting to the login page.

Table 3 Java Plug-in First-Time Setup Behaviors  

If you are using
You will see this behavior
And you should do this

Internet Explorer with Microsoft VM

You will be asked to install Java Plug-in 1.4.1_02 only when you use a Plug-in application, such as CiscoView or Netconfig.

Follow the recommended installation instructions.

You might check or uncheck Tools > Internet Options > Advanced > Use Java 2 v 1.4.1_02 for <applet>.

If you check it, all CiscoWorks applets will run in Java Plug-in 1.4.1_02.

If you uncheck it, only CiscoWorks applications that require it (e.g., CiscoView, Netconfig) will use Java Plug-in 1.4.1_02; others will use the Microsoft VM.

Internet Explorer without Microsoft VM (on Windows XP)

Instructions to install Java Plug-in 1.4.1_02 appear as soon as you use CiscoWorks Common Services 2.2.

Follow the recommended installation instructions.

If you already have the Internet Explorer option Install on demand (on Windows XP) enabled, a Windows dialog appears asking you to download the Java VM.

1. Click Cancel (not OK) and

2. Follow the recommended installation instructions.

Internet Explorer with an unsupported Java Plug-in (e.g., 1.4.1_03) as your default Java VM

If you use an unsupported Java Plug-in and chose the Internet Explorer option Use <JPI version> for <applet>, you will see a message box saying you are using an unsupported Java Plug-in.

Click OK. You will be directed to a help page. Follow the instructions given in the help page.

Netscape Navigator 4.76 on Solaris, Netscape Navigator 4.78 or 4.79 on Windows

You will be asked to install install Java Plug-in 1.4.1_02 only when you use a plug-in application, like CiscoView, Netconfig, etc.

Follow the recommended installation instructions.

Netscape Navigator 7.x with no Java Plug-in installed

As soon as you use CiscoWorks Common Services 2.2, you will see instructions to install Java Plug-in 1.4.1_02.

Follow the installation instructions.

Netscape Navigator 7.x with an unsupported Java Plug-in installed (e.g., 1.4.1_03)

You will see a message box saying you are using an unsupported Java Plug-in.

Click OK. You will be directed to a help page. Follow the instructions given in the help page.


General Recommendations on Java Plug-in 1.4.1_02

The following sections give general recommendations and procedures to follow when installing and using Java Plug-in 1.4.1_02:

• Installing and Using Java Plug-in 1.4.1_02 on Windows

• Before Using Java Plug-in 1.4.1_02 On Solaris

• Installing and Uninstalling Java Plug-in 1.4.1_02 on Solaris

• Using Sun Java Plug-in 1.4.1_05

Installing and Using Java Plug-in 1.4.1_02 on Windows

When installing or using Java Plug-in 1.4.1_02 on Windows, the guidance offered by the help pages you will be directed to is usually sufficient. You should also be aware of the following:

•Uninstall any older or later Java Plug-in versions and install only the supported Java Plug-in version (1.4.1_02). If you do not follow the uninstall and reinstall sequence, it might cause some co-existence issues.

•In some cases, uninstalling Java Plug-in 1.4.1_02 disables the Microsoft VM in Internet Explorer. To enable the Microsoft VM again, you must install Java Plug-in 1.4.1_02 again.

•If you are using Internet Explorer, we recommend that you set the Security Settings (Tools > Internet Options > Security) to the default level for security zones such as Internet and Local Intranet. If you customize the options, some of the functionality might not work as expected.

•Java Plug-in 1.4.1_02 has some coexistence conflicts with Java Plug-in 1.3.1:

–In the same browser session, if one of applets uses JPI 1.4.1_02 and the another tries to use JPI 1.3.1, the browser will not work properly.

–If you use an applet using JPI 1.3.1 first, and then try to run another applet using JPI 1.4.1_02, the server displays an error message Attachment to a running Virtual Machine failed. SUN does not support multiple VMs in the same browser session.

In general, avoid using applets with different Java Plug-in versions in the same browser session.

•Select Yes for all the Java Plug-in dialog boxes. If you select No in any of the Java Plug-in dialog boxes, exceptions appear on the Java Console. In such a case, close the browser session and start the Java Plug-in again.

When you run CiscoWorks Server in SSL mode, a dialog box prompts you to accept or deny the Certificate. The certificate gives the details about the hostname mismatch, certificate validity and so on.

Select Yes and accept these certificates to get the login Panel. Do not select No in the Certificate dialog boxes.

•Do not resize the browser windows after reloading the page.

While using Internet Explorer 6.0 with Service Pack 1 and Java Plug-in 1.4.1_02, if you run an applet and resize Internet Explorer, only part of the applet is displayed.

If you resize the window to full screen, part of the applet that was not covered will not be displayed properly. To correct this, start the applet again.

You must do the same if you are using Netscape.

•If you are using Netscape 7.1 on Windows please note that some CiscoWorks applications that are launched in new browser windows may not start properly if you have the following option enabled: Edit > Preferences > Privacy & Security > Popup Windows > Block unrequested popup windows. We recommended that you leave this option disabled. It is possible to enable this option and still allow popups for CiscoWorks only; see the Netscape Help for details on how to do this.

Before Using Java Plug-in 1.4.1_02 On Solaris

When installing or using Java Plug-in 1.4.1_02 on Solaris, we recommend:

•Be sure to install Netscape only from the Sun site at http://wwws.sun.com/software/solaris/netscape/get.html.

•Install all the recommended and required Solaris OS patches for Netscape and Java Plug-in 1.4.1_02. If you do not install the patches, you might experience browser problems, core dumps, bus errors, or other abnormal behavior when you access CiscoWorks.

•Be sure to install Java Plug-in 1.4.1_02 using the wrapper script provided with CiscoWorks (pam.sh). This script sets up the environment required for accessing CiscoWorks through Netscape. Do not download and install the Java Plug-in directly.

•If you are using Netscape 7.0, ensure that you have write access to the Netscape 7.0 directory, as you need to configure it to work with Java Plug-in 1.4.1_02.

•If you have installed Java Plug-in 1.4.1_02 using pam.sh, it will overwrite the previous configurations of Java Plug-in 1.3.1.

•Do not access CiscoWorks through Reflection X. You should access CiscoWorks directly from Solaris systems. The browser might not work properly if you do not have the required Solaris patches.

Installing and Uninstalling Java Plug-in 1.4.1_02 on Solaris

When you access an application that requires Java Plug-in 1.4.1_02, you will be redirected to a help page. This page contains instructions to install the Plug-in.

From the help page, download the installable image of the Plug-in. You must uncompress and untar the installable image. When you untar the image, you get the plug-in installation script (pam.sh), a directory named plugin and a README file.

To install Java Plug-in 1.4.1_02 on Solaris:

Step 1 Execute pam.sh.

Step 2 Choose option 1.

Step 3 Configure Java Plug-in with Netscape 4.76 or Netscape 7.0.

You should configure the Java Plug-in to work with at least one of the Netscape versions mentioned in this document to use CiscoWorks.

You can also modify the configurations with Netscape later by choosing Option 3 in the pam.sh script.

Step 4 Before accessing CiscoWorks, source the /jpi.cshrc (csh) or /jpi.profile (if you are using shell script) to set the required environment variables.

To uninstall the Java Plug-in:

Step 1 Execute pam.sh.

Step 2 Choose option 2.

The Plug-in is uninstalled from your system.

Using Sun Java Plug-in 1.4.1_05

Caution Cisco has not fully tested VMS component applications with Sun Java Plug-in 1.4.1_05. You might encounter problems.

Sun Alert Notification 56380 concerns a security vulnerability in Java Plug-in 1.4.1_02. Customers using the SSL features of VMS should review the Sun Alert and determine their level of risk. If you are not using SSL with VMS, you should use the Java Plug-in 1.4.1_02, which is installed with CiscoWorks VMS 2.2 Update 1 automatically.

At the time of this release (October 2003), Java Plug-in 1.4.1_02 was the only version tested and recommended for use with VMS 2.2 Update 1. Cisco will examine additional alternatives, including Sun Java Plug-in 1.4.1_05. Information released after this printing concerning supported versions of the Java Plug-in will be posted on the CiscoWorks Server software download page on Cisco's web site: http://www.cisco.com/pcgi-bin/tablebuild.pl/cw2000-cd-one.

Customers choosing to use Sun's Java Plug-in 1.4.1_05 instead of the one provided in VMS 2.2 Update 1 can apply the plug-in manually using the steps outlined below.

Note that if you change to Java Plug-in 1.4.1_05 on the server and one client, you must change to version 1.4.1_05 on all of your clients. You cannot run the updated version of VMS using clients with a mix of different Java Plug-in versions. Also note that, since Cisco has not fully tested VMS with Java Plug-in 1.4.1_05, you may encounter problems.

To modify your CiscoWorks installation to use Sun Java Plug-in 1.4.1_05:

Step 1 Install CiscoWorks VMS 2.2 Update 1 normally. This includes installation of Java Plug-in 1.4.1_02 on Solaris and Windows clients the first time you run CiscoWorks.

Step 2 On the updated CiscoWorks Server (either Solaris or Windows): Locate the Java Plug-in properties file /NMSROOT/lib/classpath/javaplugin.properties (where NMSROOT is the path to the CiscoWorks Server directory), and change the following entries in the javaplugin.properties file to reflect the new Java Plug-in version:

•Existing entries for Java Plug-in 1.4.1_02:

WIN_IE_VERSION=clsid:CAFEEFAC-0014-0001-0002-ABCDEFFEDCBA

WIN_NS_VERSION=application/x-java-applet;jpi-version=1.4.1_02

SOL_VERSION=application/x-java-applet;jpi-version=1.4.1_02

•Modified Entries for Java Plug-in 1.4.1_05:

WIN_IE_VERSION=clsid:CAFEEFAC-0014-0001-0005-ABCDEFFEDCBA

WIN_NS_VERSION=application/x-java-applet;jpi-version=1.4.1_05

SOL_VERSION=application/x-java-applet;jpi-version=1.4.1_05

Note Do not change the following entry: IE_PLUGINS_PAGE=/plugin/j2re-1_4_1_02-windows-i586-i.exe

Step 3 Save the modified javaplugin.properties file

Step 4 Restart the CiscoWorks Common Services Daemon Manager.

Step 5 Update each Windows client as follows:

a. Download Java Plug-in 1.4.1_05 for Windows.

b. Install the Java Plug-in on the client according to Sun's instructions.

c. Close any running browser instances and start them again.

Step 6 Update each Solaris client as follows:

a. Download Java Plug-in 1.4.1_05 for Solaris

b. Install the Java Plug-in on the client according to Sun's instructions.

c. Locate the jpi.profile and jpi.cshrc files on the client and change the MOZ_PLUGIN_PATH, NPX_PLUGIN_PATH, NPX_JRE_PATH, and similar variables in these files to reflect the path to Java Plug-in 1.4.1_05. For example, assuming that 1.4.1_02 was installed in /opt/jre14102, and that 1.4.1_05 is installed in /opt/jre14105:

Change: MOZ_PLUGIN_PATH=/opt/jre14102/j2re1.4.1_02/plugin/sparc/ns610

To: MOZ_PLUGIN_PATH=/opt/jre14105/j2re1.4.1_05/plugin/sparc/ns610.

d. Close any running browser instances and start them again.

Step 7 Update each Solaris client using Netscape 7.0 as follows:

a. Modify the links to point to the links for Java Plug-in 1.4.1_05:

Change: "NS7_HOME"/plugins/libjavaplugin_oji.so

To: "JPI1.4.1_05_HOME"/plugin/sparc/ns610/libjavaplugin_oji.so

b. Source /jpi.cshrc or /jpi.profile.

c. Close any running browser instances and start them again.

Prerequisites for CiscoWorks VMS 2.2 Update 1

Ensure that you have completed the following tasks before installing VMS 2.2 Update 1. Once you have completed these tasks, you can go on to install this Update using the instructions in the "Installing VMS 2.2 Update 1" section.

Step 1 Install CiscoWorks Common Services 2.2 and the VMS components to be updated. For details, see Quick Start Guide for the VPN/Security Management Solution 2.2 described in the "CiscoWorks VMS 2.2 Documentation" section.

Note If you decide not to install one or more of the VMS components at this point, then decide to install them later, you must reapply VMS 2.2 Update 1 after you install these missing applications.

Step 2 If you installed Resource Manager Essentials (RME), you must also install Incremental Device Update (IDU) 5.0 for Resource Manager Essentials 3.5. IDU 5.0 for RME 3.5 is available to download IDU from Cisco.com at the following URL: http://www.cisco.com/pcgi-bin/tablebuild.pl/cw2000-rme.

Caution If you have received the OpenSSL 0.9.7 patch for CiscoWorks Common Services 2.2 (see bug ID CSCec43722), be sure to install it after you install VMS 2.2 Update 1. If you have already installed the OpenSSL patch, you must reinstall it after you install VMS 2.2 Update 1.

Downloading VMS 2.2 Update 1

CiscoWorks VMS 2.2 Update 1 is available for download on the Cisco Software Center site at: http://www.cisco.com/public/sw-center/cw2000/vms-planner.shtml.

Installing VMS 2.2 Update 1

Note Before installing VMS 2.2 Update 1 on either platform, make sure you have completed the tasks listed in the "Prerequisites for CiscoWorks VMS 2.2 Update 1" section.

VMS 2.2 Update 1 is provided as a single installable file. Use the appropriate procedure to install it:

• Installing CiscoWorks VMS 2.2 Update 1 on Windows

• Installing CiscoWorks VMS 2.2 Update 1 on Solaris

Note You cannot uninstall VMS 2.2 Update 1 after you install it.

Installing CiscoWorks VMS 2.2 Update 1 on Windows

To install CiscoWorks VMS 2.2 Update 1 on Windows:

Step 1 Do one of the following steps:

•Run the installation setup script by unzipping the file CiscoWorks-VMS-2.2-Update-1-w2k-k9.zip first double-click the file CiscoWorks-VMS-2.2-Update-1-w2k-k9.exe, then double-click the file autorun.exe

or

•Select Start > Run and navigate to the location of the file CiscoWorks-VMS-2.2-Update-1-w2k-k9.exe in order to run the autorun.exe file. The CiscoWorks VMS 2.2 Update 1 confirmation dialog box appears.

Step 2 Click Yes.

The Welcome screen appears.

Step 3 Click Next to continue.

The Software License Agreement window opens. To install CiscoWorks VMS 2.2 Update 1 you must accept this agreement.

Step 4 Click Yes to continue.

The installation program checks dependencies and system requirements. The System Requirements dialog box appears.

The System Requirements dialog displays the system requirements, available space in the disk drive and temp directory, and available memory in megabytes.

Step 5 Click Next to Continue.

The Summary dialog box appears, displaying the updates that will be installed and the settings for the installation.

Step 6 Click Next to Continue.

The setup screen appears, displaying installation progress while files are copied and applications are configured.

The Setup Complete screen appears.

Note If the system you are updating has had some, but not all, of these updates previously installed, the install script will list the new updates and those it will reinstall. Enter 1 to install only the new updates not yet present on the system. Enter 2 to install all new updates and reinstall all old updates.

Step 7 Click Finish.

Step 8 To verify the installation:

a. Launch CiscoWorks.

b. Select Server Configuration > About the Server > Applications and Versions.

The About the Server page is displayed.

c. If the VMS 2.2 Update 1 installation was successful, you will see the following entries in the Packages Installed table on this page:

 

Name

Version
Installed Patches

CiscoWorks Common Services with SP2

CiscoWorks Common Services with SP2

2.2

2

Resource Manager Essentials with Update 11

Resource Manager Essentials with Update 1

3.5

3

VPN Monitor Update2

VPN Monitor Suite

1.2.1

1

IDS MC and Security Monitor3

IDS MC

1.2

1

1 This will be visible only if you have installed RME.

2 This will be visible only if you have installed VPN Monitor.

3 This will be visible only after you have installed IDS MC and Security Monitor.


Installing CiscoWorks VMS 2.2 Update 1 on Solaris

Note If you have downloaded VMS 2.2 Update 1 for Solaris, you must first extract the installable files from CiscoWorks-VMS-2.2-Update-1a-sol-k9.tar.

To install the VMS 2.2 Update 1 on Solaris:

Step 1 Log in as root on the system on which you installed Common Services.

Note The user installing VMS 2.2 Update 1 must have superuser privileges on the system being updated.

Step 2 Untar the CiscoWorks-VMS-2.2-Update-1a-sol-k9.tar file.

Step 3 Copy the file setup.sh to the appropriate directory.

Step 4 Start the installation using one of the following methods:

•For a local installation, enter:

# sh ./setup.sh

•For a remote installation, enter:

# cd remotedir

# sh ./setup.sh

where remotedir is the remote location where the CD-ROM is mounted.

The Software License Agreement (SLA) appears.

Step 5 Accept the SLA to continue.

The setup script displays a list of the updates to be installed or reinstalled. Press any key to install or reinstall all of the updates, or enter q to cancel installation.

Note If the system you are updating has had some, but not all, of these updates previously installed, the install script will list the new updates and those it will reinstall. Enter 1 to install only the new updates not yet present on the system. Enter 2 to install all new updates and reinstall all old updates.

When you press Enter, files are copied and applications are configured. Installation takes approximately 15 minutes.

When installation is finished, the setup script exits.

Step 6 To verify the installation:

a. Launch CiscoWorks.

b. Select Server Configuration > About the Server > Applications and Versions.

The About the Server page is displayed.

c. If the VMS 2.2 Update 1 installation was successful, you will see the following entries in the Packages Installed table on this page:

 

Name

Version
Installed Patches

CiscoWorks Common Services with SP2

CiscoWorks Common Services with SP2

2.2

2

Resource Manager Essentials with Update 11

Resource Manager Essentials with Update 1

3.5

3

VPN Monitor Update2

VPN Monitor Suite

1.2.1

1

1 This will be visible only if you have installed RME.

2 This will be visible only if you have installed VPN Monitor.


Known Problems

This section contains:

• CiscoWorks Common Services SP2: Known Problems

• Java Plug-in 1.4.1_02: Known Problems

• Resource Manager Essentials 3.5 Update 1: Known Problems

• VPN Monitor 1.2.1 Known Problems

Note To obtain more information about known problems, access the Cisco Software Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. You will be prompted to log in to Cisco.com.

CiscoWorks Common Services SP2: Known Problems

Table 4 lists problems known to affect CiscoWorks Common Services 2.2 with Service Pack 2 (including CiscoView 5.5 Update 1) on Solaris. Table 5 lists problems known to affect the same products on Windows platforms.

Table 4 CiscoWorks Common Services 2.2 SP2: Known Problems on Solaris  

Bug ID
Summary
Explanation

None

Nessus reports false TRACE/TRACK vulnerability.

TRACE / TRACK vulnerability reported by Nessus on CiscoWorks server reports a false positive in Ciscoworks Common Services 2.2 Service Pack 1. It is caused by a flaw in the NASL script that Nessus uses to test this vulnerability. Since TRACK is not implemented in the Apache server, Apache replies to TRACK requests with a Method Not Implemented message. The NASL script does not handle this reply properly, and signals a false positive.

CSCeb62374 (CiscoView)

Unable to print chassis view.

On Solaris clients, when you click the printer icon in the lower the right-hand corner of the CiscoView screen to print the chassis view, the view sometimes might not be printed.

To work around this problem, select File > Print from the browser's main menu.

CSCin50174

You see exceptions in the Java Console while accessing the options in the dropdown list boxes in MAAS applets or in RME applications.

You can ignore these exceptions.

CSCin50966

While backing up data using VPN/Security Management Solution > Administration > Common Services > Backup database, the popup Progress Bar applet displays incorrectly.

The Progress Bar flickers during the backup process and the bar might not display consistently.

No workaround available. This behavior does not affect backup functionality.

CSCin54021

While executing pam.sh to install Java Plug-in 1.4.1_02, you reject the Sun license agreement and the installation proceeds, but the Java Plug-in is not installed.

The Java Plug-in does not get installed, even though the message says it was not installed.

To work around this problem, accept the License agreement to install the Java Plug-in.

CSCsa01571 (CiscoView)

Unable to specify host name of device list import source.

On Solaris clients running Netscape 7.0:

1. Launch Common Services 2.2.

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

3. With the Campus or RME radio button selected, try to update the Host Name field with the correct information. You will not be able to select or modify the field's contents.

To work around this problem, click the window of any other open application and then return to the CiscoView Import Device List window to specify a host name.

Note You need to open another application if one is not open already.

CSCsa01906

Solaris Netscape 4.76 malfunctions inconsistently when online help is selected.

The Netscape malfunction happens while launching help from a Plug-in applet like CiscoView, or an RME application like Netconfig or Config Editor.

To work around this problem, use online help by clicking Help in the main CiscoWorks Desktop (next to Logout). You can browse through the contents from the help page.


Table 5 CiscoWorks Common Services 2.2 SP2: Known Problems on Windows  

Bug ID
Summary
Explanation

None

Nessus reports false TRACE/TRACK vulnerability.

TRACE / TRACK vulnerability reported by Nessus on CiscoWorks server reports false positive in CiscoWorks Common Services 2.2 Service Pack 1. It is caused by a flaw in the NASL script that Nessus uses to test this vulnerability. Since TRACK is not implemented in Apache web server, Apache replies to TRACK requests with a Method Not Implemented message. The NASL script does not handle this reply properly, and signals a false positive.

CSCdz34376

During installation of updates, a "files locked" message displays for file jpishare.dll in NMSROOT\MDC\jre\bin\.

This occurs when:

1. Server and Client are running on the same system.

2. A browser session which uses the Java Plug-in is open.

3. You have started reinstallation.

The reinstallation might abort after displaying the "locked files" messages for the files jpishare.dll and jpins32.dll.

To work around this problem, we recommend that you close all browser sessions and any Plug-in applets launched, before the installation starts.

CSCeb60816
(CiscoView)

Printout of chassis view is sometimes grayed out.

On Windows clients, when you click the Printer icon in the lower right-hand corner of the CiscoView screen to print the chassis view, in some instances, the resulting printout is grayed out.

No workaround available.

CSCec03791

Netscape 7.1 problems:

•Closing the Help window throws Java Exceptions.

•The first element in the Help Contents tree appears empty.

To work around this problem do one of the following:

•Ignore the Java Exceptions. They do not affect functionality.

•Click the Index tab and then click the Contents tab. All elements in the Contents tree will be displayed.

CSCin50966, CSCeb73291, CSCin51794

While backing up data using VPN/Security Management Solution > Administration > Common Services > Backup database, the popup Progress Bar applet displays incorrectly.

The Progress Bar applet flickers during the backup process and the bar might not display consistently.

This does not affect VMS functionality and this problem can be ignored.

CSCin51727

Java Plugin 1.4.1_02 installation on Windows hangs at 100% if the Netscape 7.x browser is open.

You will see this even if Netscape 7.x Quick Launch is running in the system tray.

To work around this problem, close all running Netscape 7.x instances and Netscape 7x Quick Launch before installing Java Plugin 1.4.1_02. If installation hangs with 100% CPU usage and you use Task Manager to kill the process IKernel.exe (doing this is not recommended), recover and reinstall the Plug-in by performing the following steps:

1. Access the Windows registry.

2. Backup the registry contents.

3. Delete the key HKEY_LOCAL_MACHINE/Software/JavaSoft
(Check the contents for JRE 1.4.1_02 before deleting).

4. Delete the uninstall key that mentions "j2re/1.4.1_02 / Java run time" (HKEY_LOCAL_MACHINE/Software/Microsoft/Windows/CurrentVersion/Uninstall).

5. Find the uninstall directory (the values in the uninstall Registry keys will say where it is) and delete it.

For example: In C:\Program Files\InstallShield Installation Information\{registry id}, check the Setup.ini file content for values like "j2re/jre/1.4.1_02" before deleting.

CSCin50359 (related bug)

If you are using Internet Explorer to use CiscoWorks, but do not have the Microsoft VM installed, you will be prompted to install JVM but will not be able to download the JVM.

If you have enabled the Internet Explorer Install on demand option, you will see dialogs prompting you to download the JVM. You will not be able to download JVM from these links.

To work around this problem, click Cancel on these dialogs. You will be redirected to a help page which will give you directions to download JPI for CiscoWorks.

If you do not have Install on demand enabled, you will be automatically redirected to the help page while launching CiscoWorks.

CSCin51984

You see Java exceptions while using RME applications like Hardware Report and Device Center.

These appear in the Java Console and include java.lang.IllegalArgumentException: null source.

To work around this problem, ignore these exceptions, as they do not affect functionality.

CSCin53036

Selecting different JRE versions to be used for Java Plugin 1.4.1_02, other than the default JRE (through the Plug-in Control Panel) results in unexpected behavior.

To work around this problem, use only the default JRE for the Plug-in. Other JRE versions are not recommended.

CSCin53790

You cannot use the Tab key to select components.

This occurs in some applets running in the Plug-in environment.

To work around this problem, use the mouse to navigate between components.

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.

To work around this problem, use Internet Explorer 6.0 with Service Pack 1 on Windows 2000 Professional or Server with Service Pack 4.

CSCin57604

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

This happens when you use Internet Explorer 6.0 with Service Pack 1 and the Internet Explorer patch Q822925 on Windows 2000 Professional or Server with Service Pack 3.

To work around this problem, use Internet Explorer 6.0 with Service Pack 1 on Windows 2000 Professional or Server with Service Pack 4.


Java Plug-in 1.4.1_02: Known Problems

Table 6 lists problems known to affect Java Plug-in 1.4.1_02.

.

Table 6 Java Plug-in 1.4.1_02: Known Problems  

Bug ID
(Severity)
Summary
Explanation

None

JPI 1.4.1_02 coexistence with Java Plug-in 1.3.1.

If in the same browser session, one of the applets uses Java Plug-in 1.4.1_02 and the other tries to use Java Plug-in 1.3.1, the browser fails.

If an applet using Java Plug-in 1.3.1 is used first and then an applet using Java Plug-in 1.4.1_02 is used, an error message Attachment to a running Virtual Machine failed is displayed.

To work around this problem, uninstall all previous versions of Java Plug-in and install only Java Plug-in 1.4.1_02.

None

Uninstalling 1.4.1_02 disables Internet Explorer JVM.

Uninstalling Java Plug-in 1.4.1_02 disables Microsoft VM in Internet Explorer.

To enable the Microsoft VM again, you must install Java Plug-in 1.4.1_02 again.

None

SSL mode requires certificate acceptance.

When you use CiscoWorks server in SSL mode, a Plug-in dialog box appears. This dialog box prompts you to accept or deny a certificate. Accept the certificate to continue working. If you click No in the dialog box, a series of exceptions appears in the Java console.

To recover, close the browser, relaunch CiscoWorks, and accept the certificate when it is next presented.


Resource Manager Essentials 3.5 Update 1: Known Problems

Table 7 lists problems known to affect RME 3.5 Update 1.

Table 7 Resource Manager Essentials 3.5 Update 1: Known Problems  

Bug ID
Summary
Explanation

None

On Windows only: RME Reports get minimized when Java Plug-in 1.4.1_02 is in use.

Sometimes when you try to generate an RME report, the report gets minimized.

For example, if you:

1. Click Resource Manager Essentials > Administration > Inventory > Check Device Attributes.

2. Select the devices whose device information you want to view.

3. Click Finish.

The Check Device Attributes Report window will be minimized as a taskbar icon.

To work around this problem, use the browser VM, if your browser has VM.

CSCsa01609

On Windows only: Buttons are not aligned properly on the Distribution Sequence Window of Software Management.

This problem occurs using Netscape 7.1 when you perform any one of the following tasks:

•Distribute by Devices

•Distribute by Images

•Remote Staging and Distribution

On the software Distribution Sequence window that appears, the buttons, Back, Next, Details, and Help are not aligned properly.

To work around this problem, use either of these browsers:

•Internet Explorer 6.0 or 6.0 SP1

•Netscape Navigator 4.78 or 4.79.

CSCin49900

On Solaris only: Netscape 7.0 malfunctions randomly.

This problem occurs when you try to perform a task when another task is still processing.

For example, if you:

1. Click Resource Manager Essentials > Administration > Inventory > Custom Reports.

2. Click Create.

3. Select View by launching the device selector.

4. Select Report Type before the Device Selection screen appears.

Netscape might malfunction.

To work around this problem, wait until the previous task is completed before beginning a new one.

CSCin57076

On Solaris only: Netscape 7.0 does not resize the NetConfig window properly.

This problem occurs when you start NetConfig (Resource Manager Essentials > Configuration Management). A part of the screen is not visible and prevents you from proceeding to the next step in the job creation panes.

This problem has no consistent workaround. However, one possible workaround is to close and then restart NetConfig.


VPN Monitor 1.2.1 Known Problems

Table 8 lists problems known to affect RME 3.5 Update 1.

Table 8 VPN Monitor Known Problems  

Bug ID
Summary
Explanation

CSCeb69574

Netscape 7.1 on Windows clients: Popup blockers may prevent application from launching.

If you are using Netscape 7.1 on Windows please note that some CiscoWorks applications that are launched in new browser windows may not start properly if you have the following option enabled: Edit > Preferences > Privacy & Security > Popup Windows > Block unrequested popup windows.

To work around this problem, leave this option disabled. It is possible to enable this option and still allow popups for CiscoWorks only; see the Netscape Help for details on how to do this.


Resolved Problems

Table 9 describes previously reported problems in CiscoWorks Common Services SP2 by installing VMS 2.2 Update 1 and Firewall MC 1.2.2.

Table 9 CiscoWorks Common Services 2.2 SP2: Resolved Problems  

Bug ID
(Severity)
Summary
Additional Information

CSCdx74061

Two steps needed to schedule backups and compacts.

This problem has been resolved

CSCea56786

String size change in License.dll corrupted system memory.

This problem has been resolved

CSCeb06767

Consolidated bug to track a patch for Apache and security fix (consolidates CSCea72180, CSCea91777, CSCeb15839, CSCeb13529).

These problems have been resolved

CSCeb08436

The CiscoWorks ESS process broadcast on UDP port 42350.

This problem has been resolved.

CSCeb08489

Login panel showed the username of the previous user and inherited privileges of this user.

These problems have been resolved

CSCeb14203

Firewall MC 1.2.2 corrects a problem in which portions of the GUI that use Java applets, including the Object Selector, might blur when you access them or resize the application window.

This problem has been resolved.

CSCeb15620

Firewall MC backup failed even after 50 tries.

This problem has been resolved

CSCeb37909

Temporary directories are not removed after installation.

Remove files with sensitive data, and possible leftovers from previous installations.

CSCec46641

Firewall MC 1.2.2 corrects a problem in which deleting a static translation rule corrupts existing Firewall, AAA, Web Filter and Translation rules that share an IP address with the static translation rule that you deleted.

This problem has been resolved.

CSCin43722

SqlcoreDB terminated before dependent daemons shut down.

This problem has been resolved

CSCeb45532

Apache child process crashed and Apache parent process restarted the child process.

This problem has been resolved

CSCeb46559

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

This problem has been resolved

CSCeb49238

Increased default tomcat heap size for Solaris.

This problem has been resolved

CSCin44573

Solaris Restore DB after password change failed.

This problem has been resolved

CSCin50393

CiscoWorks Common Services 2.2 SSH package should support SSH version 1.99.

CiscoWorks Common Services 2.2 SP2 supports secure shell 1.99.