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/topology21.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: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 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.569 ms
64 bytes from 192.168.100.20: icmp_seq=2 ttl=64 time=0.299 ms

--- 192.168.100.20 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1ms
rtt min/avg/max/mdev = 0.299/0.434/0.569/0.135 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 46434 connected to 192.168.100.20 port 5001
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec  39.9 MBytes   334 Mbits/sec  634   1.26 MBytes
[  5]   1.00-2.00   sec  37.5 MBytes   315 Mbits/sec   75   1.26 MBytes
[  5]   2.00-3.00   sec  18.8 MBytes   157 Mbits/sec   51   1.41 KBytes
[  5]   3.00-4.00   sec  31.2 MBytes   262 Mbits/sec   70    348 KBytes
[  5]   4.00-5.00   sec  1.25 MBytes  10.5 Mbits/sec    2   1.41 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec   129 MBytes   216 Mbits/sec  832             sender
[  5]   0.00-5.11   sec   125 MBytes   206 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          9846    759228          0       46096  69755271          0
eth1  up         16295   1272785          0       46017  69641556          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: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 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.419 ms
64 bytes from 192.168.100.20: icmp_seq=2 ttl=64 time=0.316 ms

--- 192.168.100.20 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 2ms
rtt min/avg/max/mdev = 0.316/0.367/0.419/0.054 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 55026 connected to 192.168.100.20 port 5001
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec  56.9 MBytes   477 Mbits/sec    1    755 KBytes
[  5]   1.00-2.00   sec  1.25 MBytes  10.5 Mbits/sec    1    755 KBytes
[  5]   2.00-3.01   sec  8.75 MBytes  73.0 Mbits/sec    1    833 KBytes
[  5]   3.01-4.18   sec  12.5 MBytes  89.0 Mbits/sec    0   1000 KBytes
[  5]   4.18-5.00   sec  12.5 MBytes   129 Mbits/sec    1   1.41 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec  91.9 MBytes   154 Mbits/sec    4             sender
[  5]   0.00-5.07   sec  89.2 MBytes   148 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: 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: 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 5001
Expect this output in DUT0:
Connecting to host 192.168.100.20, port 5001
[  5] local 192.168.100.10 port 55038 connected to 192.168.100.20 port 5001
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec  14.4 MBytes   120 Mbits/sec    1   1.41 KBytes
[  5]   1.00-2.00   sec  17.5 MBytes   147 Mbits/sec    0   1.02 MBytes
[  5]   2.00-3.00   sec  7.50 MBytes  62.9 Mbits/sec    1   1.08 MBytes
[  5]   3.00-4.00   sec  6.25 MBytes  52.4 Mbits/sec    2   1.41 KBytes
[  5]   4.00-5.00   sec  61.2 MBytes   512 Mbits/sec   82   1.10 MBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec   107 MBytes   179 Mbits/sec   86             sender
[  5]   0.00-5.01   sec   107 MBytes   179 Mbits/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: 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