Packet loss when failing back to primary slave of a bond

Solution Verified - Updated -

Issue

  • Packets are lost when failing back to the primary slave of a bond after the link to that slave comes back up.
  • Client pinging the RHEL server, note that pings with sequence numbers 289 and 290 do not get a response.
ping -s 192.168.12.10 1200

PING 192.168.12.10: 1200 data bytes
. . . .
1208 bytes from 192.168.12.10: icmp_seq=283. time=6.31 ms
1208 bytes from 192.168.12.10: icmp_seq=284. time=6.30 ms
1208 bytes from 192.168.12.10: icmp_seq=285. time=6.35 ms
1208 bytes from 192.168.12.10: icmp_seq=286. time=6.33 ms
1208 bytes from 192.168.12.10: icmp_seq=287. time=6.35 ms
1208 bytes from 192.168.12.10: icmp_seq=288. time=6.32 ms <<<< missing 289 and 290
1208 bytes from 192.168.12.10: icmp_seq=291. time=6.39 ms
1208 bytes from 192.168.12.10: icmp_seq=292. time=6.36 ms
1208 bytes from 192.168.12.10: icmp_seq=293. time=6.39 ms

Environment

  • Red Hat Enterprise Linux
  • bonding mode active-backup (mode 1)

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content