System Image Handling
57
•
Configuration files have to be stored in the logical region
nvram:
of the flash memory. The
factory default configuration is always loaded, and may be restored by pressing the
SmartNode reset button; see the
Hardware Configuration Guide
. The startup, or user-specific
configuration, is also stored in
nvram
.
The factory configuration is read-only, and is contained in the persistent memory in the logical
region
nvram:
of the SmartNode. It can be used if no user-specific configuration is available to start-
up SmartWare with a minimal functionality. This configuration is named “factory-config” in the
SmartWare terminology. A dedicated user-specific configuration has to be created and stored in the
flash memory. This configuration defines the user’s desired system functionality and is used to start-
up the system under normal conditions. This configuration has to be stored as “default-config” in the
logical region
nvram:
of flash memory. Any configuration stored within the persistent memory in the
logical region
nvram:
can be copied to a remote server using TFTP.
Since configurations are not executable from persistent memory, any configuration that is to be used
has to be copied into the volatile memory of the SmartNode prior to operation. This procedure takes
place after the system bootstrap, where the application image (i.e. SmartWare) is started and a
configuration must be available. Shortly before SmartWare is fully started up the configuration
“startup-config” is copied from the logical region
nvram:
of flash memory as the “running-config”
into the volatile memory
system:
of the SmartNode. The volatile memory
system:
is a logical region
within the random access memory (RAM) of the SmartNode.
Changing any settings during operation of a SmartNode alter the running configuration, i.e. that
named “running-config” in the volatile memory
system:
. In order to have such modifications
available after the next system start, the running configuration must to be stored back as “startup-
config” to the persistent memory
nvram:
. Furthermore it is possible to backup the “running-config”
in the volatile memory
system:
with a user-defined name in persistent memory
nvram:
or on a remote
TFTP server.
Software Configuration Guide, Revision 1.03