Table Of Contents
Release Notes for Data Migration Assistant (DMA) Release 5.1(3)
Caveats Resolved in Data Migration Assistant 5.1(3)
CSCsa98606 DMA DirExport: Map the AAPromptName of Directory to crsappliction Table
CSCsh16583 DMA Requires an Excessively Long Period to Export the Cisco Unified CallManager Directory
CSCsi56977 User must be Administrator to install DMA
CSCsi69720 DMA Install to Check Window Script Engine Version
CSCsi81184 DMA Displays Message 1720 and Installation Fails
CSCsi83799 Enhance Status Display During DMA Process
CSCsi99014 DMA Backup Fails When Informix Password Includes a Backslash Character
CSCsj22669 Device Profile Association Lost After 4.x Upgrade to 5.1(2)
CSCsj24509 Change Backup > Export in DMA
CSCsj24532 DMA Process Guidelines
CSCsj24558 DMA TAR file Cannot Exceed 2 Gigabytes
CSCsj24573 Save Validation Result in .tar File
CSCsj24579 Improve DMA Run-Time Status Text
CSCsj24600 Directory Export to Provide Progress to DMA Framework
CSCsj42131 DMA Assigns Incorrect/Unexpected Partition to Primary Directory Number
CSCsj50278 Consolidated Log Files and Error Files for Directory Export Added in DMA
CSCsj51881 DMA Export Failed During Directory Export
CSCsj53997 Generate Common Error, Warning and Auto-corrected Files in DMA
CSCsj82405 DMA Does Not Migrate Some LDAP Users Due To Spaces in the User Profile
CSCsj83255 DMA Needs to Better Flag Users Not Migrated From LDAP
CSCsj94674 Directory Export Should Export Users With an Unambiguous Numplan
CSCsj95364 DMA Does Not Export Users If the Profile Owner and User ID Do Not Match
CSCsj96134 DMA Needs to Initiate Log/Trace Initialization
CSCsk22663 DMA Ignores Personal Address Book Entries for User
CSCsk60617 Directory Export Failure Should Result in Failure Return to DMA Framework
Cisco Product Security Overview
Reporting Security Problems in Cisco Products
Release Notes for Data Migration Assistant (DMA) Release 5.1(3)
October 1, 2007
These release notes describe the caveats that were resolved in Data Migration Assistant 5.1(3). To view information about the caveats that this release resolves, see the "Caveats" section
Contents
These release notes discuss the following topics:
•
Cisco Product Security Overview
Introduction
The Cisco Data Migration Assistant (DMA) version 5.1(3) assists you with the first step in migrating Cisco Unified CallManager 4.x data to Cisco Unified CallManager 5.1(3) by exporting the data in a format that Cisco Unified CallManager 5.1(3) can read. Cisco Unified CallManager 4.x runs in a Windows environment, and Cisco Unified CallManager 5.1(3) runs in a Linux environment, so the Cisco DMA exports Windows-based data to a format that Linux can import. The Cisco Unified CallManager 5.1(3) installation process converts the exported data as needed for Cisco Unified CallManager 5.1(3), which completes the data migration. DMA also exports data for upgrading Cisco Emergency Responder 1.3 To Cisco Emergency Responder 2.0. For more information, refer to Cisco Emergency Responder Administration Guide.
The Cisco DMA saves the data that it exports in a tape archive (tar) file in a location that you specify.
Note
For more information on Data Migration Assistant 5.1(3), refer to the Data Migration Assistant User Guide Release 5.1(3)
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(3)
This section contains information about the defects that are resolved in Data Migration Assistant Release 5.1(3).
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
CSCsa98606 DMA DirExport: Map the AAPromptName of Directory to crsappliction Table
Caveat
DMA needs to migrate CRS application data.
Current Condition
The release of Data Migration Assistant 5.1(3) resolves this problem.
CSCsh16583 DMA Requires an Excessively Long Period to Export the Cisco Unified CallManager Directory
Caveat
When DMA runs on a Cisco Unified CallManager 4.2(3) cluster with 30,000 users, DMA takes about six seconds per user to export.
Current Condition
The release of Data Migration Assistant 5.1(3) resolves this problem. DMA reduces the time required for each user.
CSCsi56977 User must be Administrator to install DMA
Caveat
User must have administrator privileges to install DMA successfully.
Current Condition
The release of Data Migration Assistant 5.1(3) resolves this problem. Added checking in DMA to verify that user has the local administrator ID to proceed.
CSCsi69720 DMA Install to Check Window Script Engine Version
Caveat
DMA installation fails to complete when Microsoft Windows Script Host version prior to 5.6 does not exist on the server.
Current Condition
The release of Data Migration Assistant 5.1(3) resolves this problem. Before installing DMA, users much install the latest operating system service release on their server.
CSCsi81184 DMA Displays Message 1720 and Installation Fails
Caveat
DMA installation fails. The message indicates that a problem exists with the Windows Installer Package.
Current Condition
The release of Data Migration Assistant 5.1(3) resolves this problem.
CSCsi83799 Enhance Status Display During DMA Process
Caveat
DMA status window displays too much data and users cannot scroll to read the information.
Current Condition
The release of Data Migration Assistant 5.1(3) resolves this problem. The Status window no longer displays all of the data in the AllProgress log but displays a progress indicator to show that DMA is running. When DMA export completes, DMA shows the export and validation results. Users can access information about errors, warnings, and auto-corrected logs by clicking the corresponding button on the Status window.
CSCsi99014 DMA Backup Fails When Informix Password Includes a Backslash Character
Caveat
DMA export fails and displays a message that indicates that DMA cannot connect to the data source. The Informix IDS service does not start. Failure occurs when the Informix password ends three backslashes.
Current Condition
The release of Data Migration Assistant 5.1(3) resolves this problem. This release contains a validation check in the installation that does not allow three backslashes as the last three characters of the Informix password.
CSCsj22669 Device Profile Association Lost After 4.x Upgrade to 5.1(2)
Caveat
Users with multiple device profile association should migrate with the correct device profile association.
Current Condition
The release of Data Migration Assistant 5.1(3) resolves this problem.
CSCsj24509 Change Backup > Export in DMA
Caveat
In DMA, rename the word "Backup" in to "Export" to indicate that DMA exports data and does not backup data.
Current Condition
The release of Data Migration Assistant 5.1(3) resolves this problem.
CSCsj24532 DMA Process Guidelines
Caveat
DMA needs to provide more information on what users must do before DMA exports and validates the data.
Current Condition
The release of Data Migration Assistant 5.1(3) resolves this problem.
CSCsj24558 DMA TAR file Cannot Exceed 2 Gigabytes
Caveat
Upgrades from Cisco Unified CallManager 4.x to Cisco Unified CallManager 5.x or later may encounter issues when the DMA TAR file exceed 2 GB.
Current Condition
The release of Data Migration Assistant 5.1(3) resolves this problem. The DMA export fails if the TAR file exceeds 2 GB.
CSCsj24573 Save Validation Result in .tar File
Caveat
After completion of the DMA export process, DMA generates the .tar file but does not provide a method to check the .tar file to determine if the validation succeeded.
Current Condition
The release of Data Migration Assistant 5.1(3) resolves this problem. DMA provides a DMAResult.txt file to show validation results.
CSCsj24579 Improve DMA Run-Time Status Text
Caveat
After DMA export begins, the status on the Export Data window shows the previous status or shows ready.
Current Condition
The release of Data Migration Assistant 5.1(3) resolves this problem. The run-time status displays in the Windows status bar.
CSCsj24600 Directory Export to Provide Progress to DMA Framework
Caveat
In DMA 5.1(3) release, DMA process needs to invoke the underlying components as a separate process. After the system launches the process, DMA framework can provide progress on the status window.
Current Condition
The release of Data Migration Assistant 5.1(3) resolves this problem.
CSCsj42131 DMA Assigns Incorrect/Unexpected Partition to Primary Directory Number
Caveat
DMA needs to assign correct primary extension for end users during migration.
Current Condition
The release of Data Migration Assistant 5.1(3) resolves this problem. CSCsj51881 resolves this defect.
CSCsj50278 Consolidated Log Files and Error Files for Directory Export Added in DMA
Caveat
Three consolidated files should exist so that customers can review DMA export results: error file, warning files and auto-corrected files. These files should contain all of the errors, warnings, and auto-corrected errors from each DMA component.
DMA stores these files in the following locations.
•
•
•
Current Condition
The release of Data Migration Assistant 5.1(3) resolves this problem.
CSCsj51881 DMA Export Failed During Directory Export
Caveat
DMA export fails during the database and direction information verification process.
Current Condition
The release of Data Migration Assistant 5.1(3) resolves this problem.
CSCsj53997 Generate Common Error, Warning and Auto-corrected Files in DMA
Caveat
After DMA export begins, the status on the Export Data window shows the previous status or shows ready.
Current Condition
The release of Data Migration Assistant 5.1(3) resolves this problem. After performing a DMA export, you can examine the error, warning, and auto-correction logs created by DMA by clicking the approrpriate log button on the status page or by navigating to C:\Program Files\Cisco\Trace\DMA.
CSCsj82405 DMA Does Not Migrate Some LDAP Users Due To Spaces in the User Profile
Caveat
DMA should migrate users with spaces in the user profile.
Current Condition
The release of Data Migration Assistant 5.1(3) resolves this problem.
CSCsj83255 DMA Needs to Better Flag Users Not Migrated From LDAP
Caveat
DMA should display warning messages to customers in DirExport file (DirExport_Warning.log) if users in the directory do not have a user profile and application profile. DMA should also indicate if multiple user have the same user ID but different user profiles and when the userID is different from profile owner ID.
Current Condition
The release of Data Migration Assistant 5.1(3) resolves this problem.
CSCsj94674 Directory Export Should Export Users With an Unambiguous Numplan
Caveat
DMA should export users with a primary extension that has an unambiguous number plan representation, even if no first line appearance exists with that number plan.
Current Condition
The release of Data Migration Assistant 5.1(3) resolves this problem.
CSCsj95364 DMA Does Not Export Users If the Profile Owner and User ID Do Not Match
Caveat
DMA should migrate users even if the user and profile owner IDs differ.
Current Condition
The release of Data Migration Assistant 5.1(3) resolves this problem.
CSCsj96134 DMA Needs to Initiate Log/Trace Initialization
Caveat
The DMA framework initializes the progress related trace when DMA requests a database export. The system loses data from the CCM DB Export Progress trace when the CAR database exists and DMA exports the CAR data.
Current Condition
The release of Data Migration Assistant 5.1(3) resolves this problem. If log files that DMA uses are open when DMA export runs, a message displays and DMA fails.
CSCsk22663 DMA Ignores Personal Address Book Entries for User
Caveat
DMA needs to report personal address book entry export with appropriate trace messages.
Current Condition
The release of Data Migration Assistant 5.1(3) resolves this problem.
CSCsk60617 Directory Export Failure Should Result in Failure Return to DMA Framework
Caveat
When the directory export process encounters errors, DMA should provide the appropriate errors to the user. This type of failure handling should be applied to any directory access failures reported to the error log.
Current Condition
The release of Data Migration Assistant 5.1(3) resolves this problem.
CSCsk62050 DMA Export Fails to Export Users on a Cisco Unified Callmanager 4.x System with DC Directory 2.5
Caveat
DMA export fails on a Cisco Unified Callmanager 4.x System with DC Directory 2.5.
Current Condition
The release of Data Migration Assistant 5.1(3) 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
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
To access Bug Toolkit, you need the following items:
•
•
•
To use Bug Toolkit, follow this procedure.
Procedure
Step 1
Log on with your Cisco.com user ID and password.
Note
Step 2
Step 3
Step 4
Step 5
a.
b.
Step 6
Note
Note
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
Step 2
The Save Search Setting window displays.
Step 3
Step 4
•
•
Note
Step 5
•
•
•
Step 6
Step 7
Open Caveats
Table 1 describes possible unexpected behaviors in Data Migration Assistant.
Tip
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
Tip
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
•
•
•
Find a current list of security advisories, security notices, and security responses for Cisco products at this URL:
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:
•
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.
•
In an emergency, you can also reach PSIRT by telephone:
•
•
Tip
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.CCVP, the Cisco logo, and the Cisco Square Bridge logo are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn is a service mark of Cisco Systems, Inc.; and Access Registrar, Aironet, BPX, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Enterprise/Solver, EtherChannel, EtherFast, EtherSwitch, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, iQuick Study, LightStream, Linksys, MeetingPlace, MGX, Networking Academy, Network Registrar, PIX, ProConnect, ScriptShare, SMARTnet, StackWise, The Fastest Way to Increase Your Internet Quotient, and TransPath are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or Website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0708R)
© 2007 Cisco Systems, Inc. All rights reserved.
Guest
