Table 6-5

Copy Command Descriptions (continued)

argument

 

description

 

 

 

fs

 

HP Fabric Switch file-system. This is an internal directory that is identified by name only.

 

 

The file-systems are config, images, and syslog. The specified file-system must be

 

 

appropriate for the type of file being copied. For example, if an attempt is made to copy a

 

 

configuration file from the syslog file-system, an error is returned because the name of the

 

 

file is not appropriate for the file-system. The file-system specification is always followed by

 

 

a colon (:).

 

 

 

file

 

Name of the configuration, image, or log file to be copied. The file-name convention is:

 

 

configuration files end in “.cfg”, image files begin with “build”, and log files begin with

 

 

“ts_log”. (The .cfg extension is optional.)

 

 

 

 

 

 

NOTE: The copy and show logging commands are the only CLI commands which recognize <Ctrl>-c. You may enter <Ctrl>-cduring the uploading/downloading process to terminate file transfer in the event network transfer hangs.

Examples of copying files to and from the chassis are shown below. The first example shows copying a remote image file onto the chassis. The second example shows copying a local configuration file to a remote FTP server.

HP-IB# copy ftp://anonymous:taj@15.1.162.207/ib/HP-AB291A-Release-1.1.3hp-build023.img image:HP-AB291A-Release-1.1.3hp-build023.img

operation completed successfully HP-IB

HP-IB# copy config:startup-config2 ftp://anonymous:taj@15.1.162.207/startup-config2 operation completed successfully

HP-IB

Downloading Files to the System

To copy a configuration file, use the copy command. For example, to a copy a config file (example: config_021215.cfg) from the home directory of the user anonymous to the config file-system, enter a script such as:

HP-IB# copy ftp://anonymous:taj@15.1.162.207/ib/HP-AB291A-Release-1.1.3hp-build023.img image:HP-AB291A-Release-1.1.3hp-build023.img

operation completed successfully

HP-IB# dir image

=========================================================================

Existing Boot-Images on System

=========================================================================

slot date-createdsize file-name

-------------------------------------------------------------------------

1Mon Nov 17 14:20:09 2003 18911083 HP-AB291A-Release-1.1.3hp-build019.img

1Mon Nov 17 14:20:09 2003 18911083 HP-AB291A-Release-1.1.3hp-build021.img

1Mon Nov 17 14:27:51 2003 13082624 Release-1.1.3hp/build021

HP-IB#

NOTE: You can only download image and configuration files. Log files cannot be downloaded.

Image files require additional processing. Though they have been copied onto the chassis, image files must be installed before they can be used to initialize the system. For information about installing image files, refer to “Upgrading Image Files” (page 85).

Deleting Configuration, Image, and Log Files

The system manages available storage by rotating and compressing logs files. As a new log file is generated, the oldest log file is discarded. Also, the controller limits the user to two uninstalled image files.

This section describes how to proactively manage available space by deleting files.

94 Administration and Management