Data Migration Guide for LAN Management Solution 3.0
Chapter 1: Overview
Download this chapter
Chapter 1: OverviewChapter 1: Overview
Download the complete book
Data Migration Guide for LAN Management Solution 3.0 - PDF of Entire BookData Migration Guide for LAN Management Solution 3.0 - PDF of Entire Book (PDF - 1 MB)
give_us_feedback

Table Of Contents

Overview

Overview of Migration to LMS 3.0

System Requirements

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) 3.0. The following migration paths are described in this document:

•LMS 2.5.1 or LMS 2.6 to LMS 3.0

•LMS 2.5 to LMS 3.0

•LMS 2.2 or RWAN 1.3 to LMS 3.0

This chapter contains:

•Overview of Migration to LMS 3.0

•System Requirements

•Terms Used in the Data Migration Guide

•Scope of Data Migration

Overview of Migration to LMS 3.0

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 3.0 using either of these two methods:

•Local Migration, which is the process of installing LMS 3.0 on top of the existing LMS version on the same machine and migrating the data into it.

Or

•Remote Migration, which is the process of installing LMS 3.0 on a different machine and migrating the backed up data into it.

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

•Migrating Data to LAN Management Solution 3.0 on Solaris, page 2-1

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

System Requirements

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

Table 1-1 Operating Systems Supported for LMS 3.0

Operating System
Version

Solaris

9, 10

Windows 2003

Windows 2003 Standard and Enterprise Editions with SP1 and SP2

Windows 2003 R2 Standard and Enterprise Editions with SP1 and SP2


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

For complete information on the System Requirements, see the "System and Browser Requirements for Server and Client" section in the Prerequisites chapter of the Installing and Getting Started with CiscoWorks LAN Management Solution 3.0 Guide at this location:

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

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.1 on Common Services 3.0.5).

•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, IPM, and CV when you upgrade to LMS 3.0.

•On both platforms, migration is supported across different NMSROOT directories, where NMSROOT is the CiscoWorks installation directory. By default, it is:

–/opt/CSCOpx for Solaris

–C:\Program Files\CSCOpx for Windows, where C: is the System Drive

•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.1, the following data gets migrated:

•CiscoWorks User information

•Single Sign-on configuration

•Device and Credential Repository (DCR) configuration

•Peer Certificates

•Peer Server Account information

•System Identity Account configuration

•Cisco.com User Account

•Proxy Server

•System Preferences

•Home Page Settings

•Applications Registered

•Links Registered

•Common Services groups

•Jobs and Resources data, DCR data, Groups data, and other data stored in the database

CM Data Migration Scope

When you install Campus Manager 5.0, the following data gets migrated:

•Data Collection settings

–IP Address Filter

–SNMP Timeouts and retries

–Data Collection Schedule

–Debugging Options

•Syslog settings

•Campus Manager groups

Note The above mentioned data only applies to Campus Manager 4.x versions and above.

•Discovery Settings:

–Seed Devices

–IP address Filter

–Discovery Schedule

–SNMP Settings

–Debugging Options

•Topoplogy Groups-User Defined Groups

•Discrepency setting

•Configure Discrepancy

•Configure Syslog server

•User Tracking

–Custom Layout

–Custom Query

–Username and Notes in UT Report

–UT Purge Interval

–UT Acquisition Schedule

–Subnet Discovery Ranges

–Ping sweep options

–Domain name Display

–UT End host and IP Phone entries

–Delete Interval

–Acquisition settings

•Path Analysis

•Archive Trace

•Path Analysis Options

•Jobs and Archives

•UT Jobs and Archives

•Path Analysis Jobs

RME Data Migration Scope

When you install RME 4.1, and migrate from LMS2.2 to LMS 3.0, the following data gets migrated:

•Config Archive

–Shadow directory

–ChangeAudit records. This includes Configuration change details

–Archived configuration versions

•NetConfig

–User Defined Templates (UDT)

UDT RouterUDT in RME3.5 is migrated as RouterUDTTask with the UDT template, RouterUDT in RME 4.0.5.

–Default Template Usage

By default, all templates are assigned to Admin on migration. The device-to-task mapping is not migrated.

•Config Editor

–Editing Mode in which the files are opened. It is either Raw or Processed.

•NetShow

–All the RME 3.5.x User Defined Command Sets and the Commands associated with those command sets are migrated to RME 4.1.The migrated Command Sets will not have any device type associated with them. You must edit them before using them in jobs.

•RME groups

When you install RME 4.1, and migrate from LMS2.5.1/LMS2.5 to LMS 3.0, the following data gets migrated:

•Archive Management :

–All jobs

–Label Configs

–Custom queries

–Baseline templates

–Shadow directory

–ChangeAudit records. This includes Configuration change details.

–Archived configuration versions

•Admin:

–Purge Policies

•Config Editor:

–Private Configs

–Public Configs

–Config Editor Jobs

–Editing mode in which the files are opened. It is either Raw or Processed.

•NetConfig:

–Netconfig jobs

–User-defined tasks

•NetShow:

–NetShow jobs

–Output Archives

–Commandsets

•Software Mangement (Swim)

–Swim repository images

–All jobs in a Job Browser

•Inventory

–Inventory jobs

–Device details

–Inventory Collection Status

–DCA jobs

–Device Management state

–User Defined Groups

When you migrate RME data, the following syslog details get migrated:

•Automated actions

•Message Filters

•Custom reports

•Last 14 days syslog

•Report jobs and archives

Note When you migrate data from RME 3.5.x to RME 4.1, jobs will not be migrated. However, while restoring data from RME 4.1 to RME 4.1, all jobs, data, and admin setting will be migrated.

DFM Data Migration Scope

When you install DFM 3.0, the following data gets migrated:

•Device list—The migration procedure adds devices to Common Services Device and Credentials Repository (DCR). To manage them in DFM, either enable Auto manage feature or manually add the devices to DFM.

•The following notification information:

–Mail notification information

–Mail recipient information

–Mail sender ID

–Syslog notification

–SMTP addresses

–Trap forwarding addresses

–Trap notification addresses and ports

•DFM groups

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

This is available at http://www.cisco.com/en/US/products/sw/cscowork/ps2421/prod_installation_guides_list.html.

IPM Data Migration Scope

When you install IPM 4.0, the following data gets migrated:

•IPM database—contains information about source devices, target devices, operations, collectors, and the statistics of data collected.

•The settings in ipm.env file

Note HTML reports available in IPM 2.6 is backed-up but not restored by running restorebackup.pl.

You can generate consolidated System Reports for the data migrated from IPM 2.6 to IPM 4.0. However, the time taken to generate the reports depends on the length of the period for which you are querying.

For example, generating reports for a period of 6 months may take a longer time, than generating reports for a period of 10 days.

During the same version backup/restore, do not run /NMSROOT/bin/restorebackup.pl script from the following directories:

•Solaris

NMSROOT/MDC/tomcat/webapps/ipm/system_reports and

/var/adm/CSCOpx/files/ipm/

•Windows

NMSROOT/MDC/tomcat/webapps/ipm/system_reports and

NMSROOT/CSCOpx/files/ipm/

CV Data Migration Scope

When you install CiscoView 6.1.6, the user's device preferences are migrated.