- Print
- PDF
You can run a test suite to determine whether a portion of the network or even a specific device conforms to either a Service Level Agreement (SLA) or a given Ethernet standard.
When configuring a test suite, you have the choice of enabling one or more of the following types of tests:
- Throughput
- Frame loss
- Delay
- Back-to-back
You must also define specific values related to the remote peer (Peer Settings), as well as the contents of the test frames. The parameters you must configure vary, depending on the type of test traffic the test suite will handle.
Layer 3 Tests
Skylight orchestrator can automatically create, enable and delete remote loopback for your Layer 3 RFC-2544 tests. When the test is started with this configuration, Skylight orchestrator will first create and enable the loopback on the far-end device. Upon completion of the test, Skylight orchestrator will delete the loopback on the far-end device.
To set up an RFC-2544 test
Access the page Service Performance ▶ RFC-2544 ▶ Configuration.
Click the Add RFC-2544 Test Profile button to add a new test profile or double- click an existing test profile to modify the test parameters.
The RFC-2544 Test configuration dialog is displayed.
Click in the Near-end device field.
A list of all managed elements is displayed.Select a device in the list and click OK.
The name of the selected device is displayed in the** Near-end device** field.Configure the test parameters for the various sections of the dialog:
- General
- Near-end settings
- Far-end settings
- VLAN settings
- Global test settings
- Test settings
For more information on specific parameters, see table after this procedure.
6. Click Apply, then click Close.
RFC-2544 Test configuration (Service Performance ▶ RFC-254 ▶ Configuration)
Parameter | Description |
---|---|
Near-end device | Near-end device on which to run the test. When you click in this field, a dialog pops up. You can select a device from the Skylight orchestrator inventory. |
General
Parameter | Description |
---|---|
Suite name | A name for the test suite. A maximum of one test suite can be created per device. |
Suite description | The description configured to identify the test suite and its characteristics. |
Jumbo frame size | The size, expressed in bytes, of the user-defined jumbo frame that will be used, if selected for the tests. |
Binary duration | The duration, expressed in seconds, of each trial completed during the binary search for the maximum throughput. |
Test traffic type | The type of test traffic may be one of the following:
|
Enable strict failure | Select this box 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 | Check box to have all tests (including any tests that failed) and executed steps appear in the test report. |
Exclude VLAN size | Check box to exclude VLAN tag size from the configured frame sizes. |
Near-end settings
Parameter | Description |
---|---|
Near-end IP | The source IP address used for the IP header. Applies to Layer-3 generic and IP multicast traffic only. Notes: Layer-3 generic traffic is available for the RFC-2544 traffic generator and test suite. It is unavailable for Y.1564 SAT. IP multicast traffic is available for the RFC-2544 traffic generator. It is unavailable for the RFC-2544 test suite and Y.1564 SAT. |
Near-end port | The port from which to send the flow(s). To select a port:
|
Near-end UDP port | The near-end UDP port number used to generate the test's PDU. Note: Applies to Layer-3 traffic only. |
DSCP | The DiffServ Code Point to set in the generated packets. Applies to Layer-3 traffic only. |
Y.1731 MEG level | The Maintenance Entity Group level. Range: 0–7 |
Far-end settings
Parameter | Description |
---|---|
Far-end device | The far-end managed element used for two-way tests. To select a device:
|
Far-end IP | The IP address of the far-end device interface. Applies to Layer-3 traffic. |
Far-end device port | The port of the far-end device. Used for Layer-3 two- way tests. |
MAC destination | The peer MAC address. Applies to Layer-2 traffic only. |
L3 two-way loopback | Check this box to enable Layer-3 two-way loopback tests. |
Far-end UDP port | The far-end UDP port number associated with the IP address of the far-end device 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 to 65,535. However, you must not set the destination port value to 8,793 because this is Accedian's proprietary port number. For information on destination ports default values, see Network Requirements — TCP/UDP Ports in the documentation for the selected device. A port cannot be defined as the UDP port here if it is already being used for any of the following features on the selected far-end device:
|
VLAN settings
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:
|
ID (for VLAN 1) | The first VLAN ID. When enabled, all test frames are encapsulated with the specified VLAN ID. |
Ethertype (for VLAN 1) | Make a selection from the drop-down list to indicate the first VLAN Ethernet type. Possible values are:
|
Priority (for VLAN 1) | The first VLAN priority bits. Note: Applies only when the VLAN 1 header is enabled. |
CFI (for VLAN 1) | 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:
|
ID (for VLAN 2) | 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. |
Ethertype (for VLAN 2) | Make a selection from the drop-down list to indicate the second VLAN Ethernet type. Possible values are:
|
Priority (for VLAN 2) | The second VLAN priority bits. Note: Applies only when the VLAN 2 header is enabled. |
CFI (for VLAN 2) | The second VLAN Canonical Format Indicator (CFI). Note: Applies only when the VLAN 2 header is enabled. |
Global test settings
Parameter | Description |
---|---|
Use fine stepping | Check box 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. |
Step size (Mbps) | The granularity of the range, expressed in Mbps. Range: A value greater than zero to the maximum rate. |
Minimum rate (Mbps) | The lower bound of rates for which to search, expressed in Mbps. Range: 1 to 1,000 Mbps. In steps of 0.125 Mbps for rates from 0 to 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. |
Maximum rate (Mbps) | The upper bound of the rates for which to search, expressed in Mbps. Range: 1 to 1000 Mbps. In steps of 0.125 Mbps for rates from 0 to 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. |
Test settings
Parameter | Description |
---|---|
Throughput | Check box 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 selected Frame Size settings for the duration specified by the Trial Duration. |
Duration (s) (for throughput test) | The period of time over which the throughput test will run. Range: 1–1,800 seconds Default: 60 seconds |
Frame loss (0.1%) (for throughput test) | The 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 (for throughput test) | Check boxes to 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: The frame size you select must be smaller than the port's MTU. Selecting a higher frame size will prevent you from running the test. |
Frame loss | Check box 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 that you have entered all required parameters in the throughput settings section, since some of these parameters also apply to the frame loss test. |
Duration (s) (for frame loss test) | The period of time over which the test will run. Range: 1–1800 seconds Default: 60 seconds The frame loss test also uses the Maximum Rate, Minimum Rate and Fine Stepping values set in the Throughput Settings section. |
Step size (Mbps) (for frame loss test) | The granularity of the range, expressed in Mbps. |
Frame size (for frame loss test) | Check boxes to 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: The frame size you select must be smaller than the port's MTU. Selecting a higher frame size will prevent you from running the test. |
Delay variation | Check box 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 that you have entered all required parameters in the throughput settings, since some of these parameters are required by the delay and delay variation test. |
Duration (s) (for delay variation test) | The 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%) (for delay variation test) | The 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 (for delay variation test) | Check boxes to 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: The frame size you select must be smaller than the port's MTU. Selecting a higher frame size will prevent you from running the test. |
Back to back | Check box 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 that you have entered all required parameters in the throughput settings, since some of these parameters are required by the back-to-back test. |
Duration (ms) (for back to back test) | The period of time over which the test is run. Range: 1–10,000 milliseconds Default: 2,000 milliseconds |
Repeat (for back to back test) | The 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 (for back to back test) | Check boxes to 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: The frame size you select must be smaller than the port's MTU. Selecting a higher frame size will prevent you from running the test. |
© 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