<!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">
Either:<br>
1. phones are not resolving proper tftp server<br>
2. tftp server is not service correct data<br>
3. config is incorrect for TFTP config file<br>
<br>
to verify:<br>
1. browse to phone's ip address, check TFTP server listed there. if
TFTP server is properly listed there security can still intervene. If
you have cluster security enabled is the specified TFTP server included
as a TFTP server in CTL configuration? Form the phone LCD you can view
the contents of the CTL file to confirm what TFTP servers are valid for
the current security configuration.<br>
<br>
2. TFTP could have been busy still building config files. Check
performance counters through RTMT for:<br>
Cisco TFTP<br>
Reqeusts Aborted<br>
Requests Overflow<br>
<br>
If those show large values it is likely that TFTP was still busy
building config files and not ready to service requests. Next if you
do not encrypted config files enabled you can attempt a TFTP download
to confirm behavior. From windows command prompt:<br>
C:\Temp>tftp -i 14.48.40.57 get XMLDefault.cnf.xml<br>
Transfer successful: 6425 bytes in 1 second, 6425 bytes/s<br>
<br>
C:\Temp>notepad XMLDefault.cnf.xml<br>
For example on my cluster for 7961 the default load is:<br>
<snip><br>
<loadInformation30018 model="Cisco
7961">SCCP41.8-4-3S</loadInformation30018><br>
</snip><br>
<br>
This is the global config applied under device->device
settings->device defaults.<br>
<br>
<br>
<br>
3. Next is the phone specific configuration. Phone specific
configuration overrides global configuration. On the phone
configuration page in ccmadmin you can specify "load information" per
phone. If this is specified it takes precedence over the global
option. Check the configuration in CCMAdmin or check the phone config
file directly. Example from windows command prompt:<br>
C:\Temp>tftp -i 14.48.40.57 get SEP001bd5846d80.cnf.xml<br>
Transfer successful: 7315 bytes in 1 second, 7315 bytes/s<br>
<br>
C:\Temp>notepad SEP001bd5846d80.cnf.xml<br>
<snip><br>
<loadInformation>SCCP41.8-4-3S</loadInformation><br>
</snip><br>
<br>
<br>
/Wes<br>
<br>
On Monday, August 24, 2009 2:03:56 PM , Dave Wolgast
<a class="moz-txt-link-rfc2396E" href="mailto:dwolgas1@rochester.rr.com"><dwolgas1@rochester.rr.com></a> wrote:<br>
<blockquote
cite="mid:e4491a9c0908241103g5cddd842t734dfe0dc04452c@mail.gmail.com"
type="cite">
<div>I have two CUCM 6.1 clusters (6.1.2.1001-4) that needed some new
phone loads applied for 79X2 (to fix a dtmf problem). I applied 8.4(4)
to replace 8.4(1)sr2. I applied the downloaded phone load file to each
tftp server in each cluster using the Software Upgrade menu in platform
administration, then restarted all tftp servers in each cluster.</div>
<div> </div>
<div>I then reset phones, about 100 at a time. I found that one
cluster upgraded without a hitch. However, the other cluster's
phones did not get the new loads when reset. Even when I shut/no shut
switch ports forcing reboots of phones, the old load remained in place.</div>
<div> </div>
<div>I checked Unified Reporting, and database status looked good.</div>
<div> </div>
<div>What else should I look at? Should I try reloading the image to
the second cluster? (I used the same sftp server to upload to both
clusters).</div>
<div> </div>
<div>Thanks for any suggestions!</div>
<br>
-- <br>
Dave Wolgast<br>
Livonia, NY<br>
<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>