Guest

CiscoWorks LAN Management Solution 3.2 and earlier

Quick Start Guide for CiscoWorks LAN Management Solution 2.5 (Maintenance Kit)

  • Viewing Options

  • PDF (2.2 MB)
  • Feedback
Quick Start

Table Of Contents

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

SUPPLEMENTAL LICENSE AGREEMENT

LAN Management Solutions 2.5 Overview

Critical Upgrade Information

Licensing

Understanding Licensing Terms

Licensing Your Product

LMS Package Contents

Additional Information Online

What's New

Server and Client System Requirements

Solaris Patches for LAN Management Solution

LAN Management Solution Port Usage

LMS Data Backup

Backing up LMS Data Manually From the Command Line

Backing up LMS Data Using the CiscoWorks Server

Automatic Data Backup During Common Services Installation

Backing up IPM Data

Upgrading Your Operating System

Upgrade Installation Paths

Upgrade Options

Upgrading to LAN Management Solution 2.5

Prerequisites

Proof of Purchase

Important Upgrade Notes

Order of Upgrade

Upgrading to CiscoWorks Common Services 3.0

Upgrading to CiscoWorks Common Services 3.0 on Solaris

Upgrading to CiscoWorks Common Services 3.0 on Windows

Upgrading to Resource Manager Essentials 4.0

Upgrading to Resource Manager Essentials 4.0 on Solaris

Upgrading to Resource Manager Essentials 4.0 on Windows

Upgrading to Campus Manager 4.0

Upgrading to Campus Manager 4.0 on Solaris

Upgrading to Campus Manager 4.0 on Windows

Upgrading to Device Fault Manager 2.0

Upgrading to Device Fault Manager 2.0 on Solaris

Upgrading to Device Fault Manager 2.0 on Windows

Upgrading to Internetwork Performance Monitor 2.6

Upgrading to Internetwork Performance Monitor 2.6 on Solaris

Upgrading to Internetwork Performance Monitor 2.6 on Windows

Migrating LMS Data

Getting Started with LMS

Invoking the CiscoWorks Homepage

Logging In

Understanding the CiscoWorks Homepage

Common Services Panel

Application Panel

Resources Panel

CiscoWorks Product Updates Panel

Tool Bar Items

Post-Upgrade Tasks

Configuring Device Discovery Using Campus Manager

Adding Devices Using the Device and Credential Admin

Configuring Data Collection

Enabling Single Sign-On

Setting Up System Identity User

Configuring Master Self Signed Certificate

Configuring the CiscoWorks Homepage

Using Applications in ACS Mode

Configuring ACS

Registering Applications to the ACS

Enabling Browser-Server Security From the CiscoWorks Server

Uninstalling LMS

Where to Go Next

Related Documentation

Obtaining Documentation

Cisco.com

Ordering Documentation

Documentation Feedback

Obtaining Technical Assistance

Cisco Technical Support Website

Submitting a Service Request

Definitions of Service Request Severity

Obtaining Additional Publications and Information


Quick Start

