- What's New
- Function Overview
- Product Bulletin
- Service Overview
- Billing
- Getting Started
- User Guide
-
Best Practices
- Direct Connect Best Practices
- Connecting an On-Premises Data Center to a VPC over a Single Connection and Using Static Routing to Route Traffic
- Connecting an On-Premises Data Center to a VPC over a Single Connection and Using BGP Routing to Route Traffic
- Connecting an On-Premises Data Center to a VPC over Two Connections in Load Balancing Mode (Virtual Gateway)
- Connecting an On-Premises Data Center to a VPC over Two Connections in an Active/Standby Pair (Virtual Gateway)
- Connecting an On-Premises Data Center to Multiple VPCs that Do Not Need to Communicate with Each Other
- Connecting an On-Premises Data Center to Multiple VPCs in the Same Region Using Direct Connect and VPC Peering
- Using a Public NAT Gateway and Direct Connect to Accelerate Internet Access
- Allowing On-Premises Servers to Access Cloud Services Using Direct Connect and VPC Endpoint
-
API Reference
- Before You Start
- API Overview
- Calling APIs
-
API
- Connections
- Virtual Gateways
-
Virtual Interfaces
- Creating a Virtual Interface
- Querying the Virtual Interface List
- Querying Details About a Virtual Interface
- Updating a Virtual Interface
- Deleting a Virtual Interface
- Creating a Virtual Interface Peer
- Updating a Virtual Interface Peer
- Deleting a Virtual Interface Peer
- Performing a Virtual Interface Switchover Test
- Querying the List of Virtual Interface Switchover Test Records
- Tag Management
- Quota Management
- Global DC Gateways
- Peer Links
- Connect Gateways
- Global EIPs
- Global DC Gateway Route Tables
- Public Parameters
- Appendix
- SDK Reference
- Troubleshooting
-
FAQs
-
Popular Questions
- What Are the Network Requirements for Connections?
- What Locations Are Available for Direct Connect?
- How Do I Select a Carrier When Purchasing a Connection?
- How Will I Be Billed for Direct Connect?
- How Do I Submit a Service Ticket?
- How Do I Test the Network Connectivity Between a Location and the Cloud?
- What Do I Do If I Select the Wrong Carrier When Creating a Connection?
-
Product Consultation
- What Are the Network Requirements for Connections?
- What Are 1GE and 10GE?
- What Locations Are Available for Direct Connect?
- Is BGP Routing Supported in Direct Connect?
- What Is Full-Service Installation Statement?
- How Do I Submit a Service Ticket?
- What Are the Network Latency and Packet Loss Rate of a Connection?
- Are the Uplink and Downlink Bandwidths of a Direct Connect Connection the Same?
- What Do I Do If I Select the Wrong Carrier When Creating a Connection?
- How Do I Plan the VPCs for a New Connection?
- What Are Local and Remote Gateways (Interconnection IP Addresses)?
- How Do I Configure BFD for a Connection?
- Leased Line
-
Interconnection with the Cloud
- Can I Access the Same VPC over Multiple Connections?
- How Do I Plan the CIDR Blocks for a Connection?
- What Should I Consider When I Use Direct Connect to Access the Cloud?
- Does Direct Connect Support NAT?
- Can the VLAN of the On-premises Network Be Used in the VPC Through Direct Connect?
- Can My On-Premises Data Center Access Multiple VPCs Through One Connection?
- Can Direct Connect Be Used with Similar Services of Other Cloud Service Providers?
-
Networking and Scenarios
- Can Multiple Connections Access the Same VPC?
- Can My On-Premises Data Center Access Multiple VPCs Through One Connection?
- Can Direct Connect Be Used with Similar Services of Other Cloud Service Providers?
- Can I Limit the Bandwidth Available on Each Hosted Connection?
- How Do I Plan the VPCs for a New Connection?
-
Related Console Operations
- How Do I Submit a Service Ticket?
- How Can I Unsubscribe from Direct Connect?
- What Parameters Can Be Modified After I Have Created a Virtual Interface?
- Do I Need to Delete the Virtual Gateway and Virtual Interface Before Deleting a Hosted Connection?
- How Do I Change the Routing Mode of a Connection?
- How Do I Delete a Hosted Connection?
- What Is the BGP ASN Used by Huawei Cloud?
- What Are Local and Remote Gateways (Interconnection IP Addresses)?
- Troubleshooting
- Billing
- Resource Monitoring
- Quota
-
Popular Questions
-
More Documents
- User Guide (ME-Abu Dhabi Region)
- User Guide (Paris Region)
- eu-west-0-api
- User Guide (Kuala Lumpur Region)
-
API Reference (Kuala Lumpur Region)
- Before You Start
- API Overview
- Calling APIs
- API Usage
-
API
- Connection
- Virtual Gateway
-
Virtual Interface
- Querying Details About a Virtual Interface
- Updating a Virtual Interface
- Deleting a Virtual Interface
- Querying the Virtual Interface List
- Creating a Virtual Interface
- Updating a Virtual Interface Peer
- Deleting a Virtual Interface Peer
- Creating a Virtual Interface Peer
- Performing a Virtual Interface Switchover Test
- Querying the Switchover Test Records of a Virtual Interface
- Tag management
- Quota Management
- Public Parameters
- Appendixes
- Change History
- General Reference
Show all
Copied.
Connection Bandwidth Testing Methods
Scenario
After your on-premises data center is connected to the cloud, you need to test the link performance to ensure that the connection can meet your service requirements. This section describes how you can use iPerf3 to test the bandwidth of a connection.
Prerequisites
- Network connectivity between your on-premises data center and the cloud has been established, and the routes have been configured.
- A network access device is available in the on-premises data center as the client or server in the iPerf3 tests.
- Six ECSs that can access the Internet are available as the clients or servers in the iPerf3 tests. The ECSs establish control connections with the on-premises network access device for transmitting test information and test results.
In this example, the six ECSs use the c7.large.2 flavor and image CentOS 8.2 64bit (40 GB), and their IP addresses are from 172.16.0.2 to 172.16.0.7.
Procedure
- Install iPerf3 and set up the test environment.
Install iPerf3 on the on-premises network access device and on the six ECSs. The following describes how to install iPerf3 on an ECS.
- Log in to the ECS.
- Install iPerf3.
- Download iPerf3.
yum install iperf3
- Check whether the installation is successful.
iperf3 -v
The installation is successful when the system displays the following information:
- Download iPerf3.
- Use iPerf3 to test the bandwidth of a connection.
Table 1 describes the parameters related to iPerf3.
Table 1 iPerf3 parameter description Parameter
Description
-s
A server-specific parameter. It indicates that iPerf3 runs in server mode.
-c
A client-specific parameter. It indicates that iPerf3 runs in client mode.
-i
The interval between reports, in seconds.
-p
- Server: The listening port on the server. The default value is 5201. Both TCP and UDP are listened on.
- Client: The port for the client to connect to the server. The default value is 5201. If the -u parameter also exists, the connection is initiated through UDP. Otherwise, a TCP connection is used by default.
-u
UDP is used to send packets. If this parameter is not specified, TCP is used.
-l
The length of the read/write buffer. The recommended value is 1,400 for testing the bandwidth and 16 for testing the packet forwarding performance.
-b
The bandwidth (in bit/s) used if a UDP connection is established.
-t
The total transmission time, in seconds. It is the duration for iPerf3 to repeatedly send data packets of a specified length within a specified period. The default value is 10 seconds.
-A
CPU affinity. You can bind the iPerf3 process to the logical CPU with the corresponding number to prevent the iPerf3 process from being scheduled among different CPUs.
- Test the bandwidth of the connection with the on-premises network access device functioning as the server.
- Run the following commands on the on-premises network access device to start the iPerf3 process in server mode and specify different ports:
iperf3 -s -i 1 -p 16001 iperf3 -s -i 1 -p 16002 iperf3 -s -i 1 -p 16003 iperf3 -s -i 1 -p 16004 iperf3 -s -i 1 -p 16005 iperf3 -s -i 1 -p 16006
- Run the iperf3 -u -l 1400 -b 100m -t 120 -c server_ip -i 1 -p port command on each ECS to start the iPerf3 process in client mode and specify different ports of the on-premises network access device.
Example commands are as follows:
iperf3 -u -l 1400 -b 100m -t 120 -c 192.168.0.1 -i 1 -p 16001 #First ECS iperf3 -u -l 1400 -b 100m -t 120 -c 192.168.0.1 -i 1 -p 16002 #Second ECS iperf3 -u -l 1400 -b 100m -t 120 -c 192.168.0.1 -i 1 -p 16003 #Third ECS iperf3 -u -l 1400 -b 100m -t 120 -c 192.168.0.1 -i 1 -p 16004 #Fourth ECS iperf3 -u -l 1400 -b 100m -t 120 -c 192.168.0.1 -i 1 -p 16005 #Fifth ECS iperf3 -u -l 1400 -b 100m -t 120 -c 192.168.0.1 -i 1 -p 16006 #Sixth ECS
- Run the following commands on the on-premises network access device to start the iPerf3 process in server mode and specify different ports:
- Test the bandwidth of the connection with the on-premises network access device as a client.
- Run the iperf3 -s -i 1 -p 16001 command on each ECS to start the iPerf3 process in server mode and specify the port.
- Run the following commands on the on-premises network access device to start six iPerf3 processes in client mode:
iperf3 -u -l 1400 -b 100m -t 120 -c 172.16.0.2 -i 1 -p 16001 iperf3 -u -l 1400 -b 100m -t 120 -c 172.16.0.3 -i 1 -p 16001 iperf3 -u -l 1400 -b 100m -t 120 -c 172.16.0.4 -i 1 -p 16001 iperf3 -u -l 1400 -b 100m -t 120 -c 172.16.0.5 -i 1 -p 16001 iperf3 -u -l 1400 -b 100m -t 120 -c 172.16.0.6 -i 1 -p 16001 iperf3 -u -l 1400 -b 100m -t 120 -c 172.16.0.7 -i 1 -p 16001
- Analyze the test result.
After the iPerf3 process on the client is executed, the following information is displayed. The packets per second (PPS) of the tested link can be calculated using the formula: PPS = Number of packets received by the peer end/Time.
[ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams [ 4] 0.00-10.00 sec 237 MBytes 199 Mbits/sec 0.027 ms 500/30352 (1.6%) [ 4] Sent 30352 datagrams
The following table describes the fields in the command output.
Field
Description
Transfer
Transmitted data volume
Bandwidth
Bandwidth of the connection
Jitter
Jitter
Lost/Total Datagrams
Number of lost packets/Total number of packets (packet loss rate)
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot