Managing Files on the Controller
You can transfer the following types of files between the controller and an external server or host:
|
|
A specified file in the controller’s flash file system, or a compressed archive file that contains the entire content of the flash file system |
|
|
You back up the entire content of the flash file system to a compressed archive file, which you can then copy from the flash system to another destination.
|
|
|
Configuration file, either the active running configuration or a startup configuration |
You can use the following protocols to copy files to or from a controller:
|
|
File Transfer Protocol (FTP): Standard TCP/IP protocol for exchanging files between computers. |
|
|
Trivial File Transfer Protocol (TFTP): Software protocol that does not require user authentication and is simpler to implement and use than FTP. |
|
|
Secure Copy (SCP): Protocol for secure transfer of files between computers that relies on the underlying Secure Shell (SSH) protocol to provide authentication and security. |
|
|
You can use SCP only for transferring image files to or from the controller, or transferring files between the flash file system on the controller and a remote host. The SCP server or remote host must support SSH version 2 protocol.
|
Table 1 lists the parameters that you configure to copy files to or from a controller.
Table 1: File Transfer Configuration Parameters
|
Server Type
|
Configuration
|
|
Trivial File Transfer Protocol (TFTP)
|
|
|
IP address of the server |
|
|
File Transfer Protocol (FTP)
|
|
|
IP address of the server |
|
|
username and password to log into server |
|
|
Secure Copy (SCP)
You must use the CLI to transfer files with SCP.
|
|
|
IP address of the server or remote host |
|
|
username to log into server |
|
|
absolute path of filename (otherwise, SCP searches for the file relative to the user’s home directory) |
|
For example, you can copy an ArubaOS image file from an SCP server to a system partition on a controller or copy the startup configuration on a controller to a file on a TFTP server, You can also store the contents of a controller’s flash file system to an archive file which you can then copy to an FTP server. You can use SCP to securely download system image files from a remote host to the controller or securely transfer a configuration file from flash to a remote host.
Transferring ArubaOS Image Files
You can download an ArubaOS image file onto a controller from a TFTP, FTP, or SCP server. In addition, the WebUI allows you to upload an ArubaOS image file from the local PC on which you are running the browser.
When you transfer an ArubaOS image file to a controller, you must specify the system partition to which the file is copied. The WebUI shows the current content of the system partitions on the controller. You have the option of rebooting the controller with the transferred image file.
In the WebUI
|
1.
|
Navigate to the Maintenance > Controller > Image Management page. |
|
2.
|
Select TFTP, FTP, SCP, or Upload Local File. |
|
3.
|
Enter or select the appropriate values for the file transfer method. |
|
4.
|
Select the system partition to which the image file is copied. |
|
5.
|
Specify whether the controller is to be rebooted after the image file is transferred, and whether the current configuration is saved before the controller is rebooted. |
In the CLI
copy tftp: <tftphost> <filename> system: partition [0|1]}
copy ftp: <ftphost> <user> <filename> system: partition {0|1}
copy scp: <scphost> <username> <filename> system: partition [0|1]
Backing Up and Restoring the Flash File System
You can store the entire content of the flash file system on a controller to a compressed archive file. You can then copy the archive file to an external server for backup purposes. If necessary, you can restore the backup file from the server to the flash file system.
Backup the Flash File System in the WebUI
|
1.
|
Navigate to the Maintenance > File > Backup Flash page. |
|
2.
|
Click Create Backup to back up the contents of the flash system to the flashbackup.tar.gz file. |
|
3.
|
Click Copy Backup to enter the Copy Files page where you can select the destination server for the file. |
Backup the Flash File System in the CLI
backup flash
copy flash: flashbackup.tar.gz tftp: <tftphost> <destfilename>
copy flash: flashbackup.tar.gz scp: <scphost> <username> <destfilename>
Restore the Flash File System in the WebUI
|
1.
|
Navigate to the Maintenance > File > Copy Files page. |
|
a.
|
For Source Selection, specify the server to which the flashbackup.tar.gz file was previously copied. |
|
b.
|
For Destination Selection, select Flash File System. |
|
2.
|
Navigate to the Maintenance > File > Restore Flash page. |
|
3.
|
Click Restore to restore the flashbackup.tar.gz file to the flash file system. |
|
4.
|
Navigate to the Maintenance > Switch > Reboot Switch page. |
|
5.
|
Click Continue to reboot the controller. |
Restore the Flash File System in the CLI
copy tftp: <tftphost> <srcfilename> flash: flashbackup.tar.gz
copy scp: <scphost> <username> <srcfilename> flash: flashbackup.tar.gz
restore flash
Copying Log Files
You can store log files into a compressed archive file which you can then copy to an external TFTP or SCP server. The WebUI allows you to copy the log files to a WinZip folder which you can display or save on your local PC.
In the WebUI
|
1.
|
Navigate to the Maintenance > File > Copy Logs page. |
|
2.
|
For Destination, specify the TFTP or FTP server to which log files are copied. |
|
3.
|
Select Download Logs to download the log files into a WinZip file on your local PC, |
In the CLI
tar logs
copy flash: logs.tar tftp: <tftphost> <destfilename>
copy flash: logs.tar scp: <scphost> <username> <destfilename>
Copying Other Files
The flash file system contains the following configuration files:
|
|
startup-config: Contains the configuration options that are used the next time the controller is rebooted. It contains all options saved by clicking the Save Configuration button in the WebUI or by entering the write memory CLI command. You can copy this file to a different file in the flash file system or to a TFTP server. |
|
|
running-config: Contains the current configuration, including changes which have yet to be saved. You can copy this file to a different file in the flash file system, to the startup-config file, or to a TFTP or FTP server. |
You can copy a file in the flash file system or a configuration file between the controller and an external server.
In the WebUI
|
1.
|
Navigate to the Maintenance > File > Copy Files page. |
|
2.
|
Select the source where the file or image exists. |
|
3.
|
Select the destination to where the file or image is to be copied. |
In the CLI
copy startup-config flash: <filename>
copy startup-config tftp: <tftphost> <filename>
copy running-config flash: <filename>
copy running-config ftp: <ftphost> <user> <password> <filename> [<remote-dir>]
copy running-config startup-config
copy running-config tftp: <tftphost> <filename>