Quick Start Guide

LAN Management Solution, Release 2.2 (Maintenance Kit)

1 SUPPLEMENTAL LICENSE AGREEMENT

IMPORTANT-READ CAREFULLY: This Supplemental License Agreement ("SLA") contains additional limitations on the license to the Software provided to Customer under the Software License Agreement between Customer and Cisco. Capitalized terms used in this SLA and not otherwise defined herein shall have the meanings assigned to them in the Software License Agreement. To the extent that there is a conflict among any of these terms and conditions applicable to the Software, the terms and conditions in this SLA shall take precedence.

By installing, downloading, accessing or otherwise using the Software, Customer agrees to be bound by the terms of this SLA. If Customer does not agree to the terms of this SLA, Customer may not install, download, or otherwise use the Software. When used below, the term "server" refers to central processor unit.

ADDITIONAL LICENSE RESTRICTIONS

Installation and Use

The Software components are provided to Customer solely to install, update, supplement, or replace existing functionality of the applicable Network Management Software product. Customer may install and use following Software components:

•CiscoWorks Common Services with CiscoView: Contains shared resources used by other components in this bundle. In many cases, all components in this bundle can be installed on a single server. If some components of this bundle are installed on separate servers, a copy of CiscoWorks Common Services can be installed with each component in Customer's network management environment.

•Resource Manager Essentials (Essentials): May be installed on one (1) server in Customer's network management environment.

•Campus Manager (Campus): May be installed on one (1) server in Customer's network management environment.

•Device Fault Manager (DFM): May be installed on one (1) server in Customer's network management environment.

•nGenius Real Time Monitor (RTM): May be installed on one (1) server in Customer's network management environment.

You must install LMS on a system that meets specific requirements. You must configure client systems and some applications before use.

In this document you will find:

•LMS contents, including links for accessing online documentation.

•New features added to this release.

•Hardware and software requirements for optimal performance.

•Upgrade paths and pointers to additional documentation that provides detailed procedures for installing each product. If you already have other CiscoWorks bundled products installed on your system, you might not need to install all of the products included in LMS.

On Solaris

If you are prompted to validate the image, run the setup.sh command from a directory other than /cdrom/cdrom0. You may be requested to eject and reinsert CDs during validation. This cannot be done if you are running setup.sh from the /cdrom/cdrom0 directory.

To validate DFM:

Step 1 You are prompted to accept (and view) the license agreement. Press Enter. The installation program stops CiscoWorks and performs a requirements check.

Step 2 Depending on your configuration, you may be prompted to validate your DFM image as follows:

Step 3 Insert a DFM 1.2 (or earlier) CD into one of your system drives. (Close the File Manager window that appears.) The installation software starts validating the DFM image.

Step 4 After validation, the following message appears:

Please reinsert the original CD to complete the installation.

Press any key to continue.

Reinsert the original CD (containing DFM 1.2 Updated for Common Services Version 2.2) into the drive (close the File Manager window that appears) and continue the installation.

If the DFM image cannot be validated-that is, if you do not have a DFM 1.2 (or earlier) CD-the installation cannot proceed. Contact your Cisco sales representative.

On Windows

If you are prompted to validate the DFM image, insert a DFM 1.2 (or earlier) CD into one of your system drives. If the DFM product CD is already in the CD-ROM drive and you stopped the installation process to close programs or if Autostart is disabled, click setup.exe to restart the process.

When autoplay is enabled and the DFM product CD is inserted, a new installation window appears. Click Cancel in each new installation window.

If the DFM image cannot be validated-that is, if you do not have a DFM 1.2 (or earlier) CD-the installation cannot proceed. Contact your Cisco sales representative.

LMS Contents

Table 1 describes the contents of the LAN Management Solution, Release 2.2 for Solaris and Windows.

Table 1 LAN Management Solution 2.2 Contents

This product...

Allows you to...

And includes these components

CiscoWorks Common Services 2.2 (Includes CiscoView 5.5)

Provide common software and services for all other LMS products. You can deploy, monitor, and troubleshoot devices across your network.

The optional Fault History drop-in lets you store and access historical information about alerts and faults that are detected and processed by DFM. For location details, see "Additional Information Online" section.

•Express, Typical and Custom Installs: Reduces the number of user interactions during the install process. The Express install is faster than the Typical and Custom install.

2. CiscoView 5.5 contains the following new features:

