Table Of Contents
Overview
Overview of Migration to LMS 2.6
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
CV Data Migration Scope
Overview
This document describes the steps involved in migrating data for CiscoWorks LAN Management Solutions (LMS) 2.6. The following migration paths are described in this document:
•
LMS 2.5/ LMS 2.5.1 to LMS 2.6
•LMS 2.1/LMS 2.2/RWAN 1.2/RWAN 1.3 to LMS 2.6
This chapter contains:
•Overview of Migration to LMS 2.6
•System Requirements
•Understanding Terms Used in the Data Migration Guide
•Scope of Data Migration
Overview of Migration to LMS 2.6
Migration is the process of carrying over 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.6 using either of these two methods:
•Local Migration, which is the process of installing LMS 2.6 on top of the existing LMS version on the same machine and migrating the backed up data into it.
Or
•Remote Migration, which is the process of installing LMS 2.6 on a different machine and migrating the backed up data into it.
For details on migrating data for all applications to LMS 2.6, see:
•Migrating Data to LAN Management Solution 2.6 on Solaris, page 2-1
•Migrating Data to LAN Management Solution 2.6 on Windows, page 3-1
System Requirements
The following table provides details of the system requirements for LMS 2.6:
Table 1-1 Operating System Supported for LMS 2.6
Operating System
|
|
|
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
|
Standard Edition with SP 2
|
Enterprise Edition with SP 2
|
R2 Standard Edition with SP2
|
R2 Enterprise Edition with SP 2
|
LMS 2.6 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.5 on Common Services 3.0.3).
•Migrating—Carrying over data from an older version of LMS to a newer version.
•Restoring—Bringing the backed up data into the newer version of LMS.
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.6.
•On both platforms, migration is supported across different NMSROOT directories, where NMSROOT is the CiscoWorks installation directory.
•Cross platform data migration is not supported.
This section contains the following topics:
•CS Data Migration Scope
•CM Data Migration Scope
•RME Data Migration Scope
•DFM Data Migration Scope
•IPM Data Migration Scope
•CV Data Migration Scope
CS Data Migration Scope
When you install Common Services 3.0.5, the following data gets migrated:
•CiscoWorks User information
•Single Sign-on configuration
•Cisco.com User Configuration
•Proxy user configuration
•Device and Credential Repository (DCR) configuration
•Peer Certificates and Self Signed certificates
•Peer Server Account information
•System Identity Account configuration
•Jobs and Resources data, DCR data, Groups data, and other data stored in the database
CM Data Migration Scope
When you install Campus Manager 4.0.6, the following data get migrated:
•Data Collection schedule
•Data Collection filters
•Data Collection debugging options
Note The above mentioned data is applicable for Campus Manager 4.x versions and above only.
•Seed devices
•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
RME Data Migration Scope
Migrating RME data transfers data into the RME 4.0.5 server by providing data backups from older versions of RME (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.
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.5.
This is available at http://www.cisco.com/en/US/products/sw/cscowork/ps2073/prod_installation_guides_list.html.
DFM Data Migration Scope
The following data is migrated 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.6.
This is available at http://www.cisco.com/en/US/products/sw/cscowork/ps2421/prod_installation_guides_list.html.
No other data gets migrated to LMS 2.6.
IPM Data Migration Scope
The following data is migrated for IPM:
•IPM database—contains the list of source, target, collectors, and the statistics of data collected.
•Source, target, and collector seed files.
CV Data Migration Scope
When you install CiscoView 6.1.5, the user's device preferences are migrated.
