Guest

CiscoWorks LAN Management Solution 3.2 and earlier

Quick Start Guide for LMS 2.2 and LMS 1.3 (Maintenance Kit - Includes CiscoWorks LMS 2.2/LMS 1.3 Update 1)

  • Viewing Options

  • PDF (2.0 MB)
  • Feedback
Quick Start Guide

Table Of Contents

LAN Management Solution, Release 2.2 (Maintenance Kit)

SUPPLEMENTAL LICENSE AGREEMENT

LAN Management Solution 2.2 Overview

Prerequisite for Installing DFM for LMS 1.x Users

On Solaris

On Windows

LMS Contents

Additional Information Online

What's New?

Server and Client System Requirements

Solaris Patches for LAN Management Solution

LAN Management Solution Port Usage

Upgrade Paths

Upgrade Options

Upgrading to LAN Management Solution 2.2

Prerequisites

Important Upgrade Notes

Order of Upgrade

Upgrading to CiscoWorks Common Services 2.2

Upgrading to CiscoWorks Common Services 2.2 on Solaris

Upgrading to CiscoWorks Common Services 2.2 on Windows

Upgrading to Resource Manager Essentials 3.5

Upgrading to Resource Manager Essentials 3.5 on Solaris

Upgrading to Resource Manager Essentials 3.5 on Windows

Upgrading to Campus Manager 3.3

Upgrading to Campus Manager 3.3 on Solaris

Upgrading to Campus Manager 3.3 on Windows

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

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

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

Upgrading to nGenius Real-Time Monitor

Upgrading to nGenius Real-Time Monitor 1.4

Upgrading to nGenius Real-Time Monitor 1.4 Service Pack 6

Post-Upgrade Tasks

Adding or Updating Devices in Inventory

Upgrading to CiscoWorks LMS 2.2/LMS 1.3 Update 1

Description

Hardware and Software Requirements

General Recommendations on Java Plug-in 1.4.1_02

Prerequisites for CiscoWorks LMS 2.2/LMS 1.3 Update 1

Downloading CiscoWorks LMS 2.2/LMS 1.3 Update 1

Installing CiscoWorks LMS 2.2/LMS 1.3 Update 1

Installing CiscoWorks LMS 2.2/LMS 1.3 Update 1 on Solaris

Installing CiscoWorks LMS 2.2/LMS 1.3 Update 1 on Windows

Installing Real-Time Monitor SP 8

Installing Real-Time Monitor SP 8 on Windows

Known Problems

Device Fault Manager 1.2: Known Problems

Resolved Problems

Where to Go Next

Related Documentation

Obtaining Documentation

Cisco.com

Documentation CD-ROM

Ordering Documentation

Documentation Feedback

Obtaining Technical Assistance

Cisco TAC Website

Opening a TAC Case

TAC Case Priority Definitions

Obtaining Additional Publications and Information


Quick Start Guide

LAN Management Solution, Release 2.2 (Maintenance Kit)


1 SUPPLEMENTAL LICENSE AGREEMENT

SUPPLEMENTAL LICENSE AGREEMENT FOR CISCO SYSTEMS NETWORK MANAGEMENT SOFTWARE: CISCOWORKS LAN MANAGEMENT SOLUTION

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.

Reproduction and Distribution

Customer may not reproduce nor distribute software.

DESCRIPTION OF OTHER RIGHTS AND LIMITATIONS

Please refer to the Cisco Systems, Inc. Software License Agreement.

2 LAN Management Solution 2.2 Overview

The LAN Management Solution (LMS) software provides applications for configuring, administering, monitoring, and troubleshooting a campus network. It enables network administrators to effectively manage their LAN and campus networks.

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.

Information about ordering documentation and contacting Cisco Systems for additional assistance.


Note This document contains information for CiscoWorks LMS 2.x and CiscoWorks LMS 1.x Maintenance customers. It also includes the CiscoWorks LMS 2.2/LMS 1.3 Update 1 details.


Prerequisite for Installing DFM for LMS 1.x Users

You may be asked to validate your Device Fault Manager (DFM) image if you are installing DFM using this Maintenance Kit CD (for CiscoWorks LAN Management Solution 2.2). The maintenance kit allows all other previous licensed LMS 1.x components to upgrade (such as CD One, Resource Manager Essentials, Campus Manager and nGenius Real-Time Monitor).

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:

To validate the upgrade image, insert a Device Fault Manager (DFM) 1.2 or earlier 
CD.
Please ensure that the CD is mounted on /cdrom/cdrom0.

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.

CiscoWorks Common Services 2.2 includes:

Common Services 2.2-A set of shared application services

CiscoView 5.5-A graphical device management tool

Integration Utility 1.5-An integration module that supports third-party Network Management Systems (NMS)

CiscoWorks Common
Services 2.2 with CiscoView 5.5 product CD-ROM

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

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

Resource Manager Essentials 3.5 (Essentials)

Manage network inventory and device changes, network configuration, and software images. Also allows you to monitor network availability and perform syslog analysis.

Resource Manager
Essentials 3.5 product CD-ROM

Release Notes for Resource Manager Essentials 3.5 on Solaris

Release Notes for Resource Manager Essentials 3.5 on Windows

Campus Manager 3.3 (Campus)

Obtain graphical views of network topology, and end-user information.

Campus Manager 3.3 product CD-ROM

Release Notes for Campus Manager 3.3 on Solaris

Release Notes for Campus Manager 3.3 on Windows

Device Fault Manager 1.2 Updated for Common Services Version 2.2 (DFM)

Monitor faults real-time and determines the cause of Cisco device faults. Provides Cisco device-level fault correlation, and notifies you of critical network conditions by email or pager.

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.

Device Fault Manager 1.2 Updated for Common Services Version 2.2 product CD-ROM

Release Notes for Device Fault Manager 1.2 Updated for Common Services Version 2.2 on Solaris

Release Notes for Device Fault Manager 1.2 Updated for Common Services Version 2.2 on Windows

NetScout nGenius Real-Time Monitor 1.4 (RTM)

Manage and monitor packets, and application and protocol traffic on the network. nGenius Real-Time Monitor also provides tools for troubleshooting and monitoring traffic thresholds.

This client-server network management solution is offered to Cisco Systems customers in cooperation with NetScout Systems, Inc.

NetScout nGenius Real-Time Monitor 1.4 product CD-ROM

NetScout nGenius Real-Time Monitor 1.4 Service Pack 6 CD-ROM

NetScout nGenius Real-Time Monitor 1.4 Installation Guide

Supplement and Release Notes for NetScout nGenius Real-Time Monitor Release 1.4 Service Pack 6

NetScout nGenius Real-Time Monitor 1.4 Release Notes


Additional Information Online

Registered Cisco.com users can access the most current Incremental Device Updates, CiscoView Device Package Updates, Fault History, and Latest Adapters at the following locations:

Incremental Device Updates

For Resource Manager Essentials at

http://www.cisco.com/cgi-bin/tablebuild.pl/cw2000-rme

For Campus Manager at

http://www.cisco.com/cgi-bin/tablebuild.pl/cw2000-campus

For Device Fault Manager at

http://www.cisco.com/cgi-bin/tablebuild.pl/cw2000-dfm

CiscoView Device Package Updates at

http://www.cisco.com/cgi-bin/Software/CiscoView/cvplanner.cgi

Fault History at

http://www.cisco.com/cgi-bin/tablebuild.pl/cw-fault-history

Latest Adapters at

http://www.cisco.com/cgi-bin/tablebuild.pl/cw2000-nnm

What's New?

This section lists the new features added in the LAN Management Solution, Release 2.2:

1. CiscoWorks Common Services 2.2 replaces CD One. It contains the following new features:

Security/AAA-ACS mode: Used for user authentication and authorization, it meets the secured device view requirements.

Security/User Session Management: Passes session data back and forth between two different servlet engines, Tomcat and JRunProxyServer.

Database Password Encryption: Provides confidentiality for database passwords.

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.

A new command to extract Detailed Device Inventory information in XML format.

User-defined fields that are customizable and can hold alphanumeric strings up to 128 characters long.

Quick config downloads in Configuration Management.

Archiving of the vlan.dat file for Cat IOS switches.

Full support for interactive and multiline commands.

User-specifiable protocol for config fetch and download.

Multiple job deletion and retry of failed jobs.

Templates for IPSec and SSH.

Saving of Syslog messages for 14 days.

4. Campus Manager 3.3 contains the following new features:

Improved workflow, ease-of-use and intuitiveness in launching tasks from Campus applications.

Support for administrative view discovery and display, and creating Campus Views per user.

Support for secure communication between the client browser and Campus applications using Secure Socket Layer (SSL) protocol.

Support for new devices.

Fixes to problems that existed in previous releases.

The following enhancements have been made to individual Campus applications:

Topology Services

a. Ability to create Topology Groups

b. Options to display device labels

c. Options to prioritize label preference

d. Ability to find in LAN edge view for locating devices in switch-clouds and fabrics

e. Improved device status filter

f. Support for enabling sub filters of LANE components even after a refresh

g. Ability to generate a report to list all unused ports, and an option to print and save

h. Ability to provide uplink information when router boundary map switch clouds are selected to display context between switch cloud (subnet) and joining router

