Guest

Cisco Unified Communications Manager (CallManager)

Release Notes for Data Migration Assistant Release 5.1(2b)

  • Viewing Options

  • PDF (461.1 KB)
  • Feedback
Release Notes for Data Migration Assistant (DMA) Release 5.1(2b)

Table Of Contents

Release Notes for Data Migration Assistant (DMA) Release 5.1(2b)

Contents

Introduction

For more information

Caveats

Caveats Resolved in Data Migration Assistant 5.1(2b)

CSCsj51881 DMA Backup Fails During Directory Export

CSCsj42131 User with Incorrect Primary Extension in Directory Export

CSCsj22669 User and User Profile Association Issue In Directory Export

CSCsi20684 CSS Call Forward All

CSCsi71128 DMA Requires a Long Time to Run

CSCsj45679 Data Validation Fails For Lower Case Device Names

Resolved Caveats

Using Bug Toolkit

Saving Bug Toolkit Queries

Open Caveats

Cisco Product Security Overview

Reporting Security Problems in Cisco Products


Release Notes for Data Migration Assistant (DMA) Release 5.1(2b)


July 31, 2007

These release notes describe the open caveats that exist for Data Migration Assistant 5.1(2b).


Note This release of Data Migration Assistant adds no new features.


Contents

These release notes discuss the following topics:

Introduction

Caveats

Cisco Product Security Overview

Introduction

The Cisco Data Migration Assistant (DMA) assists you with the first step in migrating Cisco Unified CallManager 4.x data to Cisco Unified CallManager 5.x by backing up Cisco Unified CallManager 4.x data in a format that Cisco Unified CallManager 5.x can read. Cisco Unified CallManager 4.x runs in a Windows environment, and Cisco Unified CallManager 5.x runs in a Linux environment, so the Cisco DMA exports Windows-based data to a format that Cisco Unified CallManager 5.x can import. The Cisco Unified CallManager 5.x installation process converts the backed-up data as needed for Cisco Unified CallManager 5.x, which completes the data migration.

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


Note You must install and run Cisco DMA on the Cisco Unified CallManager publisher server before you upgrade to Cisco Unified CallManager 5.x. If you make any configuration changes to Cisco Unified CallManager after running the Cisco DMA, the system does not retain these changes when you upgrade.


For more information

For more information on Data Migration Assistant 5.1(2b), refer to the following document:

Data Migration Assistant 5.1(1) User Guide

Caveats

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

Caveats Resolved in Data Migration Assistant 5.1(2b)

Resolved Caveats

Open Caveats

Caveats Resolved in Data Migration Assistant 5.1(2b)

This section contains information about caveats that are resolved in Data Migration Assistant Release 5.1(2b).

CSCsj51881 DMA Backup Fails During Directory Export

CSCsj42131 User with Incorrect Primary Extension in Directory Export

CSCsj22669 User and User Profile Association Issue In Directory Export

CSCsi20684 CSS Call Forward All

CSCsi71128 DMA Requires a Long Time to Run

CSCsj45679 Data Validation Fails For Lower Case Device Names

CSCsj51881 DMA Backup Fails During Directory Export

Caveat

DMA export fails during verification of the database and directory information.

Current Condition

The release of Data Migration Assistant 5.1(2b) resolves this problem.

CSCsj42131 User with Incorrect Primary Extension in Directory Export

Caveat

After migration from Cisco Unified CallManager Release 4.x to Cisco Unified CallManager Release 5.x, the user gets associated with the wrong primary extension.

Current Condition

The release of Data Migration Assistant 5.1(2b) resolves this problem.

CSCsj22669 User and User Profile Association Issue In Directory Export

Caveat

Multiple CNN-profiles per user exist in the Cisco Unified CallManager Release 4.x directory. After an upgrade to Cisco Unified CallManager 5.1(2), despite a clean DMA run, lost/missing/incorrect login profiles and device associations exist.

Current Condition

The release of Data Migration Assistant 5.1(2b) resolves this problem.

CSCsi20684 CSS Call Forward All

Caveat

DMA fails to validate when invalid contents exist in the CSSForCFA table and one of the following errors is received in the DMA Backup log:

Pre-DMA5.1(2b):

The following directory numbers have invalid CallingSearchSpaces for forward: 61880 . Please remove or set these CallingSearchSpaces for these DNs and rerun DMA.

Exportable format of Cisco CallManager databases backed up successfully.

DMA 5.1(2b):

