![background image](http://html1.mh-extra.com/html/patton-electronics/smartware-r-3-20/smartware-r-3-20_software-configuration-manual_4044387073.webp)
Configuration file handling task list
73
SmartWare Software Configuration Guide
6 • Configuration file handling
•
Copying configurations within the local memory (see
page 73
)
•
Replacing the startup configuration with a configuration from the Flash memory (see
page 74
)
•
Copying configurations to and from a remote storing location (see
page 75
)
•
Replacing the startup configuration with a configuration downloaded from the TFTP server (see
page 76
)
•
Displaying configuration file information (see
page 76
)
•
Modifying the running configuration at the CLI (see
page 77
)
•
Modifying the running configuration offline (see
page 78
)
•
Deleting a specified configuration (see
page 79
)
•
Downloading encrypted files (see
page 80
)
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 SmartWare as shown in
figure 11
.
Figure 11. 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 nvram:. This running config
is stored under the name startup-config and replaces the existing startup configuration.
Volatile
Persistent
nvram:
• Factory
Configuration
“factory-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
Only on Startup to execute
the Startup or Factory
Configuration
Copy Configuration Files within
the persistent Memory Region