[cisco-voip] IP Phone TFTP Server Change Problem

[Lelio Fulgenzi]

When we did our migration, we had the following scenario: 

    • same DHCP server 
    • same voice VLANs 
    • different TFTP server 
    • different cluster (on new network) 

We took advantage of the fact that when phones can't communicate to the CallManagers, they get into a tizzy and end up restarting. This restart forces them to send out a new DHCP request. I'm pretty sure if they can't reach the DHCP server after a bit, they send out a new broadcast request (not 100% sure on this one, you'll have to test). 

So before the migration, we modified the TFTP option on our DHCP server and then put in an ACL which prevented access to the old CallManagers. Other than a few phones at a remote site, all went well. 

I'm pretty sure this is also how we changed over DHCP servers earlier in the year, but I could be wrong. 

It's worth trying out. 

--- 
Lelio Fulgenzi, B.A. 
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1 
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN) 
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 
Cooking with unix is easy. You just sed it and forget it. 
- LFJ (with apologies to Mr. Popeil) 


----- Original Message -----
From: "Steven Casper" <SCASPER at mtb.com> 
To: cisco-voip at puck.nether.net 
Sent: Monday, July 25, 2011 10:45:34 AM 
Subject: [cisco-voip] IP Phone TFTP Server Change Problem 




I have about 20 sites to convert from one Call Manager Cluster on 7.1.3 to another on 7.1.5. Testing this weekend we took a site and changed the Voice and Data VLANs to point to new VLANs with new associated IP and IP Helper addresses and reloaded the router. About half of the phones came up on the new Call Manager but the other half did not. They got new IP addresses and all other associated settings but the old TFTP server address stayed in the phone config. Resetting the phones, disconnecting and reconnecting the phones or shut/no shut on the switch ports did not help. The only way to get the phones to register to the new cluster was to erase the IPv4 config on each phone. The phones then reset and received the correct TFTP server address and registered correctly to the new Cluster. 



Anybody seen this before and came up with a fix other than touching each phone? Phones are 7962 running SCCP 9-0-2SR1S 



Thanks, 

Steve ************************************ 
This email may contain privileged and/or confidential information that is intended solely for the use of the addressee. If you are not the intended recipient or entity, you are strictly prohibited from disclosing, copying, distributing or using any of the information contained in the transmission. If you received this communication in error, please contact the sender immediately and destroy the material in its entirety, whether electronic or hard copy. This communication may contain nonpublic personal information about consumers subject to the restrictions of the Gramm-Leach-Bliley Act and the Sarbanes-Oxley Act. You may not directly or indirectly reuse or disclose such information for any purpose other than to provide the services for which you are receiving the information. 
There are risks associated with the use of electronic transmission. The sender of this information does not control the method of transmittal or service providers and assumes no duty or obligation for the security, receipt, or third party interception of this transmission. 
************************************ 
_______________________________________________ 
cisco-voip mailing list 
cisco-voip at puck.nether.net 
https://puck.nether.net/mailman/listinfo/cisco-voip 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20110726/c59c1de9/attachment.html>