UC8 Migration LabGuide.pdf

UC8 Migration Lab Guide v1.0

Page 1 of 51

OVERVIEW

This guide has been developed for the Cisco Virtual Expert course entitled “UC Migration to 8.x

Hands-On”. The estimated time required to complete the tasks in this guide is 3 hours.

CONTENTS

LAB INFORMATION ....................................................................................................................... 3

LAB 01: Preparing to Upgrade ................................................................................................. 7

LAB 02: Initiating Data Migration ........................................................................................... 16

LAB 03: Migrating to Cisco Unified Communication Manager 7.1(2) ........................................ 24

LAB 04: Verifying Migration................................................................................................... 37

LAB 05: Upgrading from CUCM 7.1(2) to CUCM 8.02 .............................................................. 42

LAB 06: Completing the Upgrading from CUCM 7.1(2) to CUCM 8.02....................................... 46

END OF LAB ................................................................................................................................ 51


Page 2 of 51

PLEASE READ THE FOLLOWING BEFORE PROCEEDING

1) Due to time constraint, not all features of an application and not all applications covered in

the presentation are covered in this lab session.

2) This lab covers only a subset of the pre-upgrade and post-upgrade tasks.

3) This lab is accessible ONLY via Windows Remote Desktop Connection. Prior to accessing the

lab, please ensure that port 3389 has not been blocked from your location of access.

4) Each registered attendee is pre-assigned to a pod. The pod numbers, their respective IP

addresses and the RDP usernames/passwords have been provided at the end of the

presentation. Please make sure you use and access ONLY your assigned pod.

5) This lab is accessible ONLY within the designated time.

6) When starting a VM image (if not already started for you), you may be prompted to create a

new identifier. Please select to “keep” instead of “create” the identifier. This is to ensure

that the preconfigured CIPCs running in the XP clients register to the UC Manager with their

original MAC addresses.


Page 3 of 51

LAB INFORMATION

Lab Topology

Note: AD and UC Manager have been pre-configured to support the tasks in this lab.

We have created a virtual environment including:

1) A Cisco CallManager 4.1(3) Server

2) A Cisco Unified Communications Manager server WITHOUT UC Manager 7.1(2) installed

3) A Cisco Unified Communications Manager server WITH UC Manager 7.1(2) installed

4) A Windows XP workstation installed with Cisco Unified IP Communicator, FTP and NTP

services.

5) A Cisco Unified Communications Manager server WITH UC Manager 8.02 installed

VM Image IP Address Image Login Password

CM413-Pub 172.16.130.88 Administrator cisco

XPStu-ftp 172.16.130.80 student mo$4u

CUCM712-Pub 172.16.130.88 Administrator Cisc0123

CUCM712-Installed 172.16.130.88 Administrator Cisc0123

CUCM802-Installed 172.16.130.88 Administrator Cisc0123

As there are multiple machines sharing the same IP address, please follow the lab

guide closely and ensure that only the appropriate machine is running.


Page 4 of 51

Accessing the Lab

a. Launch Remote Desktop C o nn e c ti o n by clicking on Start-> All Programs -> Accessories -

> Remote Desktop Connection or alternatively press “Windows” + “R” and type “mstsc.exe”.

b. Click on the OPTIONS button in the RDP window.

c. Prior to starting, an option on the LOCAL RESOURCES tab of the Remote Desktop

Program must be set in order for calls to be placed within the lab.


Page 5 of 51

d. To conserve resources on the host machine, set the following options on the EXPERIENCE

and DISPLAY tabs.

e. On the GENERAL tab, enter the IP address of your assigned pod and the username provided

to you. Then click on the CONNECT button.

f. Double click on the VM Server Console icon on the desktop.


Page 6 of 51

g. The VM Server Console opens with the images displayed as shown.


Page 7 of 51

LAB 01: Preparing to Upgrade

Summary

In this lab, you will install the Real-Time Monitoring Tool on the existing CallManager server and use

it to gather information about the server.

Step 1: Launch the VMWare Server Console by double clicking on the icon.

