Dell Networking Open Automation Guide 9.11(0.
Notes, cautions, and warnings NOTE: A NOTE indicates important information that helps you make better use of your product. 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 © 2016 Dell Inc. or its subsidiaries. All rights reserved. Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries.
Contents 1 About this Guide.............................................................................................................................................9 Audience..............................................................................................................................................................................9 Open Automation Features and Supported Platforms ................................................................................................
Script Examples............................................................................................................................................................... 29 BMP Operations on Servers Overview.........................................................................................................................33 Configuring the DHCP Server Settings..................................................................................................................
Puppet Agent Configuration Scripts............................................................................................................................. 67 puppet-config.............................................................................................................................................................67 puppet-show..............................................................................................................................................................
package clear-all.............................................................................................................................................................. 92 package install.................................................................................................................................................................. 93 package uninstall.......................................................................................................................................
show packages................................................................................................................................................................ 131 show virtualswitch..........................................................................................................................................................133 show vmmap....................................................................................................................................................
System Alarm............................................................................................................................................................ 178 System Inventory..................................................................................................................................................... 179 System Version.........................................................................................................................................................
1 About this Guide This document describes the components and uses of the Open Automation Framework designed to run on the Dell Networking operating system (OS).
Platform Bare Metal Provisioning (BMP) Open Management Interface (OMI) Puppet Smart Scripts Virtual Server Networking (VSN) Representatio nal State Transfer Application Programming Interface (REST API) Web Server S4048T–ON Y Y Y Y N Y Y S5000 Y Y Y Y Y Y Y S6000 Y Y Y Y N Y Y S6000–ON Y Y Y Y N Y Y S6100–ON Y Y Y Y N Y Y S6010–ON Y Y Y Y N Y Y Z9500 Y Y Y Y N Y Y MXL Y N Y Y Y N Y IOA Y N Y Y N N N S3100 Series Y N N Y N N
Platform S4048–ON S4048T–ON S3048–ON S5000 S6000 S6000–ON S6010–ON MXL Switch Z9500 C9010 Related Documents • Dell Networking Installation Guide for the S4820T System • Dell Networking OS Command Line Reference Guide for the S4048–ON System • Dell Networking OS Configuration Guide for the S4048–ON System • Dell Networking Installation Guide for the S4048–ON System • Dell Networking OS Command Line Reference Guide for the S4048T–ON System • Dell Networking OS Configuration Guide for the
Platform Related Documents S3100 Series • (S3124P, S3148, S3148P, S3124F, and • S3124) • Z9100–ON Dell Networking platform and OS 12 Dell Networking OS Command Line Reference Guide for the S3100 Series Dell Networking OS Configuration Guide for the S3100 Series Dell Networking Installation Guide for the S3100 System • Dell Networking OS Command Line Reference Guide for the Z9100–ON System • Dell Networking OS Configuration Guide for the Z9100–ON System • Dell Networking Installation Guide for the
2 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. The Dell Networking S4810, S4820T, S3048–ON, S3100 Series, S4048–ON, S4048T–ON, S5000, S6000, S6000-ON, S6010–ON, S6100–ON, Z9500, Z9100–ON, MXL, M IOA, and FN IOM platforms support the Open Automation framework.
NOTE: The Open Automation framework is seen as Open Automation in the rest of this document. Topics: • Bare Metal Provisioning • Smart Scripting • Virtual Server Networking • REST API • Web Server Bare Metal Provisioning Bare metal provisioning (BMP) provides the following features.
Virtual Server Networking Virtual server networking (VSN) provides the following: • Automatic re-provisioning of virtual local area networks (VLANs) when you migrate virtual machines (VMs). • Support for multiple hypervisors, such as VMware and Citrix XenServer. To ensure that network connectivity, quality of service (QoS), and security policies are maintained when you migrate VMs, virtual data centers require a dynamic network infrastructure.
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, S3048–ON, S3100 Series, S4048–ON, S5000, S6000, S6000-ON, S6010–ON, S6100–ON, Z9100–ON, Z9500, C9010, IOA, and MXL platforms.
Industry Standard Upgrades with BMP Dell Networking OS follows the Industry Standard Upgrades with BMP. Following are the steps to perform the upgrade process: 1 The chassis loads in BMP mode. 2 The BMP_BOOT is a special variable in Nonvolatile Random Access Memory (NVRAM) for Industry Standard Upgrade during BMP BOOT process. 3 The BMP_BOOT variable in NVRAM validates the presence of BOOT configuration.
• Switch access through all ports (management and user ports) with or without the DHCP-based dynamic IP address configuration of a switch. • Booting up in Layer 3 mode with interfaces already in No Shutdown mode and basic protocols enabled to protect the system and network. • Access to the configuration file or a pre–configuration script using the DHCP offer. • Download and execute scripts before configurations are applied, allowing pre–configuration checks on the switch.
BMP Mode In BMP mode, there are two types of contexts: factory-default context and normal context. Factory-Default Context BMP is enabled with the default parameters (no dhcp-timeout and config-scr -download). In this context, you cannot enter CLI commands. By default, the BMP syslog messages are disabled. When BMP is about to start, the following message displays: This device is configured to enter Bare Metal Provisioning (BMP).
NOTE: To apply the startup configuration, cancel the default BMP setup using the stop bmp command from the console. To disable BMP for the next reload, use the boot-type normal-reload command in reload-type configuration mode. Normal Mode When reloaded in Normal mode, the switch boots up with the management port in No Shutdown mode. If the management IP address is present in the start-up configuration file, it is assigned to the management interface.
NIL sname NIL dns IP NIL router IP NIL. 00:02:27: %STKUNIT0-M:CP %BMP-5-BMP_BOOT_OFFER: DHCP image file tftp://13.4.4.1/ftos-img-s4810. 00:02:27: %STKUNIT0-M:CP %BMP-5-BMP_BOOT_OFFER: DHCP config file scp://anvltest:force10@13.4.4.1//tftpboot/basic-l3. 00:02:27: %STKUNIT0-M:CP %BMP-5-BMP_BOOT_OFFER: stacking info NIL. 7 The system sends a message to the server to retrieve the named configuration file or pre–configuration script and/or boot file from the base directory of the server.
b • 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.sha256 and not filename.md5. If filename.sha256 is present, it uses SHA256 validation or the image downloads without SHA256 validation.
Reload with a DHCP Server Offer Without a Dell Networking OS Offer You configure the switches to reload in BMP mode. If the switches reach a DHCP server but do not locate a downloadable Dell Networking OS image file on the server, they attempt to download the configuration file. 1 The system boots up with the BMP application. 00:02:26: %STKUNIT0-M:CP %BMP-5-BMP_DHCP_OFFER: DHCP OFFER received on Te 0/21 IS SELECTED. 00:02:26: %STKUNIT0-M:CP %BMP-5-BMP_REQUEST: DHCP REQUEST sent on Te 0/21.
Te 0/21. 00:02:26: %STKUNIT0-M:CP %BMP-5-BMP_BOOT_OFFER: DHCP acquired IP 13.4.4.44 mask 255.255.255.0 server IP 13.4.4.1. 00:02:26: %STKUNIT0-M:CP %BMP-5-BMP_BOOT_OFFER: DHCP tftp IP NIL sname NIL dns IP NIL router IP NIL. 00:02:27: %STKUNIT0-M:CP %BMP-5-BMP_BOOT_OFFER: DHCP image file tftp://13.4.4.1/ftos-img-s4810. 00:02:27: %STKUNIT0-M:CP %BMP-5-BMP_BOOT_OFFER: DHCP config file NIL. 00:02:27: %STKUNIT0-M:CP %BMP-5-BMP_BOOT_OFFER: stacking info NIL.
If a pre–configuration script file downloads successfully, the following SYSLOGs display: 00:03:07: %STKUNIT0-M:CP %BMP-2-BMP_DOWNLOAD_START: The config file download has started. 00:03:19: %STKUNIT0-M:CP %BMP-5-BMP_DWNLD_FILE_IS_SCRIPT_FILE: The downloaded file is a script file. 00:03:19: %STKUNIT0-M:CP %BMP-5-BMP_DWNLD_CONFIG_SCRIPT_SUCCESS: The config/script file download is successful. 00:03:21: %STKUNIT0-M:CP %BMP-5-BMP_PRE_CONFIG_SCRIPT_BEGIN: The Pre-Config Script has started to Execute.
• The circuit ID identifies the port originating the protocol data unit (PDU) and has the interface details. • The remote ID is configurable between the switch MAC address, the hostname, or a custom string. To set the remote ID, enable the relay up-front in reload-type sub mode. If you enable the relay, by default, the remote ID is set to MAC address.
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 ...
7 The pre–configuration script can access Dell Networking OS CLI commands through the clido utility. The clido utility has no pagination, is always set to terminal length 0, and has Dell Networking OS CLI privilege 15 enabled. It works in the following modes: 8 • Continuous mode (clido command) — use to retain the Dell Networking OS context. • Reset mode (clido -r command) — use to reset the CLI command to its original context.
• If the script returns a non-zero value (indicating a failure), the configuration file does not load in the system. Debug it manually and reload the system with the corrected script. If the autoexec script fails, the system syslog displays: 00:00:34: %STKUNIT1-M:CP %BMP-5-AUTOEXE_FAILURE: The AutoExec Script execution returned Failure.
The following line indicates the start of the auto-execution script. Script is Started. 00:00:19: %STKUNIT1-M:CP %CHMGR-5-CHECKIN: Checkin from Stack unit 1 (type S4810, 64 ports) 00:00:20: %00:00:20: %STKUNIT1-M:CP %CHMGR-0-PS_UP: Power supply 0 in unit 1 is up 00:00:20: %STKUNIT1-M:CP %CHMGR-5-STACKUNITUP: Stack unit 1 is up 00:00:21: %STKUNIT1-M:CP %CHMGR-5-SYSTEM_READY: System ready 00:00:21: %STKUNIT1-M:CP %RAM-5-STACK_STATE: Stack unit 1 is in Active State.
Pre-configuration Script – BMP Mode #! /usr/bin/expect #/DELL-NETWORKING # Execute F10do and Print proc print_f10do {cmd_str} { set str [exec f10do "$cmd_str"] set tmp_str [string map {\n \r\n} $str ] puts $tmp_str } set ftp_ip "20.0.0.1" set ftp_username "lab" set ftp_passwd "lab" set config_file "s4810-10-startup-config" set post_conf "s4810-10-post-config.exp" puts "Executing Pre-Config Script !!!!\r\n" exec rm -rf "$config_file" exec rm -rf "$post_conf" puts "Downloading Startup Config and Post-Config S
puts $tmp_str } # Interfaces Configurations set interface_list_slot [list "0/1" "0/5" "0/9"] set interface_list [list "Te 0/1" "Te 0/5" "Te 0/9"] set {remote_intf(Te 0/1)} "TenGigabitEthernet 0/1" set {remote_intf(Te 0/5)} "TenGigabitEthernet 0/5" set {remote_intf(Te 0/9)} "TenGigabitEthernet 0/9" set hostname "S4810-10" set max_min 10 set status_file "s4810-10-current-status.dat" set ftp_ip "20.0.0.1" puts [exec rstimer 30] puts "\r\nReset Timer Complete\r\n" # Open Staus File set fp [open $status_file w]
$remote_intf($intf_slot)\r\n" } else { puts "ERROR: Interface $intf_slot is Not Connected to Interface $remote_intf($intf_slot)\r\n" puts $fp "ERROR: Interface $intf_slot is Not Connected to Interface$remote_intf($intf_slot) \r\n" puts "LLDP Output for $intf_slot :\r\n $result_str \r\n" puts $fp "LLDP Output for $intf_slot :\r\n $result_str \r\n" } continue } # Wait for 1 minute puts "Interface is Not Connected\r\n" puts "Wait for 1 min for the Neighbor to come-up\r\n" after [expr {60 * 1000}]incr min } if
DHCP Server To configure the DHCP server use the following information. 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, see 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 re-initiates. 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).
For example, on a DHCP3 server, you can configure the assignment of a fixed MAC-based IP address and configuration file by entering the following lines of configuration parameters in the dhcpd.conf file on the server: host S4810 { hardware ethernet 00:01:e8:81:e2:39; fixed-address 20.0.0.48; option configfile "customer.
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.23. String (Set the mac/hostname/custom-string as remote-id option in DHCP offer option 82) 1.
4 Bare Metal Provisioning CLI Bare metal provisioning commands are supported on the S4810, S4820T, S3048–ON, S3100 series, S4048–ON, S4048T–ON, S5000, S6000, S6000–ON, S6010–ON, S6100–ON, Z9100–ON, Z9500, C9010, 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.
auto-save Allows you to configure the auto save option for the downloaded configuration or script file which are not saved by default. S4810, S4820T, S3048–ON, S3100 series, S4048–ON, S4048T–ON, S5000, S6000, S6000–ON, S6010–ON, S6100– ON, Z9100–ON, Z9500, C9010, IOA, and MXL Syntax auto-save { enable | disable } To reset the auto-save option, use the no auto-save { enable | disable } command. Parameters enable Enable the option to save the downloaded configuration or script file.
bmp logging Configures the syslog messages in a console while BMP is running. S4810, S4820T, S3048–ON, S3100 series, S4048–ON, S4048T–ON, S5000, S6000, S6000–ON, S6010–ON, S6100– ON, Z9100–ON, Z9500, C9010, and MXL Syntax Parameters bmp logging {enable | disable} enable Enables the syslog messages in the console while BMP is running. disable Disables the syslog messages in the console while BMP is running. Defaults none Command Modes EXEC Command History This guide is platform-specific.
boot-type Allows you to configure the reload type. S4810, S4820T, S3048–ON, S3100 series, S4048–ON, S4048T–ON, S5000, S6000, S6000–ON, S6010–ON, S6100– ON, Z9100–ON, Z9500, C9010, IOA, and MXL Syntax boot-type { bmp-reload | normal-reload } To reset the boot-type mode, use the no boot-type { bmp-reload | normal-reload } command. Parameters bmp-reload Reloads the system in BMP mode.
config-scr-download Allows you to specify whether the configuration or script file needs to be downloaded. S4810, S4820T, S3048–ON, S3100 series, S4048–ON, S4048T–ON, S5000, S6000, S6000–ON, S6010–ON, S6100– ON, Z9100–ON, Z9500, C9010, IOA, and MXL Syntax config-scr-download { enable | disable } To reset the download option, use the no config-scr-download { enable | disable } command.
• show reload-type — displays the current Reload mode (BMP mode or Normal mode). dhcp-timeout Allows you to configure the DHCP timeout limit. S4810, S4820T, S3048–ON, S3100 series, S4048–ON, S4048T–ON, S5000, S6000, S6000–ON, S6010–ON, S6100– ON, Z9100–ON, Z9500, C9010, 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.
relay Allows you to configure the addition of option 82 in DHCP client packets. S4810, S4820T, S3048–ON, S3100 series, S4048–ON, S4048T–ON, S5000, S6000, S6000–ON, S6010–ON, S6100– ON, Z9100–ON, Z9500, C9010, 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.
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.
Usage Information Version Description 8.3.19.0 Introduced on the S4820T. To upgrade any NVRAM changes to the chassis caused by the following CLI commands, use the reload conditional nvram-cfg-change command on a switch running BMP. • stack-unit {unit} stack-group • stack-unit {unit} port {fanout-portid} portmode quad • asf-mode • cam-acl • buffer-profile reload-type Allows you to configure the reload-type options in reload-type sub command mode.
Related Commands Version Description 9.2(0.0) Introduced on the MXL Switch. Updated the parameters for S4810, S4820T, and Z9000. 9.1(0.0) Updated the command mode from EXEC Privilege to GLOBAL CONFIGURATION. Updated the parameter from jumpstart to bmp. Added support for the configscr-download and user-defined-string commands. Supported platforms are S4810, S4820T, and Z9000. 9.0.2.0 Introduced on the S6000. 9.0.0.0 Introduced in Z9000. 8.3.19.0 Introduced on the S4820T. 8.3.1.
Related Commands Version Description 9.8(2.0) Introduced on the S3100 series. 9.8(1.0P1) Introduced on the Z9100–ON. 9.8(0.0P5) Introduced on the S4048–ON. 9.8(0.0P2) Introduced on the S3048–ON. 9.7(0.0) Introduced on the S4810, S4820T, S5000, S6000, S6000–ON, Z9000, Z9500, IOA, and MXL. • reload-type — allows you to configure the reload-type options in reload-type sub command mode. • show reload-type — displays the current Reload mode (BMP mode or Normal mode).
Version Description 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 and S4820T. 9.1(0.0) Introduced on the Z9000 and S4810. show boot bmp Displays the current state of the BMP process.
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.1 Routers = NIL *********************************** ... BMP State : Downloading image boot_file.bin from 25.1.1.1 ... BMP State : Image boot_file.
Example 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)# Related Commands • reload-type — allows you to configure the reload-type options in reload-type sub command mode.
Usage Information Version Description 9.10(0.0) Introduced on the S6100–ON. 9.9(0.0) Introduced on the C9010. 9.8(2.0) Introduced on the S3100 series. 9.8(1.0P1) Introduced on the Z9100–ON. 9.8(0.0P5) Introduced on the S4048–ON. 9.8(0.0P2) Introduced on the S3048–ON. 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.
stop bmp To prevent an infinite loop, stop the switch from reloading in BMP mode. S4810, S4820T, S3048–ON, S3100 series, S4048–ON, S4048T–ON, S5000, S6000, S6000–ON, S6010–ON, S6100– ON, Z9100–ON, Z9500, C9010, 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, see the relevant Dell Networking OS Command Line Reference Guide.
The stop bmp command behaves differently in different circumstances: • While the Dell Networking OS image upgrade is in progress, it aborts the BMP process after the Dell Networking OS image upgrades. • When applying configurations from the file, it aborts the BMP process after all the configurations are applied in the system. • When running the pre-configuration or post-configuration script, it stops the script and aborts the BMP process immediately.
Related Commands Version Description 9.8(0.0P5) Introduced on the S4048–ON. 9.8(0.0P2) Introduced on the S3048–ON. 9.7(0.0) Introduced on the S4810, S4820T, S5000, S6000, S6000–ON, Z9000, Z9500, IOA, and MXL. • reload-type — allows you to configure the reload-type options in reload-type sub command mode. • show reload-type — displays the current Reload mode (BMP mode or Normal mode).
Usage Information Version Description 9.8(0.0P2) Introduced on the S3048–ON. 9.7(0.0) Introduced on the IOA and S6000–ON. 9.6(0.0) Introduced on the S5000. 9.5(0.0) Introduced on the S4810, S4820T, S6000, Z9000, and Z9500.
5 Open Management Infrastructure Dell Networking OS supports the Open Management Infrastructure (OMI) framework. OMI is supported on the S4810, S4820T, S3048– ON, S4048–ON, S4048T–ON, S5000, S6000, S6000–ON, S6010–ON, S6100–ON, Z9100–ON, and Z9500 platforms. Overview OMI is an open source package which manages infrastructure components such as servers, storage, and networking.
2 Create a user, with the user privilege 15, where this user can configure the box from the management station through OMI. 3 Install the smartscript package. For detailed information, see the Installing SmartScripting section of the Smart Scripting chapter. 4 Install the OMI package. EXEC Privilege mode package install “tftp:///OMI-I-9.11.0.0.tar.gz” 5 Enable the REST API.
The argument options are: • start — start OMI server • stop — stop the OMI server • client-test — testing the OMI server using OMI client • get-mof — copy DellNetworkingDSC.zip files to /flash directory • install-cert — install the given SSL certificates to OMI server • server-opt[options] — invoke omi-server with the given options directly omi-server-show To view the OMI server status, use the omi-server-show script.
4 To communicate from Windows server, configure the user with privilege level 15. Default user is admin. 5 Install the DellNetworking DSC module. • Unzip the DellNetworkingDSC.zip file and place it in one of the paths available in $env:PSModulePath or add the folder to the $env:PSModulePath. For additional information, see https://msdn.microsoft.com/en-us/library/dd878326(v=vs. 85).aspx. In the Windows PowerShell environment, create the configuration block.
Import-DscResource -Name MSFT_NetworkDevice_EthernetPortView Node ("") { MSFT_NetworkDevice_EthernetPortView MyPort { PortId = "tengig-0-11" Description = "Interface connecting to S4810" } } } MSFT_NetworkDevice_EthernetPortViewConfig -OutputPath c:\EthernetPortViewMof The MOF for the node gets stored in the path C:\EthernetPortViewMof. NOTE: Save the PowerShell commands in a file with an extension .ps1 (PowerShell Script) and execute. Push the configuration. PS C:\> Start-
Classes and Schema Implementation This section lists the implementation of classes and schema in OMI.
Cmdlets Description Version Support Restore-DscConfiguration Reapplies the previous configuration for the node. 4.0 and 5.0 Stop-DscConfiguration Stops a configuration job that is running. 4.0 and 5.0 Test-DscConfiguration Tests whether the actual configuration on the nodes matches the desired configuration 4.0 and 5.0 SetDscLocalConfigurationManager Applies Local Configuration Manager settings to nodes. 4.0 and 5.0 Start-DscConfiguration Applies configuration to nodes. 4.0 and 5.
6 Puppet Dell Networking OS supports the Puppet automation framework. Puppet Agent is supported on the S4810, S4820T, S3048–ON, S4048– ON, S4048T–ON, S5000, S6000, S6000–ON, S6010–ON, S6100–ON,Z9100–ON, , Z9500, MXL, and FN IOM 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.
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 Configure the username, password, and privilege for puppet. CONFIGURATION mode username puppet password puppet privilege 15 NOTE: Puppet supports only the username puppet for any puppet configurations.
Puppet Agent Configuration Scripts This section describes 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.
} } 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. node dell_s4810_node1 { netdev_device { hostname: } netdev_lag { "name": ensure => (present | absent), active => (true | false), links => ('interface-name' | ['interface-name1', 'interface-name2' ...
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.
7 Smart Scripting Smart Scripting is supported on the S4810, S4820T, S3048–ON, S3100 Series, S4048–ON, S4048T–ON, S5000, S6000, S6000–ON, S6010–ON, S6100–ON, Z9100–ON, Z9500, C9010, and MXL switch platforms. Smart Scripting is not supported on the M IOA and FN IOM platforms. Smart Scripting allows you to add functionality to Dell Networking switches without updating the Dell Networking OS release.
With Smart Scripting, you don’t need to learn proprietary scripting languages; allowing for faster development and deployment of custom scripts. Smart Scripting also offers solutions in a UNIX environment useful to cloud administrators who are familiar with working in a UNIX shell. Smart Script support in a UNIX environment allows you to invoke standard UNIX utilities like netstat, tcpdump, ls, chmod, chown, and so on.
• Python interpreter and associated files. • Ruby interpreter and associated files. • SQLlite database and Perl, Python, Ruby, TCL interface to SQLite. • NetSNMP client and Perl, Python, Ruby interface to the client. • Expanded set of UNIX utilities. • Web-Server with HTTP support (see Web Server with HTTP Support). Installing Smart Scripting After you download the Smart Scripts package, install the file from local flash memory on a switch or from an external drive on a network server.
Displaying Installed Packages To view the Open Automation packages currently installed on a switch, including version numbers and content, use the following commands. • View package information. EXEC Privilege mode show packages show packages system Uninstalling SmartScripts Uninstalling the SmartScripts package removes it from the internal flash memory. CAUTION: Before you uninstall the Smart Scripting package, stop all scripts that are running using the no script scriptname command.
set fileId [open $filename "a+"] switch $env(DELL_TRGEVT_TYPE) { "TIME EVENT" { set data "Sending Mail : The triggered Event $env(DELL_TRGEVT_NAME) is Time Event - Reload Started" } "LOG EVENT" { set data "Sending Mail : Triggered Event is $env(DELL_TRGEVT_NAME) BPDU Guard Initiated , Port will recover once it is out of Error Disable State \n" set data [concat $data "Attching the Log Message : $env(DELL_TRGEVT_LOGMSG)"] } "CPU" { set data "Sending Mail : Triggered Event is $env(DELL_TRGEVT_NAME) CPU Limits
Sample script for clido in ZSH #/usr/bin/zsh clido –r "configure terminal" clido "interface vlan 10" clido "no shutdown" clido “name MailServer_Vlan” exit 0 #usage of –r is to forcefully go to exec mode dellsh To parse a list of commands line by line in any given text file and configure it on the device, use the dellsh system command. Syntax: dellsh Sample script for dellsh in Python #! /usr/pkg/bin/python import os os.system("dellsh '/usr/pkg/ss-scripts/dellsh.
• 3 — error • 4 — warning • 5 — notify • 6 — infor • 7 — debug The default severity level is 6. Sample script for dellsyslog in Python #! /usr/pkg/bin/python import sys import os print sys.argv[1] os.system("dellsyslog -s %s 'The Syslog is generated by python'" %(sys.argv[1])) Sample script for dellsyslog in Python for S3100 Series #! /f10/flash/pkg/usr/pkg/bin/python import sys import os print sys.argv[1] os.system("dellsyslog -s %s 'The Syslog is generated by python'" %(sys.
Sample script for Perl using DellExec, DellCli, and DellConfig #! /usr/pkg/bin/perl #importing DellSSUtils require "/usr/pkg/scripts/DellSSUtils/DellSmartUtils.pl"; #Assigning Value to the vairable which is used as an argument to the #dell library functions $cli = "show version"; $script = "/usr/pkg/scripts/sample_scripts/sum.py"; $args = "1 2 3"; $ExtraArgs = "10"; @list = ("interface vlan $ARGV[0]", "no shutdown", "ip address $ARGV[0].$ARGV[0].$ARGV[0].
for input1 in sys.argv[1:]: print DellSmartUtils.DellCliConfig(["%s" %str("interface vlan %s" %str(input1) ) , "no shutdown"]) arg_val="" for b in sys.argv[1:] : arg_val=arg_val+" %s" %(b) print DellSmartUtils.DellExec("loopback.zsh" , arg_val) f = DellSmartUtils.DellCli("show version") fh = open("/f10/flash/Dellcli.txt", "w") fh.writelines(f) fh.close() For instructions about how to run a Perl, Python, or Ruby script from the Dell Networking OS CLI, see Scheduling Time / Event-based Scripts.
Limits on System Usage To restrict CPU and memory usage, Smart Scripting establishes limits on system processes for the following attributes (regardless of the user-privilege level or scripting method). Table 4. Limits on System Attributes System Attributes Value Description cputime unlimited Maximum amount of time a process uses. filesize unlimited Largest file size (in bytes) that can be created.
UNIX Utility Function cat Concatenate and print files. chmod Change file modes. 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.
UNIX Utility Function 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/ssscripts. For S3100 series, the storage location is /f10/flash/pkg/ss-scripts. Network File System (NFS) A Network File System (NFS) allows you to mount the file systems over a network and locally interact with those file systems.
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[..
Following example shows the event triggering the script after the cpu-usage reaches 30%: Dell(conf)#script trigger-event event1 cpu-usage 30 Following example shows how you can define the event to trigger a script when a SYSLOG event with the OSTATE_UP pattern occurs: Dell(conf)#script trigger-event Port_State_Event log-event tag tag-regex "OSTATE.
003 EXEC Dell# Scheduled user2 args.pl hi The script status are determined as follows: • Scheduled — The script is scheduled to run. • Running — The script is currently running. • Stopped — The script is suspended. • Completed — The script run is successful and exits normally. • Watch Blocked — The script is monitored but terminates within ten minutes. • SSMGR-Stopped — Dell Networking OS stops the script by itself, if the cpu/disk-io/mem goes beyond the threshold.
• Display a list of scripts that are scheduled or running. To display the detailed status of the scripts, enter detail. EXEC Privilege mode show script process [detail] • Display a list of supervised scripts that are scheduled or running. To display the detailed status of the supervised scripts, enter detail.
CONFIGURATION mode script [username name] script-path [script-parameter script-parameter ...] For script-path, enter the directory path and filename. (Optional) For username name, enter the user name whose read-write privileges are applied when the script runs. A username running scripts cannot contain special characters. (Optional) For script-parameter, enter the values of up to three parameters to be applied when the script runs.
8 Smart Scripting CLI Smart Scripting is supported on the S4810, S4820T, S3048–ON, S3100 Series, S4048–ON, S4048T–ON, S5000, S6000, S6000–ON, S6010–ON, S6100–ON, Z9100–ON, Z9500, C9010, and MXL platforms. Smart Scripting is not supported on the M IOA, FN IOA, and FN IOM platforms.
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. For command information about other platforms, see 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.10(0.1) Introduced on the S4048T–ON and S6010–ON. 9.10(0.0) Introduced on the S3100 Series and S6100–ON. 9.9(0.
Version Description 9.10(0.0) Introduced on the S3100 Series and S6100–ON. 9.9(0.0) Introduced on the C9010. 9.8(1.0P1) Introduced on the Z9100–ON. 9.8(0.0P5) Introduced on the S4048–ON. 9.8(0.0P2) Introduced on the S3048–ON. 9.7(0.0) Introduced on the S4810, S4820T, S5000, S6000, S6000–ON, Z9000, Z9500, and MXL. mount nfs Share the network file system the local Dell Networking OS file system uses.
Usage Information Version Description 9.8(0.0P2) Introduced on the S3048–ON. 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.
Version Description 9.9(0.0) Introduced on the S4810, S4820T, S3048–ON, S3100 Series, S4048–ON, S5000, S6000, S6000–ON, Z9100–ON, Z9500, C9010, and MXL. package install Installs the Smart Scripting package. This command downloads the package from the specified location and installs it in the internal flash memory on a switch.
Usage Information Version Description 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. Because installing an Open Automation package may take time, the installation performs in the background when the download finishes. A message displays on the console when the installation is complete. To follow the progress of a package installation, use the show packages command.
Usage Information Version Description 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. CAUTION: Before you uninstall the Smart Scripting package, first stop all scripts that are running using the no script script-name command.
Defaults none Command Modes CONFIGURATION Command History This guide is platform-specific. For command information about other platforms, see 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.10(0.1) Introduced on the S4048T–ON and S6010–ON. 9.10(0.0) Introduced on the S3100 Series and S6100–ON. 9.9(0.0) Introduced on the C9010. 9.8(1.
script (stop/resume/clear/kill/unschedule) Stops, resumes, clears, kills, or unschedules an Expect, Perl, Python, Ruby, Tcl, UNIX, and ZSH shell script from the Dell Networking OS CLI. S4810, S4820T, S3048–ON, S3100 Series, S4048–ON, S4048T–ON, S5000, S6000, S6000–ON, S6010–ON, S6100– ON, Z9100–ON, Z9500, C9010, and MXL Syntax Parameters script {stop | resume | clear | kill | unschedule} {script-name script-name | job-id job-id | all} stop Enter the keyword stop to stop a script from being run.
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.
script execute (EXEC mode) Schedules the scripts from EXEC mode either to run in foreground or background. S4810, S4820T, S3048–ON, S3100 Series, S4048–ON, S4048T–ON, S5000, S6000, S6000–ON, S6010–ON, S6100– ON, Z9100–ON, Z9500, C9010, and MXL Syntax script execute script-name [start {at | date-time | after time}] [stop {at date-time | after time}] [bg] [arguments arg[..arg]] [username username] To cancel, use the script unschedule command.
Usage Information Example Version Description 9.9(0.0) Introduced on the C9010. 9.8(1.0P1) Introduced on the Z9100–ON. 9.8(0.0P5) Introduced on the S4048–ON. 9.8(0.0P2) Introduced on the S3048–ON. 9.7(0.0) Introduced on the S4810, S4820T, S5000, S6000, S6000–ON, Z9000, Z9500, and MXL. 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 Switch.
start after date-time (Optional) Enter the keywords start after then the time in [HHHH:] MMMM format to start running the script after a set time. stop at datetime (Optional) Enter the keywords stop at date-time with the time and date either in HH:MM-MM/DD/YY format to stop running 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.
• 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 Copies a script to a switch.
• SCP: Copy from the remote file system using SCP (scp://userid:password@hostip/filepath) • FTP: Copy from the remote file system using FTP (tftp://hostip//filepath) The downloaded files are stored into a dedicated folder (/usr/pkg/ss-scripts). For S3100 series, the dedicated folder path is /f10/flash/pkg/ss-scripts. NOTE: For stack systems, the script from ss-scripts synchronizes across the stack for every one hour.
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. Usage Information The path can contain a network file system (NFS) mounted directory (see the mount nfs command). The path is added to a script search list allowing the system to search all locations for the script name. If the script is in multiple locations, the system uses the first instance of the script found.
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. This command removes the files from the dedicated folder /usr/pkg/ss-scripts on the switch. script trigger-event Configures the event that causes the script to run.
time-event stop at datetime Enter the keyword stop at then the time and date either in HH:MM — MM/DD/YY format to stop the trigger event at the specified time and date or in HH:MM format to begin the trigger event at the specified time on the same day (if the mentioned time is elapsed, the event runs on the next day HH:MM mentioned). The date must be a future date.
Usage Information Version Description 9.2(0.0) Introduced on the S4810, S4820T, Z9000, and MXL Switch. The maximum number of events you can configure is 20. The maximum number of allowed tag patterns in a log event trigger is three. The tags of the log events must be an exact comparison. The three tags work in a logical OR operation format (match with any one of the tags occurs). NOTE: Before deleting a trigger event, you MUST unlink the script from the event.
Syslog [0-5]" Dell(conf)# script trigger-event event7 log-event tag tag-regex "^ [A-Za-z] +.*Value : \?[0-9]" Dell(conf)# script trigger-event event2 log-event tag tag-regex up.*[0-9]+ Dell(conf)# script trigger-event event4 log-event tag tag-regex "up\?: Vl.*[0-9]+" Dell(conf)# script trigger-event event5 log-event tag tag-regex "The Value.*[0-9]+" show packages Displays the installed Open Automation packages, including version number and contents.
Usage Information Version Description 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. In a stack setup, the Dell Networking OS automatically synchronizes the software version installed on the master stack unit with the other switches in the stack.
rest-client 1.6.7 HTTP Server mini_httpd 1.21 Perl and Python function library for Dell Networking SmartScripts smartutils 2.0.0 DellSSUtils 1.0.0 WebConnect Web UI and CGI scripts htdocs 2.0.0 NetSNMP 5.7.2 Python NetSNMP module Perl NetSNMP module SQLite3 3.7.17 Python SQLite3 module Perl SQLite3 module TCL SQLite3 module Yaml 0.1.
process Enter the keyword process to list the scripts that are scheduled or running. Enter the optional keyword detail to show detailed output of the relevant arguments that are scheduled or running. watch Enter the keyword watch to list the supervised scripts and their relevant details. detail (Optional) Enter the keyword detail to show detailed output of the file including CPU percentage, memory percentage, next scheduled time, and any script name or relevant arguments.
Command History This guide is platform-specific. For command information about other platforms, see 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.10(0.1) Introduced on the S4048T–ON and S6010–ON. 9.10(0.0) Introduced on the S3100 Series and S6100–ON. 9.9(0.0) Introduced on the C9010. 9.8(1.0P1) Introduced on the Z9100–ON. 9.8(0.
Command History This guide is platform-specific. For command information about other platforms, see 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.10(0.1) Introduced on the S4048T–ON and S6010–ON. 9.10(0.0) Introduced on the S3100 Series and S6100–ON. 9.9(0.0) Introduced on the C9010. 9.8(1.0P1) Introduced on the Z9100–ON. 9.8(0.0P5) Introduced on the S4048–ON. 9.8(0.
Usage Information Version Description 9.10(0.0) Introduced on the S3100 Series and S6100–ON. 9.9(0.0) Introduced on the C9010. 9.8(1.0P1) Introduced on the Z9100–ON. 9.8(0.0P5) Introduced on the S4048–ON. 9.8(0.0P2) Introduced on the S3048–ON. 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 switch.
Usage Information Example Version Description 9.9(0.0) Introduced on the C9010. 9.8(1.0P1) Introduced on the Z9100–ON. 9.8(0.0P5) Introduced on the S4048–ON. 9.8(0.0P2) Introduced on the S3048–ON. 9.7(0.0) Introduced on the S4810, S4820T, S5000, S6000, S6000–ON, Z9000, Z9500, and MXL. • 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.
Usage Information 116 Version Description 9.10(0.1) Introduced on the S4048T–ON and S6010–ON. 9.10(0.0) Introduced on the S3100 Series and S6100–ON. 9.9(0.0) Introduced on the C9010. 9.8(1.0P1) Introduced on the Z9100–ON. 9.8(0.0P5) Introduced on the S4048–ON. 9.8(0.0P2) Introduced on the S3048–ON. 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.
9 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 Network fabric and the virtual servers to automate network management and configuration tasks throughout the data center.
Dell 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.
VLAN Configurations The following sections describe management, data, and hypervisor-unaware VLANs. Install VSN 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 loads into the Dell Networking OS. NOTE: VSN is only supported on standalone switches; it is not supported in stacked configurations.
To follow the progress of a package installation (or removal), use the show packages command. Enabling VSN in a Hypervisor Session To enable VSN on an interface and connect to hypervisors on network servers, follow these steps. Important Information: • VSN is only supported on standalone units; it is not supported in stacked configurations. • VSN supports connections only with VMware and Xen hypervisors. • You can define up to eight hypervisor sessions on a switch.
• config: Retrieves configuration information and automatically updates the configuration parameters in the Dell Networking OS. The default is config. 6 Enable the defined hypervisor connection. HYPERVISOR mode no disable Changing VSN Settings After you enable VSN on an interface and enable a hypervisor session that connects to hypervisors on network servers, you can change the mode setting when the session is active. You cannot, however, change the type and access settings if the session is active.
Connectivity If a network server is not reachable, a log message displays and the VSN agent tries periodically to establish the connection with the hypervisor. The initial log message is: Xen-Citrix:Connection error for hypervisor testing:LOGIN FAILURE If connectivity to a hypervisor is lost after information is retrieved and used to reconfigure a switch, the following log message displays. The VSN agent tries to connect to the hypervisor in the background.
Disabling a Hypervisor Session To stop VSN in a hypervisor session, enter the disable command in HYPERVISOR mode. The disable command does not remove connectivity with the hypervisor or remove the session information from the system configuration. • Shut down VSN in a hypervisor session. HYPERVISOR mode disable Removing a Hypervisor Session To delete the configuration of a hypervisor session from the running configuration, use the no hypervisor command in CONFIGURATION mode.
To display detailed information about a hypervisor session, enter the VSN interface and/or virtual-switch name generated by the hypervisor, as the show virtualswitch output displays. • Display information on virtual machines accessed on a switch interface, including the virtual machine name, VMAC address, and corresponding VLAN ID. Display the virtual machines accessed on a switch interface.
10 Virtual Server Networking CLI The Virtual Server Networking commands are supported on the S4810, S4820T, S5000, and MXL platforms. NOTE: VSN is supported only on standalone switches and VMware virtual distributed switches (VDS); it is not supported in stacked configurations.
Command Modes HYPERVISOR Command History This guide is platform-specific. For command information about other platforms, see 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.
hypervisor Specifies 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, see the relevant Dell Networking OS Command Line Reference Guide.
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, see 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 EXEC Privilege Command History This guide is platform-specific. For command information about other platforms, see 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 switch. 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 Uninstalling the VSN package removes it from the internal flash memory on the switch. To follow the progress when removing a package from the system, enter the show packages command. NOTE: Before you uninstall the VSN package, first stop all scripts that are currently running using the no script script-name command. Related Commands show packages — displays all the packages installed in the system.
show hypervisor supported Displays the types of Hypervisors VSN currently supports. S4810, S4820T, S5000, and MXL Switch Syntax show hypervisor supported Defaults none Command Modes EXEC Privilege Command History This guide is platform-specific. For command information about other platforms, see 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.6(0.0) Introduced on the S5000. 9.
Example 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. Dell#show packages **************************************** * Package Name:SMARTSCRIPTS Version: 2.0.0 Python 2.6.5 Perl 5.8.8 Data::Dumper 2.126 Class::MethodMaker 2.16 ExtUtils::MakeMaker 6.56 XML::NamespaceSupport 1.11 XML::SAX 0.96 XML::LibXML 1.70 Compress::Raw::Bzip2 2.027 Compress::Raw::Zlib 2.027 IO::Compress 2.027 URI 1.
show virtualswitch Displays the components of current Hypervisor sessions, including the virtual switch and name of the Hypervisor session to which a switch interface is connected. S4810, S4820T, S5000, and MXL Switch Syntax Parameters show virtualswitch [interface] [virtualswitch-name] interface virtualswitchname Display information on the Hypervisor session established on a specified interface.
The following command output displays information on the Hypervisor session established on virtual switch vSwitch3 on a VMware server connected to the interface 0/32. Dell#show virtualswitch Gigabitethernet 0/32 vSwitch3 Interface :Gi 0/32 Hypervisor Type :vmware Hypervisor Name :vmware207 Hypervisor Version :4.1.
Version Description 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 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.
vsn enable Enables 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, see 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.
11 REST API Representational state transfer (REST) application programming interface (API) is an integrated part of the Dell Networking operating system (OS) and is supported on the S4810, S4820T, S3048–ON, S4048–ON, S4048T–ON, S6000, S6000–ON, S6010–ON, S6100–ON, Z9100–ON, C9010, S5000, 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).
Request Query Parameters Following are the various request query parameters supported on REST. • deep — Retrieves a resource with all the subresources inline. • shallow — Retrieves a resource with no subresources inline. • select — Client uses to select the nodes and subresources. • with-defaults — Client uses to control and display the default data in GET request. To request a filtered partial response, use the select query parameter in the following patterns to specify the nodes and subresources.
* 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.159) port 8008 * Server auth using Basic with user 'admin' > PUT /api/running/dell/interfaces/interface/tengig-1-37 HTTP/1.1 > Authorization: Basic YWRtaW46YWRtaW4= > User-Agent: curl/7.15.5 (i686-redhat-linux-gnu) libcurl/7.15.5 OpenSSL/0.9.8b zlib/1.2.3 libidn/0.6.5 > Host: 10.16.151.159:8008 > Accept: */* > Content-Length: 171 > Expect: 100-continue > < HTTP/1.
200 false false The following configuration depicts the BGP configurations for router through the POST request: curl -v -u admin:admin http://10.16.151.159:8008/api/running/dell/router -X POST -T BGP_HTTP_REST_POST_PDU.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.2 * Connection #0 to host 10.16.151.159 left intact * Closing connection #0 The following configuration depicts adding another BGP peer to the configuration via REST– PATCH request: cat BGP_HTTP_REST_PATCH_PDU.xml 100 11.1.1.
The following configuration retrieves the BGPrunning-config via REST API: curl -u admin:admin http://10.16.151.159:8008/api/running/dell/router/bgp\?deep 100 60 180 1 1 false 11.1.1.
Status Error Codes Description 201 Created A resource is created and the new resource URI returns in the Location header. 204 No Content The request is successfully completed but no response body returns. 400 Bad Request The request could not be processed because it contains missing or invalid information (such as a validation error on an input field, a missing required value, and so on). 401 Unauthorized The request requires user authentication.
• :() refers that the node is a case node • -x for rpcs. NOTE: If the node is augmented into the tree from another module, the name is printed as :. • is one of the following: • • ? for an optional leaf or presence container • * for a leaf-list • [] for a list’s keys is the name of the type for leafs and leaf-lists. Configurations This section describes the properties of all the configurations.
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +--rw regex-eval-optz-disable? boolean | +--rw connection-retry-timer? dell:seconds | +--rw router-id? dell:ip-address | +--rw add-path? | | +--rw addpath? enumeration | | +--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
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 146 | +--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 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-map? dell:route-map-name | +--rw ospf [process-id] | | +--rw process-id uint16 | | +--rw match? | | | +--rw external1? boolean | | | +-
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 148 REST API +--rw network-v6 [ipv6-address] | +--rw ipv6-address dell:ipv6-address | +--rw route-map? dell:route-map-name | +--rw backdoor? boolean +--rw aggregate-address [ip-address] | +--rw ip-address union | +--rw advertise-map? dell:route-map-name | +--rw as-set? boolean | +--rw attribute-map? dell:route-map-name | +--rw summary-only? boolean | +--rw suppress-map
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +--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 soft-reconfiguration? | +--rw dmzlink-bw? | +--rw advertisement-start? +--rw management +--rw ip +--rw ipv6 enumeration boolean dell:seconds Global Configuration The following definition displays the global configuration entries: Module: SYSTEM URI: /api/running/dell/system Methods Supported: GET, POST, PUT, PATCH, and DELETE Global Configuration Model +--rw dell +--rw system | +--rw hostname? string | +--rw banner? | | +--rw login? string | +--rw credentials? | | +--rw username? string | | +
+--rw rules [seq-num] +--rw seq-num uint32 +--rw action ip-aspath-action-types +--rw pattern string IP Prefix-List The following definition configures and displays the properties of ip prefix-list.
| | +--rw source-host? dell:ipv4-host | +--rw (destination-address) | | +--:(destination) | | | +--rw destination? dell:ipv4-address-any | | | +--rw destination-mask dell:ipv4-mask-or-prefix | | +--:(host) | | +--rw destination-host? dell:ipv4-host | +--rw dscp? uint32 | +--rw ecn? uint32 | +--rw fragments? boolean +--rw acl-filters-qos +--rw filter-type? dell:acl-rule-types +--rw protocol dell:ipv4-protocols-qos IPv6 ACL The following definition configures and displays the properties of IPv6 ACL.
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.
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 154 | +--rw mode? | +--rw private-vlan? private-vlan-mode +--rw mac? | +--rw access-group? | | +--rw in? | | | +--rw WORD access-list-name | | | +--rw vlan* vlan-range | | +--rw out? | | +--rw WORD access-list-name | +--rw learning-limit? | +--rw count? uint32 | +--rw (operations)? | | +--:(sticky) | | | +--rw sticky? boolean | | +--:(non-sticky) | | +--rw dynamic? boolea
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +--rw name? vrf-name | +--rw address? | | +--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 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* vlan-range | +--:(optimized) | +--rw optimized? boolean +--rw out? +--rw WORD access-list-name +
+--rw prefix-min-len? +--rw prefix-max-len? uint32 uint32 IP Tunneling The following definition configures and displays the properties of IP tunneling.
| | +--rw ipv6-address dell:ipv6-address | +--rw nd? | | +--rw dad? | | | +--rw attempts? uint32 | | +--rw hop-limit? uint32 | | +--rw managed-config-flag? boolean | | +--rw ra-interval? | | | +--rw max-ra-interval uint32 | | | +--rw min-ra-interval uint32 | | +--rw mtu? uint32 | | +--rw dhcp-non-address? boolean | | +--rw prefix [prefix-name] | | | +--rw prefix-name dell:ipv6-nd-prefix-name | | | +--rw advertise? boolean | | | +--rw autoconfig? boolean | | | +--rw rtr-address? boolean | | | +--rw off-link?
| +--rw encapsulation-type? | +--rw encapsulation-operator? | +--rw encapsulation-protocol? +--rw acl-filters-qos +--rw filter-type? +--rw protocol dell:mac-acl-encap-types dell:mac-acl-encap-operators uint32 dell:acl-rule-types dell:mac-protocols-qos Management Route The following definition configures and displays the properties of a Management Route.
| +--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 access-list-name | +--ro type? access-list-types | +--ro mac-acl-filter [seq-no] | +--ro seq-no uint32 | +--ro filter-type? acl-rule-types | +--ro src-mac-filter? acl-incoming-address-filter-types | +--ro src-mac-addre
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 +--rw system +--rw interfaces +--rw router +--rw management +--rw ip +--rw ipv6 +--rw monitor-session [session-id] +--rw session-id uint32 +--rw type? enumeration +--rw description? string +--rw source-list [interface-name] | +--rw interf
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 ip +--rw route* [ip-address-prefix interface-name next-hop] | +--rw ip-address-prefix dell:ipv4-address-with-prefix | +--rw interface-name union | +--rw next-hop union | +--rw weight? uint32 | +--rw metric? uint32 | +--rw permanent? boolean | +--rw
BGP Model +--ro bgp +--ro table-version? uint32 +--ro local-router-id? string +--ro routes | +--ro prefix-list* [network-prefix network-prefix-len next-hop-address seq-num] | +--ro network-prefix inet:ip-address | +--ro network-prefix-len inet-address:InetAddressPrefixLength | +--ro next-hop-address inet:ip-address | +--ro seq-num uint32 | +--ro metric? uint32 | +--ro local-pref? uint32 | +--ro weight? uint32 | +--ro next-hop-cost-index? uint32 | +--ro as-path-string? string | +--ro path-source? enumeration
BGPv6 Use the following definition to get the BGPv6 operational data: Module: BGPv6 URI: /api/operational/dell/stats/ip/bgpv6 Methods Supported: GET BGPv6 Operational Model +--rw dell +--ro stats +--ro ip +--ro bgpv6 +--ro neighbors [neighbor-address vrf-id] | +--ro neighbor-address | +--ro vrf-id | +--ro remote-link? | +--ro router-id? | +--ro state? | +--ro state-duration? | +--ro last-read? | +--ro last-write? | +--ro hold-time? | +--ro keep-alive-interval? | +--ro stale-path-time? | +--ro config-ho
| +--ro adv-route-refresh? | +--ro adv-graceful-restart? | +--ro adv-cisco-route-refresh? | +--ro adv-four-byte-octet-as? | +--ro adv-add-path? | +--ro member-of-peer-grp? | +--ro peer-admin-status? | +--ro peer-fall-over? | +--ro bfd-enable-mode? | +--ro update-sourceset? | +--ro peer-allow-aslimit? | +--ro peer-act-in-grp-out-bound-opt? | +--ro max-prefix-set? | +--ro with-threshold? | +--ro config-drop-warn? | +--ro ttl? | +--ro ebgp-multi-hop-enable? | +--ro next-hop-set-self? | +--ro localpref? | +--ro
| +--ro denied-paths-memory? uint32 | +--ro nlri-memory? uint32 | +--ro path-memory? uint32 | +--ro total-memory? uint32 | +--ro path-attribute? uint32 | +--ro path-attribute-memory? uint32 | +--ro community? uint32 | +--ro community-memory? uint32 | +--ro external-community? uint32 | +--ro external-community-memory? uint32 | +--ro as-path? uint32 | +--ro as-path-memory? uint32 | +--ro rrcluster? uint32 | +--ro rrcluster-memory? uint32 | +--ro optional-transattribute? uint32 | +--ro optional-transattribute-
| +--ro input | | +--ro filter-list-name? bgp-list-name | +--ro output | +--ro filter-list [filter-list-name] | +--ro filter-list-name bgp-list-name | +--ro local-rib | | +--ro routes-added? uint32 | | +--ro routes-replaced? uint32 | | +--ro routes-withdrawn? uint32 | | +--ro router-id? dell:ipv6-address-with-prefix | +--ro prefix-list [network-prefix next-hop-addr] | +--ro network-prefix dell:ipv6-address-with-prefix | +--ro next-hop-addr dell:ipv6-address-with-prefix | +--ro status-code? bgp-status-code |
| | +--ro ext-community-list-name? bgp-list-name | +--ro output | +--ro ext-community-list [ext-community-list-name] | +--ro ext-community-list-name bgp-list-name | +--ro local-rib | | +--ro routes-added? uint32 | | +--ro routes-replaced? uint32 | | +--ro routes-withdrawn? uint32 | | +--ro router-id? dell:ipv6-address-with-prefix | +--ro prefix-list [network-prefix next-hop-addr] | +--ro network-prefix dell:ipv6-address-with-prefix | +--ro next-hop-addr dell:ipv6-address-with-prefix | +--ro status-code? bgp
| +--ro routes-replaced? uint32 | +--ro routes-withdrawn? uint32 | +--ro router-id? dell:ipv6-address-with-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 stati
+--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-octets? yang:counter64 +--ro in-unicast-pkts? yang:counter64 +--ro i
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 age
| +--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 proxy-arp? boolean +--ro split-horizon? boole
IPv6 ACL Operational Model +--ro dell +--ro stats +--ro access-list +--ro ipv6 [name] +--ro name dell:access-list-name +--ro ipv6-acl-filter [seq-num] +--ro seq-num uint32 +--ro filter-type? acl-rule-types +--ro protocol? ip-protocols +--ro ipv6-protocol-number? uint32 +--ro source | +--ro ipv6-filter? acl-incoming-address-filter-types | +--ro ipv6-address? dell:ipv6-address | +--ro ipv6-mask? dell:ipv6-address | +--ro operator? ip-acl-operators | +--ro port? uint32 | +--ro port-range? layer4-port-range +--
+--ro +--ro +--ro +--ro +--ro +--ro +--ro connected-active? connected-inactive? dynamic-active? dynamic-inactive? static-active? static-inactive? mgmt-route-size? uint32 uint32 uint32 uint32 uint32 uint32 uint32 MAC Address Table Use the following definition to get the entries of mac-address-table.
PBR Operational Model +--rw dell +--ro stats +--ro ip | +--ro redirect-list [name] | +--ro name string | +--ro filter [seq-no] | | +--ro seq-no uint32 | | +--ro output-action? pbr-rule-types | | +--ro next-hop-ip? dell:ipv4-no-prefix | | +--ro redirect-interface? dell:tunnel-intf-name | | +--ro track-num? uint32 | | +--ro track-status? enumeration | | +--ro protocol? dell:ip-protocols-type | | +--ro source-type? pbr-address-types | | +--ro source-address? dell:ipv4-no-prefix | | +--ro source-mask? dell:ipv4
+--ro nexthop-mac? +--ro egress-port? string string Port Mirroring Use the following model to get the Port Mirroring operational data: Module: STATS URI: /api/operational/dell/stats/monitor-session 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
| +--ro egress-count-value? uint32 | +--ro ingress-count-value? uint32 | +--ro log? boolean | +--ro monitor? boolean | +--ro order? uint32 +--ro ip* [name] +--ro name access-list-name +--ro type? access-list-types +--ro ip-acl-filter* [seq-no] +--ro seq-no uint32 +--ro filter-type? acl-rule-types +--ro protocol? ip-protocols +--ro ip-protocol-number? uint32 +--ro src-ip-filter? acl-incoming-address-filter-types +--ro source-ip-address? inet:ipv4-address +--ro source-mask? inet:ipv4-address +--ro src-operato
| +--ro hardware-revision? string | +--ro os-version? string | +--ro num-ports? uint32 | +--ro up-time? string | +--ro jumbo-capable? boolean | +--ro poe-capable? boolean | +--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 |
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
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: Module: STATS URI: /api/o
Interface Model for IPv6 +--ro interface* [interface-name] +--ro interface-name dell:interface-name +--ro description? string +--ro if-admin-status? dell:admin-status +--ro if-oper-status? dell:oper-status +--ro port-down-cause? string +--ro stateless-address-autoconfig? boolean +--ro ipv6-status? boolean +--ro link-local-ipv6-address? dell:ipv6-address +--ro global-unicast-ipv6-address* [address] | +--ro address dell:ipv6-address-with-prefix | +--ro configuration-type? enumeration | +--ro remaining-life-ti
| | | | | | | | | | | | +--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro +--ro errs-admin-prohib? errs-beyond-scope? errs-addr-unreach? errs-port-unreach? errs-pkt-too-big? errs-time-ex-trans? errs-time-ex-frags? errs-hdr-field? errs-unrec-nxt-hdr? errs-unrec-opt? errs-redirect? errs-unknown? yang:counter32 yang:counter32 yang:counter32 yang:counter32 yang:counter32 yang:counter32 yang:counter32 yang:counter32 yang:counter32 yang:counter32 yang:counter32 yang:counter32 Management Route
+--ro range-entries? +--ro sequence-min? +--ro sequence-max? +--ro seq* [seq-num] +--ro seq-num +--ro action? +--ro ipv6-prefix? +--ro ipv6-mask? +--ro ge? +--ro le? +--ro hit-count? uint32 uint32 uint32 uint32 enumeration dell:ipv6-address-with-prefix dell:ipv6-address-with-prefix uint32 uint32 uint32 Route Use the following definition to get the IPv6 Route statistics: Module: ROUTE URI: /api/operational/dell/stats/ipv6/route Methods Supported: GET Route Model for IPv6 +--ro route +--ro gateway-of-l
URI: /api/operational/mib/bgp-v2 Methods Supported: GET BGP V2 Model +--ro mib +--ro bgp4-v2 +--ro dellNetBgpM2 | +--ro dellNetBgpM2CapabilitySupportAvailable? snmpv2-tc:TruthValue | +--ro dellNetBgpM2AsSize? enumeration | +--ro dellNetBgpM2LocalAs? inetaddress:InetAutonomousSystemNumber | +--ro dellNetBgpM2LocalIdentifier? inet:ip-address | +--ro dellNetBgpM2RouteReflector? snmpv2-tc:TruthValue | +--ro dellNetBgpM2ClusterId? mib:dellNetBgpM2Identifier | +--ro dellNetBgpM2ConfederationRouter? snmpv2-tc:T
| +--ro dellNetBgpM2PeerMinASOrigInterval? uint32 | +--ro dellNetBgpM2PeerMinRouteAdverInterval? uint32 | +--ro dellNetBgpM2PeerHoldTime? uint32 | +--ro dellNetBgpM2PeerKeepAlive? uint32 | +--ro dellNetBgpM2PeerInUpdates? yang:counter32 | +--ro dellNetBgpM2PeerOutUpdates? yang:counter32 | +--ro dellNetBgpM2PeerInTotalMessages? yang:counter32 | +--ro dellNetBgpM2PeerOutTotalMessages? yang:counter32 | +--ro dellNetBgpM2PeerFsmEstablishedTrans? yang:counter32 | +--ro dellNetBgpM2PeerInKeepalives? yang:counter3
| +--ro dellNetBgpM2NlriIndex uint32 | +--ro dellNetBgpM2NlriAfi mib:dellNetBgpM2Afi | +--ro dellNetBgpM2NlriSafi mib:dellNetBgpM2Safi | +--ro dellNetBgpM2NlriPrefix inet:ip-address | +--ro dellNetBgpM2NlriPrefixLen inet-address:InetAddressPrefixLength | +--ro dellNetBgpM2NlriBest? snmpv2-tc:TruthValue | +--ro dellNetBgpM2NlriCalcLocalPref? uint32 | +--ro dellNetBgpM2PathAttrIndex? uint32 | +--ro dellNetBgpM2NlriOpaqueType? enumeration | +--ro dellNetBgpM2NlriOpaquePointer? snmpv2-tc:RowPointer | +--ro dell
| +--ro dellNetBgpM2PathAttrClusterValue? mib:dellNetBgpM2Identifier +--ro dellNetBgpM2PathAttrExtCommTable* [dellNetBgpM2PathAttrIndex dellNetBgpM2PathAttrExtCommIndex] | +--ro dellNetBgpM2PathAttrIndex uint32 | +--ro dellNetBgpM2PathAttrExtCommIndex uint32 | +--ro dellNetBgpM2PathAttrExtCommValue? mib:dellNetBgpM2ExtendedCommunity +--ro dellNetBgpM2FlapStatisticsTable* [NetworkPrefix NetworkPrefixLen NextHopAddress] +--ro NetworkPrefix inet:ip-address +--ro NetworkPrefixLen inet-address:InetAddressPrefixL
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 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? yang:counter64 | +--ro egL2MCDrops? yang:counter64 | +--ro egPktDropsOfAnyCondition? yang:counter64 | +--ro egHgMacUnderFlow
+--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:object-identifier +--ro ifName? smiv2:DisplayString +--ro ifInMulticastPkts? yang:counter32 +--ro ifInBroadcastPkts? yang:counter32 +--ro ifOutMulticastPkts? yang:counter32 +--ro ifOutBroadcastPkts? yang:counter32 +--ro ifHCInOctets? yang:c
+--rw mtu? uint32 +--rw link-up-down-trap-enable? enumeration +--rw rate-interval? 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. The command is sent as an XML payload and the corresponding command output or error message returns in an unstructured format in the XML response. There are three sets of XML commands: • • • config-commands — to send the configuration commands to the system.
mtu 10000 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, S3048–ON, S4048–ON, S4048T–ON, S6000, S6000–ON, S6010– ON, S6100–ON, Z9100–ON, C9010, S5000, and Z9500 platforms. Topics: • rest-server • crypto cert generate • crypto cert install • show crypto cert • show ip rest-server rest-server Enables the REST API service over a non-secure or secure HTTP.
Usage Information Version Description 9.8(0.0P5) Introduced on the S4048–ON. 9.8(0.0P2) Introduced on the S3048–ON. 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.4(0.0P1) Introduced on the S4810, S4820T, S6000, and Z9000. NOTE: The rest enable command is deprecated; however, the support is maintained for backward compatibility in version 9.4(0.0P1) and is removed in the 9.5(0.1) release.
state state-name (OPTIONAL) Enter the keyword state then the name of the state to include in the certificate. The default is California. validity days (OPTIONAL) Enter the keyword validity then the number of days the certificate is valid. The validity range is from 1 to 10000 days. The default value is 3650 days (10 years). Command Modes EXEC Command History This guide is platform-specific.
The following is a list of the Dell Networking OS version history for this command. Usage Information Version Description 9.10(0.1) Introduced on the S4048T–ON and S6010–ON. 9.10(0.0) Introduced on the C9010 and S6100–ON. Removed the rest-server option. 9.8(1.0P1) Introduced on the Z9100–ON. 9.8(0.0P5) Introduced on the S4048–ON. 9.8(0.0P2) Introduced on the S3048–ON. 9.7(0.0) Introduced on the S6000–ON. 9.6(0.0) Introduced on the S Series and Z Series switches.
Example Dell#show crypto cert Certificate: Data: Version: 3 (0x2) Serial Number: 7 (0x7) Signature Algorithm: sha1WithRSAEncryption Issuer: C=US, CN=Dell, O=Dell, OU=Dell Networking, L=SAN Jose, ST=California Validity Not Before: Feb 15 14:06:42 2016 GMT Not After : Feb 12 14:06:42 2026 GMT Subject: C=US, CN=Dell, O=Dell, OU=Dell Networking, L=SAN Jose, ST=California X509v3 extensions: X509v3 Subject Key Identifier: DA:39:A3:EE:5E:6B:4B:0D:32:55:BF:EF:95:60:18:90:AF:D8:07:09 Dell# show ip rest-server Disp
Example of the rest Dell#show ip rest-server service enabled over REST server status REST server protocol a secure HTTP REST server port Dell# 198 REST API CLI : enabled : HTTPS : 8888
13 Web Server You download web server with HTTP[S] support with the SmartScripts package. It is supported on the S4810, S4820T, S3100 Series, S3048–ON, S4048–ON, S4048T–ON, S5000, S6000, S6000–ON, S6010–ON, S6100–ON, Z9100–ON, Z9500, and MXL platforms. For more information, see 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.
