The credentials used are cisco and cisco as the username and password. Step 3. Press Y on your keyboard to overwrite the existing configuration file. You should now have successfully downloaded the configuration file into the switch through the CLI.
SGX copy [running-config startup-config] [dst-url] [exclude include-encrypted include-plaintext] The parameters are: running-config — The configuration file that contains the current configuration, including any changes applied in any management sessions since the last reboot. The predefined URL aliases cannot be configured. This secure option is applied by default, if no secure option is configured.
Download Configuration Files Step 1. To copy a configuration file from a specific source, enter the following: SGX copy [src-url] [running-config startup-config] The parameters are: src-url — The location URL of the source file to be copied. The predefined URL aliases can be configured. Guidelines: Use the copy s rc -url running-config command to load a configuration file from a network server to the running configuration file of the switch.
The switch and the TFTP server must be in the same subnetwork if you do not have a router to route traffic between subnets. Check connectivity to the TFTP server by using the ping command. The permission on the file should be world-read. To create an empty file, enter the touch filename command, where filename is the name of the file you will use when uploading it to the server.
Permissions on the file should be world-write. To configure the switch by using a configuration file downloaded from a TFTP server, follow these steps:. Step 3 Log into the switch through the console port, the Ethernet management port, or a Telnet session. The configuration file downloads, and the commands are executed as the file is parsed line-by-line. This example shows how to configure the software from the file tokyo-confg at IP address To upload a configuration file from a switch to a TFTP server for storage, follow these steps:.
Step 2 Log into the switch through the console port, the Ethernet management port, or a Telnet session. This example shows how to upload a configuration file from a switch to a TFTP server:. When you copy a configuration file from the switch to a server by using FTP, the Cisco IOS software sends the first valid username in this list:.
The variable username is the username associated with the current session, switchname is the configured hostname, and domain is the domain of the switch. The username and password must be associated with an account on the FTP server. Use the ip ftp username and ip ftp password commands to specify a username and password for all copies.
Include the username in the copy command if you want to specify only a username for that copy operation. If the server has a directory structure, the configuration file is written to or copied from the directory associated with the username on the server. For example, if the configuration file resides in the home directory of a user on the server, specify that user's name as the remote username.
Before you begin downloading or uploading a configuration file, do the following:. The switch and the FTP server must be in the same subnetwork if you do not have a router to route traffic between subnets. Check connectivity to the FTP server by using the ping command. You can enter the show users privileged EXEC command to view the valid username.
If you do not want to use this username, create a new FTP username by using the ip ftp username username global configuration command 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 FTP username. Include the username in the copy command if you want to specify a username for only that copy operation.
This step is required only if you override the default remote username or password. Copies the configuration file from the FTP 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 home directory for user netadmin1 on the remote server with an IP address of This example shows how to specify a remote username of netadmin1. The software copies the configuration file host2-confg from the home directory for user netadmin1 on the remote server with an IP address of Copies the specified configuration file to the specified location on the FTP server.
This example shows how to copy the running configuration file named switch2-confg to the netadmin1 directory on the remote host with an IP address of This example shows how to store a startup configuration file on a server by using FTP to copy the file:.
To copy configuration files using RCP you need access to a server that supports the remote shell rsh. Most UNIX systems support rsh.
Because you are copying a file from one place to another, you must have read permission on the source file and write permission on the destination file. If the destination file does not exist, RCP creates it for you. When you copy a configuration file from the switch to a server, the Cisco IOS software sends the first valid username in this list:.
For example, if the user is connected to the router through Telnet and was authenticated through the username command, the switch software sends the Telnet username as the remote username.
For a successful RCP copy request, you must define an account on the network server for the remote username. If the server has a directory structure, the configuration file is written to or copied from the directory associated with the remote username on the server. For example, if the configuration file is in the home directory of a user on the server, specify that user's name as the remote username. Before you begin downloading or uploading a configuration file by using RCP, do the following:.
The switch and the server must be in the same subnetwork if you do not have a router to route traffic between subnets. 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. The Backup Configuration File or log of the switch is useful for troubleshooting or if the device accidentally gets reset.
This contains manual copies of files used for protection against system shutdown or for the maintenance of a specific operating state. You can use this file to update or restore the switch back to its functional state. This article will guide you on how to download or back up a system configuration file through any of the following methods:.
Step 1. Log in to the web-based utility of your switch. Note: If you already have changed the password or created a new account, enter your new credentials instead. Step 3. Note: The available menu options may vary depending on the device model. Step 4. Click the Backup File radio button to back up a configuration file.
Step 5. In the Source File Type area, click the radio button of the type of file that you want to be backed up. The switch maintains the following configuration files. Step 2.
0コメント