cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1381
Views
15
Helpful
17
Replies

Migrating from CM 6.1.3 to CM 9.X

waqas sardar
Level 1
Level 1

Dear Team

1. We are migrating from CM 6.1.3.1000-16 to CM 9.X. I am using following path:

2. Backup the current CM 6.1.3.

3. Fresh Installed CM 6.1.3.1000-16 on the VM machine

4. Restore the old CM 6.1.3 backup on fresh CM 6.1.3.1000-16 in VM.

5. Upload the licenses.

6. Upgrade to CM 6.1.5

7. Upgrading direct from CM 6.1.5 to CM 9.X.

Anyone can please answer, is this path is correct?

Thanks

17 Replies 17

Manish Gogna
Cisco Employee
Cisco Employee

CUCM 6.1.3 on VMware is not supported. You will need to upgrade to cucm 6.1.4 or 6.1.5 first on MCS and then follow the Jump Upgrade procedure as decsribed below

http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/rel_notes/9_1_2/CUCM_BK_C9FFFCD0_00_cucm-release-notes-912_chapter_0100.html#CUCM_RF_J9359DDD_00

HTH

Manish

So basically the process would be:

Upgrade to version 6.1.4 or 6.1.5 on MCS

DRS Backup

Build same version of 6.1.4 or 6.1.5 on UCS

Restore the Backup

Upgrade to 9.x

Manish

Hi Waqas,

In addition to what Manush has said[+5] , u can also refer the presentation on Jump Upgrade.

https://supportforums.cisco.com/docs/DOC-34350

regds,

aman

Nice link for those who are not aware about the various D29 options [+5].

Manish

@ Manish

I already fresh installed 6.1.3 on the UCS and its working fine .

What are  the issues if i continous the same path?

Hi Waqas,

Installing cucm 6.1.3 on vmware is not TAC or BU supported as it has not been tested. Even if it works fine, TAC or BU will not support this installation as per the documentation which clearly says that only 6.1.4 or 6.1.5 ( or 7.1.3 / 5 ) can be used on vmware for jump upgrade to 9.x. So, i would suggest upgrading to 6.1.4 on MCS first and then restoring its backup on a freshly built 6.1.4 on vmware so that your installation is TAC and BU supported.

HTH

Manish

I can only restore backup on publisher and then reinstall subcriber ?

If you're going to use the jump upgrade option, you need to rebuild the whole live cluster in the lab.

HTH

java

if this helps, please rate

www.cisco.com/go/pdihelpdesk

HTH

java

if this helps, please rate

@ Jaime Valencia

I am using following path:

2. upgrade the current CM 6.1.3 to CM 6.1.5 on MCS  and DRS.

3. Fresh Installed CM 6.1.5 on the VM machine.(6.1.5 is VM supported  ? )

4. Restore the old CM 6.1.5 backup on fresh CM 6.1.5 in VM.

5. Upgrading direct from CM 6.1.5 to CM 9.X.

is this path is correct?

Hi Waqas,

all points are  correct.

for point 5, u need to have cop files uploaded in call manager servers, depending on you are upgrading to restricted or unrestricted version of 9.x

regds,

aman

@aman

6.1.5 is VM supported  ?

Hi Waqas,

please refer the link provided on page 11, 12 and 13. this is what is JUMP upgrade.

https://supportforums.cisco.com/docs/DOC-34350

regds,

aman

Some 6.1(x) and 7.1(x) images are supported on VMware ONLY for the jump upgrade procedure

HTH

java

if this helps, please rate

www.cisco.com/go/pdihelpdesk

HTH

java

if this helps, please rate

I have tried jump upgrade but Pub crashed every time by following error

.

*** An error occurred during the file system check.

*** Dropping you to a shell; the system will reboot

*** when you leave the shell.

Give root password for maintenance

(or type Control-D to continue):

.

*** An error occurred during the file system check.

*** Dropping you to a shell; the system will reboot

*** when you leave the shell.

Give root password for maintenance

(or type Control-D to continue):

cisco tac said its bug:

https://tools.cisco.com/bugsearch/bug/CSCui85967

NTP is configurered perfectly and also checked by command utile diagnose test.

how can get the complete traces n logs during the upgrdation process.

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: