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:6c10/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: 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 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
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.590 ms 64 bytes from 192.168.100.20: icmp_seq=2 ttl=64 time=0.360 ms --- 192.168.100.20 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 2ms rtt min/avg/max/mdev = 0.360/0.475/0.590/0.115 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 57854 connected to 192.168.100.20 port 5001 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 36.4 MBytes 305 Mbits/sec 9 158 KBytes [ 5] 1.00-2.00 sec 38.7 MBytes 325 Mbits/sec 15 185 KBytes [ 5] 2.00-3.04 sec 34.5 MBytes 279 Mbits/sec 19 185 KBytes [ 5] 3.04-4.00 sec 50.9 MBytes 442 Mbits/sec 13 536 KBytes [ 5] 4.00-5.00 sec 124 MBytes 1.04 Gbits/sec 148 338 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 284 MBytes 476 Mbits/sec 204 sender [ 5] 0.00-5.00 sec 280 MBytes 470 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 24516 1850793 0 101835 154146034 0 eth1 up 25779 1948157 0 101738 153999378 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:6c10/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: eth0 MII Status: up MII Polling Interval (ms): 100 Up Delay (ms): 0 Down Delay (ms): 0 Peer Notification Delay (ms): 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 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
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.469 ms 64 bytes from 192.168.100.20: icmp_seq=2 ttl=64 time=0.348 ms --- 192.168.100.20 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 2ms rtt min/avg/max/mdev = 0.348/0.408/0.469/0.063 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 38522 connected to 192.168.100.20 port 5001 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 81.3 MBytes 679 Mbits/sec 0 2.28 MBytes [ 5] 1.00-2.00 sec 67.5 MBytes 568 Mbits/sec 2 1.41 KBytes [ 5] 2.00-3.00 sec 81.2 MBytes 682 Mbits/sec 1177 2.22 MBytes [ 5] 3.00-4.01 sec 168 MBytes 1.40 Gbits/sec 0 2.41 MBytes [ 5] 4.01-5.00 sec 168 MBytes 1.41 Gbits/sec 0 2.57 MBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 565 MBytes 948 Mbits/sec 1179 sender [ 5] 0.00-5.00 sec 565 MBytes 947 Mbits/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: 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 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
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 44642 connected to 192.168.100.20 port 5001 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 159 MBytes 1.33 Gbits/sec 0 3.02 MBytes [ 5] 1.00-2.00 sec 156 MBytes 1.31 Gbits/sec 781 1.50 MBytes [ 5] 2.00-3.01 sec 148 MBytes 1.23 Gbits/sec 89 1.13 MBytes [ 5] 3.01-4.00 sec 131 MBytes 1.11 Gbits/sec 0 1.20 MBytes [ 5] 4.00-5.00 sec 174 MBytes 1.46 Gbits/sec 0 1.26 MBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 768 MBytes 1.29 Gbits/sec 870 sender [ 5] 0.00-5.00 sec 768 MBytes 1.29 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: 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 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