•Support for remote and local upgrades from CD One, 4th and 5th Editions, to Common Services 2.2.

•Support for all Common Services 2.2 compliant browsers and Java Plug-ins.

•Support for the Common Services 2.2 installation framework and packaging mechanism.

•Support of Audit Trail functionality.

•Background Discovery.

3. Resource Manager Essentials 3.5 contains the following new features:

•Support for over 60 new devices. For a list of these devices, see the Supported Devices Table for Resource Manager Essentials 3.5, available on Cisco. com (also see Table 21).

•Significant performance enhancements over the previous version.

•Support during job creation for specification of the username and password for selected devices. This feature is available in ConfigEditor, NetConfig and NetShow.

•A new SWIM workflow that allows users to select an image, the appropriate devices, and then schedule. This new workflow reduces the amount of time it takes to create a job (especially if the image to be deployed is known) by eliminating the Image Recommendation phase.

•A new SWIM workflow that allows users to optimize bandwidth use by storing on a router's flash memory the image they want to deploy, then instructing devices to retrieve the image from the router.

The requirements listed are for managing 500 devices, with all applications hosted on a single server.

If you are managing more than 500 devices or if you are running additional Cisco or third-party applications on the servers, the requirements might be higher. See the individual LMS application installation guides for specific product requirements.

1A Sun UltraSPARC II running Solaris 2.7 or 2.8 is the minimum recommended hardware configuration. If you plan to manage a network with more than 500 devices, or run other management solutions on the same server, an UltraSPARC III running Solaris 2.8 is strongly recommended.

2LAN Management Solution 2.2 supports only the US English and Japanese versions of these operating systems. It does not support any other language versions. Set the default locale to US-English for the US-English version and Japanese for the Japanese version.

1LAN Management Solution 2.2 supports only the US English and Japanese versions of these operating systems. It does not support any other language versions. Set the default locale to US-English for the US-English version and Japanese for the Japanese version.

3This version of LMS does not support Terminal Services on Windows 2000 Advanced Server. Terminal Services must be turned off when you upgrade LMS.

4Upgrade LMS 2.2 on an NTFS file system. Do not upgrade LMS 2.2 on a FAT file system. To verify the file system, open My Computer on the Windows desktop, right-click the drive and select Properties from the popup menu. The file system field appears in the General tab of the Properties dialog box.

4 Upgrade Paths

You might already have the latest version of another CiscoWorks bundled product installed on your LMS bundled products. Review the information in Table 8 to determine what software is required for the LMS components to function properly.

Table 8 Recommended Upgrade Paths

If you are upgrading CiscoWorks LAN Management Solution (LMS) on a system that has...

Then do this

LMS 2.0 or 2.1 installed

Upgrade to LMS 2.2 using the instructions in this Quick Start Guide (Maintenance Kit).

LMS 1.1 or 1.2 installed

Upgrade to LMS 2.2 using the instructions in this Quick Start Guide (Maintenance Kit).

•Locate the PDF versions of the installation guides for each LMS application. Print them or have them open for viewing while you perform the upgrade. For details on locating the installation guides, see the application upgrade sections of this Quick Start Guide.

•Close all open or active programs. Do not run other programs during the upgrade process.

•Be aware of the following:

–You must upgrade CiscoWorks Common Services 2.2 before upgrading any other applications, except nGenius Real-Time Monitor 1.4 Service Pack 6.

–Once you have upgraded CiscoWorks Common Services 2.2, you must upgrade each LMS 2.2 application separately. While it is strongly recommended that you follow the "Order of Upgrade" section, you can upgrade the other applications of LMS 2.2 in any order.

–You may be asked to validate your DFM image if you are installing DFM using this Maintenance Kit CD (for CiscoWorks LAN Management Solution 2.2) during installation.

Prerequisites

This section describes the factors that you should consider before upgrading LMS 2.2.

Important Upgrade Notes

This section contains important information that you should read before you begin upgrade:

•To ensure that you retain the latest device support and bug fixes for Resource Manager Essentials, Campus Manager and Device Fault Manager, you must install the latest Incremental Device Updates (IDU). For download locations, see "Additional Information Online" section.

Install IDU after upgrading the application.

•CiscoWorks applications are installed in the default directories:

–On Solaris: /opt/CSCOpx

–On Windows: SystemDrive:\Program Files\CSCOpx

If you select another directory during upgrade, the application is installed in that directory.

