CiscoWorks LAN Management Solution

Table Of Contents

Quick Start Guide for LAN Management Solution 2.5

SUPPLEMENTAL LICENSE AGREEMENT

LAN Management Solution 2.5 Overview

Licensing

Understanding Licensing Terms

Licensing Your Product

LMS Package Contents

Additional Information Online

Server and Client System Requirements

Solaris Patches for LAN Management Solution

LAN Management Solution Port Usage

Installation Paths

Upgrade Options

Installing LAN Management Solution 2.5

Prerequisites

Important Installation Notes

Order of Installation

Installing CiscoWorks Common Services 3.0

Installing CiscoWorks Common Services 3.0 on Solaris

Installing CiscoWorks Common Services 3.0 on Windows

Installing Resource Manager Essentials 4.0

Installing Resource Manager Essentials 4.0 on Solaris

Installing Resource Manager Essentials 4.0 on Windows

Installing Campus Manager 4.0

Installing Campus Manager 4.0 on Solaris

Installing Campus Manager 4.0 on Windows

Installing Device Fault Manager 2.0

Installing Device Fault Manager 2.0 on Solaris

Installing Device Fault Manager 2.0 on Windows

Installing Internetwork Performance Monitor 2.6

Installing Internetwork Performance Monitor 2.6 on Solaris

Installing Internetwork Performance Monitor 2.6 on Windows

Getting Started with LMS

Invoking the CiscoWorks Homepage

Logging In

Understanding the CiscoWorks Homepage

Common Services Panel

Application Panel

Resources Panel

CiscoWorks Product Updates Panel

Tool Bar Items

Post-Installation Tasks

Uninstalling LMS

Configuring Device Discovery Using Campus Manager

Adding Devices Using the Device and Credential Admin

Configuring Data Collection

Enabling Single Sign-On

Setting Up System Identity User

Configuring Master Self Signed Certificate

Configuring the CiscoWorks Homepage

Using Applications in ACS Mode

Configuring ACS

Registering Applications to the ACS

Enabling Browser-Server Security From the CiscoWorks Server

Where to Go Next

Related Documentation

Obtaining Documentation

Cisco.com

Ordering Documentation

Documentation Feedback

Obtaining Technical Assistance

Cisco Technical Support Website

Submitting a Service Request

Definitions of Service Request Severity

Obtaining Additional Publications and Information

Quick Start

Quick Start Guide for LAN Management Solution 2.5

---

1 SUPPLEMENTAL LICENSE AGREEMENT

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

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

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

ADDITIONAL LICENSE RESTRICTIONS

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

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

Installation and Use

The Software components are provided to Customer solely to install, update, supplement, or replace existing functionality of the applicable Network Management Software product. Some license terms such as device count and proof of preexisting licenses may be electronically enforced. Customer may install and use following Software components:

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

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

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

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

•Internetwork Performance Monitor (IPM): May be installed on one (1) server in Customer's network management environment.

Reproduction and Distribution

Customer may not reproduce nor distribute software.

DESCRIPTION OF OTHER RIGHTS AND LIMITATIONS

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

2 LAN Management Solution 2.5 Overview

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

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

---

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

---

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

•Enterprise Restricted: Limits you to managing 300 devices.

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

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

In this document you will find:

•LMS package contents, including links for accessing online documentation.

•LMS features highlights.

•Hardware and software requirements for optimal performance.

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

•Information on getting started with LMS.

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

Licensing

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

Understanding Licensing Terms

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

Table 1 Understanding PAK, PIN, and License File

