<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta name=Generator content="Microsoft Word 14 (filtered medium)"><!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"Segoe UI";
panose-1:2 11 5 2 4 2 4 2 2 3;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:70.85pt 56.7pt 56.7pt 56.7pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I think this is a Urban legend. <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>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?<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> cisco-voip-bounces@puck.nether.net [mailto:cisco-voip-bounces@puck.nether.net] <b>On Behalf Of </b>Collins, Matthew<br><b>Sent:</b> Wednesday, December 05, 2012 8:22 AM<br><b>To:</b> 'Alice Borgo'; 'Joe Martini'; 'Abebe Amare'<br><b>Cc:</b> 'cisco voip'<br><b>Subject:</b> Re: [cisco-voip] R: CUCM6.1.4 Upgrade to 8.6.X on New Hardware<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal style='margin-bottom:12.0pt'><span lang=EN-GB><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>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,<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Matt<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> cisco-voip-bounces@puck.nether.net [mailto:cisco-voip-bounces@puck.nether.net] <b>On Behalf Of </b>Alice Borgo<br><b>Sent:</b> 05 December 2012 12:36<br><b>To:</b> 'Joe Martini'; 'Abebe Amare'<br><b>Cc:</b> 'cisco voip'<br><b>Subject:</b> [cisco-voip] R: CUCM6.1.4 Upgrade to 8.6.X on New Hardware<o:p></o:p></span></p></div></div><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>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).<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>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<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>After, I will install a fresh copy of CUCM8.6 on MCS supported Hardware and import the Exported DB from 8.6 VMware environment.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Only after that i will put the license file on the MCS Supported server in 8.6.X version!<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>What do you think about that?<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I use the VMware copy only for Bridge Upgrade.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I understood the consideration for the SUB about TFTP, I'll need to upload again audio files and Firmware phone files.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>REgards<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Alessandro<o:p></o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span lang=IT style='font-size:10.0pt;font-family:"Segoe UI","sans-serif"'>Da:</span></b><span lang=IT style='font-size:10.0pt;font-family:"Segoe UI","sans-serif"'> Joe Martini [<a href="mailto:joemar2@cisco.com">mailto:joemar2@cisco.com</a>] <br><b>Inviato:</b> mercoledė 5 dicembre 2012 12:56<br><b>A:</b> Abebe Amare<br><b>Cc:</b> Alice Borgo; cisco voip<br><b>Oggetto:</b> Re: [cisco-voip] CUCM6.1.4 Upgrade to 8.6.X on New Hardware<o:p></o:p></span></p></div></div><p class=MsoNormal><span lang=IT><o:p> </o:p></span></p><p class=MsoNormal><span lang=IT>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. <o:p></o:p></span></p><div><p class=MsoNormal><span lang=IT><o:p> </o:p></span></p></div><div><p class=MsoNormal><span lang=IT>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.<o:p></o:p></span></p></div><div><p class=MsoNormal><span lang=IT><o:p> </o:p></span></p></div><div><p class=MsoNormal><span lang=IT>Again, I'd highly recommend not using the 6.x on VMware method.<o:p></o:p></span></p></div><div><p class=MsoNormal><span lang=IT><o:p> </o:p></span></p></div><div><p class=MsoNormal><span lang=IT>Joe<o:p></o:p></span></p><div><p class=MsoNormal><span lang=IT><o:p> </o:p></span></p><div><div><p class=MsoNormal><span lang=IT>On Dec 5, 2012, at 6:40 AM, Abebe Amare <<a href="mailto:abucho@gmail.com">abucho@gmail.com</a>> wrote:<o:p></o:p></span></p></div><p class=MsoNormal><span lang=IT><br>you can install the subscriber directly on new hardware it will replicated the DB from the publisher.<br><br>regards,<br><br>Abebe<o:p></o:p></span></p><div><p class=MsoNormal style='margin-bottom:12.0pt'><span lang=IT><o:p> </o:p></span></p><div><p class=MsoNormal><span lang=IT>On Wed, Dec 5, 2012 at 2:26 PM, Alice Borgo <<a href="mailto:bertacco.alessandro@alice.it" target="_blank">bertacco.alessandro@alice.it</a>> wrote:<o:p></o:p></span></p><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span lang=IT> <o:p></o:p></span></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Hi guys,<span lang=IT><o:p></o:p></span></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> I need to Upgrade PUB + ONe SUB from 6.1.4 to 8.6.X on new MCS Hardware.<span lang=IT><o:p></o:p></span></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <span lang=IT><o:p></o:p></span></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Customer want upgrade without modification on the actual Cluster, so I can't upgrade in place the cucm 6.1.4.<span lang=IT><o:p></o:p></span></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <span lang=IT><o:p></o:p></span></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <span lang=IT><o:p></o:p></span></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>So using VMware infrastructure i made an exact copy of the 6.1.4 customer cluster.<span lang=IT><o:p></o:p></span></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <span lang=IT><o:p></o:p></span></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Using Disaster Recovery export all PUB configuration from the Production Cluster and imported on the VMware copy.<span lang=IT><o:p></o:p></span></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <span lang=IT><o:p></o:p></span></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>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 <span lang=IT><o:p></o:p></span></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <span lang=IT><o:p></o:p></span></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>After that Using again DisasterRecovery export DB of the virtualized PUB and the Import again in the MCS Hardware PUB.<span lang=IT><o:p></o:p></span></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <span lang=IT><o:p></o:p></span></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Question for you!<span lang=IT><o:p></o:p></span></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <span lang=IT><o:p></o:p></span></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>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 ?<span lang=IT><o:p></o:p></span></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <span lang=IT><o:p></o:p></span></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Thank you very much<span lang=IT><o:p></o:p></span></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <span lang=IT><o:p></o:p></span></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Regards<span lang=IT><o:p></o:p></span></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <span lang=IT><o:p></o:p></span></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Alessandro Bertacco<span lang=IT><o:p></o:p></span></p></div><p class=MsoNormal style='margin-bottom:12.0pt'><span lang=IT><br>_______________________________________________<br>cisco-voip mailing list<br><a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br><a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><o:p></o:p></span></p></div><p class=MsoNormal><span lang=IT><o:p> </o:p></span></p></div><p class=MsoNormal><span lang=IT>_______________________________________________<br>cisco-voip mailing list<br><a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br><a href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a><o:p></o:p></span></p></div><p class=MsoNormal><span lang=IT><o:p> </o:p></span></p></div></div><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p><div class=MsoNormal align=center style='text-align:center'><span lang=EN-GB><hr size=2 width="100%" align=center></span></div><p class=MsoNormal><span lang=EN-GB style='font-size:7.5pt;font-family:"Arial","sans-serif";color:gray'>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.<br>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 (<a href="http://www.sra.org.uk">www.sra.org.uk</a>). 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 <a href="http://www.linklaters.com/regulation">www.linklaters.com/regulation</a> for important information on our regulatory position.<br>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.<br></span><span lang=EN-GB><br><br><span style='color:white'>itevomcid</span> <o:p></o:p></span></p></div></body></html>