<p dir="ltr">Thanks for sharing Ryan</p>
<br><div class="gmail_quote"><div dir="ltr">On Sat, Oct 17, 2015, 3:03 AM Ryan Huff <<a href="mailto:ryanhuff@outlook.com">ryanhuff@outlook.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><div dir="ltr">and now here is the attachment ..... sheesh.<br> <br><div><hr>From: <a href="mailto:ryanhuff@outlook.com" target="_blank">ryanhuff@outlook.com</a><br>To: <a href="mailto:avholloway%2Bcisco-voip@gmail.com" target="_blank">avholloway+cisco-voip@gmail.com</a>; <a href="mailto:lelio@uoguelph.ca" target="_blank">lelio@uoguelph.ca</a><br>Date: Sat, 17 Oct 2015 03:01:52 -0400</div></div></div><div><div dir="ltr"><div><br>Subject: Re: [cisco-voip] How Many Docs Does it Take to Prep for an Upgrade?<br>CC: <a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br><br>
<div dir="ltr">Here is the Excel spreadsheet that I use during UC upgrades. Don't beat me up too bad ;) .... it is a collection of 'O wait, I need that too's'; it could probably use some consolidation / tweaking.<br> <br>This is the version 1. In the 'version 2' I am making I am adding a testing plan section and I have also been experimenting with some AXL calls that will auto populate some of the 'discovery' stuff from the pre-upgraded nodes.<br> <br>If anyone finds it to be useful in whole or part; have at it.<br> <br>Thanks,<br> <br>Ryan<br><div><hr>Date: Fri, 16 Oct 2015 14:52:11 -0500<br>From: <a href="mailto:avholloway%2Bcisco-voip@gmail.com" target="_blank">avholloway+cisco-voip@gmail.com</a><br>To: <a href="mailto:lelio@uoguelph.ca" target="_blank">lelio@uoguelph.ca</a><br>Subject: Re: [cisco-voip] How Many Docs Does it Take to Prep for an Upgrade?<br>CC: <a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br><br><div dir="ltr">When you say Prime, I will assume you mean Prime Collaboration Deployment (PCD).<div><br></div><div>I have used PCD a few times now, but it's far from being the savior one might think it is.</div><div><br></div><div>First, PCD really only shines when migrating to v10 on new hardware. Or, the same hardware, but you have twice the space. You can jump straight from CUCM 6.1(4) to 10.5(2) without COP files, or intermediate versions. That's because PCD is actually installing v10 fresh, and just moving the data for you. At least it tries to. There are a few things it doesn't move yet. E.g., DHCP Server TFTP Option 150. Yes, I saw someone using that in CUCM!</div><div><br></div><div>Second, if your doing any other kind of upgrade in PCD, you're not really saving yourself from having to read all the documentation. As your still bound to all the same restrictions and COP files, and whatever else. You can look at PCD in this scenario as an intern who you've given instructions to and he/she just executes them while you go play GTA V on your Xbox you won in an <a href="https://www.youtube.com/watch?v=WZGWBkGkifM" target="_blank">Engineering Deathmatch</a>. The intern really isn't doing anything special for you, other than allowing you to look away while the upgrades happen. And even then, I've seen them fail more times than they have succeeded. YMMV.</div><div><br></div><div>Lastly, on the topic of PCD migrations, which are it's bread and butter, it only does this for CUCM and IM&P. Not CUC, nor CER, not UCCX, or anything else. So, if you go migrate with PCD, then your stuck with COBRAS for CUC, BAT for CER, and who knows what else for the rest. I'll leave that as an exercise to the reader.</div><div><br></div><div>At the end of the day, their maybe some environments where you can just pull the trigger and upgrade the system without reading any documentation, and just gamble, but for a professional of their craft, that's just not acceptable.</div></div><div><br><div>On Fri, Oct 16, 2015 at 2:02 PM, Lelio Fulgenzi <span dir="ltr"><<a href="mailto:lelio@uoguelph.ca" target="_blank">lelio@uoguelph.ca</a>></span> wrote:<br><blockquote style="padding-left:1ex;border-left-color:rgb(204,204,204);border-left-width:1px;border-left-style:solid"><div><div style="color:rgb(0,0,0);font-family:Verdana;font-size:10pt"><div>I've never made a spreadsheet like yours, but I've done something similar. Typically with compatibility checking. You do have to visit a number of documents and/or links. It's quite frustrating to say the least.</div><div><br></div><div>The process of upgrading is a difficult one to say the least, especially with things like you mention, where gotchas are hidden deep in documents that you may not read front to back.</div><div><br></div><div>My biggest issue is when you skip versions, it's not really clear which documents to read with respect to changes. For example, when I upgraded from 7.1 to 9.1, I found myself printing (eeeek!) a number of documents which had duplicate information, but I wasn't sure on where to look.</div><div><br></div><div>And then there's the issue that each application will have different rules, so CUCM might say only print the latest minor version notes, any SU or a/b/c release will have everything you need. Where Connection or Unity Express might do something different.</div><div><br></div><div>It's not fun to say the least.</div><div><br></div><div>But isn't Prime supposed to make it easy to upgrade now?</div><div><br></div><div><br></div><div><span></span>---<br>Lelio Fulgenzi, B.A.<br>Senior Analyst, Network Infrastructure<br>Computing and Communications Services (CCS)<br>University of Guelph<br><div><br></div><a>519‐824‐4120 Ext 56354</a><br><a href="mailto:lelio@uoguelph.ca" target="_blank">lelio@uoguelph.ca</a><br><a href="http://www.uoguelph.ca/ccs" target="_blank">www.uoguelph.ca/ccs</a><br>Room 037, Animal Science and Nutrition Building<br>Guelph, Ontario, N1G 2W1<span></span><br></div><div><br></div><hr><div style="color:rgb(0,0,0);font-family:Helvetica,Arial,sans-serif;font-size:12pt;font-style:normal;font-weight:normal;text-decoration:none"><b>From: </b>"Anthony Holloway" <<a href="mailto:avholloway%2Bcisco-voip@gmail.com" target="_blank">avholloway+cisco-voip@gmail.com</a>><br><b>To: </b>"Cisco VoIP Group" <<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a>><br><b>Sent: </b>Friday, October 16, 2015 2:38:40 PM<span><br><b>Subject: </b>[cisco-voip] How Many Docs Does it Take to Prep for an Upgrade?<br><div><br></div></span><div><div><div dir="ltr">Does anyone else do this? Gather all of the documentation ahead of time, because inevitably you're going to revisit a document more than once? There are a lot of documents to gather! Anything I could be doing better? Tips? Tricks?<div><br></div><div>I create a spreadsheet of all of the pertinent documents I need to review or reference, like in this screenshot. There's over 90 documents in this list. Granted, I don't read them all front to back, but some I do, and for others I need to reference information within them nonetheless. You never know when you might find a small font hidden note in there.</div><div><br></div><div>E.g., From the 8945 Release Notes</div><div><i><br></i></div><div><i>"Release 9.4(2)SR1 can only be upgraded from 9.3(4) and later. Releases prior to 9.3(4) have to be upgraded to 9.3(4) first."</i></div><div><i><br></i></div><div><i>Source: <a href="http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cuipph/8941_8945/firmware/9_4_2SR1/english/release_notes/P415_BK_RB1FD4B7_00_release-notes-942sr1.html#P415_TK_IA5F5D63_00" target="_blank">8945 9.4(2)SR1 Release Notes</a></i></div><div><br></div><div>I actually missed this one recently, and unlike 7900 series phones, they phone will just brick itself and never register. Causing you to walk to every phone and reset power to it, or walk the mac address tables of your layer 2 network and shut/no shut the ports.<br><div><br></div><div><img alt="Inline image 1" src="cid:ii_15071e483b4db3e9"><br></div></div></div><br></div></div><span>_______________________________________________<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><br></span></div><div><br></div></div></div><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" rel="noreferrer" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
<br></blockquote></div><br></div>
<br>_______________________________________________
cisco-voip mailing list
<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a></div> </div>
<br>_______________________________________________
cisco-voip mailing list
<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a></div></div></div>
_______________________________________________<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" rel="noreferrer" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
</blockquote></div>