Table Of Contents

Overview

Migrating to LMS 2.5.1

System Requirements

Understanding Terms Used in the Data Migration Guide

Scope of Data Migration

CS Data Migration Scope

CM Data Migration Scope

RME Data Migration Scope

DFM Data Migration Scope

IPM Data Migration Scope

Overview

---

This document describes the steps involved in migrating data for CiscoWorks LAN Management Solutions (LMS) 2.5.1. The following migration paths are described in this document:

•LMS 2.1/LMS 1.2/RWAN 1.2 to LMS 2.5.1

•LMS 2.2/LMS 1.3/RWAN 1.3 to LMS 2.5.1

This chapter contains:

•Migrating to LMS 2.5.1

•System Requirements

•Understanding Terms Used in the Data Migration Guide

•Scope of Data Migration

Migrating to LMS 2.5.1

Migration is the process of migrating data from an older version of LMS to a newer version of LMS.

Migration involves:

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 to LMS 2.5.1 using either of these two methods:

•Local Migration, which is the process of installing LMS 2.5.1 on top of LMS 2.1 or LMS 2.2 on the same machine.

Or

•Remote Migration, which is the process of installing LMS 2.5.1 on a different machine.

You can migrate to LMS 2.5.1 from:

•LMS 2.1/LMS 1.2/RWAN 1.2

•LMS 2.2/LMS 1.3/RWAN 1.3

Figure 1-1 shows the various applications in each of the LMS versions and the operating systems for each of these versions.

Figure 1-1 Migrating to LMS 2.5.1

* Real-Time Monitor (RTM) and Access Control List Manager are not part of LMS 2.5.1.

The following table describes the scenario when the old LMS data is automatically migrated to LMS 2.5.1:

Table 1-1 Application Data Automatically Migrated to LMS 2.5.1

Applications	LMS 2.1/1.2/RWAN 1.2	LMS 2.2/LMS 1.3/RWAN 1.3
Common Services	CD One, Fifth Edition data migrated to Common Services 3.0.3	Common Services 2.2 data migrated to Common Services 3.0.3
RME	RME 3.4.x data not migrated to RME 4.0.3	RME 3.4.x data not migrated to RME 4.0.3
Campus Manager	Campus Manager 3.2.x data migrated to Campus Manager 4.0.3.	Campus Manager 3.3.x data migrated to Campus Manager 4.0.3.
DFM	DFM 1.2.x data not migrated to DFM 2.0.3.	DFM 1.2.x (Common Services 2.2) data not 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.

---

Note RME and DFM data are not automatically migrated to LMS 2.5.1.

---

For details on manually migrating data for all applications to LMS 2.5.1, see:

•Migrating Data to LAN Management Solution 2.5.1 on Solaris

•Migrating Data to LAN Management Solution 2.5.1 on Windows, page 3-1

System Requirements

The following table provides details of the system requirements for LMS 2.5.1:

Table 1-2 Operating System Supported for LMS 2.5.1

Operating System	Type 1	Type 2
Solaris	8 (2.8)	9 (2.9)
Windows 2000	Professional with SP4	Server/Enterprise Edition (Advanced Server) with SP 4
Windows 2003	Standard Edition with SP 1	Enterprise Edition with SP 1

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

Understanding Terms Used in the Data Migration Guide

The terms frequently used in this document are explained below:

•Backing Up—Copying data to another directory.

•Upgrading—Installing a newer software version on top of an older version (for example, installing Common Services 3.0.3 on Common Services 3.0). The data may or may not be migrated to the new version. For data that is migrated, see Table 1-1.

•Migrating—Moving data from one installation (for example, LMS 2.2 with CS 2.2, RME 3.5.x, Campus Manager 3.3.x) to another (for example, LMS 2.5.1 with CS 3.0.3, RME 4.0.3, Campus Manager 4.0.3).

•Restoring—Process of configuring your upgraded system so it can use the backed up data.

Scope of Data Migration

This section lists the data that is migrated for CS, CM, RME, DFM, and IPM when you upgrade to LMS 2.5.1.

CS Data Migration Scope

When you install Common Services 3.0.3, CD One, Fifth Edition, and CS 2.2 User Details are migrated.

CM Data Migration Scope

When you install Campus Manager 4.0.3, certain data from the previous versions of Campus Manager is converted to Campus Manager 4.0.3 format. The data is:

•Seed devices

•Data Collection schedule

•Data Collection filters

•Data Collection debugging options

•User Tracking queries and layouts

•User Tracking jobs and archives

•User Tracking administration preferences

•User Tracking usernames, notes, and entries

•SNMP community strings

•Discovery schedule

•Discovery filters

•Discovery debugging options

•Path preferences

•Job schedule

•Job archives

•Topology groups

•Topology map preferences

•Discrepancies settings

•Syslog settings

No other data gets migrated to LMS 2.5.1.

RME Data Migration Scope

Migrating RME data transfers data into the RME 4.0.3 server by providing RME 3.x data backups (with their related IDUs) as inputs to the migration script.

When you migrate RME data:

•You can choose to migrate syslogs.

•You can trigger inventory collection for devices being migrated.

•On both platforms, migration is supported across different NMSROOT directories.

•Cross platform data migration is not supported.

For specific details on data that are migrated and that are not migrated, see sections Data Migrated and Data Not Migrated in the chapter Installing Resource Manager Essentials of the Installation and Setup Guide for Resource Manager Essentials 4.0.3.

DFM Data Migration Scope

The following data is migrated when you perform a local or remote migration for DFM:

•Device list—The migration procedure adds devices to Common Services Device and Credentials Repository (DCR) and to DFM.

•The following notification information:

–Mail notification information

–Mail recipient information

–Mail sender ID

–SMTP addresses

–Trap forwarding addresses

–Trap notification addresses and ports

•Some polling and threshold settings—For details, see sections Upgrading Polling Settings and Upgrading Threshold Settings in the Installation and Setup Guide for Device fault Manager 2.0.3.

No other data gets migrated to LMS 2.5.1.

IPM Data Migration Scope

The following IPM data is migrated when you perform a local or remote migration:

•IPM database—contains the list of source, target, collectors, and the statistics of data collected till the backup was taken.

•Source, target, and collector seed files.

No other data gets migrated to LMS 2.5.1.