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
If a pre–conguration script le downloads successfully, the following SYSLOGs display:
00:03:07: %STKUNIT0-M:CP %BMP-2-BMP_DOWNLOAD_START: The config
file download has started.
00:03:19: %STKUNIT0-M:CP %BMP-5-BMP_DWNLD_FILE_IS_SCRIPT_FILE:
The downloaded file is a script file.
00:03:19: %STKUNIT0-M:CP
%BMP-5-BMP_DWNLD_CONFIG_SCRIPT_SUCCESS: The config/script file
download is successful.
00:03:21: %STKUNIT0-M:CP %BMP-5-BMP_PRE_CONFIG_SCRIPT_BEGIN:
The Pre-Config Script has started to Execute.
After the pre–conguration script executes successfully, the startup conguration le loads.
00:04:30: %STKUNIT0-M:CP %BMP-5-BMP_PRE_CONFIG_SCRIPT_END:
Pre-Config script completed with return status 0.
00:03:03: %STKUNIT0-M:CP %IFMGR-5-ASTATE_DN: Changed interface
Admin state to down: Ma 0/0.
00:03:03: %STKUNIT0-M:CP %IFMGR-5-OSTATE_DN: Changed interface
state to down: Ma 0/0.
00:03:03: %STKUNIT0-M:CP %SYS-5-CONFIG_LOAD: Loading
configuration file.
00:03:04: %STKUNIT0-M:CP %IFMGR-5-ASTATE_UP: Changed interface
Admin state to up: Ma 0/0.
If a post–conguration script is present in the applied conguration le, it executes and the logs display:
00:04:22: %STKUNIT0-M:CP %BMP-5-BMP_POST_CONFIG_SCRIPT_BEGIN:
The Post-Config Script has started to Execute
..
00:05:15: %STKUNIT0-M:CP %BMP-5-BMP_POST_CONFIG_SCRIPT_END:
Post-Config script completed with return status 0.
If a post–conguration script is not present in the applied conguration le, the logs display:
00:03:03: %STKUNIT0-M:CP %SYS-5-CONFIG_LOAD: Loading
configuration file.
00:03:04: %STKUNIT0-M:CP %IFMGR-5-ASTATE_UP: Changed interface
Admin state to up: Ma 0/0.
00:03:04: %STKUNIT0-M:CP %BMP-5-BMP_POST_SCRIPT_NOT_PRESENT:
The Post-Config Script is not present.
DHCP Oer Vendor-Specic Option for BMP
To congure FIPS mode for your system, use the vendor-specic DHCP OFFER option (code 231) called fips-mode-enabled so that
BMP can decide to use the non-FIPS-approved algorithms for the image/cong-le download process.
This option accepts the boolean type value TRUE/FALSE to enable or disable FIPS mode. BMP uses this setting temporarily and only for
the image/cong-le download process. BMP never stores this in either the runing-cong or startup-cong. The DHCP OFFER controls
using non-FIPS-approved algorithms by the BMP-initiated le download process. If you have not congured this option, by default BMP
assumes you have disabled FIP mode.
• If the value is set to TRUE, BMP enables FIPS mode and uses the relevant FIPS-approved algorithms for the image/cong-le
download process.
• If the value is set to FALSE, BMP disables FIPS mode and uses the non-FIPS-approved algorithms for the image/cong-le download
process.
DHCP Oer Relay Option 82
Dell EMC Networking OS supports option 82 in DHCP oer. With option 82, the switch appends the interface details while sending the
DHCP discover packet. To support option 82, the congured circuit ID and remote IDs are lled in the DHCP discover packets. The
reload-type command has an option to enable or disable the DHCP oer option 82. By default, the option 82 is disabled. To enable the
option 82, you have to congure the remote ID using the reload-type sub-command relay remote-id "mac/hostname/
custom string
.
Bare Metal Provisioning
25