Guest

Cisco Unified Communications Manager (CallManager)

Release Notes for Data Migration Assistant Release 6.1(4b)

  • Viewing Options

  • PDF (422.4 KB)
  • Feedback
Release Notes for Data Migration Assistant Release 6.1(4b)

Table Of Contents

Release Notes for Data Migration Assistant Release 6.1(4b)

Contents

Introduction

Important Notes

Before You Begin

Cisco Security Agent

Completion Status Recognition

Caveats That Are Resolved in Data Migration Assistant 6.1(4b)

New and Changed Information for Data Migration Assistant 6.1(4b)

Caveats

Resolved Caveats

Using Bug Toolkit

Open Caveats

Obtaining Documentation and Submitting a Service Request


Release Notes for Data Migration Assistant Release 6.1(4b)


September 30, 2009

This document comprises the new features that are included and caveats that are resolved in Data Migration Assistant (DMA) Release 6.1(4b).

Contents

These release notes discuss the following topics:

Introduction

Important Notes, including

Caveats That Are Resolved in Data Migration Assistant 6.1(4b)

New and Changed Information for Data Migration Assistant 6.1(4b)

Caveats

Open Caveats for DMA 6.1(4b)

Obtaining Documentation and Submitting a Service Request

Introduction

Data Migration Assistant (DMA) Release 6.1(4b) collects application data from Unified CM Releases 4.1(3), 4.2(3), and 4.3(2) for upgrade to Cisco Unified Communications Manager Release 6.1(4). DMA exports data in the current Windows based system (with SQL server database) that later gets imported to the appliance-based system (with Informix database).

Data Migration Assistant Release 6.1(4b) also collects application data from a Cisco Emergency Response (CER) 1.3 system for upgrade to CER 2.0.

DMA saves the data that it exports in a tape archive (.tar) file in a location that you specify.

In addition to creating an export, DMA also performs a set of migration compatibility tests (data validation) on the exported Unified CM 4.x data.

If DMA discovers issues, either in the export itself or in the data validation, DMA may report some type of "Failure." Do not consider such a message to be alarming.

Even when DMA completes successfully, but especially if any "Error" or "Warning" occurs, you should examine the generated messages. These messages may comprise

Simply information about auto-data-correction that will be performed in the migration.

Alerts to let you know the problems that DMA encountered as it attempted to check the data.

Generally, these problems require user expertise to determine how to alter the data to remove the migration incompatibility.


Note You must install and run DMA Release 6.1(4b) on the Cisco Unified Communications Manager publisher server before you upgrade to Cisco Unified Communications Manager Release 6.1(4). If you make any configuration changes to Cisco Unified Communications Manager after you run DMA, the system does not retain these changes when you upgrade.



Note Do not consider the DMA Export a substitute for a system backup. You cannot use it to restore your Cisco Unified Communications Manager system in the unlikely event that you cannot complete your upgrade.


Important Notes

The following sections include important information that you should know prior to upgrading to DMA 6.1(4b).

Before You Begin

Cisco Security Agent

Completion Status Recognition

Caveats That Are Resolved in Data Migration Assistant 6.1(4b)

Before You Begin


Note Be aware that it is important that you run DMA early - possibly as early as weeks before the actual upgrade windows to allow time to fix any noncompliant data.


A successful DMA run does not completely prepare you for migration and upgrade.

To ensure that you understand critical tasks that must be completed, Cisco recommends that you read the "Before You Begin" section of the Data Migration Assistant User Guide Release 6.1(4) before you use DMA to export data from the Windows system.

To understand critical upgrade tasks that must be completed, Cisco also recommends that you refer to Upgrading to Cisco Unified Communications Manager Release 6.1(4) from Cisco Unified Communications Manager 4.x Releases.

Find these documents at http://www.cisco.com/en/US/products/sw/voicesw/ps556/prod_installation_guides_list.html.

Cisco Security Agent

Before the DMA export begins, check the system Cisco Security Agent (CSA) version by right-clicking the red CSA flag in the systray and, from the options that display, click About.

If the CSA version is

Less than 2.0(5), DMA stops CSA automatically during the export.