•On Solaris, if you select an upgrade directory different from the default, the /opt/CSCOpx directory is created as a link to the directory you selected. If you remove the link after upgrade, the product might malfunction.

On Windows, if errors occur during upgrade, check the upgrade log in the root directory on the drive where the operating system is installed. Each upgrade creates a new log file. For example, the CiscoWorks Common Services upgrade creates SystemDrive:\CiscoWorks_setupxxx.log, where xxx is the log file for the last CiscoWorks application upgraded.

•You can press Ctrl-C (on Solaris) or click Cancel (on Windows) at any time to end the upgrade. However, any changes to your system (for example, installation of new files or changes to system files) will not be undone.

On Solaris, we do not recommend ending the upgrade, using Ctrl-C. You will be required to manually cleanup the installation directories.

•If you want to use secure access between the client browser and the management server, you can enable or disable SSL from the CiscoWorks desktop.

If SSL is enabled:

–The URL begins with https instead of http to indicate a secure connection.

–The port number succeeding the server name is 1742 instead of 1741.

You cannot enable SSL on the CiscoWorks Server if there is an application that is not SSL-compliant installed on the Server.

For help with SSL, consult the User Guide for CiscoWorks Common Services 2.2.

From the CD-ROM root directory, look for \\Documentation\UserGuideForCommonServices.pdf

•Network inconsistencies might cause installation errors if you are upgrading from a remote mount point.

•Applications not supported by CiscoWorks Common Services 2.2 are disabled during upgrade.

•Device Fault Manager 1.2 Updated for Common Services 2.2 is not SSL compliant. You may be asked to validate your DFM image if you are installing DFM using this Maintenance Kit CD (for CiscoWorks LAN Management Solution 2.2) during installation.

If your CiscoWorks Management Server is integrated with any Network Management Station (NMS) in your network using the integration utility (Network Management Integration Module), you must perform the integration every time when you enable or disable SSL in the CiscoWorks Common Services 2.2 Server. You must do this to update the application registration in the NMS.

For help with NMS integration, consult the section "Integrating with Third-Party Vendors" section in Using CiscoView 5.5. You can find this document:

–On the installation CD-ROM, in Adobe Acrobat PDF form.

From the CD-ROM root directory, look for //Documentation/ug_ciscoview.pdf.

For nGenius Real-Time Monitor

This section contains important information specific to nGenius Real-Time Monitor that you should read before you begin upgrade.

•nGenius Real-Time Monitor is not SSL compliant.

•nGenius Real-Time Monitor is installed in the default directories:

–On Solaris: /opt/NetScout

–On Windows: SystemDrive:\NetScout

•We recommend that you install nGenius Real-Time Monitor on a separate server for optimal performance. If you install nGenius Real-Time Monitor and Device Fault Manager (DFM) on the same server, it might result in a port conflict.

nGenius Real-Time Monitor uses ports 162 and 395 to listen for traps and events. If you are using nGenius Real-Time Monitor with DFM on the same server, you must configure DFM to forward traps to port 395. nGenius Real-Time Monitor will only accept traps forwarded from DFM.

For more information, see the Installation Guide for Device Fault Manger and the Supplement and Release Notes for NetScout nGenius Real-Time Monitor Release 1.4 Service Pack 6.

•If CiscoWorks and nGenius Real-Time Monitor are installed on different systems, or if nGenius was installed before CiscoWorks, you must manually copy the Cisco Management Connection (CMC) files to the location specified in the CiscoWorks installation.

After the CMC files are in place, you must reboot the system for the changes to take effect. Then, when you select nGenius Server, Traffic Monitor, Packet Analyzer, or Voice Monitor, an nGenius graphic is displayed in the main CiscoWorks window (Management Connection) and the selected application starts.

The nGenius system administrator can create the same users and apply the same privileges from CiscoWorks to the nGenius system. See Supplement and Release Notes for NetScout nGenius Real-Time Monitor Release 1.4 Service Pack 6 for details.

•If the server has other Cisco bundled products already installed, which use CD One or CiscoWorks already installed, you must follow the recommended upgrade actions described in the "Upgrade Paths" section.

•If the server has CD One already installed, you must follow the recommended upgrade actions described in the "Upgrade Options" section.

Upgrading to CiscoWorks Common Services 2.2 on Solaris

