Guest

CiscoWorks LAN Management Solution 3.2 and earlier

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

  • Viewing Options

  • PDF (1.1 MB)
  • Feedback
Quick Start Guide for LAN Management Solution 2.5.1 (Maintenance Kit)

Table Of Contents

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

SUPPLEMENTAL LICENSE AGREEMENT

LAN Management Solutions 2.5.1 Overview

Licensing Your Product

Getting the Licensing Terms

Installing the Licensing File

LMS Package Contents

Additional Package Information

What's New

Server and Client System Requirements

Solaris Patches for LAN Management Solution

LAN Management Solution Port Usage

Required LAN Management Protocols

Migrating from LMS and RWAN to LMS 2.5.1

Installing LAN Management Solution 2.5.1

Installing LMS 2.5.1 on Solaris

Installing CiscoWorks Common Services 3.0.3 on Solaris

Installing Resource Manager Essentials 4.0.3 on Solaris

Installing Campus Manager 4.0.3 on Solaris

Installing Device Fault Manager 2.0.3 on Solaris

Installing Internetwork Performance Monitor 2.6 on Solaris

Installing LMS 2.5.1 on Windows

Installing CiscoWorks Common Services 3.0.3 on Windows

Installing Resource Manager Essentials 4.0.3 on Windows

Installing Campus Manager 4.0.3 on Windows

Installing Device Fault Manager 2.0.3 on Windows

Installing Internetwork Performance Monitor 2.6 on Windows

Verifying the Installation

Upgrading from LMS and RWAN to LMS 2.5.1

Upgrade from LMS 2.5 to LMS 2.5.1

Local Upgrade from LMS 2.5 to LMS 2.5.1 on Solaris

Remote Upgrade from LMS 2.5 to LMS 2.5.1 on Solaris

Local Upgrade from LMS 2.5 to LMS 2.5.1 on Windows

Remote Upgrade from LMS 2.5 to LMS 2.5.1 on Windows

Validating the Upgrade License

Validate the Upgrade License for RME on Solaris

Validating the Upgrade License for DFM on Solaris

Validate the Upgrade License for RME on Windows

Validating the Upgrade License for DFM on Windows

Getting Started with CiscoWorks LMS

Changes from LMS 2.1 or LMS 2.2 to LMS 2.5.1

Invoking the CiscoWorks Homepage

Logging In

Understanding the CiscoWorks Homepage

Common Services Panel

Application Panel

Resources Panel

CiscoWorks Product Updates Panel

Tool Bar Items

Configuring LMS Administration Parameters

Managing Devices in CiscoWorks Server

Adding Devices to DCR Using Campus Manager Device Discovery

Adding Devices to DCR Using Common Services Device and Credential Admin

Adding Devices to IPM

Editing Device Credentials

Performing Maintenance on Your CiscoWorks Server

Performing Regular Backups

Purging the Data

Maintaining the Log Files

Launching LMS Applications Online Help

Using Applications in ACS Mode

Configuring ACS

Integrating and Registering LMS Applications to the ACS

Uninstalling LMS

Frequently Asked Questions

Related Documentation

Obtaining Documentation

Cisco.com

Product Documentation DVD

Ordering Documentation

Documentation Feedback

Cisco Product Security Overview

Reporting Security Problems in Cisco Products

Obtaining Technical Assistance

Cisco Technical Support & Documentation Website

Submitting a Service Request

Definitions of Service Request Severity

Obtaining Additional Publications and Information


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


This document contains information for CiscoWorks LMS 2.x Maintenance customers. It includes:

SUPPLEMENTAL LICENSE AGREEMENT

LAN Management Solutions 2.5.1 Overview

LMS Package Contents

Server and Client System Requirements

Migrating from LMS and RWAN to LMS 2.5.1

Installing LAN Management Solution 2.5.1

Upgrading from LMS and RWAN to LMS 2.5.1

Validating the Upgrade License

Getting Started with CiscoWorks LMS

Frequently Asked Questions

Related Documentation

Obtaining Documentation

Documentation Feedback

Cisco Product Security Overview

Obtaining Technical Assistance

Obtaining Additional Publications and Information

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.

LAN Management Solutions 2.5.1 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 a few applications such as, browser settings, Solaris patches, etc. See the "Server and Client System Requirements" section for details.

You can select any one of the following two licenses of LMS 2.5.1:

Enterprise Restricted: Limits you to manage 300 devices.

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

However, the number of devices that can be managed in a single server depends on your server configuration. See "Application Scaling Numbers" section for details.

This document contains information for CiscoWorks LMS 2.x Maintenance customers. 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.

Frequently asked questions.

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

If you are installing LMS 2.5.1 applications for the first time, follow the procedure as described in Quick Start Guide for LAN Management Solution 2.5.1

You can find this documents at this URL:

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

Licensing Your Product

The LMS 2.5.1 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.

Getting the 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 you enter only a PIN, LMS runs 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 when you install the product.

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

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 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 must enter 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.3 (see "Server and Client System Requirements" section). You are not 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.3, Campus 4.0.3, DFM 2.0.3 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 for each 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 that you instal later on that server do 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 are 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 stops functioning after 90 days. The evaluation period cannot 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. You can license the product using the PAK and PIN provided with the product. For details see, "Installing the Licensing File" section.

Installing the Licensing File

We recommend that before installing the LMS 2.5.1 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.3, 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 before installation:

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

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

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

The License Administration page appears.

2. Click Update.

A file browser dialog box appears.

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

4. 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 using this Maintenance Kit CD (for CiscoWorks LAN Management Solution 2.5.1) and you are upgrading from LMS (1.2, 1.3, 2.1, or 2.2) or RWAN (1.2 or 1.3) you may be asked to validate your LMS application images after completing the installation. See "Validating the Upgrade License" section for details.


Additional Information for LMS 2.5.1 Large Enterprise Unrestricted Licensing

Users of LMS 2.5.1 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, Release 2.5.1 for Solaris and Windows.

Table 2 LAN Management Solution Contents 

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

CiscoWorks Common Services 3.0.3 (Includes CiscoView 6.1.2)

Common software and services for LMS.

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

CiscoView 6.1.2 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.3 Includes CiscoView 6.1.2 CD-ROM

Release Notes for CiscoWorks Common Services 3.0.3 (Includes CiscoView 6.1.2) on Solaris

Release Notes for CiscoWorks Common Services 3.0.3 (Includes CiscoView 6.1.2) on Windows

