tftp access-lists

[Seth]

Hi,

How does one go about tftp'ing an access list from a sever to a cisco
2500 router? I have a decent idea how, but I'd hate to overwrite the
whole config by accident. Of course if it is necessary to load in the
entire config, I can keep a copy offline and do that instead, but I
could still use a hint as to the correct tftp command from the router.

Thanks,

Seth

[Barton F. Bruce]

In article <5u9cfk$g...@pasilla.bbnplanet.com>, Barry Margolin <bar...@bbnplanet.com> writes:
> In article <1997Aug30.032557.1@eisner>,
> Barton F. Bruce <br...@eisner.decus.org> wrote:
>>Consider carefully any problems you may create if the list affects the
>>path the TFTP is taking. It may be best to define an alternate list
>>from scratch, and include at the end of the file the commands to
>>switch the references to the old list to be to the new one.

>Actually, this is one of the reasons to prefer configuring over the net
>rather than from a network terminal. The router reads the entire file
>before processing any of the commands, so you don't have to worry about

You posted that before, too, I sure hope it is always true and that cisco
is committed to keeping it so. I have been afraid to count on it because
I have never seen it affirmed by cisco (probably some place I havn't
read yet). And what if I am doing a CONF NET and am sucking in a WHOLE
monster config file (suitably rigged with appropriate "NO ..."s) and there
isn't space for that in DRAM? Some folks keep extensive comments
in their external configs too. Will CONF NET revert to line by line over
the net mode lacking memory for the whole, or simply fail?

If only they would use in memory buffers where adequate DRAM
exists for COPY TFTP FLASH and preload them before FLH reboots
from ROMs to allow writing to flash.

They already keep the SHO FLH buffers intact across reloads.