Open for Voting
over 1 year ago

I just configured the Cisco router and......

  • This is a very good plan.  I believe my instructor said that in his case, one command and the return broke the remote connection to the device.  He had the code, he always had his putty logging every command, but once the connection was broke, game over.  Time to run to the device console connection.

  • DOH!

    I will remember to save the config.

    I will remember to save the config.

    I will remember to save the config.

    I will remember to save the config.

    I will remember to save the config.

    I will remember to save the config.

    I will remember to save the config.

    I will remember to save the config.

    I will remember to save the config.

    I will remember to save the config.

  • This is (part of) why when I do major config changes, I type the commands in Notepad and paste them into the CLI. These usually include a "copy run start" at the end, or I type that manually after verifying that the changes took.
    From Notepad, it's easy to drop the change into a ticketing system either before or after the change is made too, if that's how you roll.

  • I know someone that did that.  Well, way on the other side of the complex a good 10 minutes away.  He said he had to jump up, grab a console cable and hoof it over there before the calls started flooding in.  Now imagine this was my Cisco instructor by night, network admin by day.

  • I would guess we have all been there.  Of course, it would be more painful if the router was 725 miles away, and there was no one else at the remote location to assist with reconfiguring it.