Resource Manager Essentials 4.0.3 (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.3 CD-ROM

Release Notes for Resource Manager Essentials 4.0.3 on Solaris

Release Notes for Resource Manager Essentials 4.0.3 on Windows

Campus Manager 4.0.3 (CM)

Campus Manager is sometimes referred to as Campus.

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.3 CD-ROM

Release Notes for Campus Manager 4.0.3 on Solaris

Release Notes for Campus Manager 4.0.3 on Windows

Device Fault Manager 2.0.3 (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.3 CD-ROM

Release Notes for Device Fault Manager 2.0.3 on Solaris

Release Notes for Device Fault Manager 2.0.3 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


Additional Package Information

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

Bug fixes for IPM at

http://www.cisco.com/cgi-bin/tablebuild.pl/ipm-sol

Latest Adapters at

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

nmidb at

On Internet Explorer:

http://ftp.cisco.com/cisco/netmgmt/ciscoview/5.0/packages/
nmidb.
X.zip

On Netscape:

ftp://userid@ftp.cisco.com/cisco/netmgmt/ciscoview/5.0/packages/
nmidb.
X.zip

Where, userid is the Cisco.com user ID and X is the latest nmidb version (for example, 1.0.086).

What's New

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

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.

CiscoWorks Common Services 3.0.3 New Features

The CiscoWorks Common Services 3.0.3 provides 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.

CiscoView 6.1.2 New Features

The CiscoView 6.1.2. provides 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.

Support for Mini-RMON Management

Resource Manager Essentials 4.0.3 New Features

The Resource Manager Essentials 4.0.3 provides 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.

Support for SSHv2.

Campus Manager 4.0.3 New Features

The Campus Manager 4.0.3 provides the following new features:

Support for VTPv3 and Private VLAN configuration.

Support for MSTP/PVST+.

Support for configuration of EtherChannels, Trunk, and InterVLAN routing.

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

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

Support for IPv6.

Support for Simple Network Management Protocol Version 3 (SNMPv3).

Device Fault Manager 2.0.3 New Features

The Device Fault Manager 2.0.3 provides the following new features:

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

Internetwork Performance Monitor 2.6

The Internetwork Performance Monitor 2.6 provides the following new features:

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.

Server and Client System Requirements

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

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

Table 4 lists the server requirements for upgrading the LAN Management Solution 2.5.1 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.1.

Table 8 lists the ports LAN Management Solution 2.5.1 uses.

Table 9 lists the supported device credentials for LAN Management Solution 2.5.1

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.1 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. Installation might proceed in other locales but there might be problems in the functionality of CiscoWorks.


Note LMS 2.5.1 is not supported on any native 64-bit systems.


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

Table 3 Recommended Server Requirements for Solaris Systems

Component
Recommended Server System Requirement

CPU

Sun UltraSPARC IIIi or Sun UltraSPARC IIICu for Restricted license.

Dual Sun UltraSPARC IIIi or dual Sun UltraSPARC IIICu for Unrestricted license

RAM

2 GB for Restricted license

4 GB for Unrestricted license

Software

Solaris 8 (Solaris 2.8) and Solaris 9 (Solaris 2.9)

Disk Space

80 GB or more free space for LMS applications and data

Swap Space

4 GB swap space for Restricted license

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 amount of available disk space in each of the specified partitions and directories, enter: df -k at the command prompt.


Table 4 lists the server requirements for upgrading the LAN Management Solution 2.5.1 components on Windows systems. For list of Windows HotFix patches, see "Frequently Asked Questions" section.

Table 4 Recommended Server Requirements for Windows Systems 

Component
Recommended Server System Requirement

CPU

2.8 GHz Intel Pentium IV or 2.8 GHz Intel Xeon processor for Restricted license.

Dual 2.8 GHz Intel Pentium IV or dual 2.8 GHz Intel Xeon processor for Unrestricted license

RAM

2 GB for Restricted license

4 GB for Unrestricted license.

Software1 ,2 ,3

Any one of the following:

Windows 2000 Professional with Service Pack 44

Windows 2000 Server with Service Pack 4

Windows 2000 Advanced Server with Service Pack 4

Windows Server 2003 Standard and Enterprise Editions with Service Pack 1

LAN Management Solution 2.5.1 supports only the US English and Japanese versions of these operating systems. Set the default locale to US-English for the US-English version and Japanese for the Japanese version. Installation might proceed in other locales but there might be problems in the functionality of CiscoWorks.

Disk space

80 GB or more free space for LMS applications and data

Swap space

4 GB virtual memory for Restricted license

8 GB virtual memory for Unrestricted license.

NTFS file system5 required

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

1 Installation of LMS 2.5.1 on a system with Internet Information Services (IIS) enabled is not supported. IIS Service must be disabled on the server before installing the LMS 2.5.1 applications.

2 If you are using LMS 2.5.1 on a Windows 2000 operating system (all versions), disable Hyper-Threading Technology (HTT). See http://www.intel.com/support/processors/sb/CS-017343.htm.

3 Installation of LMS 2.5.1 applications on a system with Terminal Services enabled in Remote Administration mode is supported. However, installation of LMS 2.5.1 applications on a system with Terminal Services enabled in Application mode is not supported.

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

5 Install LMS 2.5.1 on an NTFS file system. Do not install LMS 2.5.1 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 lists the client system requirements for all platforms.

Table 5 Recommended Client Hardware and Software Requirements 

Component
Recommended Requirement

Hardware/software

Any one of these systems:

IBM PC-compatible system with at least Pentium IV processor running,

Windows 2000 Professional with Service Pack 4

Windows 2000 Server with Service Pack 4

Windows 2000 Advanced Server with Service Pack 4

Windows Server 2003 Standard and Enterprise Edition with Service Pack 1

Windows XP with Service Pack 2

Sun Solaris 8 or Sun Solaris 9.

Disk space

Either of the following:

For Solaris: 1 GB swap space

For Windows: 1 GB virtual memory

RAM

512 MB minimum

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


Table 6 lists the browser requirements for all platforms.

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_082

6.0. Service Pack 1

Any one of the following:

Windows 2000

Windows Server 2003

6.0.2900.2180

Windows XP3

Netscape Navigator

7.1 and 7.2

Any one of the following:

Windows 2000

Windows Server 2003

Netscape Navigator (Downloaded from Sun site only)

7.0

Any one of the following:

Solaris 8

Solaris 9

Mozilla

1.7 and 1.7.5

Any one of the following:

Windows 2000

Windows Server 2003

Windows XP

Solaris 8

Solaris 9

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

2 You can upgrade to Java Plug-in version 1.4.2_08 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 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/interfaces with 6000 managed ports

Internetwork Performance Monitor (IPM)— 2,000 collectors

The supported concurrent users for LMS 2.5.1 are:

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

20 concurrent users for LMS 2.5.1 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.1.

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


Caution If you have installed patches 109147-36 through 109147-39 on a Solaris 8 system and patches 112963-21 through 112963-24 on a Solaris 9 system, the installation of LMS applications will fail. To complete the installation of LMS applications, you must downgrade to patch 109147-38 or earlier on a Solaris 8 system and to patch 112963-23 on Solaris 8 system.

Table 7 Solaris Patches for LAN Management Solution 2.5.11

Operating System
Required
Recommended
 
Server
Client
Server
Client

Solaris 8

111327-05

110945-08

110934-16

110898-09

109326-14

108827-40

108528-29

111626-03

108652-81

108921-21

108940-62

110951-05

110662-12

110615-11

108964-06

110286-11 109324-05

Solaris 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

112874-31

112808-06

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


LAN Management Solution Port Usage

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

7

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)

CiscoWorks Common Services (PSU), 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

Client to Server

TCP

8088

HIOP

CiscoWorks Common Services

Server to Client

Client to Server

TCP

8888

Log Server

DFM

Server Internal

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

(Applicable to IPM standalone client)

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

DFM trap receiving (if port 162 is occupied)

DFM

Client to Server

UDP

9002

DFM trap listening

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

HIOP

9091

CORBA

CM

Server to Client
Client to Server

IIOP

9092

CORBA

CM

Client to Server

IIOP

9093

CORBA

CM

Client to Server


Required LAN Management Protocols

Several important device credentials must be configured correctly on every Cisco device that will be managed and monitored through LMS. Also, you must enter the correct device credentials in the Device Credential Repository (Common Services > Device and Credentials > Device Management).

Table 9 lists all the applications and the device credentials required for proper functioning of the applications.

Table 9 Applications and the Device Credentials 

Application
Telnet/SSH Password
Enable Password
SNMP Read Only
SNMP Read / Write
Common Services

Not required

Not required

Not required

Required

Campus Manager

Not required

Not required

Required

Not required1

CiscoView

Not required

Not required

Required

Required

Device Fault Manager

Not required

Not required

Required

Not required

Internetwork Performance Monitor

Not required

Not required

Required

Required

Resource Manager Essentials

Inventory

Not required

Not required

Required

Not required

Configuration Management (Telnet)

Required

Required

Required

Not required

Configuration Management2 (TFTP) 3

Not required

Not required

Required

Required

NetConfig

Required

Required

Required

Not required4

Config Editor

Required

Required

Required

Not required5

NetShow

Required

Required

Required

Not required

Software Management

Required6

Required6

Required

Required

1 SNMP Read/Write credentials are required if you are configuring VLAN, trunk, etc.

2 Configuration download also uses TFTP. Hence, SNMP Read/Write credentials are required.

3 The file vlan.dat can be fetched only if the Telnet password and Enable password are supplied.

4 After execution of a job, NetConfig provides an option to fetch the configuration using TFTP. SNMP Read/Write credentials are required in such cases.

5 After execution of a job, Config Editor provides an option to fetch the configuration using TFTP. SNMP Read/Write credentials are required in such cases.

6 Required in case of few devices like PIX devices, Cisco 2950 series switches.


Migrating from LMS and RWAN to LMS 2.5.1

If you have any one of the following versions of LMS or RWAN, to be in LMS 2.5.1 you must migrate your LMS data:

LMS 2.2/LMS 1.3 to LMS 2.5.1

LMS 2.2 / LMS 1.3 Update 1 to LMS 2.5.1

LMS 2.1/LMS 1.2 to LMS 2.5.1

RWAN 1.3 to LMS 2.5.1

RWAN 1.3 Update 1 to LMS 2.5.1

RWAN 1.2 to LMS 2.5.1

See Table 10 for further information on migration paths.


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


Migration involves migrating data from an older version of LMS to a newer version of LMS. The steps for migration include:

1. Backing up the older version of LMS data.

2. Installing the newer version of LMS.

3. Restoring the backed up data.

You can migrate using either of these two methods:

Local migration—Installing LMS 2.5.1 on top of LMS (1.2, 1.3, 2.1, or 2.2) or RWAN (1.2 or 1.3) on the same machine.

Or

Remote migration—Installing LMS 2.5.1 on a different machine.

For information on the data that is migrated to LMS 2.5.1, see the LMS applications Installation Guides.

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

Prerequisites

This section describes the factors that you should consider before migrating to LMS 2.5.1:

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

Stop all third party network management applications, such as HP OpenView Network Node Manager, before installing the LAN Management Solution 2.5.1.

Be aware of the following:

If you are a DFM user and if you plan to upgrade your operating system from Solaris 2.7 or Solaris 2.8 (Solaris 8) to Solaris 2.9 (Solaris 9), you must upgrade the operating system only after migrating DFM.

You must migrate to CiscoWorks Common Services 3.0.3 before migrating any other application.

We recommend that you follow the exact steps that are described in the Data Migration Guide for LAN Management Solution 2.5.1 to migrate and to restore LMS/RWAN data.

The Data Migration Guide for LAN Management Solution 2.5.1 is provided as hardcopy along with LMS 2.5.1 product kit. This is also available at this location:

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

If you are using this Maintenance Kit CD (for CiscoWorks LAN Management Solution 2.5.1) and you are upgrading from LMS (1.2, 1.3, 2.1, or 2.2) or RWAN (1.2 or 1.3) you may be asked to validate your LMS application images after completing the installation. See "Validate the Upgrade License for RME on Solaris" section.

Ensure you complete the following tasks before migration:


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 Installation Notes" section and "Terms and Definitions Used in LMS 2.5 1 Installation Framework" section


Table 10 lists the supported migration paths to LMS 2.5.1.

Table 10 Migration Paths 

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

LMS 2.2 Update 1

This version contains the following applications:

CiscoWorks Common Services 2.2 with SP2 (Includes CiscoView 5.5)

Resource Manager Essentials 3.5 with Update 1

Campus Manager 3.3 with Update 1

Device Fault Manager with Update 1 (DFMSD 1.2)

NetScout nGenius Real-Time Monitor 1.4 (RTM)

You can verify the installed application versions by selecting Server Configuration > About the Server > Applications and Versions.

1. Migrate to LMS 2.5.1 using the instructions in this Data Migration Guide for LAN Management Solution 2.5.1.

2. This step is applicable only for Remote Migration. Validate the upgrade license if you are providing an upgrade license file or PIN/PAK.

See the "Validating the Upgrade License" section for more information.

LMS 1.3 Update 1

This version contains the following applications:

CiscoWorks Common Services 2.2 with SP2 (Includes CiscoView 5.5)

Resource Manager Essentials 3.5 with Update 1

Campus Manager 3.3 with Update 1

NetScout nGenius Real-Time Monitor 1.4 (RTM)

You can verify the installed application versions by selecting Server Configuration > About the Server > Applications and Versions.

1. Migrate to LMS 2.5.1 using the instructions in this Data Migration Guide for LAN Management Solution 2.5.1.

2. This step is applicable only for Remote Migration. Validate the upgrade license if you are providing an upgrade license file or PIN/PAK.

See the "Validating the Upgrade License" section for more information.

LMS 2.2

This version contains the following applications:

CiscoWorks Common Services 2.2 (Includes CiscoView 5.5)

Resource Manager Essentials 3.5

Campus Manager 3.3

Device Fault Manager 1.2 Updated for Common Services Version 2.2

NetScout nGenius Real-Time Monitor 1.4 (RTM)

You can verify the installed application versions by selecting Server Configuration > About the Server > Applications and Versions.

1. Migrate to LMS 2.5.1 using the instructions in this Data Migration Guide for LAN Management Solution 2.5.1.

2. This step is applicable only for Remote Migration. Validate the upgrade license if you are providing an upgrade license file or PIN/PAK.

See the "Validating the Upgrade License" section for more information.

LMS 1.3

This version contains the following applications:

CiscoWorks Common Services 2.2 (Includes CiscoView 5.5)

Resource Manager Essentials 3.5

Campus Manager 3.3

NetScout nGenius Real-Time Monitor 1.4 (RTM)

You can verify the installed application versions by selecting Server Configuration > About the Server > Applications and Versions.

1. Migrate to LMS 2.5.1 using the instructions in this Data Migration Guide for LAN Management Solution 2.5.1.

2. This step is applicable only for Remote Migration. Validate the upgrade license if you are providing an upgrade license file or PIN/PAK.

See the "Validating the Upgrade License" section for more information.

LMS 2.1

This version contains the following applications:

CD One, 5th Edition

Resource Manager Essentials 3.4

Campus Manager 3.2

Device Fault Manager 1.2

nGenius Real-Time Monitor 1.4

You can verify the installed application versions by selecting Server Configuration > About the Server > Applications and Versions.

1. Migrate to LMS 2.5.1 using the instructions in this Data Migration Guide for LAN Management Solution 2.5.1.

2. This step is applicable only for Remote Migration. Validate the upgrade license if you are providing an upgrade license file or PIN/PAK.

See the "Validating the Upgrade License" section for more information.

LMS 1.2

This version contains the following applications:

CD One, 5th Edition

Resource Manager Essentials 3.4

Campus Manager 3.2

nGenius Real-Time Monitor 1.4

You can verify the installed application versions by selecting Server Configuration > About the Server > Applications and Versions.

1. Migrate to LMS 2.5.1 using the instructions in this Data Migration Guide for LAN Management Solution 2.5.1.

2. This step is applicable only for Remote Migration. Validate the upgrade license if you are providing an upgrade license file or PIN/PAK.

See the "Validating the Upgrade License" section for more information.

RWAN 1.3 Update 1

This version contains the following applications:

CiscoWorks Common Services 2.2 with SP2 (Includes CiscoView 5.5)

Resource Manager Essentials 3.5 with Update 1

Access Control List Manager 1.5 Update 1

Internetwork Performance Monitor 2.5.2

You can verify the installed application versions by selecting Server Configuration > About the Server > Applications and Versions.

1. Migrate to LMS 2.5.1 using the instructions in this Data Migration Guide for LAN Management Solution 2.5.1.

2. This step is applicable only for Remote Migration. Validate the upgrade license if you are providing an upgrade license file or PIN/PAK.

See the "Validating the Upgrade License" section for more information.

RWAN 1.3

This version contains the following applications:

CiscoWorks Common Services 2.2

Resource Manager Essentials 3.5

Access Control List Manager 1.5

Internetwork Performance Monitor 2.5

You can verify the installed application versions by selecting Server Configuration > About the Server > Applications and Versions.

1. Migrate to LMS 2.5.1 using the instructions in this Data Migration Guide for LAN Management Solution 2.5.1.

2. This step is applicable only for Remote Migration. Validate the upgrade license if you are providing an upgrade license file or PIN/PAK.

See the "Validating the Upgrade License" section for more information.

RWAN 1.2

This version contains the following applications:

CD One, 5th Edition

Resource Manager Essentials 3.4

Access Control List Manager 1.4

Internetwork Performance Monitor 2.4

You can verify the installed application versions by selecting Server Configuration > About the Server > Applications and Versions.

1. Migrate to LMS 2.5.1 using the instructions in this Data Migration Guide for LAN Management Solution 2.5.1.

2. This step is applicable only for Remote Migration. Validate the upgrade license if you are providing an upgrade license file or PIN/PAK.

See the "Validating the Upgrade License" section for more information.


Installing LAN Management Solution 2.5.1

To install 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 installing LMS 2.5.1. See "Prerequisites" section.

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

Stop all third party network management applications, such as HP OpenView Network Node Manager, before installing the LAN Management Solution 2.5.1.

Be aware of the following:

If you are a DFM user and if you plan to upgrade your operating system from Solaris 2.7 or Solaris 2.8 (Solaris 8) to Solaris 2.9 (Solaris 9), you must upgrade the operating system only after upgrading DFM.

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

After you have upgraded CiscoWorks Common Services 3.0.3, you must upgrade each LMS 2.5.1 application separately. While we strongly recommend that you follow the "Recommended Order of Installation" section, you can upgrade the other applications of LMS 2.5.1 in any order.

If you are using this Maintenance Kit CD (for CiscoWorks LAN Management Solution 2.5.1) and you are upgrading from LMS (1.2, 1.3, 2.1, or 2.2) or RWAN (1.2 or 1.3) you may be asked to validate your LMS application images after completing the installation. See "Validating the Upgrade License" section for details.

Prerequisites

This section describes the factors that you should consider before upgrading LMS 2.5.1. 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 Installation Notes" section and "Terms and Definitions Used in LMS 2.5 1 Installation Framework" section


Important Installation Notes

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

You can install LMS 2.5.1 applications on a system with Terminal Services enabled in Remote Administration mode. However, installation of LMS 2.5.1 applications on a system with Terminal Services enabled in Application mode is not supported.

If you have a enabled Terminal Server in Application mode, disable the Terminal Server, reboot the system, and start the installation again.

Installation of LMS 2.5.1 on a system with Internet Information Services (IIS) enabled is not supported. IIS Service must be disabled on the server before installing the LMS 2.5.1 applications.

LMS 2.5.1 is not supported on any native 64-bit systems.

LMS 2.5.1 is not supported on virtual machines, such as VMware and VirtualPC.

If you are using LMS 2.5.1 on a Windows 2000 operating system (all versions), disable Hyper-Threading Technology (HTT). See http://www.intel.com/support/processors/sb/CS-017343.htm.

Applications not supported by CiscoWorks Common Services 3.0.3 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.3.

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

CiscoWorks applications are installed in the default directories:

On Solaris: /opt/CSCOpx

On Windows: SystemDrive:\Program Files\CSCOpx

Where SystemDrive is the Windows operating system installed directory.

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

On Solaris, if you select an installation directory other than the default, the /opt/CSCOpx directory is created as a link to the directory you selected.


Warning If you remove this link after installation, the product will malfunction.


On Solaris, if errors occur during installation, check the installation log file /var/tmp/ciscoinstall.log.

For IPM, the installation log file is /var/tmp/cisco_ipm_install.log,

On Windows, if errors occur during installation, check the installation log in the root directory on the drive where the operating system is installed. Each installation creates a new log file.

For example, the CiscoWorks Common Services installation creates SystemDrive:\CiscoWorks_setupxxx.log, where xxx is the running number for the last CiscoWorks application installed.

For IPM, there is no installation log file on Windows.

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

For example, if any new files were installed or if they were any changes to the system files, you need to manually cleanup the installation directories.


Note We recommend that you do not terminate the installation while it is running.


By default, SSL is not enabled on CiscoWorks Server.

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

If your CiscoWorks Management 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.3 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.

On Windows, if you are running any virus scanner while installing LMS applications, the installation might take longer to complete. We recommend that you disable the virus scan software on your system. You can restart it after all installations are completed.

To ensure that you have the latest device support and bug fixes for Resource Manager Essentials, Campus Manager and Device Fault Manager, you must install the latest Service Packs. For download locations, see the "Additional Package Information" section.

Terms and Definitions Used in LMS 2.5 1 Installation Framework

This section captures the terms and definitions that are used by LMS 2.5.1 applications at the time of installation.

See "Licensing Your Product" section to understand the licensing terminologies.

Common Services 3.0.3:

While installing Common Services 3.0.3, you may come across these terms:

CiscoWorks admin password—CiscoWorks administrative password. This is used while logging into the CiscoWorks server as administrator. Use a minimum of five characters.

This is the only CiscoWorks predefined user, ensure that you have noted down the password.

You are prompted to enter this password in both Typical and Custom modes of installation.

System Identity Account password—Password that is used in a multi-server environment. You must configure all the CiscoWorks servers that are part of your multi-server setup with the same system identity account password.

Communication among multiple CiscoWorks Servers is enabled by a "trust" model addressed by certificates and shared secrets. System Identity setup helps you to create a "trust" user among servers that are part of a multi-server setup. This user enables communication between servers that are part of a domain.

While entering the System Identity Account Passwords, use a minimum of five characters.

You are prompted to enter this password in both Typical and Custom modes of installation.

CiscoWorks guest password—CiscoWorks guest password. This is used while logging into the CiscoWorks server as a guest user. Use a minimum of five characters.

You are prompted to enter this password in the Custom mode of installation. In the Typical mode, this password is randomly generated.

Common Services database password—Common Services database password. Use a minimum of five characters and a maximum of 15 characters. Do not start the password with a number and do not insert spaces between characters.

This database password is used internally by the other LMS applications to communicate with the Common Services database. This password is also used while restoring or troubleshooting the Common Services database.

You are prompted to enter this password in the Custom mode of installation. In the Typical mode, this password is randomly generated.

Self Signed Certificate—CiscoWorks allows you to create security certificates to enable SSL communication between your client browser and management server.

Self Signed Certificates are valid for five years from the date of creation. When the certificate expires, the browser prompts you to install the certificate again from the server where you have installed CiscoWorks.

You are prompted to enter the following information to generate the Self Signed Certificate in the Custom mode of installation:

Country Name—Two character country code. This is optional.

State or Province—Two character state or province code or the complete name of the state or province. This is optional.

Locality—Two character city or town code or the complete name of the city or town. This is optional.

Organization Name—Complete name of your organization or an abbreviation. This is optional.

Organization Unit Name—Complete name of your department or an abbreviation. This is optional.

Host Name—DNS name of the computer or the IP address of the computer. This is mandatory.

Enter the Host Name with a proper domain name. This is displayed on your certificate (whether self-signed or third party issued). Local host or 127.0.0.1 should not be given.

E-mail Address—E-mail address to which the mail has to be sent. This is optional.

In the Typical mode, this certificate is automatically generated.

SMTP Server—System-wide name of the SMTP server used by CiscoWorks applications to deliver reports. The default server name is localhost.

You are prompted to enter this server detail only in the Custom mode of installation. In the Typical mode, after the installation you can configure SMTP by selecting Server > Admin > System Preferences on CiscoWorks homepage.

Cisco.com—Cisco.com user ID and password. This information is used while performing tasks such as, downloading software images, downloading device packages, etc.

You are prompted to enter these credentials while installing the CiscoWorks Integration Utility.

You can also change the System Identity Account password, Guest password, and Cisco.com credentials using Common Services User Interface (Common Services > Server > Security).

Resource Manager Essentials 4.0.3:

While installing RME 4.0.3, you may come across this term:

RME database password—RME database password. Use a minimum of five characters and a maximum of 15 characters. Do not start the password with a number and do not insert spaces between characters.

This password is also used while restoring or troubleshooting the RME database.

You are prompted to enter this password in the Custom mode of installation. In the Typical mode, this password is randomly generated.

Campus Manager 4.0.3:

While installing CM 4.0.3, you may come across this term:

ANI database—Campus Manager accesses the ANI database for critical network information. Use a minimum of five characters and a maximum of 15 characters. Do not start the password with a number and do not insert spaces between characters.

Device Fault Manager 2.0.3:

While installing DFM 2.0.3, you may come across these terms:

DFM database password—DFM database password. Use a minimum of five characters and a maximum of 15 characters. Do not start the password with a number and do not insert spaces between characters.

This password is also used while restoring or troubleshooting the DFM database.

You are prompted to enter this password in the Custom mode of installation. In the Typical mode, this password is randomly generated.

DFM username and password—These credentials are used by DFM processes. Use a minimum of five characters.

You are prompted to enter this password in the Custom mode of installation. In the Typical mode, this password is randomly generated.

Internetwork Performance Monitor 2.6:

While installing IPM 2.6, you may come across these terms:

Database password—IPM database password. The password is case sensitive and should begin with an alphabet. You can enter only a maximum of 15 characters and you can enter only alphanumeric characters.

This password is also used while restoring or troubleshooting the IPM database.

You are prompted to enter this password in both standard installation and Express installation.

Administrative password—You need this password to launch the IPM standalone client. To protect the integrity of your IPM database, IPM provides client security that enables you to define an IPM Administrative password.

IPM prompts you to enter this Administrative password to access the client functions such as, opening the seed files, launching the Secure Web clients, using the ipm tshoot troubleshooting command, and downloading the IPM client software from the IPM Server Home Page.

The password is case sensitive and should begin with an alphabet. You can enter only a maximum of 15 characters and you can enter only alphanumeric characters.

You are prompted to enter this password in both standard installation and Express installation.

Recommended Order of Installation

If you installing LMS 2.5.1 for the first time, we recommend that you install each application of LMS 2.5.1 in the following order:


Step 1 Install CiscoWorks Common Services 3.0.3.

Step 2 Install Resource Manager Essentials 4.0.3.

Step 3 Install Campus Manager 4.0.3.

Step 4 Install Device Fault Manager 2.0.3.

Step 5 Install Internetwork Performance Monitor 2.6.

Step 6 Perform 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 installing the product on a server other than where you have your previous version installed, the validation fails because it is a fresh installation on that machine. You are prompted to run the validateupgrade utility from CLI after the installation.

See "Validating the Upgrade License" section.


Installing LMS 2.5.1 on Solaris

The following sections capture information on how to install LMS 2.5.1 on Solaris:

Installing CiscoWorks Common Services 3.0.3 on Solaris

Installing Resource Manager Essentials 4.0.3 on Solaris

Installing Campus Manager 4.0.3 on Solaris

Installing Device Fault Manager 2.0.3 on Solaris

Installing Internetwork Performance Monitor 2.6 on Solaris

Installing CiscoWorks Common Services 3.0.3 on Solaris

Installing CiscoWorks Common Services takes approximately 25 minutes:


Step 1 Locate Installation and Setup Guide for CiscoWorks Common Services (Includes CiscoView 6.1.2) 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/cs303/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 install 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. If the default ports are in use, the installation will detect this and assign some other port. 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 a New Installation", in Chapter 2.

The default installation option is Typical. Select Custom install option if you want to specify a destination other than /opt/CSCOpx.

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

1. Understanding the CiscoWorks Homepage. See "Understanding the CiscoWorks Homepage" section in this document.

2. Configuring the CiscoWorks Server.

3. Configuring your client.

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


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

Installing Resource Manager Essentials 4.0.3 on Solaris

Installing Resource Manager Essentials takes approximately 30 minutes:


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

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

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

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

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

Step 2 Follow the steps in the section "Performing a New Installation", in Chapter 2.

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

Step 3 Follow the steps in Chapter 2, "Preparing to Use RME".


If you receive error messages during the installation, or cannot access the home page, see Appendix C, "Troubleshooting the Installation".

Installing Campus Manager 4.0.3 on Solaris

Installing Campus Manager takes approximately 30 minutes:


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

On the application 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/camp_4x/cmgr_403/index.htm

Step 2 Follow the steps in the section "Performing a New Installation", in Chapter 2.

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

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


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

Installing Device Fault Manager 2.0.3 on Solaris

Installing Device Fault Manager (DFM) takes approximately 20 minutes:


Step 1 Locate Installation Guide for Device Fault Manager on Solaris. The document is available:

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

From the CD-ROM root directory, look for CD-ROMDrive/Documentation/dfm203_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/
dfm203/install/index.html

Step 2 Follow the steps in the section "Performing a New Installation", in Chapter 2.

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


Installing Internetwork Performance Monitor 2.6 on Solaris

Installing Internetwork Performance Monitor (IPM) takes approximately 20 minutes. The installation script installs Internetwork Performance Monitor in the following default locations:

/opt/CSCOipm

/opt/CSCOcwbS

/opt/CSCOipmClient


Step 1 Locate Installation Guide for Internetwork Performance Monitor 2.6. You can find this document:

On the application CD, 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 IPM 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 4, "Installing IPM on Solaris".

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


Installing LMS 2.5.1 on Windows

The following sections capture information on how to install LMS 2.5.1 on Windows:

Installing CiscoWorks Common Services 3.0.3 on Windows

Installing Resource Manager Essentials 4.0.3 on Windows

Installing Campus Manager 4.0.3 on Windows

Installing Device Fault Manager 2.0.3 on Windows

Installing Internetwork Performance Monitor 2.6 on Windows

Installing CiscoWorks Common Services 3.0.3 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 installation. CiscoWorks Common Services 3.0.3 does not support directory encryption.

Installing CiscoWorks Common Services takes approximately 15 minutes:


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

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 a New Installation", in Chapter 2.

The default installation option is Typical. Select Custom install option if you want to specify a destination other than SystemDrive:\Program Files\CSCOpx.

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

1. Understanding the CiscoWorks Homepage. See, "Understanding the CiscoWorks Homepage" section in this document.

2. Configuring the CiscoWorks Server.

3. Configuring your client.

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


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

Installing Resource Manager Essentials 4.0.3 on Windows

Installing Resource Manager Essentials takes approximately 30 minutes:


Step 1 Locate Installation and Setup Guide for Resource Manager Essentials on Windows. The document is available:

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

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

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

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

Step 2 Follow the steps in the section "Performing a New Installation", in Chapter 2.

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

Step 3 Follow the steps in Chapter 2, "Preparing to Use RME".


If you receive error messages during the installation, or cannot access the Homepage, see Appendix C, "Troubleshooting the Installation".

Installing Campus Manager 4.0.3 on Windows

Installing Campus Manager takes approximately 20 minutes:


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

On the application 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/camp_4x/cmgr_403/index.htm

Step 2 Follow the steps in the section "Performing a New Installation", in Chapter 2.

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

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


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

Installing Device Fault Manager 2.0.3 on Windows

Installing Device Fault Manager (DFM) takes approximately 20 minutes:


Step 1 Locate Installation Guide for Device Fault Manager on Windows. The document is available:

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

From the CD-ROM root directory, look for CD-ROMDrive\Documentation\dfm203_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/
dfm203/install/index.html

Step 2 Follow the steps in the section "Performing a New Installation", in Chapter 2.

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


Installing Internetwork Performance Monitor 2.6 on Windows

Installing Internetwork Performance Monitor (IPM) takes approximately 20 minutes. The installation script installs Internetwork Performance Monitor in the following default locations:

\\Program Files\Internetwork Performance Monitor.


Step 1 Locate Installation Guide for Internetwork Performance Monitor 2.6. You can find this document:

On the application CD, 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 IPM.

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


Verifying the Installation

You can verify LMS 2.5.1 installation by following any one of these procedures.

Procedure 1:

You can verify LMS 2.5.1 installation by entering the command pdshow from /opt/CSCOpx/bin on Solaris and NMSROOT/bin on Windows.

Where, NMSROOT is the CiscoWorks installation directory (by default, SystemDrive:\Program Files\CSCOpx and SystemDrive is the Windows operating system installed directory).

or

On CiscoWorks Homepage, Common Services > Server > Admin > Processes:

The following services should be displayed:

Application Name
Services

Common Services 3.0.3

ESS, EssMonitor, CmfDbEngine, CmfDbMonitor, DCRServer, CMFOGSServer, LicenseServer, Tomcat, Apache, RmeOrb, RmeGatekeeper, EDS, EDS-GCF, EDS-TR, jrm, diskWatcher, CSRegistryServer, TomcatMonitor, RmeOrb, RmeGatekeeper, FDRewinder (Only on Solaris), Proxy (Only on Windows)

Campus Manager 4.0.3

ANIServer, ANIDbEngine, CampusOGSServer, UTMajorAcquisition, DeviceDiscovery

Device Fault Manager 2.0.3

DfmServer, DFMLogServer, DFMCTMStartup, DfmBroker, DFMMultiProcLogger, DFMOGSServer, EPMServer, EPMDbEngine, AdapterServer, FHPurgeTask, FHDbEngine, FHDbMonitor, EPMDbMonitor, FHServer, TISServer, InventoryCollector, INVDbEngine, INVDbMonitor, PMServer, NOSServer, PTMServer, Interactor, DataPurge

Resource Manager Essentials 4.0.3

RMEDbEngine, RMEDbMonitor, RMECSTMServer, ConfigMgmtServer, NCTemplateMgr, NetShowMgr, RMEOGSServer, SyslogCollector, EssentialsDM, CTMJrmServer, ChangeAudit, ICServer, SyslogAnalyzer


Procedure 2:

To verify from CiscoWorks Homepage:


Step 1 Select Common Services > Homepage > Application Registration.

The Application Registration Status page appears.

Step 2 Check the Registered Applications table.

The following applications must be lists:

CiscoView

Campus Manager

RME

Device Fault Manager

Internetwork Performance Monitor


For Internetwork Performance Monitor 2.6, see the following chapters in the Installation Guide for Internetwork Performance Monitor 2.6.

For Solaris, Chapter 4, Verifying IPM Installation on Solaris.

For Windows. Chapter 5, Verifying IPM Installation on Windows

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

Upgrading from LMS and RWAN to LMS 2.5.1

This involves overwriting the existing LMS version with the new LMS version. The data may be migrated to the newer version based on the installed LMS application. See Table 11 for more information on data migration.

You can upgrade to LMS 2.5.1 from any one of these versions:

LMS 2.5 to LMS 2.5.1

LMS 2.2/LMS 1.3 to LMS 2.5.1

LMS 2.2 / LMS 1.3 Update 1 to LMS 2.5.1

LMS 2.1/LMS 1.2 to LMS 2.5.1

RWAN 1.3 to LMS 2.5.1

RWAN 1.3 Update 1 to LMS 2.5.1

RWAN 1.2 to LMS 2.5.1

If you have upgraded from LMS 2.5 to LMS 2.5.1, the versions of all the individual LMS applications are upgraded and also all of the data are migrated, except IPM. Since there are no changes in IPM from LMS 2.5 to LMS 2.5.1, it is not upgraded.

For example, RME 4.0 is upgraded to RME 4.0.3.

You can upgrade using either of these two methods:

Local upgrade—Installing LMS 2.5.1 on top of LMS (1.2, 1.3, 2.1, or 2.2, 2.5) or RWAN (1.2 or 1.3) on the same machine.

Or

Remote upgrade—Installing LMS 2.5.1 on a different machine and then restoring the data on the machine that has LMS 2.5.1.

Table 11 describes the scenario when the data is migrated to LMS 2.5.1:

Table 11 Support for LMS and RWAN Data Migration

Application
LMS 2.1/RWAN 1.2
LMS 2.2/RWAN 1.3
LMS 2.5

Common Services

CD One, 5th Edition data migrated to Common Services 3.0.3.

Common Services 2.2 data migrated to Common Services 3.0.3.

Common Services 3.0 data migrated to Common Services 3.0.3.

RME

RME 3.4 data not migrated to RME 4.0.3.

RME 3.5 data not migrated to RME 4.0.3.

RME 4.0 data migrated to RME 4.0.3.

Campus Manager

Campus Manager 3.2 data migrated to Campus Manager 4.0.3.

Campus Manager 3.3 data migrated to Campus Manager 4.0.3.

Campus Manager 4.0 data migrated to Campus Manager 4.0.3.

DFM

DFM 1.2 data not migrated to DFM 2.0.3.

DFM 1.2 Updated for Common Services 2.2. data not migrated to DFM 2.0.3.

DFM 2.0 data migrated to DFM 2.0.3.

IPM

IPM 2.4 data migrated to IPM 2.6.

IPM 2.5 data migrated to IPM 2.6.

IPM 2.6 is not updated for LMS 2.5.1.


Prerequisites

This section describes the factors that you should consider before upgrading to LMS 2.5.1:

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 Network Node Manager, before installing the LAN Management Solution 2.5.1.

Be aware of the following:

If you are a DFM user and if you plan to upgrade your operating system from Solaris 2.7 or Solaris 2.8 (Solaris 8) to Solaris 2.9 (Solaris 9), you must upgrade the operating system only after upgrading DFM.

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

If you are upgrading from LMS (1.2, 1.3, 2.1, or 2.2) or RWAN (1.2 or 1.3) we recommend that you follow the exact steps that are described in the Data Migration Guide for LAN Management Solution 2.5.1 to upgrade to LMS 2.5.1.

The Data Migration Guide for LAN Management Solution 2.5.1 is provided as hardcopy along with LMS 2.5.1 product kit. This is also available at this location:

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

If you are using this Maintenance Kit CD (for CiscoWorks LAN Management Solution 2.5.1) and you are upgrading from LMS (1.2, 1.3, 2.1, or 2.2) or RWAN (1.2 or 1.3) you may be asked to validate your LMS application images after completing the installation. See "Validating the Upgrade License" section.

If you are upgrading from LMS 2.5 to LMS 2.5.1, follow the procedure described in "Upgrade from LMS 2.5 to LMS 2.5.1" section.

If you have upgraded from LMS 2.5 to LMS 2.5.1 and if you have already validated the upgrade license for LMS 2.5, you do not have to validate the license once again for LMS 2.5.1.

Ensure you complete the following tasks before migration:


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 Installation Notes" section and "Terms and Definitions Used in LMS 2.5 1 Installation Framework" section


Table 12 lists the supported upgrade paths to LMS 2.5.1.

Table 12 Upgrade Paths 

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

LMS 2.5

Upgrade using either the LMS 2.5.1 CD-ROM or LMS 2.5 December 2005 Update.

For CD-ROM, use the instructions in this guide. See "Upgrade from LMS 2.5 to LMS 2.5.1" section

For LMS 2.5 December 2005 Update, use the instructions in the Readme for LMS 2.5 Update 1.

This is available at this location:
http://www.cisco.com/kobayashi/sw-center/
cw2000/lan-planner.shtml

LMS 2.2 Update 1

This version contains the following applications:

CiscoWorks Common Services 2.2 with SP2 (Includes CiscoView 5.5)

Resource Manager Essentials 3.5 with Update 1

Campus Manager 3.3 with Update 1

Device Fault Manager with Update 1 (DFMSD 1.2)

NetScout nGenius Real-Time Monitor 1.4 (RTM)

You can verify the installed application versions by selecting Server Configuration > About the Server > Applications and Versions.

0. Upgrade to LMS 2.5.1 using the instructions in this Data Migration Guide for LAN Management Solution 2.5.1.

1. This step is applicable only for Remote Upgrade. Validate the upgrade license if you are providing an upgrade license file or PIN/PAK.

See the "Validating the Upgrade License" section for more information.

LMS 1.3 Update 1

This version contains the following applications:

CiscoWorks Common Services 2.2 with SP2 (Includes CiscoView 5.5)

Resource Manager Essentials 3.5 with Update 1

Campus Manager 3.3 with Update 1

NetScout nGenius Real-Time Monitor 1.4 (RTM)

You can verify the installed application versions by selecting Server Configuration > About the Server > Applications and Versions.

1. Upgrade to LMS 2.5.1 using the instructions in this Data Migration Guide for LAN Management Solution 2.5.1.

2. This step is applicable only for Remote Upgrade. Validate the upgrade license if you are providing an upgrade license file or PIN/PAK.

See the "Validating the Upgrade License" section for more information.

LMS 2.2

This version contains the following applications:

CiscoWorks Common Services 2.2 (Includes CiscoView 5.5)

Resource Manager Essentials 3.5

Campus Manager 3.3

Device Fault Manager 1.2 Updated for Common Services Version 2.2

NetScout nGenius Real-Time Monitor 1.4 (RTM)

You can verify the installed application versions by selecting Server Configuration > About the Server > Applications and Versions.

1. Upgrade to LMS 2.5.1 using the instructions in this Data Migration Guide for LAN Management Solution 2.5.1.

2. This step is applicable only for Remote Upgrade. Validate the upgrade license if you are providing an upgrade license file or PIN/PAK.

See the "Validating the Upgrade License" section for more information.

LMS 1.3

This version contains the following applications:

CiscoWorks Common Services 2.2 (Includes CiscoView 5.5)

Resource Manager Essentials 3.5

Campus Manager 3.3

NetScout nGenius Real-Time Monitor 1.4 (RTM)

You can verify the installed application versions by selecting Server Configuration > About the Server > Applications and Versions.

1. Upgrade to LMS 2.5.1 using the instructions in this Data Migration Guide for LAN Management Solution 2.5.1.

2. This step is applicable only for Remote Upgrade. Validate the upgrade license if you are providing an upgrade license file or PIN/PAK.

See the "Validating the Upgrade License" section for more information.

LMS 2.1

This version contains the following applications:

CD One, 5th Edition

Resource Manager Essentials 3.4

Campus Manager 3.2

Device Fault Manager 1.2

nGenius Real-Time Monitor 1.4

You can verify the installed application versions by selecting Server Configuration > About the Server > Applications and Versions.

1. Upgrade to LMS 2.5.1 using the instructions in this Data Migration Guide for LAN Management Solution 2.5.1.

2. This step is applicable only for Remote Upgrade. Validate the upgrade license if you are providing an upgrade license file or PIN/PAK.

See the "Validating the Upgrade License" section for more information.

LMS 1.2

This version contains the following applications:

CD One, 5th Edition

Resource Manager Essentials 3.4

Campus Manager 3.2

nGenius Real-Time Monitor 1.4

You can verify the installed application versions by selecting Server Configuration > About the Server > Applications and Versions.

1. Upgrade to LMS 2.5.1 using the instructions in this Data Migration Guide for LAN Management Solution 2.5.1.

2. This step is applicable only for Remote Upgrade. Validate the upgrade license if you are providing an upgrade license file or PIN/PAK.

See the "Validating the Upgrade License" section for more information.

RWAN 1.3 Update 1

This version contains the following applications:

CiscoWorks Common Services 2.2 with SP2 (Includes CiscoView 5.5)

Resource Manager Essentials 3.5 with Update 1

Access Control List Manager 1.5 Update 1

Internetwork Performance Monitor 2.5.2

You can verify the installed application versions by selecting Server Configuration > About the Server > Applications and Versions.

1. Upgrade to LMS 2.5.1 using the instructions in this Data Migration Guide for LAN Management Solution 2.5.1.

2. This step is applicable only for Remote Upgrade. Validate the upgrade license if you are providing an upgrade license file or PIN/PAK.

See the "Validating the Upgrade License" section for more information.

RWAN 1.3

This version contains the following applications:

CiscoWorks Common Services 2.2

Resource Manager Essentials 3.5

Access Control List Manager 1.5

Internetwork Performance Monitor 2.5

You can verify the installed application versions by selecting Server Configuration > About the Server > Applications and Versions.

1. Upgrade to LMS 2.5.1 using the instructions in this Data Migration Guide for LAN Management Solution 2.5.1.

2. This step is applicable only for Remote Upgrade. Validate the upgrade license if you are providing an upgrade license file or PIN/PAK.

See the "Validating the Upgrade License" section for more information.

RWAN 1.2

This version contains the following applications:

CD One, 5th Edition

Resource Manager Essentials 3.4

Access Control List Manager 1.4

Internetwork Performance Monitor 2.4

You can verify the installed application versions by selecting Server Configuration > About the Server > Applications and Versions.

1. Upgrade to LMS 2.5.1 using the instructions in this Data Migration Guide for LAN Management Solution 2.5.1.

2. This step is applicable only for Remote Upgrade. Validate the upgrade license if you are providing an upgrade license file or PIN/PAK.

See the "Validating the Upgrade License" section for more information.


Upgrade from LMS 2.5 to LMS 2.5.1

You can perform this upgrade using the LMS 2.5.1 CD-ROM or LMS 2.5 December 2005 Update.

For CD-ROM, use the instructions in this guide.

For LMS 2.5 December 2005 Update, use the instructions in the Readme for LMS 2.5 December 2005 Update.

This is available at this location:
http://www.cisco.com/kobayashi/sw-center/cw2000/lan-planner.shtml

The following sections contain:

Local Upgrade from LMS 2.5 to LMS 2.5.1 on Solaris

Remote Upgrade from LMS 2.5 to LMS 2.5.1 on Solaris

Local Upgrade from LMS 2.5 to LMS 2.5.1 on Windows

Remote Upgrade from LMS 2.5 to LMS 2.5.1 on Windows

Figure 2 describes the steps involved in upgrading from LMS 2.5 to LMS 2.5.1 on Solaris:

Figure 2 Flowchart for LMS 2.5 to LMS 2.5.1 on Solaris

Local Upgrade from LMS 2.5 to LMS 2.5.1 on Solaris

In order to upgrade from LMS 2.5 to LMS 2.5.1, you must first install Common Services 3.0.3, then optionally upgrade one or more of the applications RME 4.0.3, Campus Manager 4.0.3, DFM 2.0.3. You need not upgrade IPM 2.6.

To upgrade from LMS 2.5 to LMS 2.5.1 on the same Solaris machine:


Step 1 Login as root to the machine where LMS 2.5 is installed.

Step 2 Install CS 3.0.3.

1. Insert CS 3.0.3 CD.

2. Run setup.sh from the CD-ROM root directory, for example, /cdrom/cdrom0.

After you complete installation of CS 3.0.3, the following message is displayed:

WARNING: This server has the following applications installed: 
WARNING: CM 4.0.x RME 4.0.x DFM 2.0.x 
WARNING: The system might be unstable if you run the 
WARNING: above versions of the application(s), along with CS 3.0.3 
WARNING: Ensure that you upgrade the application(s) to: 
WARNING: CM 4.0.3 RME 4.0.3 DFM 2.0.3

Step 3 Install RME 4.0.3.

1. Insert RME 4.0.3 CD.

2. Run setup.sh from the CD-ROM root directory, for example, /cdrom/cdrom0.

Step 4 Install Campus Manager 4.0.3.

1. Insert Campus Manager 4.0.3 CD.

2. Run setup.sh from the CD-ROM root directory, for example, /cdrom/cdrom0.

Step 5 Install DFM 2.0.3.

1. Insert DFM 2.0.3 CD.

2. Run setup.sh from the CD-ROM root directory, for example, /cdrom/cdrom0.

You need not run any scripts to migrate data. All necessary data is migrated to LMS 2.5.1 during the upgrade.

CiscoView device preferences are migrated inline from CiscoView 6.1 or CiscoView 6.1.1 to CiscoView 6.1.2 during the upgrade.


Remote Upgrade from LMS 2.5 to LMS 2.5.1 on Solaris

To upgrade LMS 2.5 to LMS 2.5.1 on a different Solaris machine:


Step 1 Login as root to the LMS 2.5 machine.

Step 2 Take backup of LMS 2.5 data for CS, RME, CM, and DFM.

Run the following command to backup data for LMS 2.5:

NMSROOT/bin/perl NMSROOT/bin/backup.pl BKP num_generations

For example:

/opt/CSCOpx/bin/perl /opt/CSCOpx/bin/backup.pl /ciscoworksdata 2

Where,

NMSROOT—CiscoWorks installation directory (by default, /opt/CSCOpx)

BKP—Backup directory, the data will be stored in the directories BKP/0, BKP/1, and BKP/2 etc., where BKP/n stores the data of the (n+1)th generation.

num_generations—Maximum backup generations to be kept in the backup directory

Or

You can backup data using the Common Services 3.0 GUI (Server > Admin > Backup). Click Help, and follow the instructions to back up your data. If you do not have IPM or CiscoView installed, proceed to Step 5.

Step 3 Take backup of IPM data.

1. Backup the IPM Database using the command IPMServer/bin/ipm dbbackup to the following location:

IPM Install dir/CSCOcwbS/db/CSCOipm/backup

2. Take backup of the following seed files:

IPMServer/etc/source

IPMServer/etc/target

IPMServer/etc/collector

3. Take backup of IPMServer/etc/ipm.env and IPMServer/etc/ipmDbPref.conf files.

Take backup of IPMServer/Server/htdocs/reports dir.

Where, IPMServer is IPM Install dir/CSCOipm

Step 4 Take backup of CiscoView Device Preferences.

Copy the file admin.preference from:

/CSCOpx/MDC/tomcat/webapps/CVng/WEB-INF/classes/cvuserprefs/ to a temporary location on the LMS 2.5.1 machine where the application is installed.

Step 5 Login as root to the remote machine where you want to install LMS 2.5.1.

Step 6 Install CS 3.0.3

1. Insert CS 3.0.3 CD.

2. Run setup.sh from the CD-ROM root directory, for example, /cdrom/cdrom0.

After you complete installation of CS 3.0.3, the following message is displayed:

WARNING: This server has the following applications installed: 
WARNING: CM 4.0.x RME 4.0.x DFM 2.0.x 
WARNING: The system might be unstable if you run the 
WARNING: above versions of the application(s), along with CS 3.0.3 
WARNING: Ensure that you upgrade the application(s) to: 
WARNING: CM 4.0.3 RME 4.0.3 DFM 2.0.3

Step 7 Install RME 4.0.3.

1. Insert RME 4.0.3 CD.

2. Run setup.sh from the CD-ROM root directory, for example, /cdrom/cdrom0.

Step 8 Install Campus Manager 4.0.3.

1. Insert Campus Manager 4.0.3 CD.

2. Run setup.sh from the CD-ROM root directory, for example, /cdrom/cdrom0.

Step 9 Install DFM 2.0.3.

1. Insert DFM 2.0.3 CD.

2. Run setup.sh from the CD-ROM root directory, for example, /cdrom/cdrom0.

Step 10 Install IPM 2.6.

1. Insert IPM 2.6 CD.

2. Run setup.sh from the CD-ROM root directory, for example, /cdrom/cdrom0.

Step 11 Stop the daemon manager by entering:

/etc/init.d/dmgtd stop

Step 12 Migrate LMS 2.5 data for CS, RME, DFM, and Campus Manager by entering:

NMSROOT/bin/perl NMSROOT/bin/restorebackup.pl -d BKP
-gen generationNumber -t temporary_directory

For example:

/opt/CSCOpx/bin/perl /opt/CSCOpx/bin/restorebackup.pl -d 
/ciscoworksdata -gen 2 -t /tempciscoworksdata

Where,

NMSROOT—CiscoWorks installation directory (by default, /opt/CSCOpx).

BKP—Location where backup data is available

generationNumber— Backup version to be restored. By default, it is the latest generation. If generations 1 through 5 exist, then 5 will be the latest.

temporary_directory—The restore framework uses a temporary directory to extract the content of backup archive. By default the temporary directory is created under NMSROOT as NMROOT/tempBackupData. You can customize this, by using this -t option, where you can specify your own temp directory. This is to avoid overloading NMSROOT.

If you do not have IPM or CiscoView data to migrate, proceed to Step 15.

Step 13 Migrate IPM data.

1. Copy the data files that were backed up in LMS 2.5 to the respective directories in the LMS 2.5.1 machine.

2. Copy backed up IPM database and .db password from LMS 2.5 machine to the following location:

Root IPM Install dir/CSCOcwbs/db/CSCOipm/backup

3. Stop IPM processes by entering:

IPMServer/bin/ipmstop

4. Restore the data by entering:

IPMServer/bin/ipm dbrestore

5. Restart IPM processes by entering:

IPMServer/bin/ipmstart

Step 14 Migrate CiscoView Device Preferences.

Copy the file admin.preference from the temporary directory to the following location:

/CSCOpx/MDC/tomcat/webapps/CVng/WEB-INF/classes/cvuserprefs/

Step 15 Start the daemon manager by entering:

/etc/init.d/dmgtd start


Figure 3 describes the steps involved in upgrading from LMS 2.5 to LMS 2.5.1 on Windows:

Figure 3 Flowchart for LMS 2.5 to LMS 2.5.1 on Windows

Local Upgrade from LMS 2.5 to LMS 2.5.1 on Windows

In order to upgrade from LMS 2.5 to LMS 2.5.1, you must first install Common Services 3.0.3, then optionally upgrade one or more of the applications RME 4.0.3, Campus Manager 4.0.3, DFM 2.0.3. You need not upgrade IPM 2.6.

To upgrade from LMS 2.5 to LMS 2.5.1 on the same Windows machine:


Step 1 Login as administrator to the machine where LMS 2.5 is installed.

Step 2 Install CS 3.0.3

1. Insert CS 3.0.3 CD

2. Run setup.exe from the CD-ROM root directory, for example, Z:\.

If you are upgrading from LMS 2.5 to LMS 2.5.1, you need not upgrade IPM 2.6.

After you complete installation of CS 3.0.3, the following message is displayed:

This server has the following application(s) installed:
RME 4.0.x CM 4.0.x DFM 2.0.x
The system might be unstable if you run the above versions of the 
application(s) along with CS 3.0.3
Ensure that you upgrade the applications to:
RME 4.0.3 CM 4.0.3 DFM 2.0.3

Step 3 Install RME 4.0.3.

1. Insert RME 4.0.3 CD

2. Run setup.exe from the CD-ROM root directory, for example, Z:\.

Step 4 Install Campus Manager 4.0.3.

1. Insert Campus Manager 4.0.3 CD

2. Run setup.exe from the CD-ROM root directory, for example, Z\:.

Step 5 Install DFM 2.0.3.

1. Insert DFM 2.0.3 CD

2. Run setup.exe from the CD-ROM root directory, for example, Z:\.

You need not run any scripts to migrate data. All necessary data is migrated to LMS 2.5.1 during the upgrade.

CiscoView device preferences are migrated inline from CiscoView 6.1 or CiscoView 6.1.1 to CiscoView 6.1.2 during the upgrade.


Remote Upgrade from LMS 2.5 to LMS 2.5.1 on Windows

To upgrade LMS 2.5 to LMS 2.5.1 on a different Windows machine:


Step 1 Login as administrator to the LMS 2.5 machine.

Step 2 Take backup of LMS 2.5 data for CS, RME, CM, and DFM.

Run the following command to backup data for LMS 2.5:

NMSROOT\bin\perl NMSROOT\bin\backup.pl BKP num_generations

For example:

C:\Program Files\CSCOpx\bin\perl C:\Program Files\CSCOpx\bin\backup.pl D:\ciscoworksbackup 2

Where,

NMSROOT—CiscoWorks installation directory (by default, SystemDrive:\Program Files\CSCOpx and SystemDrive is the Windows operating system installed directory)

BKP—Backup directory, the data will be stored in the directories BKP/0, BKP/1, and BKP/2 etc., where BKP/n stores the data of the (n+1)th generation.

num_generations—Maximum backup generations to be kept in the backup directory

Or

You can backup data using the Common Services 3.0 GUI (Server > Admin > Backup). Click Help, and follow the instructions to back up your data. If you do not have IPM or CiscoView installed, proceed to Step 5.

Step 3 Take backup of IPM data.

1. Backup the IPM Database using the command IPMServer\bin\ipm dbbackup to the following location:

IPM Server\Sybase\Backup 1 or Backup 2

Use the Backup 1 or Backup 2 folder whichever is latest.

2. Take backup of the following seed files:

IPMServer\etc\source

IPMServer\etc\target

IPMServer\etc\collector

3. Take backup of IPMServer\etc\ipm.env and IPMServer\etc\ipmDbPref.conf files.

4. Take backup of IPMServer\Server\htdocs\reports dir.

Where, IPMServer is IPM Install dir\Server

Step 4 Take backup of CiscoView Device Preferences.

Copy the file admin.preference from:

\CSCOpx\MDC\tomcat\webapps\CVng\WEB-INF\classes\cvuserprefs\ to a temporary location on the LMS 2.5.1 machine where the application is installed.

Step 5 Login as administrator to the remote machine where you want to install LMS 2.5.1.

Step 6 Install CS 3.0.3

1. Insert CS 3.0.3 CD.

2. Run setup.exe from the CD-ROM root directory, for example, Z:\.

After you complete installation of CS 3.0.3, the following message is displayed:

This server has the following application(s) installed:
RME 4.0.x CM 4.0.x DFM 2.0.x
The system might be unstable if you run the above versions of the 
application(s) along with CS 3.0.3
Ensure that you upgrade the applications to:
RME 4.0.3 CM 4.0.3 DFM 2.0.3

Step 7 Install RME 4.0.3.

1. Insert RME 4.0.3 CD.

2. Run setup.exe from the CD-ROM root directory, for example, Z:\.

Step 8 Install Campus Manager 4.0.3.

1. Insert Campus Manager 4.0.3 CD

2. Run setup.exe from the CD-ROM root directory, for example, Z:\.

Step 9 Install DFM 2.0.3.

1. Insert DFM 2.0.3 CD

2. Run setup.exe from the CD-ROM root directory, for example, Z:\.

Step 10 Install IPM 2.6.

1. Insert IPM 2.6 CD

2. Run setup.exe from the CD-ROM root directory, for example, Z:\.

Step 11 Stop the daemon manager by entering:

net stop crmdmgtd

Step 12 Migrate LMS 2.5 data for CS, RME, and Campus Manager by entering:

NMSROOT\bin\perl NMSROOT\bin\restorebackup.pl -d BKP -gen generationNumber-t temporary_directory

For example:

C:\Program Files\CSCOpx\bin\perl C:\Program Files\CSCOpx\bin\restorebackup.pl -d D:\ciscoworksbackup -gen 2 -t D:\tempciscoworksdata

Where,

NMSROOT—CiscoWorks installation directory (by default, SystemDrive:\Program Files\CSCOpx and SystemDrive is the Windows operating system installed directory).

BKP—Location where backup data is available

generationNumber— Backup version to be restored. By default, it is the latest generation. If generations 1 through 5 exist, then 5 will be the latest.

temporary_directory—The restore framework uses a temporary directory to extract the content of backup archive. By default the temporary directory is created under NMSROOT as NMROOT/tempBackupData. You can customize this, by using this -t option, where you can specify your own temp directory. This is to avoid overloading NMSROOT.

If you do not have IPM or CiscoView data to migrate, proceed to Step 14.

Step 13 Migrate IPM data.

1. Copy the data files that were backed up in LMS 2.5 to the respective directories in the LMS 2.5.1 machine.

2. Copy backed up IPM database and .db password from LMS 2.5 machine to the following location:

IPMServer\Sybase\Backup 1

3. Stop IPM processes by entering:

IPMServer\bin\ipmstop

4. Restore the data by entering:

IPMServer\bin\ipm dbrestore

5. Restart IPM processes by entering:

IPMServer\bin\ipmstart

Step 14 Migrate CiscoView Device Preferences.

Copy the file admin.preference from the temporary directory to the following location:

\CSCOpx\MDC\tomcat\webapps\CVng\WEB-INF\classes\cvuserprefs\

Step 15 Start the daemon manager by entering:

net start crmdmgtd


Validating the Upgrade License

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 of LMS or RWAN and validates the installation. In this case, Proof of Purchase (POP) validation is done automatically. 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 because it is a fresh installation on that machine. You will be prompted to run the validateupgrade utility from CLI after the installation. The product will be in the nag mode until POP is validated.

The validation for LMS upgrade license has to be performed only for DFM and RME. You do not need to perform this validation for Campus Manager and IPM.

This message appears till you complete the upgrade validation:

This software installation requires reusing a license provided in a 
previous version. If a previous license is not available or proof of 
purchase validation was not performed, you may continue to install in 
NAG mode, while arranging with your Cisco representative to return 
this product and purchase a full licensed version.

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 have to perform this validation separately for DFM and RME:

Validate the Upgrade License for RME on Solaris

Validating the Upgrade License for DFM on Solaris

Validate the Upgrade License for RME on Windows

Validating the Upgrade License for DFM on Windows

You can either:

Validate from a CD (older version)—If you have the previous version of the RME and DFM applications CDs, then you can mount the CD to CDROM drive and provide the absolute path to the drive.

Or

Validate from a remote server (older version)—If you have the previous version of RME and DFM applications installed and running in some other server, then this option can be selected. Enter the remote CiscoWorks server:

Host name or the IP address.

HTTP or HTTPS port number.

Login name.

Login password.

The remote server is contacted and the upgrade validation is 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.

Validate the Upgrade License for RME on Solaris

To validate the upgrade license for remote installation of RME 4.0.3 on Solaris:


Step 1 Go to C Shell by running the command csh.

Step 2 Set the environment using the command:

setenv LD_LIBRARY_PATH 
/opt/CSCOpx/objects/db/lib:/opt/CSCOpx/lib:/opt/CSCOpx/MDC/lib

Step 3 Change the directory to /opt/CSCOpx/bin using the command:

cd /opt/CSCOpx/bin

Step 4 Run the CLI script:

./validateupgrade

The following prompt appears:

This utility will validate your proof of purchase of the product and 
allow you to obtain an upgrade license.
Please enter the CiscoWorks product for the proof of purchase 
validation (such as LMS, ITEM, VMS):

Step 5 Enter the bundle name and press Return.

The following prompt appears:

Please select the source for upgrade validation from the following
1. Validate from a CD (older version of RME).
2. Validate from a remote server (where older version of RME is 
installed).
Please enter 1 to upgrade from a CD; enter 2 to upgrade from a remote 
server  [1 / 2] :

If you select 1, a prompt appears:

Please insert the previous versions of RME CD into the CDROM drive 
and provide the absolute path to the CD drive:

Enter the CDROM drive path. For example, /cdrom/cdrom0

If you select 2, a prompt appears:

Please enter the remote CiscoWorks server host name or the IP 
address : 
Please enter the remote CiscoWorks server http or https port 
number :
Please enter the remote CiscoWorks server login name :
Please enter the remote CiscoWorks server login password :
Please be patient. Upgrade validation is in progress from a remote 
server.

Step 6 Enter the following details of the remote CiscoWorks server:

Host name or the IP address. For example, ciscoworks-rme

http or https port number. For example, 1741 or 443

Login name. For example, admin

Login password.

This message appears after you enter the above details:

Please be patient. Upgrade validation is in progress from a remote 
server.

After the upgrade validation completes, this message appears:

Validation succeeded.


Validating the Upgrade License for DFM on Solaris

To validate the upgrade license for remote installation of DFM 2.0.3 on Solaris


Step 1 Change the directory to /opt/CSCOpx/bin using the command:

cd /opt/CSCOpx/bin

Step 2 Run the CLI script:

./dfmValidateUpgrade.sh 

The following prompt appears:

This utility will validate your proof of purchase of the product and 
allows you to obtain an upgrade license. 
Please select the source for upgrade validation from the following:
1. Validate from a CD (old version).
2. Validate from a remote server (old version).
Please enter option [1 / 2]: 

If you select 1, a prompt appears:

Please insert the previous versions of DFM CD into the CDROM drive 
and provide the absolute path to the CD drive:

Enter the CDROM drive path. For example, /cdrom/cdrom0

If you select 2, a prompt appears:

Please enter the remote CiscoWorks server host name or the IP 
address : 
Please enter the remote CiscoWorks server http or https port 
number   :
Please enter the remote CiscoWorks server login name :
Please enter the remote CiscoWorks server login password :
Please be patient. Upgrade validation is in progress from a remote 
server.

Step 3 Enter the following details of the remote CiscoWorks server:

Host name or the IP address. For example, dfm-host

http or https port number. For example, 1741

Login name. For example, admin

Login password.

This message appears after you enter the above details:

Please be patient. Upgrade validation is in progress from a remote 
server.

After the DFM upgrade validation completes, this message appears:

Validation succeeded.


Validate the Upgrade License for RME on Windows

To validate the upgrade license for remote installation of RME 4.0.3 on Windows:


Step 1 Go to the directory NMSROOT/bin using the command.

Where NMSROOT is the CiscoWorks installed directory.

Step 2 Run the CLI script:

validateupgrade.exe

The following prompt appears:

This utility will validate your proof of purchase of the product and 
allow you to obtain an upgrade license.
Please enter the CiscoWorks product for the proof of purchase 
validation (such as LMS, ITEM, VMS):

Step 3 Enter the bundle name and press Return.

The following prompt appears:

Please select the source for upgrade validation from the following
1. Validate from a CD (older version of RME).
2. Validate from a remote server (where older version of RME is 
installed).

Please enter 1 to upgrade from a CD; enter 2 to upgrade from a remote 
server  [1 / 2] :

If you select 1, a prompt appears:

Please insert the previous versions of RME CD into the CDROM drive 
and provide the absolute path to the CD drive:

Enter the CDROM drive path. For example, Z:

If you select 2, a prompt appears:

Please enter the remote CiscoWorks server host name or the IP 
address : 
Please enter the remote CiscoWorks server http or https port 
number   :
Please enter the remote CiscoWorks server login name :
Please enter the remote CiscoWorks server login password :
Please be patient. Upgrade validation is in progress from a remote 
server.

Step 4 Enter the following details of the remote CiscoWorks server:

Host name or the IP address. For example, ciscoworks-rme

http or https port number. For example, 1741

Login name. For example, admin

Login password.

This message appears after you enter the above details:

Please be patient. Upgrade validation is in progress from a remote 
server.

After the upgrade validation completes, this message appears:

Validation succeeded.


Validating the Upgrade License for DFM on Windows

To validate the upgrade license for remote installation of DFM 2.0.3 on Windows:


Step 1 Go to the directory NMSROOT/bin using the command.

Where NMSROOT is the CiscoWorks installed directory.

Step 2 Run the CLI script:

dfmValidateUpgrade.bat 

Where NMSROOT is the CiscoWorks installed directory.

The following prompt appears:

This utility will validate your proof of purchase of the product and 
allows you to obtain an upgrade license. 
Please select the source for upgrade validation:
1. Validate from a CD (old version).
2. Validate from a remote server (old version).
Please enter option [1 / 2]: 

If you select 1, a prompt appears:

Please insert the previous versions of DFM CD into the CDROM drive 
and provide the absolute path to the CD drive:

Enter the CDROM drive path. For example, Z:

If you select 2, a prompt appears:

Please enter the remote CiscoWorks server host name or the IP 
address : 
Please enter the remote CiscoWorks server http or https port 
number   :
Please enter the remote CiscoWorks server login name :
Please enter the remote CiscoWorks server login password :
Please be patient. Upgrade validation is in progress from a remote 
server.

Step 3 Enter the following details of the remote CiscoWorks server:

Host name or the IP address. For example, dfm-host

http or https port number. For example, 1741

Login name. For example, admin

Login password.

This message appears after you enter the above details:

Please be patient. Upgrade validation is in progress from a remote 
server.

After the DFM upgrade validation completes, this message appears:

Validation succeeded.


Getting Started with CiscoWorks LMS

The topics in this section help you to work with and understand the LMS user interface. Before you start using the LMS 2.5.1 applications, you must ensure that:

The network devices that interact with LMS 2.5.1 must be set up correctly.

See the Setting Up Devices on the Network chapter in the Cisco LAN Management Solution 2.5 Deployment Guide:

http://www.cisco.com/application/pdf/en/us/guest/products/ps2425/c1244/
cdccont_0900aecd8026ee8d.pdf

The license file is installed on your CiscoWorks server.

See "Licensing Your Product" section.

The following sections help you to get started only with CiscoWorks LMS in a single-server mode.

If you have a setup with multiple CiscoWorks servers, you must:

Set up Peer Server Account

Set up System Identity Account

Set up Peer Server Certificate

Enable Single Sign-On

To get started with multiple-server mode, see the Configuring the Server section in the User Guide for User Guide for CiscoWorks Common Services 3.0.3.

These topics describe how to get started with CiscoWorks LMS:

"Changes from LMS 2.1 or LMS 2.2 to LMS 2.5.1" section

"Invoking the CiscoWorks Homepage" section

"Logging In" section

"Understanding the CiscoWorks Homepage" section

"Configuring LMS Administration Parameters" section

"Managing Devices in CiscoWorks Server" section

"Editing Device Credentials" section

"Performing Maintenance on Your CiscoWorks Server" section

"Launching LMS Applications Online Help" section

"Using Applications in ACS Mode" section

"Uninstalling LMS" section

Changes from LMS 2.1 or LMS 2.2 to LMS 2.5.1

The LMS 2.5.1 provides:

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

A new Common Services Device and Credentials Repository which enables sharing of devices credentials among all CiscoWorks family of products. This provides a central place for management of devices and their credentials.

The Common Services application maintains all of the devices and their credentials details in a single repository.

In LMS 2.5.1, you have to add devices in Common Services. These devices get added automatically in CM, DFM and RME. You have to manually add devices to IPM. See the "Managing Devices in CiscoWorks Server" section for more details.

To know more about the changes in LMS 2.5.1, see:

How is DFM 2.x Different from DFM 1.2.x? chapter in the Installation and Setup Guide for Device Fault Manager 2.0.3 document for DFM changes.

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

Navigational Changes from 3.x to 4.x chapter in the Installation and Setup Guide for Resource Manager Essentials 4.0.3 document for RME changes.

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

Changes and Enhancements in Campus Manager 4.0.3 chapter in the Installation and Setup Guide for Campus Manager 4.0.3 for Campus Manager changes.

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

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.

For example:

http://ciscoworksserver:1741


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

Enter the same admin password that you entered while installing Common Services 3.0.3

Step 2 Click Login.

The CiscoWorks Homepage appears.


Understanding the CiscoWorks Homepage

Figure 4 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.3.

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 "Launching LMS Applications Online Help" section.

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

Configuring LMS Administration Parameters

After you have installed the required applications and verified the installations, you must perform the following administrative tasks:

Common Services

The administrative tasks for Common Services are:

Manage the CiscoWorks users. You can perform this task using Common Services > Server > Security > Local User Setup.

Configure the Browser-Server Security. Common Services Server uses Secure Socket Layer (SSL) encryption to provide secure access between the client browser and management server and also between the management server and devices.

You can enable or disable SSL depending on the need to use secure access. You can perform this task using Common Services > Server > Security > Browser-Server Security Mode Setup.

Configure the SMTP server to receive e-mails from the CiscoWorks server. You can perform this task using Common Services > Server > Admin > System Preferences.

Configure the Cisco.com credentials. This information is used while performing some tasks such as downloading software images, downloading device packages, etc. You can perform this tasks using Common Services > Server > Security > Cisco.com Connection Management > Cisco.com User Account Setup.

Configure the proxy URL to access the Internet from the CiscoWorks server, if your system is behind a firewall. You can this task using Common Services > Server > Security > Cisco.com Connection Management > Proxy Server Setup.

See the Online help or User Guide for CiscoWorks Common Services 3.0.3.

Resource Manager Essentials

The administrative tasks for Resource Manager Essentials are:

Configure the protocol order for:

Network administrators can assign the protocols to be used in RME for Configuration Management and Software Management.

To define the protocol order for fetching and deploying the configuration files use Resource Manager Essentials > Admin > Config Mgmt.

The available protocols are Telnet, TFTP, RCP, SSH, SCP, and HTTPS.

To define the protocol order for Software image import and distribution use Resource Manager Essentials > Admin > Software Mgmt > View/Edit Preferences.

The supported protocols are: RCP, TFTP, SCP and HTTP.

Schedule periodic archive of configuration files (with and without configuration polling). By default, this is disabled. You can enable this using Resource Manager Essentials > Admin > Config Mgmt > Archive Mgmt > Collection Settings.

By default, the device inventory collection and polling are scheduled. You can change the schedule by selecting Resource Manager Essentials > Admin > Inventory > System Job Schedule.

See the Online help or User Guide for Resource Manager Essentials 4.0.3.

Campus Manager

The administrative tasks for Campus Manager are:

Schedule Campus Manager data collection.

You can schedule the day, time, and frequency of data collection.

You can define the periodicity for polling the network. Polling helps you to see updated devices and link information without running data collection. Polling is enabled by default. The default poll interval is 2 hours.

You can perform this task by selecting Campus Manager > Administration. Click Admin and select Campus Data Collection > Schedule Data Collection.

Set up Data Collection Filters

You can specify VTP Domains or IP Address ranges for data collection using the Campus Data Collection > Data Collection Filters.

Configure User Tracking acquisition actions.

User Tracking allows you to locate end-user hosts in the network. It collects and presents information gathered by the Asynchronous Network Interface (ANI) Server and held in the ANI database. You can also use User Tracking to find duplicate connections that could indicate potential problems in your network.

To configure this select Campus Manager > User Tracking and click Acquisition > Actions.

See the Online help or User Guide for Campus Manager 4.0.3.

Device Fault Manager

The administrative tasks for Device Fault Manager are:

Adjust polling and threshold settings.

The Common Services system-defined groups include groups such as Broadband Cable, Routers, Switches and Hubs, and so forth. These groups have specific polling and threshold settings. The DFM Polling and Threshold function creates its own corresponding groups based on Common Services and DFM groups: These are:

Polling groups that determine how often group members are polled for data.

Threshold groups that determine acceptable levels of performance and utilization for group members.

You can perform this task using Device Fault Manager > Configuration > Polling and Thresholds.

Set up notifications.

In addition to watching network conditions as they change on the Alerts and Activities display, you can use DFM notification services to automatically notify users and other systems when specific changes occur on selected devices. To do so, you must create subscriptions for e-mail notifications, DFM-generated SNMP trap notifications, or Syslog notifications.

You can also change event names to names that are more meaningful to you, and these names will be reflected in the DFM displays and notifications.

You can perform this task using Device Fault Manager > Notification Services.

Add views to the Alerts and Activities Display.

The Alerts and Activities display provides a consolidated real-time view of the operational status of your network. When a fault occurs in your network, DFM generates an event (or events). Events are rolled up into alerts, one alert for each device with a fault.

You can perform this task using Configuration > Other Configurations > Alerts and Activities Defaults.

See the Online help or User Guide for Device Fault Manager 2.0.3.

Managing Devices in CiscoWorks Server

The Device and Credential Repository (DCR) is a common repository of devices, their attributes, and credentials, meant to be used by various network management applications. The Device and Credential Admin (DCA) provides an interface to administer DCR.

DCR helps multiple applications share device lists and credentials using a client-server mechanism, with secured storage and communications. The applications can read or retrieve the information. The applications can also update the information in DCR so that the updated information could be shared with other applications. DCR:

Stores device attributes and credentials, permits dynamic creation of attribute types, and permits default grouping and filtering.

Supports proxy device attributes, unreachable devices, and pre-provisioning of devices.

Allows you to populate the repository. You can import devices from many sources. You can export device data that you can use with third-party network management systems such as, HP Network Node Manager and Netview.

Uses a unique Internal Device Identifier to access device details, and detects duplicate devices based on specific attributes.

Encrypts credential data stored in the repository. Access to device data is permitted only by secured channel and client authentication.

Supports IPv6 and SNMP v3.

You must first add devices in Common Services. These devices get added automatically in CM, DFM and RME. You have to manually add devices to IPM.

These topics describe how to add devices to the CiscoWorks Server:

"Adding Devices to DCR Using Campus Manager Device Discovery" section

or

"Adding Devices to DCR Using Common Services Device and Credential Admin" section

"Adding Devices to IPM" section

Figure 5 shows the Common Services Device Management Window. From this window, you can:

Add devices

Import device list (File, Local NMS, and Remote NMS)

Exclude devices while adding/importing devices

Edit device credentials

View the device list

Export device credentials

Delete devices

Figure 5 Common Services Device Management Page

To learn how to add devices to DCR, see either of these sections:

Adding Devices to DCR Using Campus Manager Device Discovery

Adding Devices to DCR Using Common Services Device and Credential Admin

Adding Devices to DCR Using Campus Manager Device Discovery

To discover the network, the Device Discovery process needs the SNMP credentials of the devices in the network and the IP address for the seed device. The following are some key facts about Device Discovery:

Device Discovery performs Network Discovery using the Cisco Discovery Protocol as the discovery mechanism.

Device Discovery determines the management IP address of the device.

Devices in DCR and user-configured seed devices from Campus Manager are used by the Device Discovery process. It populates the Device and Credentials Repository with the following discovered information:

Host name, Domain name, Management IP address, Display name, and sysObjectID

SNMPv2 read-only community string (if SNMPv2 was used for communicating with the device)

SNMPv3 user ID, password, engineID, authorization algorithm (if SNMPv3 was used for communicating with the device).

Device Discovery does not update SNMPv2 write community string.

To configure Device Discovery:


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

A new Campus Administration page appears. (See Figure 6.)

Figure 6 Campus Manager Administration Page

Step 2 Select 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.

You must separate the seed devices stored in the file with a carriage return. That is, only one seed device can be stored in each 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

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


Adding Devices to DCR Using Common Services Device and Credential Admin

The Device Management option in Device and Credential Admin (DCA) helps you manage the list of devices and their credentials.

To add a device:


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

The Device Management page appears.

The Device Management UI 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

CNS Managed Type

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


To import bulk of devices:


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 the "Importing and Devices and Credentials" Online help or "Managing Devices" section of the User Guide for CiscoWorks Common Services 3.0.3.


Adding Devices to IPM

You must manually import devices to IPM to manage devices. You can perform this task by selecting Internetwork Performance Monitor > Admin > Import From Device and Credential Repository.


Note There is no mechanism to import only selected devices from DCR into IPM. All the devices in DCR will be imported into IPM. Any devices in DCR that cannot be an IPM source are not added. The import log file will contain error message for the devices that are not added.


You can import devices as:

Sources

When you import devices as Sources, IPM contacts the device and adds them only if they are running IOS image with IP SLA feature and if the Read and Write community strings are provided.

Target IP SLA responders

When devices are imported as Target IP SLA Responders, if the device has a read community string, IPM verifies whether the IP SLA responder is enabled on the target. If there is no read community string, the target's IP SLA responder status is not verified.

Target IP devices

When you import devices as Target IP Devices, IPM adds the device without either contacting the device or making any verification. When you import devices from the Device and Credentials Repository, if the devices already exist in IPM, they are updated.

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

Editing Device Credentials

After adding/importing the devices to DCR, you can edit the device credentials such as, SNMP RO, SNMP RW, username, password, etc.

You can edit the credentials for a single device or bulk of devices using the Common Services Device Management Window.

To edit the device credentials for a single device:


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

The Device Management page appears.

Step 2 Select the devices from the CS@CiscoWorks_Server device group. Where, CiscoWorks_Server is the CiscoWorks server name.

Step 3 Click Edit

The Device Properties dialog box appears.

The Devices pane lists all devices selected. From the Devices pane, you should separately select each device that you need to edit.

Step 4 Select the device from the Devices pane.

The current attributes are automatically populated in the device information fields.

Step 5 Edit the device information you want to, in the respective fields.

For more information, see the "Editing Device Credentials" Online help or the "Managing Devices" section of the User Guide for CiscoWorks Common Services 3.0.3.

Step 6 Click Finish.


To edit device credentials for the bulk of devices:


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

The Device Management page appears.

Step 2 Click Export.

The Device Export popup window appears.

Step 3 Select Select from Device Selector from the Device Selection Method pane.

Step 4 Select devices from the Device Selector pane.

Step 5 Browse the file system and select the location for the output file using the Browse button in the Output File Information.

Step 6 Select CSV or XML file formats as required.

Step 7 Select Immediate as the Run Type in the Scheduling pane.

Step 8 Click OK.

Edit the device credentials in the exported device file.

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

The Device Management page appears.

Step 10 Click Bulk Import.

The Import Devices popup window appears.

Step 11 Select File in the Select a Layer pane.

Step 12 In the File Information pane,

1. Select the edited device file.

2. Select the CSV or XML file formats as specified while exporting the file.

3. Select Use Data from Import Source as the Conflict Resolution Option.

Step 13 Select Immediate as the Run Type in the Scheduling pane.

Step 14 Click Import.

In the Import Status window, the edited device list appears under Duplicate Devices. However, the edited device credentials are updated in the DCR.


Performing Maintenance on Your CiscoWorks Server

As a administrator you need to perform maintenance to keep your information updated and to get rid of unnecessary or outdated reports and data on the system.

The CiscoWorks server maintenance tasks include:

"Performing Regular Backups" section

"Purging the Data" section

"Maintaining the Log Files" section

Performing Regular Backups

You can schedule immediate, daily, weekly, or monthly automatic database backups. You should back up the database regularly so that you have a safe copy of the database. Common Services uses multiple databases to store client application data. These databases are backed up whenever you perform a backup.

To backup data:


Step 1 From the CiscoWorks Homepage, select Common Services > Server > Admin > Backup.

The Set Backup Schedule dialog box appears.

Step 2 Enter the following:

Backup Directory—Location of the backup directory. We recommend that your target location be on a different partition than where CiscoWorks is installed.

Generations—Maximum number of backups to be stored in the backup directory.

Time—From the lists, select the time period between which you want the backup to occur. Use a 24-hour format.

The Time field is not enabled if you have selected Immediate as the Frequency.

Frequency—Select the backup schedule:

Immediately—The database is backed up immediately

Daily— The database is backed up every day at the specified time.

Weekly—The database is backed up once a week on the specified day and time. Select a day from the Day of week list.

Monthly—The database is backed up once a month on the specified day and time. Select a day from the Day of month list.

Step 3 Click Apply.

The Schedule Backup message verifies your schedule and provides the location of backup log files.

You can verify backup status by examining the log file at the following location:

On Solaris:

var/adm/CSCopx/log/dbbackup.log

On Windows:

NMSROOT/log/dbbackup.log

Where NMSROOT is the CiscoWorks installed directory.


To restore the backup data, see the Restoring Data Online help or the "Configuring the Server" section of the User Guide for CiscoWorks Common Services 3.0.3

Purging the Data

Every LMS application has its own purge policies. You can define these polices by performing these tasks:

RME

You can purge RME data by performing these tasks:

To purge the archived configurations, select
Resource Manager Essentials > Administration > Config Mgmt > Archive Mgmt > Purge Settings

To purge the Syslog messages, select
Resource Manager Essentials > Administration > Syslog > Set Purge Policy

To purge the Change Audit data, select
Resource Manager Essentials > Administration > ChangeAudit > Set Purge Policy

To schedule purge operations for the RME jobs, select
Resource Manager Essentials > Admin > System Preferences > Job Purge

Campus Manager

You can purge Campus Manager data by performing these tasks:

To delete end hosts and IP phones from User Tracking either on demand or on a specified interval after major acquisition, select
Campus Manager > User Tracking > Admin > Acquisition > Delete Interval

To purge archives or jobs older than a particular date, select
Campus Manager > User Tracking > Admin > Reports > User Tracking Purge Policy

Device Fault Manager

To set up a purge schedule for fault history information, select
Device Fault Manager > Configuration > Other Configuration > Daily Purging Schedule

Maintaining the Log Files

The Logrot utility helps you manage the log files in a better fashion. Logrot is a log rotation program that can:

Rotate log when CiscoWorks is running.

Optionally archive and compress rotated logs.

Rotate log only when it has reached a particular size.

Logrot helps you add new files easily. Logrot should be installed on the same machine where you have installed Common Services.

To configure and run logrot tool, see the "Configuring the Server" section in the User Guide for CiscoWorks Common Services 3.0.3.

Launching LMS Applications Online Help

On the CiscoWorks Homepage, click Help to Launch the CiscoWorks online help. This Help button is available at the top right corner of your CiscoWorks home page. The CiscoWorks online Help is launched in a separate browser window.

The CiscoWorks online Help window contains the following buttons and links:

Button
Description

Contents

(Button)

Displays the online help table of content for the launched LMS application.

That is, if you have launched Common Services Online help, the table of content for the Common Services application appears.

Index

(Button)

Displays the index entries for the launched LMS application.

That is, if you have launched Common Services Online help, the index entries for the Common Services application appears.

Search

(Button)

Allows you search any key words within the launched LMS application.

That is, if you have launched Common Services Online help, you can search for any keywords within the Common Services online help.

If you want to search key words in all of the installed LMS application, you must select All in the application drop-down box (second drop-down box).

If you want to search key words in specific LMS application, you must select the application name in the application drop-down box (second drop-down box).

That is, if you want to search in RME, select Resource Manager Essentials from application drop-down box.

Main

(Link)

This link is available in the top right corner of the CiscoWorks online Help window. See Figure 7 for details.

Launches the homepage of LMS applications online help.

Based on your LMS installed applications, the table of content area lists the LMS application Online help. See Figure 8 for details.

If you have installed all the LMS applications, the table of content lists the following:

Campus Manager—Launches the Campus Manager online help.

CiscoWorks Common Services—Launches the Common Services online help

Device Fault Manager—Launches the Device Fault Manager online help.

Device Manager—Launches the CiscoView application (Basic) and CiscoView device packages (ATM Manager, AP1100, Catalyst 4000 IOS, etc.) online help.

Internetwork Performance Monitor—Launches the Internetwork Performance Monitor online help.

Resource Manager Essentials—Click this to launch Resource Manager Essentials application (RME User Guide) and device packages (Cisco 10000 Series Routes, Cisco 2600XM Multiservice Router, etc.) online help.

About

(Link)

This link is available in the top right corner of the CiscoWorks online Help window.

Launches the Using Help page. This page describes how to use Help to find the information you need.


Figure 7 Launching LMS Application Online Help

Figure 8 Online Help Homepage

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, 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. Cisco Secure ACS uses the TACACS+ and RADIUS protocols to provide AAA services that ensure a secure environment.

With CiscoWorks and CiscoSecure ACS integration, you can provide device level authorization. This device level authorization allows you to authorize only selected users to perform certain tasks such as configuration updates and software image updates.

When the CiscoWorks server is in the ACS Login mode, a new device group, Secure Views is created. This allows you to perform a task on a device or restrict a set of device. Secure Views enable filtering of group membership based on the user and the application task context in which a request is made. Filtering is performed only when operating in ACS Login mode. While operating in non-ACS mode, no filtering is performed and evaluating a group results in all devices that group being returned.

The following are the supported Cisco Secure ACS for Windows versions:

Cisco Secure ACS 3.2

Cisco Secure ACS 3.2.3

Cisco Secure ACS 3.3.2

Cisco Secure ACS 3.3.3 (appliance/software)

Cisco Secure ACS 4.0(1) (software)

Configuring ACS

Configure ACS after all applications are installed. If you have installed an application after configuring the CiscoWorks Login Module to the ACS mode, then the users of that application are not granted any permissions. You have to configure this manually in Cisco Secure ACS server. However, the application except IPM is registered to Cisco Secure ACS.

To register IPM to Cisco Secure ACS, you have to run this command:

On Solaris:

/opt/CSCOpx/bin/perl /opt/CSCOpx/bin/AcsRegCli.pl -register ipm

On Windows:

NMSROOT\bin\perl NMSROOT\bin\AcsRegCli.pl -register ipm

Where, NMSROOT is the CiscoWorks installed directory.

For example:

C:\Program Files\CSCOpx\bin\perl C:\Program Files\CSCOpx\bin\AcsRegCli.pl -register ipm


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

The System Identity user needs to be configured in ACS, with all the privileges the user has in CiscoWorks.

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 must create new roles for each of the LMS applications that are running on the CiscoWorks server.

For example, if you have configured 10 CiscoWorks servers with an ACS server and you have created a role in RME (for instance, RMESU), this role is shared for the RME application that runs on all 10 CiscoWorks servers.

If ACS is in HTTPS mode, you must enable ACS communication on HTTPS. 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.

Integrating and Registering LMS Applications to the ACS

Follow the steps as described in the Integrating with the ACS Server chapter of the CiscoWorks Common Services 3.0.3 white paper. This white paper is available at this location:

http://www.cisco.com/en/US/products/sw/cscowork/ps2425/
prod_white_papers_list.html

Uninstalling LMS

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

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

Frequently Asked Questions

Q. On which operating system is LMS 2.5.1 supported?

A. See Server and Client System Requirements for details.

Q. Which Windows HotFix patches are supported for LMS 2.5.1?

A. For LMS 2.5.1, we have tested all of the Windows HotFix patches that were released in:

October, 2005

http://www.microsoft.com/technet/security/bulletin/ms05-oct.mspx

November, 2005

http://www.microsoft.com/technet/security/bulletin/ms05-nov.mspx

Q. What is the difference between LMS migration and upgrade?

A. Migration involves migrating data from an older version of LMS to a newer version of LMS. The steps for migration include:

a. Backing up the older version of LMS data.

b. Installing the newer version of LMS.

c. Restoring the backed up data.

See "Migrating from LMS and RWAN to LMS 2.5.1" section for details on LMS versions that can migrated.

Upgrade refers overwriting the existing LMS version with the new LMS version. The data may be migrated to the newer version based on the installed LMS application.

See "Upgrading from LMS and RWAN to LMS 2.5.1" section for details on LMS versions that can upgraded.

Q. Is LMS 2.5.1 supported on 64-bit native systems?

A. No, LMS 2.5.1 is not supported on any native 64-bit systems.

Q. Can I install LMS 2.5.1 with Terminal Services enabled?

A. You can install LMS 2.5.1 applications on a system with Terminal Services enabled in Remote Administration mode. However, installation of LMS 2.5.1 applications on a system with Terminal Services enabled in Application mode is not supported.

If you have a enabled Terminal Server in Application mode, disable the Terminal Server, reboot the system, and start the installation again.

See Installation and Setup Guide for CiscoWorks Common Services 3.0.3 (Includes CiscoView) on Windows:

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

Q. Can I install LMS 2.5.1 with Internet Information Services (IIS) enabled?

A. No, you must disable IIS services before installing LMS 2.5.1

Q. Does LMS 2.5.1 support virtual machines, such as VMware and VirtualPC?

A. LMS 2.5.1 does not support virtual machines, such as VMware and VirtualPC.

Q. Can I install LMS 2.5.1 with Windows Domain Controller enabled?

A. No, you must disable Windows Domain Controller before installing LMS 2.5.1.

Q. Which TCP and UDP ports LAN Management Solution 2.5.1 uses?

A. See Table 8, LAN Management Solution Port Usage for details.

Q. Is LMS 2.5.1 supported on Solaris x86 (on the x86 CPU)?

A. No, LMS 2.5.1 is not supported on Solaris x86.

Q. Is LMS 2.5.1 supported on multi-homed server?

A. Yes, LMS 2.5.1 is supported on multi-homed server.

A multi-homed machine is a machine that has multiple NIC cards, each configured with different IP addresses. To run CiscoWorks Common Services on a multi-homed machine, there are two requirements.

All IP addresses must be configured in DNS.

Owing to restrictions with CORBA, only one IP address can be used by the client or browser to access the server. You must select one IP address as the external address, with which the client will login to the CiscoWorks server.

See Release Notes for CiscoWorks Common Services 3.0.3 (Includes CiscoView):

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

Q. How do I check the version of LMS 2.5.1?

A. You can check the application versions by selecting Common Services > Software Center > Software Update. For LMS 2.5.1 installation, the application versions are:

CiscoWorks Common Services 3.0.3

Campus Manager 4.0.3

CiscoView 6.1.2

Device Fault Manager 2.0.3

Integration Utility 1.6.0

Internetwork Performance Monitor 2.6.0

Resource Manager Essentials 4.0.3

If you have installed licensed version of LMS 2.5.1, you can check the LMS version in Bundles Installed table (Common Services > Software Center > Software Update). The LMS version should be 2.5.

Q. Can I migrate data from Solaris to Windows and vice versa?

A. No, you cannot migrate data between operating systems.

Q. I am currently using licensed version of LMS 2.5.1 on Solaris. I want to migrate to Windows. Do I need to get a new license for LMS 2.5.1 on Windows?

A. No, you can use the same LMS 2.5.1 Solaris license on Windows.

Q. I am currently using LMS 2.2 on Windows 2000 server. I want to upgrade my operating system to Windows 2003 server. Should I upgrade the LMS first or upgrade the operating system?

A. It is recommended to upgrade the LMS 2.2 to LMS 2.5.1 on Windows 2000 server before upgrading the operating system to Windows 2003 server.

Q. When should I install other Network Management Systems (such as HP OpenView Network Node Manager, Netview)?

A. You must install other Network Management Systems before installing the LAN Management Solution.

Q. I have configured CiscoWorks server in ACS mode. Why am I unable to view all of the devices in CiscoWorks server?

A. To manage devices in CiscoWorks server, you must configure the devices in Cisco Secure ACS server too. You can view the list of devices that are not configured in the Cisco Secure ACS server using Devices that are not configured in ACS Report. You can generate this report by selecting Common Services > Device and Credentials > Reports. This report is available only after configuring CiscoWorks with Cisco Secure ACS server.

Q. What is the replacement product for nGenius Real-Time Monitor (RTM)?

A. The nGenius Real-Time Monitor (RTM) application offered in previous releases of LMS is no longer included in version 2.5.1. Additional details about RTM's end-of-sale and end-of-life announcements can be found here:

http://www.cisco.com/en/US/products/sw/cscowork/ps2803/prod_eol_notice0900aecd8015f31d.html

Q. When is the next release of CiscoWorks Routed WAN Management Solution (RWAN)?

A. The CiscoWorks RWAN solution is EOLed (end-of-life).

The CiscoWorks Internetwork Performance Monitor (IPM), previously offered in the CiscoWorks Routed WAN Management Solution (RWAN), has been added to the LMS 2.5.1 release.

Additional details about CiscoWorks RWAN end-of-sale and end-of-life announcements can be found using the information to follow:

http://www.cisco.com/en/US/products/sw/cscowork/ps2426/
prod_eol_notice0900aecd800fcd3d.html

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.


The CiscoWorks LAN Management Solution 2.5.1 related documents are available in the HTML and PDF formats on Cisco.com at:

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


Note To view documents in Adobe Portable Document Format (PDF), Adobe Acrobat 4.0 or later is required.


To review the known product bugs (DDTS), see the LMS 2.5.1 application Release Notes. This is available:

In the LMS 2.5.1 product package

On the LMS 2.5.1 application product CD. This is provided as PDF in the Documentation folder on the application CD-ROM.

On Cisco.com

On the Cisco Documentation CD-ROM

To perform a Typical or Custom installation, see the LMS 2.5.1 application Installation and Setup Guides. This is available:

On the LMS 2.5.1 application product CD. This is provided as a PDF document in the Documentation folder on the application CD-ROM.

On Cisco.com

On the Cisco Documentation CD-ROM

To understand the features, to perform the tasks, and to troubleshoot, see the LMS 2.5.1 application User Guide. This is available:

On the LMS 2.5.1 application product CD. This is provided as a PDF document in the Documentation folder on the application CD-ROM.

In the CiscoWorks online help. From the CiscoWorks Homepage, click Help.

On Cisco.com

On the Cisco Documentation CD-ROM

To know the list of supported devices, see the LMS 2.5.1 application Supported Device tables. This is available only on Cisco.com.

LAN Management Solution 2.5.1

The following are the available user documents for LAN Management Solution 2.5.1:

Quick Start Guide for LAN Management Solution 2.5.1

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

Data Migration Guide for LAN Management Solution 2.5.1

All the above documents are available in the LMS 2.5.1 product package and also on Cisco.com at this URL:

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

Cisco LAN Management Solution 2.5 Deployment Guide:

http://www.cisco.com/application/pdf/en/us/guest/products/ps2425/c1244/cdccont_0900aecd8026ee8d.pdf

Cisco LAN Management Solution Data Sheets, White Papers, etc:

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

Common Services 3.0.3 (Including CiscoView 6.1.2)

The following are the available user documents for Common Services 3.0.3 (including CiscoView 6.1.2):

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

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

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

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

Using CiscoView 6.1 (DOC-7817225=)

User Guide for CiscoWorks Common Services 3.0.3 (DOC-7817182=)

User Guide for CiscoWorks Integration Utility 1.6

All these documents are available on Cisco.com at this URL:

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

Resource Manager Essentials 4.0.3

The following are the available user documents for RME 4.0.3:

Release Notes for Resource Manager Essentials 4.0.3 on Solaris

Release Notes for Resource Manager Essentials 4.0.3 on Windows

Installation and Setup Guide for Resource Manager Essentials 4.0.3 on Solaris (DOC-7817222=)

Installation and Setup Guide for Resource Manager Essentials 4.0.3 on Windows (DOC-7817223=)

User Guide for Resource Manager Essentials 4.0.3 (DOC-7817221=)

Supported Device Table for Resource Manager Essentials 4.0.3

All these documents are available on Cisco.com at this URL:

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

The RME 4.x Troubleshooting Tips and FAQs is available at this URL:

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

Campus Manager 4.0.3

The following are the available user documents for Campus Manager 4.0.3:

Release Notes for Campus Manager 4.0.3 on Solaris

Release Notes for Campus Manager 4.0.3 on Windows

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

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

User Guide for Campus Manager 4.0.3 (DOC-7817186=)

Supported Device Table for Campus Manager 4.0.3

All these documents are available on Cisco.com at this URL:

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

Device Fault Manager 2.0.3

The following are the available user documents for DFM 2.0.3:

Release Notes for Device Fault Manager 2.0.3 on Solaris

Release Notes for Device Fault Manager 2.0.3 on Windows

Installation Guide for Device Fault Manager 2.0.3 on Solaris (DOC-7817162=)

Installation Guide for Device Fault Manager 2.0.3 on Windows (DOC-7817163=)

User Guide for Device Fault Manager (DOC-7817161=)

Supported Devices Table for Device Fault Manager 2.0.3

All these documents are available on Cisco.com at this URL:

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

Internetwork Performance Monitor 2.6

The following are the available user documents for IPM 2.6:

Release Notes for Internetwork Performance Monitor 2.6

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

User Guide for Internetwork Performance Monitor (DOC-7816652=)

All these documents are available on Cisco.com at this URL:

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

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/techsupport

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

Product Documentation DVD

Cisco documentation and additional literature are available in the Product Documentation DVD package, which may have shipped with your product. The Product Documentation DVD is updated regularly and may be more current than printed documentation.

The Product Documentation DVD is a comprehensive library of technical product documentation on portable media. The DVD enables you to access multiple versions of hardware and software installation, configuration, and command guides for Cisco products and to view technical documentation in HTML. With the DVD, you have access to the same documentation that is found on the Cisco website without being connected to the Internet. Certain products also have .pdf versions of the documentation available.

The Product Documentation DVD is available as a single unit or as a subscription. Registered Cisco.com users (Cisco direct customers) can order a Product Documentation DVD (product number DOC-DOCDVD=) from Cisco Marketplace at this URL:

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

Ordering Documentation

Beginning June 30, 2005, registered Cisco.com users may order Cisco documentation at the Product Documentation Store in the Cisco Marketplace at this URL:

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

Nonregistered Cisco.com users can order technical documentation from 8:00 a.m. to 5:00 p.m. (0800 to 1700) PDT by calling 1 866 463-3487 in the United States and Canada, or elsewhere by calling 011 408 519-5055. You can also order documentation by e-mail at tech-doc-store-mkpl@external.cisco.com or by fax at 1 408 519-5001 in the United States and Canada, or elsewhere at 011 408 519-5001.

Documentation Feedback

You can rate and provide feedback about Cisco technical documents by completing the online feedback form that appears with the technical documents on Cisco.com.

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

Cisco Product Security Overview

Cisco provides a free online Security Vulnerability Policy portal at this URL:

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

From this site, you can perform these tasks:

Report security vulnerabilities in Cisco products.

Obtain assistance with security incidents that involve Cisco products.

Register to receive security information from Cisco.

A current list of security advisories and notices for Cisco products is available at this URL:

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

If you prefer to see advisories and notices as they are updated in real time, you can access a Product Security Incident Response Team Really Simple Syndication (PSIRT RSS) feed from this URL:

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

Reporting Security Problems in Cisco Products

Cisco is committed to delivering secure products. We test our products internally before we release them, and we strive to correct all vulnerabilities quickly. If you think that you might have identified a vulnerability in a Cisco product, contact PSIRT:

Emergencies — security-alert@cisco.com

An emergency is either a condition in which a system is under active attack or a condition for which a severe and urgent security vulnerability should be reported. All other conditions are considered nonemergencies.

Nonemergencies — psirt@cisco.com

In an emergency, you can also reach PSIRT by telephone:

1 877 228-7302

1 408 525-6532


Tip We encourage you to use Pretty Good Privacy (PGP) or a compatible product to encrypt any sensitive information that you send to Cisco. PSIRT can work from encrypted information that is compatible with PGP versions 2.x through 8.x.

Never use a revoked or an expired encryption key. The correct public key to use in your correspondence with PSIRT is the one linked in the Contact Summary section of the Security Vulnerability Policy page at this URL:

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

The link on this page has the current PGP key ID in use.


Obtaining Technical Assistance

Cisco Technical Support provides 24-hour-a-day award-winning technical assistance. The Cisco Technical Support & Documentation website on Cisco.com features extensive online support resources. In addition, if you have a valid Cisco service contract, Cisco Technical Assistance Center (TAC) engineers provide telephone support. If you do not have a valid Cisco service contract, contact your reseller.

Cisco Technical Support & Documentation Website

The Cisco Technical Support & Documentation 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, at this URL:

http://www.cisco.com/techsupport

Access to all tools on the Cisco Technical Support & Documentation 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 & Documentation 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 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 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.

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, documentation, and logo merchandise. Visit Cisco Marketplace, the company store, at this URL:

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

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

or view the digital edition at this URL:

http://ciscoiq.texterity.com/ciscoiq/sample/

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

Networking products offered by Cisco Systems, as well as customer support services, can be obtained at this URL:

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

Networking Professionals Connection is an interactive website for networking professionals to share questions, suggestions, and information about networking products and technologies with Cisco experts and other networking professionals. Join a discussion at this URL:

http://www.cisco.com/discuss/networking

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