Licensing Terms	Description
Product Identification Number (PIN)	The PIN is printed on the software claim certificate. The LMS installation program prompts you to enter the PIN during installation. If an authenticated license cannot be obtained during installation, use the PIN to proceed with the installation. If only a PIN is entered, LMS will run normally, but you will be periodically reminded to complete the license process.
Product Authorization Key (PAK)	The PAK is printed on the software claim certificate. Use the PAK to get your license file from Cisco.com. You may obtain and install your license file at any time while you are working on LMS, not necessarily only at the time you install the product. We recommend that you complete the LMS license registration and receive product license before installing the LMS 2.5. If the person installing LMS is not authorized to obtain the license on behalf of the administrator, the product can be successfully installed for a period of time using only the PIN. In this case, the product will automatically remind the administrator to complete the licensing process.
License file	When you register your LMS purchase on the product licensing area of Cisco.com, you will receive a license file. You need to provide your PAK to receive a license file. If you are a registered user of Cisco.com, get your license file from: http://www.cisco.com/go/license If you are not a registered user of Cisco.com, use this site to get your license file: http://www.cisco.com/go/license/public Logging in allows your Cisco user profile information to auto-populate many of the product registration fields. Login is case sensitive.

Figure 1 displays the licensing screen on Windows operating system.

Figure 1 Licensing Screen

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

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

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

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

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

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

Licensing Your Product

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

To license your product, you must:

---

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

The PAK is printed on the software claim certificate.

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

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

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

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

Step 3 Install the license file.

If you have obtained the LMS license prior to installation:

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

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

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

b. Click Next to install the license file.

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

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

The License Administration page appears.

b. Click Update.

A file browser popup dialog box appears.

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

d. Click OK.

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

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

---

Additional Information for LMS 2.5 Large Enterprise Unrestricted Licensing

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

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

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

LMS Package Contents

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

Table 2 LAN Management Solution Contents 

This LMS Component...	Provides...	And includes these components
CiscoWorks Common Services 3.0 (Includes CiscoView 6.1)	Common software and services for LMS. Common Services 3.0 provides a set of shared application services that are used by all LMS applications. CiscoView 6.1 is a graphical device management tool that helps monitor, and troubleshoot devices across your network. Integration Utility 1.6 is an integration module that supports third-party Network Management Systems (NMS).	•CiscoWorks Common Services 3.0 Includes CiscoView 6.1 CD-ROM •Release Notes for CiscoWorks Common Services 3.0 (Includes CiscoView 6.1) on Solaris •Release Notes for CiscoWorks Common Services 3.0 (Includes CiscoView 6.1) on Windows
Campus Manager 4.0 (Campus) Campus is sometimes referred to as CM	The ability to: •Visualize Network topology •Manage VLANs •Detect network discrepancies and best-practice non-compliance, Layer 2/3 data and voice traces •Use end-host user information to help in capacity planning.	•Campus Manager 4.0 CD-ROM •Release Notes for Campus Manager 4.0 on Solaris •Release Notes for Campus Manager 4.0 on Windows
Device Fault Manager 2.0 (DFM)	The ability to monitor: •Device faults in real-time and determine the root cause by correlating device level fault conditions. •Cisco device-level fault correlation •Fault history •E-mail, SNMP trap and syslog notifications.	•Device Fault Manager 2.0 CD-ROM •Release Notes for Device Fault Manager 2.0 on Solaris •Release Notes for Device Fault Manager 2.0 on Windows
Internetwork Performance Monitor 2.6 (IPM)	The ability to troubleshoot wide-area network response time and availability proactively. You can do this by using the available device instrumentation (IP Service Level Agreements).	•Internetwork Performance Monitor 2.6 CD-ROM •Release Notes for Internetwork Performance Monitor 2.6
Resource Manager Essentials 4.0 (RME)	The ability to manage: •Device inventory and audit changes •Configuration files, software images and syslog analysis •Filtering to help in life cycle management.	•Resource Manager Essentials 4.0 CD-ROM •Release Notes for Resource Manager Essentials 4.0 on Solaris •Release Notes for Resource Manager Essentials 4.0 on Windows

Additional Information Online

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

•Device Package Updates

–For CiscoView at

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

–For Campus at

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

–For DFM at

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

–For RME at

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

