Administrator Guide

NOTE: To display a properly formatted output string, Dell Networking recommends adding the
following clido wrapper function at the beginning of TCLSH and EXPECT scripts:
# Execute clido and return the output string
proc Execclido {cmd_str} {
set str [exec clido "$cmd_str"]
set tmp_str [string map {\n \r\n} $str ]
return $tmp_str
}
...
set out_str [Execclido "show version"]
puts $out_str
...
Auto-Execution Scripts
The autoexecution (autoexec) script is the same as a preconfiguration script except that it executes on
every reboot in Normal mode.
Store scripts in a flash://autoexec file. Autoexec scripts are independent of BMP.
The autoexec script only executes when:
• BMP is disabled.
• The script is stored in a flash://autoexec file.
• Before reloading the system, you use the reload-type normal-reload command in the reload-
type sub command mode.
If the autoexec script fails, the system generates a message indicating the failure and does not load the
configuration file. Before continuing the upgrade, correct the error in the script.
Post-Configuration Scripts
The post configuration script runs once the start-up configuration is applied as script post-config
script-name. In BMP mode, after the pre-configuration script completes and the configuration loads,
you can run a post-configuration script if one is present in the configuration file. In normal reload, if there
is
script post-config script-name config in the startup config file, post-configuration script is
executed.
To check the status of configured ports or protocols, set the host name of the system, or perform
additional configuration settings, use the post-configuration script. The system supports post-
configuration scripts in EXPECT, TCLSH, and ZSH. If you installed the SmartScripts package in your Dell
Networking switches, the system also supports post-configuration scripts in Perl, Python, and Ruby.
Using Preconfiguration Scripts
To preconfigure scripts, follow these steps:
1. Decide what information you want to preconfigure; for example, request username and password
information. Verify the integrity of the boot image the DHCP offer downloads and apply the
configuration types.
2. Create a preconfiguration script in EXPECT, TCL or ZSH.
3. Store the script on any TFTP/FTP/SFTP server that is reachable from the system and mention the URL
file (TFTP/FTP/SFTP) in the DHCP offer.
Bare Metal Provisioning
29