---
title: "Set Up a Y.1564 Test"
slug: "setting-up-a-y1564-test"
tags: ["service performance ", "Y.1564", "Test Configuration", "Legacy Orchestrator"]
updated: 2026-07-07T14:04:34Z
published: 2025-02-14T16:30:56Z
canonical: "docs.crossworkassurance.cisco.com/setting-up-a-y1564-test"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.crossworkassurance.cisco.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Set Up a Y.1564 Test

You can configure up to eight flows in a Y.1564 test profile. A Y.1564 test profile includes common parameters that apply to all flows and other parameters that are specific to particular flows.

Flow parameters are grouped in subtabs in the lower half of the Y.1564 test configuration dialog:

- **General:** Common test parameters
- **Bandwidth:** Bandwidth profile
- **Acceptance:** Service acceptance criteria
- **Far-end unit:** Remote device
- **Near-end VLAN:** VLAN configuration for the source device (downstream)
- **Far-end VLAN:** VLAN configuration for the remote device (upstream)
- **Far-end Verification DSCP:** DSCP value comparison
- **Far-end Verification VLAN 1:** VLAN 1 value comparison
- **Far-end Verification VLAN 2:** VLAN 2 value comparison

**To set up a Y.1564 test**

1. Access the **Service Performance ▶ Y.1564 ▶ Configuration** page.
2. Click the **Add Y.1564 Test Profile** ![PLUS BUTTON.png](https://cdn.document360.io/01d1de5e-a375-4fbc-aa82-666ac04c2113/Images/Documentation/PLUS%20BUTTON%289%29.png?sv=2026-02-06&spr=https&st=2026-11-11T00%3A20%3A22Z&se=2026-11-11T01%3A20%3A22Z&sr=c&sp=r&sig=uymw6xoUogwM7CVTIY%2F0H2cndZglEXnIjaigVDaVmqE%3D) button to add a new test profile or double-click an existing test profile to modify the test parameters. The **Y.1564 Test Configuration** dialog is displayed. ![24.09_Setting Up a Y.1564 Test_1.png](https://cdn.document360.io/01d1de5e-a375-4fbc-aa82-666ac04c2113/Images/Documentation/24.09_Setting%20Up%20a%20Y.1564%20Test_1.png?sv=2026-02-06&spr=https&st=2026-11-11T00%3A20%3A22Z&se=2026-11-11T01%3A20%3A22Z&sr=c&sp=r&sig=uymw6xoUogwM7CVTIY%2F0H2cndZglEXnIjaigVDaVmqE%3D)
3. Click the **Source device** field. A list of all managed elements is displayed.
4. Select a device in the list and click **OK**.
5. Configure the global test parameters in the upper half of the **Y.1564 test configuration** dialog:

- For the **Outgoing port**, click the field, then click ![THREE DOT BUTTON.png](https://cdn.document360.io/01d1de5e-a375-4fbc-aa82-666ac04c2113/Images/Documentation/THREE%20DOT%20BUTTON%283%29.png?sv=2026-02-06&spr=https&st=2026-11-11T00%3A20%3A22Z&se=2026-11-11T01%3A20%3A22Z&sr=c&sp=r&sig=uymw6xoUogwM7CVTIY%2F0H2cndZglEXnIjaigVDaVmqE%3D) to display the **Select Outgoing port** dialog.
- Select a port and click **OK**.  

These parameters apply to all flows configured for the Y.1564 tests. For more information on specific parameters, see the table after this procedure.  

![24.09_Setting Up a Y.1564 Test_2.png](https://cdn.document360.io/01d1de5e-a375-4fbc-aa82-666ac04c2113/Images/Documentation/24.09_Setting%20Up%20a%20Y.1564%20Test_2.png?sv=2026-02-06&spr=https&st=2026-11-11T00%3A20%3A22Z&se=2026-11-11T01%3A20%3A22Z&sr=c&sp=r&sig=uymw6xoUogwM7CVTIY%2F0H2cndZglEXnIjaigVDaVmqE%3D)

1. Complete the parameters for each tab in the lower section of the Y.1564 test configuration dialog:

- In the **Far-end unit** tab, click the **Far-end Element** field to choose one of the available devices.
- Enter a valid address in the **Far-end IP** field of the **Far-end unit** tab to automatically populate the **Incoming Port** and **MAC Destination** fields.  

The flows can each be configured using different parameters. For more information on specific parameters, refer to the following table.

1. Click **Apply**, then click **Close**.

**Y.1564 Test configuration (Service Performance ▶ Y.1564 ▶ Configuration)**

| Parameter | Description |
| --- | --- |
| Source device | Device that will be the source of the test. When you click in this field, a dialog pops up. You can select a device from the Legacy Orchestrator inventory |

**General**

| Parameter | Description |
| --- | --- |
| Test name | A name for the Y.1564 test profile. A maximum of 28 characters is supported. Do not include spaces, forward slashes, or backslashes in the name. |
| Test description | A description to identify the Y.1564 test and its characteristics. |
| Delay measurement type | The delay measurement type can be either *one-way delay* or *two- way delay* ***Note:** You must enable the SAT protocol in order to use one-way delay measurements.* |
| Outgoing port | The port on which to send flow(s). SAT capable possible values: - **False**: This port is not SAT capable; ports are not filtered out. - **True**: This port is SAT capable. Ports are filtered and only those that support SAT configurations are visible. |
| Device time SYNC mandatory | Check box to enable or disable mandatory device sync time. When this option is enabled, the tests will be performed only if both devices performing the Y.1564 test are synchronized using one of the supported timing mechanisms. When this option is disabled, the tests will be performed, but valid results will be displayed only if both devices performing the Y.1564 test are synchronized using one of the supported timing mechanisms. This type of test may be useful to test applications where delay is not important, but other parameters, such as CIR or EIR, are important. ***Note:** For one-way delay measurement only.* |

**Duration**

| Parameter | Description |
| --- | --- |
| Configuration step duration (seconds) | The duration, expressed in seconds, of each step during the configuration test. Range: 1–60 seconds. ***Note:** This parameter is also used for the burst SLA Test.* |
| Performance step duration (minutes) | The duration of the performance test, expressed in minutes. **Range:** 1–1,440 minutes |
| Enable configuration test | Check box to enable the configuration test allows use of the policing test and step test under each service (traffic flow) configured. It allows you to run successive tests at rates of 25% CIR, 50% CIR, 75% CIR, and 100% of CIR, CIR+EIR, and Policing. For Policing: - If EIR < 20 % x CIR, Policing Rate = (125 % x CIR) + EIR - If EIR ≥ 20 % x CIR, Policing Rate = CIR + (125 % x EIR) |
| Enable performance test | Check box to enable or disable the performance test. You must configure at least one service when you enable performance test. ***Note:** The performance test is run at 100% CIR.* |
| Enable parallel test | Check box to enable or disable the Parallel Service Configuration test. - **Enable:** All enabled services (traffic flows) are run simultaneously. - **Disable:** All enabled services (traffic flows) are run sequentially. |
| Enable burst SLA test | Enable or disable the burst SLA test. (Default is disabled) |

**General far-end settings**

| Parameter | Description |
| --- | --- |
| Test type | The type of test traffic: - **Layer-2:** Y.1731 LBM frames. - **Layer-2 Accedian:** Y.1731 LBM frames marked with the Accedian Ethertype. - **Layer-2 generic:** Special Y.1731 OpCode frames to be used only with loopback devices based on the *MAC-address swap*. - **Layer-3:** UDP segments to perform a test across a multilayered network. |
| Group reverse tests | - **Checked:** Legacy Orchestrator creates only one test for each remote unit that is featured in an enabled flow having the **OW Reverse Path** option checked. - **Unchecked:** Legacy Orchestrator creates one test for each enabled flow of all remote units that have the **OW Reverse Path** option checked. ***Note:** Applies to Layer-3 tests only.* |
| Near-end UDP port | The near-end UDP port number used to generate the test's PDU. ***Note:** Applies to Layer-3 traffic only.* |
| Far-end UDP port | The far-end UDP port number associated with the IP address of the unit that will receive, process and display the traffic statistics and report. ***Notes:*** *Applies to Layer-3 traffic only.* *For reporting to work properly, you must set the port to a value in the range of 0–65535 but you cannot set the destination port value to 8793, since this is Accedian's proprietary port number. For information on destination ports default values, refer to.* |

**General** (flow parameters)

| Parameter | Description |
| --- | --- |
| Service ID | The Y.1564 service identifier. Values range from 1 to 8 and are not user editable. |
| Service name | Name of the Y.1564 service. |
| Enable service | Enable or disable the service for this Y.1564 test. |
| Policing test | Enable or disable testing above the CIR: - If EIR < 20 % x CIR, Policing Rate = (125 % x CIR) + EIR - If EIR ≥ 20 % x CIR, Policing Rate = CIR + (125 % x EIR) |
| Step test | Enables or disables running successive tests at a rate of 25% CIR, 50% CIR, 75% CIR, 100% CIR, and CIR+EIR. |
| Availability | Selectable check box to indicate availability. |
| Out-of-order percentage | This parameter can be enabled or disabled. When enabled, the Out of Order (OOO) frames/packets count is considered in the pass or fail of the network test. |
| Preserve DSCP and PCP Verification | When this option is enabled, the peer unit verifies that the DSCP/PCP values configured in the test traffic have not changed. If they have changed, the test will fail. ***Note:** Applies to one-way delay tests only.* |

**Bandwidth** (flow parameters)

| Parameter | Description |
| --- | --- |
| CIR | The CIR value provided here can be interpreted as the maximum sustained information rate that the network has committed to transfer while meeting the performance level guaranteed in the Service Level Agreement (SLA). The CIR and EIR values specified in the bandwidth profile are used by the Y.1564 tool to define the Configuration, Performance and Policing Tests to be executed. |
| EIR | The EIR value provided here can be interpreted as the maximum sustained information rate, over and above the CIR, at which traffic is carried though the network, if possible. |
| Frame Size Type | The test will be performed with this type of frame size. |
| Packet Size | The size of each frame for the test traffic. |
| User define | The size of each user-defined packet for the test traffic. |
| Sequence of sizes | For the **EMIX** frame size type, the packet size values used in the test and the specific sequence in which they are sent. |
| Committed Burst Size | The maximum number of kibibytes available for a burst of frames that are sent at the port's speed and remain CIR conformant. Range: 0 to 10,000 KiB. |
| Excess Burst Size | This parameter is not currently used and is grayed out. This is for future implementation only. |

**Acceptance** (flow parameters)

| Parameter | Description |
| --- | --- |
| Frame Transfer Delay | For two-way delay measurements, the delay below which the test passes. Expressed in microseconds. |
| FTD Type | How Frame Transfer Delay (FTD) values will be reported. Possible values: - max - avg |
| Frame Delay Variation | For two-way delay variation measurements, the delay variation below which the test passes. Expressed in microseconds. |
| FDV Type | How Frame Delay Variation (FDV) values will be reported. Possible values: - max - avg |
| Frame Loss Ratio | The ratio below which the test passes. |
| M Factor | The M factor (margin factor) is added to the Service Acceptance Criteria in the policing test to take into account the effect of the CBS and EBS on the total rate. The policing test will pass if IR-T ≤ CIR + EIR + M. Where: - **IR-T:** Total Information Rate - **CIR:** Committed Information Rate - **EIR:** Excess Information Rate - **M:** M factor. Default value: *1 Mbps* |
| Out-of-order percentage (%) | The percentage of Out of Order (OOO) frames/packets. |

**Near-end VLAN** (flow parameters for the downstream VLAN)

| Parameter | Description |
| --- | --- |
| VLAN 1 Header | Check box to enable or disable VLAN 1 header. This encapsulates all frames with one VLAN header. If the VLAN 1 header is enabled, the packet size increases by 4 bytes. For example: - If the packet size is set to 64 and the VLAN 1 header is not enabled, the traffic generator will send packets of 64 bytes. - If the packet size is set to 64 and the VLAN 1 header is enabled, the traffic generator will send packets of 68 bytes. |
| VLAN 1 ID | The first VLAN ID. When enabled, all test frames are encapsulated with the specified VLAN ID. |
| VLAN 1 Ethertype | The first VLAN Ethernet type. Possible values are: - S-VLAN - T-VLAN - C-VLAN ***Note:** Applies only when the VLAN 1 header is enabled.* |
| VLAN 1 Priority | The first VLAN priority bits. ***Note:** Applies only when the VLAN 1 header is enabled*. |
| VLAN 1 CFI | The first VLAN Canonical Format Indicator (CFI). ***Note:** Applies only when the VLAN 1 header is enabled.* |
| VLAN 2 Header | Check box to enable or disable the VLAN 2 header. Encapsulates all frames with two VLAN headers (as in Q in Q). In order to use two VLAN headers, both VLAN 1 and VLAN 2 headers must be enabled. If VLAN 1 and VLAN 2 headers are both enabled, the packet size increases by 8 bytes. For example: - If the packet size is set to 64 and both VLAN 1 and VLAN 2 headers are enabled, the traffic generator will send packets of 72 bytes. |
| VLAN 2 ID | The second VLAN ID. When enabled, all test frames are encapsulated with the second specified VLAN ID (inner VLAN). ***Note:** Applies only when the VLAN 2 header is enabled.* |
| VLAN 2 Ethertype | The second VLAN Ethernet type. Possible values are: - S-VLAN - T-VLAN - C-VLAN ***Note:** Applies only when the VLAN 2 header is enabled.* |
| VLAN 2 Priority | The second VLAN priority bits. ***Note:** Applies only when the VLAN 2 header is enabled.* |
| VLAN 2 CFI | The second VLAN Canonical Format Indicator (CFI). ***Note:** Applies only when the VLAN 2 header is enabled.* |

**Far-end VLAN** (flow parameters for the upstream VLAN; information used to create a reverse path)

| Parameters | Description |
| --- | --- |
| VLAN 1 Header | This encapsulates all frames with one VLAN header. ***Note:** After enabling VLAN 1 header, the packet size increases by 4 bytes and after enabling VLAN 2 header, the packet size increases by 8 bytes.* *For example:* *If the packet size is set to 64 and VLAN 1 header is not enabled: The traffic generator will send 64 bytes packets.* *If the packet size is set to 64 and VLAN 1 header is enabled: The traffic generator will send 68 bytes packets.* *If the packet size is set to 64 and VLAN 2 header is enabled: The traffic generator will send 72 bytes packets.* |
| VLAN 1 ID | The first VLAN ID. When enabled, all test frames are encapsulated with the specified VLAN ID. |
| VLAN 1 Ethertype | The first VLAN Ethernet type. Possible values are: - S-VLAN - T-VLAN - C-VLAN ***Note:** Applies only when the VLAN 1 header is enabled.* |
| VLAN 1 Priority | The first VLAN priority bits. ***Note:** Applies only when the VLAN 1 header is enabled.* |
| VLAN 1 CFI | The first VLAN Canonical Format Indicator (CFI). ***Note:** Applies only when the VLAN 1 header is enabled.* |
| VLAN 2 Header | Encapsulates all frames with two VLAN headers (as in Q in Q). VLAN 1 must be enabled to use two VLAN headers. ***Note:** After enabling VLAN 1 header, the packet size increases by 4 bytes and after enabling VLAN 2 header, the packet size increases by 8 bytes.* *For example:* *1) If the packet size set to 64 and VLAN 1 header is not enabled: The traffic generator will send 64 bytes packets.* *2) If the packet size set to 64 and VLAN 1 header is enabled: The traffic generator will send 68 bytes packets.* *3) If the packet size set to 64 and VLAN 2 header is enabled: The traffic generator will send 72 bytes packets.* |
| VLAN 2 ID | The second VLAN ID. When enabled, all test frames are encapsulated with the second specified VLAN ID (inner VLAN). ***Note:** Applies only when the VLAN 2 header is enabled.* |
| VLAN 2 Ethertype | The second VLAN Ethernet type Possible values are: - S-VLAN - T-VLAN - C-VLAN ***Note:** Applies only when the VLAN 2 header is enabled.* |
| VLAN 2 Priority | The second VLAN priority bits. ***Note:** Applies only when the VLAN 2 header is enabled.* |
| VLAN 2 CFI | The second VLAN Canonical Format Indicator (CFI). ***Note:** Applies only when the VLAN 2 header is enabled.* |

