<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: Verdana; font-size: 10pt; color: #000000'>Thanks Wes. That looks like the issue. The DHCP team used option 66 rather than 150. I just assumed they used 150.<br><br>We're in the process of adding a custom option 150. We left 66 in there and it didn't work. We're gonna try taking 66 out.<br><br>---<br>Lelio Fulgenzi, B.A.<br>Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1<br>(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)<br>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<br>Cooking with unix is easy. You just sed it and forget it. <br> - LFJ (with apologies to Mr. Popeil)<br><br><br>----- Original Message -----<br>From: "Wes Sisk" <wsisk@cisco.com><br>To: "Lelio Fulgenzi" <lelio@uoguelph.ca><br>Cc: "cisco-voip voyp list" <cisco-voip@puck.nether.net><br>Sent: Tuesday, July 13, 2010 2:14:07 PM GMT -05:00 US/Canada Eastern<br>Subject: Re: [cisco-voip] slow 7936 boot times (packet capture added)<br><br>
The DHCP Offer does not include an option 150 which would normally
identify the TFTP server address. DHCP offer does include Option 66.
Option 66 is usually a DNS name to be resolved. In this capture option
66 is an IP address. Based on the phone repeatedly querying CiscoCM1 it
seems pretty clear that the phone did not take the option 66 or option
150 for TFTP server. CiscoCM1 is the default DNS name that is queried
to get TFTP address if one is not identified by other means.<br>
<br>
/Wes<br>
<br>
On Tuesday, July 13, 2010 12:56:09 PM, Lelio Fulgenzi
<a class="moz-txt-link-rfc2396E" href="mailto:lelio@uoguelph.ca" target="_blank"><lelio@uoguelph.ca></a> wrote:<br>
<blockquote cite="mid:316713662.1509531279040169675.JavaMail.root@simcoe.cs.uoguelph.ca">
<style>p { margin: 0; }</style>
<div style="font-family: Verdana; font-size: 10pt; color: rgb(0, 0, 0);">Find
two packet captures, one raw and one filtered with the IPADDR and MAC
of the phone.<br>
<br>
Interesting how the phone is asking for CiscoCM1.uoguelph.ca over and
over again.<br>
<br>
I plugged in the conference phone about 50 seconds or so after the
capture started.<br>
<br>
Filter: (ip.addr == 10.104.25.100) or (eth.addr == 00:e0:75:24:dc:da)<br>
<br>
---<br>
Lelio Fulgenzi, B.A.<br>
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1<br>
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)<br>
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<br>
Cooking with unix is easy. You just sed it and forget it. <br>
- LFJ (with apologies to Mr. Popeil)<br>
<br>
<br>
----- Original Message -----<br>
From: "Wes Sisk" <a class="moz-txt-link-rfc2396E" href="mailto:wsisk@cisco.com" target="_blank"><wsisk@cisco.com></a><br>
To: "Lelio Fulgenzi" <a class="moz-txt-link-rfc2396E" href="mailto:lelio@uoguelph.ca" target="_blank"><lelio@uoguelph.ca></a><br>
Cc: "cisco-voip voyp list" <a class="moz-txt-link-rfc2396E" href="mailto:cisco-voip@puck.nether.net" target="_blank"><cisco-voip@puck.nether.net></a><br>
Sent: Tuesday, July 13, 2010 11:56:37 AM GMT -05:00 US/Canada Eastern<br>
Subject: Re: [cisco-voip] slow 7936 boot times<br>
<br>
Packet capture please.<br>
<br>
2 things come to mind:<br>
* Phone is waiting for CDP exchange with switch. The phone waits for
quite some time to receive CDP so it knows what voice vlan to use.
Eventually it times out and assumes no CDP/trunk and behaves as access
device.<br>
* DHCP server never completes the DHCP transaction or the transaction
is significantly delayed. Along the same lines I saw some challenges
with the options returned from a DHCP server that caused 7936 phone to
not parse dhcp response.<br>
<br>
Packet Capture :)<br>
<br>
/Wes<br>
<br>
On Tuesday, July 13, 2010 11:30:51 AM, Lelio Fulgenzi
<a class="moz-txt-link-rfc2396E" href="mailto:lelio@uoguelph.ca" target="_blank"><lelio@uoguelph.ca></a>
wrote:<br>
<blockquote cite="mid:1711566240.1480861279035051363.JavaMail.root@simcoe.cs.uoguelph.ca">
<style>p { margin: 0; }</style>
<div style="font-family: Verdana; font-size: 10pt; color: rgb(0, 0, 0);">We
have had issues raised with 7936 conference phones taking between 10
and 15 minutes to boot up. I'm testing one right now that is taking 5
1/2 minutes. This was never the case. The only difference we can
remember making is switching from Windows DHCP to central DHCP
(Infoblox solution). I'll be doing some sniffing soon, but essentially
what we see is the following:<br>
<ul>
<li>power up</li>
<li>Cisco logo on screen for a bit</li>
<li>"Configuring IP... Press Menu to reconfigure" (5 1/2 min)</li>
<li>"Station IP: <ipaddr> Contacting: <tftpipaddr>"
(quick)</li>
<li>"Registering: <subipaddr>" (quick)</li>
</ul>
I am able to ping the phone from the sub very quickly after power up
(even after a config erase).<br>
<br>
Any ideas?<br>
<br>
<br>
<br>
---<br>
Lelio Fulgenzi, B.A.<br>
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1<br>
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)<br>
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<br>
Cooking with unix is easy. You just sed it and forget it. <br>
- LFJ (with apologies to Mr. Popeil)<br>
<br>
</div>
<pre><hr width="90%" size="4">
_______________________________________________
cisco-voip mailing list
<a class="moz-txt-link-abbreviated" href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a>
<a class="moz-txt-link-freetext" href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a>
</pre>
</blockquote>
<br>
</div>
</blockquote>
<br>
</div></body></html>