<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<TITLE>Message</TITLE>
<META content="MSHTML 6.00.2900.2802" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=902280715-01022006><FONT face=Arial color=#0000ff size=2>You'd
still have the failure mode where if you DHCP server chokes and the 6608 resets,
you'd get no statically assigned DHCP address. </FONT></SPAN></DIV>
<DIV><SPAN class=902280715-01022006><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=902280715-01022006><FONT face=Arial color=#0000ff size=2>You'd
be better off hanging your TFTP server off of a pair of clustered servers (or
load balanced, at least) and not worry about handling the failover in the 6608
card.</FONT></SPAN></DIV>
<DIV><SPAN class=902280715-01022006><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=902280715-01022006></SPAN> </DIV>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
<DIV></DIV>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left><FONT
face=Tahoma size=2>-----Original Message-----<BR><B>From:</B>
cisco-voip-bounces@puck.nether.net [mailto:cisco-voip-bounces@puck.nether.net]
<B>On Behalf Of </B>Matt Slaga (US)<BR><B>Sent:</B> Tuesday, January 31, 2006
4:19 PM<BR><B>To:</B> Philip Walenta; Mendoza, Anthony R; Cisco
VoIP<BR><B>Subject:</B> RE: [cisco-voip] Catalyst 6608 T1
module<BR><BR></FONT></DIV>
<META content="MSHTML 6.00.2900.2802" name=GENERATOR>
<DIV dir=ltr align=left><SPAN class=531401722-31012006><FONT face=Arial
color=#0000ff size=2>Use DHCP to push two TFTP servers, but use DHCP
reservations to obtain your "static" address.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=531401722-31012006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff
size=2></FONT> </DIV>
<DIV dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> cisco-voip-bounces@puck.nether.net
[mailto:cisco-voip-bounces@puck.nether.net] <B>On Behalf Of </B>Philip
Walenta<BR><B>Sent:</B> Tuesday, January 31, 2006 5:14 PM<BR><B>To:</B>
'Mendoza, Anthony R'; 'Cisco VoIP'<BR><B>Subject:</B> RE: [cisco-voip]
Catalyst 6608 T1 module<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV dir=ltr align=left><SPAN class=276541222-31012006><FONT face=Arial
color=#0000ff size=2>To my knowledge, the 6608 has never supported multiple
TFTP servers.</FONT></SPAN></DIV><BR>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> cisco-voip-bounces@puck.nether.net
[mailto:cisco-voip-bounces@puck.nether.net] <B>On Behalf Of </B>Mendoza,
Anthony R<BR><B>Sent:</B> Tuesday, January 31, 2006 4:03 PM<BR><B>To:</B>
Cisco VoIP<BR><B>Subject:</B> [cisco-voip] Catalyst 6608 T1
module<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV><SPAN class=338300122-31012006><FONT face=Arial
size=2>All,</FONT></SPAN></DIV>
<DIV><SPAN class=338300122-31012006><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=338300122-31012006><FONT face=Arial size=2>Is there a way
to assign multiple TFTP servers in a config on a 6608 when running CatOS and
not using DHCP? I find when I'm going a static IP configuration that I
can only assign a single TFTP server which doesn't give me much failover in
a situation where I lose a CCM and for some reason the device resets (such
as a power outage). I'd be forced to go re-configure it in order to
receive it's configuration. Any way around that
hassle?</FONT></SPAN></DIV>
<DIV><SPAN class=338300122-31012006><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=338300122-31012006><FONT face=Arial
size=2>Thanks,</FONT></SPAN></DIV>
<DIV><SPAN class=338300122-31012006><FONT face=Arial
size=2>-Anthony</FONT></SPAN></DIV></BLOCKQUOTE>
<P>
<HR SIZE=1>
<P></P>
<P><STRONG>Disclaimer:<BR><BR>This e-mail communication and any attachments
may contain confidential<BR>and privileged information and is for use by the
designated<BR>addressee(s) named above only. If you are not the intended
addressee,<BR>you are hereby notified that you have received this
communication in<BR>error and that any use or reproduction of this email or
its contents is<BR>strictly prohibited and may be unlawful. If you have
received this<BR>communication in error, please notify us immediately by
replying to<BR>this message and deleting it from your computer. Thank you.
</STRONG></P></BLOCKQUOTE></BODY></HTML>