User`s guide

Introduction 137
Common Features of Administrative User’s Windows
Trying, Saving, and Restoring Configuration
Changes
The various options for trying, saving, and restoring configuration changes
are summarized in the following table. Trying, saving, and restoring can be
done in the OSD and on the Linux command line. The “Action” column
shows the Web Manager actions.
The unsaved changes button appears on the lower right hand
corner of the Web Manager and a red graphical LED blinks
whenever the current user has made any changes and has not
yet saved the changes.
The no unsaved changes button appears and a green graphical
LED appears when no changes have been made that need to be
saved.
Table 3-5: Options for Trying, Saving, and Restoring Configuration Changes
Option Action Result
Make changes Enter information in any
of the screens and click
the OK or Done button
The “unsaved changes button” appears and a
red graphical LED blinks. Changes are held
in memory and not saved.
Try changes Click the “try changes”
button”
Updates (saves the changes in) the
appropriate configuration files. Changes are
preserved if you log in and log out again and
even if you restart the system. The changes
are not backed up unless “apply changes” is
clicked. You can restore the backed-up
configuration files by clicking “cancel
changes.”
Cancel
changes
Click the “cancel
changes” button
Restores the configuration files using the
backup file that was created the last time
changes were applied.
Table 3-4: Administrator’s Control Buttons (Continued)
Button Name Use