Service Manual
Table Of Contents
- Dell Networking Open Automation Guide December 2015
- About this Guide
- Open Automation Framework
- Bare Metal Provisioning
- Introduction
- How it Works
- Prerequisites
- Industrial Standard Upgrades with BMP
- BMP Process Overview
- BMP Operations
- Configure BMP
- BMP Commands and Examples
- System Boot and Set-Up Behavior in BMP Mode
- BMP Mode: Boot and Set-UP Behavior
- DHCP Offer Vendor-Specific Option for BMP
- DHCP Offer Relay Option 82
- Software Upgrade Using BMP
- Apply Configurations Using BMP Scripts
- Using the Post-Configuration Script
- Using Auto-Execution Script (Normal Mode Only)
- Timers in Pre–configuration and Post–configuration Scripts
- Script Examples
- BMP Operations on Servers Overview
- File Server Settings
- Domain Name Server Settings
- BMP MIB Support
- Bare Metal Provisioning CLI
- Open Management Infrastructure
- Puppet
- Smart Scripting
- Overview
- Download the Smart Scripting Package
- Dell Proprietary Utilities
- Dell SmartScript Utilities
- SQLite
- NET SNMP Client
- Limits on System Usage
- Supported UNIX Utilities
- Creating a User Name and Password for Smart Scripting
- Logging in to a NetBSD UNIX Shell
- Downloading Scripts to a Switch
- Setting a Search Path for Scripts
- Scheduling and Executing Scripts
- Running a Script from the UNIX Shell
- Running Scripts with User Privileges
- Smart Scripting CLI
- disable
- execute
- mount nfs
- package install
- package uninstall
- script (run)
- script (stop/resume/clear/kill/unschedule)
- script event-handler
- script execute (EXEC mode)
- script execute (CONFIGURATION mode)
- script get
- script path
- script remove
- script trigger-event
- show packages
- show script
- start shell
- triggered-by
- switch script limit
- username (event handler)
- username
- Virtual Server Networking
- Virtual Server Networking CLI
- REST API
- HTTP and HTTPS
- XML
- Important Points to Remember
- REST Authentication
- Request Query Parameters
- Sample BGP Configurations
- HTTP Status Error Codes
- REST API — Protocol Data Unit (PDU) Structure
- Configurations
- Operational
- Operational Data for IPv6
- Management Information Base (MIB)
- IETF Interface Operations
- REST API Framework to Execute the CLIs
- Samples of the config-command
- Samples of the EXEC command
- Samples of the show-command
- REST API CLI
- Web Server with HTTP Support

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.
CONFIGURATION mode
script execute script-name [start {at date-time | after time}] [stop {at
date-time | after time}] [watch] [arguments arg[..arg]] [username username]
Following example shows the script execution at 22:22 (FTOS clock time) and stops after 15 minutes:
Dell(conf)#script execute monitor_status.pl start at 22:22 stop after 15
watch args "Te 0/4"
The keyword watch is used to monitor the script. If the script execution terminates before 10
minutes, the system will rerun the script.
• Executing a script based on event trigger.
Define an event to trigger scripts to run by a log event (for example, SYSLOG in Dell Networking OS), a
time-based event, or when CPU or memory usage reaches a predetermined percentage. The script
runs in the background.
CONFIGURATION mode
script trigger-event event-name {log-event [{tag—or—ex tags | tag-and-ex
tags}] [severity severity level]} | time-event {[start {at date-time | after
time}] [stop {at date-time | after time | count number}] [interval time]
[weekday day] [ month month] [monthday nday]} | cpu-usage percentage | mem-
usage percentage}
Following example shows the event to trigger a script at 22:22 and then triggers every Monday
midnight and stops at 02:02–11/10/14:
Dell(conf)#script trigger-event Event2 time-event start at 22:22 stop at
02:02-11/10/14 weekday mon
Following example shows the event triggering the script once the cpu-usage reaches 30%:
Dell(conf)#script trigger-event event1 cpu-usage 30
Following example shows how you can define the 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.*up"
Following example shows how you can define the event to trigger a script even if any one of the
pattern is matched:
Dell(conf)#script trigger-event Server_Reporter_Event log-event tag tag-or-
ex "Major alarm" "Minor alarm"
• Schedule a script to run based on defined events.
Schedule a script to provide mapping between the scripts and trigger-events.
CONFIGURATION mode
Smart Scripting
85