Less than 3.0(3) but greater than 2.0(5), you must manually disable CSA before you run DMA.

3.0(3) or higher, CSA can remain enabled while DMA runs.

Completion Status Recognition

DMA completion reflects four possible outcomes:

Export Success & Validation Success


Note If your DMA run results in one of the following three outcomes, you must fix the inconsistencies and rerun DMA.


Export Success & Validation Success but with Warnings

Export Success & Validation Failure

Export Failure

You can access the DMA log files from the final status window. Use them to see what needs to be fixed.

Caveats That Are Resolved in Data Migration Assistant 6.1(4b)

The following defects are resolved in the 6.1(4b) release of DMA.

CSCsy07560 DMA does not migrate ICD Extension.

CSCtb25098 The DMA process increased in time required due to the fix introduced for the defect CSCsy07560.

CSCsz63731 Replication failure in Unified CM 4.x after DMA failed export.

CSCsz17031 Upgrade failed with no reported user error file message.

New and Changed Information for Data Migration Assistant 6.1(4b)

DMA 6.1(4b) release does not contain any enhancements or feature updates. This release comprises strictly a maintenance release.

Caveats

This section contains information about the caveats that this release of DMA resolves and information about how to create your own list of resolved and open caveats.

Resolved Caveats

Open Caveats

Resolved Caveats

You can find the latest resolved caveat information for Data Migration Assistant by using Bug Toolkit, which is an online tool that is available for customers to query defects according to their own needs.


Tip You need an account with Cisco.com to use the Bug Toolkit to find open and resolved caveats of any severity for any release.

To access the Bug Toolkit, log on to http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl.



Note You can view the list of resolved caveats in "New and Changed Information for Data Migration Assistant 6.1(4b)" section


Using Bug Toolkit

Known problems (bugs) get graded according to severity level. These release notes contain descriptions of

All severity level 1 or 2 bugs.

Significant severity level 3 bugs.

You can search for problems by using the Cisco Software Bug Toolkit.

To access Bug Toolkit, you need the following items:

Internet connection

Web browser

cisco.com user ID and password

To use the Software Bug Toolkit, follow these steps:

Procedure


Step 1 Access the Bug Toolkit, http://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs.

Step 2 Log in with your cisco.com user ID and password.

Step 3 If you are looking for information about a specific problem, enter the bug ID number in the "Search for Bug ID" field and click Go.


Tip Click Help on the Bug Toolkit window for information about how to search for bugs, create saved searches, create bug groups, and so on.


Open Caveats

Table 1 describes possible unexpected behaviors in Data Migration Assistant.


Tip For more information about an individual defect, click the associated Identifier in Table 1 to access the online record for that defect, including workarounds.


Understanding the Fixed-in Version Field in the Online Defect Record

When you open the online record for a defect, you may see data in the "First Fixed-in Version" or "Integrated-in" fields. The information that displays in this field identifies the list of Cisco Unified Communications Manager interim versions in which the defect was fixed. These interim versions then get integrated into Cisco Unified Communications Manager releases.

Some more clearly defined versions include identification for Engineering Specials (ES) or Service Releases (SR); for example 03.3(04)ES29 and 04.0(02a)SR1. However, the version information that displays for the Cisco Unified Communications Manager maintenance releases may not be as clearly identified.


Note Because defect status continually changes, be aware that Table 1 reflects a snapshot of the defects that were open at the time this report was compiled. For an updated view of open defects, access Bug Toolkit and follow the instructions as described in the Using Bug Toolkit.



Tip Bug Toolkit requires that you have an account with Cisco.com. By using the Bug Toolkit, you can find caveats of any severity for any release. Bug Toolkit may also provide a more current listing than this document provides. To access the Bug Toolkit, log on to http://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs.


Table 1 Open Caveats for DMA 6.1(4b)  

Identifier
Headline

CSCsv52741

DMA web pages get stored to local disk cache when HTTPS is enabled.

Note This represents a MCS OS defect that may impact DMA. To make sure that you are not affected, refer to the Caveat notes.

CSCsz59063

DMA successful, but upgrade fails because of a non standard table(s).


Obtaining Documentation and Submitting a Service Request

For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:

http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html

Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS Version 2.0.