Verifying Load Balancing and Redundancy
Verifying Load Balancing
On the server, enable netserver. On clients 1 and 2, use the netperf tool to test server performance:
Client 1: netperf –H 192.168.18.10 –l 30
Client 2: netpert –H 192.168.18.10 –l 30
On the server, use the sar tool to query the number of received packets per second (rxpck/s) at the network port. Ports eth0 and eth1 receive packets, and the total number of received packets is equal to the number of packets received by bond0 per second, as shown in Figure 1.
Figure 1 rxpck/s
The total bandwidth of the server doubles.
Figure 2 Average bandwidth of client 1
Figure 3 Average bandwidth of client 2
If you run ifconfig eth0 down on the server, port eth0 cannot receive packets, and only port eth1 receives packets. In this case, the rxpck/s of port eth1 is equal to the rxpck/s of bond0, as shown in Figure 4.
Figure 4 rxpck/s of port eth1
This indicates that when any port working in load balancing mode is disabled, only network bandwidth is affected, and network connection remains normal.
On the client, configure an IP address that is in the same network segment as the server, such as 192.168.18.11. Ping the bonded IP address 192.168.18.10:
When network cables are connected to ports eth0 and eth1, the IP address can be pinged.
Remove the network cable from port eth0. The IP address can be pinged.
Reconnect the network cable to port eth0 and remove the network cable from port eth1. The IP address can be pinged.
Query the Address Resolution Protocol (ARP) on the client. The IP address 192.168.18.10 maps only the Media Access Control (MAC) address 00:10:e0:fc:f4:68.