Switch Memory and Configuration

Multiple Configuration Files

For example, the following command copies a startup-config file named test­

01 from the switch to a (UNIX) TFTP server at IP address 10.10.28.14:

ProCurve(config)# copy config test-01 tftp 10.10.28.14 test-01.txt unix

TFTP: Copying a Configuration File from a Remote Host

Syntax: copy tftp config < dest-file> < ip-addr> < remote-file> < pc unix >[oobm]

This is an addition to the copy tftp command options. Use this command to download a configuration file from a TFTP server to the switch.

For switches that have a separate out-of-band management port, the oobm parameter specifies that the TFTP traffic must come in through the out-of-band management interface. If this parameter is not specified, the TFTP traffic comes in through the data interface. The oobm parameter is not available on switches that do not have a separate out-of-band management port. Refer to Appendix I, “Network Out-of-Band Management” in this guide for more information on out-of­ band management.

Note: This command requires an empty memory slot in the switch. If there are no empty memory slots, the CLI displays the following message:

Unable to copy configuration to "< filename >".

You can erase one or more configuration files using the erase config <filename> command.

For more on using TFTP to copy a file from a remote host, refer to “TFTP: Copying a Configuration File from a Remote Host” on page A-31.

For example, the following command copies a startup-config file named test­ 01.txt from a (UNIX) TFTP server at IP address 10.10.28.14 to the first empty memory slot in the switch:

ProCurve(config)# copy tftp config test-01 10.10.28.14 test-01.txt unix

6-39