Two post-boot configuration extension files are supported and are triggered when either a successful or failed boot configuration file is processed. The commands specify URLs for the CLI scripts to be run following the completion of the bootup configuration. A URL must be specified or no action is taken. The commands are persistent between router (re)boots and are included in the configuration saves (admin>save).
config>system
— boot-bad-exec file-url
— boot-good-exec file-url
—
config>system# boot-bad-exec ftp://test:test@192.168.xx.xxx/./
— fail.cfg
— config>system# boot-good-exec ftp://test:test@192.168.xx.xxx/./
— ok.cfg
The following example shows the command output:
A:ALA-12>config>system# info
#------------------------------------------
echo "System Configuration"
#------------------------------------------
name "ALA-12"
contact "Fred Information Technology"
location "Bldg.1-floor 2-Room 201"
clli-code "abcdefg1234"
coordinates "N 45 58 23, W 34 56 12"
config-backup 7
boot-good-exec "ftp://test:test@192.168.xx.xxx/./ok.cfg"
boot-bad-exec "ftp://test:test@192.168.xx.xxx/./fail.cfg"
power-supply 1 dc
power-supply 2 dc
lacp-system-priority 1
sync-if-timing
begin
ref-order ref1 ref2 bits
..
----------------------------------------------
A:ALA-12>config>system#