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

Dell EMC Networking OS supports up to eight hypervisor sessions. A hypervisor session can consist of a single hypervisor unit (ESX, ESXi,
XenServer) or a centralized hypervisor (vCenter, Xenpool). To manage a single VMware hypervisor, use a vSphere client. A vCenter server
is a centralized management server for managing multiple VMware hypervisors.
Figure 2. Virtual Server Networking Example
For any change, VSN subscribes use hypervisor to notify the switch. Depending on the hypervisor mode you congure, the Dell EMC
Networking OS may automatically update its conguration, provide provisioning for conguration changes, or require system administrator
intervention.
Hypervisor Modes
There are two modes for retrieving conguration information from a hypervisor on a virtual server: check and cong.
• Check — VSN retrieves conguration information from a hypervisor and noties the system administrator when there is a change in
the network conguration; for example, when you add or remove a VLAN. A system administrator must make manual updates to the
Dell EMC Networking OS conguration.
• Cong — VSN retrieves conguration information from a hypervisor and automatically makes the required conguration changes in the
Dell EMC Networking OS on the switch.
VSN Persistency
VSN installation and conguration are persistent in the Dell EMC Networking OS conguration and remains after a system reload.
However, the conguration information a hypervisor retrieves is not persistent. If the system reloads, when it boots up, the VSN application
retrieves the network conguration of virtual servers again and recongures the Dell EMC Networking OS accordingly.
Virtual Server Networking
121