Failure: #####>>> Invalid Call Forward All Calling Search Space settings have been detected. The following directory number(s) are involved: [ 61880 ]. These DN records, (usually Phone related), must be either corrected or removed and DMA then re-executed. The problem data may have resulted from either residual settings from an older CM version or from an external, adjunct, or third-party CM call forwarding application directly storing into this column. If the affected DN records are obsolete or easily re-entered, they should be deleted via the administration menus. The administrative interface does not provide any means to otherwise correct the problem data. If the problem records can not be deleted, correction will require the use of Enterprise Manager or other SQL access tools. Correction using these direct DB modification tools may require the approval and assistance of Cisco Support. If pursuing record correction, the following SQL query may be helpful to identify problem records that can not be deleted: [ SELECT * FROM NumPlan WHERE CSSforCFA IS NOT NULL AND CSSforCFA NOT LIKE '{%' ]. Additionally, correct settings for the CSSforCFA column include either empty/null or the PKID of a valid CSS in the form '{pkid}:{}'.

modExportDatabase=Failure

Could not complete database processing successfully.

Failed to back up exportable format of Cisco CallManager databases.

Current Condition

The release of Data Migration Assistant 5.1(2b) resolves this problem.

CSCsi71128 DMA Requires a Long Time to Run

Caveat

Upgrading to Cisco Unified CallManager Release 5.x, from releases of Cisco Unified CallManager prior to release 4.1(3), DMA execution takes a very long time in the pre-migration phase. If this occurs, you should wait for completion. A delay in this phase of up to 23 hours for 45,000 devices has occurred.

Current Condition

The release of Data Migration Assistant 5.1(2b) resolves this problem.

CSCsj45679 Data Validation Fails For Lower Case Device Names

Caveat

DMA 5.1(2) data validation reports rules compliance errors related to device names containing lower case characters. If you migrate to Cisco Unified CallManager 5.1(2) despite these error messages, various administrative activities involving these records and those that use them can fail.

Current Condition

The release of Cisco Unified CallManager Release 5.1(2a) and Data Migration Assistant 5.1(2b) resolves this problem.

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 (CDC) 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.


This section includes the following topics:

Using Bug Toolkit

Saving Bug Toolkit Queries

Using Bug Toolkit

To access Bug Toolkit, you need the following items:

Internet connection

Web browser

Cisco.com user ID and password

To use Bug Toolkit, follow this procedure.

Procedure


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

Log on with your Cisco.com user ID and password.


Note If you are looking for information about a specific caveat, enter the ID number in the "Search for bug ID:" field and click Go.


Step 2 From the Select Product Category drop-down box, choose "Voice and Unified Communications."

Step 3 From the Select Product drop-down box, choose "Cisco Unified Communications (CallManager)."

Step 4 In the Software Version, Version drop-down list, choose the major release of Cisco Unified Communications Manager for which you want the caveats (for example, 5.0, 6.0, etc.).

Step 5 Under Advanced Options, choose "Use custom settings for severity, status, and others."

a. To find resolved caveats, in the information that displays, click (to "uncheck") the Fixed check box.

To find unresolved caveats, in the information that displays, ensure that the Fixed check box is "checked".

b. From the Modified Date drop-down list, choose "Any Time."

Step 6 Click Search.


Note To see caveats relavant to DMA, you should search for all of the Cisco Unified CallManager caveats, then
- locate the caveats associated with the cpi-dma component and
- locate any other caveats that contain "migration" or "DMA" in their headlines.



Note You can save your query for future use. See the "Saving Bug Toolkit Queries" section.




Note For detailed online help with Bug Toolkit, click Help on any Bug Toolkit window.


Saving Bug Toolkit Queries

Bug Toolkit allows you to create and then save your queries to monitor a specific defect or network situation. You can edit a saved search at any time to change the alert conditions, the defects that are being watched, or the network profile.

Follow this procedure to save your Bug Toolkit queries.

Procedure


Step 1 Perform your search for caveats, as described in the "Using Bug Toolkit" section.

Step 2 Click the Save Search button that displays at the bottom of the window.

The Save Search Setting window displays.

Step 3 In the Search Name field, enter a name for the saved search.

Step 4 In the Place in Group section, you can:

Click the Existing group: radio button and choose an existing group name from the drop-down list box.

Click the Create new group named: radio button and enter a group name to create a new group for this saved search.


Note This bug group will contain the bugs that are identified by using the search criteria that you have saved. Each time that a new bug meets the search criteria, the system adds it to the group that you chose.


Step 5 In the Group Notifications Settings section, for Email Updates, you can choose to set optional e-mail notification preferences if you want to receive automatic updates of a bug status change. Bug Toolkit provides the following options:

No email updates—If you choose this default setting, Bug Toolkit does not send e-mail notifications.

