Skylight Flex Service Creation Management

Skylight Flex supports E-Line, E-LAN and E-Tree service types. Skylight orchestrator allows the configuration of these E-Line service types through commissioning and supports the definition of the services, the management of their lifecycle, and the ability to edit the services in bulk. These service definitions will be pushed to the Flex devices for configuration into Flex operations.

This article describes the procedure for Skylight Flex (100 and 25) service creation management in Skylight orchestrator.

The E-Line configuration will be executed via the Flow Executor function. The following E-Line service types are supported:

• untagged / 1 Tag push: Ethertype 0x88a8 | 0x8100 | 0x9100
• untagged / 2 Tags push-push: Ethertype 0x88a8/0x8100 | 0x9100/0x8100 | 0x8100/0x8100
• 1 Tag / 1 Tag replace: Ethertype 0x88a8
• 1 Tag / 2 Tags preserve-push: Ethertype 0x88a8 | 0x9100 | 0x8100
• 1 Tag / 2 Tags replace-push: Ethertype 0x9100 -> 0x88a8+0x8100 | 0x8100 -> 0x9100/0x9100
• 1 Tag / 3 Tags push-push: Ethertype 0x8100 -> 0x88a8+0x9100
• 1 Tag / 3 Tags translate 0x8100 and push-push: Ethertype 0x88a8+0x9100

Preconditions

The following preconditions must be met beforehand:

• Base configurations must be configured on both Flex devices
• IP address, hostname
• NTP
• Route
• MTU and bridge port type with customerEdgePort on UNI

• Ensure that the configured UNI port name on both Flex devices is the same.
• Ensure that you shutdown spanning tree.
• Each NNI port is only delegated for a single E-Line service type.
  Example: Port NNI 0/1 is used for 1 Tag / 1 Tag replace E-Line type; other E-Line types will not be configured on this port.

Procedure

Import the Flow Profiles

The first time you configure the E-Line service types to be supported, you must import seven flow profiles per the following attachment. of E-Line service CLI Sets and CLI flow template will be imported automatically.

flowProfileELine.profile

To Import a Configuration flow profile

1. Access the page Commissioning ▶ Flow Profiles.

2. Click the Import flow button. The Commissioning file import dialog is displayed.

3. Browse to the flowProfileELINE.profile file and click the Import button. The status of the import is indicated in the Commissioning file import dialog.

4. Close the Import devices dialog.
   

Create Flow Executor

A configuration flow executor sets up the final details on how a particular configuration flow profile for E-Line services will be executed. Before creating the flow executor you must ensure that flow profiles are imported.

To create a configuration flow executor

1. Access the page Commissioning ▶ Flow Executors.

2. Select the Add flow executor button. The Profile selection tab is above.

3. Enter a name for the executor in the Executor name field.

4. In the Profile name tab, check the E-Line service profile that you wish to execute. Only one E-Line service profile can be selected.
   

5. Select the Device selection tab.

6. Drag devices from the list of available devices (in the left pane) to the appropriate group of target devices (in the right pane).

7. Select the Parameters Input tab.

8. Enter values for all parameters in the list. If you have duplicated or are reusing the executor, values will already be displayed. You can change the values, if necessary.

9. Click Apply.

10. Select the Execution status tab and click the Start Executor button to immediately execute the configuration flow.
    

Template Examples

CLI set #1: Import before CLI script. Refer to Before CLI script name to use the before template script.

CLI set #2: Import the execution CLI script based on the types of E-Line services. Refer to Execution CLI script name to use the execution template scripts.

CLI set #3: Import after CLI script. Refer to After CLI script name to use the after template script.

Before CLI script name

configure terminal; interface ${NNI_INF_ID}; shutdown;mtu ${MTU}; bridge port-type providerNetworkPort ${THREE_TAGGED}; no shutdown; end

configure terminal; interface vlan 1000; no shutdown; end

Execution CLI script name

After CLI script name

The following commands will be reused for all E-Line service types:

configure terminal; vlan ${S_VLAN_ID}; ports ${UNI_INF_ID} ${NNI_INF_ID} untagged ${UNI_INF_ID}; end

Token Variables

• UNI_INF_ID: UNI ethernet ID ( as extreme-ethernet 0/3…).

• UNI_ETHER_TYPE: Ethernet type for UNI interface (as 0x88a8, 0x8100, 0x9100).

• NNI_INF_ID: NNI Ethernet ID (as XL-ethernet 0/1…).

• NNI_INNER_ETHER_TYPE: Inner ethernet type for NNI interface (as 0x88a8, 0x8100, 0x9100).

• NNI_ETHER_TYPE: Ethernet type for NNI interface (as 0x88a8, 0x8100, 0x9100).

• C_VLAN_ID: Customer VLAN ID.

• S_VLAN_ID: Service VLAN ID.

• C_RELAY_VLAN_ID: Relay VLAN ID.

• MTU: MTU value.

• T_VLAN_ID: Tunnel VLAN ID.

• T_PRIORITY: Tunnel priority.

• THREE_TAGGED: Enable three tagged in brigde port-type, Value: three-tagged or empty value.

Use Cases

Use Case #1

Set up a new type of E-Line with the new NNI port

Follow the procedure to create the flow profiles with specific E-Line service types.

Use Case #2

Set up multiple services on a configured E-Line type

Some commands in before CLI step should be run once, in case the multiple service for E-Line types must be configured. To avoid affecting traffic to the existing service, the Before-CLI script must be unset in the defined CLI step before running the profile job.

Example: For setting up multiple services on a configured E-Line – Layer-2 traffic 1 Tag / 1 Tag replace – Ethertype 0x88a8

With 1-Tag-1-Tag-replace type, there is a service #1 that is already configured with customer VLAN 10 and service VLAN 100; configure a new service (named service #2) with the customer VLAN 11 and service VLAN 101.

To configure service #2

In Jobs Page

1. Access the Commission ▶ Jobs page.

2. Select CLI step “1-Tag-1-Tag-replace“ in the Job name. The CLI tab is displayed.

3. Unset Before-CLI script.

4. Click Apply, then click Close.
   

In Flow Profiles Page

1. Access the Commission ▶ Flow Profiles page.

2. Double-click 1-Tag-1-Tag-replace in the list.

3. Click Apply, then click Close.
   

In Flow Executors Page

1. Access the Commissioning ▶ Flow Executors page.

2. Double-click 1-Tag-1-Tag-replace in the list.

3. Select the Parameters Input tab.

4. Only enter new values for the C_VLAN_ID and S_VLAN_ID parameters in the list (service #2 uses customer VLAN 11 and service VLAN 101).
   

   ---

   Note: If the type of E-Line has relay VLAN ID, a new value for the C_RELAY_VLAN_ID token must be set.

   Example: There is a service #1 that is already configured with relay VLAN ID 1000; configure service #2 with C_RELAY_VLAN_ID=1001.

   ---

5. Click Apply.