Copying Configurations To And From A Remote Storage Location - Patton electronics SmartNode Series Software Configuration Manual

SmartWare Software Configuration Guide 7 • Configuration file handling
Copying configurations to and from a remote storage location
Configuration files can be copied from local memory (persistent or volatile region) to a remote data store.
Remember the different store locations; they are the local memory in your SmartNode and the remote data store
on a server system (see figure 21). A remote storage location is mostly used to store ready configurations for later
download to a certain SmartNode. A TFTP server has to be used as a remote data store. From within SmartWare,
this remote TFTP server is represented by the memory region tftp: in combination with the IP address of the
TFTP server and the name and path of the configuration file. We will explain the usage of the remote memory
region tftp: in the following section more detailed. Another typical task is uploading the current running configu-
ration to the remote data store for backup purpose, or if an extensive configuration file is to be edited on the
remote host. In this case the running configuration, named running-config, which is to be found in the volatile
memory region system: is transferred to the TFTP server. On the TFTP server the running configuration is stored
to a file whose name is defined as one of the arguments of the copy command.
Figure 21. Remote memory regions for SmartWare
Finally, configuration files, i.e. the startup configuration or a user-specific configuration that is stored in the
persistent memory region nvram: are often uploaded to the remote data store for backup, edit or cloning pur-
poses. The latter procedure is very helpful when you have several SmartNode devices, each using a configura-
tion which does not greatly differ from the others, or which is the same for all devices. During the
configuration of the first SmartNode according to your requirements, the running configuration of this device,
named running-config and located in the volatile memory region system:, is edited. Next, the configuration is
tested and if everything is as required, the running configuration is copied as startup configuration, named star-
tup-config, into the persistent memory region nvram: of the target device. After this, the startup configuration is
Configuration file handling task list 89