•Latest Adapters at

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

3 Server and Client System Requirements

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

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

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

•Table 5 lists the client system requirements for all platforms.

•Table 6 lists the browser requirements for all platforms.

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

•Table 8 lists the ports LAN Management Solution 2.5 uses.

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

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

Table 3 Minimum Server Requirements for Solaris Systems

Component	Minimum Requirement
Hardware	•Sun UltraSPARC IIIi with 1 GHz •CD-ROM drive •Color monitor with video card capable of 256 colors or more •10BaseT or faster (10 Mbps or faster network connection)
Software	For UltraSPARC IIIi: Solaris 2.8 and 2.9
Available memory (RAM)	•For UltraSPARC IIIi: 2 GB for restricted license and 4 GB for unrestricted license
Available disk space	•For UltraSPARC IIIi (Workstation and Server): 80 GB •4 GB swap space for restricted license and 8 GB swap space for unrestricted license. •UNIX file system recommended 1 We recommend that you set swap space to twice the size of RAM.

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

Table 4 Minimum Server Requirements for Windows Systems 

Component	Minimum Requirement
Hardware	•IBM PC-compatible computer with 1 GHz or Pentium III processor •Color monitor with video card capable of 256 colors or more •CD-ROM drive •10BaseT or faster (10 Mbps or faster network connection)
Software for Windows	One of the following: •Windows 2000 Professional with Service Pack 41 •Windows 2000 Server with Service Pack 4 •Windows 2000 Advanced Server2 with Service Pack 4 •Windows Server 2003 Standard and Enterprise Editions
Available memory (RAM)	•2 GB for restricted license •4 GB for unrestricted license.
Available disk space	•80 GB minimum •4 GB virtual memory for restricted license and 8 GB virtual memory for unrestricted license. •NTFS file system3 required We recommend that you set virtual memory to twice the size of RAM.

1 To verify the Service Pack version on Windows, select Start > Run, then enter winver. 2 This version of LMS does not support Terminal Services on Windows 2000 Advanced Server. Terminal Services must be turned off when you install LMS. 3 Install LMS2.5 on an NTFS file system. Do not install LMS 2.5 on a FAT file system. To verify the file system, open My Computer on the Windows desktop, right-click the drive and select Properties from the popup menu. The file system field appears in the General tab of the Properties dialog box.

Table 5 Minimum Client Hardware and Software Requirements 

Component	Minimum Requirement
Hardware/software	•Any one of these systems: –IBM PC-compatible system with at least a 300 MHz Pentium processor running Windows 2000 (Professional and Server) with Service Pack 3 or Service Pack 4 , Windows XP (SP1 and SP2), Windows Server 2003 (Standard and Enterprise Edition). –Sun UltraSPARC IIIi, running Solaris 2.8 or 2.9. •Color monitor with video card set to 256 colors
Available disk space	•One of the following: –For Solaris: 1 GB swap space –For Windows: 1 GB virtual memory
Available memory (RAM)	•512 MB minimum We recommend that you set virtual memory to twice the size of RAM.

Table 6 Browser Requirements 

Browser	JVM1	Version	Platform
Internet Explorer (recommended)	5.0.0.3802 or later, and Java Plug-in version 1.4.2_042	6.0.26 and 6.0.28	Any one of the following: •Windows 2000 •Windows XP
		6.0 (6.0.3790.0)	Windows Server 20033
Netscape Navigator	—	7.1	Any one of the following: •Windows 2000 •Windows XP
Netscape Navigator (Downloaded from Sun site only)	—	7.0	Solaris 2.8 or 2.9
Mozilla	—	1.7.1	Windows
Mozilla	—	1.7	Solaris 2.8 or 2.9

1 Java Virtual Machine. 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_06 manually. See Installation Guide for IPM and Campus Manager for more details. 3 Windows XP professional is not packaged with JVM. JVM is installed after you install Windows XP.

Application Scaling Numbers

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

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

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

