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 that are run following the completion of the boot-up configuration. A URL must be specified or no action is taken. The commands are persistent between router reboots and are included in the configuration saves (admin>save).
Use the following syntax to configure a URL for a CLI script that runs when the boot-up configuration is completed.
config>system
boot-bad-exec file-url
boot-good-exec file-url
The following example shows the command usage to configure a URL for a CLI script that runs when the boot-up configuration is completed.
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*A:ALA# configure system
*A:ALA>config>system# info
----------------------------------------------
#--------------------------------------------------
echo "System Configuration"
#--------------------------------------------------
name "ALA"
boot-good-exec "cf1:\good.cfg"
boot-bad-exec "cf1:\bad.cfg"
snmp
shutdown
exit
login-control
idle-timeout disable
pre-login-message "ala-1" name
exit
time
ntp
authentication-key 1 key "SV3BxZCsIvI" hash type message-digest
server 10.135.16.130
peer 10.0.0.1 key-id 1
no shutdown
exit
sntp
server-address 10.135.16.90 preferred
no shutdown
exit
zone UTC
exit
thresholds
rmon
exit
exit
#--------------------------------------------------
echo "System Security Configuration"
#--------------------------------------------------
security
hash-control read-version all write-version 1
telnet-server
ftp-server
snmp
community "private" rwa version both
community "public" r version both
exit
source-address
application ftp 10.135.16.97
application snmptrap 10.135.16.97
application ping 10.135.16.97
application dns 10.135.16.97
exit
exit
----------------------------------------------
*A:ALA>config>system#