Installation guide

Brocade NetIron CES 2000 and NetIron CER 2000 Hardware Installation Guide 83
53-1001834-01
Dynamic configuration loading
6
Making local copies of the startup configuration file
You can copy the startup-config file in code flash to a TFTP server or to a PCMCIA flash card
inserted in a NetIron CES and NetIron CER 2000 Series device’s slot 1.
For example, to make a backup copy of the startup-config file and save the backup file to a TFTP
server, enter a command such as the following at the Privileged EXEC level in the CLI.
NetIron# copy startup-config tftp 10.28.40.21 startup-config.bak
Syntax: copy startup-config tftp <ip-address> <dest-file-name>
The <ip-address> variable specifies the IP address of the TFTP server that you want to save the
startup configuration to.
The <dest-file-name> specifies the name of the file you copied to a new destination.
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 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
Consider the following:
• 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 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.
Consider the following while preparing the configuration file:
• 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 command that configures ACL 1, the software rejects ACL 1
in the configuration file, and displays a message that ACL 1 is already configured.