Patton CopperLink CL2300, User Manual, Page: 67 / 116

Configuration File Handling Task List 67
CopperLink CL2300 User Manual 9 • Configuration File Handling
• Displaying configuration file information (see page 70 )
• Modifying the running configuration at the CLI (see page 71 )
• Modifying the running configuration offline (see page 72 )
• Deleting a specified configuration (see page 73 )
Copying Configurations Within the Local Memory
Configuration files may be copied into the local memory in order to switch between different configurations.
Remember the different local memory regions in Trinity as shown in
figure 17 .
Volatile Persistent
config:
¥Shipping
Configuration
Òshipping-configÓ
(read-only)
¥Startup
Configuration
Òstartup-configÓ
¥ User specific
Configuration
Òuser-configÓ
system:
¥current Running
Configuration
Òrunning-configÓ
Local Memory Regions
Store the current Running
Configuration persistently
Local
(Intelligent Access Device)
Only on Startup to execute
the Startup or Shipping
Configuration
Copy Configuration Files within
the persistent Memory Region
Figure 17. Local memory regions
In most cases, the interactively modified running configuration known as the
running-config
, which is located
in the volatile memory region system: , is copied into the persistent memory region config . This running config is
stored under the name
startup-config
and replaces the existing startup configuration.
You can copy the current running configuration into the persistent memory region
config
: under a user-speci-
fied name, if you want to preserve that configuration.
In addition, an already existing configuration is usually copied into the persistent memory region config: by
using a user-specified name, for conservation or later activation.
As shown in figure 17 the local memory regions are identified by their unique names, like
config:,
which is
located in flash memory, and system :, which is the system RAM, i.e. the volatile memory. As already mentioned,