Dell Networking Open Automation Guide December 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 the Post-Configuration Script.................................................................................................. 28 Using Auto-Execution Script (Normal Mode Only)........................................................................... 28 Timers in Pre–configuration and Post–configuration Scripts.......................................................... 29 Script Examples...................................................................................................................
Overview..............................................................................................................................................67 Installing Puppet..................................................................................................................................67 Prerequisites........................................................................................................................................ 67 Configuring the Puppet Agent............................
Running Scripts with User Privileges.................................................................................................. 89 8 Smart Scripting CLI............................................................................................ 90 disable................................................................................................................................................. 90 execute.............................................................................................
10 Virtual Server Networking CLI..................................................................... 126 access................................................................................................................................................ 126 disable................................................................................................................................................ 127 hypervisor.....................................................................................
Management Route..................................................................................................................... 172 MAC Address Table......................................................................................................................172 Policy Based Routing (PBR)......................................................................................................... 173 Port Mirroring.....................................................................................
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 MXL 9.2(0.0) or later Z9500 9.5(0.1) or later (BMP, SmartScripts, and REST API only) Z9100–ON 9.8.1.0 or later 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 S3048–ON S5000 S6000 S6000–ON MXL Switch Z9500 Z9100–ON Dell Networking platform and OS About this Guide Related Documents • Dell Networking OS Command Line Reference guide for the S3048–ON System • Dell Networking OS Configuration Guide for the S3048–ON System • Installing the S3048–ON System • Dell Networking OS Command Line Reference guide for the S5000 System • Dell Networking OS Configuration Guide for the S5000 System • Installing the S5000 System • Dell
2 Open Automation Framework The Dell Networking S4810, S4820T, S3048–ON, S4048–ON, S5000, S6000, S6000-ON, Z9500, Z9100–ON, 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.
The scripting environment (Expect, Perl, Python, Ruby, Tcl, UNIX and ZSH shell scripts) makes it easy for IT administrators to quickly develop scripts. REST API Representational state transfer (REST)-application programming interface (API) provides tools that allow you to manage Dell Networking OS switches by in-house or third-party system management tools.
Bare Metal Provisioning 3 Bare metal provisioning (BMP) is included as part of the Dell Networking OS image and is supported on the S4810, S4820T, S3048–ON, Z9100–ON, S4048–ON, S5000, S6000, S6000-ON, 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.
• Relay agent (optional) — an intermediary network device that passes messages between the DHCP clients and the DHCP server when the server is not on the same subnet. It can also provide IP addresses for multiple subnets. For more information, refer to Domain Name Server Settings and File Server Settings. Industrial Standard Upgrades with BMP Dell Networking OS follows the Industrial Standards with BMP. Following are the steps to perform the upgrade process: 1. Chassis Loads in BMP mode. 2.
NOTE: The configuration file maintains normal BMP functionality when a preconfiguration script is not sent. BMP Operations BMP is supported on the user ports and management ports of a switch.
address is not present in the start-up configuration file, no IP address is assigned to the management interface. • BMP mode (default) — the switch automatically configures all ports (management and user ports) as Layer 3 physical ports and acts as a DHCP client on the ports for a user-configured time (DHCP timeout). Set BMP mode using the (conf-reload-type)# boot-type bmp-reload command.
Normal Context To auto-configure a switch, before you use BMP mode, first configure a DHCP, DNS, and file server in the network. NOTE: By default, a syslog severity level greater than two does not display. Enable syslog before applying the preconfiguration script which helps identify any configuration errors. To help configure a new factory loaded switch, the switch boots up in the default BMP mode. You can reconfigure the switch to reload either in BMP mode or Normal mode.
4. If a DHCP offer has neither an image path nor a configuration file path, it is an invalid BMP DHCP offer and is ignored. The first DHCP offers the following to choose from: • • • • IP address Dell Networking OS image Configuration file or preconfiguration script IP address and Dell Networking OS image OR IP address and configuration file or preconfiguration script 5. DHCP OFFER is selected. All other ports except the port on which the offer was received and selected are set to Shutdown mode.
• c. 7. If the versions match, the system downloads the configuration file or preconfiguration script. 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:22: %STKUNIT0-M:CP %BMP-2-BMP_SHA256_VALIDATE_FAILURE: The Config/Script SHA256 Checksum Validation Failed. BMP Mode: Boot and Set-UP Behavior When you configure a switch to reload in BMP mode, one of the following scenarios may occur.
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 2. If you enabled the config-scr-download command, the system downloads the customer.conf configuration file from the file-server address. 3. If the configuration download is successful, the following logs display: file download has started.
Downloaded Image Minor Version : 0 00:02:56: %STKUNIT0-M:CP %BMP-5-BMP_RELEASE_HEADER_INFO: Downloaded Image Main Version : 0 00:02:56: %STKUNIT0-M:CP %BMP-5-BMP_RELEASE_HEADER_INFO: Downloaded Image Patch Version : 1216 00:02:56: %STKUNIT0-M:CP %BMP-5-BMP_RELEASE_HEADER_INFO: Flash A Image Major Version : 1 00:02:56: %STKUNIT0-M:CP %BMP-5-BMP_RELEASE_HEADER_INFO: Flash A Image Minor Version : 0 00:02:56: %STKUNIT0-M:CP %BMP-5-BMP_RELEASE_HEADER_INFO: Flash A Image Main Version : 0 00:02:56: %STKUNIT0-M:CP
00:03:03: %STKUNIT0-M:CP %IFMGR-5-ASTATE_DN: Admin state to down: Ma 0/0. 00:03:03: %STKUNIT0-M:CP %IFMGR-5-OSTATE_DN: state to down: Ma 0/0. 00:03:03: %STKUNIT0-M:CP %SYS-5-CONFIG_LOAD: configuration file. 00:03:04: %STKUNIT0-M:CP %IFMGR-5-ASTATE_UP: Admin state to up: Ma 0/0.
Software Upgrade Using BMP BMP simplifies switch configuration by allowing you to boot images and run configurations that are specified in a DHCP server and also by automatically downloading files from a file server. In a network topology with a large number of devices, use BMP to easily administer, upgrade, and maintain your devices. Configure Auto-Configuration mode using the reload-type bmp command. Reload the switch in Configuration mode using the reload command.
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 ...
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. The preconfiguration script can access Dell Networking OS CLI commands through the clido utility.
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. • After the script execution is successful, Dell Networking OS log displays: 00:04:05: %STKUNIT0-M:CP %BMP-5-AUTOEXEC_SUCCESS: The AutoExec Script execution returned Success.
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)... unmounting / (/dev/md0a)... done rebooting .. .. .. Starting Dell Networking application 00:00:13: %STKUNIT1-M:CP %RAM-6-ELECTION_ROLE: Stack unit 1 is transitioning to Managementunit.
FIT-INDUS-1-0-0/SW/SRC System image file is "dt-maa-s4810-72" System Type: S4810Control Processor: Freescale QorIQ P2020 with 2147483648 bytes of memory. 128M bytes of boot flash memory. 1 52-port GE/TE/FG (SE)48 Ten GigabitEthernet/IEEE 802.3 interface(s) 4 Forty GigabitEthernet/IEEE 802.3 interface(s) Dell#Wed Jan 2 22:47:34 GMT 2013 this is Autoexec script The following line indicates the auto-execution script has completed successfully.
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 print_f10do "show version" after 5000 print_f10do "copy flash://$config_file startup-config" print_f10do "yes" after 5000 puts "Pre-Config Script Execution Successful !!!!!\r\n" exit
# 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 "Configuring $intf ...\n" print_f10do "configure terminal" print_f10do "interface $intf" print_f10do "no ip address" print_f10do "no shutdown" print_f10do "end" after 200 } # Wait for 2 mins for the Neighbor to come-up puts "Wait for 1 min for the Neighbor to come-up\r\n" after [expr {
# Configure FTP - Interface print_f10do "configure terminal" print_f10do "interface TenGigabitEthernet 0/22" print_f10do "ip address 20.0.0.34/16" print_f10do "no shutdown" print_f10do "end" puts "Uploading Status File($status_file) to $ftp_ip ...\n" spawn ftp "$ftp_ip" expect "Name .*: " send "lab\n" expect "Password:" send "lab\n" expect "ftp>" send "cd scripts\n" expect "ftp>" send "ls\n" expect "ftp>" send "put $status_file\n" expect "ftp>" send "ls\n" expect "ftp>" send "bye\n" expect eof print_f10do "
– Configuration File Name — the configurations applied to the system. The configuration filename is expected to use option 209. To configure the device by itself for a download configuration file, you can also create a preconfiguration script in option 209. – File Server Address — the server where the image and configurations files are placed. The address is assumed to be a TFTP address unless it is given as a URL.
Following is a configuration example of a DHCP server included on the most popular Linux distribution. The dhcpd.conf file shows that the MAC-based IP and configuration file assignment are fixed. option configfile code 209=text; option bootfile-name code 67=text; host HOST1{ #####MAC to IP mapping hardware ethernet 00:01:e8:8c:4d:0e; fixed-address 30.0.0.
Class-Based Configuration By matching a part of the string from the vendor class identifier option 60 string, the image, configuration file, or script file is sent in the DHCP offer. For example: host dt-maa-z9000-11 { hardware ethernet 00:01:e8:a9:81:a3; fixed-address 10.16.151.175; option tftp-server-address 10.16.151.209; match if substring (option vendor-class-identifier,0,17) = "TY=DELLNTW-Z9000 "; { filename "tftp://10.16.151.209/FTOS-ZB-9.3.0.0.bin"; option configfile "ftp://anvltest:force10@10.16.
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 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, S3048–ON, S4048–ON, S5000, S6000, S6000–ON, Z9500, Z9100–ON, 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 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. Related Commands Version Description 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.
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.5(0.0) Introduced on the S4810, S4820T, S6000, Z9000, and MXL. Usage Information 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.
Related Commands Version Description 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). config-scr-download Allows you to specify whether the configuration or script file needs to be downloaded.
Usage Information For an initial setup, the config-scr-download parameter of the reload-type command is enabled. After the configuration file successfully downloads, the config-scr-download parameter is automatically disabled. You can enable it again using the reload-type command. Related Commands • 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).
Related Commands • 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). relay Allows you to configure the addition of option 82 in DHCP client packets.
• show reload-type — displays the current Reload mode (BMP mode or Normal mode). 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, S3048–ON, S4048–ON, S5000, S6000, S6000–ON, Z9100– ON, Z9500, and MXL Switch Syntax reload conditional nvram-cfg-change Defaults none Command Modes EXEC Command History This guide is platform-specific.
reload-type Allows you to configure the reload-type options in reload-type sub command mode. S4810, S4820T, S3048–ON, S4048–ON, S5000, S6000, S6000–ON, Z9100– ON, 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, 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.
• stop bmp — stops the BMP process and prevents a loop if the DHCP server is not found. retry-count Allows you to configure the number of retries for downloading the Dell Networking OS image and configuration file.
script post-config To run the post-configuration script after the preconfiguration script is executed during the BMP reload, ensure that this command is present in the startup-configuration. S4810, S4820T, S3048–ON, S4048–ON, S5000, S6000, S6000–ON, Z9100– ON, Z9500, and MXL Syntax Parameters script post-config {script-name} scriptname Enter the name of the script to run after the BMP start-up configuration is applied.
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 following is a list of the Dell Networking OS version history for this command. Version Description 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.
show config Displays the reload type options that are configured on the system. S4810, S4820T, S3048–ON, S4048–ON, S5000, S6000, S6000–ON, Z9100– ON, Z9500, IOA, and MXL Switch Syntax show config Defaults none Command Modes RELOAD-TYPE 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.
• retry-count — allows you to configure the number of retries for downloading the Dell Networking OS image and configuration file. • vendor-class-identifier — allows you to configure the optional vendor class identifier for DHCP option 60. show reload-type Displays the reload type currently configured on the system.
To display the current reload mode for BMP, use the show bootvar or show system brief commands. The show bootvar command includes the path of the Dell Networking OS image file retrieved from a DHCP server when BMP is running, but not after you exit BMP.
Version Description 9.2(0.0) Introduced on the Z9000, S4810, S4820T, and MXL switch. Replaces the stop jumpstart command. 9.1(0.0) Introduced on the Z9000 and S4810. Replaces the stop jumpstart command. Usage Information If the switch enters a loop while reloading in BMP mode, use the stop bmp command on a switch running BMP. A loop occurs when the switch is continuously trying to contact a DHCP server and a DHCP server is not found.
with Type, Hardware, Serial Number, Service Tag and OS Version. Defaults none Command Modes RELOAD-TYPE 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. Related Commands Version Description 9.8(1.0P1) Introduced on the Z9100–ON. 9.8(0.0P5) Introduced on the S4048–ON. 9.8(0.
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 following is a list of the Dell Networking OS version history for this command. Version Description 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 IOA and S6000–ON. 9.6(0.0) Introduced on the S5000. 9.5(0.
Open Management Infrastructure 5 Dell Networking OS supports the Open Management Infrastructure (OMI) framework. OMI is supported on the S4810, S4820T, S3048–ON, S4048–ON, S6000, Z9100–ON, 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.
Pre-requisites 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 see the Installing SmartScripting section of the Smart Scripting chapter. 3. Install the OMI package. EXEC Privilege mode package install “tftp:///OMI-I-9.8.1.0.tar.
• dsc — show dsc log • top — show the status from top • bottom — show the status from bottom • number of lines — specify the number of lines • client–test — test the OMI server using OMI client • install–cert — install the given SSL certificates to the OMI server • start — start the OMI server • stop — stop the OMI server NOTE: The script path is/usr/pkg/omi108/bin.
} 7. } • PortId identifies the interface. This example configures tengigabitethernet 0/1. • EnabledState identifies the status of the port. In this example, “Enabled” brings up the port. In Powershell, create the Ethernet MOF using configuration block. MSFT_NetworkDevice_EthernetPortViewConfig -OutputPath c:\EthernetPortViewMof This configuration creates the MOF in the C:\EthernetPortViewMof directory. 8. Connect to OMI. $cred=Get-Credential -UserName:"admin" -Message:"Admin User?" 9.
IsPolicyMapMatchCondition = True; SourceInfo = "C:\\ConfigFiles\ \MSFT_NetworkDevice_AclView_config.ps1::6::9::MSFT_NetworkDevice_AclView"; AclList = { $MSFT_NetworkDevice_AclEntry1ref }; ModuleName = "DSCModules"; ModuleVersion = "1.0"; }; instance of OMI_ConfigurationDocument { Version="1.0.
}; instance of MSFT_NetworkDevice_IpAddress as $MSFT_NetworkDevice_IpAddress3ref { IpAddressFamily = 1; IpAddress = "10.10.10.15"; NetworkPrefix = 32; }; 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_BgpConfiguration
instance of MSFT_Credential as $MSFT_Credential1ref { Password = "force10"; UserName = "Any\\Any"; }; 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.
Id Name PeerCredential AddressFamily VrfContext IsEnabled ActivateIPv6 AllowAsIn MultiHopTimeToLive RouteMapIn RouteMapOut Ensure KeyEncryptionMethod RemoteRouterId UpdateSourceInterface UpdateSourceInterfaceType ExtAsNumber PSComputerName : : : : : : : : : : : : : : : : : : 1-vrf1-1.2.3.
IsEnabled ActivateIPv6 AllowAsIn MultiHopTimeToLive RouteMapIn RouteMapOut Ensure KeyEncryptionMethod RemoteRouterId UpdateSourceInterface UpdateSourceInterfaceType ExtAsNumber PSComputerName : : : : : : : : : : : : : False True Id Name PeerCredential AddressFamily VrfContext IsEnabled ActivateIPv6 AllowAsIn MultiHopTimeToLive RouteMapIn RouteMapOut Ensure KeyEncryptionMethod RemoteRouterId UpdateSourceInterface UpdateSourceInterfaceType ExtAsNumber PSComputerName : : : : : : : : : : : : : : : : : : 2-
address-family ipv4 vrf vrf1 network 10.10.10.15/32 network 10.10.10.20/32 maximum-paths ebgp 3 redistribute static route-map rmap3 redistribute connected route-map rmap1 neighbor 1.2.3.4 remote-as 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.
Puppet 6 Dell Networking OS supports the Puppet automation framework. Puppet Agent is supported on the S4810, S4820T, S3048–ON, S4048–ON, S5000, S6000, S6000–ON, Z9100–ON, 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.
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. Configure script path /usr/pkg/puppet/bin.
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.
} } 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', 'interfacename2' ...
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, S3048–ON, S4048–ON, S5000, S6000, Z9100–ON, Z9500, and MXL switch platforms. Smart Scripting is not supported on the M IOA, FN IOA, and FN IOM platforms. Smart Scripting allows you to add functionality to Dell Networking switches without updating the Dell Networking OS release.
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.
• 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).
• 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. Displaying Installed Packages To view the Open Automation packages currently installed on a switch, including version numbers and content, use the following command. • View package information.
clido "end" clido "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. 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: • Continuous mode (clido command) — use to retain the Dell Networking OS context.
The severity level maps as follows: • 0 — emergency • 1 — alert • 2 — critical • 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.
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].
NET SNMP Client To manage the device using the simple network management protocol (SNMP) through scripts, the Dell Networking OS supports the NetSNMP client. You can run scripts that use SNMP to manage the data center and devices from within the Dell Networking OS. The Dell Networking OS provides Perl, Python, and Ruby interfaces for the NetSNMP client. To run the SNMP operations, use the tclsh exec command.
System Attributes Value Description memory use 233,244 Maximum size (in bytes) to which a process’s resident set size may grow. This value imposes a limit on the amount of physical memory a process is given; if memory is tight, the system prefers to take memory from processes that are exceeding their declared resident set size. memorylocked 77,741 Maximum size (in bytes) which a process may lock into memory using the mlock(2) function.
UNIX Utility Function file Determine the file type. find Walk a file hierarchy. ftp Internet file transfer program. getopts Called each time you process an argument. grep Print lines matching a pattern. hostname Set or print the name of the current host system. ifconfig Configure network interface parameters. iostat Report I/O statistics. ln Make links. ls List directory contents. md5 Calculates and verifies 128-bit MD5 hashes. more Filter for browsing text files.
Creating a User Name and Password for Smart Scripting Before you run a script from the Dell Networking OS CLI, you may want to configure an additional user name and password to use only to run scripts on a switch. Use the user name and password to log in to a UNIX shell and apply the read-write privileges assigned to the user name when a script runs with the script command from the Dell Networking OS CLI.
Setting a Search Path for Scripts Create a path to the location where you stored the scripts. The Dell Networking OS uses this path when searching for the scripts. This way you do not have to specify a specific path when executing a script. • Set a search path for a script in the Dell Networking OS. CONFIGURATION mode script path path-name The script path can contain a network file-system-mounted directory (defined in the mount nfs command).
The following example shows how you can schedule the script named sample.zsh to start after one hour and 12 minutes from now and runs the script in the background: • Dell#script execute sample.zsh start 01:12 bg Schedule a script to run periodically. Schedule scripts to run at a certain time, to be repeated, to stop at a specified time or by a string of arguments. This script runs in the background.
script event—handler event-name Following snippet triggers the 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 Dell(conf)#script event-handler handler1 Dell(conf-screvt-handler)#execute Report_server.
• 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. • To monitor the running script, use the watch command. • Dell#show script watch details JobID Script Type Script Status Reset Count Watch StartTime Script NameArgs Username 002 CONF WATCH Watch Blocked 3 Tue Dec 3 18:04:28 2013 args.
• 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.
Running Scripts with User Privileges Use these scripts to administer any Expect, PERL, Python, Ruby, Tcl, UNIX and ZSH shell scripts stored on the switch from the Dell Networking OS CLI. To apply the associated read-write privileges while running a script from the Dell Networking OS CLI, specify an optional username (refer to XXXCreating a User Name and Password for Smart Scripting). If you do not specify a user name, the script runs with the privileges of the configured user.
Smart Scripting CLI 8 Smart Scripting is supported on the S4810, S4820T, S3048–ON, S4048–ON, S5000, S6000, S6000–ON, Z9100–ON, Z9500, and MXL platforms. Smart Scripting is not supported on the M IOA, FN IOA, and FN IOM platforms. disable Allows you to enable or disable the current event handler configuration. S4810, S4820T, S3048–ON, S4048–ON, S5000, S6000, S6000–ON, Z9100– ON, Z9500, and MXL Syntax disable To reset the event handler, use the [no] disable command.
Parameters script-name Enter the name of the script to schedule for execution. 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, see the relevant Dell Networking OS Command Line Reference Guide.
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 Related Commands Version Description 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.
• From an NFS mount server: nfsmount://filepath 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.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.
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.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.
Parameters username name (Optional) Enter the user name with read-write privileges. A username cannot contain special characters. script-name Enter the name of the script to run, including the directory path and filename; for example: scriptparameter • Perl script: /usr/pkg/scripts/sample_scripts/ cmd-server.pl • Python script: /usr/pkg/scripts/sample_scripts/ DisplayAlarms.py • Ruby script: /usr/pkg/ss-scripts/ interface_monitor.rb • UNIX shell script: /usr/pkg/home/admin/test.
Usage Information To run more than one script at the same time, use the script (run) command multiple times; for example: Dell(conf)#script username root /usr/pkg/scripts/ sample_scripts/ DisplayAlarms.py Dell(conf)#script username root /usr/pkg/bin/python /usr/pkg/ scripts/ VSNAgent/Xen/hpAgtMain.py When you run a script from the Dell Networking OS CLI with the script (run) command, you can specify an optional user name to apply the read-write privileges assigned to the user name when the script runs.
job-id Enter the keywords job-id then the job identifier of the specific job stop, resume, clear, kill, or unschedule. all Enter the keyword all to stop, resume, clear, kill or unschedule all scripts. 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 following is a list of the Dell Networking OS version history for this command.
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.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.
bg Enter the keyword bg to schedule scripts to run in the background. 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. username username Enter the keyword username to use when the script runs. The maximum length is 16 characters. The default username is the user configuring the CLI. bg Enter the keyword bg to schedule scripts to run in the background.
This example illustrates that the script execution starts at 22:22 10/30/14 (MM/DD/YY) and stops after 1 hour and the script runs in the background. script execute (CONFIGURATION mode) Schedule the scripts to run across reloads. S4810, S4820T, S3048–ON, S4048–ON, S5000, S6000, S6000–ON, Z9100– ON, Z9500, and MXL Syntax script execute script-name [start {at date-time | after time}] [stop {at date-time | after time}] [watch] [arguments arg[..
username username (Optional) Enter the username to use when the script runs. The maximum length is 16 characters. The default username is the user configuring the CLI. Defaults The script runs in the background. 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.
script get Copy a script to a switch. S4810, S4820T, S3048–ON, S4048–ON, S5000, S6000, S6000–ON, Z9100– ON, Z9500, and MXL Syntax Parameters script get url url Enter the keyword url then the URL location of the script to download to a switch. 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.
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, S3048–ON, S4048–ON, S5000, S6000, S6000–ON, Z9100– ON, Z9500, and MXL Syntax script path path-name To remove the path for the script, use the no script path command.
Related Commands mount nfs — sets up the folders in the NFS-mounted directory. script remove Remove a script from a switch. S4810, S4820T, S3048–ON, S4048–ON, S5000, S6000, S6000–ON, Z9100– ON, 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.
script trigger-event Configure 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.
Version Description 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. Usage Information 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.
show packages Display the installed Open Automation packages, including version number and contents. S4810, S4820T, S3048–ON, S4048–ON, S5000, S6000, S6000–ON, Z9100– ON, Z9500, and MXL Syntax Parameters show packages [system] system (Optional) Enter the keyword brief to display system information about the package, version, and status of the package in all stack-units. NOTE: This option is only available on switches that allow stacking.
view the installed software versions on the stack units, use the show packages system command. Example (show packages) Dell# show packages * Package Name:SMARTSCRIPTS Python 2.7.8 Version:9.8(0.0) 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.54 HTML::Tagset 3.20 HTML::Parser 3.65 LWP 5.836 Net::Telnet 3.03 OSSP::uuid 1.0602 UUID 0.
TCL SQLite3 module Yaml Example (show packages system) 0.1.5 Dell#show packages system Package Information ------------------------------------------------------Unit Package Name Version Status ------------------------------------------------------0 SMARTSCRIPTS 9.8(0.0) Installed 1 not present 2 not present 3 not present 4 not present 5 not present 6 not present 7 not present 8 not present 9 not present 10 not present 11 not present show script Display the stored, scheduled, and running scripts.
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.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 S6000. 9.5(0.1) Introduced on the Z9500. 9.3(0.
Version Description 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 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 (see Running a Script from the UNIX Shell). After you start a shell, you are prompted to enter a username and password.
switch script limit To control the script that is running based on CPU, memory, or disk IO usage, use the switch script limit. S4810, S4820T, S3048–ON, S4048–ON, S5000, S6000, S6000–ON, Z9100– ON, Z9500, and MXL Syntax switch script limit {cpu percentage mem percentage disk percentage} To return to the default value, use the no switch script limit command. Parameters cpu percentage Enter the keyword cpu and the maximum percentage limit for the script execution. The range is from 20 to 90 percent.
username (event handler) Allows you to configure the username to run the scripts. S4810, S4820T, S3048–ON, S4048–ON, S5000, S6000, S6000–ON, Z9100– ON, Z9500, and MXL Syntax Parameters username username privilege privilege username username Enter the keyword username then the name of the user to access the script. The maximum length is 16 characters. The default username is the user configuring the CLI. privilege privilege Enter the keyword privilege then the privilege level to run the scripts.
username Configure an additional username and password to run the scripts on a switch. Use the username and password to log in to a UNIX shell and apply the read-write privileges assigned to the username when a script runs. S4810, S4820T, S3048–ON, S4048–ON, S5000, S6000, S6000–ON, Z9100– ON, Z9500, and MXL Syntax username name password password To remove the username and password, use the no username command. Parameters name Enter a username to access the UNIX shell.
Usage Information When you run a script from the Dell Networking OS CLI with the script (run) command, you can specify an optional username to apply the read-write privileges assigned to the username when the script runs (seeScheduling Time / Event-based Scripts.
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. 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. • ftp://userid:password@host-ipaddress/filepath logs in and installs VSN from a file stored on an FTP server. • 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.
Where url is one of the following values: 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 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. Users interested in writing scripts for VMware products must obtain the VMware SDK directly from VMware.
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 hypervisor supported command. Dell#show hypervisor supported vmware xen-citrix Example of the show virtualswitch all hypervisor sessions command. Dell#show Interface Gi 0/32 Po 7 virtualswitch VSwitch Hypervisor vSwitch3 VMWare_vmware207 vSwitch1 VMWare_vmware206 Example of the show virtualswitch specified hypervisor sessions command. Dell#show virtualswitch GigabitEthernet 0/32 vSwitch3 Interface :Gi 0/32 Hypervisor Type :vmware Hypervisor Name :vmware207 Hypervisor Version :4.1.
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; it is not supported in stacked configurations and VMware virtual distributed switches (VDS). 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.
Version Description 8.3.8.0 Introduced on the S4810. Usage Information 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.
Parameters 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. 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.2(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.6(0.0) Introduced on the S5000. 9.2(0.0) Introduced on the MXL. 8.3.19.0 Introduced on the S4820T. 8.3.8.0 Introduced on the S4810.
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 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.
Version Description 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.
For Xen Citrix hypervisors, the hpAgtMain.py Python script is stored in the /usr/ pkg/ scripts/VSNAgent/Xen directory. 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.
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. 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.
Python 2.6.5 XenAPI Perl 5.8.8 VIPerlToolkit 4.1 VSNAgent Scripts **************************************** 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.
Usage Information To display the interface, virtual-switch name, and Hypervisor-session name for all current Hypervisor connections on the switch, use the show virtualswitch command. To display detailed information about a Hypervisor session, re-enter the command with the interface and virtual-switch name for the session from the show virtualswitch output as shown in the following example.
Parameters interface Display information on the Hypervisor session established on a specified interface. Enter one of the following interface types: • For a 100/1000 Ethernet interface or 1-Gigabit Ethernet interface, enter GigabitEthernet slot/port. • For a 10-Gigabit Ethernet interface, enter TenGigabitEthernet slot/port. • For a port-channel interface, enter port-channel number. Valid port-channel numbers are from 1 to 128.
type Set the hypervisor type to which you want to connect. S4810, S4820T, S5000, and MXL Switch Syntax Parameters [no] type {vmware | xen-citrix} vmware Set the hypervisor type as VMware. xen-citrix Set the hypervisor type as Xen-Citrix. 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.
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 Enter the vsn enable command only on Hypervisor-facing interfaces. DO NOT enter this command on an interface used for inter-switch links. Enter the no vsn enable command to remove the VSN configuration from the system. To re-enable a Hypervisor session, reconfigure VSN.
REST API 11 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, S5000, S6000, S6000–ON, Z9100–ON, 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).
levels 2 through 15 have read-write access in REST API. The allowed methods are GET, PATCH, PUT, POST, and DELETE. For information about the privilege level command, see the Dell Networking OS Command Line Reference Guide, Security chapter. 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.
* 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.1 100 Continue < Server: ConfD/5.2 < Allow: GET, POST, OPTIONS, HEAD < Content-Length: 0 < HTTP/1.1 204 No Content < Server: ConfD/5.
11.1.1.2 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.
1 1 false 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.
Following is the current configurations applied on the system: Dell#show config ! router bgp 100 neighbor 11.1.1.2 neighbor 11.1.1.2 neighbor 11.1.1.3 neighbor 11.1.1.3 Dell# remote-as 200 no shutdown remote-as 200 no shutdown 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 PAGE 145100 1860238788none active
* Connection #0 to host 10.16.151.159 left intact * Closing connection #0 HTTP Status Error Codes The REST API server returns the following HTTP status error codes.
• Logical interface • BGP • Infrastructure • Miscellaneous Each node is printed as: . • is one of the following: – + for current – x for deprecated – o for obsolete • is one of the following: – rw for configuration data – ro for non-configuration data – -x for rpcs – -n for notifications • is the name of the node. – () refers that the node is a choice node – :() refers that the node is a case node – -x for rpcs.
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | REST API +--rw bgp [as-name] +--rw as-name dell:as-number +--rw bgp | +--rw asnotation? enumeration | +--rw always-compare-med? boolean | +--rw bestpath? | | +--rw as-path? enumeration | | +--rw med? | | | +--rw confed? boolean | | | +--rw missing-as-best? boolean | | +--rw router-id-ignore? boolean | +--rw client-to-client? | | +--rw reflection? boolean | +--rw cluster-id? union
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 148 | | +--rw ttl? uint8 | +--rw fall-over? boolean | +--rw send-community? | | +--rw community-type? enumeration | +--rw shutdown? boolean | +--rw update-source-loopback? uint16 | +--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? |
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | REST API | | +--rw as-number? dell:as-number | | +--rw no-prepend? boolean | +--rw password? | | +--rw encryption-type? enumeration | | +--rw password-value? string | +--rw activate? boolean | +--rw advertisement-interval? dell:seconds | +--rw allowas-in? uint8 | +--rw default-originate? | | +--rw route-map? dell:route-map-name | +--rw distribute-list [direction] | | +--rw direct
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 150 +--rw bgp? | +--rw asnotation? enumeration | +--rw always-compare-med? boolean | +--rw bestpath? | | +--rw as-path? enumeration | | +--rw med? | | | +--rw confed? boolean | | | +--rw missing-as-best? boolean | | +--rw router-id-ignore? boolean | +--rw client-to-client? | | +--rw reflection? boolean | +--rw cluster-id? union | +--rw confederation? | | +--rw identifier? dell:as
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | REST API | +--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 | | | +--rw external2? boolean | | | +--rw internal? boolean | | +--rw route-map? dell:route-map-name | +--rw isis [tag] | +--rw tag string | +--rw lev
| | +--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 dmzlink-bw? boolean | +--rw neighbor [ip-address] | +--rw ip-address union | +--rw peer-group-name? dell:peer-group-name | +--rw remote-as? dell:as-number | +--rw description? string | +--rw ebgp-multihop? | | +--rw ttl? uin
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 password? string | | +--rw privilege? uint32 | +--rw default-vlan? | | +--rw vlan-id? vlan-id-num | +--rw ip | +--rw dhcp? | | +--rw server? bool
– GigabitEthernet – TwentyfiveGigabitEthernet – FiftyGigabitEthernet – HundredGigabitEthernet • Example: tengig-0–0, fortygig-0–48, gige-1–10, twentyfivegig-1–3–1, fiftygig-1–5–1, hundredgig-1–2–1 • Management: mgmt-- Example: mgmt-5–0 2. Logical Interface: - • The can be vlan, port-channel, loopback, or management.
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | REST API | | +--:(log) | | | +--rw log boolean | | +--:(shutdown) | | +--rw shutdown boolean | +--rw station-move-violation? | +--rw (action)? | +--:(log) | | +--rw log boolean | +--:(shutdown-both) | | +--rw shutdown-both boolean | +--:(shutdown-offending) | | +--rw shutdown-offending boolean | +--:(shutdown-original) | +--rw shutdown-original boolean +--rw channel-members [name]
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 156 | | | | +--rw user-string? string | | | +--rw vendor-class-identifier? | | | +--rw distinct-string? string | | +--rw secondary [address] | | +--rw address dell:ipv4-address-with-prefix | +--rw access-group? | | +--rw in? | | | +--rw acl-name access-list-name | | | +--rw implicit-permit? boolean | | | +--rw (ip-action)? | | | +--:(vlan) | | | | +--rw vlan* vlan-range | | | +--
| | | | | | | | | | | | | | | | +--rw WORD | +--rw implicit-permit? | +--rw (ipv6-action)? | +--:(vlan) | | +--rw vlan* | +--:(optimized) | +--rw optimized? +--rw out? +--rw WORD +--rw implicit-permit? +--rw (ipv6-action)? +--:(vlan) | +--rw vlan* +--:(optimized) +--rw optimized? access-list-name boolean vlan-range boolean access-list-name boolean vlan-range boolean IPv6 Global Configurations The following definition displays the entries of IPv6 global configurations: Module: IPv6 URI: /api/operationa
Management Route The following definition configures and displays the properties of a Management Route.
types | +--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 REST API | | | +--ro src-mac-address? +--ro src-mac-mask? +--ro dest-mac-filter? yang:phys-address yang:phys-address acl-incoming-address-filter- | +--ro dest-mac-address? yang:phys-address | +--ro dest-mac
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 inter
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-hopaddress 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 local-pref? uint32 | +--ro weight? uint32 | +--ro next-hop-cost-index? uint32 | +--ro as-path-string? string | +--ro path-source? enumeration |
+--ro +--ro +--ro +--ro +--ro is-nlre-loc-aggtd? is-stale? status-code? best-route? link-bandwidth? snmpv2-tc:TruthValue snmpv2-tc:TruthValue enumeration snmpv2-tc:TruthValue string 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 with-prefix | +--ro vrf-id | +--ro re
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 164 +--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 +--ro
with-prefix with-prefix with-prefix REST API | | | | +--ro +--ro +--ro +--ro no-active-tcp-connection? pdu-cap-dir? pdu-cap-stats? local-host? | | +--ro local-port? +--ro foreign-host? | +--ro foreign-port? +--ro summary | +--ro local-router-id? string string string dell:ipv6-addressuint32 dell:ipv6-addressuint32 dell:ipv6-address- | +--ro local-as? string | +--ro neighbor-count? uint32 | +--ro nlri-count? uint32 | +--ro path-count? uint32 | +--ro penalized-paths? uint32 | +--ro denied-paths? uint
prefix prefix 166 | +--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 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 +--ro peer-group [peer-group-name] | +--ro peer-group-name string | +--ro version? uint32 |
prefix prefix prefix REST API | +--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 community-list | +--ro input | | +--ro community-list-name? bgp-list-name | +--ro output | +--ro community-list [community-list-name] | +--ro community-list-name bgp-list-name | +--ro local-rib | | +--ro routes-added? uint32 | | +--ro routes-replaced? uint32 | | +--ro routes-withdrawn? uint32
prefix 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 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 flap-statistics | +--ro input | | +--ro filter-list? string | +--ro output | +--ro flap-sta
Methods Supported: GET Interface Model for IPv4 +--ro stats +--ro interfaces* [name] +--ro name dell:interface-name +--ro description? string +--ro type? ianaiftype-mib:IANAifType +--ro if-index? uint32 +--ro admin-status? enumeration +--ro oper-status? enumeration +--ro oper-down-reason? string +--ro mtu? int32 +--ro speed? yang:gauge32 +--ro queueing-strategy? string +--ro phys-address? yang:phys-address +--ro tunnel-mode? encapsulation-modes +--ro decapsulate-any? boolean +--ro source? string +--ro sou
+--ro in-over-511bytes-pkts? yang:counter64 +--ro in-over-1023bytes-pkts? yang:counter64 +--ro in-symbol-errors? yang:counter64 +--ro in-runts? yang:counter64 +--ro in-giants? yang:counter64 +--ro in-throttles? yang:counter64 +--ro in-crc? yang:counter64 +--ro in-over-run? yang:counter64 +--ro in-discards? yang:counter64 +--ro in-unknown-protocol? yang:counter64 +--ro out-octets? yang:counter64 +--ro out-unicast-pkts? yang:counter64 +--ro out-multicast-pkts? yang:counter64 +--ro out-broadcast-pkts? yang:cou
| | +--ro weight? uint32 | | +--ro route-type? enumeration | +--ro route-owner? enumeration | +--ro metric? uint32 | +--ro age? yang:timestamp | +--ro route-tag? string | +--ro distance? uint32 | +--ro default-route? boolean | +--ro summary? boolean +--ro summary +--ro connected-active? uint32 +--ro connected-in-active? uint32 +--ro dynamic-active? uint32 +--ro dynamic-in-active? uint32 +--ro static-active? uint32 +--ro static-in-active? uint32 +--ro route-size-active? uint32 +--ro route-size-in-active? uin
Management Route Use the following definition to get the Management Route statistic.
+--ro multicast +--ro count? uint32 +--ro mac-vlan* [vlan-id] +--ro vlan-id vlan-id +--ro static-mac-count? uint32 +--ro mac-address-list* [mac-address] +--ro mac-address yang:phys-address +--ro state? enumeration +--ro l2-mc-index? uint32 +--ro interface-list? string Policy Based Routing (PBR) Use the following model to get the PBR operational data: Module: STATS URI: /api/operational/dell/stats/ip/redirect-list Methods Supported: GET PBR Operational Model +--rw dell +--ro stats +--ro ip | +--ro red
| +--ro rule-entry [cam-index] | | +--ro cam-index uint32 | | +--ro port? uint32 | | +--ro vlan-id? dell:vlan-id-num-with-default | | +--ro protocol? dell:ip-protocols-type | | +--ro tcp-flag* tcp-bits | | +--ro source-port? uint32 | | +--ro destination-port? uint32 | | +--ro source-ip? string | | +--ro destination-ip? string | | +--ro nexthop-mac? string | | +--ro egress-port? string | +--ro rule-entry-count? uint32 +--ro interface [name] +--ro name dell:interface-name +--ro rule-entry [cam-index] +--ro ca
URI: /api/operational/dell/stats/access-list Methods Supported: GET Static Access-List Model +--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-address? yang:phys-address | +--ro src-mac-mask? yang:phys-address | +--ro dest-mac-filter? acl-incoming-address-filter-types | +--ro dest-mac-address?
+--ro ecn? +--ro fragments? uint32 boolean System Use the following definition to display the System entries: Module: STATS URI: /api/operational/dell/stats/system Methods Supported: GET System Model +--ro mac-address? yang:phys-address +--ro reload-type? reload-type +--ro next-boot? reload-type +--ro units* [unit-id] | +--ro unit-id uint32 | +--ro unit-role? string | +--ro unit-status? string | +--ro unit-next-boot-status? string | +--ro required-type? string | +--ro current-type? string | +--ro ma
| +--ro bay-status? string | +--ro fan-id? uint32 | +--ro fan-status? string | +--ro fan-speed? uint32 +--ro environment-status* [unit-id] | +--ro unit-id uint32 | +--ro unit-status? string | +--ro temperature? int32 | +--ro voltage? voltage-status | +--ro temp-status? uint32 +--ro thermal-sensor-reading* [unit-id] +--ro unit-id uint32 +--ro sensor-class* [sensor-type] +--ro sensor-type sensor-types +--ro sensor* [sensor-id] +--ro sensor-id uint32 +--ro temperature? int32 System Alarm Use the following def
System Inventory Model +--ro inventory +--ro system-type? string +--ro system-mode? string +--ro sw-version? string +--ro parts [index] | +--ro index | +--ro stack-unit? | +--ro part-type? | +--ro serial-number? | +--ro part-number? | +--ro revision? | +--ro piece-part-id? | +--ro ppid-revision? | +--ro service-tag? | +--ro express-service-code? +--ro protocols? uint32 uint32 string string string string string string string string string System Version The following definition displays version-info: Modul
VLAN Model +--ro vlan* [vlan-id] +--ro vlan-id vlan-id-num +--ro vlan-name? vlan-name +--ro default-vlan? boolean +--ro vlan-codes? vlan-codes +--ro vlan-status? vlan-status +--ro vlan-description? string +--ro vlan-port-list* [vlan-port-list-num] +--ro vlan-port-list-num int32 +--ro vlan-port-list-port-mode? vlan-port-mode +--ro vlan-port-list-intf-type? vlan-intf-type +--ro vlan-port-list-data? string Operational Data for IPv6 This section describes the method of fetching the IPv6 operational data.
+--ro nd-mtu? uint32 +--ro dad? boolean +--ro dad-attempts? uint32 +--ro nd-reachable-time? uint32 +--ro nd-base-reachable-time? uint32 +--ro nd-advertised-reachable-time? uint32 +--ro nd-advertised-retransmit-interval? uint32 +--ro nd-router-advertisement-interval-min? uint32 +--ro nd-router-advertisement-interval-max? uint32 +--ro nd-router-advertisement-live-for? uint32 +--ro nd-router-advertised-hop-limit? uint32 +--ro ipv6-hop-limitfor-orig-pkts? uint32 +--ro flowlabel-zero +--ro label_value? boolean +
IPv6 Management Route Model +--ro ipv6 +--ro management-route +--ro route-entry* [destination] | +--ro destination dell:ipv6-address-with-prefix | +--ro gateway? string | +--ro state? enumeration | +--ro default-route? boolean +--ro summary +--ro connected-active? uint32 +--ro connected-inactive? uint32 +--ro static-active? uint32 +--ro static-inactive? uint32 +--ro route-size-active? uint32 +--ro route-size-inactive? uint32 +--ro total-active-routes? uint32 +--ro total-inactive-routes? uint32 Prefix-list
Route Model for IPv6 +--ro route +--ro gateway-of-last-resort? string +--ro route-entry* [destination] | +--ro destination dell:ipv6-address-with-prefix | +--ro gateway? dell:ipv6-address-with-prefix | +--ro route-type? enumeration | +--ro route-owner? string | +--ro metric? string | +--ro intf-type? string | +--ro last-change? yang:timestamp | +--ro state? enumeration | +--ro default-route? boolean | +--ro summary? boolean +--ro summary +--ro connected-active? uint32 +--ro connected-inactive? uint32 +--ro
| +--ro dellNetBgpM2CfgLocalAs? inetaddress:InetAutonomousSystemNumber | +--ro dellNetBgpM2CfgLocalIdentifier? inet:ip-address | +--ro dellNetBgpM2CfgRouteReflector? snmpv2-tc:TruthValue | +--ro dellNetBgpM2CfgClusterId? mib:dellNetBgpM2Identifier | +--ro dellNetBgpM2CfgConfederationRouter? snmpv2-tc:TruthValue | +--ro dellNetBgpM2CfgConfederationId? inetaddress:InetAutonomousSystemNumber | +--ro dellNetBgpM2CfgPeerNextIndex? int32 | +--ro dellNetBgpM2PathAttrCount? yang:counter32 +--ro dellNetBgpM2VersionT
| +--ro dellNetBgpM2PeerOutOpen? yang:counter32 | +--ro dellNetBgpM2PeerInRteRefresh? yang:counter32 | +--ro dellNetBgpM2PeerOutRteRefresh? yang:counter32 | +--ro dellNetBgpM2PeerReflectorClient? enumeration | +--ro dellNetBgpM2PeerConfedMember? snmpv2-tc:TruthValue | +--ro dellNetBgpM2CfgPeerConfedMember? snmpv2-tc:TruthValue | +--ro dellNetBgpM2PeerGroupName? string +--ro dellNetBgpM2PeerCapsAnnouncedTable* [dellNetBgpM2PeerIndex dellNetBgpM2PeerCapAnnouncedCode dellNetBgpM2PeerCapAnnouncedIndex] | +--ro
address:InetAddressPrefixLength | +--ro dellNetBgpM2NlriBest? snmpv2-tc:TruthValue | +--ro dellNetBgpM2NlriCalcLocalPref? uint32 | +--ro dellNetBgpM2PathAttrIndex? uint32 | +--ro dellNetBgpM2NlriOpaqueType? enumeration | +--ro dellNetBgpM2NlriOpaquePointer? snmpv2-tc:RowPointer | +--ro dellNetBgpM2RouteFlag? enumeration +--ro dellNetBgpM2AdjRibsOutTable* [dellNetBgpM2PeerIndex dellNetBgpM2NlriAfi dellNetBgpM2NlriSafi dellNetBgpM2NlriPrefix dellNetBgpM2NlriPrefixLen dellNetBgpM2AdjRibsOutIndex] | +--ro dellN
| +--ro dellNetBgpM2LinkLocalNextHop? inet-address:InetAddress +--ro dellNetBgpM2PathAttrOriginatorIdTable* [dellNetBgpM2PathAttrIndex] | +--ro dellNetBgpM2PathAttrIndex uint32 | +--ro dellNetBgpM2PathAttrOriginatorId? inet:ip-address +--ro dellNetBgpM2PathAttrClusterTable* [dellNetBgpM2PathAttrIndex dellNetBgpM2PathAttrClusterIndex] | +--ro dellNetBgpM2PathAttrIndex uint32 | +--ro dellNetBgpM2PathAttrClusterIndex uint32 | +--ro dellNetBgpM2PathAttrClusterValue? mib:dellNetBgpM2Identifier +--ro dellNetBgpM2
+--ro dellNetInetCidrRouteEgressPort? +--ro dellNetInetCidrRouteCamIndex? string uint32 Forwarding Plane Statistics The following definition displays the Forwarding Plane statistics: Module: FP-STATS URI: /api/operational/mib/fp-stats Methods Supported: GET 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 inputPackets? int32 | +--ro inputBytes? int32 | +--ro inputDropped? int32 | +--ro inputError? int32 | +--ro outputPackets? int32 | +--ro outputBytes? int32 | +--ro outputError? int32 +--ro fp-drops-table* [stackUnitId stackPortId] | +--ro stackUnitId int32 | +--ro stackPortId int32 | +--ro inDrops? yang:counter64 | +--ro inIBPCBPFullDrops? yang:counter64 | +--ro inPortSTPnotFwdDrops? yang:counter64 | +--ro inIPv4L3Discards? yang:counter64 | +--ro inPolicyDiscards? yang:counter64 | +--ro inPktDropped
IF MIB Model +--ro mib +--ro if-mib +--ro ifNumber? int32 +--ro ifTable* [ifIndex] +--ro ifIndex mib:InterfaceIndex +--ro ifDescr? smiv2:DisplayString +--ro ifType? ianaiftype-mib:IANAifType +--ro ifMtu? int32 +--ro ifSpeed? yang:gauge32 +--ro ifPhysAddress? yang:phys-address +--ro ifAdminStatus? enumeration +--ro ifOperStatus? enumeration +--ro ifLastChange? yang:timeticks +--ro ifInOctets? yang:counter32 +--ro ifInUcastPkts? yang:counter32 x--ro ifInNUcastPkts? yang:counter32 +--ro ifInDiscards? yang:coun
+--ro ifTableLastChange? +--ro ifStackLastChange? yang:timeticks yang:timeticks IETF Interface Operations The following definition configures and displays the properties of an Interface using IETF: Module: IETF INTERFACE URI: /api/operational/interfaces 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-interva
+--ro input | +--ro config-commands? | +--ro show-command? | +--ro exec-command? +--ro output +--ro command string string dell:show-cmd-str dell:cli-cmd-str 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
12 REST API CLI The REST API CLI commands are supported on the S4810, S4820T, S3048–ON, S4048–ON, S5000, S6000, S6000–ON, Z9100–ON, and Z9500 platforms. rest-server Enable the REST API service over a non-secure or secure HTTP. S4810, S4820T, S3048–ON, S4048–ON, S5000, S6000, S6000–ON, Z9100– ON, 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.
Usage Information 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. crypto cert generate Generate a self-signed certificate and key files, if exists, and replace them with the newly generated files.
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. 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.8(1.
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 S Series and Z Series switches. Usage Information If either certificate or key files are not present or not valid, the prompt displays a message File not found/invalid. show crypto cert Display the certificate information.
Issuer: C=US, ST=California, L=San Jose, O=Dell, OU=Dell Networking,CN=S6000-NA Validity Not Before: Apr 28 19:05:16 2014 GMT Not After : Apr 30 19:05:16 2014 GMT Dell# show ip rest-server Display the status of the configured rest-server (HTTP or Secure HTTP). S4810, S4820T, S3048–ON, S4048–ON, S5000, S6000, S6000–ON, Z9100– ON, and Z9500 Syntax show ip rest-server Defaults none Command Modes EXEC Privilege Command History This guide is platform-specific.
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, and MXL switch platforms. For more information, see the 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.
