Concept Guide
Table Of Contents
- Dell EMC Networking Open Automation Guide 9.14.1.0 November 2018
- About this Guide
- Open Automation Framework
- Bare Metal Provisioning
- Introduction
- How it Works
- Prerequisites
- Industry Standard Upgrades with BMP
- BMP Process Overview
- BMP Operations
- Configure BMP
- BMP Commands and Examples
- System Boot and Set-up Behavior in BMP Mode
- BMP Mode - Boot and Set-up Behavior
- DHCP Offer Vendor-Specific Option for BMP
- DHCP Offer Relay Option 82
- Software Upgrade Using BMP
- Apply Configurations Using BMP Scripts
- Using the Post-configuration Script
- Using Auto-Execution Script - Normal Mode Only
- Timers in Pre–configuration and Post–configuration Scripts
- Script Examples
- BMP Operations on Servers Overview
- File Server Settings
- Domain Name Server Settings
- BMP MIB Support
- Bare Metal Provisioning CLI
- Open Management Infrastructure
- Puppet
- Smart Scripting
- Overview
- Download the Smart Scripting Package
- Dell EMC Environment Variables
- Dell EMC Proprietary Utilities
- Dell EMC SmartScript Utilities
- SQLite
- NET SNMP Client
- Limits on System Usage
- Supported UNIX Utilities
- Creating a Username and Password for Smart Scripting
- Logging in to a NetBSD UNIX Shell
- Downloading Scripts to a Switch
- Network File System (NFS)
- Setting a Search Path for Scripts
- Scheduling and Executing Scripts
- Running a Script from the UNIX Shell
- Running Scripts with User Privileges
- Smart Scripting CLI
- disable
- execute
- mount nfs
- package clear-all
- package install
- package uninstall
- script (run)
- script (stop/resume/clear/kill/unschedule)
- script event-handler
- script execute (EXEC mode)
- script execute
- script get
- script path
- script remove
- script trigger-event
- show packages
- show script
- start shell
- triggered-by
- switch script limit
- username (event handler)
- username
- SNMP MIBs
- Virtual Server Networking
- Virtual Server Networking CLI
- REST API
- HTTP and HTTPS
- XML
- Important Points to Remember
- REST Authentication
- Request Query Parameters
- Sample BGP Configurations
- HTTP Status Error Codes
- REST API — Protocol Data Unit (PDU) Structure
- Configurations
- Operational
- Operational Data for IPv6
- Management Information Base (MIB)
- IETF Interface Operations
- REST API Framework to Execute the CLIs
- Samples of the config-command
- Samples of the EXEC command
- Samples of the show-command
- REST API CLI
- Web Server

7 The pre–conguration script can access Dell EMC Networking OS CLI commands through the clido utility. The clido utility has no
pagination, is always set to terminal length 0, and has Dell EMC Networking OS CLI privilege 15 enabled. It works in the
following modes:
• Continuous mode (clido command) — use to retain the Dell EMC 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-conguration Script
To run the post-conguration script, ensure the following:
• You can write the post–conguration script in EXPECT, TCLSH, or ZSH. If you installed the SmartScripts package, you can also write
the post-conguration script in Perl, Python, or Ruby.
• No restraints are required for the post–conguration script; for example, the signature #/DELL-NETWORKING that is required for the
pre–conguration script is not required for the post-conguration script.
• Congure the post–conguration script by using the script post-config command.
• Reload the device (either in BMP mode or Normal reload-type mode).
• Execute the post–conguration script after the start-up conguration process is applied.
• The post-conguration script has the ability to use Dell EMC Networking OS CLI commands using the utility name clido.
• If the script post-config script is present in the startup–cong le, irrespective of the reload-type, upon reload and after the
conguration le is loaded, the post–cong 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-conguration 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
preconguration script is not required for the post-conguration script.
• The autoexecution script can use Dell EMC Networking OS CLIs using the utility name F10do.
• When the autoexecution script completes, the start-up conguration applies depending on the return status of the script:
– Success–0 — the start-up conguration applies.
– Failure–non-zero — the start-up conguration 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 EMC Networking application
00:00:13: %STKUNIT1-M:CP %RAM-6-ELECTION_ROLE: Stack unit 1 is
transitioning to Management unit.
00:00:15: %STKUNIT1-M:CP %CHMGR-5-STACKUNITDETECTED: Stack unit
1 present
00:01:02: %STKUNIT0-M:CP %BMP-5-AUTOEXEC_START: The AutoExec
Script is Started.
• After the script execution is successful, Dell EMC Networking OS log displays:
00:04:05: %STKUNIT0-M:CP %BMP-5-AUTOEXEC_SUCCESS: The AutoExec
Script execution returned Success.
copy startup-config running-config
!
4774 bytes successfully copied
00:04:06: %STKUNIT0-M:CP %SYS-5-CONFIG_LOAD: Loading
configuration file
28
Bare Metal Provisioning