•Resource Manager Essentials (RME)—5,000 devices

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

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

•Internetwork Performance Monitor (IPM)— 2,000 collectors

The supported concurrent users for LMS 2.5 are:

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

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

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

Solaris Patches for LAN Management Solution

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

---

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

---

Table 7 Solaris Patches for LAN Management Solution 2.5¹

Operating System	Required		Recommended
	Server	Client	Server	Client
Solaris 2.8	111327-05 110945-08 110934-16 110898-09 109326-14 108827-40 108528-29	111626-03 108652-81 108921-21 108940-62	110951-01 110662-02 110615-01 110286-02	110951-05 110662-12 110615-11 108964-06
Solaris 2.9	114224-01 113580-01 112839-04 112233-12 114006-01	112771-14 112661-06 113244-05	113326-01 112998-03 113713-14 112964-07 113575-05 112970-07	112808-06

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

LAN Management Solution Port Usage

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

Table 8 LAN Management Solution Port Usage 

Protocol	Port Number	Service Name	Application(s)	Direction (of Establishment) of Connection
ICMP	-	Ping	RME, CM, and DFM	Server to Device
TCP	22	Secure Shell (SSH)	CiscoWorks Common Services and RME	Server to Device
TCP	23	Telnet	CiscoWorks Common Services, CiscoView, and RME	Server to Device
TCP	25	Simple Mail Transfer Protocol (SMTP)	RME	Server Internal
TCP	49	TACACS+ and ACS	CiscoWorks Common Services, RME, CM, and DFM	Server to ACS
TCP	80	HyperText Transfer Protocol (HTTP)	CiscoWorks Common Services, CiscoView	Client to Server
TCP	443	CiscoWorks HTTP server in SSL mode	CiscoWorks Common Services	Sever Internal
TCP	514	Remote Copy Protocol	CiscoWorks Common Services	Server to Device
TCP	514	rsh Daemon	RME	Server to Device
TCP	1683	Internet Inter-ORB Protocol (IIOP)	CiscoWorks Common Services, and CM	Client to Server
TCP	1684	IIOP	CiscoWorks Common Services, and CM	Server to Client
TCP	1741	CiscoWorks HTTP Protocol	CiscoWorks Common Services, CiscoView, and RME	Client to Server
TCP	1783	IIOP for IPM Gatekeeper	IPM	Client to Server
TCP	1784	IIOP for IPM Gatekeeper	IPM	Server to Client
TCP	8088	HIOP	CiscoWorks Common Services	Server to Client Client to Server
TCP	9002	DynamID authentication (DFM Broker)	DFM	Client to Server
TCP	9007	Tomcat shutdown	CiscoWorks Common Services	Server Internal
TCP	9009	Ajp13 connector used by Tomcat	CiscoWorks Common Services	Server Internal
TCP	9088	HIOP port for IPM gatekeeper	IPM	Server to Client Client to Server
TCP	9191	HIOP port for IPM Gatekeeper	IPM	Server Internal
TCP	9192	IIOP port for IPM Gatekeeper	IPM	Server Internal
TCP	9193	IIOP port for IPM Gatekeeper	IPM	Server Internal
TCP	9194	HIOP port for IPM Gatekeeper	IPM	Server Internal
TCP	15000	Log server	DFM	Server Internal
TCP	40050- 40070	CSTM ports used by CS applications such as OGS, Device and Credential Repository (DCR)	CiscoWorks Common Services	Server Internal
TCP	40401	LicenseServer	CiscoWorks Common Services	Server Internal
TCP	42340	CiscoWorks Daemon Manager - Tool for Server Processes	CiscoWorks Common Services	Server Internal
TCP	42344	ANI HTTP Server	CiscoWorks Common Services	Server Internal
TCP	42351	Event Services Software (ESS) Listening (Alternate port is 44351/tcp)	CiscoWorks Common Services	Server Internal
TCP	42352	ESS HTTP (Alternate port is 44352/tcp)	CiscoWorks Common Services	Client to Server
TCP	42353	ESS Routing (Alternate port is 44352/tcp)	CiscoWorks Common Services	Server Internal
TCP	43441	CMF Database	CiscoWorks Common Services	Server Internal
TCP	43455	RME Database	RME	Server Internal
TCP	43443	ANIDbEngine	CM	Server Internal
TCP	43445	Fault History Database	DFM	Server Internal
TCP	43446	Inventory Service Database	DFM	Server Internal
TCP	43447	Event Promulgation Module Database	DFM	Server Internal
TCP	43500 - 43530	CSTM Port for DFM	DFM	Server Internal
TCP	44341	IPM Database	IPM	Server Internal
TCP	44342	IPM Name Server (OSAGENT)	IPM	Client to Server
TCP	47000- 47040	CSTM Port for RME	RME	Server Internal
TCP	55000 - 55020	CSTM Port for Campus Manager	CM	Server Internal
TCP	57860	JRun - JRun Server Manager Control Server	CiscoWorks Common Services	Server Internal
UDP	69	Trivial File Transfer Protocol (TFTP)	CiscoWorks Common Services and RME	Server to Device Device to Server
UDP	161	Simple Network Management Protocol (SNMP)	CiscoWorks Common Services, CiscoView, RME, CM, and DFM	Server to Device Device to Server
UDP	162	SNMP Traps (Standard Port)	CiscoWorks Common Services, and DFM	Server to Device Device to Server
UDP	514	Syslog	CiscoWorks Common Services and RME	Device to Server
UDP	9000	CSlistener (DFM server if port 162 is occupied)	DFM	Client to Server
UDP	14004	Lock port for ANI Server singlet on check	CM	Server Internal
UDP	16236	UT Host acquisition	CM	Device to Server
UDP	42342	OSAGENT	CiscoWorks Common Services and RME	Server Internal (Common Services); RSAC to Server via OSAGENT (RME)
UDP	42350	Event Services Software (ESS) (Alternate port is 44350/udp)	CiscoWorks Common Services	Server Internal

