- Print
- PDF
Service Activation Test and Reporting for Skylight Flex
The following procedure is for Provider Connectivity Assurance Sensor F100 and F25 Service Activation Test (SAT) and Reporting in Legacy orchestrator. The SAT test is executed via the Flow Executors page. The workflow involves:
- Importing profile template support for SAT on Assurance Sensor F100 or F25
- Enabling Y.1564 on the Assurance Sensor F100 or F25 device that will be the near end device
- Creating, starting, and showing the test report
- Obtaining final SAT test result
Supported SAT Test Types
- Y1564 Service Configuration - SAC - SLA – Untagged
- Y1564 Service Configuration - SAC - SLA - Single-tagged
- Y1564 Service Configuration - SAC - SLA - Double-tagged
- Y1564 Service Configuration - SAC - SLA - Performance – Untagged
- Y1564 Service Configuration - SAC - SLA - Performance - Single-tagged
- Y1564 Service Configuration - SAC - SLA - Performance - Double-tagged
Preconditions
Before beginning:
- Set up topology
- Prepare the devices
- Enable Y.1564 on the near end device
Set Up Topology
Two Assurance Sensor F100 or F25 units, Flex-1 (near end device) and Flex-2 (far end device), must be connected back-to-back via interface XL-ethernet 0/1.
Prepare the Devices
After your setup is complete, follow the steps in this section to prepare both Flex devices.
Note: ProviderEdgeMode (PEM) is the default mode for Assurance Sensor F100 and F25. If the bridge mode is customerEdge, no VLAN configuration is required on the remote Flex to reflect the SAT packets. To view the bridge mode, enter: show vlan device info.
- Change bridge port type of UNI interface to Customer Edge Port-type (optional).
- Connect to the UNI Interface:
config terminal; interface extreme-ethernet 0/1
- Change port type to customerEdgePort:
bridge port-type customerEdgePort; end
- Change bridge port type of the NNI interface to Provider Network Port-type.
- Connect to NNI Interface:
config terminal; interface XL-ethernet 0/1
- Change port type to provider network port:
bridge port-type providerNetworkPort
- Configure member ports on VLAN 1 (applicable for: un-tagged):
config terminal; vlan 1
- Add the NNI port to the VLAN:
ports add XL-ethernet 0/1
ports xl 0/1 untagged xl 0/1 ;end
- Configure EtherType on the NNI interface (applicable for: single-tagged; double-tagged).
- Connect to NNI interface:
config terminal; interface XL-ethernet 0/1
- Egress EtherType (use the necessary tpid 0x88a8 or 0x8100):
switchport egress ether-type 0x88a8
- Ingress EtherType (use the necessary tpid 0x88a8 or 0x8100):
switchport ingress ether-type 0x88a8; end
- Configure Customer VLAN (applicable for: double-tagged).
- Connect to NNI interface:
config terminal; interface XL-ethernet 0/1
- Configure the Inner EtherType on the NNI port:
switchport egress inner-ether-type 0x88a8
switchport ingress inner-ether-type 0x88a8
- Connect to the UNI interface:
config terminal; interface extreme-ethernet 0/1
- Configure the Customer VLAN. This is optional and not required for a test that is created between Flex NNI to NNI.
switchport customer-vlan 20 service-vlan 10
switchport dot1q customer vlan 20
- Configure member ports on VLAN 10 (applicable for: single-tagged; double-tagged).
- Create VLAN 10:
config terminal; vlan 10
- Add the member ports to VLAN 10 and configure the ex 0/1 as untagged. Untagging the port enables it to receive the packets from the trunk port after the VLAN is popped out.
ports extreme-ethernet 0/1 XL-ethernet 0/1 untagged extreme-ethernet 0/1
Enable Y.1564 on the Near End Device
This step applies to Flex-1. You only need to enable Y.1564 once; all SAT tests are created without performing this step again.
- Enable the Y.1564 system:
config terminal; no shutdown y1564; end
- Enable the Y.1564 module:
config terminal; y1564 enable; end
- Set Flow Bytes mode to Layer 2 (Layer 2 is default):
config terminal; y1564 flow-bytes mode layer2; end
Procedure
Import the Flow Profile
You must import a flow profile the first time you use the SAT test on Assurance Sensor F100 or F25 from Legacy orchestrator.
Subsequent CLI Sets and SAT test flow templates will be automatically imported.
flowProfileExportForSAT.profile
Note: If you have already imported the file, skip this step.
To Import a Configuration flow profile
Access the page Commissioning ▶ Flow Profiles.
Click the Import flow button. The Commissioning file import dialog is displayed.
Browse to the flowProfileForSAT.profile file and click the Import button. The import status is indicated in the Commissioning file import dialog.
Close the Import devices dialog.
Create Flow Executor for SAT Test
After the preconditions are met and importing is complete, create the flow executor supports for the SAT test.
To create a SAT test through flow executor
Access the page Commissioning ▶ Flow Executors.
Select the Add flow executor button. The Profile selection tab is above.
Enter a name for the executor in the Executor name field.
In the Profile name tab, check the profile of the SAT type that you want to execute. Only one profile can be selected.
Select the Device selection tab for the near end device; Flex-1.
Drag devices from the list of available devices (in the left pane) to the appropriate group of target devices (in the right pane).
Select the Parameters Input tab.
Enter values for all parameters in the list. Refer to required parameters.
Click Apply.
Select the Execution status tab and click the Start Executor button to immediately execute the configuration flow.
Use Cases
Use case | Modes | Description |
---|---|---|
Create, start and show new SAT |
| Use flow executor type 1 the next time you complete the SAT. |
Update, start and show SAT - Ascending mode |
| If you update the SAT with the mode in this order, only use flow executor type 1 the next time you complete the SAT. |
Update, start and show SAT -Descending mode |
| If you update the SAT with the mode in this order, you must use flow executor type 2 to delete the traffic profile, SAC, and service configuration. Then, you must reconfigure it as flow executor type 1 to complete the SAT. |
Flow Executor Type 1
Create, start, and show SAT test
Notes: Before creating the SAT test flow executor, ensure that flow profiles are imported.
If you run flow executor type 1 for the first time, Before CLI script name must be empty.
Note: If you run flow executor type 1 again, add Unassign Y1564 SLA to Before script and then reapply the flow template and flow profile.
Example
Using Y1564 Service Configuration - SAC - SLA - Untagged flow profile to begin the SAT test
Access the page Commissioning ▶ Flow Executors.
Select the Add flow executor button. The Profile selection tab is above.
Enter a name for the executor in the Executor name field.
In the Profile name tab, check Y1564 Service Configuration - SAC - SLA - Untagged flow profile.
Select the Device selection tab for the near end device; Flex-1.
Drag devices from the list of available devices (in the left pane) to the appropriate group of target devices (in the right pane).
Select the Parameters Input tab.
Enter values for all parameters in the list. Refer to required parameters.
Click Apply.
Select the Execution status tab and click the Start Executor button to immediately execute the configuration flow.
View the final SAT test result in the CLI of Flex-1:
- Display the test result:
show y1564 service-configuration-report sla-id ${Y1564_SLA_ID}
- Display the test result with performance:
show y1564 service-performance-report performance-id ${Y1564_SERVICE_PER_TEST_ID}
Flow Executor Type 2
Delete Y.1564 SLA
Note: When deleting Y.1564 SLA, you must also delete SAC, traffic profile, and service configuration.
Access the page Commissioning ▶ Flow Executors.
Select the Add flow executor button. The Profile selection tab is above.
Enter a name for the executor in the Executor name field.
In the Profile name tab, check Delete Y1564 Traffic Profile flow profile.
Select the Device selection tab for the near end device; Flex-1.
Drag devices from the list of available devices (in the left pane) to the appropriate group of target devices (in the right pane).
Select the Parameters Input tab.
Enter values for all parameters in the list. Refer to required parameters.
Click Apply.
Select the Execution status tab and click the Start Executor button to immediately execute the configuration flow.
Required Parameters
SAT types will have the following required parameters where a value must be entered:
Specific parameters to each SAT type
SAT Type | Required Parameters |
---|---|
Y1564 Service Configuration - SAC - SLA - Untagged | - |
Y1564 Service Configuration - SAC - SLA - Single-tagged |
|
Y1564 Service Configuration - SAC - SLA - Double-tagged |
|
Y1564 Service Configuration - SAC - SLA - Performance - Untagged |
|
Y1564 Service Configuration - SAC - SLA - Performance - Single-tagged |
|
Y1564 Service Configuration - SAC - SLA - Performance - Double-tagged |
|
Delete Y1564 SLA |
|
Common parameters for all SAT types
- TRAFFIC_PROFILE_ID
- TRAFFIC_PROFILE_NNI_INF_ID
- TRAFFIC_PROFILE_DEST_MAC_ADDRESS
- TRAFFIC_PROFILE_SOURCE_MAC_ADDRESS
- SER_CONF_ID
- SER_CONF_CIR
- SER_CONF_CBS
- SER_CONF_EIR
- SER_CONF_EBS
- SAC_ID
- SAC_INFO_RATE
- SAC_FRAME_LOSS_RATIO
- SAC_FRAME_TIME_DELAY
- SAC_FRAME_DEPLAY_VARIATION
- SAC_AVAILABILITY
- SLA_ID
- SLA_CONF_TEST_DURATION
- SLA_EIR_TEST
- SLA_SIMPLE_CIR_TEST
- SLA_STEPLOAD_CIR_TEST
- SLA_TRAFFIC_POLICING_TEST
- SLA_RATE_STEP
- SLA_PACKET_SIZE
- SLA_DURATION
© 2024 Cisco and/or its affiliates. All rights reserved.
For more information about trademarks, please visit: Cisco trademarks
For more information about legal terms, please visit: Cisco legal terms
For legal information about Accedian Skylight products, please visit: Accedian legal terms and tradmarks