Foundry Networks Switch and Router Installation And Configuration Manual page 155

Using Redundant Management Modules
The command in this example reboots the device using the image file B2R07100.bin located on the PCMCIA flash
card in slot 1. This example assumes the image file is in the root directory on the flash card. If the image file is in
a subdirectory, specify the subdirectory path. For example, to boot using an image in a subdirectory called "B2R",
enter command such as the following:
BigIron# boot system slot1 \B2R\B2R07100.bin
Syntax: boot system slot1 | slot2 [\<dir-path>\]<file-name>
The slot1 | slot2 parameter indicates the flash card slot.
The <file-name> parameter specifies the file name. If the file is in a subdirectory, specify the subdirectory path in
front of the file name. If the file name you specify is not a full path name, the CLI assumes that the name (and
path, if applicable) you enter are relative to the subdirectory that currently has the management focus.
NOTE: This command also is supported at the boot PROM.
Configuring the Flash Card as the Boot Source for Future Reboots
To set a flash card as the primary boot source, enter a command such as the following at the global CONFIG
level of the CLI:
BigIron(config)# boot system slot2 B2R07100.bin
The command in this example sets PCMCIA slot 1 as the primary boot source for the device. When you reload
the software or power cycle the device, the device looks for the flash image file you specify on the flash card in the
slot you specify.
Syntax: boot system slot1 | slot2 <file-name>
NOTE: The command syntax is the same for immediately reloading and for changing the primary boot source,
except the <file-name> must be the full path name. You cannot specify a relative path name. If the first character
in the path name is not a backslash ( \ ), the CLI treats the name you specify as relative to the root directory.
The device's response to the command depends on whether you enter the command at the Privileged EXEC level
or the global CONFIG level.
If you enter multiple boot system commands at the global CONFIG level, the software places them in the running-
config in the order you enter them, and saves them to the startup-config file in the same order when you save the
configuration. When you reload or power cycle the device, the device tries the boot sources in the order they
appear in the startup-config file and running-config.
Displaying the Current Location for Saving Configuration Changes
Enter the following command at the Privileged EXEC level of the CLI to display the current save location for the
startup-config file:
BigIron# locate startup-config
Syntax: locate startup-config
Specifying the Location for Saving Configuration Changes
By default, when you save configuration changes, the changes are saved to the startup-config file on the device's
flash memory module. If you want to change the save location to a PCMCIA slot, enter a command such as the
following:
BigIron# locate startup-config slot1 router1.cfg
BigIron# write memory
The first command in this example sets the device to save configuration changes to the file named "router1.cfg" in
the flash card in PCMCIA slot 1. The second command saves the running-config to the router1.cfg file on the
flash card in slot 1.
December 2000 5 - 31