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 within the local memory in order to switch between different configura-
tions. Remember the different local memory regions in SmartWare as shown in figure 21.
Figure 21. Local memory regions in SmartWare
In the majority of cases, the interactively modified running configuration known as the running-config, which
is to be found in the volatile memory region system:, is copied to the persistent memory region nvram:. This
running config is stored under the name startup-config and replaces the existing startup configuration.
The current running configuration can be copied to the persistent memory region nvram: under a user-speci-
fied name, if that configuration is to be preserved.
In addition, an already existing configuration is usually copied to the persistent memory region nvram: using a
user-specified name, for conservation or later activation.
As shown in figure 21 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 mentioned,
within the same memory region any configuration file needs a unique name so for example it is not possible to
have two configurations 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 files names for which the specification of the memory region is
optional, namely the files factory-config, startup-config and running-config.
82 Configuration file handling task list