Filter
Top Products
146 Brocade BigIron RX Series Hardware Installation Guide
53-1002483-03
Loading and saving configuration files
6
• Running configuration – This active configuration is in the system RAM but not yet saved to
code flash. These changes could represent a short-term requirement or general configuration
change. To display this configuration, enter the show running-config or write terminal
command at any CLI prompt.
Each device can have one startup configuration file and one running configuration. The startup
configuration file is shared by both flash modules. The running configuration resides in DRAM.
Replacing the startup configuration with the running
configuration
After you make configuration changes to the active system, you can save those changes by writing
them to code flash. When you write configuration changes to code flash, you replace the startup
configuration with the running configuration.
To replace the startup configuration with the running configuration, enter the following command
at any Enable or CONFIG command prompt:
BigIron RX# write memory
Replacing the running configuration with the startup
configuration
If you want to back out of the changes you have made to the running configuration and return to
the startup configuration, enter the following command at the Privileged EXEC level of the CLI:
BigIron RX# reload
When the system detects differences between the running and startup configurations, it prompts
you as follows:
Are you sure? (enter ‘y’ or ‘n’):
Enter y, and press the Enter key.
Logging changes to the startup-config file
You can configure a BigIron RX Series to generate a Syslog message when the startup-config file is
changed. The trap is enabled by default.
The following Syslog message is generated when the startup-config file is changed:
startup-config was changed
If the startup-config file was modified by a valid user, the following Syslog message is generated:
startup-config was changed by <username>
To disable or re-enable Syslog messages when the startup-config file is changed, use the following
command at the global CONFIG level of the CLI:
Syntax: [no] logging enable config-changed