Guest

CiscoWorks LAN Management Solution 3.2 and earlier

Quick Start Guide for LAN Management Solution 2.2 (Maintenance Kit)

  • Viewing Options

  • PDF (1.8 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

LMS Contents

Additional Information Online

What's New?

Server and Client System Requirements

Solaris Patches

LAN Management Solution Port Usage

Upgrade Paths

Upgrade Options

Upgrading to LAN Management Solution 2.2

Prerequisites

Important Upgrade Notes

Order of Upgrade

Upgrading CiscoWorks Common Services 2.2

Upgrading CiscoWorks Common Services 2.2 on Solaris

Upgrading CiscoWorks Common Services 2.2 on Windows

Upgrading Resource Manager Essentials 3.5

Upgrading Resource Manager Essentials 3.5 on Solaris

Upgrading Resource Manager Essentials 3.5 on Windows

Upgrading Campus Manager 3.3

Upgrading Campus Manager 3.3 on Solaris

Upgrading 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 nGenius Real-Time Monitor 1.4 Service Pack 6

Adding or Updating Devices in Inventory

Where to Go Next

Related Documentation

Obtaining Documentation

Cisco.com

Documentation CD-ROM

Ordering Documentation

Documentation Feedback

Obtaining Technical Assistance

Cisco.com

Technical Assistance Center

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.

LMS Contents

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

Table 1 LMS 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 (download site provided at the end of this 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 includes:

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

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

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

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 recommended4

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

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 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.1 or 2.0 installed

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

CiscoWorks Routed WAN Management Solution (RWAN) Release 1.2 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.

RWAN 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 those components are already installed on your system.


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


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. 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. For more information, See the Installation and Setup Guide For Device Fault Manager. Document location details are provided in "Related Documentation" section.

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 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 CiscoWorks Common Services 2.2" section.

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

Step 3 Upgrade Campus Manager 3.3. See "Upgrading 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 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 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 CD-ROMDrive/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 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 Resource Manager Essentials 3.5

Upgrading Resource Manager Essentials takes approximately 30 minutes.

Upgrading 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 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 Campus Manager 3.3

Upgrading Campus Manager takes approximately 11 minutes.

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

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

Post-Upgrade Tasks

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

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.

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

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.


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

13 Related Documentation

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


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

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

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

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

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

NetScout nGenius Real-Time Monitor 1.4 Getting Started Guide

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 web sites 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 monthly and may be more current than printed documentation. The CD-ROM package is available as a single unit or through an annual subscription.

Registered Cisco.com users can order the Documentation CD-ROM (product number DOC-CONDOCCD=) through the online Subscription Store:

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

Ordering Documentation

You can find instructions for ordering documentation at this URL:

http://www.cisco.com/univercd/cc/td/doc/es_inpck/pdi.htm

You can order Cisco documentation in these ways:

Registered Cisco.com users (Cisco direct customers) can order Cisco product documentation from the Networking Products MarketPlace:

http://www.cisco.com/en/US/partner/ordering/index.shtml

Registered Cisco.com users can order the Documentation CD-ROM (Customer Order Number DOC-CONDOCCD=) through the online Subscription Store:

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

Nonregistered Cisco.com users can order documentation through a local account representative by calling Cisco Systems Corporate Headquarters (California, U.S.A.) at 408 526-7208 or, elsewhere in North America, by calling 800 553-NETS (6387).

Documentation Feedback

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

You can email your comments to bug-doc@cisco.com.

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

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

We appreciate your comments.

Obtaining Technical Assistance

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

Cisco.com

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

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

Streamline business processes and improve productivity

Resolve technical issues with online support

Download and test software packages

Order Cisco learning materials and merchandise

Register for online skill assessment, training, and certification programs

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

http://www.cisco.com

Technical Assistance Center

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

We categorize Cisco TAC inquiries according to urgency:

Priority level 4 (P4)-You need information or assistance concerning Cisco product capabilities, product installation, or basic product configuration.

Priority level 3 (P3)-Your network performance is degraded. Network functionality is noticeably impaired, but most business operations continue.

Priority level 2 (P2)-Your production network is severely degraded, affecting significant aspects of business operations. No workaround is available.

Priority level 1 (P1)-Your production network is down, and a critical impact to business operations will occur if service is not restored quickly. No workaround is available.

Cisco TAC Website

You can use the Cisco TAC website to resolve P3 and P4 issues yourself, saving both cost and time. The site provides around-the-clock access to online tools, knowledge bases, and software. To access the Cisco TAC website, go to this URL:

http://www.cisco.com/tac

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

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

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

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

If you have Internet access, we recommend that you open P3 and P4 cases through the Cisco TAC website so that you can describe the situation in your own words and attach any necessary files.

Cisco TAC Escalation Center

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

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

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

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

Obtaining Additional Publications and Information

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

The Cisco Product Catalog describes the networking products offered by Cisco Systems as well as ordering and customer support services. Access the Cisco Product Catalog at this URL:

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

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

http://www.ciscopress.com

Packet magazine is the Cisco monthly periodical that provides industry professionals with the latest information about the field of networking. You can access Packet magazine at this URL:

http://www.cisco.com/en/US/about/ac123/ac114/about_cisco_packet_magazine.html

iQ Magazine is the Cisco monthly periodical that provides business leaders and decision makers with the latest information about the networking industry. You can access iQ Magazine at this URL:

http://business.cisco.com/prod/tree.taf%3fasset_id=44699&public_view=true&kbns=1.html

Internet Protocol Journal is a quarterly journal published by Cisco Systems for engineering professionals involved in the design, development, and operation of 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, with current offerings in network training listed at this URL:

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