Advertisements

If you use "copy tftp run" then the script is applied as if you had sat down
and typed it in. So you can just send the "no username ..." lines.

If you use "copy tftp start" then it replaces the startup-config completely,
so you need to upload the whole configuration. Only the brave use "copy tftp
start", especially if the router is more than 5 minutes run away

Guest

On 28 May 2004 14:46:19 GMT, -cnrc.gc.ca (Walter
Roberson) wrote:
>In article <>,
>Reinhard <> wrote:
>:another question. If I use tftp to upload a new configuration - do I
>:have to upload the whole configuration file or just the changes?
>
>Just the changes.

Only if you are tftping the changes to the running config - ie it acts
like you pasted the changes in while at the config prompt. You'll
want the whole thing if you are copying to the startup-config.

In article <>,
John Rennie <> wrote:
:If you use "copy tftp run" then the script is applied as if you had sat down
:and typed it in. So you can just send the "no username ..." lines.

That's not quite the case. The lines are not applied "as if you had
sat down and typed it in": if it were, then changes to (e.g.) ACLs
could cause you to lose connectivity for the rest of the 'copy' command.
For IOS devices, the 'copy tftp' command reads the -entire- new config
in first, and -then- processes it.

The PIX, on the other hand, only reads one tftp block (512 bytes exactly)
at a time before processing the commands, which *can* lead you
into problems if you change interface IPs or routes: if you don't
restore back the IP or route before the end of the current 512 byte
swath, the copy won't know how to continue on the PIX.
--
"WHEN QUINED, YIELDS A TORTOISE'S LOVE-SONG"
WHEN QUINED, YIELDS A TORTOISE'S LOVE-SONG. (GEB)

Guest

On 30 May 2004 09:21:29 GMT, -cnrc.gc.ca (Walter
Roberson) wrote:
>In article <>,
>John Rennie <> wrote:
>:If you use "copy tftp run" then the script is applied as if you had sat down
>:and typed it in. So you can just send the "no username ..." lines.
>
>That's not quite the case. The lines are not applied "as if you had
>sat down and typed it in": if it were, then changes to (e.g.) ACLs
>could cause you to lose connectivity for the rest of the 'copy' command.
>For IOS devices, the 'copy tftp' command reads the -entire- new config
>in first, and -then- processes it.

Excellent point. One most people don't need to consider, but can be
helpful if you are rearranging something that will affect network
connectivity.

For the original poster, I'll also recommend getting familiar with the
reload command. For example, if the router is not right next to you,
right before changing your config, run "reload in 10". If the changes
are sucessful and you still have connectivity, then do "reload abort".
That way, if you totally dork it up, it'll reboot and save you a trip
to the router to cycle the power. Saved my but a few times,
particulary when changing ACLs.

-cnrc.gc.ca (Walter Roberson) wrote in message news:<c97jbr$qoh$>...
> In article <>,
> Reinhard <> wrote:
> :another question. If I use tftp to upload a new configuration - do I
> :have to upload the whole configuration file or just the changes?
>
> Just the changes.

wrote in message news:<>...
> On 30 May 2004 09:21:29 GMT, -cnrc.gc.ca (Walter
> Roberson) wrote:
>
> >In article <>,
> >John Rennie <> wrote:
> >:If you use "copy tftp run" then the script is applied as if you had sat down
> >:and typed it in. So you can just send the "no username ..." lines.
> >
> >That's not quite the case. The lines are not applied "as if you had
> >sat down and typed it in": if it were, then changes to (e.g.) ACLs
> >could cause you to lose connectivity for the rest of the 'copy' command.
> >For IOS devices, the 'copy tftp' command reads the -entire- new config
> >in first, and -then- processes it.
>
> Excellent point. One most people don't need to consider, but can be
> helpful if you are rearranging something that will affect network
> connectivity.
>
> For the original poster, I'll also recommend getting familiar with the
> reload command. For example, if the router is not right next to you,
> right before changing your config, run "reload in 10". If the changes
> are sucessful and you still have connectivity, then do "reload abort".
> That way, if you totally dork it up, it'll reboot and save you a trip
> to the router to cycle the power. Saved my but a few times,
> particulary when changing ACLs.
>
>
> -Chris

Thank you, this was one of my first questions - how to recover if
changes were wrong btw isn't the command "reload cancel" ??

Share This Page

Welcome to Velocity Reviews!

Welcome to the Velocity Reviews, the place to come for the latest tech news and reviews.

Please join our friendly community by clicking the button below - it only takes a few seconds and is totally free. You'll be able to chat with other enthusiasts and get tech help from other members.
Sign up now!