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
<dellNetBgpM2NlriCalcLocalPref>100</dellNetBgpM2NlriCalcLocalPref>
<dellNetBgpM2PathAttrIndex>1860238788</dellNetBgpM2PathAttrIndex
<dellNetBgpM2NlriOpaqueType>none</dellNetBgpM2NlriOpaqueType>
<dellNetBgpM2RouteFlag>active</dellNetBgpM2RouteFlag>
</dellNetBgpM2NlriTable>
</collection>
* Connection #0 to host 10.16.151.159 left intact
* Closing connection #0
HTTP Status Error Codes
The REST API server returns the following HTTP status error codes.
Status Error
Codes
Description
200 OK The request was successfully completed. A response body returns containing a
representation of the resource.
201 Created A resource is created and the new resource URI returns in the “Location” header.
204 No Content The request is successfully completed but no response body returns.
400 Bad Request The request could not be processed because it contains missing or invalid
information (such as a validation error on an input field, a missing required value,
and so on).
401 Unauthorized The request requires user authentication. The response includes a “WWW-
Authenticate” header field for basic authentication.
403 Forbidden Access to the resource is denied by the server due to authorization rules.
404 Not Found The requested resource does not exist.
405 Method Not
Allowed
The HTTP method specified in the request (DELETE, GET, HEAD, PATCH, POST,
PUT) is not supported for this resource.
406 Not
Acceptable
The resource this request identifies is not capable of generating the requested
representation, specified in the “Accept” header or in the “format” query parameter.
409 Conflict This code is used if a request tries to create a resource that already exists.
415 Unsupported
Media Type
The format of the request is not supported.
500 Internal Error The server encountered an unexpected condition which prevented it from fulfilling
the request.
501 Not
Implemented
The server does not (currently) support the functionality required to fulfill the
request.
503 Unavailable The server is currently unable to handle the request because the resource is being
used by someone else or is temporarily overloaded.
REST API — Protocol Data Unit (PDU) Structure
The following features are supported to configure the REST API.
• Physical interface
REST API
145