<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Hi Darren,<br>
<br>
You will need to be bit more explicit here.<br>
<br>
Most "OS Updates" on the appliance (cm5.x and later) come in the form
of ".cop.sgn" files. These files patch the current active partition and
do not involve the inactive partition.<br>
<br>
If you upgrade to a Mainline version (6.1 to 7.0), upgrade to a
maintenance release (7.0.1 to 7.0.2), upgrade to a service update
(7.0.1 to 7.0.1.11002-4 or "SU1a") or upgrade to an engineering special
(7.0.2.20000-5 or "7.0(2a)" to 7.0.2.21010-2) then then upgrade will
install to the inactive partition, migrate your data, and require
reboot to switch partitions. If this is completed in proper order
(publisher, tftp, backup subscribers, active subscribers) then phones
*should* attempt to upgrade automatically. This may fail if:<br>
1. cm6.x or later and replication to TFTP server is still in progress
when phones reboot<br>
2. tftp server is still rebuilding configuration files when phones
reboot<br>
3. some phones will fail if tftp processing allocation is exceeed.
this is likely to happen with large numbers of phones (2000+ attempting
concurrent upgrade) or if phones are across a WAN from CUCM. WAN
causes the TFTP process to take much longer. This in turn keeps TFTP
threads tied up for extended periods of time. The phone peer to peer
firmware sharing feature is intended to counter this process. Using
"load server" on the phone configuration page can also counter this.<br>
<br>
There are perfmon counters in RTMT for Cisco TFTP to identify these
conditions.<br>
<br>
If a failure does occur most admins have the best success with reseting
phones one device pool at a time to allow phones to upgrade. This is
assuming your phones are divided into device pools of less than ~1000
phones each.<br>
<br>
Regards,<br>
Wes<br>
<br>
On Tuesday, May 26, 2009 2:23:45 PM, Darren Ducote
<a class="moz-txt-link-rfc2396E" href="mailto:ducotedt@stfran.com"><ducotedt@stfran.com></a> wrote:<br>
<blockquote
cite="mid:3CD48F74DEDD72448FE79232802125E00347928ADF@SFMCMAIL07.stfran.net"
type="cite">
<meta http-equiv="Content-Type" content="text/html; ">
<meta name="Generator" content="Microsoft Word 11 (filtered medium)">
<style>
<!--
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:Arial;
color:windowtext;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
{page:Section1;}
-->
</style>
<div class="Section1">
<p class="MsoNormal"><font face="Arial" size="2"><span
style="font-size: 10pt; font-family: Arial;">When I install an
OS/Engineering update and reboot to the inactive partition, do the
phones try and download the new firmware after the swing back over to
the subscriber or do I have to manually update that for each device?<o:p></o:p></span></font></p>
<p class="MsoNormal"><font face="Arial" size="2"><span
style="font-size: 10pt; font-family: Arial;"><o:p> </o:p></span></font></p>
<p class="MsoNormal"><font face="Arial" size="2"><span
style="font-size: 10pt; font-family: Arial;">In other words I am
worried that all the phones will try to do a TFTP firmware update after
installing the updated OS. Thanks!<o:p></o:p></span></font></p>
</div>
<br>
<hr>
<font color="Black" face="Arial" size="3">This message contains
confidential information and is intended only for the individual named.
If you are not the named addressee you should not disseminate,
distribute or copy this e-mail. Please notify the sender immediately by
e-mail if you have received this e-mail by mistake and delete this
e-mail from your system. E-mail transmission cannot be guaranteed to be
secure or error-free as information could be intercepted, corrupted,
lost, destroyed, arrive late or incomplete, or contain viruses. The
sender therefore does not accept liability for any errors or omissions
in the contents of this message, which arise as a result of e-mail
transmission.<br>
</font>
<br>
***St. Francis Medical Center and affiliates encrypt email containing
Patient Health Information. You will receive a notice with instructions
on how to open any encrypted email you receive. To learn more about
this click <a moz-do-not-send="true"
href="http://userawareness.zixcorp.com/sites/index.php?b=141&type=1"><b>Here</b></a>
<pre wrap="">
<hr size="4" width="90%">
_______________________________________________
cisco-voip mailing list
<a class="moz-txt-link-abbreviated" href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>
<a class="moz-txt-link-freetext" href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a>
</pre>
</blockquote>
<br>
</body>
</html>