Brocade Communications Systems 6650 Copying a configuration file to or from a TFTP server, Dynamic configuration loading

Brocade ICX 6650 Administration Guide 59

53-1002600-01

Loading and saving configuration files 3

Copying a configuration file to or from a TFTP server

To copy the startup-config or running-config file to or from a TFTP server, use one of the following

methods.

NOTE

For details about the copy and ncopy commands used with IPv6, refer to “Using the IPv6 copy

command” on page 62 and “IPv6 ncopy command” on page 64.

NOTE

You can name the configuration file when you copy it to a TFTP server. However, when you copy a

configuration file from the server to a Brocade device, the file is always copied as “startup-config”

or “running-config”, depending on which type of file you saved to the server.

To initiate transfers of configuration files to or from a TFTP server using the CLI, enter one of the

following commands:

•copy startup-config tftp <tftp-ip-addr> <filename> – Use this command to upload a copy of the

startup configuration file from the Layer 2 Switch or Layer 3 Switch to a TFTP server.

•copy running-config tftp <tftp-ip-addr> <filename> – Use this command to upload a copy of

the running configuration file from the Layer 2 Switch or Layer 3 Switch to a TFTP server.

•copy tftp startup-config <tftp-ip-addr> <filename> – Use this command to download a copy of

the startup configuration file from a TFTP server to a Layer 2 Switch or Layer 3 Switch.

Dynamic configuration loading

You can load dynamic configuration commands (commands that do not require a reload to take

effect) from a file on a TFTP server into the running-config on the Brocade device. You can make

configuration changes off-line, then load the changes directly into the device running-config,

without reloading the software.

•Use this feature only to load configuration information that does not require a software reload

to take effect. For example, you cannot use this feature to change statically configured

memory (system-max command).

•Do not use this feature if you have deleted a trunk group but have not yet placed the changes

into effect by saving the configuration and then reloading. When you delete a trunk group, the

command to configure the trunk group is removed from the device running-config, but the

trunk group remains active. To finish deleting a trunk group, save the configuration (to the

startup-config file), then reload the software. After you reload the software, then you can load

the configuration from the file.

•Do not load port configuration information for secondary ports in a trunk group. Since all ports

in a trunk group use the port configuration settings of the primary port in the group, the

software cannot implement the changes to the secondary port.

A configuration file that you create must follow the same syntax rules as the startup-config file the

device creates.