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
Virtual Server Networking
Virtual server networking (VSN) is supported on the S4810, S4820T, S5000, and MXL switch platforms.
As a part of the Open Automation package, VSN provides real-time communication between the Dell EMC Network fabric and the virtual
servers to automate network management and conguration tasks throughout the data center. VSN provides a closed-loop provisioning
system; for example, the automatic reprovisioning of virtual local area networks (VLANs) and port proles across multiple switches
simultaneously, thereby increasing employee productivity and minimizing human error.
Because Open Automation supports hypervisors from multiple vendors, data center managers can use a single mechanism to
simultaneously support multiple hypervisors and their current management tools.
VSN installs as a self-contained package and requires the Smart Scripting package.
NOTE: VSN is supported only on standalone switches and VMware virtual distributed switches (VDS); it is not supported in
stacked congurations.
Topics:
• Overview
• Install VSN
• Installing VSN
• Enabling VSN in a Hypervisor Session
• Changing VSN Settings
• Discovery
• Connectivity
• Running VSN Scripts
• Disabling a Hypervisor Session
• Removing a Hypervisor Session
• Uninstalling VSN
• Viewing VSN Information
Overview
Virtual server networking is an Open Automation tool that enables Dell EMC Networking switches and routers in a data center network to
retrieve conguration information from hypervisors. VMware vSphere and Citrix Xen hypervisors are supported.
Both VMware and Citrix Xen provide software development kits (SDKs) and application programming interfaces (APIs) for accessing their
conguration objects. VSN requires Layer 3 connectivity to access a hypervisor.
The following shows an example of the network architecture in which a Dell EMC Networking OS switch connects to multiple servers, each
of which may run a dierent type of hypervisor. The vCenter hypervisor from VMware is a centralized server management system that
manages multiple vSphere operating systems on which multiple virtual machines (VMs) run. The VMware ESX server is a single unit, that
can be managed by the hypervisor or act as an independent unit. The Citrix Xen hypervisor uses a distributed management methodology
under which a number of XenServers is grouped in a management domain, with a master server managing the other units in the domain.
Minimal packet drops may be seen when migrating VMS from one server to another. The drops may vary from one second or higher,
depending on the load on the server and network.
10
120 Virtual Server Networking