Step 1 Locate Installation and Setup Guide for CiscoWorks Common Services (Includes CiscoView 5.5) on Solaris. The document is available:

•On the installation CD-ROM, in Adobe Acrobat PDF form.

From the CD-ROM root directory, look for //Documentation/InstallSetupGuideForComSerCVSol.pdf

Step 2 In Chapter 2, "Installing CiscoWorks Common Services", read the section "Preparing to Install CiscoWorks Common Services". As explained in that section, be sure you:

•Have root access to the server on which you plan to upgrade CiscoWorks Common Services.

•Know the server's IP address.

•Verify that the TCP ports that CiscoWorks Common Services uses will not create conflicts with existing applications. For details, see Table 7 in this document.

Step 3 Determine the password that you want the CiscoWorks Common Services administrator to use. For rules to follow when forming passwords, see the section "Admin Password" in Appendix C, "Password Information".

Step 4 Follow the steps in the section "Performing an Upgrade Installation", in Chapter 2, "Installing CiscoWorks Common Services". While performing the upgrade:

•If you are performing a local upgrade: Back up your data.

To perform this task, follow the steps in "Backing Up Your Data" in Chapter 2.

•If you are performing a remote upgrade: Export your data to a new installation.

To perform this task, follow the steps in "Exporting the Data" in Chapter 2.

•Select an Express upgrade.

Select a Typical or Custom upgrade only if you want to specify a destination directory other than the default or want to set other CiscoWorks parameters. For details on the parameters you can set, see Appendix D, "User Inputs for the Installation".

If you select a Typical or Custom upgrade, you must upgrade all products. Otherwise, LMS will not function correctly.

Step 5 After you complete the upgrade, prepare to use CiscoWorks Common Services by:

a. Configuring the CiscoWorks server.

b. Configuring your client.

c. Accessing the CiscoWorks navigation tree.

Follow the steps in Chapter 3, "Preparing to Use CiscoWorks".

If you receive error messages during the upgrade, or cannot complete the tasks in this step, see Appendix A, "Troubleshooting the Installation".

Upgrading to CiscoWorks Common Services 2.2 on Windows

Before you begin:

•If you are using Windows, do not use a cloned version of the administrator account.

•On Windows, when prompted to replace a newer file with an older file, you should always keep the newer file.

•On Windows, do not select an encrypted directory for upgrade. CiscoWorks Common Services 2.2 does not support directory encryption.

Step 1 Locate Installation and Setup Guide for CiscoWorks Common Services (Includes CiscoView 5.5) on Windows. The document is available:

•On the installation CD-ROM, in Adobe Acrobat PDF form.

From the CD-ROM root directory, look for CD-ROMDrive\Documentation\InstallSetupGuideForComSerCVWin.pdf

Step 2 In Chapter 2, "Installing CiscoWorks Common Services", read the section "Preparing to Install CiscoWorks Common Services". As explained in that section, be sure you:

•Verify that the server on which you plan to upgrade CiscoWorks Common Services is not configured as a domain controller, does not use the FAT file system, and does not have Windows XP installed.

•Have installed all of the required Windows software on the server.

•Verify that the TCP ports CiscoWorks Common Services uses will not create conflicts with existing applications. For details, see Table 7 in this document.

Step 3 Determine the password that you want the CiscoWorks Common Services administrator to use. For rules to follow when forming passwords, see the section "Admin Password" in Appendix B, "Password Information".

Step 4 Follow the steps in the section "Performing an Upgrade Installation", in Chapter 2, "Installing CiscoWorks Common Services". While performing the upgrade:

•If you are performing a local upgrade: Back up your data.

To perform this task, follow the steps in "Backing Up Your Data" in Chapter 2.

•If you are performing a remote upgrade: Export your data to a new installation.

To perform this task, follow the steps in "Exporting the Data" in Chapter 2.

•Select an Express upgrade.

Select a Typical or Custom upgrade only if you want to specify a destination directory other than the default or want to set other CiscoWorks parameters. For details on the parameters you can set, see Appendix D, "User Inputs for the Installation".

If you select a Typical or Custom upgrade, you must upgrade all products. Otherwise, LMS will not function correctly.

Step 5 After you complete the upgrade, prepare to use CiscoWorks Common Services by:

a. Configuring CiscoWorks Server.

b. Accessing the CiscoWorks navigation tree.

Follow the steps in Chapter 3, "Preparing to Use CiscoWorks Common Services".

