From: Mas Kato (tealp729@xxxxxxxx)
Date: Tue May 01 2001 - 02:21:49 GMT-3
It looks like when 'dialer watch' was introduced with 11.3(2)T it only
supported IGRP and EIGRP. It appears to have become "dynamic
protocol-independent" with 12.0.
Because of the connectionless, unreliable nature of UDP, about the only
things you can normally do with most implementations of TFTP are
increase the timeout and possibly turn on checksumming. Neither of these
will help with your throughput, but the transfer would be more
delay-tolerant and files with bad checksums would be discarded.
So unless you can provide some sort of end-to-end QoS for TFTP, there's
not much else you can do... Are FTP or rcp options available to you?
Regards,
Mas Kato
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
Chuck Church
Sent: Monday, April 30, 2001 8:33 PM
To: ccielab@groupstudy.com
Subject: Dialer watch for OSPF???
Anyone,
I'm seeing conflicting info on CCO concerning dialer watch and
OSPF.
Some documents said it only supports (E)IGRP, others said also OSPF.
The
CCO feature Navigator didn't help. Any idea what version started
allowing
OSPF to be dialer watched? Also, does anyone have any hints for
improving
TFTP performance over slow wan links or the Internet? I didn't see any
UDP
global config parameters like there are for TCP. Even though I'm using
Solar Winds rather than the buggy Cisco server, I get lots of timeouts,
and
today an image with a bad checksum, even though the copy claimed to be
ok.
Thanks,
Chuck Church
**Please read:http://www.groupstudy.com/list/posting.html
**Please read:http://www.groupstudy.com/list/posting.html
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:30:31 GMT-3