![background image](http://html1.mh-extra.com/html/foundry-networks/fastiron-edge-switch-x424/fastiron-edge-switch-x424_manual_2324269721.webp)
Updating Software Images and Configuration Files
December 2005
© Foundry Networks, Inc.
23 - 9
•
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 a Foundry device’s running-config. You can make configuration changes off-line, then load
the changes directly into the device’s running-config, without reloading the software.
Usage Considerations
•
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) or
to enter trunk group configuration information into the running-config.
•
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’s 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.
Preparing the Configuration File
A configuration file that you create must follow the same syntax rules as the startup-config file the device creates.
•
The configuration file is a script containing CLI configuration commands. The CLI reacts to each command
entered from the file in the same way the CLI reacts to the command if you enter it. For example, if the
command results in an error message or a change to the CLI configuration level, the software responds by
displaying the message or changing the CLI level.
•
The software retains the running-config that is currently on the device, and changes the running-config only
by adding new commands from the configuration file. If the running config already contains a command that
is also in the configuration file you are loading, the CLI rejects the new command as a duplicate and displays
an error message. For example, if the running-config already contains a a command that configures ACL 1,
the software rejects ACL 1 in the configuration file, and displays a message that ACL 1 is already configured.
•
The file can contain global CONFIG commands or configuration commands for interfaces, routing protocols,
and so on. You cannot enter User EXEC or Privileged EXEC commands.
•
The default CLI configuration level in a configuration file is the global CONFIG level. Thus, the first command
in the file must be a global CONFIG command or “ ! ”. The ! (exclamation point) character means “return to
the global CONFIG level”.
NOTE:
You can enter text following “ ! “ as a comment. However, the “ !” is not a comment marker. It returns
the CLI to the global configuration level.
NOTE:
If you copy-and-paste a configuration into a management session, the CLI ignores the “ ! “ instead of
changing the CLI to the global CONFIG level. As a result, you might get different results if you copy-and-
paste a configuration instead of loading the configuration using TFTP.
•
Make sure you enter each command at the correct CLI level. Since some commands have identical forms at
both the global CONFIG level and individual configuration levels, if the CLI’s response to the configuration file
results in the CLI entering a configuration level you did not intend, then you can get unexpected results.
For example, if a trunk group is active on the device, and the configuration file contains a command to disable
Summary of Contents for FastIron Edge Switch X424
Page 36: ...Foundry Configuration Guide for the FESX FSX and FWSX 2 12 Foundry Networks Inc December 2005...
Page 56: ...Foundry Configuration Guide for the FESX FSX and FWSX 3 20 Foundry Networks Inc December 2005...
Page 70: ...Foundry Configuration Guide for the FESX FSX and FWSX 4 14 Foundry Networks Inc December 2005...
Page 198: ...Foundry Configuration Guide for the FESX FSX and FWSX 8 38 Foundry Networks Inc December 2005...
Page 316: ...Foundry Configuration Guide for the FESX FSX and FWSX 12 26 Foundry Networks Inc December 2005...
Page 350: ...Foundry Configuration Guide for the FESX FSX and FWSX 15 12 Foundry Networks Inc December 2005...
Page 458: ...Foundry Configuration Guide for the FESX FSX and FWSX 18 18 Foundry Networks Inc December 2005...
Page 712: ...Foundry Configuration Guide for the FESX FSX and FWSX 22 32 Foundry Networks Inc December 2005...
Page 760: ...Foundry Configuration Guide for the FESX FSX and FWSX A 34 Foundry Networks Inc December 2005...
Page 796: ...Foundry Configuration Guide for the FESX FSX and FWSX C 18 Foundry Networks Inc December 2005...
Page 820: ...Foundry Configuration Guide for the FESX FSX and FWSX E 10 Foundry Networks Inc December 2005...