User Guide

OmniAccess SafeGuard OS Administration Guide
110
Chapter 3: Working with Configuration Files and Upgrading Images
This chapter describes the tasks associated with the configuration files and how to
upgrade system software.
Understanding Configuration Files
The SafeGuard OS maintains two basic configuration files that manage the device: the
startup configuration and the running configuration.
■ The startup configuration is used when the device is started or rebooted.
■ The running configuration is the current operating configuration.
While the two configurations can be the same, the running configuration and the startup
configuration can also be different. A third kind of configuration file, a backup
configuration, can also be created. This file may be a backup of an existing running
configuration, or a starting configuration.
See the following sections for more details:
■ Saving Changes to the Running Configuration
■ Saving Changes to the Startup Configuration
■ Moving Backup Files to External Storage
■ Restoring Configuration Files
■ Erasing the Startup Configuration
■ Displaying Configuration Information
Saving Changes to the Running Configuration
After making changes to the running configuration, save the changes to the startup
configuration to make sure that the changes persist across system reloads. In addition to
saving the running configuration as the startup file, it is recommended to store the file to
external storage (for example, Compact Flash (CF) or to a Trivial File Transfer Protocol
(TFTP) server).
From Running to the Startup
If the startup file is overwritten with the running configuration, the system uses the
updated file on the next reboot.
There are two separate Privileged Exec commands that can be used to save the running
configuration as the startup configuration: write memory or copy system:running-
config.
■ write memory has no parameters or variables.