6 Dynamic configuration loading
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 BigIron RX Series switch’s
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
•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
•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
•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
The CLI changes to the global CONFIG level if you instead of the
load the configuration as a
148 | Brocade BigIron RX Series Hardware Installation Guide |
|