If you receive error messages during the upgrade, or cannot complete the tasks in this step, see Appendix A, "Troubleshooting the Installation".

Step 2 Follow the steps in the section "Upgrading from a Previous Version", in Chapter 1, "Installing Essentials".

As explained in this section, we recommend that you change the Resource Manager Essentials database password and back up the database before upgrading.

If you are upgrading an evaluation version of Essentials 3.5, follow the steps in the section "Reinstalling or Upgrading from the Evaluation Version", also in Chapter 1.

Step 3 After you complete the upgrade, verify that Essentials was upgraded correctly as follows:

a. Access the CiscoWorks desktop.

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

CiscoWorks About the Server page appears.

c. Check the Applications Installed table. Essentials should be listed as installed and enabled on your system. Follow the steps in Chapter 2, "Preparing to Use Essentials".

If you receive error messages during the upgrade, or cannot access the desktop, see Appendix A, "Troubleshooting the Installation".

To ensure that you retain the latest device support and bug fixes, install the latest Incremental Device Update (IDU) for Resource Manager Essentials 3.5. You can download the latest IDU from http://www.cisco.com/cgi-bin/tablebuild.pl/cw2000-rme. See the Installation and Setup Guide for details.

Step 2 Follow the steps in the section "Upgrading from a Previous Version", in Chapter 1, "Installing Essentials".

As explained in this section, we recommend that you change the Resource Manager Essentials database password and back up the database before upgrading.

If you are upgrading an evaluation version of Resource Manager Essentials 3.5, follow the steps in the section "Reinstalling or Upgrading from the Evaluation Version", also in Chapter 1.

Step 3 After you complete upgrade, verify that Resource Manager Essentials was upgraded correctly as follows:

a. Access the CiscoWorks desktop.

b. Select System Configuration > About the Server > Applications and Versions. The CiscoWorks About the Server page appears.

c. Check the Applications Installed table. Resource Manager Essentials should be listed as installed and enabled on your system.

Follow the steps in Chapter 2, "Preparing to Use Essentials".

If you receive error messages during the upgrade, or cannot access the desktop, see Appendix A, "Troubleshooting the Installation".

To ensure that you retain the latest device support and bug fixes, please install the latest Incremental Device Update (IDU) for Resource Manager Essentials 3.5. You can download the latest IDU from http://www.cisco.com/cgi-bin/tablebuild.pl/cw2000-rme. See the Installation and Setup Guide for details.

9 Upgrading to Campus Manager 3.3

Upgrading Campus Manager takes approximately 11 minutes.

Upgrading to Campus Manager 3.3 on Solaris

Step 1 Locate Installation and Setup Guide for Campus Manager on Solaris. The document is available:

•On the product CD-ROM, in Adobe Acrobat PDF form.

From the CD-ROM root directory, look for CD-ROMDrive/Documentation/InstallSetupGuideForCampusSol.pdf

As explained in this section, we recommend that you change the ANI database password and back up the database before upgrading.

Step 3 After you complete the upgrade, verify that Campus Manager was upgraded correctly by accessing the CiscoWorks server, logging in as administrator, and selecting Campus Manager > Administration > System Configuration.

Follow the steps in Chapter 3, "Preparing to Use Campus Manager".

If you receive error messages during the upgrade, or cannot access the server, see Appendix A, "Troubleshooting the Installation".

To ensure that you retain the latest device support and bug fixes, install the latest Incremental Device Update (IDU) for Campus Manager 3.3.

We recommend that you change the ANI database password when prompted to do so.

Step 3 After the upgrade, verify that Campus Manager was correctly upgraded by accessing the CiscoWorks server, logging in as administrator, and selecting Campus Manager > Administration > System Configuration.

Follow the steps in Chapter 3, "Preparing to Use Campus Manager".

If you receive error messages during the upgrade, or cannot access the server, see Appendix A, "Troubleshooting the Installation".

To ensure that you retain the latest device support and bug fixes, install the latest Incremental Device Update (IDU) for Campus Manager 3.3.

10 Upgrading to Device Fault Manager 1.2 Updated for Common Services Version 2.2

Upgrading Device Fault Manager takes approximately 10 minutes.

Note To install DFM, you will require a previous licensed copy of DFM. If you do not have a DFM 1.2 (or earlier) CD-the installation cannot proceed. You may not have a previous licensed copy of DFM if you are an LMS 1.x customer. Contact your Cisco sales representative, if you wish to install DFM.

