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.429 ms 64 bytes from 192.168.100.20: icmp_seq=2 ttl=64 time=0.495 ms --- 192.168.100.20 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 2ms rtt min/avg/max/mdev = 0.429/0.462/0.495/0.033 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 33854 connected to 192.168.100.20 port 5001 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 160 MBytes 1.34 Gbits/sec 164 294 KBytes [ 5] 1.00-2.00 sec 169 MBytes 1.42 Gbits/sec 21 382 KBytes [ 5] 2.00-3.00 sec 156 MBytes 1.31 Gbits/sec 34 573 KBytes [ 5] 3.00-4.00 sec 140 MBytes 1.17 Gbits/sec 24 508 KBytes [ 5] 4.00-5.00 sec 158 MBytes 1.32 Gbits/sec 20 516 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 783 MBytes 1.31 Gbits/sec 263 sender [ 5] 0.00-5.00 sec 780 MBytes 1.31 Gbits/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 50644 3898871 0 282144 427113231 0 eth1 up 67076 5188806 0 283269 428824572 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.881 ms 64 bytes from 192.168.100.20: icmp_seq=2 ttl=64 time=0.694 ms --- 192.168.100.20 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 3ms rtt min/avg/max/mdev = 0.694/0.787/0.881/0.097 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 50128 connected to 192.168.100.20 port 5001 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.01 sec 214 MBytes 1.77 Gbits/sec 0 3.12 MBytes [ 5] 1.01-2.00 sec 208 MBytes 1.77 Gbits/sec 748 1.13 MBytes [ 5] 2.00-3.00 sec 198 MBytes 1.66 Gbits/sec 0 1.21 MBytes [ 5] 3.00-4.01 sec 192 MBytes 1.61 Gbits/sec 0 1.27 MBytes [ 5] 4.01-5.00 sec 184 MBytes 1.55 Gbits/sec 0 1.32 MBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 995 MBytes 1.67 Gbits/sec 748 sender [ 5] 0.00-5.00 sec 995 MBytes 1.67 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: 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 49110 connected to 192.168.100.20 port 5001 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 205 MBytes 1.72 Gbits/sec 184 1.76 MBytes [ 5] 1.00-2.00 sec 205 MBytes 1.72 Gbits/sec 376 1.34 MBytes [ 5] 2.00-3.01 sec 186 MBytes 1.55 Gbits/sec 0 1.43 MBytes [ 5] 3.01-4.01 sec 191 MBytes 1.60 Gbits/sec 18 1.08 MBytes [ 5] 4.01-5.00 sec 192 MBytes 1.63 Gbits/sec 0 1.14 MBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 980 MBytes 1.64 Gbits/sec 578 sender [ 5] 0.00-5.00 sec 977 MBytes 1.64 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