i. Ability to create SPVC (Soft Permanent Virtual Connection) when both ATM end ports are down

Path Analysis

a. Support for batch job processing and archiving in Path analysis

b. Support for displaying error messages on unsuccessful path analysis for L3 and L2

c. Support for sorting subnet-to-VLAN Mapping table

d. Improved Path Analysis tracing capabilities

e. Support for CCM login

f. Improved GUI: Pull down menu in Path Analysis connected to the source and destination field

User Tracking

a. Ability to define acquisition based on a subnet range

b. Support for scheduled archive and export feature in User Tracking

c. Support for enhanced troubleshooting support using a new debugger utility

d. Improved GUI: Addition of two new columns to the User Tracking tables (Duplex type and port speed)

Discrepancy Reports

a. Support for enhanced discrepancy reporting

Administration

a. Support for administering Topology Groups

b. Ability to configure scheduling of Path Analysis traces, and archiving of User Tracking data

5. Device Fault Manager 1.2 Updated for Common Services Version 2.2 includes:

Bug fixes listed in the Release Notes for DFM 1.2 Updated for Common Services Version 2.2

Device Support:

Cisco Interfaces and Modules: IGX-URM-2FE, IGX-URM-2FE-2V Network Modules

Cisco Routers:

a. Cisco 1700 Series Access Routers: 1760(V)

b. Cisco 2600 Series: 2610XM, 2610XM-DC, 2610XM-RP5, 2620XM, 2620XM-DC, 2620XM-RP5, 2621XM, 2621XM-DC, 2621XM-RP5, 2650, 2650XM, 2650XM-DC, 2650XM-RP5, 2651, 2651XM, 2651XM-DC, 2651XM-RP5

c. Cisco 3600: 3662Ac, 3662Dc, 3662AcCo, 3662DcCo

d. Cisco 3700: 3725, 3745

e. Cisco 10000 Series Internet Router: 10005 ESR, 10008 ESR

f. Cisco 12000 Series (Gigabit Switch Routers): 12404 GSR, 12406 GSR, 12410 GSR, 12416 GSR

Cisco Switches:

a. Cisco Catalyst: 2950-12, 2950-24, 2950C-24, 2950G-12, 2950G-24, 2950G-48, 2950G-24-DC, 2950T-24 (running IOS)

b. Cisco Catalyst: 3548XL (running IOS)

c. Cisco Catalyst: 3550-12T, 3550-12G, 3550-24, 3550-24Dc, 3550-24Mmf, 3550-48 (running IOS)

d. Cisco Catalyst 6009 (running IOS)

e. Cisco Catalyst 6509, 6513 (running IOS)

f. Cisco 7600 Series Internet Router 7600 OSR

g. Cisco CSS 11000 Content Services Switches 11050, 11503, 11506, 11150

Cisco Wireless LAN devices: Cisco Aironet 1200 Series Access Point AP1200

Cisco Firewalls: Cisco PIX Firewall Series 501, 506, 506E, 515, 515E, 520, 525

Cisco IP Telephony Devices: Cisco VG248 FXS Port Voice Gateway

6. nGenius Real-Time Monitor includes:

Bug fixes listed in the Supplement and Release Notes for NetScout nGenius Real-Time Monitor Release 1.4 Service Pack 6

Support for Service Pack 6.

3 Server and Client System Requirements

This section provides LAN Management Solution 2.2 server and client requirements.

Table 2 lists the server requirements for upgrading the LAN Management Solution 2.2 components on Solaris systems.

Table 3 lists the server requirements for upgrading the LAN Management Solution 2.2 components on Windows systems.

Table 4 lists the client system requirements for all platforms.

Table 5 lists the browser requirements for all platforms.

Table 6 lists the Solaris patches required and recommended for LAN Management Solution 2.2.

Table 7 lists the ports LAN Management Solution 2.2 uses.

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.

Table 2 Minimum Server Requirements for Solaris Systems 

Component
Minimum Requirement

Hardware

One of the following1 :

Sun UltraSPARC II

Sun UltraSPARC III (Sun Blade 1000 Workstation or Sun Fire 280R Workgroup Server)

Dual processor required for hosting multiple management solutions

CD-ROM drive

Color monitor with video card capable of 256 colors or more

10BaseT or faster (10 Mbps or faster network connection)

Software2

One of the following3 :

For UltraSPARC II: Solaris 2.7 or 2.8

For UltraSPARC III: Solaris 2.8

Available memory (RAM)

One of the following:

For UltraSPARC II: 1 GB RAM minimum

For UltraSPARC III Workstation: 1 GB RAM minimum

For UltraSPARC III Server: 2 GB RAM minimum

8 MB E-cache

Available disk space

One of the following:

For UltraSPARC II: 9 GB, with 2 GB swap space

For UltraSPARC III Workstation: 40 GB internal FC-AL disk drive

For UltraSPARC III Server: Dual 40 GB internal FC-AL disk drives

UNIX file system recommended 4

1 A 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.

2 LAN 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.

3 Upgrade Solaris patches, as required, for the Solaris version you are using. See the "Solaris Patches for LAN Management Solution" section.

4 To verify the file system: Enter df -k at the command prompt.


Table 3 Minimum Server Requirements for Windows Systems 

Component
Minimum Requirement

Hardware

IBM PC-compatible computer with 550 MHz or Pentium III processor (dual processor required for hosting multiple management solutions)

Color monitor with video card capable of 256 colors or more

CD-ROM drive

10BaseT or faster (10 Mbps or faster network connection)

Software1

One of the following:

Windows 2000 Professional with Service Pack 32

Windows 2000 Server with Service Pack 3

Windows 2000 Advanced Server3 with Service Pack 3

Available memory (RAM)

1 GB

Available disk space4

40 GB

2 GB virtual memory

NTFS file system required

1 LAN 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.

2 To verify the Service Pack version, select Start > Run, then enter winver.

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

4 Upgrade 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.


Table 4 Minimum Client Hardware and Software Requirements 

Component
Minimum Requirement

Hardware/Software

Any one of these systems:

IBM PC-compatible computer with 300 MHz Pentium processor, running Windows XP Professional or Windows 2000 (Advanced Server, Server, or Professional) with Service Pack 3

Sun UltraSPARC 10 with 333 MHz processor, running Solaris 2.7 or 2.8

Color monitor with video card set to 256 colors

Available disk space

One of the following:

For Solaris: 512 MB swap space

For Windows: 512 MB virtual memory

Available memory (RAM)

256 MB RAM


Table 5 Browser Requirements 

Browser
Java Virtual Machine (JVM 1 )
Version
Platform

Internet Explorer (IE)
(recommended)

5.0.0.3802 or later

IE 6.0 (6.0.26),
IE 6.0 SP1 (6.0.28) with patch Q810847

Windows XP Professional2 or Windows 2000

Netscape Navigator

-

4.78 or 4.79

Windows XP Professional or Windows 2000

Netscape Navigator (Downloaded from Sun site only)

-

4.76

Solaris 2.7 or 2.8

1 To verify JVM, select View > Java Console in Internet Explorer and Communicator > Tools > Server > Java Console in Netscape Navigator. If Java Console is not listed in View, you must enable it. To enable Java Console, in Internet Explorer, select Tools > Internet Options > Advanced. In the JVM section, select the Java Console option. Restart Internet Explorer.

2 For Windows XP Professional, SP1 must be installed. Windows XP professional is not packaged with JVM. JVM is installed after you install Windows XP SP1. Windows XP SP1a should not be installed.


Solaris Patches for LAN Management Solution

Table 6 lists the Solaris patches for the LAN Management Solution 2.2.


Note A warning message is displayed if obsolete Solaris patches are present on your system. Before running CiscoWorks Common Services 2.2, download and install the latest recommended patches from http://www.sunsolve.sun.com.


Table 6 Solaris Patches for LAN Management Solution 2.21

Operating System
Required
Recommended

Solaris 2.7

106980-10

106327-05

107081-11

107636-03

108376-03

112300-01

108301-02

108482-02

Solaris 2.8

111626-01

111327-02

110945-02

110934-01

110898-02

110700-01

109326-05

108827-30

108652-51

108528-18

108921-14

108940-24

110951-01

110662-02

110615-01

110286-02

109324-02

111085-02

108964-06

1 Use the showrev -p command to verify that these patches have been applied.


LAN Management Solution Port Usage

This section provides a list of ports used by the various CiscoWorks components.

Table 7 LAN Management Solution Port Usage 

Protocol
Port Number
Service Name
Application(s)
Direction (of establishment) of connection

ICMP

-

Ping

Resource Manager Essentials, Campus Manager, and Device Fault Manager

Server to Device

TCP

22

Secure Shell (SSH)

CiscoWorks Common Services and Resource Manager Essentials

Server to Device

TCP

23

Telnet

CiscoWorks Common Services, and Resource Manager Essentials

Server to Device

TCP

25

Simple Mail Transfer Protocol (SMTP)

Resource Manager Essentials

Server Internal

TCP

80

HyperText Transfer Protocol (HTTP)

CiscoWorks Common Services, CiscoView, and nGenius Real-Time Monitor

Client to Server

TCP

514

Remote Copy Protocol

CiscoWorks Common Services

Server to Device

TCP

514

rsh Daemon

Resource Manager Essentials

Server to Device

TCP

1099

Remote Method Invocation (RMI) Registry

nGenius Real-Time Monitor

Client to Server

TCP

1683

Internet Inter-ORB Protocol (IIOP)

CiscoWorks Common Services, and Campus Manager

Client to Server

TCP

1684

Internet Inter-ORB Protocol (IIOP)

CiscoWorks Common Services, and Campus Manager

Server to Client

TCP

1741

CiscoWorks HTTP Protocol

CiscoWorks Common Services, CiscoView, and Resource Manager Essentials

Client to Server

TCP

1742

SSL (HTTPS)

CiscoWorks Common Services, and Resource Manager Essentials

Client to Server

TCP

1961

Service Manager for Server

nGenius Real-Time Monitor

Client to Server

TCP

1962

Service for Server

nGenius Real-Time Monitor

Client to Server

TCP

1963

Application for Client

nGenius Real-Time Monitor

Server to Client

TCP

1964

Application Manager for Client

nGenius Real-Time Monitor

Server to Client

TCP

1965

Monitor

nGenius Real-Time Monitor

Client to Server

TCP

2639

Sybase database connection

nGenius Real-Time Monitor

Server Internal

TCP

8007

Ajp12Connector port for Tomcat

nGenius Real-Time Monitor

Server Internal

TCP

8009

Ajp12Connector port for Tomcat

nGenius Real-Time Monitor

Server Internal

TCP

8080

Web Server

nGenius Real-Time Monitor

Client to Server

TCP

8081

HttpConnect port for Tomcat

nGenius Real-Time Monitor

Client to Server

TCP

8088

HIOP

CiscoWorks Common Services

Server to Client

Client to Server

TCP

9002

DynamID authentication (DFM Broker)

Device Fault Manager

Client to Server

TCP

10033

CMF Licensing

CiscoWorks Common Services

Server Internal

TCP

42340

CiscoWorks Daemon Manager - Tool for Server Processes

CiscoWorks Common Services

Server Internal

TCP

42343

JRun

CiscoWorks Common Services

Server Internal

TCP

42344

ANI HTTP Server

CiscoWorks Common Services

Server Internal

TCP

42351

Event Services Software (ESS) Listening (Alternate port is 44351/tcp)

CiscoWorks Common Services

Server Internal

TCP

42352

ESS HTTP (Alternate port is 44352/tcp)

CiscoWorks Common Services

Client to Server

TCP

42353

ESS Routing (Alternate port is 44352/tcp)

CiscoWorks Common Services

Server Internal

TCP

43441

CMF Database

CiscoWorks Common Services

Server Internal

TCP

43442

RME Database

Resource Manager Essentials

Server Internal

TCP

43443

ANIDbEngine

Campus Manager

Server Internal

TCP

57860

JRun - JRun Server Manager Control Server

CiscoWorks Common Services

Server Internal

UDP

69

Trivial File Transfer Protocol (TFTP)

CiscoWorks Common Services and Resource Manager Essentials

Server to Device

Device to Server

UDP

161

Simple Network Management Protocol (SNMP)

CiscoWorks Common Services, CiscoView, Resource Manager Essentials, Campus Manager, Device Fault Manager, and nGenius Real-Time Monitor

Server to Device

Device to Server

UDP

162

SNMP Traps (Standard Port)

CiscoWorks Common Services, Resource Manager Essentials, Device Fault Manager and nGenius Real-Time Monitor

Device to Server only (RTM);

Server to Device Device to Server (all others)

UDP

395

NetScout Proprietary Port, Server Monitor

nGenius Real-Time Monitor

Device to Server

UDP

514

Syslog

CiscoWorks Common Services and Resource Manager Essentials

Device to Server

UDP

1971

Trap and Alarms Listener

nGenius Real-Time Monitor

Server Internal

UDP

1972

Trap and Alarms Listener

nGenius Real-Time Monitor

Server Internal

UDP

1974

Shutdown Listener for RMI Registry

nGenius Real-Time Monitor

Server Internal

UDP

1975

Shutdown Listener for PM Server

nGenius Real-Time Monitor

Server Internal

UDP

1976

Shutdown Listener for Watchdog

nGenius Real-Time Monitor

Server Internal

UDP

1977

Shutdown Listener for nGenius Native

nGenius Real-Time Monitor

Server Internal

UDP

9000

CSlistener (DFM server if port 162 is occupied)

Device Fault Manager

Device to Server

UDP

14004

Lock port for ANI Server singlet on check

Campus Manager

Server Internal

UDP

16236

UT Host acquisition

Campus Manager

Device to Server

UDP

42342

OSAGENT

CiscoWorks Common Services and Resource Manager Essentials

Server Internal (Commom Services); RSAC to Server via OSAGENT (RME)

UDP

42350

Event Services Software (ESS) (Alternate port is 44350/udp)

CiscoWorks Common Services

Server Internal


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


Note 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. See "Prerequisite for Installing DFM for LMS 1.x Users" section for details.


CiscoWorks Routed WAN Management Solution (RWAN) Release 1.2 or 1.1 installed

First upgrade to RWAN 1.3. Then install Campus Manager 3.3,
Device Fault Manager 1.2 Updated for Common Services 2.2, nGenius Real-Time Monitor 1.4 and nGenius Real-Time Monitor 1.4 SP6 using the instructions in this Quick Start Guide. See "Upgrade Options" section.


5 Upgrade Options

Table 9 describes the recommended sequence for upgrading individual LAN Management Solution 2.2 (LMS) component applications when prior versions of these components are already installed on your system.


Note For specific upgrading and installation instructions, see the installation documentation provided with each of the LMS components (See the "Related Documentation" section for details).


Table 9 Recommended Upgrade Sequence 

If the following product is already installed...
And one or more of the following products are also already installed...
You should upgrade in the following order...

CD One, 5th Edition or CD One, 4th Edition

-

CiscoWorks Common Services 2.2
(Includes CiscoView 5.5)

Resource Manager Essentials 3.3

CD One, 4th Edition

1. CiscoWorks Common Services 2.2 (Includes CiscoView 5.5)

2. Resource Manager Essentials 3.5

Resource Manager Essentials 3.4

CD One, 5th Edition

1. CiscoWorks Common Services 2.2 (Includes CiscoView 5.5)

2. Resource Manager Essentials 3.5

Campus Manager 3.1

CD One, 4th Edition

Resource Manager Essentials 3.3

1. CiscoWorks Common Services 2.2 (Includes CiscoView 5.5)

2. Resource Manager Essentials 3.5

3. Campus Manager 3.3

Campus Manager 3.2

CD One, 5th Edition

Resource Manager Essentials 3.4

1. CiscoWorks Common Services 2.2 (Includes CiscoView 5.5)

2. Resource Manager Essentials 3.5

3. Campus Manager 3.3

Device Fault Manager 1.1

CD One, 4th Edition

Resource Manager Essentials 3.3

1. CiscoWorks Common Services 2.2 (Includes CiscoView 5.5)

2. Resource Manager Essentials 3.5

3. Device Fault Manager 1.2 Updated for Common Services 2.2

Device Fault Manager 1.2

CD One, 5th Edition

Resource Manager Essentials 3.4

1. CiscoWorks Common Services 2.2 (Includes CiscoView 5.5)

2. Resource Manager Essentials 3.5

3. Device Fault Manager 1.2 Updated for Common Services 2.2

nGenius Real-Time Monitor 1.3

-

1. nGenius Real-Time Monitor 1.4

2. nGenius Real-Time Monitor 1.4 SP6

nGenius Real-Time Monitor 1.4

-

nGenius Real-Time Monitor 1.4 SP6


6 Upgrading to LAN Management Solution 2.2

To upgrade an application, log in as root (on Solaris) or local administrator (on Windows) on the system on which you want to upgrade the application.

Before you begin:

Check the factors to be considered before upgrading LMS 2.2. See "Prerequisites" section.

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.

Ensure you complete the following tasks before upgrade:


Step 1 Install required operating system upgrades. See "Server and Client System Requirements" section.

Step 2 Install required service packs. See "Server and Client System Requirements" section.

Step 3 Read "Important Upgrade Notes" section.


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 Solaris, if errors occur during upgrade, check the upgrade log file /var/tmp/ciscoinstall.log.

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.

You can find the User Guide for CiscoWorks Common Services 2.2:

On Cisco.com, in both HTML and PDF form.

Log into Cisco.com. Select Products and Services > Network Management CiscoWorks > CiscoWorks CiscoView > Instructions and Guides > User Guide Books > User Guide for CiscoWorks Common Services 2.2

On the CiscoWorks Common Services 2.2 (includes CiscoView) CD-ROM, in Adobe Acrobat PDF format.

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.

On Cisco.com, in both HTML and PDF form.

Log into Cisco.com. Select Products and Services > Network Management CiscoWorks > CiscoWorks CiscoView > Versions and Options > CiscoWorks CiscoView 5.5, then select Using CiscoView 5.5.

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.

Order of Upgrade

Upgrade each application of LMS 2.2 in the following order:


Step 1 Upgrade CiscoWorks Common Services 2.2. See "Upgrading to CiscoWorks Common Services 2.2" section.

