<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML dir=ltr><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.3354" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=916000916-18122008><FONT face=Arial
color=#0000ff size=2>Hi, I'm doing this exact procedure this coming
weekend. Our CUCM 5.1.3 is a 7 server cluster over the wan, with
4 of them running TFTP service. My experience is that you will need
to "install" the new firmwares on each of the TFTP servers, via the
IPTplatform/OS Administration. (in our case the publisher is one of the
four TFTP servers) When installed on the Publisher/TFTP server the device
default firmware is updated. Next restart the TFTP
services.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=916000916-18122008><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=916000916-18122008><FONT face=Arial
color=#0000ff size=2>My approach is to update the firmware(s) in a controlled
fashion. Or in other words, I prefer to have a reasonable stopping
point. In this manner, I first queried all my Ethernet access switches to
determine the exact list of SEPxxxxxxxxxxxx devices connected to each switch
(show cdp neighbors | incl SEP). From this I created a unique text file
for each access-switch. The text file was uploaded to CUCM as a phone
"target" with "transaction type" of custom reset file. Next step(s)
is to do a "bulk admin -> phone -> reset/restart -> custom file" query
for each file/access-switch uploaded. Then at the bottom of the page, I
set the job to run Later.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=916000916-18122008><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=916000916-18122008><FONT face=Arial
color=#0000ff size=2>At this point a bunch of scheduled reset jobs are queued
and I can release to run at my discretion. I will use RTMT to monitor the
progress of phone registrations. I could also monitor the CLI "term mon"
of the access switch, if I just need something to do to keep me awake during the
tedious/repetitive process. </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=916000916-18122008><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=916000916-18122008><FONT face=Arial
color=#0000ff size=2>Not rocket science but it will allow me to assure
management exactly which portion of which building of which site is being worked
at a given point in time.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=916000916-18122008><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=916000916-18122008><FONT face=Arial
color=#0000ff size=2>Good Luck,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=916000916-18122008><FONT face=Arial
color=#0000ff size=2>Tom Grisham</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=916000916-18122008><FONT face=Arial
color=#0000ff size=2>CCIE 1767</FONT></SPAN></DIV><BR>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> Ruben Montes (Europe)
[mailto:Ruben.Montes@eu.didata.com] <BR><B>Sent:</B> Thursday, December 18,
2008 4:57 AM<BR><B>To:</B> cisco-voip@puck.nether.net<BR><B>Subject:</B>
[cisco-voip] Upgrade IP phones firmware CCM 5.1<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV id=idOWAReplyText68505 dir=ltr>Hi,</DIV>
<DIV dir=ltr> </DIV>
<DIV dir=ltr>I'm looking for the procedure to follow to upgrade the IP phone
firmware in a 6 servers CCM cluster (upload the file to all the servers,
only the TFTP, is it necessary to reboot or restart the TFTP service,
etc)</DIV>
<DIV dir=ltr> </DIV>
<DIV dir=ltr>Thanks in advance,</DIV>
<DIV dir=ltr> </DIV>
<DIV dir=ltr>Ruben</DIV></BLOCKQUOTE></BODY></HTML>