[cisco-voip] 7911s coming with hardcoded tftp server?

Tue Aug 24 15:50:37 EDT 2010

Jonathan,

The bug is updated, it will take ~24 hours to display on Cisco.com. 
CiscoCM1 is the only change I am aware of so far though the boot 
sequence is maybe not as consistent as it could be between phone models.

I do not know of any way of automatically clearing that information.  It 
would be good to open a TAC case and provide information of how you 
received these phones.  There does appear to be an issue in QA or MFG if 
you received devices that still retain pre-existing configuration.

/Wes

Madziarczyk, Jonathan wrote:
>
> Awesome....never saw this message before J
>
>  
>
> I assume that "Remove support for CiscoCM1" was the only notable 
> change listed in that super secret bug?
>
>  
>
> Dear valued Cisco Bug Toolkit customer, the bug ID CSCsb56599 you 
> searched contains proprietary information that cannot be disclosed at 
> this time; therefore, we are unable to display the bug details. Please 
> note it is our policy to make all externally-facing bugs available in 
> Bug Toolkit to best assist our customers. As a result, the system 
> administrators have been automatically alerted to the problem.
>
> While we are working to resolve this issue, we invite you to reach out 
> to the experts on the Bug Toolkit Support Community 
> <https://supportforums.cisco.com/community/netpro/idea-center/btk>. 
> You may find answers there to your Bug Toolkit questions, or post your 
> feedback on our forum as well. Thank you.
>
> Note: Some product enhancement requests and documentation bugs may not 
> be available in Bug Toolkit.
>
>  
>
> It sounds like hardcoded TFTP servers on phones is a somewhat common 
> experience.  Is there a procedure for wiping the phone, or should I 
> continue to **# and delete the record when I find it on phones?...or 
> is there a better way that doesn't require menu navigation?
>
>  
>
> JM
>
>  
>
> ------------------------------------------------------------------------
>
> *From:* Wes Sisk [mailto:wsisk at cisco.com]
> *Sent:* Tuesday, August 24, 2010 2:15 PM
> *To:* Madziarczyk, Jonathan
> *Cc:* cisco-voip at puck.nether.net
> *Subject:* Re: [cisco-voip] 7911s coming with hardcoded tftp server?
>
>  
>
> Yes,
>
> Newer devices do not use the same TFTP/CM resolution sequence that 
> older devices did:
> CSCsb56599    Remove support for CiscoCM1
>
> /Wes
>
> Madziarczyk, Jonathan wrote:
>
> Thanks Brian,
>
>  
>
> Unfortunately that option doesn't seem to overwrite what's hardcoded 
> on the phone.  We already have option 150 set up on the DHCP server to 
> alleviate the problem that occurs with option 66 and PXE boot on PCs 
> on the same subnet as the phones (not recommended, I know, but some 
> things we can't fix as easily as others).
>
>  
>
> JM
>
>  
>
> ------------------------------------------------------------------------
>
> *From:* Brian Schultz [mailto:bms314 at gmail.com]
> *Sent:* Tuesday, August 24, 2010 11:31 AM
> *To:* Madziarczyk, Jonathan
> *Cc:* cisco-voip at puck.nether.net <mailto:cisco-voip at puck.nether.net>
> *Subject:* Re: [cisco-voip] 7911s coming with hardcoded tftp server?
>
>  
>
> I had a similar problem with 7925 phones.  I had to configure option 
> 66 in my DHCP server and then they worked fine. 
>
> Brian
>
>
> On Tue, Aug 24, 2010 at 11:20 AM, Madziarczyk, Jonathan 
> <JMad at cityofevanston.org <mailto:JMad at cityofevanston.org>> wrote:
>
> So I just got a batch of 7911G phones in and they wouldn't register to 
> save their lives.
>
>  
>
> After some investigation I found that they were all set with a 
> hardcoded TFTP server
>
> (Option 8) TFTP Server 1: 131.248.46.128
>
>  
>
> Once I unlocked the phone (**#) I was able to delete the entry and the 
> phone autoconfiged and everything works fine now.
>
>  
>
> Has anyone seen this before?  I did an ARIN and it's a SE Asian address.
>
>  
>
> % APNIC found the following authoritative answer from: whois.apnic.net <http://whois.apnic.net>
> % [whois.apnic.net <http://whois.apnic.net> node-2]
> % Whois data copyright terms    http://www.apnic.net/db/dbcopyright.html
> *_inetnum_*:      131.248.0.0 - 131.248.255.255
> netname:      CTC-NET
> country:      JP
> descr:        ITOCHU Techno-Solutions Corporation
> admin-c:      HK64-AP <http://wq.apnic.net/apnic-bin/whois.pl?searchtext=HK64-AP&form_type=advanced>
> tech-c:       HK64-AP <http://wq.apnic.net/apnic-bin/whois.pl?searchtext=HK64-AP&form_type=advanced>
> status:       ASSIGNED PORTABLE
> mnt-by:       MAINT-JPNIC <http://wq.apnic.net/apnic-bin/whois.pl?searchtext=MAINT-JPNIC&form_type=advanced>
> mnt-lower:    MAINT-JPNIC <http://wq.apnic.net/apnic-bin/whois.pl?searchtext=MAINT-JPNIC&form_type=advanced>
> changed:      hm-changed at apnic.net <mailto:hm-changed at apnic.net> 20050408
> changed:      ip-apnic at nic.ad.jp <mailto:ip-apnic at nic.ad.jp> 20070115
> source:       APNIC
>
>  
>
>  
>
> Ideas on what's going on here?
>
>  
>
> JM
>
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net <mailto:cisco-voip at puck.nether.net>
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>  
>
>  
>
>
> ------------------------------------------------------------------------
>
>
>  
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net <mailto:cisco-voip at puck.nether.net>
> https://puck.nether.net/mailman/listinfo/cisco-voip
>   
> ------------------------------------------------------------------------
>
> _______________________________________________
> 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/20100824/5554391f/attachment.html>