Replacing The Startup Configuration With A Configuration From Flash Memory - Patton electronics SmartNode Series Software Configuration Manual

SmartWare Software Configuration Guide
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 11 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
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.
Mode: Administrator execution
Step
node #copy {factory-config | startup-
1
config | running-config | nvram: source-
name } nvram: target-name
Example: Backing up the startup configuration
The following example shows how to make a backup copy of the startup configuration. It is copied under the
name backup into the flash memory region nvram:.
node#copy startup-config nvram:backup
Replacing the startup configuration with a configuration from Flash memory
It is possible to replace the startup configuration by a configuration that is already present in the flash memory.
You can do so by copying it to the area of the flash memory where the startup configuration is stored.
Mode: Administrator execution
Step
node # copy nvram: backup startup-config
1
Note
The configuration backup can be a previously backed up configuration or
previously downloaded from a TFTP server.
Configuration file handling task list
copy command does not move but replicates a selected source to a target configura-
Command
Command
6 • Configuration file handling
Purpose
Copies the selected source configuration file
source-name as target configuration file target-
name into the local memory.
Replaces the existing persistent startup con-
figuration with the startup configuration
backup already present in flash memory.
Purpose
75