4 Installation Paths

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

Table 9 Recommended Installation Paths 

If you are installing CiscoWorks LAN Management Solution (LMS) on a system that has...	Then do this
LMS 2.2 / LMS 1.3 Update 1	1. Install LMS 2.5 using the instructions in this Quick Start Guide.
LMS 2.2	1. Install LMS 2.2 / LMS1.3 Update 1 2. Install LMS 2.5 using the instructions in this Quick Start Guide.
LMS 2.0 or 2.1	1. Install LMS 2.2 2. Install LMS 2.2 / LMS1.3 Update 1 3. Install LMS 2.5 using the instructions in this Quick Start Guide.

5 Upgrade Options

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

---

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

---

Table 10 Recommended Upgrade Sequence 

If the following components are already installed...	You should upgrade in the following order...
CiscoWorks Common Services 2.2	CiscoWorks Common Services 3.0 (Includes CiscoView 6.1)
CD One, 5th Edition	CiscoWorks Common Services 3.0 (Includes CiscoView 6.1)
•CiscoWorks Common Services 2.2 •Resource Manager Essentials 3.5	1. CiscoWorks Common Services 3.0 (Includes CiscoView 6.1) 2. Resource Manager Essentials 4.0
•CD One, 5th Edition •Resource Manager Essentials 3.4	1. CiscoWorks Common Services 3.0 (Includes CiscoView 6.1) 2. Resource Manager Essentials 4.0
•CiscoWorks Common Services 2.2 •Resource Manager Essentials 3.5 •Campus Manager 3.3	1. CiscoWorks Common Services 3.0 (Includes CiscoView 6.1) 2. Resource Manager Essentials 4.0 3. Campus Manager 4.0
•CD One, 5th Edition •Resource Manager Essentials 3.4 •Campus Manager 3.2	1. CiscoWorks Common Services 3.0 (Includes CiscoView 6.1) 2. Resource Manager Essentials 4.0 3. Campus Manager 4.0
•CiscoWorks Common Services 2.2 •Resource Manager Essentials 3.5 •Device Fault Manager 1.2 Updated for Common Services 2.2	1. CiscoWorks Common Services 3.0 (Includes CiscoView 6.1) 2. Resource Manager Essentials 4.0 3. Device Fault Manager 2.0
•CD One, 5th Edition •Resource Manager Essentials 3.4 •Device Fault Manager 1.2	1. CiscoWorks Common Services 3.0 (Includes CiscoView 6.1) 2. Resource Manager Essentials 4.0 3. Device Fault Manager 2.0
•CiscoWorks Common Services 2.2 •Internetwork Performance Monitor 2.5	1. CiscoWorks Common Services 3.0 (Includes CiscoView 6.1) 2. Resource Manager Essentials 4.0 3. Internetwork Performance Monitor 2.6
•CD One, 5th Edition •Internetwork Performance Monitor 2.4	1. CiscoWorks Common Services 3.0 (Includes CiscoView 6.1) 2. Resource Manager Essentials 4.0 3. Internetwork Performance Monitor 2.6

