Problem Description

Engineers often encounter situations where they need to test Ethernet service pass-through, actual bandwidth, and service packet loss during engineering or Ethernet troubleshooting. When testing service throughput, we can use PING, test frame or OAM function. However, when testing the actual service bandwidth or dealing with packet loss faults, there is no professional test equipment, and there are fewer means to deal with it except RMON. This case is to provide a simple test method to increase the means of dealing with packet loss type faults.

Warning message

RMON can be used to view the sending and receiving of different byte data frames during the test. If the product supports the traffic overrun alarm, it is possible that this alarm will appear during the test.

Processing

The specific use method is as follows:

1. Copy the software directly to the hard disk, such as the root directory of D disk:

2、Run it on two PCs that need to be tested respectively;

One as a server, one as a client.

On the PC as server-side, use: iperf �s

D:>iperf -s

Used on the PC as client: iperf �c ipaddress (whereipaddress is the IP address of the server-side PC )

D:>iperf �c serveripaddress

3. Run on the PCs at both ends of the Ethernet service respectively, the test process is completed automatically, and the packet with TCP port 5001 (the port number on the Server side is 5001, and the port on the Client side is random) is used in the default configuration. The result is as follows:

Server side:

D:>iperf -s

- ------- ----------------------------------------------------

Server listening on TCP port 5001

TCP window size: 8.00 KByte (default)

- ------- ----------------------------------------------------

[1896] local 10.12.10.11 port 5001 connected with 10.12.10.28 port 1765

[ ID] Interval Transfer Bandwidth

[1896] 0.0-10.0 sec 107 MBytes 94.7 Mbits/sec

client side:

D:>iperf -c 10.12.10.11

- ------- ----------------------------------------------------

Client connecting to 10.12.10.11, TCP port 5001

TCP window size: 8.00 KByte (default)

- ------- ----------------------------------------------------

[1916] local 10.12.10.28 port 1765 connected with 10.12.10.11 port 5001

[ ID] Interval Transfer Bandwidth

[1916] 0.0-10.0 sec 107 MBytes 94.7 Mbits/sec

The result of the above test is 94.7 Mbits/sec (for a 100M computer pair). The value of the test for official use is based on the actual configuration of the Ethernet service.

4. By default, iperf.exe uses TCP protocol, according to the actual situation of the field service, you can use the -u parameter to select UDP protocol; you can use the -p parameter to set up the test port (the above modifications can be used for firewall testing, etc.). You can also use the -h parameter to view the use of all supported parameters. Since optical networking products currently support fewer Ethernet features, the use of other parameters of iperf.exe will not be introduced;

Root Cause

iperf.exe is a small piece of software that runs under DOS, and its actual use requires that it be run on a test PC at each end of the Ethernet service.

Recommendations and Summary

Note:

1. The accuracy of this software in testing the actual bandwidth is not very high. For example, if you bind 5VC12s and the actual bandwidth is 10M, the test result can reach about 9M. Therefore, this test method is not suitable for scenarios that require high testing accuracy. If you need accurate test results or to use professional test equipment, or professional test software (such as: Solarwind, Chriot, etc., these software can be found on the Internet );

2, the software can also verify the QoS function of the optical network data veneer, the same precision is not very high, but can basically explain the problem;

3, the software is inaccurate to test the bandwidth of 1000M or higher rates, because the test software relies on the performance of the computer, for engineers to use the general computer although the network port for 1000M, but the actual computer bus and can not reach this rate;

4, in dealing with failures caused by packet loss, the software plays a role: verify the actual bandwidth of the equipment for different protocols packet processing. General handling of such failures, if the verification of the completion of the equipment on different protocols to deal with no bandwidth limitations, but also need to work with Sniffer, Ethereal and other professional packet analysis software to run on the business link to analyze the specific protocols (the content of the main content of the case is not, and is more complex, you need to be very familiar with a variety of protocols for data);

5, similar to the test of small software and WTCP, etc., the use of its methods and effects and iperf similar, personally believe that as long as the mastery of a sufficient;

6, due to the test software main user bandwidth test, so before the test to use ping and other means to confirm the connectivity of the business;