
Shipping Configuration
66
CopperLink CL2300 User Manual
9
• Configuration File Handling
gatekeeper-discovery auto
bind interface lan router
no shutdown
port ethernet 0 0
medium auto
encapsulation ip
bind interface lan router
no shutdown
port ethernet 0 1
medium 10 half
encapsulation ip
bind interface wan router
no shutdown
Figure 16. Sample configuration file
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. Trinity predefines some names for configuration files. These are the shipping
configuration (
shipping-config
), startup configuration (
startup-config
), minimal configuration (
minimal-config
)
and running configuration (
running-config
) file names.
Shipping Configuration
The CL2300 is delivered with a
shipping configuration
in the logical region
config:.
This shipping configuration
initially parameterizes the most useful network and component settings of Trinity.
Once a user-specific configuration is created and stored as the startup configuration, the shipping configura-
tion is no longer used, but still remains in the persistent memory. It is possible to switch back to the shipping
configuration at any time during the operation of a CL2300 configuration. The
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 CL2300 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
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
)
•
Replacing the startup configuration with a configuration from the Flash memory (see
•
Copying configurations to and from a remote storing location (see
•
Replacing the startup configuration with a configuration downloaded from the TFTP server (see