Factory configuration
74
IPLink Software Configuration Guide
7 • Configuration file handling
Each configuration file stored in the flash memory needs a unique name. The user has to assign a file name to
any user-specific configuration. IPLink software predefines some names for configuration files. These are the
factory configuration (factory-config), startup configuration (startup-config), and running configuration (run-
ning-config) file names. Refer to appendix A,
“Terms and definitions”
on page 304 to learn more about config-
uration file types.
Factory configuration
Patton IPLink devices are delivered with a factory configuration in the logical region nvram:. This factory con-
figuration initially parameterizes the most useful network and component settings of IPLink software. More-
over, in case of IPLink software malfunction, resetting to the initial state means possibly reloading the factory
configuration. The factory configuration consists of:
•
Default settings for the IP networking subsystem
•
Default settings for the quality of service subsystem
Once a user-specific configuration is created and stored as the startup configuration, the factory configuration
is no longer used, but still remains in the persistent memory. It is possible to switch back to the factory config-
uration at any time during the operation of an IPLink configuration. The getting started guide included with
your IPLink device describes the restoration procedure for restoring the default settings.
Configuration file handling task list
This section describes how to create, load, and maintain configuration files. Configuration files contain a set of
user-configured commands that customize the functionality of your IPLink device to suit your own operating
requirements.
The tasks in this chapter assume that you have at least a minimal configuration running on your system. You
can create a basic configuration file by using the
configure
command; see section
“Modifying the running
configuration at the CLI”
on page 80 for details.
To display, copy, delete, and download or upload configuration files, perform the tasks described in the follow-
ing sections:
•
Copying configurations within the local memory (see
page 75
)
•
Replacing the startup configuration with a configuration from the Flash memory (see
page 76
)
•
Copying configurations to and from a remote storing location (see
page 78
)
•
Replacing the startup configuration with a configuration downloaded from the TFTP server (see
page 79
)
•
Displaying configuration file information (see
page 80
)
•
Modifying the running configuration at the CLI (see
page 80
)
•
Modifying the running configuration offline (see
page 81
)
•
Deleting a specified configuration (see
page 83
)
Avoid downloading any configuration file if you do not com-
pletely understand what you have to do! If a configuration file
download fails or succeeds only partially your IPLink device can-
not start up without a support intervention at the factory.
IMPORTANT