Bonding
These scenarios cover some aspects related to link-aggregation, which is the technique of combining multiple network connections in parallel in order to increase throughput, to provide redundancy or both. On OSDx, this can be achieved by using bonding interfaces.
Test Round-Robin Mode
Description
A bonding interface is configured in DUT0 using the round-robin mode. This mode can be used to achieve load-balancing.
Scenario
Step 1: Set the following configuration in DUT0
:
set interfaces bonding bond0 miimon 100 set interfaces bonding bond0 address 192.168.100.10/24 set interfaces ethernet eth0 bond-group bond0 set interfaces ethernet eth1 bond-group bond0 set interfaces bonding bond0 mode round-robin
Step 2: Set the following configuration in DUT1
:
set interfaces ethernet eth0 address 192.168.100.20/24
Step 3: Run command interfaces bonding show
at DUT0
and check if output matches the following regular expressions:
bond0\s+192.168.100\.10\/24\s+up\s+upShow output
------------------------------------------------------------------ Name IP Address Admin Oper Vrf Description ------------------------------------------------------------------ bond0 192.168.100.10/24 up up fe80::dcad:beff:feef:6c11/64
Step 4: Run command interfaces bonding bond0 show ports
at DUT0
and check if output contains the following tokens:
Bonding Mode: load balancing (round-robin)Show output
Ethernet Channel Bonding Driver: v5.10.127 Bonding Mode: load balancing (round-robin) MII Status: up MII Polling Interval (ms): 100 Up Delay (ms): 0 Down Delay (ms): 0 Peer Notification Delay (ms): 0 Slave Interface: eth1 MII Status: up Speed: Unknown Duplex: Unknown Link Failure Count: 0 Permanent HW addr: de:ad:be:ef:6c:11 Slave queue ID: 0 Slave Interface: eth0 MII Status: up Speed: Unknown Duplex: Unknown Link Failure Count: 0 Permanent HW addr: de:ad:be:ef:6c:10 Slave queue ID: 0
Step 5: Ping IP address 192.168.100.20
from DUT0
:
admin@DUT0$ ping 192.168.100.20 count 2 size 56 timeout 1Show output
PING 192.168.100.20 (192.168.100.20) 56(84) bytes of data. 64 bytes from 192.168.100.20: icmp_seq=1 ttl=64 time=0.510 ms 64 bytes from 192.168.100.20: icmp_seq=2 ttl=64 time=0.358 ms --- 192.168.100.20 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 11ms rtt min/avg/max/mdev = 0.358/0.434/0.510/0.076 ms
Step 6: Run command interfaces ethernet clear
at DUT0
.
Step 7: Initiate a bandwidth test from DUT0
to DUT1
admin@DUT1$ monitor test performance server port 5001 admin@DUT0$ monitor test performance client 192.168.100.20 duration 5 port 5001Expect this output in
DUT0
:Connecting to host 192.168.100.20, port 5001 [ 5] local 192.168.100.10 port 37236 connected to 192.168.100.20 port 5001 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 33.3 MBytes 280 Mbits/sec 6 180 KBytes [ 5] 1.00-2.00 sec 32.1 MBytes 270 Mbits/sec 0 175 KBytes [ 5] 2.00-3.00 sec 34.4 MBytes 288 Mbits/sec 3 222 KBytes [ 5] 3.00-4.01 sec 51.1 MBytes 424 Mbits/sec 40 287 KBytes [ 5] 4.01-5.00 sec 125 MBytes 1.06 Gbits/sec 92 354 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 275 MBytes 462 Mbits/sec 141 sender [ 5] 0.00-5.00 sec 274 MBytes 459 Mbits/sec receiver iperf Done.
Step 8: Run command interfaces ethernet show counters
at DUT0
and check if output matches the following regular expressions:
eth0\s+up\s+\d+\s+\d+\s+0\s+\d{2,} eth1\s+up\s+\d+\s+\d+\s+0\s+\d{2,}Show output
----------------------------------------------------------------------------- Name Oper Rx Packets Rx Bytes Rx Errors Tx Packets Tx Bytes Tx Errors ----------------------------------------------------------------------------- eth0 up 17031 1274384 0 100611 152297655 0 eth1 up 19968 1500631 0 97944 148261471 0
Test Active-Backup Mode
Description
A bonding interface is configured in DUT0 using the active-backup mode. This mode can be used to achieve a higher degree of fault-tolerance.
Scenario
Step 1: Set the following configuration in DUT0
:
set interfaces bonding bond0 miimon 100 set interfaces bonding bond0 address 192.168.100.10/24 set interfaces ethernet eth0 bond-group bond0 set interfaces ethernet eth1 bond-group bond0 set interfaces bonding bond0 mode active-backup
Step 2: Set the following configuration in DUT1
:
set interfaces ethernet eth0 address 192.168.100.20/24
Step 3: Run command interfaces bonding show
at DUT0
and check if output matches the following regular expressions:
bond0\s+192.168.100\.10\/24\s+up\s+upShow output
------------------------------------------------------------------ Name IP Address Admin Oper Vrf Description ------------------------------------------------------------------ bond0 192.168.100.10/24 up up fe80::dcad:beff:feef:6c11/64
Step 4: Run command interfaces bonding bond0 show ports
at DUT0
and check if output contains the following tokens:
Bonding Mode: fault-tolerance (active-backup)Show output
Ethernet Channel Bonding Driver: v5.10.127 Bonding Mode: fault-tolerance (active-backup) Primary Slave: None Currently Active Slave: eth1 MII Status: up MII Polling Interval (ms): 100 Up Delay (ms): 0 Down Delay (ms): 0 Peer Notification Delay (ms): 0 Slave Interface: eth1 MII Status: up Speed: Unknown Duplex: Unknown Link Failure Count: 0 Permanent HW addr: de:ad:be:ef:6c:11 Slave queue ID: 0 Slave Interface: eth0 MII Status: up Speed: Unknown Duplex: Unknown Link Failure Count: 0 Permanent HW addr: de:ad:be:ef:6c:10 Slave queue ID: 0
Step 5: Ping IP address 192.168.100.20
from DUT0
:
admin@DUT0$ ping 192.168.100.20 count 2 size 56 timeout 1Show output
PING 192.168.100.20 (192.168.100.20) 56(84) bytes of data. 64 bytes from 192.168.100.20: icmp_seq=1 ttl=64 time=0.520 ms 64 bytes from 192.168.100.20: icmp_seq=2 ttl=64 time=0.388 ms --- 192.168.100.20 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 2ms rtt min/avg/max/mdev = 0.388/0.454/0.520/0.066 ms
Step 6: Initiate a bandwidth test from DUT0
to DUT1
admin@DUT1$ monitor test performance server port 5001 admin@DUT0$ monitor test performance client 192.168.100.20 duration 5 port 5001Expect this output in
DUT0
:Connecting to host 192.168.100.20, port 5001 [ 5] local 192.168.100.10 port 34198 connected to 192.168.100.20 port 5001 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 36.4 MBytes 306 Mbits/sec 0 747 KBytes [ 5] 1.00-2.00 sec 95.0 MBytes 797 Mbits/sec 42 1.25 MBytes [ 5] 2.00-3.00 sec 141 MBytes 1.18 Gbits/sec 0 1.37 MBytes [ 5] 3.00-4.00 sec 198 MBytes 1.66 Gbits/sec 0 1.47 MBytes [ 5] 4.00-5.00 sec 159 MBytes 1.33 Gbits/sec 0 1.54 MBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 629 MBytes 1.05 Gbits/sec 42 sender [ 5] 0.00-5.01 sec 627 MBytes 1.05 Gbits/sec receiver iperf Done.
Step 7: Run command interfaces bonding bond0 show ports
at DUT0
and check if output contains the following tokens:
Currently Active Slave: eth0Show output
Ethernet Channel Bonding Driver: v5.10.127 Bonding Mode: fault-tolerance (active-backup) Primary Slave: None Currently Active Slave: eth0 MII Status: up MII Polling Interval (ms): 100 Up Delay (ms): 0 Down Delay (ms): 0 Peer Notification Delay (ms): 0 Slave Interface: eth1 MII Status: down Speed: Unknown Duplex: Unknown Link Failure Count: 1 Permanent HW addr: de:ad:be:ef:6c:11 Slave queue ID: 0 Slave Interface: eth0 MII Status: up Speed: Unknown Duplex: Unknown Link Failure Count: 0 Permanent HW addr: de:ad:be:ef:6c:10 Slave queue ID: 0
Step 8: Initiate a bandwidth test from DUT0
to DUT1
admin@DUT1$ monitor test performance server port 5001 admin@DUT0$ monitor test performance client 192.168.100.20 duration 5 port 5001Expect this output in
DUT0
:Connecting to host 192.168.100.20, port 5001 [ 5] local 192.168.100.10 port 57798 connected to 192.168.100.20 port 5001 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 93.3 MBytes 783 Mbits/sec 0 2.76 MBytes [ 5] 1.00-2.00 sec 142 MBytes 1.19 Gbits/sec 163 1.45 MBytes [ 5] 2.00-3.00 sec 168 MBytes 1.41 Gbits/sec 33 1.08 MBytes [ 5] 3.00-4.00 sec 159 MBytes 1.33 Gbits/sec 0 1.16 MBytes [ 5] 4.00-5.00 sec 156 MBytes 1.31 Gbits/sec 0 1.24 MBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 718 MBytes 1.21 Gbits/sec 196 sender [ 5] 0.00-5.00 sec 717 MBytes 1.20 Gbits/sec receiver iperf Done.
Step 9: Run command interfaces bonding bond0 show ports
at DUT0
and check if output contains the following tokens:
Currently Active Slave: eth1Show output
Ethernet Channel Bonding Driver: v5.10.127 Bonding Mode: fault-tolerance (active-backup) Primary Slave: None Currently Active Slave: eth1 MII Status: up MII Polling Interval (ms): 100 Up Delay (ms): 0 Down Delay (ms): 0 Peer Notification Delay (ms): 0 Slave Interface: eth1 MII Status: up Speed: Unknown Duplex: Unknown Link Failure Count: 1 Permanent HW addr: de:ad:be:ef:6c:11 Slave queue ID: 0 Slave Interface: eth0 MII Status: down Speed: Unknown Duplex: Unknown Link Failure Count: 1 Permanent HW addr: de:ad:be:ef:6c:10 Slave queue ID: 0