Check connectivity to the RCP server by using the ping command. If you do not want to use this username, create a new RCP username by using the ip rcmd remote-username username global configuration command to be used during all copy operations. If you are accessing the switch through a Telnet session and you have a valid username, this username is used, and you do not need to set the RCP username. For UNIX systems, you must add an entry to the.
For example, suppose that the switch contains these configuration lines:. If the switch IP address translates to Switch1. Using RCP, copies the configuration file from a network server to the running configuration or to the startup configuration file. This example shows how to copy a configuration file named host1-confg from the netadmin1 directory on the remote server with an IP address of Then it copies the configuration file host2-confg from the netadmin1 directory on the remote server with an IP address of Using RCP, copies the specified configuration file from the switch running to the specified network server.
You can clear the configuration information from the startup configuration. If you reboot the switch with no startup configuration, the switch enters the setup program so that you can reconfigure the switch with new settings.
To clear the contents of your startup configuration, use the erase nvram: or the erase startup-config privileged EXEC command. To delete a saved configuration from flash memory, use the delete flash: filename privileged EXEC command. Depending on the setting of the file prompt global configuration command, you might be prompted for confirmation before you delete a file. By default, the switch prompts for confirmation on destructive file operations. The configuration replacement and rollback feature replaces the running configuration with any saved Cisco IOS configuration file.
You can use the rollback function to roll back to a previous configuration. The configuration archive provides a mechanism to store, organize, and manage an archive of configuration files. The configure replace privileged EXEC command increases the configuration rollback capability.
As an alternative, you can save copies of the running configuration by using the copy running-config destination-url privileged EXEC command, storing the replacement file either locally or remotely. However, this method lacks any automated file management. The configuration replacement and rollback feature can automatically save copies of the running configuration to the configuration archive. You use the archive config privileged EXEC command to save configurations in the configuration archive by using a standard location and filename prefix that is automatically appended with an incremental version number and optional timestamp as each consecutive file is saved.
You can specify how many versions of the running configuration are kept in the archive. After the maximum number of files are saved, the oldest file is automatically deleted when the next, most recent file is saved. The show archive privileged EXEC command displays information for all the configuration files saved in the configuration archive. The configure replace privileged EXEC command replaces the running configuration with any saved configuration file. When you enter the configure replace command, the running configuration is compared with the specified replacement configuration, and a set of configuration differences is generated.
The resulting differences are used to replace the configuration. The configuration replacement operation is usually completed in no more than three passes. To prevent looping behavior no more than five passes are performed. You can use the copy source-url running-config privileged EXEC command to copy a stored configuration file to the running configuration. When using this command as an alternative to the configure replace target-url privileged EXEC command, note these major differences:.
This command does not remove commands from the running configuration that are not present in the source file. In contrast, the configure replace target-url command removes commands from the running configuration that are not present in the replacement file and adds commands to the running configuration that are not present. You must use a complete configuration file as the replacement file for the configure replace target-url command.
You can also use the configure replace command to roll back changes that were made since the previous configuration was saved. Instead of basing the rollback operation on a specific set of changes that were applied, the configuration rollback capability reverts to a specific configuration based on a saved configuration file. If you want the configuration rollback capability, you must first save the running configuration before making any configuration changes.
Then, after entering configuration changes, you can use that saved configuration file to roll back the changes by using the configure replace target-url command. You can specify any saved configuration file as the rollback configuration. You are not limited to a fixed number of rollbacks, as is the case in some rollback models. Follow these guidelines when configuring and performing configuration replacement and rollback:.
Otherwise, the configuration replacement operation fails. The replacement file must be a complete configuration generated by a Cisco IOS device for example, a configuration generated by the copy running-config destination-url command.
Note If you generate the replacement configuration file externally, it must comply with the format of files generated by Cisco IOS devices. Using the configure replace command with the configuration archive and with the archive config command is optional but offers significant benefit for configuration rollback scenarios.
Before using the archive config command , you must first configure the configuration archive. Starting in privileged EXEC mode, follow these steps to configure the configuration archive:.
Specifies the location and filename prefix for the files in the configuration archive. Optional Sets the maximum number of archive files of the running configuration to be saved in the configuration archive.
Valid values are from 1 to The default is Note Before using this command, you must first enter the path archive configuration command to specify the location and filename prefix for the files in the configuration archive. Optional Sets the time increment for automatically saving an archive file of the running configuration in the configuration archive. Starting in privileged EXEC mode, follow these steps to replace the running configuration file with a saved configuration file:.
Note Enter the path archive configuration command before using this command. The total number of passes also appears. If you do not enter the configure confirm command within the specified time limit, the configuration replacement operation is automatically stopped.
In other words, the running configuration file is restored to the configuration that existed before you entered the configure replace command. Note You must first enable the configuration archive before you can use the time seconds command line option.
Optional Confirms replacement of the running configuration with a saved configuration file. Note Use this command only if the time seconds keyword and argument of the configure replace command are specified. This section describes how to download, upload, and install Cisco IOS XE software bundle files, which contain the system software packages.
You can use this uploaded bundle for future downloads to the same switch or to another switch of the same type. You can install the package files on the switch or you can boot the switch from the IOS XE bundle itself. To display information about the provisioning software that is currently running on the switch, use the show version privileged EXEC command. In the display, check the line that begins with. System bundle file is When the switch is running in installed mode, this line displays the name and location of the booted Cisco IOS XE provisioning file, typically flash:packages.
When the switch is running in bundle mode, this line displays the name and location of the booted Cisco IOS XE bundle file. When the switch is running in installed mode, this command displays information about the set of package files contained in the booted provisioning file. When the switch is running in bundle mode, this command displays information about the set of package files contained in the booted Cisco IOS XE software bundle.
You can upload a Cisco IOS XE bundle file to a network server for backup purposes; the uploaded bundle can be used for future downloads to the same or another switch of the same type. Directory and bundle names are case sensitive.
You can upload a bundle file from the switch to a TFTP server. You can later download this bundle to the switch or to another switch of the same type. Directory and bundle file names are case sensitive. You can later download this bundle to the same switch or to another switch of the same type.
These must be associated with an account on the FTP server. For the RCP copy request to execute successfully, an account must be defined on the network server for the remote username. You can upload a software bundle file from the switch to an RCP server. The method that you use to upgrade Cisco IOS XE software depends on whether the switch is running in installed mode or in bundle mode.
To upgrade the Cisco IOS XE software when the switch is running in installed mode, use the software install privileged EXEC command to install the packages from a new software bundle file. The software install command expands the package files from the specified source bundle file and copies them to the local flash: storage device.
When the source bundle is specified as a tftp: or ftp: URL, the bundle file is first downloaded into the switch's memory RAM ; the bundle file is not copied to local storage media. After the package files are expanded and copied to flash: the running provisioning file flash:packages. Note The software install command is not supported when the switch is running in bundle mode.
Use the software expand privileged EXEC command to convert the switch from bundle mode to installed mode. Download the bundle file to local storage media.
Configure the boot system global configuration command to point to the bundle file. Reload the switch. It shows using the copy command to copy the bundle file to flash:, configuring the boot system variable to point to the bundle file, saving a copy of the running configuration, and finally, reloading the switch.
To convert the running mode of a switch from bundle mode to installed mode, use the software expand running privileged EXEC command. This command expands the packages from the booted IOS XE software bundle and copies them and the provisioning file to the specified to destination.
When you use the software expand running command to convert the switch from bundle mode to installed mode, specify the to destination as f lash:. After you execute the command, configure the boot system command to point to the expanded provisioning file flash:packages. Note The software expand running command is not supported when the switch is running in installed mode. This example shows using the software expand running command to convert the active switch in a switch stack from the bundle running mode to the installed running mode:.
For switch stacks running in installed mode, use the software install source switch privileged EXEC command to install the running software packages from an existing stack member to one or more other stack members that are running different but compatible software packages. This example shows a 2-member stack where each switch is running a different but compatible software packages. The s oftware install source switch command is used to install the packages that are currently running on the standby switch switch 1 onto the active switch switch 2.
For switch stacks running in bundle mode, follow these steps to copy the bundle file from one stack member to another:. Use the copy privileged EXEC command to copy the running bundle from one switch in the stack to the other. To upgrade a switch that is running in installed mode with software packages that are incompatible with the switch stack also running in installed mode , use the software auto-upgrade privileged EXEC command to install the software packages from an existing stack member to the stack member that is running incompatible software.
Upon completion of the auto-upgrade installation, the incompatible switch automatically reloads and joins the stack as a fully functioning member. Note If you configure the global software auto-upgrade enable command, the auto-upgrade functionality is initiated automatically when a switch with incompatible software running in installed mode joins the stack that is running in installed mode.
This example shows a 2-member switch stack; switch 2 is the active switch and switch 1 is running incompatible software. To upgrade a switch that is running in bundle mode with a software bundle that is incompatible with the switch stack also running in bundle mode , follow these steps:. This example shows a 2-member switch stack running in bundle mode; switch 2 is the active switch and switch 1 is running an incompatible bundle.
When a switch running in bundle mode tries to join a stack running in installed mode, use the software auto-upgrade privileged EXEC command to install the incompatible switch's running packages and convert the switch to installed mode.
Upon completion of the auto-upgrade running mode conversion, the incompatible switch automatically reloads and attempts to join the stack in installed mode. This example shows a 2-member switch stack running in installed mode. Switch 2 is the active switch and switch 1 is running in bundle mode.
Note When you use the software auto-upgrade command to convert an incompatible switch to installed mode, the command installs the packages from the incompatible switch's running bundle. If, after you reload and boot the incompatible switch in installed mode, the switch's installed packages are found to be incompatible with the stack, you can use the s oftware auto-upgrade command again.
To convert a switch that is running in installed mode and joining a stack that is running in bundle mode, follow these steps:. After reloading, the incompatible switch boots in bundle mode and joins the stack as a fully functioning member. This example shows a 2-member switch stack running in bundle mode; switch 2 is the active switch and switch 1 is running in installed mode:.
Log in to the switch console. If you have configured a new username or password, enter the credentials instead. Note: The commands may vary depending on the exact model of your switch. In this example, the SG switch is accessed through Telnet. Step 2. To back up a configuration file to a specific destination, enter the following:. Before you proceed with the SCP method, make sure that SSH server authentication is enabled and the corresponding settings have been configured.
Use the copy startup-config dst-url command to copy the startup configuration file to a network server. Note: In this example, the running configuration file in plaintext form is saved to the SCP server with IP address You should now have successfully backed up the configuration files from your switch to a network server through the CLI. To copy a configuration file from a specific source, enter the following:.
For example, a recorded announcement MoH file is available on one cluster and same MoH is required to be played on another cluster, but the required MoH file is not available with the administrator or the administrator who had the file earlier has left the company and the only way to get the same MoH file, is through the Call Manager. In such scenarios, this specified method to download the MoH file comes very handy.
Check the list of all MoH files available on the server with this command:. Skip to content Skip to search Skip to footer. Available Languages. Download Options. Updated: July 29, Contents Introduction.
0コメント