<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 15 (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:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 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;}
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
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.EmailStyle18
{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 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 believe it works like this:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">The firmware updates immediately upon device package install, but isn’t available until TFTP is restarted. The device defaults are updated as well. Just go into
device defaults before you restart (since you do have to do a full restart for new device models to work) and change the settings back to your older versions.<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">Now the thing I am wondering is if any of the newer http enhancements to downloads change things with respect to firmware availability, but even then you’d still
only have a few minute window between the install completing and you changing the fields back to what they were. I guess it really matters what your root concern with the other firmware is as to whether there is an acceptable risk where a few phones might
upgrade and have to revert.<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>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Matthew G. Loraditch – CCNP-Voice, CCNA, CCDA<br>
</span><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#1F497D"><br>
1965 Greenspring Drive</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><br>
</span><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#1F497D">Timonium, MD 21093</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><br>
</span><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#1F497D"><br>
voice. 410.252.8830<br>
fax. 410.252.9284 <br>
<br>
<a href="http://twitter.com/heliontech">Twitter</a> | <a href="http://www.facebook.com/#!/pages/Helion/252157915296">
Facebook</a> | <a href="http://www.heliontechnologies.com/">Website</a> | <a href="mailto:support@heliontechnologies.com?subject=Technical%20Support%20Request">
Email Support</a></span><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-bottom:12.0pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
</div>
<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 #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<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:cisco-voip-bounces@puck.nether.net]
<b>On Behalf Of </b>Ryan Huff<br>
<b>Sent:</b> Saturday, January 03, 2015 3:31 PM<br>
<b>To:</b> Jeremy Bresley; cisco-voip@puck.nether.net<br>
<b>Subject:</b> Re: [cisco-voip] Device pack installation methodology question<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-family:"Calibri",sans-serif">Correct, ordinarily that would be what I would do as well. In this case though, I am trying to avoid upgrading the firmware on anything, other than the devices
I am trying to get support for.<br>
<br>
Thanks,<br>
<br>
Ryan<o:p></o:p></span></p>
<div>
<div class="MsoNormal" align="center" style="text-align:center"><span style="font-family:"Calibri",sans-serif">
<hr size="2" width="100%" align="center" id="stopSpelling">
</span></div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-family:"Calibri",sans-serif">Date: Sat, 3 Jan 2015 14:20:43 -0600<br>
From: <a href="mailto:brez@brezworks.com">brez@brezworks.com</a><br>
To: <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
Subject: Re: [cisco-voip] Device pack installation methodology question<o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif">On 1/3/2015 2:11 PM, Ryan Huff wrote:<o:p></o:p></span></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif">I need to install a device pack on a 2 node 9.1(2) CCM cluster to get support for some 88xx phones but I do not want to update the loads for anything else.<br>
<br>
The approach I am going to use is:<br>
<br>
Drop the publisher out of the CM Group, forcing all phones to the subscriber. Install the device pack on the publisher and reboot the publisher. Once the publisher is backup, set all the device defaults back to what I want them to be then add the publisher
back to the CM Group. Then drop the subscriber from the CM Group forcing all the phones on the publisher and start the install process over for the subscriber. Once everything is back up add the subscriber back to the CM Group.<br>
<br>
Does that sound reasonable or is there an easier way?<o:p></o:p></span></p>
</div>
</blockquote>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif"><br>
Any time I've needed device support I just install it on all the nodes then reboot them one at a time during a maintenance window. As long as both nodes are running call processing, they'll fail over when the node reboots. Not sure about on 9.X, but on 10.X
this just shows as a blip on the phones of them reregistering, not a full reboot. Obviously if you install new software for those phones, they'll upgrade software when they reboot.<br>
<br>
Jeremy "TheBrez" Bresley<br>
<a href="mailto:brez@brezworks.com">brez@brezworks.com</a><br>
<br>
_______________________________________________ cisco-voip mailing list <a href="mailto:cisco-voip@puck.nether.net">
cisco-voip@puck.nether.net</a> <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>
</div>
</div>
</body>
</html>