<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 HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><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:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";
color:black;}
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;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:black;}
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";
color:black;}
span.content
{mso-style-name:content;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;
color:black;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";
color:black;}
span.EmailStyle22
{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:1.0in 1.0in 1.0in 1.0in;}
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 bgcolor=white 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'>Hi, Andy,<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'>Thank you very much.<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'>Tom<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";color:windowtext'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext'> cisco-voip-bounces@puck.nether.net [mailto:cisco-voip-bounces@puck.nether.net] <b>On Behalf Of </b>Andy<br><b>Sent:</b> Sunday, March 04, 2012 4:48 AM<br><b>To:</b> cisco-voip@puck.nether.net<br><b>Subject:</b> Re: [cisco-voip] Upgrade Methods<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Tom, <br>It will depend on the version of firmware that you had on your handsets prior to the upgrade.<br>So if you wanted to upgrade to the latest version 9.2(3)<br>From the release notes<br><br><span class=content>For all SCCP firmware upgrades from firmware release versions earlier than 8.3(3) to Version 9.2(3) or later, </span><br><span class=content>you must first upgrade your firmware to an intermediate Version (8.3(3) to 8.5(2)) and then upgrade to 9.2(3).</span><br><br><br><o:p></o:p></p><pre>Rgds<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>Andy<o:p></o:p></pre><p class=MsoNormal><br>On 04/03/2012 01:23, Thomas LeMay wrote: <o:p></o:p></p><pre>Lelio,<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>I recently upgraded from CCM 6.1.4 to 7.1.5 and found that the phone<o:p></o:p></pre><pre>firmware code did not update . I had to manually update with interim<o:p></o:p></pre><pre>firmware for the 7965s. Do you know what interim firmware I will need to<o:p></o:p></pre><pre>update the 7945/7960s\62?<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>Thank you,<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>Tom<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>-----Original Message-----<o:p></o:p></pre><pre>From: <a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a><o:p></o:p></pre><pre>[<a href="mailto:cisco-voip-bounces@puck.nether.net">mailto:cisco-voip-bounces@puck.nether.net</a>] On Behalf Of Lelio Fulgenzi<o:p></o:p></pre><pre>Sent: Saturday, March 03, 2012 7:51 PM<o:p></o:p></pre><pre>To: Ed Leatherman<o:p></o:p></pre><pre>Cc: <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><o:p></o:p></pre><pre>Subject: Re: [cisco-voip] Upgrade Methods<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>As someone else mentioned, upgrade the firmware on your phones to the<o:p></o:p></pre><pre>default version your going to before the upgrade. How long before is your<o:p></o:p></pre><pre>choice. The biggest issue with this is if you've waited too long, you might<o:p></o:p></pre><pre>have to do interim firmware upgrades. <o:p></o:p></pre><pre><o:p> </o:p></pre><pre>Also, if you can't swing a change freeze, implement some sort of change<o:p></o:p></pre><pre>management records so you can apply the changes after you switch versions. <o:p></o:p></pre><pre><o:p> </o:p></pre><pre><o:p> </o:p></pre><pre><o:p> </o:p></pre><pre>Sent from my iPhone...<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>"There's no place like 127.0.0.1"<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>On Mar 3, 2012, at 11:12 AM, Ed Leatherman <a href="mailto:ealeatherman@gmail.com"><ealeatherman@gmail.com></a> wrote:<o:p></o:p></pre><pre><o:p> </o:p></pre><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><pre>1) All in one shot. I try to stage/install all the upgrades ahead of <o:p></o:p></pre><pre>time the night before so the next morning during the "official"<o:p></o:p></pre><pre>maintenance window I just have to spend time rebooting and testing.<o:p></o:p></pre><pre>This is particularly helpful if I find myself needing to upgrade some <o:p></o:p></pre><pre>other application (coughUCCX) at the same time as CM.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>2) This would not work in my environment as there are too many changes <o:p></o:p></pre><pre>that happen day-to-day. A configuration freeze of more than a day is <o:p></o:p></pre><pre>not possible.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>3) Test plan for me covers all major dial plan features - 911, local, <o:p></o:p></pre><pre>long distance, International, plus any trunks or special ties to other <o:p></o:p></pre><pre>systems. Also, conf bridges, MOH. Unity, UCCX, paging, call recording <o:p></o:p></pre><pre>apps, CDR delivery. I try a few of these features between CM nodes <o:p></o:p></pre><pre>also (call a phone that's registered to another node etc). Impossible <o:p></o:p></pre><pre>to test every detail but I try to at least hit things that would <o:p></o:p></pre><pre>uncover the broadest number of potential issues. I still need to add <o:p></o:p></pre><pre>something about ITL for my 8.6 upgrade just haven't figure out what <o:p></o:p></pre><pre>yet. YMMV<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>I would suggest familiarizing some with the db replication between CM <o:p></o:p></pre><pre>nodes - I've found they don't always want to fully sync up after <o:p></o:p></pre><pre>upgrade/reboot and its good to have an idea of what the CLI commands <o:p></o:p></pre><pre>do around in case you have a problem. TAC is really good at fixing <o:p></o:p></pre><pre>those issues but it's nice if you can resolve the easy problems <o:p></o:p></pre><pre>yourself.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>Also goes w/o saying but make sure you have any of your license file <o:p></o:p></pre><pre>that you need in advance.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>On Fri, Mar 2, 2012 at 7:22 PM, Frank Arrasmith <o:p></o:p></pre><pre><a href="mailto:frank.arrasmith@gmail.com"><frank.arrasmith@gmail.com></a> wrote:<o:p></o:p></pre><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><pre>Hey all,<o:p></o:p></pre><pre> I have a quick question about best practices/tips during system <o:p></o:p></pre><pre>upgrade, particularly on the Linux appliance models. My previous <o:p></o:p></pre><pre>experience with upgrades has been primarily in a lab, which have <o:p></o:p></pre><pre>always gone fine, However, in my new enterprise, we have an 8 server <o:p></o:p></pre><pre>cluster(pub,5 subs, 2 tftp) running 7.1.5, with critical uptime <o:p></o:p></pre><pre>requirements. Other than recommended procedures from the Cisco <o:p></o:p></pre><pre>Upgrade guides, what other practices or additional procedures do you <o:p></o:p></pre><pre>employ to ensure a smooth upgrade, and/or to speed the process along?<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>1. Do you upgrade all in one shot, long maintenance window? Install, <o:p></o:p></pre><pre>Reboot , Test?<o:p></o:p></pre><pre>2. Do you do spread out the install over a few days? Install over a <o:p></o:p></pre><pre>few maintenance windows utilizing inactive partitions, then schedule <o:p></o:p></pre><pre>restart and testing for another maintenance window? how long of a <o:p></o:p></pre><pre>time period is it acceptable to spread out?<o:p></o:p></pre><pre>3. Other then basic call testing, and ensuring that appropriate <o:p></o:p></pre><pre>services are started/running( we distribute service between the <o:p></o:p></pre><pre>subs), what other checks do you include?<o:p></o:p></pre><pre><o:p> </o:p></pre><pre><o:p> </o:p></pre><pre>Thanks in advance.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>Frank Arrasmith<o:p></o:p></pre><pre><o:p> </o:p></pre><pre><o:p> </o:p></pre><pre><o:p> </o:p></pre><pre><o:p> </o:p></pre><pre>_______________________________________________<o:p></o:p></pre><pre>cisco-voip mailing list<o:p></o:p></pre><pre><a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><o:p></o:p></pre><pre><a href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a><o:p></o:p></pre><pre><o:p> </o:p></pre></blockquote><pre><o:p> </o:p></pre><pre><o:p> </o:p></pre><pre><o:p> </o:p></pre><pre>--<o:p></o:p></pre><pre>Ed Leatherman<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>_______________________________________________<o:p></o:p></pre><pre>cisco-voip mailing list<o:p></o:p></pre><pre><a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><o:p></o:p></pre><pre><a href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a><o:p></o:p></pre></blockquote><pre><o:p> </o:p></pre><pre>_______________________________________________<o:p></o:p></pre><pre>cisco-voip mailing list<o:p></o:p></pre><pre><a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><o:p></o:p></pre><pre><a href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a><o:p></o:p></pre><pre><o:p> </o:p></pre><pre>_______________________________________________<o:p></o:p></pre><pre>cisco-voip mailing list<o:p></o:p></pre><pre><a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><o:p></o:p></pre><pre><a href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a><o:p></o:p></pre><pre><o:p> </o:p></pre></div></body></html>