Dell Networking Open Automation Guide May 2015 Regulatory Model: Open Automation
Notes, cautions, and warnings NOTE: A NOTE indicates important information that helps you make better use of your computer. CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid the problem. WARNING: A WARNING indicates a potential for property damage, personal injury, or death. Copyright © 2015 Dell Inc. All rights reserved. This product is protected by U.S. and international copyright and intellectual property laws.
Contents 1 About this Guide....................................................................................................9 Audience................................................................................................................................................ 9 Supported Platforms and Required Dell Networking OS Versions..................................................... 9 Conventions.....................................................................................................
Using Preconfiguration Scripts..................................................................................................... 29 Using the Post-Configuration Script..................................................................................................30 Using Auto-Execution Script (Normal Mode Only)........................................................................... 30 Timers in Pre–configuration and Post–configuration Scripts..........................................................
6 Puppet.................................................................................................................. 69 Overview..............................................................................................................................................69 Installing Puppet..................................................................................................................................69 Prerequisites......................................................................
Viewing Script Information........................................................................................................... 90 Running a Script from the UNIX Shell................................................................................................ 90 Running Scripts with User Privileges.................................................................................................. 91 8 Smart Scripting CLI...............................................................................
Viewing VSN Information..................................................................................................................125 10 Virtual Server Networking CLI..................................................................... 127 access.................................................................................................................................................127 disable......................................................................................................
IP Interface................................................................................................................................... 172 Management – Route................................................................................................................. 173 MAC Address Table......................................................................................................................173 Policy Based Routing (PBR)...............................................................
About this Guide 1 This document describes the components and uses of the Open Automation Framework designed to run on the Dell Networking operating system (OS).
Dell Networking Platform Minimum Operating Software S6000 9.0.2.0 or later S6000-ON 9.7(0.0) or later MXL 9.2(0.0) or later Z9500 9.5(0.1) or later (BMP, SmartScripts, and REST API only) Conventions To describe command syntax, this document uses the following conventions. Convention Description keyword Keywords are shown in a terminal font and are entered in the CLI as listed. parameter Parameters are shown in italics and require you enter a number or word in the CLI.
Dell Networking Platform Z9000 S6000 S6000-ON MXL Switch Z9500 Dell Networking platform and OS About this Guide Related Documents • Dell Networking OS Command Line Reference guide for the Z9000 System • Dell Networking OS Configuration Guide for the Z9000 System • Installing the Z9000 System • Dell Networking OS Command Line Reference guide for the S6000 System • Dell Networking OS Configuration Guide for the S6000 System • Installing the S6000 System • Dell Networking OS Command Line R
2 Open Automation Framework The Dell Networking S4810, S4820T, S5000, S6000, S6000-ON, Z9000, Z9500, and MXL platforms support the Open Automation framework. The Open Automation framework provides an open, industry standards-based automation technology that simplifies managing dynamic virtual data centers and reduces risk and overhead.
Figure 1. Open Automation Framework NOTE: The Open Automation framework is referred to as Open Automation in the rest of this document. Bare Metal Provisioning Bare metal provisioning (BMP) provides the following features.
network administrators can implement version control systems, automatically generate alerts, create custom logging tools, and automate management of network devices. Any function that you can perform through the Dell Networking OS command line interface (CLI), you can perform with smart scripting. The scripting environment (Expect, Perl, Python, Ruby, Tcl, UNIX and ZSH shell scripts) makes it easy for IT administrators to quickly develop scripts.
The programmatic management environment and set of interfaces communicate directly with the thirdparty system management tools, avoiding the need for a dedicated network management tool. As a result, the network management is simplified and the number of management tools are minimized. Web Server with HTTP Support Open Automation supports web connectivity through its web server with HTTP support. The web server consists of both HTTP and HTTPS daemons running on a switch.
3 Bare Metal Provisioning Bare metal provisioning (BMP) is included as part of the Dell Networking OS image and is supported on the S4810, S4820T, S5000, S6000, S6000-ON, Z9000, Z9500, IOA, and MXL platforms. Introduction BMP improves operational efficiency to your system by automatically loading pre-defined configurations and Dell Networking OS images using standard protocols such as dynamic host configuration protocol (DHCP) and common file transfer mechanisms.
Prerequisites Before you use BMP to auto-configure your Dell Networking switch, configure the following: • External DHCP server (required) — a network device offering configuration parameters. • File server (required) — a network device for storing and servicing files. • Domain name server (DNS) (optional) — a server that associates domain names in the network with IP addresses.
BMP Process Overview When your system boots up in default BMP mode, the following items are requested. 1. The current (new) Dell Networking OS build image. 2. The configuration file or preconfiguration script (EXPECT, TCL, or Z-shell [ZSH] script). 3. A list of checksums for all these components. NOTE: If you already installed the SmartScripts package, the preconfiguration scripts can be in Perl, Python or Ruby.
Configure BMP BMP supports two types of Reload modes: BMP mode and Normal mode. Reload Modes This section describes the following Reload modes: • BMP Mode • Normal Mode BMP mode is the default boot mode configured for a new system arriving from the Dell factory. This mode obtains the Dell Networking OS image and configuration file from a network source (DHCP and file servers). To boot up the switch with the management port in No Shutdown mode, use Normal mode.
Press L to toggle BMP syslog and console messages. Press S to display the BMP status. [A/C/L/S]: NOTE: In the Factory-Default context, the console only accepts A/C/L/S input. • Enter S to display the BMP status (show boot bmp). If you enter another key while BMP is running, it displays the previous message and repeats the process. • Enter A to stop BMP.
• DHCP Configuration — Normal mode does not require a separate DHCP server configuration. • Dell Networking OS Image Retrieval — The Dell Networking OS image is loaded from the local flash memory. BMP Commands and Examples You can configure BMP on supported switches using a series of commands. To enable BMP mode on your switches, and to apply configurations or run scripts using the BMP commands, refer the Bare Metal Provisioning CLI section.
a. If you use the optional bootfile-name command, the filename can be 256 bytes. If you specify the filename field in the DHCP offer, the filename can be 128 bytes. The name can be a fully qualified URL or a filename only. b. When a Dell Networking OS build image is found, the system compares that build image to the version currently loaded on the chassis. • If there is a mismatch between the build images, the system upgrades to the downloaded version and reloads.
a. b. When you disable FCoE initialization protocol (FIPs) mode: • If both filename.sha256 and filename.md5 are not present, the image is downloaded without validation. • If both filename.sha256 and filename.md5 are present, SHA256 validation has a higher priority compared with MD5 validation. • If filename.sha256 or filename.md5 alone is present, the corresponding type of validation is completed. When you enable FIPs mode: • MD5 validation is not used. BMP checks only for the filename.
00:03:55: %STKUNIT0-M:CP sent on Te 0/8. 00:03:41: %STKUNIT0-M:CP sent on Ma 0/0. 00:03:40: %STKUNIT0-M:CP sent on Te 0/21. 00:03:40: %STKUNIT0-M:CP sent on Te 0/8. 00:03:25: %STKUNIT0-M:CP sent on Ma 0/0. 00:03:25: %STKUNIT0-M:CP sent on Te 0/21. 00:03:25: %STKUNIT0-M:CP sent on Te 0/8.
00:01:25: %STKUNIT0-M:CP %SYS-5-CONFIG_LOAD: Loading configuration file Reload with a DHCP Server Offer and no Configuration File A switch is configured to reload in BMP mode. If the switch reaches a DHCP server but cannot retrieve a configuration file, the switch looks for a configuration file on the file server if you enabledconfig-scrdownload. 1. The system boots up with the BMP application. 2.
Reload with a DHCP Server Offer Without a DNS Server Reload the Dell Networking OS on a switch using a preconfiguration script. To reload the Dell Networking OS on a switch using a preconfiguration script, the following must be true: • BMP is enabled. • The download of the script is from an external server and the location is specified in the DHCP offer.
If a post configuration script is not present in the applied configuration file, the logs display: 00:03:03: %STKUNIT0-M:CP %SYS-5-CONFIG_LOAD: Loading configuration file. 00:03:04: %STKUNIT0-M:CP %IFMGR-5-ASTATE_UP: Changed interface Admin state to up: Ma 0/0. 00:03:04: %STKUNIT0-M:CP %BMP-5-BMP_POST_SCRIPT_NOT_PRESENT: The Post-Config Script is not present.
Configure Auto-Configuration mode using the reload-type bmp command. Reload the switch in Configuration mode using the reload command. Apply Configurations Using BMP Scripts With Dell Networking OS version 9.1(0.0) or later, Open Automation supports a scripting environment when a BMP or Normal reload occurs. BMP uses pre-configuration scripts, while a Normal reload-type uses an auto-exec script. The BMP post-configuration script runs on its own, without any BMP or Normal reload-type restrictions.
NOTE: To display a properly formatted output string, Dell Networking recommends adding the following clido wrapper function at the beginning of TCLSH and EXPECT scripts: # Execute clido and return the output string proc Execclido {cmd_str} { set str [exec clido "$cmd_str"] set tmp_str [string map {\n \r\n} $str ] return $tmp_str } ... set out_str [Execclido "show version"] puts $out_str ...
4. Change the reload-type to BMP and reload the switch. The system boots in BMP mode. 5. The system receives an IP address via the DHCP server which it uses to get a Dell Networking OS image to boot, a configuration file (if supplied), and a preconfiguration script. 6. The system runs the preconfiguration script. • 7. 8. The default timer on the script is 10 minutes. The maximum amount of time the script can run is one hour.
• • • If you reboot the system with the reload-type set as normal-reload and an autoexec script is present in the Flash directory, the following log displays: Starting Dell Networking application 00:00:13: %STKUNIT1-M:CP %RAM-6-ELECTION_ROLE: Stack unit 1 is transitioning to Management unit. 00:00:15: %STKUNIT1-M:CP %CHMGR-5-STACKUNITDETECTED: Stack unit 1 present 00:01:02: %STKUNIT0-M:CP %BMP-5-AUTOEXEC_START: The AutoExec Script is Started.
puts [ exec f10do "show version" ] puts [ exec date ] puts "this is Autoexec script" Dell# Dell# Dell#reload System configuration has been modified. Save? [yes/no]: no Proceed with reload [confirm yes/no]: yes 00:32:16: %STKUNIT1-M:CP %CHMGR-5-RELOAD: User request to reload the chassis syncing disks... done unmounting file systems... unmounting /f10/flash (/dev/ld0h)... unmounting /usr/pkg (/dev/ld0g)... unmounting /usr (mfs:35)... unmounting /f10 (mfs:21)... unmounting /kern (kernfs)...
The following line indicates that the auto-execution script is executing. Dell#show version Dell Networking Real Time Operating System Software Dell Networking Operating System Version: 2.0 Dell Networking Application Software Version: 1-0(0-338) Copyright (c) 1999-2012 by Dell Inc. All Rights Reserved.
send "get $post_conf\n" expect "ftp>" send "get $config_file\n" expect "ftp>" send "bye\n" expect eof after 5000 puts "Download Complete !!!\r\n" if {[file exists $config_file]} { puts "Config File: $config_file downloaded successfully\r\n" } else { puts "ERROR: Config File: $config_file - Not Found\r\n" } if {[file exists $post_conf]} { puts "Post Config Script: $post_conf downloaded successfully\r\n" } else { puts "ERROR: Post Config Script: $post_conf - Not Found\r\n"} # Copy Config to Startup Config pri
print_f10do "end" # Check for Protocl LLDP set lldp_output [ exec f10do "show runn | grep lldp" ] if {[regexp "lldp" $lldp_output]} { puts "LLDP is configured\r\n" # Write the Result to Status File puts $fp "LLDP is configured\n" } else { puts "ERROR: LLDP is not configured\r\n" # Write the Result to Status File puts $fp "ERROR: LLDP is not configured\r\n" } # Configure Interfaces foreach intf_slot $interface_list_slot { set intf "TenGigabitEthernet $intf_slot" puts "Configuring $intf ...\n" puts $fp "Confi
puts $fp "Interface $intf_slot is Connected\r\n" } else { puts "ERROR: Interface $intf_slot is Not Connected\r\n" # Write the Result to Status Fileputs $fp "ERROR: Interface $intf_slot is Not Connected\r\n" }} # Close & FTP Status File puts $fp "========================================\n" close $fp # Configure FTP - Interface print_f10do "configure terminal" print_f10do "interface TenGigabitEthernet 0/22" print_f10do "ip address 20.0.0.
Configuring the DHCP Server Settings Before you can use BMP mode on a switch, first configure a DHCP server. To assign an IP address to the system and other parameters, configure the DHCP server. For more information, refer to the Dell Networking OS Configuration Guide, the Dynamic Host Configuration Protocol chapter. • Configure the DHCP server with the following set of parameters for each client switch.
DHCP Server IP Blacklist If the process does not complete successfully, the DHCP server IP is blacklisted and the BMP process reinitiates. A DHCP server IP is maintained in the blacklist for 10 minutes. If a DHCP offer is received from the blacklisted DHCP server, the offer is rejected until the IP is alive in the blacklist (10 minutes).
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.
• OS — refers to the Dell Networking OS version in the device • US — refers to the user-defined string (a maximum string of 64 characters) File Server Settings Set up a file server and ensure connectivity. To allow file transfers to the switch, configure the file server that holds the boot and configuration files. The system recognizes HTTP, HTTPS, SFTP, TFTP, FTP, USB, and Flash URLs. For example: • tftp://server ip or name/filename • ftp://user:passwd@serverip or name//mypath/Dell-A.B.C.D.
MIB OID Value and Functionality 1.3.6.1.4.1.6027.3.2 0 - 50 (DHCP timeout value config) 3.1.4 1.3.6.1.4.1.6027.3.2 0 - 50 (Set BMP Retry count ) 3.1.5 1.3.6.1.4.1.6027.3.2 String (Set the vendor-class identifier values up to a maximum of 60 characters) 3.1.6 1.3.6.1.4.1.6027.3.2 1 or 2 (Enable or Disable relay option) 3.1.7 1.3.6.1.4.1.6027.3.2 String (Set the mac/hostname/custom-string as remote-id option in DHCP offer 3.1.
4 Bare Metal Provisioning CLI Bare metal provisioning commands are supported on the S4810, S4820T, S5000, S6000, S6000–ON, Z9000, Z9500, IOA, and MXL platforms. In a data center network, BMP automates configuring and updating the switches, ensuring standard configurations across the installed devices. To set up a single switch or a stack of switches with minimal effort, use the auto-configuration function.
Command Modes RELOAD-TYPE CONFIGURATION Command History This guide is platform-specific. For command information about other platforms, refer to the relevant Dell Networking OS Command Line Reference Guide. The following is a list of the Dell Networking OS version history for this command. Related Commands Version Description 9.7(0.0) Introduced on the S4810, S4820T, S5000, S6000, S6000– ON, Z9000, Z9500, IOA, and MXL.
Usage Information Version Description 9.5(0.0) Introduced on the S4810, S4820T, S6000, Z9000, and MXL. This command is applicable only when BMP is running and enables or disables the syslog messages (with a Severity level >2, critical). When BMP is not running, the following error message displays: % Error: bmp process is not running. NOTE: This CLI command is only available in BMP normal context, which is similar to providing the L option in the Factory-default context.
• show reload-type — displays the current Reload mode (BMP mode or Normal mode). config-scr-download Allows you to specify whether the configuration or script file needs to be downloaded. S4810, S4820T, S5000, S6000, S6000–ON, Z9000, Z9500, IOA, and MXL Syntax config-scr-download { enable | disable } To reset the download option, use the no config-scr-download { enable | disable } command.
dhcp-timeout Allows you to configure the DHCP timeout limit. S4810, S4820T, S5000, S6000, S6000–ON, Z9000, Z9500, IOA, and MXL Syntax dhcp-timeout minutes To reset the DHCP time out limit, use the no dhcp-timeout minutes command. Parameters dhcp-timeout minutes Configure the DHCP timeout (in minutes) after which the BMP exits. The range is from 0 to 50. If you enter a range of 0, the timeout is 0 (no limit). NOTE: Dell Networking recommends setting the value to 2 or higher.
relay Allows you to configure the addition of option 82 in DHCP client packets. S4810, S4820T, S5000, S6000, S6000–ON, Z9000, Z9500, IOA, and MXL Syntax relay { enable | disable | remote-id { hostname | MAC | Word }} To reset the options 82 information, use the no relay { enable | disable | remote-id { hostname | MAC | Word }} command. Parameters enable Enable the option 82 in BMP. The default value is the MAC address. disable Disable the option 82 in BMP.
reload conditional nvram-cfg-change After saving the BMP configuration, to perform a reload on the chassis due to configuration changes that changes the NVRAM content, use this command. S4810, S4820T, S5000, S6000, S6000–ON, Z9000, Z9500, and MXL Switch Syntax reload conditional nvram-cfg-change Defaults none Command Modes EXEC Command History This guide is platform-specific. For command information about other platforms, refer to the relevant Dell Networking OS Command Line Reference Guide.
reload-type Allows you to configure the reload-type options in reload-type sub command mode. S4810, S4820T, S5000, S6000, S6000–ON, Z9000, Z9500, IOA, and MXL Syntax reload-type Defaults BMP Command Modes CONFIGURATION Command History This guide is platform-specific. For command information about other platforms, refer to the relevant Dell Networking OS Command Line Reference Guide. The following is a list of the Dell Networking OS version history for this command.
retry-count Allows you to configure the number of retries for downloading the Dell Networking OS image and configuration file.
Parameters scriptname Enter the name of the script to run after the BMP start-up configuration is applied. Defaults none Command Modes CONFIGURATION Command History This guide is platform-specific. For command information about other platforms, refer to the relevant Dell Networking OS Command Line Reference Guide. The following is a list of the Dell Networking OS version history for this command. Version Description 9.7(0.0) Introduced on the S6000–ON. 9.6(0.0) Introduced on the S5000. 9.5(0.
Version Description 9.2(0.0) Introduced on the Z9000, S4810, S4820T, and MXL switch. Example Dell# show boot bmp Config Download via DHCP: enabled BMP State : Waiting for boot options ... BMP State : Received DHCP offer from DHCP server 25.1.1.1 ***** SELECTED OFFER DETAILS ****** Server type= DHCP Acquired IP= 25.1.1.25 Subnet-mask = 255.255.0.0 Image file = tftp://25.1.1.1/boot_file.bin config file = tftp://25.1.1.1/config_file.cfg Server IP = 25.1.1.1 TFTP Server IP = NIL DNS IP = 25.1.1.
Example Related Commands Version Description 9.7(0.0) Introduced on the S4810, S4820T, S5000, S6000, S6000– ON, Z9000, Z9500, IOA, and MXL. Dell(conf-reload-type)#show config ! reload-type auto-save enable boot-type bmp-reload config-scr-download enable dhcp-timeout 12 retry-count 3 vendor-class-identifier Sample relay enable relay remote-id TEST Dell(conf-reload-type)# • reload-type — allows you to configure the reload-type options in reload-type sub command mode.
The following is a list of the Dell Networking OS version history for this command. Usage Information Version Description 9.7(0.0) Introduced on the S6000–ON. 9.6(0.0) Introduced on the S5000. 9.5(0.1) Introduced on the Z9500. 9.3(0.0) Introduced on the S6000. 9.2(0.0) Introduced on the MXL switch. Updated the parameters for S4810, S4820T, and Z9000. 9.1.0.0 Updated the parameters for S4810 and Z9000. 9.0.2.0 Introduced on the S6000. 9.0.0.0 Introduced on the Z9000. 8.3.19.
stop bmp To prevent an infinite loop, stop the switch from reloading in BMP mode. S4810, S4820T, S5000, S6000, S6000–ON, Z9000, Z9500, and MXL Syntax stop bmp NOTE: This command replaces the stop jumpstart command. Defaults none Command Modes EXEC Command History This guide is platform-specific. For command information about other platforms, refer to the relevant Dell Networking OS Command Line Reference Guide. The following is a list of the Dell Networking OS version history for this command.
• When downloading the configuration or script file, it aborts the BMP process after the download and does not apply the configuration or run the script. When you enter GLOBAL CONFIGURATION mode during the BMP process, to avoid configuration conflicts between you and the BMP process, warning / error messages display. Related Commands reload-type — allows you to configure the reload-type options in reload-type sub command mode.
verify Validates the software image on the flash drive after the image is transferred to the system but before the image is installed. S4810, S4820T, S5000, S6000, S6000–ON, Z9000, Z9500, IOA, and MXL Syntax Parameters verify {md5 | sha256} [flash://] img-file [hash-value] md5 MD5 message-digest algorithm. sha256 SHA256 Secure hash algorithm. [flash://] flash (Optional) Specifies the flash drive. The default is to use the flash drive. Enter the filename of the image.
Example Output example without entering the Hash Value for verification using SHA256: Dell# verify sha256 flash://Dell-SE-9.5.0.0.bin SHA256 hash for Dell-SE-9.5.0.0.bin: e6328c06faf814e6899ceead219afbf9360e986d692988023b749e6b2093e93 3 Output example of entering the Hash Value for verification using SHA256: Dell# verify sha256 flash://Dell-SE-9.5.0.0.bin e6328c06faf814e6899ceead219afbf9360e986d692988023b749e6b2093e93 3 SHA256 hash VERIFIED for Dell-SE-9.5.0.0.
Open Management Infrastructure 5 Dell Networking OS supports the Open Management Infrastructure (OMI) framework. OMI is supported on the S4810, S4820T, S5000, S6000, and Z9500 platforms. Overview OMI is an open source package which manages infrastructure components such as servers, storage, and networking. OMI supports the distributed management task force (DMTF) common information model (CIM) / web-based enterprise management (WBEM) standards.
Prerequisites Before using OMI on the Dell Networking OS switch, configure the following: 1. Create a user, with the user privilege 15, where this user can configure the box from the management station through OMI. 2. Install the smartscript package. For detailed information, please refer to the Installing SmartScripting section of the Smart Scripting chapter. 3. Install the OMI package. EXEC Privilege mode package install /OMI-I-9.8.0.0.tar.
• agent — show omi-agent log • client — show omi-client log • dsc — show dsc log • top — show the status from top • bottom — show the status from bottom • number of lines — specify the number of lines NOTE: The script path is/usr/pkg/omi108/bin. Getting Started with OMI This section describes how you start configuring the OMI. To configure the OMI, follow these steps: 1. Get the chassis ready with the packages installed. a. Copy the MOF file tar to flash asflash:/dscmof.tar.
This configuration creates the MOF in the C:\EthernetPortViewMof directory. 8. Connect to OMI. $cred=Get-Credential -UserName:"admin" -Message:"Admin User?" 9. Enter the credential of the user admin.
ModuleName = "DSCModules"; ModuleVersion = "1.0"; }; instance of OMI_ConfigurationDocument { Version="1.0.0"; Author="Administrator"; GenerationDate="12/31/2014 00:11:54"; GenerationHost="WIN-FMOQ86BVN3F"; }; Ethernet Configuration Configuration MSFT_NetworkDevice_EthernetPortViewConfig { Import-DscResource -Name MSFT_NetworkDevice_EthernetPortView Node ("172.168.1.
}; instance of MSFT_NetworkDevice_BgpConfigurationView as $MSFT_NetworkDevice_BgpConfigurationView1ref { EnabledState =True; Id = "1-1-vrf-1"; ExtAsNumber = 1; Ensure = 0; ResourceID = "[MSFT_NetworkDevice_BgpConfigurationView]MyBgpConfiguration"; RouterId = $MSFT_NetworkDevice_IpAddress1ref; SourceInfo = "C:\\ConfigFiles\ \MSFT_NetworkDevice_BgpConfigurationViewConfig.ps1::8::9::MSFT_NetworkDevice_Bgp ConfigurationView"; ModuleVersion = "1.
instance of MSFT_NetworkDevice_BgpPeerView as $MSFT_NetworkDevice_BgpPeerView1ref { Id = "1-vrf-1-1.2.3.4"; ResourceID = "[MSFT_NetworkDevice_BgpPeerView]MyBgpPeer"; SourceInfo = "C:\\ConfigFiles\ \MSFT_NetworkDevice_BgpPeerViewConfig.
AllowAsIn MultiHopTimeToLive RouteMapIn RouteMapOut Ensure KeyEncryptionMethod RemoteRouterId UpdateSourceInterface UpdateSourceInterfaceType ExtAsNumber PSComputerName : : : : : : : : : : : Id Name PeerCredential AddressFamily VrfContext IsEnabled ActivateIPv6 AllowAsIn MultiHopTimeToLive RouteMapIn RouteMapOut Ensure KeyEncryptionMethod RemoteRouterId UpdateSourceInterface UpdateSourceInterfaceType ExtAsNumber PSComputerName : : : : : : : : : : : : : : : : : : 1-vrf1-2.3.4.
KeyEncryptionMethod RemoteRouterId UpdateSourceInterface UpdateSourceInterfaceType ExtAsNumber PSComputerName : : : : : : 3 MSFT_NetworkDevice_IpAddress Id Name PeerCredential AddressFamily VrfContext IsEnabled ActivateIPv6 AllowAsIn MultiHopTimeToLive RouteMapIn RouteMapOut Ensure KeyEncryptionMethod RemoteRouterId UpdateSourceInterface UpdateSourceInterfaceType ExtAsNumber PSComputerName : : : : : : : : : : : : : : : : : : 2-vrf1-1.2.3.
neighbor 1.2.3.4 description descr1 neighbor 1.2.3.4 allowas-in 3 neighbor 1.2.3.4 shutdown neighbor 2.3.4.5 remote-as 3 neighbor 2.3.4.5 shutdown neighbor 1::1 remote-as 3 neighbor 1::1 shutdown exit-address-family ! address-family ipv4 vrf vrf2 neighbor 1.2.3.4 remote-as 3 neighbor 1.2.3.4 shutdown exit-address-family ! address-family ipv4 vrf vrf-1 network 10.10.10.15/32 network 10.10.10.20/32 redistribute static route-map rmap1 redistribute connected route-map rmap2 neighbor 1.2.3.
Puppet 6 Dell Networking OS supports the Puppet automation framework. Puppet Agent is supported on the S4810, S4820T, S5000, S6000, S6000–ON, Z9000, and Z9500 platforms. Overview Puppet is a configuration management utility, that defines the state of system, then automatically enforces the correct state. Puppet Agent is a daemon that runs on all the client servers.
EXEC Privilege mode Dell#package install tftp://10.16.127.35/SMARTSCRIPTS-I-9.6.9.5.tar.gz 3. Install the puppet package. EXEC Privilege mode package install tftp://10.16.127.35/PUPPET-I-9.8.0.0.tar.gz NOTE: You must keep the clock of the chassis in sync with the Puppet master. The synchronization is done by the Network Transfer Protocol (NTP) server. Configuring the Puppet Agent To configure the Puppet Agent, use the following steps. 1. Enable the REST API. CONFIGURATION mode rest-server http 2.
Puppet Agent Configuration Scripts This section describes about the various Puppet Agent configuration scripts: puppet-config To configure or make changes to the agent’s parameters, use the puppet-config script. puppet-config [-d] option=value Following are the mandatory puppet configuration options: agentrestipaddr : IP address to be used for rest apis. The default IP address is 127.0.0.1. agentrestpasswd : Password of the user given in agentrestuser. agentrestport : Port number to be used for rest apis.
puppet-apply To apply any puppet manifest file, use the puppet-apply script.
} } description => "interface-description", tagged_vlans => (vlan | [vlan1, vlan2, vlan3, ...]), untagged_vlan => vlan, vlan_tagging => (enable | disable) LAG Configuration Apply the LAG configurations using both the Puppet Standalone and Puppet Agent. You can read and write the LAG configurations by using the netdev_lagtype.
} } active => (true | false), vlan_id => id, description => "vlan-description", Using the Puppet Facter Dell Networking OS supports the standalone tool called the Puppet Facter. This tool is based on Ruby and provides complete system information about the agent node to the puppet master. To apply the configurations using puppet, you must install the Puppet Facter tools on all the nodes. Following are the facts pair in the manifest files.
Smart Scripting 7 Smart Scripting is supported on the S4810, S4820T, S5000, S6000, Z9000, Z9500, and MXL switch platforms. Smart Scripting allows you to add functionality to Dell Networking switches without updating the Dell Networking OS release. Smart Scripting is available as a separate installable package that supports SQLite DB and NET SNMP applications and TCL, Expect, Perl, Python, Ruby, and Unix scripting languages.
Smart Scripting supports running a script either from the Dell Networking OS CLI or directly from a UNIX shell. You can run scripts periodically, based on events, at boot up or after the switch is initialized. In addition, you can run scripts in the foreground or background and display the progress of a script. If required, you can cancel, stop, or resume scripts. Smart Scripting allows you to automate common management and maintenance tasks, such as: • Building visibility and/or discovery programs.
• Dell Smartscript Utilities supports Perl, Python, and Ruby APIs. • SQLlite database and Perl, Python, Ruby, TCL interface to SQLite. • NetSNMP client and Perl, Python, Ruby interface to the client. • Perl interpreter and associated files. • Python interpreter and associated files. • Ruby interpreter and associated files. • Expanded set of UNIX utilities. • Web-Server with HTTP support (refer to Web Server with HTTP Support).
• tftp://host-ipaddress/filepath installs Smart Scripting from a file stored on a TFTP server. • nfsmount://filepath copies from the nfs mount file system. To remove an installed Open Automation package, such as Smart Scripting, use the package uninstall command. To follow the progress of a package installation (or removal), use the show packages command.
clido To configure any command on the device directly without handling it via the telenet or ssh sessions, use the clido system command. Syntax: clido “CLI command” Example clido clido clido clido clido "configure terminal" "interface vlan 10" "no shutdown" "end" "show vlan" NOTE: clido maintains context upon execution in the system. To handle such cases, switch between different submodes wherever required for the needed configurations.
no shutdown exit interface loopback 10 ip address 10.10.10.10/24 end do show vlan show running | grep loopback dellsyslog A Dell proprietary utility which helps you in generating custom SYSLOGS with the configured severity.
Following are the Dell Networking OS APIs: • DellExec — If you need to execute the script inside another script, you can make use of this API. Syntax: DellExec (scriptName, [args]) • DellCliConfig — If you need to configure the list of Dell Networking OS commands, you can make use of this API.
SQLite The Dell Networking OS supports the SQLite database engine as it is self-contained, serverless, zeroconfiguration, and transactional. This database performs the following tasks: • Stores all the periodically collected data and/or statistics from the Dell Networking OS. • Stores the Dell Networking OS configuration files. • Stores other script logs, updated, deleted, and transferred using this database. Dell Networking OS provides Perl, Python, Ruby, and TCLSH interfaces for SQLite.
System Attributes Value Description value defines how far a program may extend its break with the sbrk(2) system call. stacksize 2,408 Maximum size (in bytes) of the stack segment for a process; this value defines how far a program’s stack segment can be extended. The system automatically performs stack extension. coredumpsize unlimited Largest size (in bytes) of a core file that can be created. memory use 233,244 Maximum size (in bytes) to which a process’s resident set size may grow.
UNIX Utility Function chown Change file owner and group. cksum Display file checksums and block counts. cut Select portions of each line of a file. date Display or set date and time. dd Convert and copy a file. df Display free disk space. env Set and print environment. expr Evaluate expression. fc List the history of commands on the computer. fg Change the background process to the foreground process. file Determine the file type. find Walk a file hierarchy.
UNIX Utility Function ssh Open the SSH client (remote login program). stty Change the settings of a UNIX computer terminal. tail Display the last part of a file. test Condition evaluation utility. ulimit Get and set process limits. umask Set the file creation mode mask. vmstat Report virtual memory statistics. wait Await process completion. wc Word, line, and byte count. who Display the users who are currently logged in.
Downloading Scripts to a Switch Download a script to the switch using TFTP, FTP, or FLASH. Save the script to the dedicated script storage location, /usr/pkg/ss-scripts. 1. Configure the folders to mount a remote directory in the local Dell Networking OS path through a network file system (NFS). CONFIGURATION mode mount nfs nfs-server-ip: remote_dir mount_name [username username | password password] 2. Copy a script to a switch. Downloaded files are stored in the following path: /usr/pkg/ssscripts.
Script Scheduler from EXEC mode To trigger scripts to run periodically or based on an event, use the following commands. • Schedule a script to run in EXEC mode. Schedule a script to execute at a specific time and optionally stop after a specified time. By default, the script runs in the foreground. To run the script in the background, use the bg parameter. EXEC mode script execute script-name [start {at | date-time | after time}] [stop {at date-time | after time}] [bg] [arguments arg[..
[weekday day] [ month month] [monthday nday]} | cpu-usage percentage | memusage percentage} Following example shows the event to trigger a script at 22:22 and then triggers every Monday midnight and stops at 02:02–11/10/14: Dell(conf)#script trigger-event Event2 time-event start at 22:22 stop at 02:02-11/10/14 weekday mon Following example shows the event triggering the script once the cpu-usage reaches 30%: Dell(conf)#script trigger-event event1 cpu-usage 30 Following example shows how you can define the e
Following snippet triggers a script even if any one of the pattern matches: Dell(conf)#script trigger-event Server_Reporter_Event log-event tag tag-orex "Major alarm" "Minor alarm" Dell(conf)#script event-handler handler1 Dell(conf-screvt-handler)#execute Report_server.
• To suspend a currently running script, use the script stop command. • Dell#script stop script-name admin.pl To resume suspended script, use the script resume command. • Dell#script resume job-id 0 To clear the supervised script that is in blocked state, use the script clear command. • Dell#script clear script-name args.pl To clear all the watch blocked state scripts, use the script clear all command. • Dell#script clear all To terminate a script that is running, use the script kill command.
1. When you run a script from a UNIX shell, first access the shell using the start shell command. 2. You are prompted to enter a user name and password configured with the username command. For more information, refer to Creating a User Name and Password for Smart Scripting. The following shows examples of how to execute a Perl, Python, and UNIX shell script directly from a NetBSD shell on Dell Networking OS. • The first bold line shows logging in to a UNIX shell.
(Optional) For script-parameter, enter the values of up to three parameters to be applied when the script runs. Enter a blank space between parameter values; for example: script username admin /f10/flash/createVlans.
Smart Scripting CLI 8 Smart Scripting is supported on the S4810, S4820T, S5000, S6000, S6000–ON, Z9000, Z9500, and MXL platforms. disable Allows you to enable or disable the current event handler configuration. S4810, S4820T, S5000, S6000, S6000–ON, Z9000, Z9500, and MXL Syntax disable To reset the event handler, use the [no] disable command. Defaults none Command Modes SCRIPT EVENT HANDLER CONFIGURATION Command History This guide is platform-specific.
arguments arg [..args] Enter the keyword arguments then the arguments to script. The maximum length is 64 characters. The arguments can be any number of words within quotes and separated by a space. Defaults none Command Modes SCRIPT EVENT HANDLER CONFIGURATION Command History This guide is platform-specific. For command information about other platforms, refer to the relevant Dell Networking OS Command Line Reference Guide.
Usage Information Related Commands Version Description 9.7(0.0) Introduced on the S6000–ON. 9.6(0.0) Introduced on the S5000. 9.5(0.1) Introduced on the Z9500. 9.3(0.0) Introduced on the S6000. 9.2(0.0) Introduced on the S4810, S4820T, Z9000, and MXL. • All the mount points are maintained in the /f10/mnt/nfs folder. • Only the relative path (mount point name) is acceptable. If the path you enter is either complete or absolute, an error occurs.
The following is a list of the Dell Networking OS version history for this command. Usage Information Version Description 9.7(0.0) Introduced on the S6000–ON. 9.6(0.0) Introduced on the S5000. 9.5(0.1) Introduced on the Z9500. 9.2(0.0) Introduced on the MXL switch. 9.0.2.0 Introduced on the S6000. 9.0.0.0 Introduced on the Z9000. 8.3.19.0 Introduced on the S4820T. 8.3.8.0 Introduced on the S4810.
Usage Information Version Description 9.6(0.0) Introduced on the S5000. 9.5(0.1) Introduced on the Z9500. 9.2(0.0) Introduced on the MXL switch. 9.0.2.0 Introduced on the S6000. 9.0.0.0 Introduced on the Z9000. 8.3.19.0 Introduced on the S4820T. 8.3.8.0 Introduced on the S4810. When you uninstall an Open Automation package, it is removed from the local flash memory.
scriptparameter (Optional) Enter the values of up to three parameters to apply when the script runs. Enter a blank space between parameter values. For example, script username admin /f10/flash/createVlans.py 1 2. Defaults none Command Modes CONFIGURATION Command History This guide is platform-specific. For command information about other platforms, refer to the relevant Dell Networking OS Command Line Reference Guide. The following is a list of the Dell Networking OS version history for this command.
To display the scripts that are currently running, including the scripts you have stopped, use the show running-config | grep command. script (stop/resume/clear/kill/unschedule) Stop, resume, clear, kill, or unschedule an Expect, Perl, Python, Ruby, Tcl, UNIX, and ZSH shell script from the Dell Networking OS CLI.
Usage Information Version Description 9.3(0.0) Introduced on the S6000. 9.2(0.0) Introduced on the S4810, S4820T, Z9000, and MXL Switch. Use the keyword unschedule only on scripts that are not currently running and that were scheduled using the script execute command in EXEC mode. script event-handler Allows you to provide mapping between the scripts and trigger events.
Parameters script-name Enter the name of the script to schedule for execution. start at date-time Enter the keywords start at then the time and date in HH:MM-MM/DD/YY format to begin executing the script at a specific time and date or in HH:MM format to begin the script at the specified time on the same day (if the mentioned time is elapsed, the script runs on the next day HH:MM mentioned). The date can be the present or a future date.
Usage Information Version Description 9.5(0.1) Introduced on the Z9500. 9.3(0.0) Introduced on the S6000. 9.2(0.0) Introduced on the S4810, S4820T, Z9000, and MXL Switch. All times selected follow the system time of the switch. The maximum number of scripts to configure is 100. An error message displays when you exceed the limit. • • Example Only the person who configured the scheduled scripts (or a higher privileged user) can manage the script.
stop at date-time (Optional) Enter the keywords stop at date-time with the time and date either in HH:MM-MM/DD/YY format to stop executing the script or in HH:MM format to stop the script at the specified time on the same day. The date must be a future date. stop after time (Optional) Enter the keywords stop after time then the time in [HHHH:] MMMM format to indicate the time after which the script stops executing.
• Only the person who configures the scheduled scripts (or a higher privileged user) can change them. • If you do not provide the username, the system uses current session username. If the script is triggered from the console, the system uses the Dell Networking OS default username (smartuser). script get Copy a script to a switch.
NOTE: For stack systems, the script from ss-scripts synchronizes across the stack for every one hour. When the stack forms first, the script synchronization from the master to members happens only after 10 minutes. script path Configure the path for the script on the switch. S4810, S4820T, S5000, S6000, S6000–ON, Z9000, Z9500, and MXL Syntax script path path-name To remove the path for the script, use the no script path command. Parameters path-name Enter the full path of the location of the script.
script remove Remove a script from a switch. S4810, S4820T, S5000, S6000, S6000–ON, Z9000, Z9500, and MXL Syntax Parameters script remove {file-name | all} file-name Enter the filename of the script to remove from the switch. all Enter the keywords all to remove all files from the dedicated folder on the switch. Defaults none Command Modes EXEC Command History This guide is platform-specific.
[weekday day] [ month month] [monthday nday]} | cpu-usage percentage | mem-usage percentage} To delete the trigger event, use the no script trigger-event command. Parameters Smart Scripting CLI event-name Enter the name of the script event to trigger. log-event tag tag—or— ex tags Enter the keywords log-event tag tag—or—ex then the pattern (tag) in the syslog message to trigger the event if any pattern matches the syslog message. You can enter a maximum of three tags. Separate each tag by commas.
weekday day Enter the keyword weekday then the day of a week to execute the script. Select one or more days from the following values: mon, tue, wed, thu, fri, sat, and sun. Separate each day by commas. month month Enter the keyword month then the month to execute the script. Select one or more months from the following values: jan, feb, mar, apr, may, jun, jul aug, sep, oct, nov, and dec. Separate each month by commas. monthday nday Enter the keyword monthday then the day to execute the script event.
NOTE: The time-events schedule time takes effect once after the device configures the trigger-event (event). Related Command script event-handler — Allows you to provide mapping between the scripts and trigger events. Examples Following example shows how the event triggers a script, even if any one of the pattern matches.
Command History This guide is platform-specific. For command information about other platforms, refer to the relevant Dell Networking OS Command Line Reference Guide. The following is a list of the Dell Networking OS version history for this command. Version Description 9.7(0.0) Introduced on the S6000. 9.6(0.0) Introduced on the S5000. 9.5(0.1) Introduced on the Z9500. 9.2(0.0) Introduced on the MXL Switch. 9.0.2.0 Introduced on the S6000. 9.0.0.0 Introduced on the Z9000. 8.3.19.
HTTP Server mini_httpd 1.19 Perl and Python function library for Force10 SmartScripts smartutils 2.0.0 WebConnect Web UI and CGI scripts htdocs 2.0.0 Example (show packages system) Dell#show packages system Package Information -----------------------------------Unit Package Name Version Status ------------------------------------0 SMARTSCRIPTS 2.9.9.2 Installed nano 2.2.6nb1 Installing 1 SMARTSCRIPTS 2.9.9.2 Installing nano 2.2.
Defaults none Command Modes EXEC Privilege Command History This guide is platform-specific. For command information about other platforms, refer to the relevant Dell Networking OS Command Line Reference Guide. The following is a list of the Dell Networking OS version history for this command. Version Description 9.7(0.0) Introduced on the S6000–ON. 9.6(0.0) Introduced on the S6000. 9.5(0.1) Introduced on the Z9500. 9.3(0.0) Introduced on the S6000. 9.2(0.
Usage Information Version Description 8.3.8.0 Introduced on the S4810. To invoke the Dell Networking OS operations, start an NetBSD shell on a switch before you can enter UNIX commands or run a script directly from the shell (refer to Running a Script from the UNIX Shell). After you start a shell, you are prompted to enter a username and password. Related Commands show packages — displays all the Open Automation packages installed on the switch.
Parameters cpu percentage Enter the keyword cpu and the maximum percentage limit to suspend and hold scripts for execution. The range is from 20 to 90 percent. mem percentage Enter the keyword mem and the maximum percentage limit to suspend and hold scripts for execution. The range is from 20 to 90 percent. disk percentage Enter the keyword disk and the maximum percentage limit to suspend and hold scripts for execution. The range is from 20 to 90 percent. Only /usr/pkg is monitored.
privilege privilege Enter the keyword privilege then the privilege level to run the scripts. The range is from 1 to 15. Defaults none Command Modes SCRIPT EVENT HANDLER CONFIGURATION Command History This guide is platform-specific. For command information about other platforms, refer to the relevant Dell Networking OS Command Line Reference Guide. The following is a list of the Dell Networking OS version history for this command. Usage Information Example Version Description 9.7(0.
password password Enter a password to access the UNIX shell. Defaults none Command Modes CONFIGURATION Command History This guide is platform-specific. For command information about other platforms, refer to the relevant Dell Networking OS Command Line Reference Guide. The following is a list of the Dell Networking OS version history for this command. Usage Information 116 Version Description 9.7(0.0) Introduced on the S6000–ON. 9.6(0.0) Introduced on the S5000. 9.5(0.
Virtual Server Networking 9 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 Network fabric and the virtual servers to automate network management and configuration tasks throughout the data center.
Figure 2. Virtual Server Networking Example For any change, VSN subscribes use hypervisor to notify the switch. Depending on the hypervisor mode you configure, the Dell Networking OS may automatically update its configuration, provide provisioning for configuration changes, or require system administrator intervention. Hypervisor Modes There are two modes for retrieving configuration information from a hypervisor on a virtual server: check and config.
VLAN Configurations The following sections describe management, data, and hypervisor-unaware VLANs. Management VLANs The management interface between a switch and a hypervisor can be a single port or VLAN interface. If the connection with a hypervisor is through a VLAN, manually configure the VLAN interface on the switch before VSN can establish a connection with the hypervisor and retrieve information from it about the virtual-server configuration.
Install VSN You install VSN as a separate Open Automation package, apart from the Dell Networking OS image and the downloaded Smart Scripting package. When you install the VSN package, VSN is loaded into the Dell Networking OS. NOTE: VSN is only supported on standalone switches; it is not supported in stacked configurations.
• • 7. tftp://host-ipaddress/filepath installs VSN from a file stored on a TFTP server. nfsmount://filepath copies from a file stored on an NFS mount file system. Enter the following command to configure the Perl script (VSNAgent.pl) used for VSN operations on VMware hypervisors: script /usr/pkg/scripts/VSNAgent/VMWare/VSNAgent.pl. To follow the progress of a package installation (or removal), use the show packages command.
• • • • 5. For a VMware hypervisor: https://[ip-address]/sdk/vimService username [name] password [password] For an Xen hypervisor: http://ip-address username [name] password [password] username name: Username to use for authentication on the server. password password: Password to use for authentication shown in clear text. Set the mode for retrieving virtual server configurations and updating Dell Networking OS settings on the switch.
• Enter the shutdown and no shutdown commands on a VSN-enabled port. The discovery process resumes on the individual port only, not on all enabled ports. • Enter the disable and no disable commands in Hypervisor Configuration mode, for a specified type of hypervisor connection. The discovery process resumes on all enabled ports. • An update arrives from a hypervisor. The discovery process resumes on all VSN-enabled ports.
• For VMware hypervisors, the Perl script is stored is at /usr/pkg/scripts/VSNAgent/VMWare/ VSNAgent.pl. • For Citrix Xen hypervisors, the Python script is stored is at /usr/pkg/scripts/VSNAgent/Xen/ hpAgtMain.py CAUTION: The Dell Open Automation Virtual Server Networking™ software package (the “Product”) may contain the VMware SDK for Perl, which is licensed by VMware, Inc. VMware will not provide technical support for the VMware SDK included in the Product.
no hypervisor name Enter the name of the hypervisor session that you want to remove. Uninstalling VSN Uninstalling the VSN package removes it from the internal flash memory on a switch. CAUTION: Before you uninstall the VSN package, first stop all VSN scripts that are currently running using the no script script-name command. • Uninstall the VSN package from the system. EXEC Privilege mode package uninstall name Enter the name of the VSN package exactly as it appears in show packages output.
Example of the show configuration hypervisor session command. Dell(conf-hypervisor)#show config ! hypervisor LocalNetwork mode config access https://10.10.10.10 username admin password 7 1d28e9f33f99cf5c Example of the show hypervisor supported command. Dell#show hypervisor supported vmware xen-citrix Example of the show virtualswitch all hypervisor sessions command.
Virtual Server Networking CLI 10 The virtual server networking CLI is supported on the S4810, S4820T, S5000, and MXL switch platforms. NOTE: VSN is only supported on standalone switches; it is not supported in stacked configurations. access Configure the connection to access a hypervisor. S4810, S4820T, S5000, and MXL Switch Syntax Parameters [no] access url username name password password url Enter the URL location of the desired hypervisor.
Usage Information Version Description 8.3.19.0 Introduced on the S4820T. 8.3.8.0 Introduced on the S4810. VSN tries to establish a connection with a hypervisor only after you configure the user credentials (username and password) with the access command. disable Stop a hypervisor session. S4810, S4820T, S5000, and MXL Switch Syntax [no] disable Defaults disable Command Modes HYPERVISOR Command History This guide is platform-specific.
hypervisor Specify the name of a hypervisor session with which VSN connects. S4810, S4820T, S5000, and MXL Switch Syntax Parameters [no] hypervisor name name Enter up to 40 characters to specify the name of a hypervisor session to which you want to connect on network servers. Defaults none Command Modes HYPERVISOR Command History This guide is platform-specific. For command information about other platforms, refer to the relevant Dell Networking OS Command Line Reference Guide.
configuration has changed (for example, a VLAN is added or removed). Manually enter changes in the Dell Networking OS configuration parameters. config VSN retrieves configuration information from the Hypervisor and implements any necessary configuration changes automatically. Defaults config Command Modes HYPERVISOR Command History This guide is platform-specific. For command information about other platforms, refer to the relevant Dell Networking OS Command Line Reference Guide.
Parameters location Enter the location where you want to install an Open Automation package, where location is one of the following values: • flash://filename installs the VSN package file stored in flash memory on the switch. • ftp://userid:password@host-ip-address/filepath logs in and installs VSN from a file stored on an FTP server. • tftp://host-ip-address/file-path installs VSN from a file stored on a TFTP server. • nfsmount://filepath copies from a file stored on an NFS mount file system.
Parameters name Enter the name of the Open Automation package, exactly as it appears in the show packages list. Defaults none Command Modes EXEC Privilege Command History This guide is platform-specific. For command information about other platforms, refer to the relevant Dell Networking OS Command Line Reference Guide. The following is a list of the Dell Networking OS version history for this command. Usage Information Version Description 9.6(0.0) Introduced on the S5000. 9.2(0.
Defaults none Command Modes CONFIGURATION Command History This guide is platform-specific. For command information about other platforms, refer to the relevant Dell Networking OS Command Line Reference Guide. The following is a list of the Dell Networking OS version history for this command. Usage Information Version Description 9.6(0.0) Introduced on the S5000. 9.2(0.0) Introduced on the MXL switch. 8.3.19.0 Introduced on the S4820T. 8.3.8.0 Introduced on the S4810.
Usage Information Use this information when defining types of Hypervisor connections with the hypervisor command. Example Dell#show hypervisor supported vmware xen-citrix Related Commands hypervisor — defines a hypervisor instance. show packages Displays all Open Automation packages installed on a switch. S4810, S4820T, S5000, and MXL Switch Syntax show packages Defaults none Command Modes EXEC Privilege Command History This guide is platform-specific.
HTML::Tagset 3.20 HTML::Parser 3.65 LWP 5.836 Net::Telnet 3.03 OSSP::uuid 1.0602 UUID 0.02 version 0.82 Class::Inspector 1.24 Task::Weaken 1.03 Algorithm::Diff 1.1902 Text::Diff 1.37 SOAP::Lite 0.712 Crypt::SSLeay 0.57 URI::urn::uuid 0.03 UUID 0.03 Crypt::SSLeay 0.57 Net::SNMP 6.0.0 Net::Telnet::Cisco 1.10 HTTP Server mini_httpd 1.19 Perl and Python function library for Force10 SmartScripts smartutils 2.0.0 WebConnect Web UI and CGI scripts htdocs 2.0.
virtualswitc h-name Display information on a specified virtual switch by entering the name the Hypervisor generates. Defaults none Command Modes EXEC Privilege Command History This guide is platform-specific. For command information about other platforms, refer to the relevant Dell Networking OS Command Line Reference Guide. The following is a list of the Dell Networking OS version history for this command. Usage Information Version Description 9.6(0.0) Introduced on the S5000. 9.2(0.
Vlan Id :VIFs: MAC 00:0c:29:4f:66:19 PIFs: MAC 00:26:55:dd:01:4f MTU 8000 MTU 8000 NOTE: In the show virtualswitch output, VLAN 1 displays as VLAN ID 1; VLAN 4095 displays without a VLAN ID as "-". show vmmap Displays the virtual machines accessed on a switch interface. S4810, S4820T, S5000, and MXL Switch Syntax Parameters show vmmap interface interface Display information on the Hypervisor session established on a specified interface.
Usage Information The show vmmap command displays information on the virtual machines accessed on a switch interface, including the virtual machine name, VMAC address, and corresponding VLAN ID Example Dell#show vmmap gigabitethernet 0/32 VM Name VIF Vlan Redhat_207_03_nfs 00:0c:29:4f:66:19 Redhat_207_03_nfs 00:50:56:92:00:77 ID 138 NOTE: In the show vmmap output, VLAN 1 displays as VLAN ID 1; VLAN 4095 displays without a VLAN ID as "- ". Related Commands hypervisor — defines a Hypervisor instance.
vsn enable Enable VSN on an interface. S4810, S4820T, S5000, and MXL Switch Syntax [no] vsn enable Defaults VSN is disabled by default on switch interfaces. Command Modes INTERFACE Command History This guide is platform-specific. For command information about other platforms, refer to the relevant Dell Networking OS Command Line Reference Guide. The following is a list of the Dell Networking OS version history for this command. Usage Information Version Description 9.6(0.
REST API 11 Representational state transfer (REST) application programming interface (API) is an integrated part of the Dell Networking operating system (OS). The Dell Networking OS supports the S4810, S4820T, S5000, S6000, Z9000, and Z9500 platforms. HTTP and HTTPS Use REST API to configure and monitor a Dell Networking switch over the hyper text transfer protocol (HTTP) and hyper text transfer protocol secure (HTTPS).
REST Authentication The REST API authenticates and authorizes the user based on the Dell Networking OS AAA configuration. You can locally configure or validate through the AAA infrastructure. For more information about the AAA Accounting mode, refer to the Dell Networking OS Configuration Guide, Security chapter. The Dell Networking OS CLI user level privilege dictates the level of the REST API access. Users with privilege level 0 or 1 have read-only access; the allowed REST API method is GET.
- 11.1.1.1/24 The following configuration depicts the IP address configuration for router interfaces via REST– PUT request: curl -v -u admin:admin http://10.16.151.159:8008/api/running/dell/interfaces/ interface/tengig-0-0 -X PUT -T ipaddr_config_put.xml * About to connect() to 10.16.151.159 port 8008 * Trying 10.16.151.159... connected * Connected to 10.16.151.159 (10.16.151.
- 11.1.1.1/24 auto 299 * 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 100 11.1.1.
Following is the current configurations applied on the system: Dell#show config ! router bgp 100 neighbor 11.1.1.2 remote-as 200 neighbor 11.1.1.2 no shutdown Dell# The following configuration retrieves the BGP running-config via REST API: curl -u admin:admin http://10.16.151.159:8008/api/running/dell/router/bgp PAGE 145> > > > > < < < < < < < < < < < < * * Host: 10.16.151.159:8008 Accept: */* Content-Length: 493 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:25:31 GMT Allow: GET, POST, OPTIONS, HEAD Content-Length: 0 Content-Type: text/html Etag: 1417-699531-877544@0 Connection #0 to host 10.16.151.
11 1 5.0.
Status Error Codes Description 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.
• is the name of the type for leafs and leaf-lists. Configurations This section describes the properties of all the configurations. BGP The following definition configures and displays the properties of a BGP configuration.
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | REST API | | +--rw path-count? uint8 | | +--rw enable? boolean | +--rw dampening? | +--rw half-life? uint32 | +--rw reuse? uint32 | +--rw suppress? uint32 | +--rw max-suppress-time? uint32 | +--rw route-map? dell:route-map-name +--rw default-metric? uint32 +--rw description? string +--rw timers | +--rw bgp | +--rw keepalive? dell:seconds | +--rw hold-time? dell:seconds +--rw maxi
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 150 | +--rw remove-private-as? boolean | +--rw route-map [direction] | | +--rw direction dell:bgp-opt-dir | | +--rw name? dell:route-map-name | +--rw route-reflector-client? boolean | +--rw sender-side-loop-detection? boolean | +--rw soft-reconfiguration? enumeration | +--rw subnet? dell:ip-address-with-prefix | +--rw dmzlink-bw? boolean +--rw neighbor [neighbor-router] | +--rw n
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | REST API | +--rw summary-only? boolean | +--rw suppress-map? dell:route-map-name +--rw distance? | +--rw bgp? | +--rw external-distance? uint8 | +--rw internal-distance? uint8 | +--rw local-distance? uint8 +--rw redistribute? | +--rw connected? | | +--rw route-map? dell:route-map-name | +--rw static? | | +--rw route-map? dell:route-map-name | +--rw imported-bgp? | | +--rw route-m
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 152 | +--rw dampening? | +--rw half-life? uint32 | +--rw reuse? uint32 | +--rw suppress? uint32 | +--rw max-suppress-time? uint32 | +--rw route-map? dell:route-map-name +--rw network [ipv4-address] | +--rw ipv4-address dell:ipv4-address-with-prefix | +--rw route-map? dell:route-map-name | +--rw backdoor? boolean +--rw network-v6 [ipv6-address] | +--rw ipv6-address dell:ipv6-addre
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | REST API | +--rw weight? uint16 | +--rw timers? | | +--rw keepalive? dell:seconds | | +--rw hold-time? dell:seconds | +--rw add-path? | | +--rw addpath? enumeration | | +--rw path-count? uint8 | +--rw local-as? | | +--rw as-number? dell:as-number | | +--rw no-prepend? boolean | +--rw password? | | +--rw encryption-type? enumeration | | +--rw password-value? string | +--rw activat
| +--rw allowas-in? uint8 | +--rw default-originate? | | +--rw route-map? dell:route-map-name | +--rw distribute-list [direction] | | +--rw direction dell:bgp-opt-dir | | +--rw name? dell:prefix-list-name | +--rw filter-list [direction] | | +--rw direction dell:bgp-opt-dir | | +--rw name? dell:aspath-access-list-name | +--rw maximum-prefix? | | +--rw maximum? uint32 | | +--rw threshold? uint8 | | +--rw warning-only? boolean | +--rw next-hop-self? boolean | +--rw remove-private-as? boolean | +--rw route-map
Interface The following definition configures and displays the properties of an Interface: Module: INTERFACE URI: /api/running/dell/interfaces/interface Methods Supported: GET, POST, PUT, PATCH, and DELETE NOTE: The POST and DELETE operations are not supported on Physical Interfaces. Use the following formats for various interface types: 1. 2. Physical Interface:-- • The can be TenGigabitEthernet or FortyGigabitEthernet.
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 156 | | +--rw out? | | +--rw WORD access-list-name | +--rw learning-limit? | +--rw count? uint32 | +--rw (operations)? | | +--:(sticky) | | | +--rw sticky? boolean | | +--:(non-sticky) | | +--rw dynamic? boolean | | +--rw station-move? boolean | +--rw learn-limit-violation? | | +--rw (action)? | | +--:(log) | | | +--rw log boolean | | +--:(shutdown) | | +--rw shutdown boolean | +--
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | REST API | | +--rw primary? | | | +--rw address? dell:ipv4-address-with-prefix | | +--rw dhcp? | | | +--rw relay? | | | | +--rw information-option? | | | | +--rw remote-id? | | | | +--rw (remote-id-string)? | | | | +--:(hostname) | | | | | +--rw hostname? boolean | | | | +--:(mac) | | | | | +--rw mac? boolean | | | | +--:(user-string) | | | | +--rw user-string? string | | | +--rw
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | +--rw autoconfig? boolean | | +--rw rtr-address? boolean | | +--rw off-link? boolean | | +--rw lifetime? | | +--rw valid ipv6-nd-prefix-lifetime | | +--rw preferred ipv6-nd-prefix-lifetime | +--rw ra-lifetime? uint32 | +--rw reachable-time? uint32 | +--rw retrans-timer? uint32 | +--rw suppress-ra? boolean +--rw access-group? +--rw in? | +--rw WORD access-list-name | +--rw implicit-permit? boolean | +--rw (ipv6-action)? | +--:(vlan) | | +--rw vlan* v
+--rw prefix-list* [name] +--rw name dell:prefix-list-name +--rw description? string +--rw seq* [seq-num] +--rw seq-num uint32 +--rw action ipv6-prefix-list-action-types +--rw ipv6-prefix union +--rw prefix-min-len? uint32 +--rw prefix-max-len? uint32 Management-Route The following definition configures and displays the properties of a Management-Route: Module: MANAGEMENT-ROUTE URI: /api/running/dell/management/route Methods Supported: GET, POST, PUT, PATCH, and DELETE Management Route Configuration
types types 160 | +--rw protocol ip-protocols-type | +--rw source ipv4-address-any | +--rw source-mask dell:ipv4-mask-or-prefix | +--rw destination ipv4-address-any | +--rw destination-mask dell:ipv4-mask-or-prefix | +--rw tcp-options* enumeration | +--rw tcp-udp-port-oper-list [port-type] | +--rw port-type tcp-udp-port-type | +--rw oper-type tcp-udp-port-oper-type | +--rw port uint32 | +--rw start-port uint32 | +--rw end-port uint32 +--rw ipv6 +--ro stats +--ro access-list +--ro mac [name] | +--ro name
+--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro count-type? egress-count-value? ingress-count-value? log? monitor? order? dscp? ecn? fragments? acl-rule-count-types uint32 uint32 boolean boolean uint32 uint32 uint32 boolean Port Mirroring The following definition is for configuring and displaying the properties of port mirroring: Module: Port Mirroring URI: /api/running/dell/monitor-session Methods Supported: GET, POST, PUT, PATCH, and DELETE Port Mirroring Configuration Model +--rw dell +--r
Route Map Configuration Model +--rw route-map* [map-name seq] +--rw map-name string +--rw seq union +--rw (entry)? | +--:(permit) | | +--rw permit? boolean | +--:(deny) | +--rw deny? boolean +--rw set +--rw ext-community! +--rw bandwidth? uint32 Static Route The following definition configures and displays the properties of a Static Route configuration: Module: IP STATIC ROUTE URI: /api/running/dell/ip/route Methods Supported: GET, POST, PUT, PATCH, and DELETE Static Route Configuration Model +--rw i
Operational This section describes the properties of all the IPv4 operational data.
| +--ro origin-code? enumeration | +--ro is-nlre-loc-aggtd? snmpv2-tc:TruthValue | +--ro is-stale? snmpv2-tc:TruthValue | +--ro status-code? enumeration | +--ro best-route? snmpv2-tc:TruthValue | +--ro link-bandwidth? string +--ro received-routes +--ro prefix-list* [network-prefix network-prefix-len nexthop-address seq-num] +--ro network-prefix inet:ip-address +--ro network-prefix-len inetaddress:InetAddressPrefixLength +--ro next-hop-address inet:ip-address +--ro seq-num uint32 +--ro metric? uint32 +--ro l
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | REST API +--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro +
with-prefix with-prefix with-prefix 166 | | | | | | | | | | | | | | | | | | | | | | | | | | +--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro inq-replaced-list? inq-removed-list? outq-added-list? outq-removed-list? accept-prefix? advertised-prefix? prefix-denied? addr-withdrawn-from-peer? addr-withdrawn-by-peer? martian-addr-ignored? restart-time-adver-peer? restart-time-rece-peer? stale-path-time-
prefix REST API | +--ro bfd-role? enumeration | +--ro local-rib | | +--ro routes-added? uint32 | | +--ro routes-replaced? uint32 | | +--ro routes-withdrawn? uint32 | | +--ro router-id? dell:ipv6-address-with-prefix | +--ro neighbor [neighbor-address] | +--ro neighbor-address dell:ipv6-address-with-prefix | +--ro remote-as? string | +--ro msg-rcvd? uint32 | +--ro msg-sent? uint32 | +--ro table-version? uint32 | +--ro in-queue? string | +--ro out-queue? string | +--ro up-time? string | +--ro state-prefix? s
prefix prefix prefix 168 | +--ro weight? uint32 | +--ro as-path-string? string | +--ro origin-code? bgp-origin-code +---x community | +--ro input | | +--ro local-as? boolean | | +--ro no-advertise? boolean | | +--ro no-export? boolean | | +--ro community-number? string | +--ro output | +--ro community | +--ro local-rib | | +--ro routes-added? uint32 | | +--ro routes-replaced? uint32 | | +--ro routes-withdrawn? uint32 | | +--ro router-id? dell:ipv6-address-with| +--ro prefix-list [network-prefix next-hop
prefix prefix REST API | +--ro network-prefix dell:ipv6-address-with-prefix | +--ro next-hop-addr dell:ipv6-address-with-prefix | +--ro status-code? bgp-status-code | +--ro best-route? boolean | +--ro path-source? bgp-path-source | +--ro metric? string | +--ro local-pref? string | +--ro weight? uint32 | +--ro as-path-string? string | +--ro origin-code? bgp-origin-code +---x cluster-list | +--ro input | | +--ro cluster-list-id? bgp-list-name | +--ro output | +--ro cluster-list [cluster-list-id] | +--ro cl
prefix +--ro routes [network from] +--ro network dell:ipv6-address-with-prefix +--ro from dell:ipv6-address +--ro status-code? bgpv6-status-code +--ro best-route? boolean +--ro flaps? uint8 +--ro duration? hour-minute-second +--ro reuse? hour-minute-second +--ro as-path? string +--ro path-source? bgp-path-source +--ro origin-code? bgp-origin-code Interface Use the following definition to get the static IPv4 operational data: Module: STATS URI: /api/operational/dell/stats Methods Supported: GET Inter
+--ro ipv4-address? string +--ro ipv4-address-mode? enumeration +--ro dhcp-client? string +--ro link-local-ipv6-address? dell:ipv6-address-with-prefix +--ro global-ipv6-address* [address] | +--ro address dell:ipv6-address-with-prefix +--ro secondary-ip-address* [address] | +--ro address dell:ipv4-address-with-prefix +--ro line-speed? enumeration +--ro ip-mtu? uint32 +--ro arp-type? enumeration +--ro arp-timeout? uint32 +--ro last-clear-intf-cnters? uint32 +--ro last-intf-status-changed? uint32 +--ro in-octe
IP Route Use the following definition to get the Route statistics: Module: IP ROUTE URI: /api/operational/dell/stats/ip/route Methods Supported: GET Route Model +--ro route +--ro gateway-of-last-resort? string +--ro route-entry* [destination] | +--ro destination inet:ip-prefix | +--ro next-hop* [address] | | +--ro address inet:ip-address | | +--ro interface? dell:interface-name | | +--ro weight? uint32 | | +--ro route-type? enumeration | +--ro route-owner? enumeration | +--ro metric? uint32 | +--ro ag
+--ro if-oper-status? enumeration +--ro ip | +--ro address! | +--ro primary | | +--ro address? dell:ipv4-address-with-prefix | +--ro secondary* [address] | +--ro address dell:ipv4-address-with-prefix +--ro if-virtual-address? dell:ipv4-address-with-prefix +--ro if-broadcast-address? inet:ip-address +--ro if-address-input? enumeration +--ro if-ip-mtu? int32 +--ro protocols +--ro udp-helper* [helper] | +--ro helper inet:ip-address +--ro udp-broadcast? inet:ip-address +--ro directed-broadcast? boolean +--ro pr
Methods Supported: GET MAC Address Table Model +--ro mac-address-table +--ro count | +--ro dynamic-mac-count? uint32 | +--ro static-mac-count? uint32 | +--ro sticky-mac-count? uint32 | +--ro total-mac-in-use? uint32 +--ro aging-time? uint32 +--ro mac-vlan* [vlan-id] | +--ro vlan-id vlan-id | +--ro count | | +--ro dynamic-mac-count? uint32 | | +--ro static-mac-count? uint32 | | +--ro sticky-mac-count? uint32 | | +--ro total-mac-in-use? uint32 | +--ro mac-address-list* [mac-address] | +--ro mac-address yang
| | +--ro protocol? dell:ip-protocols-type | | +--ro source-type? pbr-address-types | | +--ro source-address? dell:ipv4-no-prefix | | +--ro source-mask? dell:ipv4-mask-or-prefix | | +--ro source-operator? ip-acl-operators | | +--ro source-port? uint32 | | +--ro source-start-port? uint32 | | +--ro source-end-port? uint32 | | +--ro destination-type? pbr-address-types | | +--ro destination-address? dell:ipv4-no-prefix | | +--ro destination-mask? dell:ipv4-mask-or-prefix | | +--ro destination-operator? ip-acl-o
Methods Supported: GET Port Mirroring Operational Model +--rw dell +--rw stats +--ro monitor-session [session-id source] +--ro session-id uint32 +--ro source dell:interface-name +--ro session-type? enumeration +--ro destination? dell:interface-name +--ro direction? enumeration +--ro mode? enumeration +--ro remote-vlan? dell:vlan-id-num +--ro rspan-session-type? enumeration +--ro source-ip? dell:ipv4-no-prefix +--ro destination-ip? dell:ipv4-no-prefix Static Access-list The following definition describes
+--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro filter-type? protocol? ip-protocol-number? src-ip-filter? source-ip-address? source-mask? src-operator? srcport? srcportrange? dest-ip-filter? dest-ip-address? destination-mask? dst-operator? dstport? dstportrange? ack? fin? psh? rst? syn? urg? count-type? egress-count-value? ingress-count-value? log? monitor? order? dscp? ecn? f
| +--ro fips-mode? boolean | +--ro boot-flash? string | +--ro memory-size? uint32 | +--ro temperature? int32 | +--ro voltage? voltage-status | +--ro serial-number? string | +--ro part-number? string | +--ro vendor-id? string | +--ro date-code? string | +--ro country-code? string | +--ro piece-part-id? string | +--ro ppid-revision? string | +--ro service-tag? string | +--ro express-service-code? string | +--ro auto-reboot? boolean | +--ro burned-in-mac? yang:phys-address | +--ro no-of-macs? uint32 +--ro powe
System Alarm Model +--ro alarms +--ro major-alarms [index] | +--ro index uint32 | +--ro alarm-description? string | +--ro duration? yang:timestamp +--ro minor-alarms [index] | +--ro index uint32 | +--ro alarm-description? string | +--ro duration? yang:timestamp +--ro alarm-thresholds [unit-number] +--ro unit-number uint32 +--ro minor? uint32 +--ro minor-off? uint32 +--ro major? uint32 +--ro major-off? uint32 +--ro shutdown? uint32 System Inventory The following definition displays the Inventory details: Mo
Methods Supported: GET System Version Model +--ro version-info +--ro os-ver? string +--ro sw-ver? string +--ro build-time? string +--ro build-path? string +--ro up-time? string +--ro image-name? string +--ro chassis-type? string +--ro processor-type? string +--ro flash-info? string +--ro card-info [index] | +--ro index uint32 | +--ro card-info-detail? string +--ro card-if-info [index] +--ro index uint32 +--ro card-if-info-detail? string VLAN The following definition is for displaying VLAN operations: Mod
Operational Data for IPv6 This section describes the method of fetching the IPv6 operational data. Interface Use the following definition to get the statistics of IPv6 Interface operational data.
+--ro flowlabel-zero +--ro label_value? boolean +--ro mld-host +--ro elapsed-time? dell:hour-minute-second +--ro valid-mld-pkts-received? yang:counter32 +--ro valid-mld-pkts-sent? yang:counter32 +--ro reports-received? yang:counter32 +--ro reports-sent? yang:counter32 +--ro leaves-sent? yang:counter32 +--ro mldv2-queries-received? yang:counter32 | +--ro mldv1-queries-received? yang:counter32 | +--ro errors-malformed-pkts? yang:counter32 +--ro neighbors* [ipv6-address] | +--ro ipv6-address dell:ipv6-address-
+--ro +--ro +--ro +--ro +--ro static-inactive? route-size-active? route-size-inactive? total-active-routes? total-inactive-routes? uint32 uint32 uint32 uint32 uint32 Prefix-list Use the following definition to get the IPv6 Prefix– list data: Module: PREFIX-LIST URI: /api/operational/dell/stats/ipv6/prefix-list Methods Supported: GET Prefix-List Model for IPv6 +--ro prefix-list +--ro last-deletion-insertion? dell:prefix-list-name +--ro prefix-list-name* [name] +--ro name dell:prefix-list-name +--ro
| +--ro state? enumeration | +--ro default-route? boolean | +--ro summary? boolean +--ro summary +--ro connected-active? uint32 +--ro connected-inactive? uint32 +--ro dynamic-active? uint32 +--ro dynamic-in-active? uint32 +--ro static-active? uint32 +--ro static-inactive? uint32 +--ro route-size-active? uint32 +--ro route-size-in-active? uint32 Management Information Base (MIB) Management Information Base (MIB) is a database of objects that can be monitored by a network management system.
| +--ro f10BgpM2VersionIndex uint32 | +--ro f10BgpM2VersionSupported? snmpv2-tc:TruthValue +--ro f10BgpM2SupportedCapabilitiesTable* [f10BgpM2SupportedCapabilityCode] | +--ro f10BgpM2SupportedCapabilityCode uint32 | +--ro f10BgpM2SupportedCapability? snmpv2-tc:TruthValue +--ro f10BgpM2PeerTable* [f10BgpM2PeerInstance f10BgpM2PeerLocalAddr f10BgpM2PeerRemoteAddr] | +--ro f10BgpM2PeerInstance uint32 | +--ro f10BgpM2PeerIdentifier? inet:ip-address | +--ro f10BgpM2PeerState? enumeration | +--ro f10BgpM2PeerStat
| +--ro f10BgpM2PeerCapAnnouncedValue? binary +--ro f10BgpM2PeerCapsReceivedTable* [f10BgpM2PeerIndex f10BgpM2PeerCapReceivedCode f10BgpM2PeerCapReceivedIndex] | +--ro f10BgpM2PeerIndex uint32 | +--ro f10BgpM2PeerCapReceivedCode uint32 | +--ro f10BgpM2PeerCapReceivedIndex uint32 | +--ro f10BgpM2PeerCapReceivedValue? binary +--ro f10BgpM2PrefixCountersTable* [f10BgpM2PeerIndex f10BgpM2PrefixCountersAfi f10BgpM2PrefixCountersSafi] | +--ro f10BgpM2PeerIndex uint32 | +--ro f10BgpM2PrefixCountersAfi mib:F10BgpM2
| +--ro f10BgpM2NlriPrefixLen inet-address:InetAddressPrefixLength | +--ro f10BgpM2AdjRibsOutIndex uint32 | +--ro f10BgpM2AdjRibsOutRoute? snmpv2-tc:RowPointer +--ro f10BgpM2PathAttrTable* [f10BgpM2PathAttrIndex] | +--ro f10BgpM2PathAttrIndex uint32 | +--ro f10BgpM2PathAttrOrigin? enumeration | +--ro f10BgpM2PathAttrNextHop? inet:ip-address | +--ro f10BgpM2PathAttrMedPresent? snmpv2-tc:TruthValue | +--ro f10BgpM2PathAttrMed? uint32 | +--ro f10BgpM2PathAttrLocalPrefPresent? snmpv2-tc:TruthValue | +--ro f10Bg
+--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro NetworkPrefix NetworkPrefixLen NextHopAddress StatusCode? BestRoute? PathSource? OriginCode? RouteFlapCount? RouteFlapDuration? ReuseDuration? AsPathString? inet:ip-address inet-address:InetAddressPrefixLength inet:ip-address enumeration snmpv2-tc:TruthValue enumeration enumeration uint32 yang:timeticks yang:timeticks snmp-framework:SnmpAdminString Forwarding Information Base (FIB) The following definition displays the properties of interf
Forwarding Plane Statistics Model +--ro mib +--ro fp-stats +--ro fp-stats-table* [stackUnitId] | +--ro stackUnitId int32 | +--ro rxHandle? int32 | +--ro numMsgHdr? int32 | +--ro numMsgBuf? int32 | +--ro numCluster? int32 | +--ro received? int32 | +--ro dropped? int32 | +--ro rxToNetwork? int32 | +--ro rxError? int32 | +--ro rxDatapathError? int32 | +--ro rxPktCOS0? int32 | +--ro rxPktCOS1? int32 | +--ro rxPktCOS2? int32 | +--ro rxPktCOS3? int32 | +--ro rxPktCOS4? int32 | +--ro rxPktCOS5? int32 | +--ro rxPkt
| +--ro inPktDroppedByFP? yang:counter64 | +--ro inL2L3Drops? yang:counter64 | +--ro inPortBitMapZeroDrops? yang:counter64 | +--ro inRxVLANDrops? yang:counter64 | +--ro inFCSDrops? yang:counter64 | +--ro inMTUExceeds? yang:counter64 | +--ro mmuHoldDrops? yang:counter64 | +--ro mmuTxPurgeCellErr? yang:counter64 | +--ro mmuAgedDrops? yang:counter64 | +--ro egressFCSDrops? yang:counter64 | +--ro egIPv4L3UCAgedDrops? yang:counter64 | +--ro egTTLThresholdDrops? yang:counter64 | +--ro egInvalidVLANCounterDrops? y
+--ro ifOperStatus? enumeration +--ro ifLastChange? yang:timeticks +--ro ifInOctets? yang:counter32 +--ro ifInUcastPkts? yang:counter32 x--ro ifInNUcastPkts? yang:counter32 +--ro ifInDiscards? yang:counter32 +--ro ifInErrors? yang:counter32 +--ro ifInUnknownProtos? yang:counter32 +--ro ifOutOctets? yang:counter32 +--ro ifOutUcastPkts? yang:counter32 x--ro ifOutNUcastPkts? yang:counter32 +--ro ifOutDiscards? yang:counter32 +--ro ifOutErrors? yang:counter32 x--ro ifOutQLen? yang:gauge32 x--ro ifSpecific? yang
Methods Supported: GET, PATCH, and PUT IETF Interface Model +--rw interfaces +--rw interface [name] +--rw name +--rw description? +--ro type? +--ro location? +--rw enabled? +--ro if-index? +--rw mtu? +--rw link-up-down-trap-enable? +--rw rate-interval? string string ianaift:iana-if-type string boolean int32 uint32 enumeration uint32 REST API Framework to Execute the CLIs REST CLI is an alternative approach for Telnet and SSH to send the Dell Networking OS commands to the system.
Samples of the config-command Following is the sample output of CONFIG command: To configure an IP address: Input.xml: interface vlan 100\r\n ip address 1.2.3.4/24 curl -u demo:demo -X POST -T Input.xml http://:8008/api/running/dell/ _operations/cli
Dell# Samples of the show-command Following is the sample output of SHOW command: Input.xml: version curl -u demo:demo -X POST -T Input.xml http://:8008/api/running/dell/ _operations/cli
12 REST API CLI The REST API CLI commands are supported on the S4810, S4820T, S5000, S6000, S6000–ON, Z9000, and Z9500 platforms. rest-server Enable the REST API service over a non-secure or secure HTTP. S4810, S4820T, S5000, S6000, S6000–ON, Z9000, and Z9500 Syntax rest-server {http | secure-http} To disable the REST API over a non-secure or secure HTTP request, use the no rest-server {http | secure-http} command. Parameters http Enable the REST API on HTTP (Port: 8008).
crypto cert generate Generate a self-signed certificate and key files, if exists, and replace them with the newly generated files.
Command Modes EXEC Command History This guide is platform-specific. For command information about other platforms, refer to the relevant Dell Networking OS Command Line Reference Guide. The following is a list of the Dell Networking OS version history for this command. Usage Information Version Description 9.7(0.0) Introduced on the S6000–ON. 9.6(0.0) Introduced on the S Series and Z Series switches.
show crypto cert Display the certificate information. S4810, S4820T, S5000, S6000, S6000–ON, Z9000, and Z9500 Syntax show crypto cert {rest-server |file-name} Command Mode EXEC Parameters rest-server Enter the keyword rest-server to display the certificate information installed for rest service. file-name Enter the filename with full path to display the certificate information. Command Modes EXEC Command History This guide is platform-specific.
show ip rest-server Display the status of the configured rest-server (HTTP or Secure HTTP). S4810, S4820T, S5000, S6000, S6000–ON, Z9000, and Z9500 Syntax show ip rest-server Defaults none Command Modes EXEC Privilege Command History This guide is platform-specific. For command information about other platforms, refer to the relevant Dell Networking OS Command Line Reference Guide. The following is a list of the Dell Networking OS version history for this command. Version Description 9.7(0.
13 Web Server with HTTP Support You download web server with HTTP support with the SmartScripts package. It is supported on the S4810, S4820T, S5000, Z9000, and MXL switch platforms. For more information, refer to Download the Smart Scripting Package. Starting the Web Server In the Open Automation package, the web server runs on a switch and handles HTTP and HTTPS requests. You can start the web server in a non-secure (HTTP) or secure (HTTPS) mode.
