User guide

Saving Configuration Changes
ExtremeWare 7.2e Installation and User Guide 315
Software Signatures
Each ExtremeWare image contains a unique signature. The BootROM checks for signature compatibility
and denies an incompatible software upgrade. In addition, the software checks both the installed
BootROM and software and also denies an incompatible upgrade.
Rebooting the Switch
To reboot the switch, use the following command:
reboot {time <date> <time> | cancel}
where date is the date and time is the time (using a 24-hour clock format) when the switch will be
rebooted. The values use the following format:
mm/dd/yyyy hh:mm:ss
If you do not specify a reboot time, the reboot occurs immediately following the command, and any
previously schedule reboots are cancelled. To cancel a previously scheduled reboot, use the
cancel
option.
Saving Configuration Changes
The configuration is the customized set of parameters that you have selected to run on the switch. As
you make configuration changes, the new settings are stored in run-time memory. Settings that are
stored in run-time memory are not retained by the switch when the switch is rebooted. To retain the
settings, and have them load when you reboot the switch, you must save the configuration to
nonvolatile storage.
The switch can store two different configurations: a primary and a secondary. When you save
configuration changes, you can select to which configuration you want the changes saved. If you do not
specify, the changes are saved to the configuration area currently in use.
To save the configuration, use the following command:
save configuration {primary | secondary}
To use the configuration, use the following command:
use configuration [primary | secondary]
The configuration takes effect on the next reboot.
Beta Version 7.0.1 (Build 3) beta1.triumph-r4 7.0.1b3 beta1.triumph-r4
Development
Branch
Version 7.0.0 (Build 67) branch.triumph-r5 7.0.0b67 branch.triumph-r5
Table 43: Sample show output
Release Type Show Version Command Show Switch Command