Service Manual
Table Of Contents
- Dell Networking Open Automation Guide December 2015
- About this Guide
- Open Automation Framework
- Bare Metal Provisioning
- Introduction
- How it Works
- Prerequisites
- Industrial 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 Proprietary Utilities
- Dell SmartScript Utilities
- SQLite
- NET SNMP Client
- Limits on System Usage
- Supported UNIX Utilities
- Creating a User Name and Password for Smart Scripting
- Logging in to a NetBSD UNIX Shell
- Downloading Scripts to a Switch
- 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 install
- package uninstall
- script (run)
- script (stop/resume/clear/kill/unschedule)
- script event-handler
- script execute (EXEC mode)
- script execute (CONFIGURATION mode)
- script get
- script path
- script remove
- script trigger-event
- show packages
- show script
- start shell
- triggered-by
- switch script limit
- username (event handler)
- username
- 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 with HTTP Support
Following is a configuration example of a DHCP server included on the most popular Linux distribution.
The dhcpd.conf file shows that the MAC-based IP and configuration file assignment are fixed.
option configfile code 209=text;
option bootfile-name code 67=text;
host HOST1{
#####MAC to IP mapping
hardware ethernet 00:01:e8:8c:4d:0e;
fixed-address 30.0.0.20;
FTP URL with IP address
HTTP URL with DNS
TFTP
#####bootfile-name could be given in the following way
option bootfile-name “ftp://
admin:admin@Guest-1/Dell-SE-8.3.10.1.bin”;
option bootfile-name “http://30.0.0.1/
Dell-SE-8.3.10.1.bin”;
FTP URL with DNS
HTTP URL with IP address
TFTP URL with IP address
MAC-Based IP Address Assignment
To assign a fixed IP address and configuration file based on the system’s MAC address, configure the
DHCP server to deploy in BMP mode.
In this way, the same IP address is assigned and the same configuration file is retrieved when the switch
reloads.
Using a dynamic IP address assignment may cause the desired configuration to not load on the system
because the IP address changes each time the system is reloaded.
For example, on a DHCP3 server, you can configure the assignment of a fixed MAC-based IP address and
configuration file by entering the following lines of configuration parameters in the dhcpd.conf file on
the server:
host S4810 {
hardware ethernet 00:01:e8:81:e2:39;
fixed-address 20.0.0.48;
option configfile "customer.conf";
}
36
Bare Metal Provisioning