Upgrading to Device Fault Manager 1.2 Updated for Common Services Version 2.2 on Solaris

This Update is cumulative for all applications in the LAN Management Solution (LMS), Release 2.2 bundle that use the CiscoWorks Common Services 2.2 framework. It is provided as a single installable and contains updates for the following applications:

•CiscoWorks Common Services 2.2 (includes CiscoView 5.5)

•Resource Manager Essentials 3.5

•Campus Manager 3.3 Update 1

•Device Fault Manager 1.2 Updated for Common Services Version 2.2

If you are using more than one bundled product (e.g., you use LMS and RWAN), you must install the Update for each bundled product on all servers where that bundled product or any part of it is installed. This will ensure that all applications work properly. You may install the bundle Updates in any order.

Changes for NetScout nGenius Real-Time Monitor 1.4 Service Pack 8 (RTM) are part of this update. However, the RTM upgrade is located in a different directory and will not install with the Update 1 installation. To install RTM Service Pack 8, see the "Installing Real-Time Monitor SP 8" section.

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

Changes in Java Support

Since the Microsoft Virtual Machine (VM) has been removed from new Microsoft products going into distribution, CiscoWorks Common Services 2.2 SP2 provides Java Plug-in 1.4.1_02 support to users 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 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 may see special behaviors the first time you run 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.

Installing and Using Java Plug-in 1.4.1_02 on Windows

See the help pages for instructions on installing or using Java Plug-in 1.4.1_02 on Windows. 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/reinstall sequence, it may cause some co-existence issues.

•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 may not work as expected.

•Java Plug-in 1.4.1_02 has some co-existence issues with Java Plug-in 1.3.1, as given below:

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

–If you run an applet using JPI 1.3.1 first, and then try to run another applet using JPI 1.4.1_02, the server displays the error message Attachment to a running Virtual Machinefailed. Sun JPIs do 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 Noin 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 starting the applet.

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: 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 recommend 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 only the version of Netscape available from the Sun site: http://wwws.sun.com/software/solaris/netscape/get.html.

•Install all the recommended and required Solaris patches for Netscape and Java Plug-in 1.4.1_02. If you do not install the operating system patches, you may experience browser crashes, 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 to access 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 ReflectionX. You should access CiscoWorks directly from Solaris systems. Otherwise, the browser may crash 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 Java 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 Run pam.sh.

Step 2 Select Option 1.

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

To use CiscoWorks, you must configure the Java Plug-in to work with at least one of the Netscape versions mentioned in this document.

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 corresponding file (/jpi.cshrc or /jpi.profile) before restarting your browser, to get the correct environment.

To uninstall Java Plug-in 1.4.1_02 on Solaris:

Step 1 Run pam.sh.

Step 2 Select Option 2.

The Plug-in is uninstalled from your system.

Using Sun Java Plug-in 1.4.1_05

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

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 CiscoWorks LMS 2.2/LMS 1.3 Update 1. Cisco will examine additional alternatives, including Sun Java Plug-in 1.4.1_05. Information released after this print about 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/cgi-bin/tablebuild.pl/cw2000-cd-one.

Customers who want to use Sun's Java Plug-in 1.4.1_05 instead of the one provided in CiscoWorks LMS 2.2/LMS 1.3 Update 1 can apply the plug-in manually using the procedure given below.

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 LMS using clients with a mix of different Java Plug-in versions.

Also, since Cisco has not fully tested LMS with Java Plug-in 1.4.1_05, you may encounter problems.

Step 3 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 4 Save the modified javaplugin.properties file

Step 5 Restart the CiscoWorks Common Services Daemon Manager.

Step 6 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 7 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:

•If you decide not to install one or more of the LMS applications at this point, then install them later, you must remember to reapplyCiscoWorks LMS 2.2/LMS 1.3 Update 1 after you install the missing applications.

•If you have installed Resource Manager Essentials (RME), you must also install Incremental Device Update (IDU) 5.0 for Resource Manager Essentials 3.5 before you attempt to install CiscoWorks LMS 2.2/LMS 1.3 Update 1. The IDU 5.0 for RME 3.5 and the accompanying README explaining how to install it are available:

–On the IDU Prerequisite CD in your product package. For the Solaris version, see the folder /Solaris/IDU for Resource Manager Essentials. For the Windows version, see the folder \Windows\IDU for Resource Manager Essentials.

