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

Wed Dec 5 10:08:35 EST 2012

I know the engineer from Core that ran into this. It was escalated up to the
BU and they pulled the plug on support. The partner had to rebuild the
cluster for free.

And your first mistake was askin an SE. You need to talk to the PSS.

From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Jason Aarons (AM)
Sent: Wednesday, December 05, 2012 9:49 AM
To: Collins, Matthew; 'Alice Borgo'; 'Joe Martini'; 'Abebe Amare'
Cc: 'cisco voip'
Subject: Re: [cisco-voip] R: CUCM6.1.4 Upgrade to 8.6.X on New Hardware

I think this is a Urban legend. 

I’ve asked my Cisco SE about this and he can’t find it documented.  Sort of
a hidden easter egg only the TAC engineer can find (using WebEx while you
watch?) to tell you that you can’t call Cisco TAC any more your on the
blacklist?

From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Collins, Matthew
Sent: Wednesday, December 05, 2012 8:22 AM
To: 'Alice Borgo'; 'Joe Martini'; 'Abebe Amare'
Cc: 'cisco voip'
Subject: Re: [cisco-voip] R: CUCM6.1.4 Upgrade to 8.6.X on New Hardware

I would double check this with Cisco but we where told that if at any time a
CUCM 6 was built on a VM system even if only used as a bridging build the DB
would be marked at unsupported and would remain so no matter what upgrades
where done in future,

Matt

From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Alice Borgo
Sent: 05 December 2012 12:36
To: 'Joe Martini'; 'Abebe Amare'
Cc: 'cisco voip'
Subject: [cisco-voip] R: CUCM6.1.4 Upgrade to 8.6.X on New Hardware

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

  _____  

Any business communication, sent by or on behalf of Linklaters LLP or one of
its affiliated firms or other entities (together "Linklaters"), is
confidential and may be privileged or otherwise protected. If you receive it
in error please inform us and then delete it from your system. You should
not copy it or disclose its contents to anyone. Messages sent to and from
Linklaters may be monitored to ensure compliance with internal policies and
to protect our business. Emails are not secure and cannot be guaranteed to
be error free. Anyone who communicates with us by email is taken to accept
these risks.
Linklaters LLP is a limited liability partnership registered in England and
Wales with registered number OC326345. It is a law firm authorised and
regulated by the Solicitors Regulation Authority (www.sra.org.uk). The term
partner in relation to Linklaters LLP is used to refer to a member of
Linklaters LLP or an employee or consultant of Linklaters LLP or any of its
affiliated firms or entities with equivalent standing and qualifications.
Please refer to www.linklaters.com/regulation for important information on
our regulatory position.
A list of Linklaters LLP members together with a list of those non-members
who are designated as partners and their professional qualifications, may be
inspected at our registered office, One Silk Street, London EC2Y 8HQ and
such persons are either solicitors, registered foreign lawyers or European
lawyers.

itevomcid 

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