Quick Start Guide for LAN Management Solution 2.5 (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

Three Hundred Device Restricted Version. Customer may install and run the Software on a single server to manage up to three hundred (300) Cisco devices concurrently across all components provided in this solution. When used anywhere in this SLA, a "device" means any device in the Customer's network environment which has its own IP address. Please refer to the component installation guide for further device definition. Customers whose requirements exceed the restricted version limit of three hundred (300) devices must upgrade to the non-restricted version of the Software. Device restrictions are enforced by license registration.

Non-Restricted Device Version. Customer may install and run the Software on a single server to manage Cisco devices concurrently across all components provided in this solution. Please refer to the component installation guide for further device definition. Device restrictions are enforced by license registration. The deployment of the non-restricted device version is defined by the Installation and Use section in this document.

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. Some license terms such as device count and proof of preexisting licenses may be electronically enforced. Customer may install and use following Software components:

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

Resource Manager Essentials (RME): 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.

Internetwork Performance Monitor (IPM): 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 Solutions 2.5 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.


Caution LMS 2.5 must be installed only on a dedicated server. If you install any other product on the same server, it will lead to issues resulting in the uninstallation and reinstallation of LMS.

You can select any one of the following two versions of LMS 2.5:

Enterprise Restricted: Limits you to manage 300 devices.

Large Enterprise Unrestricted: Does not impose any limit on the number of managed devices.

LAN Management Solution 2.5 does not coexist with any other Solution.

In this document you will find:

LMS package contents, including links for accessing online documentation.

LMS features highlights.

Hardware and software requirements for optimal performance.

Upgrade paths and pointers to additional documentation that provides detailed procedures for installing each application.

Information on getting started with LMS.

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


Note This document contains information for CiscoWorks LMS 2.x Maintenance customers.


Critical Upgrade Information

If you are installing LMS 2.5 on a Solaris server that previously hosted LMS or RWAN, run check_pkg_errors.sh before Common Services 3.0 upgrade. The script checks and fixes any Solaris Package error.

The script is available at:

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

To check the package errors in Solaris:


Step 1 Download the check_pkg_errors.sh script from: http://www.cisco.com/cgi-bin/tablebuild.pl/cw2000-cd-one

Step 2 Enter the following command to check and display package errors:

sh dir/check_pkg_errors.sh

where dir is the directory to which you downloaded the script.

Step 3 Enter the following command to fix the package errors:

sh dir/check_pkg_errors.sh -c


The script logs all its output to the /var/tmp/ciscoinstall.log file.

Licensing

The LMS 2.5 product features software based product registration and license key activation technologies. During the installation process, the installer displays the registration and licensing input dialog box. The following table provides information about terminology used in the registration process.

Understanding Licensing Terms

Table 1 describes PAK, PIN, and License file and its usage.

Table 1 Understanding PAK, PIN, and License File

Licensing Terms
Description

Product

Identification

Number (PIN)

The PIN is printed on the software claim certificate. The LMS installation program prompts you to enter the PIN during installation. If an authenticated license cannot be obtained during installation, use the PIN to proceed with the installation. If only a PIN is entered, LMS will run normally, but you will be periodically reminded to complete the license process.

Product

Authorization Key

(PAK)

The PAK is printed on the software claim certificate. Use the PAK to get your license file from Cisco.com. You may obtain and install your license file at any time while you are working on LMS, not necessarily only at the time you install the product.

We recommend that you complete the LMS license registration and receive product license before installing the LMS 2.5.

If the person installing LMS is not authorized to obtain the license on behalf of the administrator, the product can be successfully installed for a period of time using only the PIN. In this case, the product will automatically remind the administrator to complete the licensing process.

License file

When you register your LMS purchase on the product licensing area of Cisco.com, you will receive a license file. You need to provide your PAK to receive a license file.

If you are a registered user of Cisco.com, get your license file from: http://www.cisco.com/go/license

If you are not a registered user of Cisco.com, get your license file from: http://www.cisco.com/go/license/public

Logging in allows your Cisco user profile information to auto-populate many of the product registration fields. Login is case sensitive.


Figure 1 displays the licensing screen on Windows operating system.

Figure 1 Licensing Screen

As you begin the LMS installation process, you must first install CiscoWorks Common Services 3.0 (see Server and Client System Requirements). You will not be prompted for registration information during this process. After Common Services is installed on your LMS server, you can install LMS applications, such as RME 4.0, Campus 4.0, DFM 2.0 and IPM 2.6.

The first LMS application you install, prompts you to provide the LMS licensing information (see Figure 1). The LMS installation program prompts you to enter either the license file, or the PIN and PAK. We recommend that you complete the license registration process at this point.

The LMS installer only prompts you once per server for licensing information that is used by all components of the solution. If you provide a valid license or the PIN and PAK while installing the first LMS application on a given server, the other applications installed later on that server will not prompt for a license.

Evaluation Mode: If you have received the LMS as an evaluation copy, you need not register the product during the 90 day evaluation period. The installation process for an evaluation copy is same as that of a purchased product; except that you will be prompted by each of the LMS applications to select the Evaluation Only option from the Licensing Information page (see Figure 1.)

If you choose to run any application in evaluation mode, the application will stop functioning after 90 days. The evaluation period can NOT be extended. If you have a purchased copy and you decide to install it in evaluation mode, please use your PAK to register the product on the Cisco online licensing site and receive a valid license.

If you have not purchased the product, the LMS evaluation server can be reactivated by purchasing LMS from your authorized Cisco reseller and license the product using the PAK and PIN provided with the product. For details see, "Licensing Your Product" section.

While installing DFM, the installer will look for an older version of DFM. Installation proceeds if an older copy of DFM is found in the local machine, remote machine, or in a designated CD drive.

Licensing Your Product

We recommend that prior to installing the LMS 2.5 product, that you register the product and receive a permanent license.

To license your product, you must:


Step 1 Register the LMS product using the PAK with Cisco.com to get your license file.

The PAK is printed on the software claim certificate.

If you are a registered user of Cisco.com, get your license file from: http://www.cisco.com/go/license

If you are not a registered user of Cisco.com, get your license file from: http://www.cisco.com/go/license/public

Logging in allows your Cisco user profile information to auto-populate many of the product registration fields. Login is case sensitive.

Step 2 After you install Common Services 3.0, copy the new license file to the CiscoWorks Common Services server into a directory with read permissions for the user name casuser or the user group casusers.

Step 3 Install the license file.

If you have obtained the LMS license prior to installation:

a. Select the first LMS application you wish to install, and when prompted:

On Windows, select the first radio button (see Figure 1) and use the browse window to locate the license file directory.

On Solaris, select L for License File after you accept the Licensing Agreement and continue installing the application.

b. Click Next to install the license file.

If you have completed the LMS install by entering the PAK and PIN, or if you want to convert an evaluation copy to a licensed copy:

a. From the CiscoWorks Homepage, select Common Services > Server > Admin > Licensing.

The License Administration page appears.

b. Click Update.

A file browser dialog box appears.

c. Enter the path to the new license file in the License field, or click Browse to locate the license file you copied to the server in step 2.

d. Click OK.

The system verifies whether the license file is valid, and updates the license.

The updated licensing information appears in the License Information page. If you encounter errors, repeat the steps to license your product.

If you are upgrading DFM, you might be prompted to validate your DFM image. Insert a DFM 1.2 or DFM 1.2 updated for Common Services 2.2 CD into one of your system drives. The installation software validates the DFM image.


Additional Information for LMS 2.5 Large Enterprise Unrestricted Licensing

Users of LMS 2.5 for Large Enterprises often require individual LMS applications such as DFM or RME to be run on separate servers to support large number of devices or to meet certain performance criteria.

When more than one server is used to host the LMS, each server should have a copy of the license in it. You should copy the license file to the server as described in Step 2, and install the license as described in Step 3. You should not modify the license file.

Legal restriction concerning the distribution of the LMS applications is described in the Supplemental License Agreement. More than one copy of an application (RME, DFM, Campus, or IPM) should not be running in the network unless additional copies of LMS have been purchased and licensed.

LMS Package Contents

Table 2 describes the contents of the LAN Management Solution for Solaris and Windows.

Table 2 LAN Management Solution Contents 

This LMS Component...
Provides...
And includes these components

CiscoWorks Common Services 3.0 (Includes CiscoView 6.1)

Common software and services for LMS.

Common Services 3.0 provides a set of shared application services that are used by all LMS applications.

CiscoView 6.1 is a graphical device management tool that helps monitor, and troubleshoot devices across your network.

Integration Utility 1.6 is an integration module that supports third-party Network Management Systems (NMS).

CiscoWorks Common
Services 3.0 Includes CiscoView 6.1 CD-ROM

Release Notes for CiscoWorks Common Services 3.0 (Includes CiscoView 6.1) on Solaris

Release Notes for CiscoWorks Common Services 3.0 (Includes CiscoView 6.1) on Windows

Campus Manager 4.0 (Campus)

Campus is sometimes referred to as CM

The ability to:

Visualize Network topology

Manage VLANs

Detect network discrepancies and best-practice non-compliance, Layer 2/3 data and voice traces

Use end-host user information to help in capacity planning.

Campus Manager 4.0 CD-ROM

Release Notes for Campus Manager 4.0 on Solaris

Release Notes for Campus Manager 4.0 on Windows

Device Fault Manager 2.0 (DFM)

The ability to monitor:

Device faults in real-time and determine the root cause by correlating device level fault conditions.

Cisco device-level fault correlation.

Fault history.

E-mail, SNMP trap and syslog notifications.

Device Fault Manager 2.0 CD-ROM

Release Notes for Device Fault Manager 2.0 on Solaris

Release Notes for Device Fault Manager 2.0 on Windows

Internetwork Performance Monitor 2.6 (IPM)

The ability to troubleshoot wide-area network response time and availability proactively.

You can do this by using the available device instrumentation (SAA agents).

Internetwork Performance Monitor 2.6 (IPM) CD-ROM

Release Notes for Internetwork Performance Monitor 2.6

Resource Manager Essentials 4.0 (RME)

The ability to manage:

Device inventory and audit changes.

Configuration files, software images and syslog analysis.

Filtering to help in life cycle management.

Resource Manager Essentials 4.0 CD-ROM

Release Notes for Resource Manager Essentials 4.0 on Solaris

Release Notes for Resource Manager Essentials 4.0 on Windows


Additional Information Online

Registered Cisco.com users can access the most current Device Package Updates, and Latest Adapters for 3rd party network management applications at the following locations:

Device Package Updates

For CiscoView at

http://www.cisco.com/cgi-bin/Software/CiscoView/cvresult.cgi?product_class=
All+Product+Types&product=All+Products&application=CiscoView+6.1

For Campus at

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

For DFM at

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

For RME at

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

Latest Adapters at

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

What's New

The following new features are added in this release of LAN Management Solution 2.5:

Applications share devices and credentials using a Device and Credential Repository, enabling common administration. Device and Credential Repository provides a central place for management of devices and their credentials that can used by the applications.

New licensing framework.

Enhanced security to support SNMPv3 authNoPriv—Provides packet level security, integrity protection, and replay protection, but would not encrypt the packets.

Granular role based access and ability to integrate with Cisco Secure Access Control Server (ACS).

Support for managing IPv6 functionality using SNMP over IPv4 transport, using dual stacks.

The following sections lists the features supported by each application.

1. CiscoWorks Common Services 3.0 contains the following new features:

The CiscoWorks Homepage—Provides launch points for CiscoWorks family of products and other resources. The HTML based CiscoWorks Homepage replaces the Java applet based Desktop.

Device and Credentials Repository—Enables sharing of devices and credentials enabling common administration. It provides a central place for management of devices and their credentials that different applications managing those devices can use.

Device CenterEnables device level trouble shooting by giving a quick snap shot summary for the device and the various tools, reports, and tasks that can be performed on a selected device.

GroupsProvides a mechanism for applications to create shared device groups. It provides grouping facility based on various attributes in Device and Credentials Repository.

Software CenterProvides a mechanism to download and deploy device packages and software patches.

Enhanced restore frameworkEnables Common Services and its applications to restore the backed up data from an earlier version.

New utilities for diagnosing problems with CiscoWorks server and managing log files.

2. CiscoView 6.1 contains the following new features:

HTML Client support for Netscape and Mozilla, and server support for Solaris.

Integration with a common Device and Credential Repository.

Integration with the common software center of CiscoWorks.

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

New Graphical User Interface (GUI) that been redesigned using Light Weight components for faster performance.

Redesigned GUI workflow that supports better scalability and higher performance.

Significant improvement in performance and scalability of the individual applications compared to prior versions of RME.

4. Campus Manager 4.0 contains the following new features:

Data CollectionYou can choose devices to be managed by Campus Manager from the devices in Device and Credential Repository, or through data collection filters (IP subnets or VTP domains).

Expanded support for VLAN and VTP, including PVLANs and VTPv3.

Support for MSTP/MISTP/PVST+.

Support for configuration of Ether Channels and Inter-VLAN routing.

Architectural changes for scalability and performance.

Support for Time-Domain Reflectometry (TDR) reports for Catalyst 6000 devices.

Non Java based user interface for User Tracking application and Campus Manager Administration.

5. Device Fault Manager 2.0 includes:

New Graphical User Interface (GUI) and GUI workflow - See Appendix C "How is DFM 2.0 Different from DFM 1.2?" in Installation Guides.

New notification MIB with more detail for indepth analysis.

Simplified notification services configuration.

SNMP, e-mail, and syslog notification.

Fault History integrated into DFM.

Supports the following security features:

SSL protocol between the client and the server.

SNMPv3 Protocol (authnopriv) between the server and the device.

Integration with Cisco Secure Access Control Server (ACS).

6. Internetwork Performance Monitor 2.6 includes:

Support for Differentiated Service Code Point (DSCP) support — In IPM 2.6 users are provided with the feature of selecting either the IP Precedence settings or DSCP setting.

Source interface on collector — In the earlier IPM releases, users could not specify a source interface configuration on an individual collector basis while configuring a collector. IPM 2.6 has features to overcome this limitation.

Improved Scalability—IPM 2.6 supports 2000 collectors.

Compliancy for SSL—IPM 2.6 is SSL compliant and enables secure HTTP communication between the client and server.

3 Server and Client System Requirements

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

Table 3 lists the server requirements for upgrading the LAN Management Solution 2.5 components on Solaris systems.

Table 4 lists the server requirements for upgrading the LAN Management Solution 2.5 components on Windows systems.

Table 5 lists the client system requirements for all platforms.

Table 6 lists the browser requirements for all platforms.

Table 7 lists the Solaris patches required and recommended for LAN Management Solution 2.5.

Table 8 lists the ports LAN Management Solution 2.5 uses.

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.

LAN Management Solution 2.5 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.

Table 3 Minimum Server Requirements for Solaris Systems

Component
Minimum Requirement

Hardware

Sun UltraSPARC IIIi with 1 GHz

CD-ROM drive

Color monitor with video card capable of 256 colors or more

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

Software

For UltraSPARC IIIi: Solaris 2.8 and 2.9

Available memory (RAM)

For UltraSPARC IIIi: 2 GB for restricted license and 4 GB for unrestricted license

Available disk space

For UltraSPARC IIIi (Workstation and Server): 80 GB

4 GB swap space for restricted license and 8 GB swap space for unrestricted license

UNIX file system recommended 1

We recommend that you set swap space to twice the size of RAM.

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


Table 4 Minimum Server Requirements for Windows Systems

Component
Minimum Requirement

Hardware

IBM PC-compatible computer with 1 GHz or Pentium III processor

Color monitor with video card capable of 256 colors or more

CD-ROM drive

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

Software for Windows

One of the following:

Windows 2000 Professional with Service Pack 41

Windows 2000 Server with Service Pack 4

Windows 2000 Advanced Server2 with Service Pack 4

Windows Server 2003 Standard and Enterprise Editions

Available memory (RAM)

2 GB for restricted license

4 GB for unrestricted license.

Available disk space

80 GB minimum

4 GB virtual memory for restricted license and 8 GB virtual memory for unrestricted license

NTFS file system3 required

We recommend that you set virtual memory to twice the size of RAM.

1 To verify the Service Pack version on Windows, select Start > Run, then enter winver.

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

3 Install LMS2.5 on an NTFS file system. Do not install LMS 2.5 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 5 Minimum Client Hardware and Software Requirements 

Component
Minimum Requirement

Hardware/software

Any one of these systems:

IBM PC-compatible system with at least a 300 MHz Pentium processor running Windows 2000 (Professional and Server) with Service Pack 3 or Service Pack 4 , Windows XP (SP1 and SP2), Windows Server 2003 (Standard and Enterprise Edition)

Sun UltraSPARC IIIi, running Solaris 2.8 or 2.9

Color monitor with video card set to 256 colors

Available disk space

One of the following:

For Solaris: 1 GB swap space

For Windows: 1 GB virtual memory

Available memory (RAM)

512 MB minimum

We recommend that you set virtual memory and swap space to twice the size of RAM.


Table 6 Browser Requirements 

Browser
JVM 1
Version
Platform

Internet Explorer (recommended)

5.0.0.3802 or later,

and

Java Plug-in version 1.4.2_042

6.0 SP1 (6.0.28) with patch Q810847

Any one of the following:

Windows 2000

Windows XP 3

6.0 (6.0.3790.0)

Windows Server 2003

Netscape Navigator

7.1

Any one of the following:

Windows 2000

Windows XP

Netscape Navigator (Downloaded from Sun site only)

7.0

Solaris 2.8 or 2.9

Mozilla

1.7.1

Windows

Mozilla

1.7

Solaris 2.8 or 2.9

1 Java Virtual Machine. A JVM running inside the browser is required to run IPM and Campus Manager. No other LMS applications require a JVM. In Internet Explorer, you can use either the Microsoft VM or the Java plug-in for the JVM. In Netscape Navigator you must use the Java plug-in for the JVM.

To verify the JVM version, open the Java console window by selecting View > Java Console (if using the Microsoft VM) or Tools > Sun Java Console (if using the Java plug-in) in Internet Explorer or Communicator > Tools > Server > Java Console in Netscape Navigator.

If Java Console is not listed in View menu, you must enable it. To enable the Java Console, in Internet Explorer, select Tools > Internet Options > Advanced > JVM > Java Console. Then restart Internet Explorer.

2 You can upgrade to Java Plug-in version 1.4.2_06 manually. See Installation Guide for IPM and Campus Manager for more details.

3 Windows XP professional is not packaged with JVM. JVM is installed after you install Windows XP.


Application Scaling Numbers

This section presents information on the specific scaling numbers for each of the CiscoWorks LMS applications. This helps you decide what server size and distribution would best suit your needs and optimize performance.

Below are the tested numbers for each application in standalone mode:

Common Services Device and Credential Repository (DCR)—Maximum of 50,000 devices and 100 user-defined groups

Resource Manager Essentials (RME)—5,000 devices

Campus Manager (CM)—5,000 devices and 100,000 end stations

Device Fault Manager (DFM)— 40,000 ports or interfaces with 6000 managed ports

Internetwork Performance Monitor (IPM)— 2,000 collectors

The supported concurrent users for LMS 2.5 are:

3 concurrent users for LMS 2.5 Restricted license with 2 GB RAM

20 concurrent users for LMS 2.5 Unrestricted license with 4 GB RAM

More number of concurrent users can affect system performance. Depending upon the size of the server, 20 simultaneous users is the maximum recommended.

Solaris Patches for LAN Management Solution

Table 7 lists the Solaris patches for the LAN Management Solution 2.5.


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


Table 7 Solaris Patches for LAN Management Solution 2.51

Operating System
Required
Recommended
 
Server
Client
Server
Client

Solaris 2.8

111327-05

110945-08

110934-16

110898-09

109326-14

108827-40

108528-29

111626-03

108652-81

108921-21

108940-62

110951-01

110662-02

110615-01

110286-02

110951-05

110662-12

110615-11

108964-06

Solaris 2.9

114224-01

113580-01

112839-04

112233-12

114006-01

112771-14

112661-06

113244-05

113326-01

112998-03

113713-14

112964-07

113575-05

112970-07

112808-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 8 LAN Management Solution Port Usage 

Protocol
Port Number
Service Name
Application(s)
Direction (of Establishment) of Connection

ICMP

-

Ping

RME, CM, and DFM

Server to Device

TCP

22

Secure Shell (SSH)

CiscoWorks Common Services and RME

Server to Device

TCP

23

Telnet

CiscoWorks Common Services, CiscoView, and RME

Server to Device

TCP

25

Simple Mail Transfer Protocol (SMTP)

RME

Server Internal

TCP

49

TACACS+ and ACS

CiscoWorks Common Services, RME, CM, and DFM

Server to ACS

TCP

80

HyperText Transfer Protocol (HTTP)

CiscoWorks Common Services, CiscoView

Client to Server

TCP

443

CiscoWorks HTTP server in SSL mode

CiscoWorks Common Services

Sever Internal

TCP

514

Remote Copy Protocol

CiscoWorks Common Services

Server to Device

TCP

514

rsh Daemon

RME

Server to Device

TCP

1683

Internet Inter-ORB Protocol (IIOP)

CiscoWorks Common Services, and CM

Client to Server

TCP

1684

IIOP

CiscoWorks Common Services, and CM

Server to Client

TCP

1741

CiscoWorks HTTP Protocol

CiscoWorks Common Services, CiscoView, and RME

Client to Server

TCP

1783

IIOP for IPM Gatekeeper

IPM

Client to Server

TCP

1784

IIOP for IPM Gatekeeper

IPM

Server to Client

TCP

8088

HIOP

CiscoWorks Common Services

Server to Client

Client to Server

TCP

9002

DynamID authentication (DFM Broker)

DFM

Client to Server

TCP

9007

Tomcat shutdown

CiscoWorks Common Services

Server Internal

TCP

9009

Ajp13 connector used by Tomcat

CiscoWorks Common Services

Server Internal

TCP

9088

HIOP port for

IPM gatekeeper

IPM

Server to Client

Client to Server

TCP

9191

HIOP port for IPM Gatekeeper

IPM

Server Internal

TCP

9192

IIOP port for IPM Gatekeeper

IPM

Server Internal

TCP

9193

IIOP port for IPM Gatekeeper

IPM

Server Internal

TCP

9194

HIOP port for IPM Gatekeeper

IPM

Server Internal

TCP

15000

Log server

DFM

Server Internal

TCP

40050-
40070

CSTM ports used by CS applications such as OGS, Device and Credential Repository (DCR)

CiscoWorks Common Services

Server Internal

TCP

40401

LicenseServer

CiscoWorks Common Services

Server Internal

TCP

42340

CiscoWorks Daemon Manager - Tool for Server Processes

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

43455

RME Database

RME

Server Internal

TCP

43443

ANIDbEngine

CM

Server Internal

TCP

43445

Fault History Database

DFM

Server Internal

TCP

43446

Inventory Service Database

DFM

Server Internal

TCP

43447

Event Promulgation Module Database

DFM

Server Internal

TCP

43500 -
43530

CSTM Port for DFM

DFM

Server Internal

TCP

44341

IPM Database

IPM

Server Internal

TCP

44342

IPM Name Server (OSAGENT)

IPM

Client to Server

TCP

47000-
47040

CSTM Port for RME

RME

Server Internal

TCP

55000 -
55020

CSTM Port for Campus Manager

CM

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 RME

Server to Device

Device to Server

UDP

161

Simple Network Management Protocol (SNMP)

CiscoWorks Common Services, CiscoView, RME, CM, and DFM

Server to Device

Device to Server

UDP

162

SNMP Traps (Standard Port)

CiscoWorks Common Services, and DFM

Server to Device Device to Server

UDP

514

Syslog

CiscoWorks Common Services and RME

Device to Server

UDP

9000

CSlistener (DFM server if port 162 is occupied)

DFM

Client to Server

UDP

14004

Lock port for ANI Server singlet on check

CM

Server Internal

UDP

16236

UT Host acquisition

CM

Device to Server

UDP

42342

OSAGENT

CiscoWorks Common Services and RME

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

UDP

42350

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

CiscoWorks Common Services

Server Internal


4 LMS Data Backup

This section describes:

Backing up LMS Data Manually From the Command Line

Backing up LMS Data Using the CiscoWorks Server

Automatic Data Backup During Common Services Installation

Backing up LMS Data Manually From the Command Line

You can use backup.pl to backup data for Common Services, RME, Campus, and DFM.

If BKP is the directory you chose to back up, the data will be stored as BKP/0, BKP/1, BKP/2, where BKP/0 stores the data of the 1st generation.

The syntax for using the script backup.pl on Solaris is:

$NMSROOT/bin/perl $NMSROOT/bin/backup.pl BackupDirectory LogFile Num_Generations

The syntax for using the script backup.pl on Windows is:

%NMSROOT%\bin\perl %NMSROOT%\bin\backup.pl BackupDirectory LogFile Num_Generations

Where,

BackupDirectory—Directory where you want to backup the data. Create this directory before you run the script.

LogFile—The file name for the backup log file.

Num_Generations—Number of backup generations to be kept in the backup directory.

Example:

$NMSROOT/bin/perl $NMSROOT/bin/backup.pl  /backup_dir logfile 2

Backing up LMS Data Using the CiscoWorks Server

To backup the LMS 2.2 data using the CiscoWorks server:


Step 1 Log in to the CiscoWorks.

Step 2 From the CiscoWorks desktop, select Server Configuration > Administration > Database Management > Back Up Data Now.

The Back Up Data Now dialog box appears.

Step 3 Enter the path and name for the backup directory.

We recommend that you use a different directory from the directory where CiscoWorks is located, for example, C:\backups.

Step 4 Click Finish to start the back up.


Automatic Data Backup During Common Services Installation

During an upgrade, the installation of the first Common Services CD included in the LMS 2.5 will force another backup and this will backup only RME, Campus, and DFM data. The IPM data is not backed up.

The installation will prompt the user for a backup directory. If the given backup directory is $DB_BKP, the Common Services installation process creates the following two subdirectory trees under this directory:

$DB_BKP/automaticbackup/cmfbackup

$DB_BKP/automaticbackup/mcbackup


Note If VMS applications are not installed on this server, the $DB_BKP/automaticbackup/mcbackup directory will be empty. While restoring the data, you have to specify $DB_BKP/automaticbackup/cmfbackup as the backup directory.


Backing up IPM Data

IPM data is not backed up while using the backup.pl script or automatic backup during an in-place upgrade. The IPM data must be backed up using RBackup.sh script on Solaris and rbackup.exe for Windows.

To backup data on Solaris:

Run RBackup.sh, from the IPM 2.6 CD-ROM root directory, on the machine on which IPM is installed. This stops all IPM servers that are running and takes a backup of the database, the seed files, the HTML reports, the environment variables, and the version information. This data is compressed and the ipmBackup.tar file is created in the IPM 2.4 or IPM 2.5 root directory.

To backup data on Windows:

Run rbackup.exe, from the IPM 2.6 CD-ROM root directory, on the machine on which IPM is installed. This stops all IPM servers that are running and takes a backup of the database, the seed files, HTML reports, and the environment variables. The data is backed up in the backup directory under the IPM 2.4 or IPM 2.5 root directory.

5 Upgrading Your Operating System

If your system does not meet the minimum requirements, please upgrade your operating system before proceeding.

See section 3 "Server and Client System Requirements" for the minimum operating system requirements for LMS 2.5.

6 Upgrade Installation Paths

You might already have the previous version of LMS installed. Review the information in Table 9 to determine what software is required for the LMS components to function properly.

Table 9 Recommended Installation Paths 

If you are installing CiscoWorks LAN Management Solution
(LMS) on a system that has...
Then do this

LMS 2.2 / LMS 1.3 Update 1

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

LMS 2.2

1. Upgrade to LMS 2.2 / LMS1.3 Update 1

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

LMS 2.0 or 2.1

1. Upgrade to LMS 2.2

2. Upgrade to LMS 2.2 / LMS1.3 Update 1

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



Note LMS 2.5 does not contain ACL Manager (ACLM). If the you have ACLM installed from a previous release of LMS, ACLM will get uninstalled during RME upgrade.


7 Upgrade Options

Table 10 describes the recommended sequence for upgrading individual LAN Management Solution 2.5 (LMS) component applications when prior versions of these applications are already installed on your system. We recommend that you install CiscoWorks LAN Management Solution 2.5 on a machine that has no other CiscoWorks solution components installed.

You can use either of these upgrade options:

In-place Upgrade—Install LMS 2.5 on the same machine as the existing LMS version and migrate existing data to LMS 2.5.

Remote Upgrade—Install LMS 2.5 on a different machine from the current LMS installation and migrate existing data to the new machine.

If you are using Remote Upgrade:

a. Install LMS 2.5 on a machine where you do not have any of the previous versions of LMS installed.

b. Copy the backed up data folder to this machine.

c. Follow the steps in Data Migration document to migrate the data to the new installation.


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


Table 10 Recommended Upgrade Sequence 

If the following components are already installed...
You should upgrade in the following order...

CiscoWorks Common Services 2.2

CiscoWorks Common Services 3.0
(Includes CiscoView 6.1)

CD One, 5th Edition

CiscoWorks Common Services 3.0
(Includes CiscoView 6.1)

CiscoWorks Common Services 2.2

Resource Manager Essentials 3.5

1. CiscoWorks Common Services 3.0 (Includes CiscoView 6.1)

2. Resource Manager Essentials 4.0

CD One, 5th Edition

Resource Manager Essentials 3.4

1. CiscoWorks Common Services 3.0 (Includes CiscoView 6.1)

2. Resource Manager Essentials 4.0

CiscoWorks Common Services 2.2

Resource Manager Essentials 3.5

Campus Manager 3.3

1. CiscoWorks Common Services 3.0 (Includes CiscoView 6.1)

2. Resource Manager Essentials 4.0

3. Campus Manager 4.0

CD One, 5th Edition

Resource Manager Essentials 3.4

Campus Manager 3.2

1. CiscoWorks Common Services 3.0 (Includes CiscoView 6.1)

2. Resource Manager Essentials 4.0

3. Campus Manager 4.0

CiscoWorks Common Services 2.2

Resource Manager Essentials 3.5

Device Fault Manager 1.2 Updated for Common Services 2.2

1. CiscoWorks Common Services 3.0 (Includes CiscoView 6.1)

2. Resource Manager Essentials 4.0

3. Device Fault Manager 2.0

CiscoWorks Common Services 2.2

Resource Manager Essentials 3.5

Device Fault Manager 1.2

1. CiscoWorks Common Services 3.0 (Includes CiscoView 6.1)

2. Resource Manager Essentials 4.0

3. Device Fault Manager 2.0

CD One, 5th Edition

Resource Manager Essentials 3.4

Device Fault Manager 1.2

1. CiscoWorks Common Services 3.0 (Includes CiscoView 6.1)

2. Resource Manager Essentials 4.0

3. Device Fault Manager 2.0

CiscoWorks Common Services 2.2

Internetwork Performance Monitor 2.5

1. CiscoWorks Common Services 3.0 (Includes CiscoView 6.1)

2. Resource Manager Essentials 4.0

3. Internetwork Performance Monitor 2.6

CD One, 5th Edition

Internetwork Performance Monitor 2.4

1. CiscoWorks Common Services 3.0 (Includes CiscoView 6.1)

2. Resource Manager Essentials 4.0

3. Internetwork Performance Monitor 2.6


8 Upgrading to LAN Management Solution 2.5

To upgrade an application, log in as root (on Solaris), or local administrator or user with administrator privileges (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.5. 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.

Stop all third party network management applications, such as HP OpenView, before installing the LAN Management Solution 2.5.

Be aware of the following:

You must upgrade CiscoWorks Common Services 3.0 before upgrading any other application.

After you have upgraded CiscoWorks Common Services 3.0, you must upgrade each LMS 2.5 application separately. While we strongly recommend that you follow the "Order of Upgrade" section, you can upgrade the other applications of LMS 2.5 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.5) during installation.

Prerequisites

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

Ensure you complete the following tasks before upgrade:


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

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

Step 3 Read the "Important Upgrade Notes" section.


Proof of Purchase

If you are providing an upgrade license file or PIN/PAK, LMS validates the upgrade installation by checking the existence of the license file of the previous version of the product.

If you are upgrading LMS in the same machine you have the previous versions installed, LMS checks for the previous version and validates the installation. If the validation fails, you will be prompted to run the utility validateupgrade from CLI after the installation.

If you are installing the product on a server other than where you have your previous version installed, the validation fails as it is a fresh installation on that machine. You will be prompted to run the validateupgrade utility from CLI after the installation.

The utility is located under: NMSROOT/bin.


Note For Solaris, the LD_LIBRARY_PATH needs to be set as NMSROOT/MDC/lib:NMSROOT/lib.


You can select any one of the following two options:

Validate from a CD (older version).

Validate from a remote server (older version).

Validate from a CD: If you have the previous version of the RME CD, then you can mount the CD to CDROM drive and provide the absolute path to the drive.

Validate from a remote server: If you have the previous version of RME installed and running in some other server, then this option can be selected. You must enter the following information:

The remote CiscoWorks server host name or the IP address.

The remote CiscoWorks server http or https port number.

The remote CiscoWorks server login name.

The remote CiscoWorks server login password.

The remote server will be contacted and the upgrade validation will be done.

To validate the license from a remote server, CiscoWorks should be running on the remote server. Also, the CiscoWorks login credentials can be any of the following user groups:

CiscoWorks System administrator

CiscoWorks Network administrator

CiscoWorks Network operator.

Important Upgrade Notes

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

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.

Applications not supported by CiscoWorks Common Services 3.0 are disabled during upgrade. RME 3.5 is uninstalled automatically after taking the backup. Applications dependent on RME such as ACLM are also uninstalled during the upgrade. For more information, see Installation and Setup Guide for Resource Manager Essentials 4.0.

You can do a local upgrade or a remote upgrade. You need to do a local upgrade on the system where you have the LMS application installed and a remote upgrade on a system where the application is not installed.

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

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.


Note We do not recommend ending the upgrade using Ctrl-C or by clicking Cancel. If you do this, you will required to manually cleanup the installation directories.


To ensure that you retain the latest device support and bug fixes for 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.

To ensure that you retain the latest device support and bug fixes for Resource Manager Essentials you must install the latest RME device package. For download location, see "Additional Information Online" section.

Install device packages after upgrading the application.

By default, SSL is not enabled on CiscoWorks Server.

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

For help with NMS integration, see the User Guide for CiscoWorks Integration Utility 1.6. You can find this document: On Cisco.com, in both HTML and PDF form.

http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/cw2000/cw2000_d/index.htm

Disable any popup blocker utility, installed on your client system.

Order of Upgrade

Upgrade each application of LMS 2.5 in the following order:


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

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

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

Step 4 Upgrade Device Fault Manager 2.0. See "Upgrading to Device Fault Manager 2.0" section.

Step 5 Upgrade Internetwork Performance Monitor 2.6. See "Upgrading to Internetwork Performance Monitor 2.6" section.


9 Upgrading to CiscoWorks Common Services 3.0

Upgrading CiscoWorks Common Services takes approximately 40 minutes.

Upgrading to CiscoWorks Common Services 3.0 on Solaris


Step 1 Locate Installation and Setup Guide for CiscoWorks Common Services (Includes CiscoView) 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.

http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/cw2000/cw2000_d/
index.htm

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

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.

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

a. Understanding the CiscoWorks Homepage. See Understanding the CiscoWorks Homepage.

b. Configuring the CiscoWorks server.

c. Configuring your client.

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

Step 6 Verify CiscoWorks Common Services installation by entering the command pdshow from /opt/CSCOpx/bin. The following services should be displayed:

ESS, EssMonitor, CmfDbEngine, CmfDbMonitor, DCRServer, CMFOGSServer, LicenseServer, Tomcat, Apache, RmeOrb, RmeGatekeeper, EDS, EDS-GCF, EDS-TR, jrm, diskWatcher, CSRegistryServer, TomcatMonitor, FDRewinder.


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 3.0 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 3.0 does not support directory encryption.

To install CiscoWorks Common Services 3.0 (CWCS) on Windows:


Step 1 Locate Installation and Setup Guide for CiscoWorks Common Services 3.0 (Includes CiscoView) 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.

http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/cw2000/cw2000_d/
index.htm

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 8 in this document.

Are not installing CiscoWorks and ACS on the same machine.

Do not install CiscoWorks and ACS on the same machine. This is because ACS mandates CiscoWorks to be configured as an AAA client in it for CiscoWorks to avail AAA service.

However, you cannot configure ACS as an AAA client, which is required when ACS and CiscoWorks coexists. Hence the configuration required for ACS integration will fail.

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

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

a. Understanding the CiscoWorks Homepage. See, Understanding the CiscoWorks Homepage.

b. Configuring CiscoWorks Server.

c. Configuring your client.

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

Step 6 Verify CiscoWorks Common Services installation by entering the command pdshow from DOS prompt. The following services should appear:

Tomcat, Apache, TomcatMonitor, RmeOrb, RmeGatekeeper, EDS, EDS-TR, Proxy, LicenseServer, ESS, EssMonitor, diskWatcher, CSRegistryServer, CmfDbEngine, CmfDbMonitor, DCRServer, CMFOGSServer, EDS-GCF, jrm.


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

10 Upgrading to Resource Manager Essentials 4.0

Upgrading to Resource Manager Essentials 4.0 takes approximately 30 minutes.

You can migrate the RME data from an older version of RME to a newer version. Migration from RME 3.4.x or RME 3.5.x is permitted (.x stands for the IDU upgrades). RME 3.4.x or RME 3.5.x backup data is essential for migration. You can migrate data from the same server or a different server.

Data migration across operating systems is not supported.

For more information on data migration, see "Data Migration from an earlier Version" in Chapter 1 in Installation and Setup Guide for Resource Manager Essentials 4.0.

Upgrading to Resource Manager Essentials 4.0 on Solaris


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

http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/cw2000/cw2000e/index.htm

Step 2 Follow the steps in the section "Data Migration From an Earlier Version", in Chapter 1.

We recommend that you change the RME database password and back up the database before upgrading.

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

Step 3 After you complete the migration, verify that RME was upgraded correctly as follows:

a. Access the CiscoWorks Homepage.

b. Select Common Services > HomePage > Application Registration.

The Application Registration Status page appears.

c. Check the Registered Applications table. RME should be listed.

Or

After you complete the installation, verify that the following processes are running using Common Services > Server > Admin > Processes:

RMEDbEngine, RMEDbMonitor, ConfigMgmtServer, NCTemplateMgr, RMEOGSServer, SyslogCollector, EssentialsDM, CTMJrmServer, ChangeAudit, ICServer, and SyslogAnalyzer.

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


If you receive any error messages during the upgrade, see Appendix D, "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 4.0. You can download the latest IDU from:

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

Upgrading to Resource Manager Essentials 4.0 on Windows


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

http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/cw2000/cw2000e/index.htm

Step 2 Follow the steps in the section "Data Migration From an Earlier Version", in Chapter 1.

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

If you are upgrading an evaluation version of RME 4.0, 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 RME was upgraded correctly as follows:

a. Access the CiscoWorks Home Page.

b. Select Common Services > HomePage > Application Registration.

The Application Registration Status page appears.

c. Check the Registered Applications table. Resource Manager Essentials should be listed.

Or

After you complete the installation, verify that the following processes are running using Common Services > Server > Admin > Processes:

RMEDbEngine, RMEDbMonitor, ConfigMgmtServer, NCTemplateMgr, RMEOGSServer, SyslogCollector, EssentialsDM, CTMJrmServer, ChangeAudit, ICServer, and SyslogAnalyzer.

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


If you receive any error messages during the upgrade, see Appendix C, "Troubleshooting the Installation".

To ensure that you retain the latest device support and bug fixes, please install the latest Incremental Device Update (IDU) for RME 4.0. You can download the latest IDU from:

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

11 Upgrading to Campus Manager 4.0

Upgrading Campus Manager takes approximately 11 minutes.

When you install Campus Manager 4.0, certain data from the previous database is converted to Campus Manager 4.0 format. This includes: seed devices, SNMP community strings, discovery schedule, User Tracking queries and layouts, Username and Notes fields in User Tracking, Path preferences, job schedule, and Topology groups.

Upgrading to Campus Manager 4.0 on Solaris


Step 1 Locate Installation and Setup Guide for Campus Manager 4.0 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.

http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/cw2000/camp_mgr/
index.htm

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

We recommend that you change the ANI database password and back up the database before upgrading.

Step 3 After you complete the installation, verify that Campus was installed correctly as follows:

a. Access the CiscoWorks Homepage.

b. Select Common Services > Homepage > Application Registration. The Application Registration Status page appears.

c. Check the Registered Applications table. Campus Manager should be listed.

Or

After you complete the installation, verify that Campus was installed correctly by accessing the CiscoWorks Server, logging in as administrator, and selecting Campus Manager > Administration > System Configuration.

After you install Campus Manager 4.0, choose one of the following:

If you have installed Campus Manager 4.0 on a different system and have data to import, import the database remotely. See the "Restoring Data After Installation" section in Chapter 2

If your data is already converted or you do not want to import the old data. 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".

After installation is complete, the installer re-applies some device updates previously released on Cisco's download site as Incremental Device Updates (IDU). IDU 9.0 has been incorporated in Campus 4.0.

To ensure that you retain the latest device support and bug fixes, install the latest Incremental Device Update (IDU) for Campus Manager 4.0. You can download the latest IDU from:

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

Upgrading to Campus Manager 4.0 on Windows


Step 1 Locate Installation and Setup Guide for Campus Manager 4.0 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.

http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/cw2000/camp_mgr/
index.htm

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 you complete the installation, verify that Campus was installed correctly as follows:

a. Access the CiscoWorks Homepage.

b. Select Common Services > Homepage > Application Registration.

The Application Registration Status page appears.

c. Check the Registered Applications table. Campus should be listed.

Or

After the installation, verify that Campus Manager was correctly installed by accessing the CiscoWorks Server, logging in as administrator, and selecting Campus Manager > Administration > System Configuration.

If your client does not have Java plug-in, you will receive a message asking if you want to install it. Campus Manager requires the plug-in for Topology Services, Path Analysis, Discrepancy Reports and VLAN Port Assignment. The plug-in is not required for User Tracking and Campus Manager Administration.

After you install Campus Manager 4.0, choose one of the following:

If you have installed Campus 4.0 on a different system and have data to import, import the database remotely. See the "Restoring Data After Installation" section in Chapter 2

If your data is already converted or you do not want to import the old data. 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".

After installation is complete, the installer re-applies some device updates previously released on Cisco's download site as Incremental Device Updates (IDU). IDU 9.0 has been incorporated in Campus 4.0.

You can download the latest IDU from:

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

12 Upgrading to Device Fault Manager 2.0

Upgrading Device Fault Manager takes approximately 10 minutes.


Note To install DFM, you will require a previous licensed copy of DFM. You can validate the license if you have a copy of the DFM CD or if you have DFM 1.2 installed locally or remotely. 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.


Table 11 lists the DFM 1.2.x data that is migrated in the following upgrade scenarios:

Local upgrade

Remote upgrade with upgrade kit—A remote upgrade as documented in the installation guides, but used along with scripts provided in the DFM 2.0 Upgrade Kit (which is available on Cisco.com)

Remote upgrade without upgrade kit—A remote upgrade as documented in the installation guides, without using the DFM 2.0 Upgrade Kit

Table 11 Data That is Migrated When Upgrading DFM 2.0

Data That is Migrated
Upgrade Type
Local Upgrade
Remote Upgrade
With Upgrade Kit
Without Upgrade Kit

Device list

X

X

X

Device managed state

X

X

-

Polling and threshold settings (for selected device groups; see installation guides for details)

X

X

-

E-mail notification information: recipient, sender ID, and SMTP address

X

-

-

SNMP Trap notification information: destination port and address

X

-

-


The DFM 2.0 Upgrade Kit provides an additional script that creates several DFM 1.2.x export files based on the DFM 1.2 DFM.rps (inventory) file. The standard migration script then uses the new export files to migrate the data listed in Table 11. Therefore, to use the DFM 2.0 Upgrade Kit, you must have a copy of the DFM.rps file from a DFM 1.2.x installation. See the Upgrade Kit Readme for more information on the DFM.rps file.

Although you can run the scripts provided in the DFM 2.0 Upgrade Kit at any time, you should run them when you perform the DFM upgrade. If you run the scripts at a later time, and the DFM migration data contains devices already in the DCR, the DFM migration data will overwrite the DCR information, and you may lose changes you made in the meantime.

The upgrade script and accompanying Readme files are available from the DFM download site:

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

Upgrading to Device Fault Manager 2.0 on Solaris


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

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

http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/cw2000/dfm/dfm20/install/
index.htm

Step 2 Follow the steps in the section "Upgrading to DFM 2.0", in Chapter 3.

You can do a local upgrade or a remote upgrade. You need to do a local upgrade on the system where DFM 1.2.x is installed and a remote upgrade on a system where DFM 1.2.x is not installed.

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

Step 3 After you complete the installation, verify that DFM was installed correctly as follows:

a. Access the CiscoWorks Homepage.

b. Select Common Services > Homepage > Application Registration. The Application Registration Status page appears.

c. Check the Registered Applications table. Device Fault Manager should be listed.

Or

After you complete the installation, verify that Device Fault Manager was installed correctly by verifying that the DfmServer process is running. To verify, log on to the CiscoWorks Homepage as the administrator and select Common Services > Server > Admin > Processes.


If you receive error messages during the installation, or cannot access the server, check the installation log at NMSROOT/var/tmp/ciscoinstall.log.

Upgrading to Device Fault Manager 2.0 on Windows


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

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

http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/cw2000/dfm/dfm20/install/
index.htm

Step 2 Follow the steps in the section "Upgrading to DFM 2.0", in Chapter 3.

You might need to do a local upgrade or a remote upgrade. You can do a local upgrade on the system where DFM 1.2.x is installed and a remote upgrade on a system where DFM 1.2.x is not installed.

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

Step 3 After you complete the installation, verify that DFM was installed correctly as follows:

a. Access the CiscoWorks Homepage.

b. Select Common Services > Homepage > Application Registration. The Application Registration Status page appears.

c. Check the Registered Applications table. Device Fault Manager should be listed.

Or

After you finish the installation, verify that Device Fault Manager was installed properly by verifying that the DfmServer process is running. To verify, log on to the CiscoWorks Homepage as the administrator and select Common Services > Server > Admin > Processes.


If you receive error messages during the installation, or cannot access the server, check the installation log at System Drive\CiscoWorks_Setupxxx.log.

13 Upgrading to Internetwork Performance Monitor 2.6

Upgrading to Internetwork Performance Monitor 2.6 takes approximately 20 minutes. The installation script installs Internetwork Performance Monitor in the following default locations:

On Solaris: /opt/CSCOipm, /opt/CSCOcwbS, and /opt/CSCOipmClient

On Windows: \\Program Files\Internetwork Performance Monitor

Before you begin:

You can take a backup of IPMDB.db, IPMDB.log, and ipm.env before you do an upgrade. Make sure that you back up these files after stopping IPM servers.

If there is a failure in the upgrade process or if you terminate the upgrade process, you cannot restore the old database.

Make sure you have installed all the required OS patches, Service packs, and Third party device drivers for the current operating system.

You can upgrade from IPM 2.4 and IPM 2.5. During upgrade, the IPM database, seed files from IPM 2.4 and IPM 2.5 are preserved. This data is backed up automatically as part of the installation process and then converted to the format used by IPM 2.6.

For more information on migration see, Chapter 3 "Upgrading to IPM Release 2.6" in Installation Guide For Internetwork Performance Monitor 2.6.

Upgrading to Internetwork Performance Monitor 2.6 on Solaris

Perform the following steps to upgrade Internetwork Performance Monitor:


Step 1 Locate Installation Guide For Internetwork Performance Monitor 2.6. The document is available:

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

From the CD's root directory, look for /docs/ipm26_install.pdf

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

http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/ipmcw2k/cipm26/install/
index.htm

Step 2 Read Chapter 2, "Preparing to Install IPM". As explained in that chapter, be sure that:

Your routers are running Cisco IOS software Release 11.2(18) or later, including the SA Agent feature. For help, see the section "Cisco IOS Software Requirements" in Chapter 2.

Your routers support SNMP and can send SA Agent traps. For help, see the section "Configuring Routers to Support SNMP and Send SA Agent-Related Traps" in Chapter 2.

You have administrator access to the server on which you plan to install Internetwork Performance Monitor.

You have verified that the ports that Internetwork Performance Monitor uses will not create conflicts with existing applications (see Table 8).

You know the location of the Netscape Communicator executable (if it is not in the default location). You will be prompted for this during installation.

Step 3 Follow the steps in the section "Installing IPM on Solaris", in Chapter 4.

We recommend that you select an Express install. Select another install option only if you want to specify a destination other than /opt/CSCOipm.

Step 4 After you complete the installation, verify that IPM was installed correctly as follows:

a. Access the CiscoWorks Homepage.

b. Select Common Services > Homepage > Application Registration. The Application Registration Status page appears.

c. Check the Registered Applications table. IPM should be listed.

Or

After you complete installing, verify that Internetwork Performance Monitor was correctly installed. To perform this task, follow the steps in the section "Verifying IPM Installation on Solaris" in Chapter 4.


Upgrading to Internetwork Performance Monitor 2.6 on Windows

Perform the following steps to upgrade Internetwork Performance Monitor:


Step 1 Locate Installation Guide For Internetwork Performance Monitor 2.6. The document is available:

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

From the CD's root directory, look for \\docs\ipm26_install.pdf.

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

http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/ipmcw2k/cipm26/install/
index.htm

Step 2 Read Chapter 2, "Preparing to Install IPM". As explained in that chapter, be sure that:

Your routers are running Cisco IOS software Release 11.2(18) or later, including the SA Agent feature. For help, see the section "Cisco IOS Software Requirements" in Chapter 2.

Your routers support SNMP and can send SA Agent traps. For help, see the section "Configuring Routers to Support SNMP and Send SA Agent-Related Traps" in Chapter 2.

You have administrator access to the server on which you plan to install Internetwork Performance Monitor.

You have verified that the ports that Internetwork Performance Monitor uses will not create conflicts with existing applications (see Table 8).

You know the location of the Netscape Communicator executable (if it is not in the default location). You will be prompted for this during installation.

Step 3 Follow the steps in Chapter 5, "Installing IPM on Windows".

Step 4 After you complete the installation, verify that IPM was installed correctly as follows:

a. Access the CiscoWorks Homepage.

b. Select Common Services > Homepage > Application Registration. The Application Registration Status page appears.

c. Check the Registered Applications table. Internetwork Performance Monitor should be listed.

Or

After you complete installing, verify that Internetwork Performance Monitor was correctly installed. To perform this task, follow the steps in the section "Verifying IPM Installation on Windows" in Chapter 5.


When you want to migrate IPM 2.4 or IPM 2.5 data from one machine to IPM 2.6 on another machine on the same network, you need to do a remote upgrade. When you do a remote upgrade, the existing IPM 2.6 data is overwritten.

To perform a remote upgrade on Windows, see section "Migrating Remote Data on Windows", in Chapter 3, "Upgrading to IPM Release 2.6" in Installation Guide.

To perform a remote upgrade on Solaris, see section "Migrating Remote Data on Solaris", in Chapter 3, "Upgrading to IPM Release 2.6" in Installation Guide.

14 Migrating LMS Data

For the latest information on data migration refer LMS 2.5 Data Migration Guidelines on Cisco.com. The document is available at: http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/cw2000/cw2000_b/lms/lms25/index.htm.

15 Getting Started with LMS

The topics in this section help you to work with and understand the LMS user interface.

Invoking the CiscoWorks Homepage

Enter the URL for your CiscoWorks Server in your browser.

http://server_name:port_number

where server_name is the name of the CiscoWorks Server and port_number is the TCP port used by the CiscoWorks Server. In normal mode (HTTP), the default TCP port for CiscoWorks Server is 1741. When SSL is enabled (HTTPS), the default TCP port for CiscoWorks Server is 443.

If you enter, http://server_name:port_number/login.html in your web browser, the CiscoWorks Server will not launch. Also, do not bookmark the URL with the with the trailing login.html.

On Windows, CiscoWorks Server always uses the default port numbers in secure and normal modes.

On Solaris, if the default TCP ports (1741 and 443) are used by other applications, you can select different ports for secure and normal modes during CiscoWorks Server installation. For more information, see Installation and Setup Guide for CiscoWorks Common Services on Solaris.

Logging In


Step 1 Enter the administrator username and password in the Login Manager dialog box:

User Name: admin
Password:  password

Step 2 Click Login.

The CiscoWorks Homepage appears.


Understanding the CiscoWorks Homepage

Figure 2 CiscoWorks Homepage with all the LMS Applications Installed

1

Common Services Panels. See, the "Common Services Panel" section.

4

Resources Panel. See, the "Resources Panel" section.

2

CiscoWorks Server Name.

5

CiscoWorks Tool Bar. See, the "Tool Bar Items" section.

3

Application Panel. See, the "Application Panel" section.

6

CiscoWorks Product Updates Panel. See, the "CiscoWorks Product Updates Panel" section.


Common Services Panel

The Common Services Panel displays all Common Services functions. The Common Services panel appears as a collapsible folder. You can view the first level items when the folder is opened.

Device Troubleshooting Panel

The Device Troubleshooting panel provides a launch point to the Device Center.

Device Center helps you to view device details, launch troubleshooting tools, perform management tasks, and view reports for the selected device. You can also change device credentials, update the inventory, and telnet a device.

For more information, see the "Using Device Center" chapter in the User Guide for CiscoWorks Common Services 3.0.

Application Panel

Each Application Panel in the CiscoWorks Homepage serves as a top-level launch point for all LMS applications installed on the local or remote server. Applications appear in the CiscoWorks Homepage in three columns. By default, only the first level items are displayed when you login. These first level items are in the collapsed mode. Lower level navigations are displayed only if you manually expand a first level item.

The title of each application panel displays the application name and it serves as a link to the relevant application home page. Application tasks are displayed in a hierarchical manner. When you select a task from the hierarchy, it launches the application Homepage in a new window.

If the corresponding application Homepage already exists for some other task, the window for this task is focused, instead of creating a new window.

Resources Panel

Resources panel is located at the top right corner of the CiscoWorks Homepage. It also serves as a top-level launch point for CiscoWorks resources, Cisco.com resources, third party application links, and web based custom tool links. This panel shows the types of resources at the first level and details in the next level.


Note CiscoWorks Homepage provides an admin user interface to turn off this information if you are behind the firewall or if you do not want this information to be displayed in the CiscoWorks Homepage.


CiscoWorks Product Updates Panel

CiscoWorks Product Updates panel is located at the lower right corner of the page. It displays informative messages about CiscoWorks product announcements, and help related topics. If you click the More Updates link, a popup window appears with all the Cisco Product Update details.

If the Common Services server is behind a firewall, the proxy settings are used to download messages from Cisco.com. CiscoWorks Homepage provides an Admin UI to accept the proxy settings. CiscoWorks Homepage alerts you if any urgent messages are found. By default, the polling interval is one minute. You can change the polling interval.

Tool Bar Items

Three buttons are available on top of the right hand side of the CiscoWorks Homepage:

Logout—Returns the browser to the Login dialog box.

Help—Displays the Online help in a separate browser window. See Using Online Help for details.

About—Displays the general information about the software. The window displays license information, version and patch level, installation date and copyright information.

16 Post-Upgrade Tasks

After you have upgraded the required applications and verified the installations, you must:


Step 1 Get updated device support and defect fixes by installing the latest version of Campus, RME, DFM and CiscoView device packages. See "Additional Information Online" section.

Step 2 Add devices into the system. You can add devices into the system using any of the following methods:

Automatic Discovery. See "Configuring Device Discovery Using Campus Manager" section.

Import from third party NMS. Select Common Services > Device and Credentials > Device Management > Bulk Import. The Import Devices dialog box appears. Enter all required data and options (such as Local NMS or Remote NMS), and click Import.

Add Device feature of Device and Credential Admin (DCA). See "Adding Devices Using the Device and Credential Admin" section.

Import From Flat File. See the bulk import section under Adding Devices Using the Device and Credential Admin.

Step 3 Manage Devices. Select Common Services > Device and Credentials > Device Management.

The Device Management option in DCA helps you manage the list of devices and their credentials. You can:

Add Devices

Delete Devices

Edit Device Credentials

Import Devices and Credentials

Export Devices and Credentials

Exclude Devices

View Devices List

Figure 3 Common Services Device Management Page

For more information, see Managing Devices Online help or the Managing Devices section in the Managing Device and Credentials chapter of the User Guide for CiscoWorks Common Services 3.0.

By default, DFM automatically synchronizes its managed inventory with the Device and Credential Repository (DCR). For more information, see the "Using Device Management" of the User Guide for Device Fault Manager 2.0. After adding devices to DCR, RME automatically adds the devices in DCR to RME.

Step 4 View, create, and manage Inventory jobs. Select Resource Manager Essentials > Devices > Inventory.

For more information, see the online help or see the "Using Inventory Management" chapter in the User Guide for Resource Manager Essentials 4.0.

Step 5 Configure DFM trap receiving.

For more information, see the online help or see the "Configuring and Administering DFM (Basic)" chapter in User Guide for Device Fault Manager 2.0.


Optional Steps

The following steps are optional:


Step 1 Enable Single Sign-On.

In a multi-server deployment of LMS, enable Single Sign-On to avoid separately signing on to each server. See "Enabling Single Sign-On" section.

Step 2 Configure the CiscoWorks Homepage to launch all applications from a single location. See "Configuring the CiscoWorks Homepage" section.

Step 3 Enable Browser Server-Security for a more secure browser to server connection. See "Enabling Browser-Server Security From the CiscoWorks Server" section.

Step 4 Enable ACS Mode. See "Using Applications in ACS Mode" section.

Step 5 Perform application level configuration tasks.

For Campus

a. Configure User Tracking acquisition actions. Select Campus Manager > User Tracking and click Acquisition > Actions. For more information, see the online help or see the "Using User Tracking Administration" chapter in the User Guide for Campus Manager 4.0.

b. Schedule data collection. Select Campus Manager > Administration. Click Admin and select Campus Data Collection > Schedule Data Collection. For more information, see the online help or "Scheduling Data Collection" chapter in the User Guide for Campus Manager 4.0.

For RME

a. Set up the transport protocol for Configuration Management. Select RME > Admin > Config Mgmt. For more information, see the online help or see "Using Archive Management" chapter in the User Guide for Resource Manager Essentials 4.0.

b. View, create, and manage Inventory jobs. Select RME > Devices > Inventory. For more information, see the online help or see "Using Inventory Management" chapter in the User Guide for Resource Manager Essentials 4.0.

For DFM

a. Configure SNMP trap forwarding. For more information, see the online help or see the "Configuring and Administering DFM (Basic)" chapter in the User Guide for Device Fault Manager 2.0.

b. Set up notifications. For more information, see the online help or see the "Using Notification Services" chapter in the User Guide for Device Fault Manager 2.0.

c. Adjust polling and threshold settings. For more information, see the online help or see the "Configuring Polling and Thresholds" chapter in User Guide for Device Fault Manager 2.0.

d. Adjust the rediscovery schedule and daily purging schedule. For more information, see the online help or see the "Configuring and Administering DFM (Basic)" chapter in User Guide for Device Fault Manager 2.0.

e. Add views to the Alerts and Activities Display. For more information, see the online help or see the "Configuring Views for the Alerts and Activities Display" chapter in User Guide for Device Fault Manager 2.0.

For IPM

a. Import devices from the Device Credentials Repository as source or targets. Select Internetwork Performance Monitor > Admin > Import From Device and Credential Repository.

The Import from Device and Credential Repository page appears.

b. Click Import Devices.

The Import from Devices screen appears.

c. Select the method of import as either Sources, Targets as SAA Responders or Targets as IP Devices.

Select Sources: To import the device that IPM can use for source routers.

Select Targets as SAA Responders: To import data from Inventory that IPM can use for SAA Responders target devices.

Select Targets as IP Devices: To import the device that IPM can use for IP target devices.

For more information see the online help or "Defining a Collector" section of the User Guide for Internetwork Performance Monitor 2.6.


Configuring Device Discovery Using Campus Manager

To configure Device Discovery:


Step 1 From CiscoWorks Homepage, select Campus Manager > Administration.

A new Campus Administration page appears.

Figure 4 Campus Manager Administration page

Step 2 Click Admin > Device Discovery > SNMP Settings.

The SNMP Settings page appears.

Step 3 Specify the community strings as required.

Step 4 Click Admin > Device Discovery > Discovery Settings.

The Discovery Settings page appears.

Step 5 Specify the Discovery options.

Step 6 Click Seed Devices > Configure.

The Configure Seed Devices dialog box appears. Seed devices are devices used to initiate network discovery.

Step 7 In the Seed Device field, click Browse to enter seed devices stored in a file.

The seed devices stored in the file have to be separated by a carriage return. That is, only one seed device can be stored per line in the file.

For example, the seed devices in the file can be entered as:

172.20.5.6
172.20.118.130
10.77.209.209
172.20.99.2
10.77.210.101
10.77.210.103

Step 8 (Optional) To limit discovery by IP addresses in your network, from the Discovery Settings page, click IP Address Range > Configure.

The IP Address Range settings screen appears. Specify IP Address Range settings as required.

If IP address range is not specified, Device Discovery will try to discover as many devices as it can, based on the community strings and connectivity.

For more information, see Configuring Device Discovery Online help or the "Using Device Discovery Administration" section in the "Administering Campus Manager" chapter of the User Guide for Campus Manager 4.0.


Adding Devices Using the Device and Credential Admin

The Device Management option in Device and Credential Admin (DCA) helps you manage the list of devices and their credentials. You can use this feature to add devices, device properties, and device credentials to DCA. You can also add devices to RME, Campus, DFM and IPM.

To add devices to the device list:


Step 1 In the CiscoWorks Homepage, select Common Services > Device and Credentials > Device Management.

The Device Management page appears.

The Device Management page helps you perform operations on Standard Devices, Cluster Managed devices and Auto Update devices. Operations on Auto Update Servers can be performed only at the Auto Update Server Management UI.

The Device Summary window displays the devices and groups in DCA.

Step 2 Click Add.

The Device Properties page appears. The Device Information dialog box provides three device management types:

Standard Type

Auto Update Type

Cluster Managed Type

For more information, see Adding Devices Online help or "Managing Devices" section of the User Guide for CiscoWorks Common Services 3.0.


To do a bulk import:


Step 1 In the CiscoWorks Homepage, select Common Services > Device and Credentials > Device Management.

The Device Management page appears.

Step 2 Click Bulk Import.

The Import Devices popup window appears.

Step 3 Select any one of the following from the drop-down list:

File

Local NMS (network management station)

Remote NMS—You should have permissions to log into the remote network management system (NMS), without a password. Common Services uses remote login to log into the Server and get device details. The rhosts file should be modified to enable you to login without a password.

For more information, see "Importing and Devices and Credentials" section of the User Guide for CiscoWorks Common Services 3.0.


Configuring Data Collection

You must configure Data Collection for Campus Manager to manage devices. You can configure data collection using the Campus Manager Administration module (select Campus Manager > Administration). Data collection configuration involves:

Viewing the summary of data collection settings—Navigate to the Campus Manager Administration module, select Campus Data Collection.

Scheduling data collection—Navigate to the Campus Manager Administration module, select Campus Data Collection > Schedule Data Collection.

Specifying data collection filters—Navigate to the Campus Manager Administration module, select Campus Data Collection > Data Collection Filters.

Specifying the data collection debugging options—Navigate to the Campus Manager Administration module, select Campus Data Collection > Debugging Options.

For more information, see the Online help or the "Using ANI Data Collection Administration" section in the "Administering Campus Manager" chapter of the User Guide for Campus Manager 4.0.

Enabling Single Sign-On

With Single Sign-On (SSO), you can use your browser session to transparently navigate to multiple CiscoWorks Servers without having to authenticate to each of them. Communication between multiple CiscoWorks Servers is enabled by a trust relationship using self-signed certificates and passwords shared between servers.

You must do the following tasks, initially:


Step 1 Designate one of the CiscoWorks Server as the SSO authentication server (Master) and other CiscoWorks Servers as SSO Regular servers (Slaves).

Figure 5 Common Services Security Settings Page

Step 2 Ensure that the System Identity User for all the CiscoWorks Servers is the same and the password is the same.

To verify that the same username is used, for each server, select Common Services > Server > Security > Multi-Server Trust Management > System Identity Setup and verify the System Identity Setup screen.

To ensure that you use the same system identity user and password, while installing Common Services on each server, use the default username for the administrative user and enter the same password. For more information, see "Setting Up System Identity User" Online help.

Step 3 Set up a trust relationship among the Master and Slave servers. To do this:

a. Select Common Services > Server > Security > Multi-Server Trust Management > Peer Server Certificate Setup from the Master.

The Peer Server Certificate screen appears.

b. Click Add.

A popup dialog box appears.

c. For each Slave server, enter the Slave server name and click OK.

The certificate details of the imported certificate appear in the Peer Server Certificate page. For more information, see "Creating Self Signed Certificates" Online help.

Step 4 Set up a trust relationship between each Slave and the Master server. To do this:

a. Select Common Services > Server > Security > Multi-Server Trust Management > Peer Server Certificate Setup from the Slave.

The Peer Server Certificate screen appears.

b. Click Add.

A popup dialog box appears.

c. Enter the Master server name and click OK.

The certificate details for the Master should appear in the Peer Server Certificate screen of each Slave.

Step 5 Set up the designated Master as the SSO Authentication server. To do this:

a. Select Common Services > Server > Security > Single Sign-On Setup.

The Single Sign-On Setup page appears.

b. Select the Master (SSO Authentication Server) radio button.

c. Click Apply.

Step 6 Set up all other CiscoWorks Servers as SSO Regular servers. To do this:

a. Select Common Services > Server > Security > Single Sign-On Setup.

The Single Sign-On Setup screen appears.

b. From the Single Sign-On Setup screen of each SSO Regular Server, select the Slave (SSO Regular Server) radio button.

c. Enter the server name of the machine designated as Master and the port (443).

d. Click Apply.


If the server is either configured as Master or Slave, you must:

Configure the System Identity user and password in both Master and Slave. The System Identity user name and password you specify in Master and Slave should be the same. See, "Setting Up System Identity User" section.

Configure Master's Self Signed Certificate in Slave. See, "Configuring Master Self Signed Certificate" section.

Setting Up System Identity User

System Identity setup helps you to create a trust user on servers that are part of a Multi-Server setup. This user enables communication between servers part of a Domain. There can only be one System Identity User for each machine.

The System Identity User you configure has to be a Peer Server User. In Non-ACS mode, the System Identity User you create has to be a Local User, with System Administrator privileges. In ACS mode, the System Identity user needs to be configured in ACS, with all the privileges the user has on CiscoWorks Server.

In non-ACS mode, the default user admin is also the system identity user. But in ACS mode, you need to add the system identity user to the ACS server. You can configure the admin user as the default System Identity User during the CiscoWorks installation.

Single Sign-On uses System Identity user password as the secret key to provide confidentiality and authenticity between Master and Slave. It is sufficient to have the same System Identity user passwords in Master and Slave, without having the same user name. We recommend that you have the same user name and password across Master and Slave.

To set up System Identity user:


Step 1 Select Common Services > Server > Security > System Identity Setup.

Step 2 Enter the username and password.

Step 3 Click Apply.


Configuring Master Self Signed Certificate

To configure Master's Self Signed Certificate in the Slave, select Common Services > Server > Security > Peer Server Certificate Setup > Add.

The common name (CN) in the certificate must be identical to the Master server name to be considered a valid certificate.

Configuring the CiscoWorks Homepage

CiscoWorks Homepage is the primary user interface and the launch point for all features. After you log in to Common Services, the default CiscoWorks Homepage appears.

The Application Registration, Link Registration, and Settings links under Homepage help you configure your CiscoWorks Homepage. They help you in:

Registering Applications With CiscoWorks Homepage: You can register CiscoWorks applications on local or remote servers.

To register your application with CiscoWorks Homepage:

From the CiscoWorks Homepage, select Common Services > Homepage > Application Registration.

Figure 6 Common Services Application Registration Status Page

Registering Links With CiscoWorks Homepage: You can add additional links to the CiscoWorks Homepage for Custom tools and home grown tools, and third party applications such as HP OpenView. The links will appear in the list of third party or custom tools.

To register your links with CiscoWorks Homepage:

From the CiscoWorks Homepage, select Common Services > Homepage > Link Registration.

Setting Up CiscoWorks Homepage: You can configure or change the CiscoWorks Homepage settings.

To set up CiscoWorks Homepage:

From the CiscoWorks Homepage, select Common Services > Homepage > Settings.

For more information on Homepage configuration, see the Online help or Chapter 2, "Interacting with CiscoWorks Homepage", in User Guide for CiscoWorks Common Services 3.0.

Using Applications in ACS Mode

By default, CiscoWorks Common Services uses CiscoWorks Server authentication (CiscoWorks Local) to authenticate users, and authorize them to access CiscoWorks Common Services applications.

After authentication, your authorization is based on the privileges that have been assigned to you. A privilege is a task or an operation defined within the application. The set of privileges assigned to you defines your role, and dictates the extent and type of system access you have.

You can use the Cisco Secure Access Control Server (ACS) services to add new users, using a source of authentication other than the native CiscoWorks Server mechanism (that is, the CiscoWorks Local login module).

CiscoSecure ACS provides authentication, authorization, and accounting services to network devices that function as AAA clients. CiscoSecure ACS uses the TACACS+ and RADIUS protocols to provide AAA services that ensure a secure environment.

In ACS mode, you can create custom roles so that you can customize Common Services client applications to suit your business workflow and needs. That is, you can create a user, and assign the user with a set of privileges, that would suit your needs.

System Identity User in ACS Mode: There can only be one System Identity User per machine. The System Identity User you configure has to be a Peer Server User. In ACS mode, the System Identity user needs to be configured in ACS, with all the privileges the user has in CiscoWorks.

Configuring ACS

Configure ACS after all applications are installed. If you have installed an application after configuring the CiscoWorks Login Module to the TACACS+ mode, then the users of that application are not granted any permissions. However, the application is registered to Cisco Secure ACS.

Multiple instances of same application using the same ACS server will share settings. Any changes will affect all instances of that application.

If an application is configured with ACS and then the application is reinstalled, the application will inherit the old settings.

You can create new roles using ACS. The role you create is not shared across all the LMS applications. The role is shared across the same application in different CiscoWorks Servers registered to that particular ACS. You have to create new roles for each of the LMS applications that are running on the CiscoWorks Server.

For example: Assume you have configured 10 CiscoWorks Servers with an ACS server and you have created a role in RME (say, RMESU). This role is shared for the RME application that runs on all 10 CiscoWorks Servers.

Registering Applications to the ACS

To register or re-register all the installed applications to the ACS:


Step 1 In the CiscoWorks Homepage, select Common Services > Server > Security > AAA Mode Setup.

The AAA Mode Setup page appears with the AAA Mode Setup dialog box.

Step 2 Select the ACS radio button.

Step 3 In the Server details panel, enter:

Primary IP Address/Hostname

Secondary IP Address/Hostname

Tertiary IP Address/Hostname

and the corresponding ACS TACACS+ port numbers.

The default port is 49. Secondary and Tertiary IP address/hostname details are optional.

The values true and false will not be accepted in the Primary, Secondary, and Tertiary IP Address/Hostname fields.

Step 4 In the login panel, enter:

ACS Admin Name

ACS Admin Password

ACS Shared Secret Key

Step 5 Re-enter the ACS admin password, and ACS shared secret key in the Verify fields. The values true and false will not be accepted in the above fields.

Step 6 Select the Register all installed applications with ACS to register all the installed application with the ACS server.

If an application is already registered with ACS, the current registration will overwrite the previous one.

Step 7 Click Apply.

Step 8 Restart the Daemon Manager:

On Windows:

a. Enter net stop crmdmgtd

b. Enter net start crmdmgtd

On Solaris:

a. Enter /etc/init.d/dmgtd stop

b. Enter /etc/init.d/dmgtd start


You must enable ACS communication on HTTPS if ACS is in HTTPS mode. To enable ACS communication, select the Connect to ACS in HTTPS mode check box in the Login Module dialog box. For more information, see User Guide for Cisco Secure ACS. You can find the document at http://www.cisco.com/univercd/cc/td/doc/product/access/acs_soft/csacs4nt/acs33/user/index.htm.

Enabling Browser-Server Security From the CiscoWorks Server

To enable Browser-Server Security:


Step 1 From the CiscoWorks Homepage, select Common Services > Server > Security > Browser-Server Security Mode Setup.

The Browser-Server Security Mode Setup dialog box appears.

Step 2 Select the Enable check box.

Step 3 Click Apply.

Step 4 Log out from your CiscoWorks session, and close all browser sessions.

Step 5 Restart the Daemon Manager from the CiscoWorks Server CLI:

On Windows:

a. Enter net stop crmdmgtd

b. Enter net start crmdmgtd

On Solaris:

a. Enter /etc/init.d/dmgtd stop

b. Enter /etc/init.d/dmgtd start

Step 6 Restart the browser, and the CiscoWorks session.

When you restart the CiscoWorks session after enabling SSL, you must enter the URL with the following changes:

The URL should begin with https instead of http to indicate secure connection. CiscoWorks will automatically redirect you to HTTPS mode if SSL is enabled.

Change the port number suffix from 1741 to 443.

If you do not make the above changes, CiscoWorks Server will automatically redirect you to HTTPS mode with port number 443. The port numbers mentioned above are applicable for CiscoWorks Server running on Windows.

On Solaris, if the default port (1741) is used by another application, you can select a different port during CiscoWorks Server installation. For details, see Installation and Setup Guide for CiscoWorks Common Services 3.0 (Includes CiscoView) on Solaris.


Uninstalling LMS

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

You need to uninstall all applications dependent on CiscoWorks before uninstalling CiscoWorks Common Services 3.0.

17 Where to Go Next

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

User Guide for CiscoWorks Common Services 3.0

Using CiscoView 6.1

User Guide for Campus Manager 4.0

User Guide for Device Fault Manager 2.0

User Guide for Internetwork Performance Monitor 2.6

User Guide for Resource Manager Essentials 4.0

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. Enter the URL, http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/cw2000/index.htm

b. Select the appropriate application.

c. Select appropriate application version.

d. Select User Guide.

From the CiscoWorks Online help:

a. From the CiscoWorks Homepage, click Help.

b. Select the appropriate LMS application.

18 Related Documentation


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


For information about installing, troubleshooting, and using the components in the LAN Management Solution, see the sources of information described in Table 12.


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 enter the URL, http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/cw2000/index.htm.


Table 12 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 3.0 (Includes CiscoView 6.1) on Solaris

Release Notes for CiscoWorks Common Services 3.0 (Includes CiscoView 6.1) on Windows

Release Notes for Campus Manager 4.0 on Solaris

Release Notes for Campus Manager 4.0 on Windows

Release Notes for Device Fault Manager 2.0 on Windows

Yes

Yes

Yes

Yes (PDF, HTML)

No

The known product bugs (DDTS)

Release Notes for Device Fault Manager 2.0 on Solaris

Release Notes for Internetwork Performance Monitor 2.6

Release Notes for Resource Manager Essentials 4.0 on Solaris

Release Notes for Resource Manager Essentials 4.0 on Windows

         

Performing a typical or custom installation

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

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

Installation and Setup Guide for Resource Manager Essentials 4.0 on Solaris (DOC-7816504=)

Installation and Setup Guide for Resource Manager Essentials 4.0 on Windows (DOC-7816505=)

No

Yes

Yes

Yes (PDF, HTML)

No

Performing a typical or custom installation

(continued)

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

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

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

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

Installation Guide for Internetwork Performance Monitor 2.6 (DOC-7816653=)

No

Yes

Yes

Yes (PDF, HTML)

No

Features, tasks, and troubleshooting

User Guide for CiscoWorks Common Services 3.0 (DOC-7816571=)

Using CiscoView 6.1 (DOC-7815605=)

User Guide for Campus Manager 4.0 (DOC-7816398=)

User Guide for Resource Manager Essentials 4.0 (DOC-7816503=)

No

Yes

Yes2

Yes

Yes

Features, tasks, and troubleshooting

(continued)

User Guide For Device Fault Manager 2.0 (DOC-7816266=)

User Guide for Internetwork Performance Monitor 2.6 (Doc-7816652=)

No

Yes

Yes

Yes

Yes

Device Support

Supported Device Table for Resource Manager Essentials 4.03

Supported Device Table for Campus Manager 4.04

Supported Devices Table for Device Fault Manager 2.05

No

No

Yes

No

No

Integration with third party NMS

User Guide for CiscoWorks Integration Utility 1.6

No

No

Yes

No

No

1 Provided as PDF in Documentation folder.

2 From the CiscoWorks Homepage, click Help.

3 To view the documents on Cisco.com, log on to your Cisco.com home page, then enter the URL: http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/cw2000/cw2000e/index.htm

4 To view the documents on Cisco.com, log on to your Cisco.com home page, then enter the URL: http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/cw2000/camp_mgr/index.htm

5 To view the documents on Cisco.com, log on to your Cisco.com home page, then enter the URL: http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/cw2000/dfm/dev_sup/dfm2_0.htm


19 Obtaining Documentation

Cisco documentation and additional literature are available on Cisco.com. Cisco also provides several ways to obtain 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 at this URL:

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

You can access the Cisco website at this URL:

http://www.cisco.com

You can access international Cisco websites at this URL:

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

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 Ordering tool:

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 1 800 553-NETS (6387).

20 Documentation Feedback

You can send 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.

21 Obtaining Technical Assistance

For all customers, partners, resellers, and distributors who hold valid Cisco service contracts, Cisco Technical Support provides 24-hour-a-day, award-winning technical assistance. The Cisco Technical Support Website on Cisco.com features extensive online support resources. In addition, Cisco Technical Assistance Center (TAC) engineers provide telephone support. If you do not hold a valid Cisco service contract, contact your reseller.

Cisco Technical Support Website

The Cisco Technical Support Website provides online documents and tools for troubleshooting and resolving technical issues with Cisco products and technologies. The website is available 24 hours a day, 365 days a year, at this URL:

http://www.cisco.com/techsupport

Access to all tools on the Cisco Technical Support Website requires a Cisco.com user ID and password. If you have a valid service contract but do not have a user ID or password, you can register at this URL:

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


Note Use the Cisco Product Identification (CPI) tool to locate your product serial number before submitting a web or phone request for service. You can access the CPI tool from the Cisco Technical Support Website by clicking the Tools & Resources link under Documentation & Tools. Choose Cisco Product Identification Tool from the Alphabetical Index drop-down list, or click the Cisco Product Identification Tool link under Alerts & RMAs. The CPI tool offers three search options: by product ID or model name; by tree view; or for certain products, by copying and pasting show command output. Search results show an illustration of your product with the serial number label location highlighted. Locate the serial number label on your product and record the information before placing a service call.


Submitting a Service Request

Using the online TAC Service Request Tool is the fastest way to open S3 and S4 service requests. (S3 and S4 service requests are those in which your network is minimally impaired or for which you require product information.) After you describe your situation, the TAC Service Request Tool provides recommended solutions. If your issue is not resolved using the recommended resources, your service request is assigned to a Cisco TAC engineer. The TAC Service Request Tool is located at this URL:

http://www.cisco.com/techsupport/servicerequest

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

To open a service request 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 list of Cisco TAC contacts, go to this URL:

http://www.cisco.com/techsupport/contacts

Definitions of Service Request Severity

To ensure that all service requests are reported in a standard format, Cisco has established severity definitions.

Severity 1 (S1)—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.

Severity 2 (S2)—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.

Severity 3 (S3)—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.

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

22 Obtaining Additional Publications and Information

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

Cisco Marketplace provides a variety of Cisco books, reference guides, and logo merchandise. Visit Cisco Marketplace, the company store, at this URL:

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

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://cisco.com/univercd/cc/td/doc/pcat/

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

http://www.ciscopress.com

Packet magazine is the Cisco Systems technical user magazine for maximizing Internet and networking investments. Each quarter, Packet delivers coverage of the latest industry trends, technology breakthroughs, and Cisco products and solutions, as well as network deployment and troubleshooting tips, configuration examples, customer case studies, certification and training information, and links to scores of in-depth online resources. You can access Packet magazine at this URL:

http://www.cisco.com/packet

iQ Magazine is the quarterly publication from Cisco Systems designed to help growing companies learn how they can use technology to increase revenue, streamline their business, and expand services. The publication identifies the challenges facing these companies and the technologies to help solve them, using real-world case studies and business strategies to help readers make sound technology investment decisions. 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/ipj

World-class networking training is available from Cisco. You can view current offerings at this URL:

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