Loading/saving settings
UM Basic Configuration L3P
Release
7.1
12/2011
3.1
Loading settings
61
3.1.4 Loading from the AutoConfiguration Adapter
Loading a configuration during the boot procedure
If you have connected an ACA to the device, the device automatically
loads its configuration from the ACA during the boot procedure. After the
loading, the device updates its configuration in the local non-volatile
memory with the configuration from the ACA.
Note: During the boot procedure, the configuration on the ACA has
priority over the configuration in the local non-volatile memory.
The chapter “Saving locally (and on the ACA)” on page 64 describes how
you can save a configuration file on an ACA.
Loading a script from the ACA
If the ACA contains a script file, the device automatically loads its
configuration from the script file on the ACA during the boot procedure.
The prerequisites for this are:
The ACA is connected during the boot procedure.
There is no binary configuration in the main directory of the ACA.
The main directory of the ACA contains a file with the name
“autoupdate.txt”.
The file “autoupdate.txt” is a text file and contains a line whose content
has the format script=<file_name>. Here <file_name> stands
for the name of the script file to be loaded, e.g. custom.cli.
The file specified using script=<file_name>, e.g. custom.cli, is
located in the main directory of the ACA and is a valid script file.
If the local non-volatile memory of the device contains a configuration, the
device ignores this.
After applying the script, the device updates the configuration in the local
non-volatile memory with the configuration from the script.
In the process, it also writes the current binary configuration to the ACA.
Note: During the boot procedure, a binary configuration on the ACA has
priority over a script on the ACA.
The chapter “Saving as a script on the PC” on page 68 describes how you
can save a script file on an ACA.
To Next Page
Loading...
Need help?
General
