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.

../../../../_images/topology22.svg

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+up
Show output
------------------------------------------------------------------
Name            IP Address           Admin  Oper  Vrf  Description
------------------------------------------------------------------
bond0  192.168.100.10/24             up     up
       fe80::dcad:beff:feef:6c01/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:01
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:00
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 1
Show 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=12.2 ms
64 bytes from 192.168.100.20: icmp_seq=2 ttl=64 time=0.310 ms

--- 192.168.100.20 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 2ms
rtt min/avg/max/mdev = 0.310/6.246/12.183/5.937 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 5001
Expect this output in DUT0:
Connecting to host 192.168.100.20, port 5001
[  5] local 192.168.100.10 port 51760 connected to 192.168.100.20 port 5001
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec  89.2 MBytes   748 Mbits/sec  136    328 KBytes
[  5]   1.00-2.00   sec   101 MBytes   845 Mbits/sec   85    402 KBytes
[  5]   2.00-3.00   sec   104 MBytes   875 Mbits/sec   32    417 KBytes
[  5]   3.00-4.00   sec   113 MBytes   948 Mbits/sec    7    559 KBytes
[  5]   4.00-5.00   sec  97.2 MBytes   819 Mbits/sec    0    503 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec   505 MBytes   847 Mbits/sec  260             sender
[  5]   0.00-5.01   sec   503 MBytes   842 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         29861   2244628          0      181519  274797562          0
eth1  up         54109   4126729          0      182938  276943074          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+up
Show output
------------------------------------------------------------------
Name            IP Address           Admin  Oper  Vrf  Description
------------------------------------------------------------------
bond0  192.168.100.10/24             up     up
       fe80::dcad:beff:feef:6c01/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:01
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:00
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 1
Show 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.486 ms
64 bytes from 192.168.100.20: icmp_seq=2 ttl=64 time=0.431 ms

--- 192.168.100.20 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 21ms
rtt min/avg/max/mdev = 0.431/0.458/0.486/0.034 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 5001
Expect this output in DUT0:
Connecting to host 192.168.100.20, port 5001
[  5] local 192.168.100.10 port 54202 connected to 192.168.100.20 port 5001
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec   166 MBytes  1.39 Gbits/sec  465   1.29 MBytes
[  5]   1.00-2.00   sec   191 MBytes  1.60 Gbits/sec    0   1.37 MBytes
[  5]   2.00-3.00   sec   184 MBytes  1.54 Gbits/sec    0   1.43 MBytes
[  5]   3.00-4.00   sec   191 MBytes  1.60 Gbits/sec    7   1.06 MBytes
[  5]   4.00-5.00   sec   194 MBytes  1.62 Gbits/sec    0   1.16 MBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec   926 MBytes  1.55 Gbits/sec  472             sender
[  5]   0.00-5.01   sec   923 MBytes  1.55 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: eth0
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: eth1
MII Status: down
Speed: Unknown
Duplex: Unknown
Link Failure Count: 1
Permanent HW addr: de:ad:be:ef:6c:01
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:00
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 5001
Expect this output in DUT0:
Connecting to host 192.168.100.20, port 5001
[  5] local 192.168.100.10 port 43026 connected to 192.168.100.20 port 5001
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec   107 MBytes   893 Mbits/sec  142   1.43 MBytes
[  5]   1.00-2.00   sec   161 MBytes  1.35 Gbits/sec   40   1.11 MBytes
[  5]   2.00-3.00   sec   170 MBytes  1.43 Gbits/sec    0   1.17 MBytes
[  5]   3.00-4.00   sec   186 MBytes  1.56 Gbits/sec    0   1.23 MBytes
[  5]   4.00-5.00   sec   158 MBytes  1.32 Gbits/sec    0   1.29 MBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec   782 MBytes  1.31 Gbits/sec  182             sender
[  5]   0.00-5.01   sec   778 MBytes  1.30 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: eth1
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: 1
Permanent HW addr: de:ad:be:ef:6c:01
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:00
Slave queue ID: 0