This case is not the same as described on bug #1766330. All NIC devices installed on SUT have failed the Multi-NIC iperf3 stress testing on 18.04 beta release. The test stopped and exited with messages “packet_write_wait: Connection to <ip_address_primary-network>: Broken pipe” on the 2nd iteration of iperf3 testing. At IPERF server, a message popped-out on screen “the client has terminated”.
Most system have at least 4 NICs devices installed. Two 1Gb/s Ethernet (eno1 and eno2) and two 10Gb/s either Ethernet or SFP (in this case ens2s0f0, and ens2s0f1). Due to different socket type, two IPERF subnets created - one for 1G/10G Ethernet NIC devices and the other one is for 10G SFP NIC devices. Below is the networked logical diagram of my current configuration.
This case is not the same as described on bug #1766330. All NIC devices installed on SUT have failed the Multi-NIC iperf3 stress testing on 18.04 beta release. The test stopped and exited with messages “packet_write_wait: Connection to <ip_address_ primary- network> : Broken pipe” on the 2nd iteration of iperf3 testing. At IPERF server, a message popped-out on screen “the client has terminated”.
Most system have at least 4 NICs devices installed. Two 1Gb/s Ethernet (eno1 and eno2) and two 10Gb/s either Ethernet or SFP (in this case ens2s0f0, and ens2s0f1). Due to different socket type, two IPERF subnets created - one for 1G/10G Ethernet NIC devices and the other one is for 10G SFP NIC devices. Below is the networked logical diagram of my current configuration.