- Print
- PDF
Use a test suite to determine whether a network section or a device conforms to a Service Level Agreement (SLA) or an Ethernet standard. This procedure consists of:
- Setting up a test suite
- Running a test suite
- Viewing a test report
Note: SAT Reporting is a system feature that enables you to have RFC-2544 or Y.1564 test reports automatically pushed from the unit to a designated remote server (FTP, FTPS, SFTP, TFTP, or SCP). Automatically pushing test reports to the server means that you can view the test results quicker since you do not have to manually poll the remote server to determine whether or not the test has completed execution. For details on how to automate report uploads to a remote server, see Setting Up SAT Reporting.
Setting Up a Test Suite
When configuring a test suite, enable one or more of the following tests:
- Throughput
- Frame loss
- Delay
- Back-to-back
See the table Test to Run for a description of each test.
You must set information pertaining to the remote peer (Peer settings) and the test frame contents. The configurable parameters available depend on the type of test traffic.
Note: The unit contains pre-programmed loopbacks for layer-2 or layer-2 Accedian frames. For layer-2 generic traffic or layer-3/layer-3 generic testing with UDP segments, you must program the peer unit to have a manual loopback to match the test traffic, with a swapping action on the MAC addresses, IP addresses, and port numbers as needed. You can do this through the menu.
To set up a test suite
Access the page SAT ▶ RFC-2544 ▶ Testsuite ▶ Configuration.
A summary of all test suites that have been set up displays.
Click Add to add a new test suite.
or
Click the name of an existing test suite to edit its settings.
Select the tests to run, complete their corresponding settings and other required fields, and then click Apply.
For more information on specific parameters, refer to the following table:
RFC-2544 testsuite configuration (SAT ▶ RFC-2544 ▶ Testsuite ▶ Configuration)
Parameter | Description |
---|---|
Name / Suite name | Test suite name. Only one test suite can be created per device. |
Description / Suite description | Description configured to identify the test suite and its characteristics. |
Jumbo frame size | Size, expressed in bytes, of the user-defined jumbo frame that will be used for the tests if selected. Default: 2000 bytes Range: 1518–10240 bytes Note: The size must be less than or equal to the port's MTU. |
Binary duration | Duration, expressed in seconds, of each trial completed during the binary search for the maximum throughput. Default: 2 seconds Range: 1–10 seconds |
Outgoing port | Port from which to send the flows. |
Enable strict failure | Select to enable failure on Out of Order (OOO) or duplicate frames/packets. Out of Order frames/packets are frames/packets that are received in a different order than what they were sent in. When strict failure is enabled, OOO or duplicate frames/packets will cause a test to fail, even if all frames/packets were received. When strict failure is disabled, the unit tolerates OOO and duplicate frames/packets. If all frames/packets were received, the test is marked as passed. |
Enable verbose report | Select to have all tests (including any tests that failed) and executed steps appear in the test report. |
Exclude VLAN size | Select to exclude the VLAN size. When excluding the VLAN size, the frame length is increased by the size of the VLAN tag header(s) being added to the frame. Note: Enabling this parameter does not affect the Frame size that will appear in the test report. |
Test to Run
Parameter | Description |
---|---|
Enable throughput | Select to enable the throughput test. The throughput test begins by determining the maximum rate at which the test settings yield no lost frames. For example, to measure the quality of a wire-speed GigE circuit, enter a Minimum Rate of 800 Mbps, a Maximum Rate of 1000 Mbps, a Step Size of 10 Mbps, and a Binary Duration of 2 seconds. The unit then performs a binary search between 800 Mbps and 1000 Mbps for 2 seconds using 10 Mbps increments in order to determine the highest rate at which the test can be performed without failing. Once the maximum rate is determined, the throughput test starts executing the actual test, which involves sending frames according to the selected Frame Size settings for the duration specified by the Trial Duration. |
Enable delay | Select to enable the delay and delay variation test. Once a wire-speed rate with no frame loss has been defined by the throughput test, the delay and delay variation test measures the latency and jitter at that specific rate. Ensure to enter all required parameters in the Throughput settings section as some of these parameters are required by this test. |
Enable frame loss | Select to enable the frame loss test. The frame loss test verifies that no frames are lost when the current test settings are used. The unit starts at the maximum rate defined in the Throughput settings section, then steps down by the value entered in the Step Size parameter of the Frame Loss settings. Two consecutive rates must have no frame loss in order to successfully pass this test. For example, if the Unit Under Test (UUT) is able to perform full wire-speed at GigE, the test runs at 1000 Mbps and 980 Mbps (for a Step Size of 20 Mbps). Both tests must yield no frame loss in order to be successful. Otherwise, a lower rate will be tested. Ensure to enter all required parameters in the Throughput settings section as some of these parameters are required by this test. |
Enable back-to-back | Select to enable the back-to-back test. The back-to-back test sends a minimum of 50 repetitive bursts of frames with minimum inter-frame gap (line rate) according to the test settings. For this test to be successful, the network being tested must not lose any frames after a burst. A two-second pause is inserted after each burst. Ensure to enter all required parameters in the Throughput settings section as some of these parameters are required by this test. |
Peer settings
Parameter | Description |
---|---|
Type | Type of test traffic. May be one of the following:
|
MAC destination | Peer MAC address. Applies to layer-2 and layer-3 generic traffic only. Note: Layer-3 generic traffic is available for the traffic generator and test suite. It is not available for Y.1564 SAT. |
Y.1731 MEG level | Maintenance Entity Group level. Applies to layer-2 traffic only. For details, refer to ITU-TY.1731. |
Destination IP address | IP address of the remote unit interface. Applies to layer-3 and layer-3 generic traffic only. |
DSCP | DiffServ Code Point to set in the generated packets. Applies to layer-3 and layer-3 generic traffic only. |
Source port | Near-end UDP port number used to generate the test's PDU. Applies to layer-3 and layer-3 generic traffic only. |
Source IP address | Source IP address used for the IP header. Applies to layer-3 generic traffic only. |
Destination port | Far-end UDP port number associated with the IP address of the unit that will receive, process, and display the traffic statistics and report. Applies to layer-3 and layer-3 generic traffic only. Note: 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 a proprietary port number. For information on destination ports default values, refer to "Network Requirements — TCP/UDP Ports". A port cannot be defined as the UDP port here if it is already in use for any of the following features:
|
TTL | The Time To Live (TTL) of the packets transmitted on the flow. Applies to layer-3 and layer-3 generic traffic only. |
Enable VLAN 1 header | Check box to encapsulate all frames with one VLAN header. |
VLAN 1 ID | First VLAN ID. When enabled, all test frames are encapsulated with the specified VLAN ID. |
VLAN 1 Ethernet type | First VLAN Ethernet type. Applies only when the VLAN 1 header is enabled. Possible values are:
Note: The Ethertype associated with the selected value displays in a read-only text box. |
VLAN 1 priority | First VLAN priority bits. Applies only when the VLAN 1 header is enabled. |
VLAN 1 CFI | First VLAN Canonical Format Indicator (CFI). Applies only when the VLAN 1 header is enabled. |
Enable VLAN 2 header | Check box to encapsulate all frames with two VLAN headers (as in QinQ). VLAN 1 must be enabled to use two VLAN headers. |
VLAN 2 ID | Second VLAN ID. When enabled, all test frames are encapsulated with the second specified VLAN ID (inner VLAN). Applies only when the VLAN 2 header is enabled. |
VLAN 2 Ethernet type | Second VLAN Ethernet type. Applies only when the VLAN 2 header is enabled. Possible values are:
|
VLAN 2 priority | Second VLAN priority bits. Applies only when the VLAN 2 header is enabled. |
VLAN 2 CFI | Second VLAN Canonical Format Indicator (CFI). Applies only when the VLAN 2 header is enabled. |
Throughput settings
Parameter | Description |
---|---|
Trial duration (s) | Period of time over which the throughput test will run. Range: 1–1,800 seconds Default: 60 seconds |
Maximum rate (Mbps) | Upper bound of the rates for which to search, expressed in Mbps. Range: 1– 10000 Mbps (10 Gbps). In steps of 0.125 Mbps for rates from 0–12.5 Mbps, and in steps of 1 Mbps for rates greater than or equal to 13 Mbps. You must select a Maximum Rate that does not exceed the capacity of the outgoing port being used for the test suite. Failure to do so may produce inaccurate results. Note: The actual transmission rate (TX rate) used during the throughput test will not necessarily match the value of the Maximum Rate parameter since the transmission rate depends on the results obtained from the binary search algorithm. This parameter also applies to the delay and delay variation test, as well as to the frame loss test. |
Minimum rate (Mbps) | Lower bound of rates for which to search, expressed in Mbps. Range: 1– 10000 Mbps (10 Gbps). In steps of 0.125 Mbps for rates from 0–12.5 Mbps, and in steps of 1 Mbps for rates greater than or equal to 13 Mbps. You must select a Minimum Rate that does not exceed the capacity of the outgoing port being used for the test suite. Failure to do so may produce inaccurate results. This parameter also applies to the delay and delay variation test, as well as to the frame loss test. |
Step size (Mbps) | Granularity of the range, expressed in Mbps. Range: A value greater than zero to the maximum rate. |
Use fine stepping | Select to enable fine stepping in the case of low bandwidth testing (below 12 Mbps). When fine stepping is enabled, the configured Step Size is ignored. The step size used for the range is 125 kbps. This parameter also applies to the delay and delay variation test, as well as to the frame loss test. |
Frame loss (0.1%) | Acceptable difference between measured frame losses (n x 0.1%). For example, a setting of 1 would mean a 0.1% frame loss would be acceptable and not considered as a frame loss by the test. Default: 0, which means a target of no frame loss is tolerated when defining full throughput, i.e. losing a single frame will cause the test to fail. |
Frame size settings | Select the frame sizes to include in the test. By default, the Jumbo frame size is not selected because it is not a frame size defined by the RFC-2544 standard. Note: Select frame sizes that are smaller than the port's MTU. Selecting a higher frame size will prevent the test from running. |
Delay and delay variation settings
Parameter | Description |
---|---|
Trial duration (s) | Period of time over which the test is run. Range: 1–1800 seconds Default: 120 seconds The delay and delay variation test also uses the Maximum Rate, Minimum Rate, and Fine Stepping values set in the Throughput Settings. |
Frame loss (0.1%) | Acceptable difference between measured frame losses (n x 0.1%). For example, a value of 1 would mean a 0.1% frame loss would be acceptable and considered as no frame loss by the test. Default: 0, which means a target of no frame loss is tolerated when defining full throughput, i.e., losing a single frame will cause the test to fail. |
Frame size settings | Select the frame sizes to include in the test. By default, the Jumbo frame size is not selected because it is not a frame size defined by the RFC-2544 standard. Note: Select frame sizes that are smaller than the port's MTU. Selecting a higher frame size will prevent the test from running. |
Frame loss settings
Parameter | Description |
---|---|
Trial duration (s) | Period of time over which the test is run. Range: 1–1800 seconds Default: 120 seconds The delay and delay variation test also uses the Maximum Rate, Minimum Rate, and Fine Stepping values set in the Throughput Settings. |
Step size (Mbps) | Granularity of the range, expressed in Mbps. |
Frame size settings | Select the frame sizes to include in the test. By default, the Jumbo frame size is not selected because it is not a frame size defined by the RFC-2544 standard. Note: Select frame sizes that are smaller than the port's MTU. Selecting a higher frame size will prevent the test from running. |
Back to back settings
Parameter | Description |
---|---|
Trial duration (ms) | Period of time over which the test is run. Range: 1–10,000 milliseconds Default: 2,000 milliseconds |
Repeat | Number of bursts to perform for each frame/packet size. A two-second pause is inserted after each burst. Default: 50 bursts Range: up to 100 bursts |
Frame size settings | Select the frame sizes to include in the test. By default, the Jumbo frame size is not selected because it is not a frame size defined by the RFC-2544 standard. Note: Select frame sizes that are smaller than the port's MTU. Selecting a higher frame size will prevent the test from running. |
Running a Test Suite
Once you have set up a test suite, you can run it and then view its report. Since each test is associated with one test report, you must configure a new report each time you want to run a new test. You can run a specific test suite several times as long as you configure a new report.
To run a test suite
Access the page SAT ▶ RFC-2544 ▶ Testsuite ▶ Reports.
A summary of all test suite reports displays.
Click Start New Testsuite to configure a new report.
Complete the required fields, then click Run.
For more information on specific parameters, refer to the following table.
RFC-2544 Test Suite Reports (SAT ▶ RFC-2544 ▶Testsuite ▶Reports)
Parameter | Description |
---|---|
File name | Name assigned to the report. |
Status | The test status is displayed for all the reports that have been created. Possible values are:
|
Description | Concise description used to help identify the report. |
Technician name | Name of the individual who executed the test suite. |
Test suite nonfiguration | Select the test suite you want to run for this report. |
Special Note | Any additional report-related details that were not included in the previous field. |
Viewing a Test Report
To view, save, or delete a test suite report
Access the page SAT ▶ RFC-2544 ▶ Testsuite ▶ Report.
A summary of all test suite reports displays.
Click the Name of an existing test suite report to view its report file or to perform other actions.
Note: You can click Stop to stop a test while it is running. You can then click either Save to save it on the management station as a text file or Delete to delete it.
© 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