Configuration file handling task list
78
IPLink 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 IPLink and the remote data store on a
server system (see
figure 13
). A remote storage location is mostly used to store ready configurations for later
download to a certain IPLink. A TFTP server has to be used as a remote data store. From within IPLink software,
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 13. Remote memory regions for IPLink software
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 IPLink devices, each using a configuration
which does not greatly differ from the others, or which is the same for all devices. During the configuration of
the first IPLink according to your requirements, the running configuration of this device, named running-con-
fig and located in the volatile memory region system:, is edited. Next, the configuration is tested and if every-
thing is as required, the running configuration is copied as startup configuration, named startup-config, into the
persistent memory region nvram: of the target device. After this, the startup configuration is transferred to the
Volatile
Persistent
nvram:
• Factory
Configuration
“factory-config”
(read-only)
• Startup
Configuration
“startup-config”
• User specific
Configuration
“user-config”
system:
• current Running
Configuration
“running-config”
Remote Memory
Regions
Store the current Running
Configuration remotely
Local
(Intelligent Access Device)
Configuration File Download
tftp:
• Configuration Files
• Batchfiles for
System Image
download
Remote
(TFTP Server)
Configuration File Upload