Copying Configurations Within The Local Memory - Patton electronics SmartNode Series Software Configuration Manual

7 • Configuration file handling SmartWare Software Configuration Guide
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 20.
Figure 20. Local memory regions in SmartWare
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.
You can copy the current running configuration into the persistent memory region nvram: 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 nvram: by
using a user-specified name, for conservation or later activation.
As shown in figure 20 the local memory regions are identified by their unique names, like nvram:, which is
located in flash memory, and system:, which is the system RAM, i.e. the volatile memory. As already men-
tioned, configuration files in the same memory region need a unique name. For example, it is not possible to
have two configuration files with the name running-config in the memory region nvram:.
As you might expect, the copy command does not move but replicates a selected source to a target configura-
tion file in the specified memory region. Therefore the source configuration file is not lost after the copy pro-
cess. There are three predefined configuration file names for which it is optional to specify the memory region,
namely factory-config, startup-config and running-config.
86 Configuration file handling task list