Step 2: Ensure all images are shutdown. If an image is running (the green arrow in front

of the image indicates it is running ), shut it down by clicking on the Red

Square .

Step 3: From the Inventory pane, select CM413-Pub and click on Start this Virtual

Machine. Click OK on all warnings that appear while the image is starting.


Page 8 of 51

Step 4: Once CM413-Pub has started, from the VMware console menu, select VM Send

Ctrl+Alt+Del.

Step 5: Log in to the server with username ‘Administrator’ and password ‘cisco’.

Step 6: Once the server has finished loading, browse to CallManager Administration from Start Programs Cisco CallManager 4.1 CallManager Administration.

Step 7: Click Yes when a security alert dialog box appears as below.


Page 9 of 51

Step 8: Login to CallManager Administration with username ‘Administrator’ and password

‘cisco’.

Step 9: When prompted to accept the security certificate, click Yes.

Step 10: When prompted again as below, login using the username ‘Administrator’ and

password ‘cisco’.

Step 11: Download and install the Cisco Unified Communications Manager Real-Time

Monitoring Tool (RTMT). From the Administration menu bar, select Application

Install Plug-in. Scroll down and locate Cisco CallManager Real-Time Monitoring

Tool. Click on the Installer icon. Click Save to save the RTMT plug-in executable to

the desktop. When the download has completed, click Open to install it. Select

default settings when installing.


Page 10 of 51

Step 12: While RTMT is installing on CM412-Pub, from the inventory pane of the VM server

console, select XPStu-ftp and click on Start this virtual machine. Click OK on all

warnings that appear while the image is starting.

Step 13: Log in to XPStu-ftp with username ‘student’ and password ‘mo$4u’.

Step 14: On the desktop, double click on the Cisco IP Communicator icon to launch the

phone.


Page 11 of 51

The CIPC launches as shown.

Step 15: Launch 3C FTP Daemon from Start 3CDaemon or Start All Programs

3CDaemon 3CDaemon. Ensure that this FTP server is running in XPStu-ftp

throughout the lab.

Step 16: Switch over to CM413-Pub. From the Call Manager Administration screen, select

Device → Phone


Page 12 of 51

Step 17: Click on Find to do a search and list of all phones. Note the number of phones listed

(15).

Step 18: Minimize the CM Administrator. Ensure that RTMT has been installed successfully.

Then, launch RTMT from the Real-Time Monitoring Tool shortcut created on the

desktop.

Step 19: When prompted, enter the IP Address of CM413-Pub: 172.16.130.88.

Step 20: Log in with the username ‘Administrator’ and password ‘cisco’.


Page 13 of 51

Step 21: In the Server Certificate dialog box that appears, click on Yes.

Step 22: Cisco CallManager Serviceability Real-Time Monitoring Tool launches as shown.

Click Cancel on the Mail Server Configuration dialog box.

Step 23: Click OK on the Select Configuration dialog box.


Page 14 of 51

Step 24: From the menu, select Monitor Device Summary.

Step 25: Record the number of each device type that is displayed, including the number of

registered phones, FXS, FXO, T1Cas, PRI, MOH, MTP, CFB, XCODE, and H323

Gateways.

Step 26: From the menu, select Monitor Server Critical Services.


Page 15 of 51

Step 27: Record the status of all critical services.


Page 16 of 51

LAB 02: Initiating Data Migration

Summary

In this lab, you will make some configuration changes to the database of the existing CallManager

server, install the Data Migration Tool and use it to export the data from the database .

Step 1: Start → Programs → Cisco CallManager 4.1. From the Administration menu bar, select Device Phone.

Step 2: In the Find and List Phones page change the first search criteria from Device Name to Directory Number.

Step 3: Type 1001 as the Directory Number to search for.

Step 4: Click Find.

Step 5: Click on the matching record found.

Step 6: On the left side under Directory Number, click on Line1-1001.


Page 17 of 51

Step 7: Change the Directory Number from 1001 to 1150.