Step 2 Upgrade Resource Manager Essentials 3.5. See "Upgrading to Resource Manager Essentials 3.5" section.

Step 3 Upgrade Campus Manager 3.3. See "Upgrading to Campus Manager 3.3" section.

Step 4 Upgrade Device Fault Manager 1.2 Updated for Common Services Version 2.2. See "Upgrading to Device Fault Manager 1.2 Updated for Common Services Version 2.2" section.

Step 5 Upgrade nGenius Real-Time Monitor 1.4. See "Upgrading to nGenius Real-Time Monitor" section.


7 Upgrading to CiscoWorks Common Services 2.2

Upgrading CiscoWorks Common Services takes approximately 40 minutes.

Before you begin:

Verify that the server on which you intend to upgrade CiscoWorks Common Services 2.2 with CiscoView 5.5, meets the requirements listed in the tables in the"Server and Client System Requirements" section.

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

On Cisco.com, in both HTML and PDF form.

Log into Cisco.com. Select Products and Services  >  Network Management CiscoWorks. Navigate to  CiscoWorks Common Services  2.2, then select  Installation and Setup Guide for CiscoWorks Common Services (Includes CiscoView 5.5) on Solaris.

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

On Cisco.com, in both HTML and PDF form.

Log into Cisco.com. Select Products and Services  >  Network Management CiscoWorks. Navigate to  CiscoWorks Common Services  2.2, then select  Installation and Setup Guide for CiscoWorks Common Services (Includes CiscoView 5.5) on Windows.

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

8 Upgrading to Resource Manager Essentials 3.5

Upgrading Resource Manager Essentials takes approximately 30 minutes.

Upgrading to Resource Manager Essentials 3.5 on Solaris


Step 1 Locate Installation and Setup Guide for Resource Manager Essentials 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/InstallSetupGuideForEssentialsSol.pdf

On Cisco.com, in both HTML and PDF form.

Log into Cisco.com. Select Products and Services  >  Network Management CiscoWorks  > CiscoWorks Resource Manager Essentials  > Versions and Options > CiscoWorks Resource Manager Essentials 3.5, then select  Installation and Setup Guide for Resource Manager Essentials on Solaris.

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.

Upgrading to Resource Manager Essentials 3.5 on Windows


Step 1 Locate Installation and Setup Guide for Resource Manager Essentials on Windows. 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\InstallSetupGuideForEssentialsWin.pdf

On Cisco.com, in both HTML and PDF form.

Log into Cisco.com. Select Products and Services  >  Network Management CiscoWorks  > CiscoWorks Resource Manager Essentials  > Versions and Options > CiscoWorks Resource Manager Essentials 3.5, then select  Installation and Setup Guide for Resource Manager Essentials on Windows.

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

On Cisco.com, in both HTML and PDF form.

Log into Cisco.com. Select Products and Services  >  Network Management CiscoWorks  > CiscoWorks Campus Manager  > Versions and Options > CiscoWorks Campus Manager 3.3, then select  Installation and Setup Guide for Campus Manager on Solaris.

Step 2 Follow the steps in the section "Performing an Upgrade Installation", in Chapter 1, "Installing Essentials".

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.

You can download the latest IDU from http://www.cisco.com/cgi-bin/tablebuild.pl/cw2000-campus. See Installation and Setup Guide for details.

Upgrading to Campus Manager 3.3 on Windows


Step 1 Locate Installation and Setup Guide for Campus Manager on Windows. 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\InstallSetupGuideForCampusWin.pdf

On Cisco.com, in both HTML and PDF form.

Log into Cisco.com. Select Products and Services  >  Network Management CiscoWorks  > CiscoWorks Campus Manager  > Versions and Options > CiscoWorks Campus Manager 3.3, then select  Installation and Setup Guide for Campus Manager on Windows.

Step 2 Follow the steps in the section "Performing an Upgrade Installation", in Chapter 2, "Installing Campus Manager".

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.

You can download the latest IDU from http://www.cisco.com/cgi-bin/tablebuild.pl/cw2000-campus. See the Installation and Setup Guide for details.

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


Step 1 Locate Installation and Setup Guide For Device Fault 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/dfm12_solaris_install_and_setup.pdf

On Cisco.com, in both HTML and PDF form.

Log into Cisco.com. Select Products and Services > Network Management CiscoWorks > CiscoWorks Device Fault Manager > Versions and Options > CiscoWorks Device Fault Manager 1.2 Updated for Common Services Version 2.2, then select Installation and Setup Guide For Device Fault Manager on Solaris.

Step 2 Follow the steps in the section "Upgrading DFM 1.2 to DFM 1.2 Updated for Common Services Version 2.2", in Chapter 2, "Upgrading Device Fault Manager".

We recommend that you change the Device Fault Manager database password when prompted to do so.

Step 3 Reconfigure DFM to forward traps to port 395 when you upgrade DFM and nGenius Real-Time Monitor on the same server. For details, see the Installation and Setup Guide for Device Fault Manager.


Note You must reconfigure nGenius Real-Time Monitor to listen for traps on the correct port. For details, see the NetScout nGenius Real-Time Monitor 1.4 Installation Guide.


Step 4 After you complete the upgrade, verify that Device Fault Manager was upgraded correctly by accessing the CiscoWorks server, logging in as administrator, and selecting Server Configuration > Administration > Process Management > Process Status.

Step 5 If desired, download and install Fault History from:

http://www.cisco.com/cgi-bin/tablebuild.pl/cw-fault-history


If you receive error messages during the upgrade, or cannot access the server, see the User Guide for Device Fault Manager for "Device Fault Manager Frequently Asked Questions".

To ensure that you retain the latest device support and bug fixes, install the latest Incremental Device Update (IDU) for Device Fault Manager 1.2 Updated for Common Services Version 2.2.

You can download the latest IDU from http://www.cisco.com/cgi-bin/tablebuild.pl/cw2000-dfm. For details, see Installation and Setup Guide.

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


Step 1 Locate Installation and Setup Guide For Device Fault Manager on Windows. 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\dfm12_windows_install_and_setup.pdf

On Cisco.com, in both HTML and PDF form.

Log into Cisco.com. Select Products and Services > Network Management CiscoWorks > CiscoWorks Device Fault Manager > Versions and Options > CiscoWorks Device Fault Manager 1.2 Updated for Common Services Version 2.2, then select Installation and Setup Guide For Device Fault Manager on Windows.

Step 2 Follow the steps in the section "Upgrading DFM 1.2 to DFM 1.2 Updated for Common Services Version 2.2", in Chapter 2, "Upgrading Device Fault Manager".

We recommend that you change the Device Fault Manager database password when prompted to do so.

Step 3 Reconfigure DFM to forward traps to port 395 when you upgrade DFM and nGenius Real-Time Monitor on the same server. For details, see the Installation and Setup Guide for Device Fault Manager


Note You must reconfigure nGenius Real-Time Monitor to listen for traps on the correct port. For details, see the NetScout nGenius Real-Time Monitor 1.4 Installation Guide.


Step 4 After you finish the upgrade, verify that Device Fault Manager was upgraded properly by accessing the CiscoWorks server, logging in as administrator, and selecting Server Configuration > Administration > Process Management > Process Status.

Step 5 If desired, download and install Fault History from:

http://www.cisco.com/cgi-bin/tablebuild.pl/cw-fault-history


If you receive error messages during the upgrade, or cannot access the server, see the User Guide for Device Fault Manager for "Device Fault Manager Frequently Asked Questions".

To ensure that you retain the latest device support and bug fixes, install the latest Incremental Device Update (IDU) for Device Fault Manager 1.2 Updated for Common Services Version 2.2.

You can download the latest IDU from http://www.cisco.com/cgi-bin/tablebuild.pl/cw2000-dfm. For details, see Installation and Setup Guide.

11 Upgrading to nGenius Real-Time Monitor

Upgrading nGenius Real-Time Monitor takes approximately 10 minutes.

Before you begin:

Verify that you are not upgrading nGenius Real-Time Monitor on a Windows system that has the server name nGenius.

Check if you have 300 MB of space available in the /tmp or Temp directory.

Upgrading nGenius Real-Time Monitor includes the following steps:


Step 1 Upgrading to nGenius Real-Time Monitor 1.4. See Upgrading to nGenius Real-Time Monitor 1.4

Step 2 Install nGenius Real-Time Monitor 1.4 Service Pack 6. See Upgrading to nGenius Real-Time Monitor 1.4 Service Pack 6


Upgrading to nGenius Real-Time Monitor 1.4

Perform the following steps to upgrade nGenius Real-Time Monitor 1.4:


Step 1 Locate NetScout nGenius Real-Time Monitor 1.4 Installation Guide. The document is available. This document comes in your product package.

Step 2 Follow the steps in the section "Upgrading nGenius Real-Time Monitor", in Chapter 1, "Installing nGenius Real-Time Monitor".

We recommend that you change the nGenius Real-Time Monitor database password when prompted to do so.

Step 3 If you are upgrading nGenius Real-Time Monitor and DFM on the same server, change the default configuration of nGenius Real-Time Monitor to receive traps properly:

Stop the nGenius Server process.

Open the file //<nGenius_directory > /bin/serverprivate.properties (where //<nGenius_directory > is the path to the installed nGenius server files).

