Cisco auto-copy-software

Cisco Community. Thank you for your support! We're happy to announce that we met our goal for the Community Helping Community campaign! Turn on suggestions. Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type. Showing results for. Search instead for. Did you mean:. All Community This category This board.

Cisco Community : Technology and Support : Networking : Networking Documents : How to upgrade a Cisco Catalyst switch with an incompatible software image in a multiswitch sta How to upgrade a Cisco Catalyst switch with an incompatible software image in a multiswitch stack configuration.

Labels: Other Switching. Resolution In order to upgrade a Cisco Catalyst switch that has an incompatible software image, issue the archive copy-sw privileged EXEC command. In privileged EXEC mode and to start from the stack member to be upgraded, perform these steps in order to copy the running image file from the Flash memory of a different stack member: Access the global configuration mode.

Issue the reload slot stack-member-number command. Reset the updated stack member in order to put this configuration change into effect. Latest Contents. Internal error when running basic Ansible playbook. Created by s. R1 config-archive path flash:. If you encounter a technical issue on the site, please open a support case.

Communities: Chinese Japanese Korean. All Rights Reserved. The Cisco Learning Network. VIP Perspectives. The importance of the configuration files of the network can be seen from many administrative perspectives: Compare and validate configurations between devices. In case of any damage of the equipment, configuration files could be used to restore the operational state of the network with a simple copy and paste of the configuration in another device.

To rollback configurations to a previous state. R1 conf t Enter configuration commands, one per line. R1 archive config!! Time Variable in Path We could also configure a time variable in the naming convention of the archive configuration. Archive Write-Memory Option R1 config archive R1 config-archive write-memory R1 config-archive exit If we execute the "write memory" or "copy running-config startup-config" commands we can see that the configuration is automatically stored in the TFTP folder.

Archive Time-Period Option R1 config archive R1 config-archive time-period R1 config-archive exit The next backup will be performed in one week exactly time in minutes , but what if we would like to configure this periodicity with an explicit date time?

Elvin Arias. Sort by:. Search this feed Skip Feed View This Post. August 23, at PM. This was very useful, thank you. Log In to Comment.

View This Post. August 7, at PM. Welcome, Martin! August 1, at AM. Thank you so much. It helped me a lot. Thanks, Selva. More comments 1 of 3. February 22, at PM. Hi, Is there something similar on Cisco Wireless controllers? Thank you, Carlos. July 23, at PM. Thanks for the great write up. R1 config-archive path t null I would prefer a date and time. Hi Brad, By default Cisco devices show the time in the debugs or logging in terms of "Uptime" of the device the time past since the device was turned on instead of "Datetime".

Good to know you liked the article. HTH, Elvin. February 11, at PM. This space is needed to store the. For example, if the. Extract the. After you extract the. You need to find the path where the. Note: This boot system switch all has been brought down to a second line due to spatial considerations.

Reload the switch and verify that the switch runs the new Cisco IOS software release after the reload:. A switch stack can be managed either with the web device manager or with the CLI. If you manage the switch with the CLI, you do not need the. This section explains the IOS upgrade with the. It is assumed that you have already configured the switch stack with an IOS image. This section explains how to copy and upgrade the new IOS in the switch stack.

Note: The commands archive download-sw and archive upload-sw are applicable only for. This output shows the stack member and the master in this stack:. You can verify the available memory in the Flash file system of both switches individually as this example output shows:. In a Catalyst switch stack, flash: represents the Flash file system of the master switch.

In this example, the dir flash: command displays the contents of the master switch Switch 2 which is flash Reload the switch and verify that the switch runs the new Cisco IOS software version after the reload:.

Certain show commands are supported by the Output Interpreter Tool registered customers only , which allows you to view an analysis of show command output. This document provides solutions to known issues with the TFTP server. You see this error when the Cisco IOS image is corrupt or a.

In order to resolve the issue, complete these steps:. If the error message still appears, format the Flash and reload the switch. After the IOS upgrade, any one or more of the switches do not boot with the new images. Or, when you add a switch to the existing stack and the newly added switch has a different Cisco IOS software release than the existing switch stack, the new switch is unusable.

The switch stack has a feature called auto-upgrade which is enabled by default. This feature enables the switch stack to automatically upgrade the IOS on the newly added switch. Sometimes this auto-upgrade fails to upgrade the IOS of the newly added switch.

You see this message sequence when you add the switch to the existing stack. Note: The auto-upgrade feature must be enabled to upgrade the switch in version-mismatch VM mode. By default, auto-upgrade is enabled. You can check the status of auto-upgrade by using the show boot privileged EXEC command and by checking the auto upgrade line in the display.

You can disable auto-upgrade by using the no boot auto-copy-sw global configuration command on the stack master. Upgrade the member switch that has an incompatible software image using the archive copy-sw privileged EXEC command. This command copies the software image from an existing stack member to the one with the incompatible software.

The affected switch automatically reloads and joins the stack as a fully functioning member. If you do not specify the stack member number, the running image file is copied to all stack members by default.

For the source-stack-member-number , specify the number of the stack member from which to copy the running image file. The stack member number range is 1 to 9. This archive copy-sw command copies the current running IOS image from switch 1 to switch 3 on the switch stack. You can use this method if you use the device manager to manage the switch stack. It is assumed that you already have the. Configure the boot variable on the new switch.

This step is not mandatory. But if you disconnect this switch out of the stack in the future, the switch might not boot the correct IOS.