×

Warning message

  • Cisco Support Forums is in Read Only mode while the site is being migrated.
  • Cisco Support Forums is in Read Only mode while the site is being migrated.

Migrating from CM 6.1.3 to CM 9.X

Unanswered Question
Jan 16th, 2014
User Badges:

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


  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (3 ratings)
Loading.
Manish Gogna Thu, 01/16/2014 - 19:02
User Badges:
  • Cisco Employee,

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

Manish Gogna Thu, 01/16/2014 - 19:43
User Badges:
  • Cisco Employee,

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


Manish

waqas sardar Fri, 01/17/2014 - 00:14
User Badges:

@ 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?

Manish Gogna Fri, 01/17/2014 - 00:19
User Badges:
  • Cisco Employee,

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

waqas sardar Tue, 01/21/2014 - 10:44
User Badges:

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

waqas sardar Wed, 01/22/2014 - 03:14
User Badges:

@ 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?

Aman Soi Wed, 01/22/2014 - 03:21
User Badges:
  • Purple, 4500 points or more
  • Cisco Designated VIP,

    2017 IP Telephony

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

waqas sardar Wed, 01/29/2014 - 08:33
User Badges:

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.

Aman Soi Wed, 01/29/2014 - 18:36
User Badges:
  • Purple, 4500 points or more
  • Cisco Designated VIP,

    2017 IP Telephony

Hi Rob,


thanks for sharing the bug[+5]


regds,

aman

Mark Lyman Wed, 01/29/2014 - 14:05
User Badges:

This occurs when you dont specify an NTP server in the 6.1.5 VM.  When you jump it to 9.1.2, it errors out.  Specify an NTP server in the 6.1.5 VM before you do the jump.


Also, you missed a step at the end where you have to build a fresh 9.1.2 VM and DRS from the "jumped" 9.1.2 to the fresh one.  This is because the 6.1.5 VM does not support VM and it causes a partition misalignment, which you will see in the 9.1.2 gui.

Actions

This Discussion