**Far-end unit** (flow parameters)

| Parameters | Description |
| --- | --- |
| Near-end IP | The IP address of the local unit. ***Note:** Applies to one-way Layer-3 reverse-path tests only.* |
| Far-end IP | The IP address of the remote unit. ***Note:** Applies to Layer-3 traffic only.* |
| Incoming Port | The port on which to perform the loopback in the remote NE. ***Notes:*** *Applies to two-way delay measurements only.* *This field is ignored if **TW loopback** is not selected..* |
| DSCP | The DiffServ Code Point to set in the generated packets. ***Note:** Applies to Layer-3 traffic only.* |
| Far-end Element | Use this field to select the far-end device when configuring one of the following: - A one-way reverse path from the far-end device. - A loopback for a two-way Layer-3 test on the remote device. ***Note:** This field is ignored when both the **OW Reverse Path** and the "TW Loopback" parameters are not selected.* |
| OW Reverse Path | Indicates that the remote unit transmits a traffic flow. |
| TW Loopback | If this option is selected, you must select the remote device associated with the Y.1564 flow in the **Far-end element** field. If this option is not selected, the remote network field is ignored and can be left blank. You may choose this configuration if you want to perform a two-way Layer-3 test so you can configure the far-end device as a Layer-3 reflector at a later time. |
| MAC Destination | The peer MAC address. ***Note:** Applies to Layer-2 traffic only.* |
| Y.1731 MEG Level | The Maintenance Entity Group level, as described in ITU-T Y.1731. Range: 0–7 ***Note:** Applies to Layer-2 traffic only.* |

