BelAir100SN User Guide
System Settings
May 31, 2010
Confidential
Document Number BDTM11001-A01 Released
Example
/system# show restart-reason
Previous reboot was a cold restart initiated by user.
Creating and
Using Script Files
You can use script files to:
• make repetitive tasks quicker and easier to do
• automate the configuration of a node when it starts up. See
Auto-configuration” on page 63
.
The BelAir100SN provides several CLI commands to manage script files.
Script Creation
Guidelines
Use the following guidelines to create a script file:
• Make sure the script contains only valid and supported BelAir CLI
commands. If you are using an older script, make sure the CLI commands
that it contains are still valid and supported.
• Some BelAir node functions, such as Network Address Translation (NAT),
require that you reboot the node after you configure them. If your script is
for BelAir100SN auto-configuration at startup and if it must include the
reboot
command, then your script must include special declarations. For
details, see
“Guidelines for Using the reboot Command in a Script” on
.
Caution!
Using the
reboot
command in an auto-configuration script without the correct
declarations may cause the node to enter a continuous
reboot
loop.
• Test the final script to ensure all commands are valid, syntactically correct
and appropriate for the installed hardware.
Put the final script on a TFTP, FTP or FTPS server to transfer the script file to
the BelAir unit.
Specifying a Physical
Interface in Script
Script files can use the following method to ensure commands are applied to
the correct physical interface:
1 Begin the command sequence by specifying the physical interface with the
following declaration:
int[-<asbly>]-<iftype>[-<desc>]-<instance>
<asbly> specifies the node’s assembly code. This part of the declaration is
optional. If provided, it must match at least part of the text in the
Assembly