•If you have installed Campus Manager (CM), you must also install Incremental Device Update (IDU) 5.0 for Campus Manager 3.3 before you attempt to install CiscoWorks LMS 2.2/LMS 1.3 Update 1. The IDU 5.0 for CM 3.3 and the accompanying README explaining how to install it are available:

–On the IDU Prerequisite CD in your product package.

For the Solaris version, see the folder /Solaris/IDU for Campus Manager. For the Windows version, see the folder \Windows\IDU for Campus Manager.

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 fails to handle this reply properly, and signals a false positive.

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 fails to handle this reply properly, and signals a false positive.

Workaround:

You can ignore these false reports.

CSCin50359 (related bug)

You are using Internet Explorer to run CiscoWorks, do not have the Microsoft VM installed, and are prompted to install the Java Plug-in. However, you cannot download the Java Plug-in.

If you have enabled the Internet Explorer Install on demand option, you will see dialogs prompting you to download the Java Plug-in. However, you cannot download it from these links.

Workaround:

Click Cancel on these dialogs. You are redirected to a help page that instructs you to download the Java Plug-in for CiscoWorks.

If you do not have Install on demand enabled, you are redirected to the help page while starting CiscoWorks.

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.

If you use the Plug-in Control Panel to select a different JRE version, unexpected results occur.

Workaround:

Use only the default JRE for the Plug-in. Other JRE versions are not recommended.

CSCin51984

You see Java exceptions while using Resource Manager Essentials applications like Hardware Report and Device Center.

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

Workaround:

You can ignore this behavior. It does not affect functionality.

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 InternetExplorer 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.

Workaround:

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

CSCec03791

On Netscape 7.1: Closing the Help window throws Java Exceptions.

When using Netscape 7.1 on Windows clients, you see Java Exceptions when you close the Help window.

Workaround:

You can ignore this behavior. It does not affect functionality.

On Netscape 7.1: The first element in the Help Contents tree appears empty.

When using Netscape 7.1 on Windows clients, the first element appears to be blank.

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

Workaround:

Use the browser VM, if your browser has VM.

CSCsa01609

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

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

•Distribute by Devices.

•Distribute by Images.

•Remote Staging and Distribution.

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

Workaround:

Use either of these browsers:

•Internet Explorer 6.0 or 6.0 SP1.

•Netscape Navigator 4.78 or 4.79.

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.

Workaround:

This problem has no consistent workaround. However, you can close NetConfig and then restart NetConfig again.

CSCin49900

On Solaris only: Netscape 7.0 crashes randomly.

This problem occurs when you try to perform a task while another task is still processing. For example, Netscape may crash if you:

When LMS 2.2 Update 1 is installed on a DFM server, Solaris clients may experience browser problems when resizing the Monitoring Console. If the Monitoring Console is resized, columns and rows do not adjust to fit the expanded/compressed window. (Scrolling bars may disappear after compressing the window, and when the window is expanded, black patches may appear on the vertical and horizontal sides.)

This problem has only been observed on Netscape 7.0 when Java Plugin 1.4.1_02 is installed. There is currently no workaround. Contact the Technical Assistance Center for the availability of a patch.

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:

Obtaining Technical Assistance

For all customers, partners, resellers, and distributors who hold valid Cisco service contracts, the Cisco Technical Assistance Center (TAC) provides 24-hour-a-day, award-winning technical support services, online and over the phone. Cisco.com features the Cisco TAC website as an online starting point for technical assistance. If you do not hold a valid Cisco service contract, please contact your reseller.

For P1 or P2 cases (P1 and P2 cases are those in which your production network is down or severely degraded) or if you do not have Internet access, contact Cisco TAC by telephone. Cisco TAC engineers are assigned immediately to P1 and P2 cases to help keep your business operations running smoothly.

TAC Case Priority Definitions

To ensure that all cases are reported in a standard format, Cisco has established case priority definitions.

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

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

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

Priority 4 (P4)—You require information or assistance with Cisco product capabilities, installation, or configuration. There is little or no effect on your business operations.

Obtaining Additional Publications and Information

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

•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:

•Cisco Press publishes a wide range of general networking, training and certification titles. Both new and experienced user will benefit from these publications. For current Cisco Press titles and other information, go to Cisco Press online at this URL:

•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:

•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: