<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<TITLE>weirdness with DHCP and 7960 phones..</TITLE>
<META content="MSHTML 6.00.2900.2802" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=900395220-10042006><FONT face=Arial
color=#0000ff size=2>It's true, the 7960s do not obey the DHCP
protocol.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=900395220-10042006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=900395220-10042006><FONT face=Arial
color=#0000ff size=2>If they cannot talk to a DHCP server, they will use
whatever previous address they had.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=900395220-10042006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=900395220-10042006><FONT face=Arial
color=#0000ff size=2>We have complained to Cisco before about this disregard for
the protocol and were told it is "by design".</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=900395220-10042006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=900395220-10042006><FONT face=Arial
color=#0000ff size=2>Our solution was to make gigantic DHCP pools for phones so
that there is plenty of address space available and it is unlikely that we will
have IP conflicts.</FONT></SPAN></DIV>
<DIV> </DIV><!-- Converted from text/plain format -->
<P><FONT size=2>---<BR>Bill Simon - bills@tns.its.psu.edu - (814) 865-2270<BR><A
href="http://tns.its.psu.edu/">http://tns.its.psu.edu/</A><BR><BR></FONT></P>
<DIV> </DIV><BR>
<BLOCKQUOTE dir=ltr
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> Tim Reimers
[mailto:tim.reimers@asheville.k12.nc.us] <BR><B>Sent:</B> Monday, April 10,
2006 4:41 PM<BR><B>To:</B> cisco-voip@puck.nether.net<BR><B>Subject:</B>
[cisco-voip] weirdness with DHCP and 7960 phones..<BR></FONT><BR></DIV>
<DIV></DIV><!-- Converted from text/rtf format --><BR><BR>
<P><FONT face=Arial size=2>Hi everyone---</FONT> </P>
<P><FONT face=Arial size=2>We had a weird occurrence in the last few days I
thought I'd run past the group to see what everyone thought...</FONT> </P><BR>
<P><FONT face=Arial size=2>A vendor (who shall remain nameless) rebuilt our
CCM -- and in the process, it turns out, failed to reinstall the DHCP
server/scope and TFTP options..</FONT></P>
<P><FONT face=Arial size=2>All worked fine until we had a power glitch of some
sort and the phones rebooted...</FONT> </P>
<P><FONT face=Arial size=2>At that point- well, that's when things get
weird..</FONT> </P>
<P><FONT face=Arial size=2>You'd think that NONE of the phones would come back
up ---</FONT> </P>
<P><FONT face=Arial size=2>but about 20 out of 75 did just that... with no
DHCP server.</FONT> </P>
<P><FONT face=Arial size=2>Mine, which was one that did it, is NOT set for
static addressing (none are)...</FONT> </P>
<P><FONT face=Arial size=2>Smoehow, it retained it's IP settings, though it
took a while to boot...</FONT> </P><BR>
<P><FONT face=Arial size=2>my question??? Wassup with that? I thought
"no dhcp, no boot', no NOTHING....for ALL of the phones on that subnet?</FONT>
</P>
<P><FONT face=Arial size=2>Why did some come up and work and others not? Is
there some magic in some of the boot code?</FONT> </P>
<P><FONT face=Arial size=2>(except perhaps a phone with a 169.254.x.x address,
trying to find a CCM, a load ID ,etc..)</FONT> </P>
<P><FONT face=Arial size=2>Tim</FONT> </P></BLOCKQUOTE></BODY></HTML>