[cisco-voip] R: CUCM6.1.4 Upgrade to 8.6.X on New Hardware

Alice Borgo bertacco.alessandro at alice.it
Wed Dec 5 07:35:50 EST 2012


Hi Joe, my intention  is to install 6.0 without license in VMware
environment and after upgrade to 6.1.4, only for import the actual DB of my
customer (In version 6.1.4).

After that i will upgrade from 6.1.4 to 8.6 the VMware copy, and the I will
export DB in 8.6 version

 

After, I will install a fresh copy of CUCM8.6 on MCS supported Hardware and
import the Exported DB from 8.6 VMware environment.

 

Only after that i will put the license file on the MCS Supported server in
8.6.X version!

 

What do you think about that?

 

I use the VMware copy only for Bridge Upgrade.

 

I understood the consideration for the SUB about TFTP, I'll need to upload
again audio files and Firmware phone files.

 

 

REgards

 

Alessandro

Da: Joe Martini [mailto:joemar2 at cisco.com] 
Inviato: mercoledì 5 dicembre 2012 12:56
A: Abebe Amare
Cc: Alice Borgo; cisco voip
Oggetto: Re: [cisco-voip] CUCM6.1.4 Upgrade to 8.6.X on New Hardware

 

A few things to point out.  Installing or using any non 8.0.3 CUCM version
on VMware is unsupported.  I've personally seen issues with the license
manager service when putting a pre 8.0.3 CUCM version on VMware as you're
looking to do, even after upgrading it to 8.x!  The supported method
requires an upgrade on the current MCS server to an 8.0.3 or later version,
backup, restore to a VM running the same exact version.  That's why we
created bridged upgrades, so that you can install 8.x on hardware that
doesn't support it, simply to take a backup to move to VMware.  

 

Adding to Abebe's reply, also remember that any custom TFTP files or MoH
files will be lost using the rebuild method for the subscribers and letting
them replicate.  Remember to put back MoH files on the subscribers and
custom TFTP files, and even certificate loaded on the OS admin page for
secure LDAP connections, etc.

 

Again, I'd highly recommend not using the 6.x on VMware method.

 

Joe

 

On Dec 5, 2012, at 6:40 AM, Abebe Amare <abucho at gmail.com> wrote:


you can install the subscriber directly on new hardware it will replicated
the DB from the publisher.

regards,

Abebe

 

On Wed, Dec 5, 2012 at 2:26 PM, Alice Borgo <bertacco.alessandro at alice.it>
wrote:

 

Hi guys,

   I need to Upgrade PUB + ONe SUB from 6.1.4 to 8.6.X on new MCS Hardware.

 

Customer want upgrade without modification on the actual Cluster, so I can't
upgrade in place the cucm 6.1.4.

 

 

So using VMware infrastructure i made an exact copy of the 6.1.4 customer
cluster.

 

Using Disaster Recovery export all PUB configuration from the Production
Cluster and imported on the VMware copy.

 

Afeter that I'll proceed with the upgrade step 6.1.4 -> 7.1.5.33900-10 ->
RefreshUpgrade -> 8.6.1.2000-1 on the Virtualized environment 

 

After that Using again DisasterRecovery export DB of the virtualized PUB and
the Import again in the MCS Hardware PUB.

 

Question for you!

 

Need to make the same for the SUB, or is possible to install the SUB
directly on the MCS Hardware without all the upgrade step ?

 

Thank you very much

 

Regards

 

Alessandro Bertacco


_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

 

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20121205/8889d9ae/attachment.html>


More information about the cisco-voip mailing list