Step 8: Scroll down to the Line Settings for this Device. Change the Display (Internal

CallerID) to 1150.

Step 9: Click on Update. (near top of page)

Step 10: Once the screen refreshes, from the administration menu bar, select User Global Directory.

Step 11: In the User Search below, search for ‘user 1’.


Page 18 of 51

Step 12: In the search result window, click on ‘user 1’.

Step 13: Change the First Name of ‘user 1’ to ‘yourFirstName’ and the Last Name of ‘user 1’ to ‘yourLastName’.

Step 14: Change the Telephone Number from 1001 to 1150.

Step 15: Click Update.

Step 16: On the left hand navigation links, click on Device Associations. Scroll down.

Step 17: Set the Primary Extension by selecting the Primary Ext. radio button next to the extension 1150.

Step 18: Scroll to bottom of page. Click on Update.


Page 19 of 51

Step 19: Click OK on box below.

Step 20: Scroll down on the User Configuration page and confirm that the correct primary extension is listed.

Step 21: Minimize the Administration window.

Step 22: Locate DataMgrationAssistant-7-1-2 icon on the desktop of CM413-Pub. Double

click on it to install the Data Migration Assistant.

Note: The install will take a minimum of 30 minutes.


Page 20 of 51

Step 23: Follow the on screen instructions to install DMA. When prompted for the Informix password, enter ‘Cisco,123’. Restart (reboot) the system when prompted.

Step 24: Launch the DMA from Start Programs Cisco Data Migration Assistant Cisco DMA.

Step 25: Click Yes on the Security Alert box. Log in with the username ‘Administrator’ and password ‘cisco’. Click Yes to accept the certificate of the server.

Step 26: From the Administration menu bar, select Export Storage Location.

Step 27: In the Storage Location page, select Local Directory by clicking on the radio button

next to it. Set the Path Name as ‘C:\’. In the Destination Option for License File

section, set the Path Name as ‘C:\’.

Note: When completing this task in a live upgrade, set the Storage Location as a Network Directory or Tape Device. The upgrade process will erase and reformat the local disk in preparation of loading the new OS and would therefore erase the exported data. Running the lab in VMWare allows for a work around for this step.

Step 28: Click on Update.

Step 29: If a warning message appears (to move the contents from the LOCAL directory to an

external device before upgrading), click OK. On the dialog box indicating that the

storage location has been successfully updated, click OK.


Page 21 of 51

Step 30: From the administration menu bar, select Export Export Data. Check the check

box on this page and click on Start Export Now.

Step 31: In the warning below, click Ok to continue.

Note: This data exporting process will take approximately 1 hour. Before exporting data in a live upgrade, make sure to complete the DMA Pre-export tasks before running a DMA export.


Page 22 of 51

When the process completes the following screen is displayed:

Step 32: When the process completes, verify that the DMA tool exported the file by looking in C:\ for the file DMAExportSuccessful.tar with today’s date.

Note: Carefully write down this complete filename…it IS case sensitive.


Page 23 of 51

Step 33: In this step, the .tar file is copied to a FTP server so that it can be copied to the new system once it is built. Launch Internet Explorer. Direct the browser to FTP://172.16.130.80 (XPStu-ftp). Transfer (copy & paste) the DMAExportSuccessful.tar file to the FTP server. Leave it in the root of the directory that the FTP server opens to.

Step 34: Verify that the DMAExportSuccessful.tar file has been successfully transferred to the FTP server. Switch over to XPStu-ftp, locate the file in C:\Lab. Leave the FTP Server running on XPStu-ftp.

ftp://172.16.130.80/


Page 24 of 51

LAB 03: Migrating to Cisco Unified Communication Manager 7.1(2)

Summary

The following steps launch the installation of the appliance version of CUCM and import data migrated using DMA in the previous lab.

Step 1: On CM413-Pub, select Start Shutdown to shutdown the server.

Step 2: From the inventory pane of the VM server console, select CUCM712-Pub and click

on Start this virtual machine.

The Installation script will now start.

Note: The use of the mouse is not possible when navigating through the CUCM installation steps.

