copy

The copy command uploads and downloads files to and from the switch. You can also use the copy command to manage the dual images (active and backup) on the file system. Upload and download files from a server using FTP, TFTP, Xmodem, Ymodem, and Zmodem. If FTP is used, a password is required.

SFTP and SCP are available as additional transfer methods if the software package supports secure management. CLI- based file transfers using the HTTP and HTTPS protocols are supported on selected platforms where a native wget utility is available.

Replace the source and destination parameters with the options in Table 1. For the url source or destination, use one of the following values:

{xmodem | tftp://ipaddr|hostname|ip6address|hostname/filepath/filename [noval] | sftp|scp://username@ipaddr | ipv6address/filepath/filename | ftp://user@ipaddress | hostname/filepath/filename | http://{user@}ipaddr|hostname/filepath/filename | https://{user@}ipaddr|hostname/filepath/filename}

The optional source option parameters specify the source-interface or source IP address for the copy command. The selected source-interface IP address is to be used for filling the IP header of management protocol packets (SCP, SFTP and TFTP). This allows security devices (firewalls) to identify the source packets coming from the specific switch. If a source-interface is not specified, the primary IP address of the originating (outbound) interface is used as source address. When the user selects the source interface for SCP, SFTP, TFTP applications, it (re)bind the interface source IP address with the server. The source interface is not supported for HTTP/HTTPS protocols.

The verify | noverify options are only available if the image/configuration verify options feature is enabled (see file verify). verify specifies that digital signature verification will be performed for the specified downloaded image or configuration file. noverify specifies that no verification will be performed.

For HTTPS transfers, the [checkcert | nocheckcert] options are available to enable or disable server certificate validation. This option is valid only for HTTPS file transfer. If no option is specified, default action is applied for HTTPS file transfer.

The keyword ias-users supports the downloading of the IAS user database file. When the IAS users file is downloaded, the switch IAS user's database is replaced with the users and its attributes available in the downloaded file. In the command copy url ias-users, for url one of the following is used for IAS users file:

{ { tftp://<ipaddr | hostname> | <ipv6address | hostname> /<filepath>/<filename> } | { sftp | scp://<username>@<ipaddress>/<filepath>/<filename>} }

For FTP, TFTP, SFTP, and SCP, the ipaddr|hostname parameter is the IP address or host name of the server, filepath is the path to the file, and filename is the name of the file you want to upload or download. For SFTP and SCP, the username parameter is the username for logging into the remote server via SSH.

For platforms that include stacking, use the optional [unit unit id] parameter (when available) to specify the stack member to use as the source for the item to copy. If no unit is specified, the item is copied from the stack master.

To copy OpenFlow SSL certificates to the switch using TFTP or XMODEM, using only the following options pertinent to the OpenFlow SSL certificates.

Example: The following shows an example of downloading and applying ias users file.

(Routing) #copy tftp://10.131.17.104/aaa_users.txt ias-users

Mode........................................... TFTP
Set Server IP.................................. 10.131.17.104
Path........................................... ./
Filename....................................... aaa_users.txt
Data Type...................................... IAS Users

Management access will be blocked for the duration of the transfer
Are you sure you want to start? (y/n) y

File transfer operation completed successfully.

Validating and updating the users to the IAS users database.

Updated IAS users database successfully.

(Routing) #

Example: The following shows an example of the command to copy running config to a remote system URL for upload operation.

(Routing) #copy system:running-config tftp://10.89.105.143/run-cfg

Mode........................................... TFTP
Set Server IP.................................. 10.89.105.143
Path........................................... ./
Filename....................................... run-cfg
Data Type...................................... Text Configuration
Source Filename................................ running-config

Management access will be blocked for the duration of the transfer
Are you sure you want to start? (y/n) y

File transfer in progress. Management access will be blocked for the duration of the transfer. Please
wait...

File transfer operation completed successfully.

(Routing)#