Service Manual

5. The system receives an IP address via the DHCP server which it uses to get a Dell Networking OS
image to boot, a configuration file (if supplied), and a pre–configuration script.
6. The system runs the pre–configuration script.
The default timer on the script is 10 minutes. The maximum amount of time the script can run is
one hour.
7. The pre–configuration script can access Dell Networking OS CLI commands through the clido
utility. The clido utility has no pagination, is always set to terminal length 0, and has Dell
Networking OS CLI privilege 15 enabled. It works in the following modes:
Continuous mode (clido command) — use to retain the Dell Networking OS context.
Reset mode (clido -r command) — use to reset the CLI command to its original context.
8. To execute CLI commands during boot time, the system uses the clido utility.
Using the Post-configuration Script
To run the post-configuration script, ensure the following:
You can write the post–configuration script in EXPECT, TCLSH, or ZSH. If you installed the
SmartScripts package, you can also write the post-configuration script in Perl, Python, or Ruby.
No restraints are required for the post–configuration script; for example, the signature #/DELL-
NETWORKING that is required for the pre–configuration script is not required for the post-
configuration script.
Configure the post–configuration script by using the script post-config command.
Reload the device (either in BMP mode or Normal reload-type mode).
Execute the post–configuration script after the start-up configuration process is applied.
The post-configuration script has the ability to use Dell Networking OS CLI commands using the
utility name clido.
If the script post-config script is present in the startup–config file, irrespective of the reload-
type, upon reload and after the configuration file is loaded, the post–config runs.
Using Auto-Execution Script (Normal Mode Only)
To use the autoexec script, the following conditions must be true:
BMP is disabled.
The autoexecution script is stored in flash://autoexec.
You can write the autoexecution script in EXPECT, TCLSH, or ZSH. If you installed the SmartScripts
package, you can also write the post-configuration script in Perl, Python or Ruby.
No restraints are required for the autoexec script; for example, the signature #/ DELL-NETWORKING
that is required for the preconfiguration script is not required for the post-configuration script.
The autoexecution script can use Dell Networking OS CLIs using the utility name F10do.
When the autoexecution script completes, the start-up configuration applies depending on the return
status of the script:
Success–0 — the start-up configuration applies.
Failure–non-zero — the start-up configuration does not apply.
If you reboot the system with the reload-type set as normal-reload and an autoexec script is
present in the Flash directory, the following log displays:
Starting Dell Networking application
00:00:13: %STKUNIT1-M:CP %RAM-6-ELECTION_ROLE: Stack unit 1 is
transitioning to Management unit.
Bare Metal Provisioning
29