Click once with the mouse on the blue screen to bring navigation focus to the VMware screen.

Use the Arrow keys for navigation.

Use the Space bar when making a selection * from a list of items.

Use the Enter key to continue on to the next step.

Additional navigation instructions are found at the bottom of the blue installation screen.


Page 25 of 51

Step 3: Tab to No and press Enter to skip a media check.

Note: In a live upgrade, select Yes to perform a media check.

Step 4: Ensure that Cisco Unified Communications Manager is selected and tab to OK and

press Enter to proceed.

Step 5: Press Enter on the screen below to proceed with the install.


Page 26 of 51

Step 6: Press Enter on the screen below to proceed with the initial configuration of the

platform.

Step 7: We are not applying an upgrade patch as part of this installation. Tab to No and

press Enter on the screen below.

Step 8: Tab to Yes and press Enter on the screen below to import Windows data.


Page 27 of 51

Step 8a: If you are prompted to choose the Time Zone, select Singapore.

Step 9: Press Enter on the screen below to enable automatic negotiation of NIC speed and

duplex.


Page 28 of 51

Step 10: We are not changing the default MTU size. Tab to No and press Enter on the screen

below.

Step 11: We are not configuring this server as a DHCP client. Tab to No and press Enter on

the screen below.


Page 29 of 51

Step 12: Enter the following information in the Static Network Configuration screen below:

a. Host Name CUCM712

b. IP Address 172.16.130.88

c. IP Mask 255.255.255.0

d. GW Address 172.16.130.80

Tab to OK and press Enter.

Step 13: We are not enabling DNS client on this machine. Tab to No and press Enter on the

screen below.


Page 30 of 51

Step 14: Enter the following Administrator login Information in the screen below:

a. Administrator ID Administrator

b. Password Cisc0123

c. Confirm Password Cisc0123


Step 15: Enter the certificate information as follows. In a live scenario, these would need to reflect the appropriate information.

a. Organization Lab

b. Unit HQ

c. Location Singapore

d. State Singapore

e. Country Singapore



Page 31 of 51

Step 16: This is the first node being installed. Press Enter for First Node in cluster.

Step 17: Enter the NTP server IP address ‘172.16.130.80’ (XPStu-ftp has been configured as an NTP server in this lab) as shown in the NTP Client Configuration screen below.


Page 32 of 51

Step 18: Enter the following security password in the Database Access Security Configuration screen below:

a. Security Password Cisc0123

b. Confirm Password Cisc0123

Tab to OK and Press Enter.

Step 19: We are not configuring a SMTP host for this machine. Tab to No and press Enter in the screen below.


Page 33 of 51

Step 20: Select FTP as the desired DMA Retrieval Mechanism. (Press the space bar to select.) Tab twice to OK and press Enter.

Step 21: Enter the following in the DMA Backup Configuration screen below:

a. Remote Server Name or IP 172.16.130.80 (XPStu-ftp)

b. Remote File Path / (root directory as set in the FTP server.)

c. Remote File name This is the complete name of the .tar file (including file extension) that you uploaded to the FTP server in an earlier step. Remember it is case sensitive.

d. Remote Login ID anonymous

e. Remote Password Leave Blank

f. Confirm Password Leave Blank



Page 34 of 51

Step 22: Enter the following Application User username and password in the screen below:

a. Application User Username Administrator

b. Application User Password Cisc0123

c. Confirm Application User Password Cisc0123


Step 23: Enter the following End User password and PIN in the screen below:

a. End User Password Cisc0123

b. Confirm End User password Cisc0123

c. End User PIN 12345

d. Confirm End User PIN 12345



Page 35 of 51

Step 24: Tab to OK and press Enter in the Platform Configuration Confirmation screen

below.

Note: The install will take a minimum of 60 minutes.

Step 25: Tab to Proceed and press Enter in the DMA Validation screen below to remap the

hostname of this server.

Step 26: In a live upgrade, take note of the following MAC address to use for requesting a

license for this server. This screen is presented for several minutes before the

installation proceeds.


Page 36 of 51

Step 27: If the DMA Retrieval Mechanism Configuration screen below appears, tab to OK

and press Enter to proceed.

Note: Instead of waiting for the installation to complete, you may now proceed to an already installed version of Communications Manager.

Step 28: Power off CUCM712-Pub by selecting, from the VM menu, Power -> Power Off.

This is important because the image to start is using the same IP Address as this

image.

Step 29: Start CUCM712-Installed. Click OK on all warnings that appear while the image is

starting. Once the CUCM CLI login prompt is displayed as shown below, proceed to

the next lab.


Page 37 of 51

LAB 04: Verifying Migration

Summary

The following steps verify the status of the migration. With the installation complete, all administration of CUCM and the server is done via the CCM Administration pages. Access to the Administration pages is done via https.

Step 1: Switch over to XPStu-ftp, launch Internet Explorer and connect to http://172.16.130.88

Step 2: Answer Yes to any Security Alerts.

Step 3: Login to CUCM Administration with ‘Administrator’ and password ‘Cisc0123’. Read the licensing warnings displayed.

Step 4: From the Administrator menu bar, select System Licensing License Unit

Report. Notice that under the Software License Version no Software License

information is displayed. What this means is, licensing needs to be applied to this

server.


Page 38 of 51

Note: There is no license file provided in this lab. The following steps are to be done when a license file is available. To continue with the lab, proceed to step 17.

Step 5: From the Administrator menu bar, select System Licensing License File Upload.

Step 6: Click on Upload License File.

Step 7: Click Browse to browse to the license file and then click Upload to validate the

license file.

Step 8: Once the file has been successfully validated, click on Upload License File to upload

the license file.

Step 9: Now to make sure the License information is correct, from the Administration menu bar, select System Licensing License Unit Report. Observe the change in the Software License Status.

Step 10: Uploading the SW Feature License activates the CallManager Service but does not start it. To start this service, from the Navigation menu in the top right corner, select Cisco Unified Serviceability and click Go.

Step 11: From the Administrator menu bar, select Tools Control Center – Feature

Services.

Step 12: Select CUCM712 server and click on Go.


Page 39 of 51

Step 13: Scroll down to the CM Services section. Note that the Cisco CallManager service is

Activated but Not Started. Click the radio button next to the Cisco CallManager

service.

Step 14: Scroll up the page and click on the green arrow to start the service and verify that

the service is started successfully.

Step 15: From the Navigation menu in the top right corner, select Cisco Unified CM Administration and click Go.

Step 16: Bring to focus the IP Communicator. It should be registered to CUCM and showing extension 2002 as before prior to the migration.

Step 17: From the Administrator menu bar, select Device Phone.

Step 18: On the Find and List Phones page below, click on Find.

Step 19: Verify that all of the phones (15 of them) have been successfully migrated to the

new system.

Step 20: Search for a phone with directory number 1150 by selecting to Find Phone where

Directory Number begins with 1150. The phone is listed as shown below, indicating

that the changes made to this phone in the previous system have been migrated to

the new system.

Step 21: From the Administrator menu bar, select User Management End User.

Step 22: On the Find and List Users page below, click on Find.


Page 40 of 51

Step 23: Verify that all of the users (13 of them) have been successfully migrated to the new system. Click on ‘user1’ to open the configuration page of this user.

Step 24: Notice the changes (Last name, First name, Telephone Number, Primary Extension)

made to ‘user1’ in the previous server have been migrated to the new server.

.

.

.


Page 41 of 51

.

Step 25: You will continue to use this browser connection with the installed CUCM 7.12 for

the next part of the lab.


Page 42 of 51

LAB 05: Upgrading from CUCM 7.1(2) to CUCM 8.02

Summary

You will now complete the necessary steps to do an upgrade using a DVD. As in the earlier part of the lab, you will not sit through the entire upgrade process due to constraints with the allocated lab time. After going through the initial steps of starting the upgrade, you will then continue with a near-finished upgraded 8.02 CUCM.