**Far-end Verification DSCP**

| Parameters | Description |
| --- | --- |
| DSCP Check | Check this option if you want the peer unit to verify that the DSCP value in the test traffic has not changed. If it has changed, the test will fail. |
| DCSP Unpreserved | Check this option if you expect the DSCP value to change before it reaches the far end. This option also instructs the peer unit to verify the value received against the one defined for the *Far-End Expected Value*. The test will fail if this criterion is not met. |
| DSCP Value | The value expected by the far-end when the DSCP *unpreserve* option is enabled. |

**Far-End Verification VLAN1 or VLAN2** (flow parameters)

| Parameters | Description |
| --- | --- |
| No VLAN 1 Check No VLAN 2 Check | Check this option if you want to validate that the frames received at the far-end do not have a first (or second) VLAN tag, i.e. that far-end frames are untagged. |
| VLAN 1 PCP Check VLAN 1 PCP Check | Check this option if you want the peer unit to verify that the PCP value in the test traffic has not changed. If it has changed, the test will fail. |
| VLAN 1 PCP Unpreserved VLAN 2 PCP Unpreserved | Check this option if you expect the PCP value to change before it reaches the far-end. This option also instructs the peer unit to verify the value received against the one defined for the *Far-End Expected Value*. The test will fail if this criterion is not met. |
| VLAN 1 PCP Value VLAN 2 PCP Value | The value expected by the far-end when the PCP *unpreserve* option is enabled. |
| VLAN 1 DEI Check VLAN 1 DEI Check | Check this option if you want the peer unit to verify that the DEI value in the test traffic has not changed. If it has changed, the test will fail. |
| VLAN 1 DEI Unpreserved VLAN 2 DEI Unpreserved | Check this option if you expect the DEI value to change before it reaches the far end. This option also instructs the peer unit to verify the value received against the one defined for the *Far-End Expected Value*. The test will fail if this criterion is not met. |
| VLAN 1 DEI Value VLAN 2 DEI Value | The value expected by the far-end when the DEI *unpreserve* option is enabled. |
| VLAN 1 ID Check VLAN 1 ID Check | Check this option if you want the peer unit to verify that the VLAN ID for the test traffic has not changed. If it has changed, the test will fail. |
| VLAN 1 ID Unpreserved VLAN 2 ID Unpreserved | Check this option if you expect the VLAN ID to change before it reaches the far end. This option also instructs the peer unit to verify the value received against the one defined for the *Far-End Expected Value*. The test will fail if this criterion is not met. |
| VLAN 1 ID Value VLAN 2 ID Value | The value expected by the far-end when the ID *unpreserve* option is enabled. |

**© 2026 Cisco and/or its affiliates. All rights reserved.** For more information about trademarks, please visit: [Cisco trademarks](https://www.cisco.com/c/en/us/about/legal/trademarks.html)[](https://www.cisco.com/c/en/us/about/legal/trademarks.html) For more information about legal terms, please visit: [Cisco legal terms](https://www.cisco.com/c/en/us/about/legal/terms-conditions.html)