About Configuration Jobs

As part of its commissioning functionality, Skylight orchestrator allows you to configure Skylight devices that are in its inventory.

You can configure devices by means of two entities that can be set up and executed in the Commission tabs:

• Jobs: Configuration jobs (also known as "config jobs") are useful for performing tasks that do not require user input at execution time.
• Flows: Configuration flows (also known as "config flows") are useful for tasks that require user input at execution time. For more information, see "About Configuration Flows".

You can define configuration jobs in either of two ways:

• GUI mode: The job is set up entirely in the Skylight orchestrator web interface. This chapter explains how to set up configuration jobs in GUI mode.
• Dataset mode: In dataset mode, you use CSV text files to define the information required for a configuration job. For more information, see "About Datasets and CLI Sets".

Job Configuration Window

Configuration jobs are set up in the Job configuration window. These are the main features of the Job configuration window (shown in the figure below):

• Configuration steps: This area, the pane on the left, has check boxes to allow you to select configuration steps (tasks) to include in the configuration job. It also allows you to set the order in which the selected configuration steps will be executed by dragging the steps into a different position in the list.
• ME reference data set and ME reference data set enabled: These two areas allow you to select, from a pull-down menu, a list of devices to be configured and a list of parameters to apply to the devices and to enable dataset mode, using a check box.
• List of elements to configure: Elements are listed here if a dataset file is selected.
• Parameters for selected configuration step: This area allows you to set the parameters in GUI mode. You can set values for the parameters directly in this page.
• Grid style of configuration: A button at the beginning of each row. Upon clicking, a form will open that allows to edit the current configuration row.
•  In this form, the fields are grouped in the same sections as the ones displayed as tabs in the grid. As an example, for CoS profiles, the form has sections for General, PCP -03, etc.".
• Sections can be collapsed or expanded.
• When the user edits values in the form, the corresponding field in the grid is automatically updated.

Configuration Steps

Here is an alphabetical list of the configuration steps that are currently supported for devices. In the Job configuration window, the configuration steps are displayed in a different order by default. You can drag the steps to list them in any order.

• Backup configuration
• Bandwidth regulators
• Bandwidth regulator sets
• CFM Interface, Default and VSP
• CFM IEEE 802.3ag
• CFM ITU-T Y.1731
• CLI (Command Line Interface script)
• Clocks
• CoS profiles (Class of Service profiles)
• Device attributes
• Discovery configuration
• DMM Reflector
• DNS
• Flow
• FW upgrade (firmware upgrade)
• Interfaces
• IPv4 filter
• IPv6 filter
• L2 filter (Layer 2 filter)
• Loopbacks
• NTP-PTP
• PAA (Performance Assurance Agent)
• PM (Performance Monitoring data collection configuration)
• Module & SFP configuration
• Permission groups
• Policies
• Port CoS mapping
• Ports
• Rehoming
• SNMP agent
• SNMP traps
• System time
• Traffic configuration
• TWAMP Generator
• TWAMP Reflector
• Users
• Session Reflector
• VID sets (VLAN ID sets)
• Virtual Connection Access
• Virtual Connection

You can set up a configuration job in two ways:

• GUI mode: For details, see "Creating Configuration Jobs in GUI Mode".
• Dataset mode: For details, see "Creating Configuration Jobs Using Data Sets".

After you have set up all generic parameters for the configuration job (in GUI mode or dataset mode), you set up the parameters specific to the configuration job that you are performing. See the section for the particular type of configuration job.