.svg?sv=2022-11-02&spr=https&st=2024-12-23T05%3A58%3A31Z&se=2024-12-23T06%3A08%3A31Z&sr=c&sp=r&sig=wjVhyG9x6LcdHzvru%2BGJkica6mEkQspoUQ8Q0pcJXOA%3D){kind=logo}
Running a Y.1564 Test
- 19 Sep 2024
- 2 Minutes to read
- Contributors
- Print
- PDF
Running a Y.1564 Test
- Updated on 19 Sep 2024
- 2 Minutes to read
- Contributors
- Print
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
The Y.1564 tests are executed according to how devices were configured.
To run a Y.1564 test
Access the Service Performance ▶ Y.1564 ▶ Configuration page.
Select a test profile. You can select several tests by clicking while holding down the Ctrl or the Shift key on your keyboard.
Note: It may be useful to filter the test profiles in order to focus on the tests you have configured.
Click the Start Y.1564 Test ▶ button to display the Y.1564 test activation configuration window.
Enter values as required. For details on specific parameters, see the table after this procedure.
Note: If you selected multiple tests, the values you enter here will apply to all tests. If you want to enter different values for each test, start each test separately.
- Click Apply to launch the Y.1564 test.
Y.1564 Test Activation Configuration (Y.1564 ▶ Configuration)
| Parameter | Description |
|---|---|
| Force device out of service | This parameter is only used for a Provider Connectivity Assurance Sensor Control that will be used as the near-end element in the test. In this case, the remote device (a Provider Connectivity Assurance Sensor Module or Sensor SFP module) that is selected as the near-end port of the Assurance Sensor Control must be out of service. Checking this box will put the remote device in the out of service state before activating the test. This parameter is ignored for other element models and for an Assurance Sensor Control being used as the far-end in the test. |
| Force loopback override | This offers the user the option of forcing loopback override and continuing the test. |
| Operator name | The name of the individual who executed the test. |
| Description | A concise description of the test. |
| Special note | Any additional information specific to the test appears here. |
When a service activation test is launched by Legacy orchestrator, it will automatically configure the report notification feature of the device to send the completed report to Legacy orchestrator via a secure FTP mechanism. This allows Legacy orchestrator to be aware of a completed test the moment the test completes on the device.
This same mechanism can also be leveraged if a user desires to launch a test directly from the device interface (CLI and/or web). It must be noted that in this case, it is up to the user to configure the report complete notifications to be sent to the Legacy orchestrator. When this is done, result files will be sent to Legacy orchestrator on test completion and will be stored in the Legacy orchestrator database. The result file then becomes visible just as if the test had been launched from Legacy orchestrator.
Note: When a test is launched from Legacy orchestrator, the result file, once transferred to the Legacy orchestrator database, is deleted from the device. In contrast, when the test is launched from the device, Legacy orchestrator will retrieve the result, but the test result will not be deleted from the device.
© 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
Was this article helpful?