Change devicelistener.portlist=162,395 to devicelistener.portlist=395.

If you have not already done so, reconfigure DFM to forward traps to port 395 (for more information, see the Installation and Setup Guide for Device Fault Manager.

Step 4 After you complete the upgrade, verify that nGenius Real-Time Monitor was upgraded properly by accessing nGenius Real-Time Monitor launch page, logging in as administrator, and selecting Administration > nGenius Server.


If you receive error messages during the upgrade, or cannot access the server, see User Guide for nGenius Real-Time Monitor for "Troubleshooting the Installation".

Upgrading to nGenius Real-Time Monitor 1.4 Service Pack 6

Perform the following steps to upgrade nGenius Real-Time Monitor 1.4 Service Pack 6:


Step 1 Locate Supplement and Release Notes for NetScout nGenius Real-Time Monitor Release 1.4 Service Pack 6. This document comes in your product package.

Step 2 Read the "Important Installation Notes" section.

Step 3 Follow the steps in the section "Installing Service Pack 6".

Step 4 If you are upgrading nGenius Real-Time Monitor and DFM on the same server, change the default configuration of nGenius Real-Time Monitor to receive traps properly:

Stop the nGenius Server process.

Open the file //<nGenius_directory > /bin/serverprivate.properties (where //<nGenius_directory > is the path to the installed nGenius server files).

Change devicelistener.portlist=162,395 to devicelistener.portlist=395.

If you have not already done so, reconfigure DFM to forward traps to port 395 (for more information, see the Installation and Setup Guide for Device Fault Manager.

Step 5 After you complete the upgrade, verify that nGenius Real-Time Monitor was upgraded properly by accessing nGenius Real-Time Monitor launch page, logging in as administrator, and selecting Administration > nGenius Server.


If you receive error messages during the upgrade, or cannot access the server, see User Guide for nGenius Real-Time Monitor for "Troubleshooting the Installation".

12 Post-Upgrade Tasks

After you have upgraded the required products and verified the upgrades, you must:


Step 1 Get updated device support and defect fixes by installing the latest version of Incremental Device Update (IDU) for Resource Manager Essentials. You can download this IDU from http://www.cisco.com/cgi-bin/tablebuild.pl/cw2000-rme.

Step 2 Add or update the devices in the inventory (see "Adding or Updating Devices in Inventory", below).

Step 3 Upgrade to CiscoWorks LMS 2.2/LMS 1.3 Update 1. For details, see "Upgrading to CiscoWorks LMS 2.2/LMS 1.3 Update 1" section.


You can uninstall LMS using the instructions in the application installation guides. Uninstall each application in the reverse order of upgrade.


Note You should not uninstall CiscoWorks Common Services 2.2 before uninstalling applications dependent on it.


Adding or Updating Devices in Inventory


Step 1 Verify that the devices you want to monitor have the correct Cisco IOS version.

Step 2 Log in to your CiscoWorks Common Services server.

The CiscoWorks Common Services Server desktop appears.

Step 3 To add or update a device, select one of the following:

Resource Manager Essentials  >  Administration  >  Inventory  >  Add Devices

Resource Manager Essentials  >  Administration  >  Inventory  >  Update Inventory.

The Add a Single Device or the Update Device dialog box appears.

Step 4 Enter the access information and annotations for atleast one device.

You must enter the device name or IP address in the Device Name filed. All other fields are optional. For more information, see the Inventory online help.


Upgrading to CiscoWorks LMS 2.2/LMS 1.3 Update 1

This section contains the following information:

Description

Hardware and Software Requirements

Prerequisites for CiscoWorks LMS 2.2/LMS 1.3 Update 1

Downloading CiscoWorks LMS 2.2/LMS 1.3 Update 1

Installing CiscoWorks LMS 2.2/LMS 1.3 Update 1

Installing Real-Time Monitor SP 8

Known Problems

Resolved Problems

Description

CiscoWorks LMS 2.2/LMS 1.3 Update 1 contains the following updates:

CiscoWorks Common Services 2.2 with 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

Campus Manager 3.3 Update 1

Device Fault Manager 1.2 Updated for Common Services Version 2.2

Real-Time Monitor 1.4 Service Pack 8

CiscoWorks LMS 2.2/LMS 1.3 Update 1 provides new support for the following:

Java Plug-in 1.4.1_02

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

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

Netscape Navigator 7.0 (Solaris)

Netscape Navigator 7.1 (Windows)

Secure Shell 1.99

Table 10 describes the content of each update. CiscoWorks LMS 2.2/LMS 1.3 Update 1 also provides resolutions to known problems for individual applications (see the "Resolved Problems" section).

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.

Table 10 CiscoWorks LMS 2.2/LMS 1.3 Update 1 Contents  

Update
Contents

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

Java Plug-in 1.4.1_02 support

Netscape Navigator 7.x support (Netscape Navigator 7.0 on Solaris and Netscape Navigator 7.1 on Windows)

Windows 2000 SP4 support (client and server)

Windows XP SP1a support (client)

Fixes for problems in CiscoWorks Common Services 2.2.

Resource Manager Essentials 3.5 Update 1(RME)

Java Plug-in 1.4.1_02 support

Netscape Navigator 7.x support (Netscape Navigator 7.0 on Solaris and Netscape Navigator 7.1 on Windows)

Windows 2000 SP4 support (client and server)

Windows XP SP1a support (client).

Campus Manager 3.3 Update 1 (Campus)

Java Plug-in 1.4.1_02 support

Netscape Navigator 7.x support (Netscape Navigator 7.0 on Solaris and Netscape Navigator 7.1 on Windows.)

Windows 2000 SP4 support (client and server)

Windows XP SP1a support (client).

Device Fault Manager 1.2 Updated for Common Services Version 2.2 (DFM)

Java Plug-in 1.4.1_02 support

Netscape Navigator 7.x support (Netscape Navigator 7.0 on Solaris and Netscape Navigator 7.1 on Windows.)

Windows 2000 SP4 support (client and server)

Windows XP SP1a support (client)

Fixes for DFM-specific problems.

Real-Time Monitor 1.4 Service Pack 8

Java Plug-in 1.4.1_02 support

Netscape Navigator 7.x support (Netscape Navigator 7.0 on Solaris and Netscape Navigator 7.1 on Windows)

Windows 2000 SP4 support (client and server)

Windows XP SP1a support (client).


Hardware and Software Requirements

Hardware and software requirements for CiscoWorks LMS 2.2/LMS 1.3 Update 1 are the same as those for initial installation of CiscoWorks LMS 2.2, except for the following:

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

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

For a listing of the basic hardware and software requirements, see the "Hardware and Software Requirements" section.

Changes in Browser Support

CiscoWorks LMS 2.2/LMS 1.3 Update 1 supports the following browsers:

On Solaris:

Netscape Navigator 7.0

Netscape Navigator 4.76

On Windows:

Internet Explorer 6.0 and 6.0 SP1

Netscape Navigator 7.1, 4.78, and 4.79


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.

Table 11 summarizes the conditions under which you will see these behaviors and the actions you should take in each case. See also 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. For details, see http://sunsolve.sun.com. Customers who are concerned about this Alert Notification should see the "Using Sun Java Plug-in 1.4.1_05" section.


Note In Internet Explorer, a dummy applet is loaded before the login page in order to detect whether the browser has a Java VM. This may cause a slight delay in getting to the login page.


Table 11 Java Plug-in First-Time Setup Behavior 

Browser
Symptom
Recommended Action

Any supported browser

The first time you run ACL Manager or IPM, a message appears, prompting you to download the file vbjorb.jar.

1. Click OK to download the file.

2. Close and restart your browser.

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 >, a message appears, indicating that you are using an unsupported Java Plug-in.

1. Click OK.

You are directed to a help page.

2. Follow the instructions given in the help page.

Internet Explorer with Microsoft VM

You are prompted to install Java Plug-in 1.4.1_02 only when you run a Plug-in application, such as CiscoView or NetConfig.

Follow the recommended installation instructions.

You may 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 run CiscoWorks Common Services 2.2.

Follow the recommended installation instructions.

If you have the Internet Explorer option Install on demand (on Windows XP) enabled, you are prompted to download the Java VM.

1. Click Cancel (not OK).

2. Follow the recommended installation instructions.

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

You are prompted to install Java Plug-in 1.4.1_02 only when you run a plug-in application, such as CiscoView, NetConfig, etc.

Follow the installation instructions.

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

A message appears, indicating that you are using an unsupported Java Plug-in.

1. Click OK.

You are directed to a help page.

2. Follow the instructions given in the help page.

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

Instructions to install Java Plug-in 1.4.1_02 appear when you run CiscoWorks Common Services 2.2.

Follow the installation instructions.


General Recommendations on Java Plug-in 1.4.1_02

The following sections give general recommendations and procedures to follow when installing and using the Java Plug-in (JPI):

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

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.

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 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 Machine failed. 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 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 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.

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


Step 1 Install CiscoWorks CiscoWorks LMS 2.2/LMS 1.3 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)

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:

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 8 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 LMS 2.2/LMS 1.3 Update 1

Ensure that you have completed the following tasks before installing
CiscoWorks LMS 2.2/LMS 1.3 Update 1. After you have completed these tasks, you can install this Update using the instructions in the
"Installing CiscoWorks LMS 2.2/LMS 1.3 Update 1" section.

Install CiscoWorks Common Services 2.2 and the LMS applications to be updated. For details, see the Quick Start Guide for your LMS bundle listed in the "Hardware and Software Requirements" section.

Please note:

If you decide not to install one or more of the LMS applications at this point, then install them later, you must remember to reapply
CiscoWorks 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.

Through download from Cisco.com at the following URL: http://www.cisco.com/cgi-bin/tablebuild.pl/cw2000-rme.

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.

Through download from Cisco.com at the following URL: http://www.cisco.com/cgi-bin/tablebuild.pl/cw2000-campus.

If you have installed Device Fault Manager (DFM), you must also install eitherthe DFM 1.2 Patch/Incremental Device Update (IDU) 1.2.5, or the latest DFM patch/IDU, before you attempt to install CiscoWorks LMS 2.2/LMS 1.3 Update 1.

The DFM 1.2 Patch/IDU 1.2.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 Device Fault Manager.

For the Windows version, see the folder \Windows\IDU for Device Fault Manager.

The latest DFM 1.2 patch/IDU and the accompanying README explaining how to install it are available through download from Cisco.com at the following URL: http://www.cisco.com/cgi-bin/tablebuild.pl/cw2000-dfm.

If you have received the OpenSSL 0.9.7c patch for
CiscoWorks Common Services 2.2 (see bug ID CSCec43722), be sure to install it after you install CiscoWorks LMS 2.2/LMS 1.3 Update 1.

If you have already installed the OpenSSL patch, you must reinstall it after you install CiscoWorks LMS 2.2/LMS 1.3 Update 1.

RTM 1.4 must be installed before you upgrade to
Real-Time Monitor 1.4 Service Pack 8.

Downloading CiscoWorks LMS 2.2/LMS 1.3 Update 1

CiscoWorks LMS 2.2/LMS 1.3 Update 1 is available for download from the Cisco.com Software Center site at

http://www.cisco.com/kobayashi/sw-center/cw2000/lan-planner.shtml

Installing CiscoWorks LMS 2.2/LMS 1.3 Update 1

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

CiscoWorks LMS 2.2/LMS 1.3 Update 1 is provided as a single installable. Use the appropriate procedure to install it:

Installing CiscoWorks LMS 2.2/LMS 1.3 Update 1 on Solaris

Installing CiscoWorks LMS 2.2/LMS 1.3 Update 1 on Windows


Note You cannot uninstall CiscoWorks LMS 2.2/LMS 1.3 Update 1 after you install it.


Installing CiscoWorks LMS 2.2/LMS 1.3 Update 1 on Solaris

If you have downloaded the Update for Solaris, you must first extract the installable files from CiscoWorks-LMS-2.2-LMS-1.3-Update-1-k9.tar.

To install the Update on Solaris:


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

To install the Update, you must have superuser privileges on the system being updated.

Step 2 Mount the Update CD-ROM using one of the following methods:

Mount the CD-ROM on the CiscoWorks Server system.

or

Copy the file setup.sh to the appropriate directory.

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

For a local installation, enter:

# cd /cdrom/cdrom0/

# 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 4 Accept the SLA to continue.

The setup script displays a list of the updates to be installed or reinstalled.

Step 5 Press any key to install or reinstall all of the updates, or enter q to cancel installation.

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.

After the installation is completed, the setup script exits.


After you install the Update on Solaris, you must verify the installation. To do this:


Step 1 Launch CiscoWorks.

Step 2 Select Server Configuration > About the Server > Applications and Versions.

The About the Server page appears.

For each application you have chosen to install: If Update installation was successful, you will see the following entries in the Packages Installed table on this page:

Update
Columns in the Packages Installed Table
 

Name

Version
Installed Patches

CiscoWorks Common Services 2.2 with SP2

CiscoWorks Common Services with SP2

2.2

2

Resource Manager Essentials with Update 1

Resource Manager Essentials with Update 1

3.5

3

Campus Manager with Update 1

Campus Manager with Update 1

3.3

3

Device Fault Manager with Update 1

DFMSD

1.2

51

1 If you installed a later DFM 1.2 Patch/IDU, this number should match the last number of the patch/IDU version—for example, 6 for 1.2.6, 7 for 1.2.7, and so forth.



Installing CiscoWorks LMS 2.2/LMS 1.3 Update 1 on Windows

To install the Update on Windows:


Step 1 Start the Update installation using either of the following methods:

If you have the Update on CD-ROM and autorun is enabled on your system, place the CD-ROM in the CD-ROM drive.

If autorun is not enabled on your system or you are using a downloaded copy of the Update:

Run the installation setup script by double-clicking the file CiscoWorks-LMS-2.2-LMS-1.3-Update-1-k9.exe.

or

Select Start > Run, navigate to the location of the file CiscoWorks-LMS-2.2-LMS-1.3-Update-1-k9.exe, and click OK.

The CiscoWorks LMS 2.2/LMS 1.3 Update 1 confirmation screen appears.

Step 2 Click Yes.

The Welcome screen appears.

Step 3 Click Next to continue.

The Software License Agreement window appears. You must accept this agreement to install CiscoWorks LMS 2.2/LMS 1.3 Update 1.

Step 4 Click Yes to continue.

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

The System Requirements window 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 window appears, displaying the updates that will be installed and the settings for the installation.

Step 6 Click Next to continue.

The Setup window appears, displaying installation progress while files are copied and applications are configured. Installation takes approximately 15 minutes.

After the installation is complete, the Setup Complete window appears.

Step 7 Click Finish.


After you install the Update on Windows, you must verify the installation. To do this:


Step 1 Launch CiscoWorks.

Step 2 Select Server Configuration > About the Server > Applications and Versions.

The About the Server page appears.

For each application you have chosen to install: If Update installation was successful, you will see the following entries in the Packages Installed table on this page:

Update
Columns in the Packages Installed Table
 

Name

Version
Installed Patches

CiscoWorks Common Services 2.2 with SP2

CiscoWorks Common Services with SP2

2.2

2

Resource Manager Essentials with Update 1

Resource Manager Essentials with Update 1

3.5

3

Campus Manager with Update 1

Campus Manager with Update 1

3.3

3

Device Fault Manager with Update 1

DFMSD

1.2

51

1 If you installed a later DFM 1.2 Patch/IDU, this number should match the last number of the patch/IDU version—for example, 6 for 1.2.6, 7 for 1.2.7, and so forth.



Installing Real-Time Monitor SP 8

Before you begin:

Ensure that you install Real Time Monitor 1.4 before upgrading to Real Time Monitor SP 8.

Installing Real-Time Monitor SP 8 on Solaris

To install the Update on Solaris:


Step 1 Close all client browsers.

Step 2 Enter /RTM installation root directory/rtm/bin/stop to stop the nGenius Server.

For example, /opt/NetScout/rtm/bin/stop.

Step 3 Wait until all processes shut down.

Step 4 Log in as root.

Step 5 Copy rtm140-sp8-unix.sh to $NSHOME.

$NSHOME is the RTM home directory

Step 6 Execute rtm140-sp8-unix.sh available at $NSHOME.

Step 7 Enter /RTM installation root directory/rtm/bin/start to restart the nGenius Server:

Step 8 Clear the jar cache on every client system.


Installing Real-Time Monitor SP 8 on Windows

To install the Update on Windows:


Step 1 Close all client browsers.

Step 2 Select Start > Programs > NetScout nGenius Server > Stop nGenius Server to stop the nGenius Server

Step 3 Wait until all processes shut down.

Step 4 Execute rtm140-sp8-win.exe available at the following directory in the LMS Update 1 CD:

RTM1.4_SP8/

Step 5 Select Start > Programs > NetScout nGenius Server > Start nGenius Server to restart the nGenius Server.

Step 6 Clear the jar cache on every client system.


Known Problems

The following topics describe known problems in this Update:

CiscoWorks Common Services SP2: Known Problems

Java Plug-in 1.4.1_02: Known Problems

Resource Manager Essentials 3.5 Update 1: Known Problems

Campus Manager 3.3 Update 1: Known Problems

Device Fault Manager 1.2: Known Problems


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 in to Cisco.com.


CiscoWorks Common Services SP2: Known Problems

Table 12 lists problems that affect CiscoWorks Common Services 2.2 with Service Pack 2 (including CiscoView 5.5 Update 1) on Solaris.

Table 12 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 Common Services 2.2 web server ports is 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 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.

CSCsa01906

On Solaris, Netscape 4.76 crashes inconsistently while starting online help.

Netscape crashes while you run help from a plug-in applet such as a CiscoView, or a Resource Manager Essentials application like NetConfig or Config Editor.

Workaround:

Start online help by clicking Help in the main CiscoWorks Desktop (next to Logout).

You can browse through the contents from the help page.

CSCsa01571 (CiscoView)

Unable to specify host name of device list import source.

This occurs on Solaris clients running Netscape 7.0 when you:

1. Start Common Services 2.2.

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

3. Update the Host Name field with the correct information while the Campus or RME radio button is selected.

You cannot select or modify the field's contents.

Workaround:

1. Click the window of any other open application.

You must open another application if one is not open already.

2. Return to the CiscoView Import Device List window to specify a host name.

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, although a message confirms it.

Workaround:

Accept the License agreement to install the Java Plug-in properly.

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 applet flickers during the backup process and the bar may not display consistently.

Workaround:

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

CSCin50174

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

Exceptions sometimes appear when you use MAAS applets or RME applications.

Workaround:

You can ignore these exceptions.

CSCec35611 (CiscoView)

Unable to launch Telnet on Windows XP.

This problem occurs when you do the following on a Windows XP client that uses either Netscape 4.78 or Netscape 7.1 or Internet Explorer 6.0:

1. Click Device Manager > Cisco View

CiscoView window appears.

2. Select any device from the menu.

3. Click the Telnet button.

Telnet does not launch.

Workaround:

None.

CSCeb62374 (CiscoView)

Unable to print chassis view.

This problem occurs 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 may not be printed.

Workaround:

Select File > Print from the browser's Main Menu.


Table 13 lists problems that affect CiscoWorks Common Services 2.2 with Service Pack 2 (including CiscoView 5.5 Update 1) on Windows.

Table 13 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 Common Services 2.2 web server ports is 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 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.

Workaround:

1. Click on the Index tab.

2. Click on the Contents tab.

All elements in the Contents tree will be displayed.

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 applet flickers during the backup process and the bar may not display consistently.

Workaround:

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

CSCeb73291

While backing up data using VPN/Security Management Solution > Administration > Common Services > Backup database, the popup Progress Bar applet's text Backup Job progress status is not visible.

This sometimes occurs when using a Windows XP client.

Workaround:

Resize the popup up window to display the text properly.

CSCin51794

While backing up data using VPN/Security Management Solution > Administration > Common Services > Backup database, the popup Progress Bar applet hangs and you cannot exit from the applet.

This problem occurs only on Windows 2000 with Service Pack 4 as client and Netscape 4.78 as the browser.

Workaround:

Restart the browser.

CSCdz34376

During installation of updates, the message files locked appears.

This occurs when:

Server and client are running on the same system.

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

You have started reinstallation.

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

Workaround:

Close all browser sessions and any plug-in applets before the installation starts.

CSCin53790

You cannot use the Tab key to select components.

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

Workaround:

If this occurs, use the mouse to navigate among components.

CSCeb60816
(CiscoView)

Printout of chassis view is sometimes grayed out.

This occurs 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.

Workaround:

None.

CSCin51727

Java Plugin 1.4.1_02 installation on Windows hangs with 100 percent CPU usage if the Netscape 7.x browser is open.

This problem also occurs if Netscape 7.x Quick Launch is running in the system tray.

Workaround:

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 percent CPU usage and you use Task Manager to kill the process IKernel.exe (Doing this is not recommended), recover and reinstall the Plug-in as follows:

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.


Java Plug-in 1.4.1_02: Known Problems

Table 14 lists problems that affect Java Plug-in 1.4.1_02.

.

Table 14 Java Plug-in 1.4.1_02: Known Problems 

Bug ID
Summary
Explanation

None.

JPI 1.4.1_02 does not coexist with Java Plug-in 1.3.1.

The following problems occur:

The browser crashes 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 error message Attachment to a running Virtual Machine failed is displayed if you start an applet using Java Plug-in 1.3.1 and then start an applet using Java Plug-in 1.4.1_02.

Workaround:

Uninstall all previous versions of the 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.

Workaround:

Install Java Plug-in 1.4.1_02 again to re-enable the Microsoft VM.

None

SSL mode requires certificate acceptance.

When you run 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.

Workaround:

Close the browser, start CiscoWorks again, and this time choose to accept the certificate.


Resource Manager Essentials 3.5 Update 1: Known Problems

Table 15 lists problems that affect RME 3.5 Update 1.

Table 15 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.

When you try to generate an RME report, the report gets minimized. For example, if you:

1. Click on 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.

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:

1. Click on 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.

Workaround:

Wait until the previous task is completed.


Campus Manager 3.3 Update 1: Known Problems

Table 16 lists the problems known to affect Campus Manager 3.3 Update 1.

Table 16 Campus Manager 3.3 Update 1 Known Problems 

Bug ID
Summary
Explanation

CSCin57957

Campus OGSServer fails to start in the LMS or RWAN bundle when Fault History (FH) is installed. (Solaris with Netscape 7.0)

The problem occurs when you install FH on a server that has the LMS or RWAN installed. Campus OGSServer uses xerces.jar located in NMSROOT/MDC/tomcat/lib/apps/ directory for document traversal.

FH extracts the Sun XML parser jar file onto the NMSROOT/lib/classpath directory. This XML parser does not support document traversal that the Campus OGSServer requires.

Workaround:

Reorder the classpath of Campus OGSServer as follows:

On Solaris:

1. Open dmgtd.conf in the edit mode. The file is available at the following location:

NMSROOT/objects/dmgt/dmgtd.conf

   

2. Change the launch path of the CMFOGSServer to the following:

CampusOGSServer y CmfDbMonitor,ESS 
/opt/CSCOpx/bin/ 
cwjava -cpNMSROOT/MDC/tomcat/webapps/ 
campus/WEB-INF/classes:NMSROOT/MDC/ 
tomcat/webapps/campus/WEB-INF/lib/ 
ctm.jar:NMSROOT/MDC/tomcat/webapps/ 
campus/WEB-INF/lib/ 
ogs-server1.0.jar:NMSROOT/MDC/tomcat/ 
webapps/campus/WEB-INF/lib/ 
ogs-sharedasa1.0.jar:NMSROOT/MDC/ 
tomcat/webapps/campus/WEB-INF/lib/ 
ogs-sqlasa1.0.jar:NMSROOT/MDC/tomcat/ 
webapps/campus/WEB-INF/lib/ 
ogs-util1.0.jar:NMSROOT/MDC/tomcat/ 
webapps/campus/WEB-INF/ 
lib/ogs-client1.0.jar:NMSROOT/MDC/ 
tomcat/webapps/campus/WEB-INF/lib/ 
ogs-cmasa1.0.jar:NMSROOT/MDC/tomcat/ 
webapps/campus/WEB-INF/ 
lib/ogs-cmclient1.0.jar:NMSROOT/MDC/ 
tomcat/lib/apps/xerces.jar:NMSROOT/MDC/tomcat/l
ib/apps/log4j.jar:NMSROOT/MDC/ 
tomcat/webapps/campus/WEB-INF/lib/ 
jconnect5.2.jar:NMSROOT/lib/ 
classpath:NMSROOT/www/ 
classpath:NMSROOT/MDC/tomcat/lib/ 
appscom.cisco.nm.xms.ogs.server.OGSServer

In the above line, the variable, NMSROOT should be replaced with the CiscoWorks installation directory.

3. Restart the daemon manager by typing

/etc/init.d/dmgtd stop

and

/etc/init.d/dmgtd start

   

On Windows:

1. Click Start > Run

2. Enter regedit

The registry editor appears.

3. Click Edit > Find

4. Enter keyword CampusOGSServer.

This search will yield the key with this name.

5. Right click on value Args and choose Modify

6. Copy the following line:

-DNMSROOT=NMSROOT -cp 
MDC\tomcat\webapps\campus\WEB-INF\lib\ctm.jar;M
DC\tomcat\lib\apps\xerces.jar;MDC\ 
tomcat\webapps\campus\WEB-INF\lib\ 
ogs-server1.0.jar;MDC\tomcat\webapps\ 
campus\WEB-INF\lib\ 
ogs-sharedasa1.0.jar;MDC\tomcat\webapps\ 
campus\WEB-INF\lib\ogs-sqlasa1.0.jar;MDC\ 
tomcat\webapps\campus\WEB-INF\lib\ 
ogs-util1.0.jar;MDC\tomcat\webapps\campus\WEB-I
NF\lib\ogs-client1.0.jar;MDC\tomcat\ 
webapps\campus\WEB-INF\lib\ 
ogs-cmasa1.0.jar;MDC\tomcat\webapps\ 
campus\WEB-INF\lib\ 
ogs-cmclient1.0.jar;MDC\tomcat\webapps\ 
campus\WEB-INF\lib\jconnect5.2.jar;MDC\ 
tomcat\lib\apps\log4j.jar;MDC\tomcat\ 
webapps\campus\WEB-INF\classes;www\ 
classpath;lib\ 
classpathcom.cisco.nm.xms.ogs.server.OGSServer

In the above line, the variable, NMSROOT should be replaced with the CiscoWorks installation directory.

7. Restart the daemon manager by typing:

net stop crmdmgtd and then net start crmdmgtd


Device Fault Manager 1.2: Known Problems

Table 17 lists the problems known to affect Device Fault Manager Update 1.

Table 17 Device Fault Manager 1.2 Known Problems  

Bug ID
Summary
Explanation

CSCec31624

DFM update information is not provided in the Selected Component Screen of the LMS 2.2/LMS 1.3 Update 1.

The problem occurs when you do the following:

1. Install Common Services 2.2, RME 3.5, CM 3.3, DFM 1.2 Updated for Common Services 2.2 and Fault History

2. Install LMS 2.2/ LMS 1.3 Update 1

In the Summary window, the current settings field does not list DFM as part of the Selected Components although DFM 1.2 Update 1 is installed.

Workaround:

None.

CSCed48695

LMS 2.2 Update 1: Resizing Monitoring Console does not resize the columns

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.


Resolved Problems

The following topics describe previously reported problems resolved by installing CiscoWorks LMS 2.2/LMS 1.3 Update 1:

CiscoWorks Common Services SP2: Resolved Problems

Device Fault Manager 1.2: Resolved Problems

Real Time Monitor 1.4: Resolved Problems

CiscoWorks Common Services SP2: Resolved Problems

Table 18 lists reported problems with CiscoWorks Common Services 2.2 which this Update resolves.

Table 18 CiscoWorks Common Services 2.2 SP2: Resolved Problems 

Bug ID
Summary
Additional Information

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.

CSCin44573

Solaris Restore DB after password change failed.

This problem has been resolved.

CSCin43722

SqlcoreDB terminated before dependent daemons shut down.

This problem has been resolved.

CSCeb49238

Increased default tomcat heap size for Solaris.

This problem has been resolved.

CSCeb46559

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

This problem has been resolved.

CSCeb45532

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

This problem has been resolved.

CSCeb44684

Unnecessary jars were set to the CLASSPATH in tomcat.sh.

This problem has been resolved.

CSCeb37909

Temporary directories are not removed after installation.

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

CSCeb15620

PixMC backup failed even after 50 tries.

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.

CSCeb08436

The CiscoWorks ESS process broadcast on UDP port 42350.

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.

CSCea56786

String size change in License.dll corrupted system memory.

This problem has been resolved.

CSCdx74061

Two steps needed to schedule backups and compacts.

This problem has been resolved.


Device Fault Manager 1.2: Resolved Problems

Table 19 lists previously reported DFM problems which this Update resolves.

Table 19 Device Fault Manager 1.2 Resolved Problems  

Bug ID
Summary
Additional Information

CSCdz09238

Unable to resize the Monitoring Console columns

This problem has been resolved.


Real Time Monitor 1.4: Resolved Problems

Table 20 lists previously reported RTM problems which this Update resolves.

Table 20 Device Fault Manager 1.2 Resolved Problems  

Bug ID
Summary
Additional Information

CSCea73863

Unable to add Cat4k IOS switch access for port-channel configuration.

This problem has been resolved.

CSCdz90082

SMON Monitor menu is not disabled for NetFlow interface

This problem has been resolved.


13 Where to Go Next

After you have upgraded the required products, you are ready to manage your LAN environment. For more information, see the following User Guides for the LMS component applications:

Using CiscoView 5.5

User Guide for CiscoWorks Common Services

User Guide for Resource Manager Essentials

User Guide for Campus Manager

User Guide For Device Fault Manager

NetScout nGenius Real-Time Monitor 1.4 Getting Started Guide

You can access these documents:

In PDF in the Documentation directory on the LMS product CD-ROM.

In HTML and PDF on Cisco.com.

From Cisco.com:

a. Select Products and Services > Network Management CiscoWorks > CiscoWorks LAN Management Solution.

b. Select the appropriate LMS application.

c. Select Instructions and Guides > User Guides Books.

From the CiscoWorks Online help:

a. From the CiscoWorks desktop, click Help.

b. Select the appropriate LMS application.

14 Related Documentation

For information about upgrading, troubleshooting, and using the products in the LAN Management Solution, see Table 21.


Note To view documents in Adobe Portable Document Format (PDF), Adobe Acrobat 4.0 or later is required. To view documents on Cisco.com, log on to your Cisco.com home page, then select Products and Services>Network Management CiscoWorks > CiscoWorks LAN Management Solution > Versions and Options > CiscoWorks LAN Management Solution 2.2.


Table 21 Related Documentation 

To learn
more about...
See this document
In the product package?
On the product
CD? 1
On Cisco.com?
On the Cisco Doc. CD?
In the online
help?

The known product bugs (DDTS)

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

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

Release Notes for Resource Manager Essentials 3.5 on Solaris

Release Notes for Resource Manager Essentials 3.5 on Windows

Release Notes for Campus Manager 3.3 on Solaris

Release Notes for Campus Manager 3.3 on Windows

Yes

No

Yes

Yes (PDF, HTML)

No

The known product bugs (DDTS)

(continued)

Supplement and Release Notes for NetScout nGenius Real-Time Monitor Release 1.4 Service Pack 6

NetScout nGenius Real-Time Monitor 1.4 Release Notes

Release Notes for Device Fault Manager 1.2 Updated for Common Services Version 2.2 on Windows

Release Notes for Device Fault Manager 1.2 Updated for Common Services Version 2.2 on Solaris

Yes

No

Yes

Yes (PDF, HTML)

No

Performing a typical or custom installation

Installation and Setup Guide for CiscoWorks Common Services (Includes CiscoView) on Solaris (DOC-7815431=)

Installation and Setup Guide for CiscoWorks Common Services (Includes CiscoView) on Windows (DOC-7815430=)

Installation and Setup Guide for Resource Manager Essentials 3.5 on Solaris (DOC-7814808=)

No

Yes

Yes

Yes (PDF, HTML)

No

Performing a typical or custom installation

(continued)

Installation and Setup Guide for Resource Manager Essentials 3.5 on Windows (DOC-7814809=)

Installation and Setup Guide for Campus Manager on Solaris (DOC-7815049=)

Installation and Setup Guide for Campus Manager on Windows (DOC-7815050=)

Installation and Setup Guide For Device Fault Manager on Solaris (DOC-7814966=)

Installation and Setup Guide For Device Fault Manager on Windows (DOC-7814965=)

No

Yes

Yes

Yes (PDF, HTML)

No

NetScout nGenius Real-Time Monitor 1.4 Installation Guide (DOC-7814181=)

Yes

Yes

Yes

Yes (PDF, HTML)

No

Features, tasks, and troubleshooting

Using CiscoView 5.5 (DOC-7815219=)

User Guide for CiscoWorks Common Services (DOC-7815301=)

No

Yes

Yes2

Yes

Yes

Features, tasks, and troubleshooting

(continued)

User Guide for Resource Manager Essentials (DOC-7814810=)

User Guide for Campus Manager (DOC-7815051=)

NetScout nGenius Real-Time Monitor 1.4 Getting Started Guide

User Guide For Device Fault Manager (DOC-7814967=)

No

Yes

Yes

Yes

Yes

Device Support

Supported Device Table for Resource Manager Essentials 3.53

Supported Device Table for Campus Manager 3.34

Supported Devices Table for Device Fault Manager 1.25

No

No

Yes

No

No

1 Provided as PDF in Documentation directory on the product CD-ROM.

2 From the CiscoWorks desktop, click Help.

3 To view the document on Cisco.com, log on to your Cisco.com home page, then select Products and Services > Network Management CiscoWorks > CiscoWorks Resource Manager Essentials > Technical Documentation > Device Support Tables.

4 To view the document on Cisco.com, log on to your Cisco.com home page, then select Products and Services > Network Management CiscoWorks > CiscoWorks Campus Manager > Technical Documentation > Device Support Tables.

5 To view the document on Cisco.com, log on to your Cisco.com home page, then select Products and Services > Network Management CiscoWorks > CiscoWorks Device Fault Manager > Technical Documentation > Device Support Tables.


5 Although every effort has been made to validate the accuracy of the information in the printed and electronic documentation, you should review the documentation on Cisco.com for the latest updates.



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 annual or quarterly subscriptions through the online Subscription Store:

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

Click Subscriptions & Promotional Materials in the left navigation bar.

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

Documentation Feedback

You can submit e-mail comments about technical documentation to bug-doc@cisco.com.

You can submit comments by using the response card (if present) behind the front cover of your document or by writing to the following address:

Cisco Systems
Attn: Customer Document Ordering
170 West Tasman Drive
San Jose, CA 95134-9883

We appreciate your comments.

Obtaining Technical Assistance

For all customers, partners, resellers, and distributors who hold valid Cisco service contracts, 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.

Cisco TAC Website

The Cisco TAC website (http://www.cisco.com/tac) provides online documents and tools for troubleshooting and resolving technical issues with Cisco products and technologies. The Cisco TAC website is available 24 hours a day, 365 days a year.

Accessing all the tools on the Cisco TAC website requires a Cisco.com user ID and password. If you have a valid service contract but do not have a login ID or password, register at this URL:

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

Opening a TAC Case

Using the online TAC Case Open Tool (http://www.cisco.com/tac/caseopen) is the fastest way to open P3 and P4 cases. (P3 and P4 cases are those in which your network is minimally impaired or for which you require product information.) After you describe your situation, the TAC Case Open Tool automatically recommends resources for an immediate solution. If your issue is not resolved using the recommended resources, your case will be assigned to a Cisco TAC engineer.

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.

To open a case by telephone, use one of the following numbers:

Asia-Pacific: +61 2 8446 7411 (Australia: 1 800 805 227)
EMEA: +32 2 704 55 55
USA: 1 800 553-2447

For a complete listing of Cisco TAC contacts, go to this URL:

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

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:

http://www.cisco.com/en/US/products/index.html

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:

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/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/index.html