<div dir="ltr"><div><div>Kevin, Mike,<br><br>Thanks for your input. I think I would go with second route and build the new cluster manually and leave other servers up for couple more months after the cut-over for historical data.<br><br></div>Thanks,<br></div>Ashwani<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Dec 18, 2014 at 10:17 AM, Kevin Przybylowski <span dir="ltr"><<a href="mailto:kevinp@advancedtsg.com" target="_blank">kevinp@advancedtsg.com</a>></span> wrote:<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div link="blue" vlink="purple" lang="EN-US">
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">Ashwani,<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">Since you’re taking 2 separate CCX servers, and migrating to 1 there is no way to bring over Historical data from the older version as part of the upgrade. As
this is Historical data, I would advise the supervisors to generate all the reports they’ll need the week before the cutover and then do a clean cut on the new version.
<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">How big is the call center as far as applications/skills/scripts/etc? If small enough, you will save yourself lots of heartache and time if you treat the new
cluster as new and manually migrate the 2 call centers over. This task is fairly easy if old and new are both online.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">I would also agree with Mike and suggest you bring it up to 10.5, just note that HRC is no longer used and the Reporting users will have to be trained on CUIC
if you do that.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">Kevin P.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> cisco-voip [mailto:<a href="mailto:cisco-voip-bounces@puck.nether.net" target="_blank">cisco-voip-bounces@puck.nether.net</a>]
<b>On Behalf Of </b>Mike King<br>
<b>Sent:</b> Thursday, December 18, 2014 9:40 AM<br>
<b>To:</b> Cisco VoIPoE List<br>
<b>Subject:</b> Re: [cisco-voip] Consolidate two separate UCCX cluster and migrate to 9.x<u></u><u></u></span></p><div><div class="h5">
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<p class="MsoNormal">Ashwani,<u></u><u></u></p>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">At this point, I question why you don't upgrade to 10.5. Coming off 7.1, you're in for a major jump/upgrade path, you might as well go the last two versions and be current. <u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Also, you didn't make clear if you're going to 9.0, or 9.1. They will have different EOS dates.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Cisco has not made public any EOS/EOL statements about CUCM9.x, but based off this chart:<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><a href="http://www.voicecerts.com/2011/05/cisco-unified-communications-manager.html" target="_blank">http://www.voicecerts.com/2011/05/cisco-unified-communications-manager.html</a><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">(Not on the chart, 8.6, which was EOS January 2014)<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">I wouldn't be surprised to see an EOL statement in the next calendar year for 9.0. I personally think we'll see it in January. If you have a Cisco Account Manager, and have signed an NDA, you might be able to get the EOS date from him.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">I wouldn't guess what 9.1 EOS date would be.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">As for Merging two clusters together, I don't think with that big a jump, you'll be able to keep the historical data. I believe UCCX 7 still ran on Windows, and UCCX 9 is on Linux, I don't think this data is carried over. Perhaps someone
with more experience with these types of upgrades will comment.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">I recommend practicing your upgrade several times. With this big of a jump practicing several times (Looking at you Leilo and your Saga) will expose upgrade issues in the lab, not in production.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Mike<u></u><u></u></p>
</div>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<p class="MsoNormal">On Thu, Dec 18, 2014 at 8:36 AM, Ashwani R <<a href="mailto:ashwani@ranpise.com" target="_blank">ashwani@ranpise.com</a>> wrote:<u></u><u></u></p>
<blockquote style="border:none;border-left:solid #cccccc 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<div>
<div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">Team,<u></u><u></u></p>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt">I have a customer who has two separate UCCX HA cluster with their respective CUCM cluster (merging two companies). They would like to merge both CUCM and UCCX cluster to one cluster and upgrade them to 9.x.
They are running CUCM version <b>7.1.3.10000-11</b> and UCCX cluster running <b>
7.0(2) Build254</b>. What is the best way to do this? Can they keep both historical data from UCCX and move them to 9.x ? I know this is not possible but just want to see if anyone has done it before. We have already built new 9.x CUCM and UCCX cluster with
new set of IP addresses with blank configurations. Any help will be appreciated.<u></u><u></u></p>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt">Thanks,<u></u><u></u></p>
</div>
<p class="MsoNormal">Ashwani<u></u><u></u></p>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net" target="_blank">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><u></u><u></u></p>
</blockquote>
</div>
</div>
</div></div></div>
</div>
<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><br>
<br></blockquote></div></div>