Yes, send my updates to—Click the radio button to choose this option to send e-mail notifications to the user ID that you enter in this field.

On a schedule—Click the radio button to choose this option and from the drop-down list, choose the how often you want to get updates from the Bug Toolkit.

Step 6 To save your changes, click Save Search.

Step 7 A window displays the bug group(s) that you have saved. From this window, you can click a bug group name to see the bugs and the saved searches; you can also edit the search criteria.

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 and the Integrated-in Fields 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 these fields identifies the list of Cisco Unified CallManager interim versions in which the defect was fixed. These interim versions then get integrated into Cisco Unified CallManager 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 CallManager 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" section.



Tip Bug Toolkit requires that you have an account with Cisco.com (Cisco Connection Online). 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 as of July 30, 2007 

Identifier
Headline

CSCsj04294

The DMA logs contain errors that indicate files and directories could not be accessed or created.

CSCsj69397

DMA generates one large installdbw1.log file.

CSCsj24532

The need exists for guidelines on the DMA process.

CSCsj24595

The need exists for simplified log file collection.

CSCsi81184

Installation fails and displays:"Error 1720. There is a problem with this Windows Installer Package. A script required for this install to complete could not be run. Contact your support personnel or package vendor."

CSCsi68776

The estimated time to complete a backup is not displayed on the DMA window.

CSCsj02921

DMA installation fails.

CSCsj78789

DMA validation fails with International Dial plans.

CSCsj24610

The need exists to improve DMA uninstall.

CSCsj49413

During a DMA backup, a "This page cannot be displayed" message displays.

CSCsf24390

User tried to install DMA, and an error occurred.

CSCsh05766

DMA backup status indicates "ready" after the backup instead of "successful" or "failed".

CSCsb71648

Migration took over 15 hours.

CSCsg90581

DMA upgrade fails.

CSCsj40566

User cannot easily migrate from 4.x to 5.x if special characters exist in the database.

CSCsj01673

DMA fails to validate when invalid contents are in the CSSForCFA table.

CSCsj50260

After DMA invokes CAR export routine, no progress information displays on the DMA status window.

CSCsj78261

DMA XML format error.

CSCsi83076

DMA fails when backslash gets used in Informix password.

CSCsj24485

After DMA validation fails, the need exists for error messages that indicate how to fix the problem that caused the failure.

CSCsj83255

Migration occurs, but not all users get migrated.

CSCsj82405

After DMA and upgrade, LDAP users in the Cisco Unified CallManager database are missing.

CSCsj24600

When the directory export is exporting directory data, no progress indication gets provided to DMA.


Cisco Product Security Overview

Cisco provides a free online Security Vulnerability Policy portal at this URL:

http://www.cisco.com/en/US/products/products_security_vulnerability_policy.html

From this site, you will find information about how to

Report security vulnerabilities in Cisco products.

Obtain assistance with security incidents that involve Cisco products.

Register to receive security information from Cisco.

Find a current list of security advisories, security notices, and security responses for Cisco products at this URL:

http://www.cisco.com/go/psirt

To see security advisories, security notices, and security responses as they are updated in real time, you can subscribe to the Product Security Incident Response Team Really Simple Syndication (PSIRT RSS) feed. Find information about how to subscribe to the PSIRT RSS feed at this URL:

http://www.cisco.com/en/US/products/products_psirt_rss_feed.html

Reporting Security Problems in Cisco Products

Cisco is committed to delivering secure products. We test our products internally before we release them, and we strive to correct all vulnerabilities quickly. If you think that you have identified a vulnerability in a Cisco product, contact PSIRT:

For Emergencies only — security-alert@cisco.com

An emergency is either a condition in which a system is under active attack or a condition for which a severe and urgent security vulnerability should be reported. All other conditions are considered nonemergencies.

For Nonemergencies — psirt@cisco.com

In an emergency, you can also reach PSIRT by telephone:

1 877 228-7302

1 408 525-6532


Tip We encourage you to use Pretty Good Privacy (PGP) or a compatible product (for example, GnuPG) to encrypt any sensitive information that you send to Cisco. PSIRT can work with information that has been encrypted with PGP versions 2.x through 9.x.

Never use a revoked or an expired encryption key. The correct public key to use in your correspondence with PSIRT is the one linked in the Contact Summary section of the Security Vulnerability Policy page at this URL:

http://www.cisco.com/en/US/products/products_security_vulnerability_policy.html

The link on this page has the current PGP key ID in use.

If you do not have or use PGP, contact PSIRT at the aforementioned e-mail addresses or phone numbers before sending any sensitive material to find other means of encrypting the data.