Configuration handling and software updates
U
SER
G
UIDE
356
located on a system where the TFTP server is active. For example, the file
gprs.cli.txt
containing
the
CLI
commands is located on server
192.168.1.1
:
set gprs apn myapn.tim.it
set gprs login mylogin password mypasswd
set gprs default-route
set gprs on
set loopback ipaddr 10.10.0.1
set loopback on
set eth1 ipaddr 172.15.113.1 netmask 255.255.0.0
set eth1 on
The following commands are executed on Imola
download command-file gprs.cli.txt from 192.168.1.1
run from gprs.cli.txt
The first one transfers the file locally to Imola and the second one executes the commands
contained in it.
Vice versa, in order to upload the current Imola configuration on TFTP server the following
commands can be used:
show config current > /tmp/imola.cli.txt
upload command-file /tmp/imola.cli.txt to 192.168.1.1
the first command creates the file
/tmp/imola.cli.txt
containing the router configuration and
the second one transfers this file to TFTP server.
In order to specify the IP source address which must be used in order to send messages to remote
TFTP server, the following command is used:
set tftp source <local-ip>
or
set tftp source loopback
in order to use the loopback address.
As commands are executed it is also possible to save them in a file and then save them on the TFTP
server:
record in /tmp/myconf.cli.txt
set adsl encap rfc1483-llc
set adsl pvc atm0 ipaddr 83.1.1.1 nexthop 83.1.1.2
set trigger adsl up ip route default dev atm0
no-record
upload command-file /tmp/myconf.cli.txt to 192.168.1.1
S
OFTWARE UPDATING
Imola software is modular. Modules together with their version numbers can be displayed by using
the command:
show system