Data Service Performance Test

In this user interface, you can test the E-Line service indicators such as the throughput and latency on the U2000 Web LCT, so as to avoid costly and inefficient meter test.

Navigation Path

In the NE Explorer, select an NE and choose Diagnosis&Maintenance > Data Service Performance Test from the Function Tree.

Application Scenarios

Data service performance tests are performed in the following two scenarios:
  • UNI-UNI: Both ends of an E-Line service are based on VLANs, that is, PORT+VLAN.
  • UNI-NNI: The source end of an E-Line service is based on an S-VLAN or C-VLAN, that is, PORT+SVLAN/CVLAN. The sink end is based on a PW. This scenario applies to hybrid MSTP NEs and RTN 900 NEs.

The following part uses the UNI-UNI scenario as an example.

Figure 1 Test connection diagram

Figure 1 shows the test procedure, using the Ethernet service between PORT1 on NEA and PORT2 on NEB as an example. NEA is tested as source, NEB is tested as sink.

  1. Change the TAG attribute of the Ethernet service. Set Tag to Access. Set Default VLAN ID to the VLAN ID of the tested E-Line service.
  2. Set NEB as the sink node for the test.
  3. Set NEA as the source node for the test. Then start the test.
  4. After the progress bar indicates that the test is 100% complete, set Source Status and Sink Status to Disabled for the related ports (port 1 of NE A and port 2 of NE B in this example).
NOTICE:
  • The test can be started on only the source node.
  • The ports at the ends of the Ethernet service to be tested must be Ethernet ports. During the test, the other Ethernet services on the related ports are interrupted.
  • If the tested service is configured with QoS, OAM, LAG, inband DCN or any data transmission protocol, the precision of test results may be affected. To ensure the precision of test results, it is recommended you delete the above configurations.
  • If the enabled source port of the tested service also transmits other services, the precision of test results may be affected. To ensure the precision of test results, it is recommended you disconnect the port from the other services.

Buttons

Button

Description

Start

Starts testing the short-term throughput, latency, and packet loss.

The test results can be viewed on the Throughput, Latency, and Latency tabs in the lower pane.

NOTICE:

Exercise caution when performing this operation because it may cause service interruption.

NOTE:

After clicking Start, you can set the frame length in the dialog box displayed. The default value is All item.

Specified frame length is displayed only for enabled services.

The frame length setting applies to tests on the throughput, latency, and packet loss rate at the same time.

Stop

Stops testing the short-term throughput, latency, and packet loss.

You can stop a test manually no matter whether it is ongoing or complete.

Start Long-term Test

Starts testing the long-term packet loss.

The test results can be viewed on the Long-term Packet Loss Rate tab in the lower pane.

NOTICE:

Exercise caution when performing this operation because it may cause service interruption.

Stop Long-term Test

Stops testing the long-term packet loss.

You can stop a test manually no matter whether it is ongoing or complete.

Apply

Applies the configured or modified test parameters to NEs to make the settings take effect. The test can be started only after you click Apply.

Export Report

Exports the test results to a table.

In a test service, the report for short-term throughput, latency, and packet loss rate, and the report for long-term packet loss rate are exported to the same table. In the table, the untested items are blank.

NOTE:

Testing multiple services of the same Ethernet port simultaneously is not supported. Therefore, test one service on the Ethernet port at a time.

In addition, the short-term and long-term tests cannot be performed simultaneously. Perform the short-term test first and perform the long-term test after the short-term test is finished.

Parameters

Field

Value

Description

Test Name

Example: test1234

Indicates the name of the test.

A test name does not allow 8 or more characters. It uniquely identifies a test on an NE.

NOTE:

This parameter can be set only when the source or sink node is set to Enabled.

Service Name

Example: service_1

Indicates the name of the service.

Tested As

Source, Sink

Specifies whether to test the service as source or sink. The test can be started only when the service is set to Source.

NOTE:

This parameter can be set only when the source or sink node is set to Enabled.

Source Node

Example: 4-EM6F-1(PORT-1)

Indicates the source node of the service.

Source Status

Enabled, Disabled

Specifies whether to enable the source node of the service.

NOTE:
  • The test can be started only when one end of the service is set to Enabled and the other end is set to Disabled.
  • When both the source and sink nodes are Disabled, the test cannot be started.
  • In the UNI-NNI scenario, only Source Status can be set to Enabled.

Sink Node

Example: 4-EM6F-2(PORT-2)

Indicates the sink node of the service.

Sink Status

Enabled, Disabled

Specifies whether to enable the sink node of the service.

NOTE:
  • The test can be started only when one end of the service is set to Enabled and the other end is set to Disabled.
  • When both the source and sink nodes are Disabled, the test cannot be started.
  • In the UNI-NNI scenario, only Source Status can be set to Enabled.

Progress

Example: 20%

Indicates the test progress.

When the progress bar is displayed as 100%, the test is complete.

Service ID

Example: 1

Indicates the ID of the test service.

Frame Length (Bytes)

64, 128, 256, 512, 1024, 1280, 1518, All item

Indicates the frame length of the test.

  • The short-term test starts with the shortest frame and ends with the longest frame, with the frame length increasing accordingly. You can get results of the tests that are performed in specified frame length and at different throughput percentages.
  • The long-term packet loss test is performed in a fixed frame length and at a fixed throughput percentage. Therefore, the frame length must be set in advance.

Throughput (kbit/s)

Example: 45

Indicates the throughput of the service.

That is, the number of bits transmitted per second in a physical link.

Throughput Percentage (%)

80, 90, 100

Indicates the throughput percentage. That is, the percentage of test—packet rate in throughput when testing latency, packet loss ratio or long-term packet loss ratio.

  • The test for short-term throughput, latency, and packet loss rate is performed at different throughput ratios accordingly in specified frame length, so as to obtain comprehensive results.
  • The test for long-term packet loss rate is performed in a fixed frame length and at a fixed throughput percentage. Therefore, the throughput percentage must be set in advance.

Latency (us)

Example: 10

Indicates the latency of the test.

The throughput is affected by the latency. The longer the latency, the less the throughput.

Packet Loss Ratio (%)

Example: 0.1

Indicates the rate of lost data packets to the sent data packets. This parameter is usually tested at a specified throughput percentage. The packet loss rate is associated with the packet length and sending frequency.

The throughput is affected by the packet loss rate. The higher the packet loss rate, the less the throughput.

Number of Received Packets

Example: 8

Indicates the number of packets received in a fixed frame length and at a fixed throughput percentage.

Number of Sent Packets

Example: 8

Indicates the number of packets sent in a fixed frame length and at a fixed throughput percentage.


Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.