[cisco-voip] tftp server 255.255.255.255

[Andy Carse]

Thanks to all that replied to this

We are going to use 3rd party app suggested by Lelio and others as 350 
handsets to do across the patch.


On 02/15/2011 09:54 AM, Andy Carse wrote:
> Hi James,
> The phones were delivered in this state from the reseller all we've 
> done is unboxed them and connected them to the network.
> I suppose if we ungraded to v8 then we could find all the duff 
> handsets rather quickly as they would fail to register (but I don't 
> expect the field guys would like that senario ;-).
> I guess that as there isn't any indication from the web admin that 
> things are broken then maybe this is something that may crop up in 
> other deployments.
>
> I've done the following:-
> reset the handset
> reset the dhcp scope, including expiring the leases
> changed to a different vlan
> sniffer traces show the dhcp options being given to the handset (other 
> handsets that don't have this set that are on the same vlan all work 
> correctly)
> checked for ctl
> The only thing that seems to work is to erase the config and then when 
> the handset restarts it downloads the correct code.
>
> I've tried your suggestion about the show risdb and it works on my lab 
> setup but on site its completely wrong, in that it doesn't match what 
> the handset actually says.
> So I'm wondering if resetting the ris database service may at least 
> clear this database up otherwise its going to be a long march for 
> whoever gets to check the handsets..........
>
>
> On 02/14/2011 12:49 PM, James.Brown at barclayswealth.com wrote:
>> Hi Andy,
>>
>> Out of interest, how did the phones end up with this TFTP server 
>> address? Have you hard-coded it on the CCMadmin device page, or is it 
>> some bug that I narrowly avoided over the years ;-)
>>
>> My suggestions would be:
>>
>> 1. Does a reset help pick up the Option-150 setting? If so, I guess 
>> you would have to do this en-masse from CUCM or by disabling POE on 
>> the switch-port then re-enabling
>>
>> 2. You could obtain a full list of registered phones via "show risdb 
>> query phone" on each subscriber CLI. Then feed this list into CURL 
>> via a shell script
>>
>>   
>> http://$IPPHONE/CGI/Java/Serviceability?adapter=device.statistics.configuration
>>
>> Just pipe all the output into a file and filter it using vim (or 
>> similar) to narrow down to just those phones which are affected.
>>
>> Hope this helps
>>
>> James.
>>
>> -----Original Message-----
>> From: cisco-voip-bounces at puck.nether.net 
>> [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Andy Carse
>> Sent: 14 February 2011 11:30
>> To: cisco-voip
>> Subject: [cisco-voip] tftp server 255.255.255.255
>>
>> I guess I already know the answer, but I'll ask any way.
>>
>> I have possibly several handsets that have been deployed that out of 
>> the box had their tftp server as 255.255.255.255.
>>
>> They are setup for DHCP but the tftp server info doesn't seem to get 
>> updated, I have seen this before but we found it whilst actually 
>> deploying handsets so we checked them as they were rolled out.
>>
>> As such they would have booted up ok and worked assuming they didn't 
>> have extension mobilty setup.
>>
>> No we are in the process of upgrading the firmware for an upgrade due 
>> in a couple of weeks.
>>
>> These handsets won't be able to upgrade is there an "easy" way of 
>> finding these devices?
>>
>> They won't show up in the Device Firmware Load info as they don't 
>> talk to the cluster in the normal way.
>>
>> The only way we have found to recify this is to visit a handset and 
>> erase its config.
>>
>> we have 10 sites and 4000 handsets, so it could take awhile.
>>
>> Currently running 5.1.2 going to 7.1.5su3
>>
>> -- 
>> Rgds Andy
>>
>> _______________________________________________
>> cisco-voip mailing list
>> cisco-voip at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/cisco-voip
>> Barclays Wealth is the wealth management division of Barclays Bank 
>> PLC. This email may relate to or be sent from other members of the 
>> Barclays Group.
>>
>> The availability of products and services may be limited by the 
>> applicable laws and regulations in certain jurisdictions. The 
>> Barclays Group does not normally accept or offer business 
>> instructions via internet email. Any action that you might take upon 
>> this message might be at your own risk.
>>
>> This email and any attachments are confidential and intended solely 
>> for the addressee and may also be privileged or exempt from 
>> disclosure under applicable law. If you are not the addressee, or 
>> have received this email in error, please notify the sender 
>> immediately, delete it from your system and do not copy, disclose or 
>> otherwise act upon any part of this email or its attachments.
>>
>> Internet communications are not guaranteed to be secure or without 
>> viruses. The Barclays Group does not accept responsibility for any 
>> loss arising from unauthorised access to, or interference with, any 
>> Internet communications by any third party, or from the transmission 
>> of any viruses. Replies to this email may be monitored by the 
>> Barclays Group for operational or business reasons.
>>
>> Any opinion or other information in this email or its attachments 
>> that does not relate to the business of the Barclays Group is 
>> personal to the sender and is not given or endorsed by the Barclays 
>> Group.
>>
>> Barclays Bank PLC. Registered in England and Wales (registered no. 
>> 1026167).
>> Registered Office: 1 Churchill Place, London, E14 5HP, United Kingdom.
>>
>> Barclays Bank PLC is authorised and regulated by the Financial 
>> Services Authority.
>>
>

-- 
Rgds Andy