Step 1: Navigate to the Cisco Unified OS Administration screen. Login in with Username

‘Administrator’ and Password ‘Cisc0123’

Step 2: From the Administrator menu bar, select Software Upgrades → Install/Upgrade


Page 43 of 51

Step 3: We are going to perform a hybrid upgrade. The upgrade is going to be done from an

Upgrade DVD. Choose the Source as DVD/CD from the drop-down and enter \ as

the Directory. Click Next to continue to the next step.

Step 4: The upgrade source is searched for and found in the DVD. Click Next to continue

with the Upgrade. Downloading of the file is started.


Page 44 of 51

Step 5: A warning is issued by the Upgrade process. Please note a backup is highly

recommended before proceeding. Also the Current Version and the Upgrade

Version are displayed under Version Information. (We are doing a backup in this

lab). Click Next to proceed.

NOTE: The installation process proceeds from this point till it completes.

The process may take a few hours. You will instead of waiting for the

upgrade to complete, will follow the steps to stop the process on this

machine and proceed to an already installed version of CUCM 8.02


Page 45 of 51

Step 6: Power off CUCM712-Installed by selecting, from the VM menu, Power -> Power

Off. This is important because the image to start is using the same IP Address as

this image.

Step 7: Start CUCM802-Installed. Click OK on all warnings that appear while the image is

starting. Once the CUCM CLI login prompt is displayed as shown below, proceed to

the next lab. Note the CLI prompt is still referring to the CUCM as version 7.12


Page 46 of 51

LAB 06: Completing the Upgrading from CUCM 7.1(2) to CUCM 8.02

Summary

The upgrade method you have done is the hybrid type. As such, the freshly upgraded machine will still have the previous CUCM 7.12 version active. You are going to do the necessary to complete the upgrading to CUCM 8.02

Step 1: Switch over to XPStu-ftp, close the current browser window and re-launch Internet Explorer. Connect to http://172.16.130.88


Step 3: Login to CUCM Administration with ‘Administrator’ and password ‘Cisc0123’. Read the licensing warnings displayed. Note the Licensing Warning. There is no license file provided in this lab.

Step 4: Navigate to Cisco Unified OS Administration and login as Administrator with the Password Cisc0123.


Page 47 of 51

Step 5: From the Administrator menu, access Settings → Version and verify the Installed Versions. Note that CUCM 8.02 is inactive and CUCM 7.12 is active.

Step 6: Switch over to CUCM802-Installed and access the CLI. To verify the active CUCM, issue the command, ‘show version active’. Verify that CUCM 7.12 is active.


Page 48 of 51

Step 7: You are now going to effect the switching and complete the CUCM 8.02 upgrade. From the CLI, issue the command, ‘utils system switch-version’. Enter ‘yes’ when prompted.

Step 8: The switching will go through the ‘Switching Version and Restarting the Appliance’ process. The duration can vary depending on the database size and platform configuration. You will continue to monitor the switchover process from the CLI.


Page 49 of 51

Step 9: After the restart, login and verify the active version with the command ‘show version active’. The Active Master Version will show as 8.02

Step 10: Switch over to XPStu-ftp, launch Internet Explorer and connect to http://172.16.130.88


Step 12: Login in Cisco Unified OS Administration as Administrator and Password Cisc0123

http://172.16.130.88/


Page 50 of 51

Step 13: From the Administrator menu, go to Settings → Version and verify that the switching is successful.

Step 14: Navigate to Cisco Unified CM Administration, login and from the Administrator menu, go to Device → Phone and do a search by clicking on Find. You should see the list of 15 phones as migrated from the earlier version.


Page 51 of 51

Step 15: For the last step of the lab, you are going to view the License MAC address that was tied to this upgrade process. Note that in UC 8 migration, the MAC address is NOT tied to machine’s MAC address. It is created per installation/upgrade. Switch to the Cisco Unified OS Administration page and login. From the Administrator menu, go to Show → System to view the License MAC address in the System Status section.

END OF LAB

Documents

UC8 Migration LabGuide.pdf