Table 23, Using configuration files – B&B Electronics WLNN-AN(ER,SE,SP.EK)-DP551 - Manual User Manual
Page 71

Airborne Enterprise CLI Reference Manual
71
Table 23 - Using Configuration Files
Command
Description
Obtain or create configuration
file
A file is required before the transfer to the module is performed.
This file must be a plain text file containing the parameters
which are to be configured, section XX outlines the file and
command format.
The file may be created in any text editor and does not need to
be called user_config.txt or oem_config.txt; it is
recommended that the file be named in a way that indicates the
installation and revision of the configuration. This name will be
used by the ftp-filename command to identify the file to be
uploaded when suing FTP for the transfer.
Alternately a configuration file can be pulled from an existing
module. Using the web interface it is possible to list the
configuration files available on the module and copy the
contents to a local host. This way supports the use of a pre-
tested golden unit for configuration in large deployments or in a
configuration control system. This method is recommended by
B&B Electronics.
get-cfg [config_filename]
This command uses the configuration settings for the FTP client
and will upload the file identified by ftp-filename to the
module with the name [config_filename].
It is necessary that a valid configuration exist for the FTP client
before this command is used. See section 14.0 for details.
[config_filename]
can be set as:
user_config.txt
oem_config.txt
user_enc_config.uue
It is necessary to issue a save after this command for the
configuration file to be persistent across power cycles or
restarts.
put-cfg [config_filename]
This will use Xmodem to upload the user configuration file to
the module with the name [config_filename].
Once the command has been issued the host connected
through the CLI session will need to start the Xmodem transfer
using Xmodem or Xmodem-1K.to the module.
[config_filename]
can be set as:
user_config.txt
oem_config.txt
user_enc_config.uue
It is necessary to issue a save after this command for the
configuration file to be persistent across power cycles or
restarts.
list-cfg
This will list the installed configuration files on the module.
The command will list files that have been uploaded but have
not yet been saved to the module as well as those saved to the
module.
del-cfg [config_filename]
The command deletes configuration files that are stored on the
module; the command requires a filename argument
[config_filename]
to be supplied.
The save command must be issued after this command to
make the changes persistent across power cycles and restarts.