Command Line Interface (CLI) |
| |
CLI Batch File |
| |
|
| |
set ipaddr 11.0.0.66 |
| |
set ipaddrtype static |
| |
set ipsubmask 255.255.255.0 |
| |
set ipgw 11.0.0.1 |
| |
set wif 4 | autochannel disable |
|
set wif 4 | mode 1 |
|
set syslogstatus enable |
| |
set sysloghbstatus enable |
| |
set sysloghbinterval 5 |
| |
set wif 4 | netname london |
|
reboot |
|
|
Figure A-18 Sample CLI Batch File
Reboot Behavior
When a CLI Batch file contains a reboot command, the reboot will occur only after the entire CLI Batch file has been executed.
There are two methods of uploading the CLI Batch File:
•Upload
•Upload and reboot (this option is to be used for a CLI Batch file containing the configuration parameters that require a reboot)
CLI Batch File Error Log
If there is any error during the execution of the CLI Batch file, the AP will stop executing the file. The AP generates traps for all errors and each trap contains the following information:
•Start of execution
•Original filename of the uploaded file
•End of execution (along with the status of execution)
•Line number and description of failures that occurred during execution
The AP logs all the errors during execution and stores them in the Flash memory in a CLI Batch File Error Log named “CBFERR.LOG”. The CLI Batch File Error Log can be downloaded though TFTP, HTTP, or CLI file transfer to a specified host.