6 Installing LAN Management Solution 2.5

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 install the application.

Before you begin:

•Check the factors to be considered before installing LMS 2.5. See "Prerequisites" section.

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

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

•Be aware of the following:

–You must install CiscoWorks Common Services 3.0 before installing any other applications.

–After you have installed CiscoWorks Common Services 3.0, you must install each LMS 2.5 application separately. While we strongly recommend that you follow the "Order of Installation" section, you can install the other applications of LMS 2.5 in any order.

Prerequisites

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

Ensure you complete the following tasks before installation:

---

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.

---

Important Installation Notes

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

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

Install device IDU after installing the application.

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

Install the device package after installing the application.

•CiscoWorks applications are installed in the default directories:

–On Solaris: /opt/CSCOpx

–On Windows: SystemDrive:\Program Files\CSCOpx

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

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

•On Solaris, if errors occur during installation, check the installation log file /var/tmp/ciscoinstall.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 log file for the last CiscoWorks application installed.

•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 (for example, installation of new files or changes to system files) will not be undone.

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

•By default, SSL is not enabled on CiscoWorks Server.

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

•Applications not supported by CiscoWorks Common Services 3.0 are disabled during upgrade. RME 3.5 is automatically uninstalled after backing up data. 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.

•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 Server. You must do this to update the application registration in the NMS.

For help with NMS integration, see the User Guide for CiscoWorks Integration Utility 1.6. You can find this document:

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

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

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

Order of Installation

Install each application of LMS 2.5 in the following order:

---

Step 1 Install CiscoWorks Common Services 3.0. See "Installing CiscoWorks Common Services 3.0" section.

Step 2 Install Resource Manager Essentials 4.0. See "Installing Resource Manager Essentials 4.0" section.

Step 3 Install Campus Manager 4.0. See "Installing Campus Manager 4.0" section.

Step 4 Install Device Fault Manager 2.0. See "Installing Device Fault Manager 2.0" section.

Step 5 Install Internetwork Performance Monitor 2.6. See "Installing Internetwork Performance Monitor 2.6" section.

---

7 Installing CiscoWorks Common Services 3.0

Installing CiscoWorks Common Services takes approximately 40 minutes.

Installing CiscoWorks Common Services 3.0 on Solaris

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

---

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

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

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

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

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

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

•Have root access to the server on which you plan to 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. 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. If you select Custom install, you must install all components or LMS will not function correctly.

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

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

b. Configuring the CiscoWorks Server.

c. Configuring your client.

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

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

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

---

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

Installing CiscoWorks Common Services 3.0 on Windows

Before you begin:

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

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

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

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

---

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