.svg?sv=2022-11-02&spr=https&st=2024-12-23T00%3A53%3A56Z&se=2024-12-23T01%3A03%3A56Z&sr=c&sp=r&sig=8a%2FlKY1dXXV8zZr7Xxc6BubT3NYZlrmxFplYITZOwdU%3D){kind=logo}
Performance Session Metrics
- 19 Sep 2024
- 3 Minutes to read
- Contributors
- Print
- PDF
Performance Session Metrics
- Updated on 19 Sep 2024
- 3 Minutes to read
- Contributors
- Print
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
This article lists the metrics reported for each session type and indicates how metrics are collected.
Metrics Collection and Export
Legacy orchestrator handles collection of metrics from performance sessions in the same way as other metrics collected from devices.
After session data is collected, it can be transferred to another system (such as Provider Connectivity Assurance) for visualization and analysis. The data can be transferred in two ways:
- Exported from Legacy orchestrator as CSV files. This method allows you to export data in a CSV format that is consistent with the format used for other Cisco products including Provider Connectivity Assurance Sensors and the Provider Connectivity Assurance Sensor Control. For more information about the format of the CSV files exported by Legacy orchestrator, see the CSV File Description.
You enable (or disable) export of session metrics in the Collection ▶ Server Configuration page. The data will be transferred to the same export destination as the metrics collected directly from devices. For more information, see "Configuring Global Collection Settings".
It is also possible to export a subset of the metrics collected (rather than the full set of metrics described in "Metrics Reported"). This is done on the Legacy orchestrator command line (Appliance Monitor). It involves applying an export template. The template is applied to sessions of all types. For more information about creating and applying an export template, see: "Exporting Performance Data" in the Legacy orchestrator Administration Guide.
- Retrieved from Legacy orchestrator in XML format. Other systems can pull session data from Legacy orchestrator in XML format using http(s) requests. For more information about this way of transferring performance data, see the XML Export Manual.
Metrics Reported
The following table gives an overview of the metrics collected by the different types of performance sessions supported by Legacy orchestrator.
Metrics Reported per Performance Session Type
| Session Type | Uses and Applicability |
|---|---|
| Echo-ICMP Echo-UDP | Two-Way metrics:
|
| ETH-DM Ethernet Frame Delay Measurement (based on Y.1731 or IEEE 802.1ag) | One-way metrics:
|
| ETH-LB Ethernet Loopback (based on Y.1731 or IEEE 802.1ag) | Two-way metrics:
|
| ETH-VS Ethernet Vendor Specific (based on Y.1731) | 2xOneWay is the Vendor Specific PDU (ETH-VSP) that Legacy orchestrator supports. One-way metrics:
|
| TWAMP Stateful | TWAMP sessions report separate result data for each direction: uplink and downlink directions as default. If Round trip delay is enabled, TWAMP sessions report separate result data for each direction: uplink, downlink, and round trip directions. One-way metrics:
|
| TWAMP Stateless | The same metrics are measured and reported as for One-way Active Measurement Protocol (OWAMP) sessions. TWAMP sessions report separate result data for each direction: uplink and downlink directions. One-Way metrics:
|
| 2xOneWay | The same metrics are reported as for TWAMP stateful sessions. |
© 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?