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
* Server auth using Basic with user 'admin'
> PUT /api/running/dell/interfaces/interface/tengig-1-37 HTTP/1.1
> Authorization: Basic YWRtaW46YWRtaW4=
> User-Agent: curl/7.15.5 (i686-redhat-linux-gnu) libcurl/7.15.5 OpenSSL/0.9.8b
zlib/1.2.3 libidn/0.6.5
> Host: 10.16.151.159:8008
> Accept: */*
> Content-Length: 171
> Expect: 100-continue
>
< HTTP/1.1 100 Continue
< Server: ConfD/5.2
< Allow: GET, POST, OPTIONS, HEAD
< Content-Length: 0
< HTTP/1.1 204 No Content
< Server: ConfD/5.2
< Cache-control: private, no-cache, must-revalidate, proxy-revalidate
< Date: Thu, 04 Dec 2014 13:13:25 GMT
< Allow: GET, POST, OPTIONS, HEAD
< Content-Length: 0
< Content-Type: text/html
< Etag: 1417-698805-339353@0
* Connection #0 to host 10.16.151.159 left intact
* Closing connection #0
Following is the current running configurations applied on the system:
Dell#show running-config interface tengigabitethernet 0/0
!
interface TenGigabitEthernet 0/0
ip address 11.1.1.1/24
shutdown
Dell#
The following configuration retrieves the interface running-config via REST API.
curl -u admin:admin http://10.16.151.159:8008/api/running/dell/interfaces/
interface/tengig-0-0
\?deep
<interface xmlns="http://www.dell.com/ns/dell:0.1/root" xmlns:y="http://tail-
f.com/ns/rest" xmlns:dell="http://www.dell.com/ns/dell:0.1/root">
<name>tengig-0-0</name>
<mtu>1554</mtu>
<shutdown>true</shutdown>
<ip>
<address>
<primary>
<address>11.1.1.1/24</address>
</primary>
</address>
</ip>
<speed>auto</speed>
<rate-interval>299</rate-interval>
</interface>
* Connection #0 to host 10.16.151.159 left intact
* Closing connection #0
The PDU structure for configuring BGP on the Router 1 is as follows:
cat BGP_HTTP_REST_POST_PDU.xml
<bgp>
<as-name>100</as-name>
REST API
141