bonding option arp_validate=3 does not seem to function properly with vlan tagging

Solution Verified - Updated -

Issue

  • user specifies arp_validate=3 in their bonding configuration and both slave links show as 'down' even though the arp_target is responding to the arp requests sent by the bonding driver
  • when user removes arp_validate or sets arp_validate=0, the bonding driver comes up just fine

Environment

  • RHEL 5.4 - 2.6.18-164.el5 (or any previous)
  • bonding in use, mode 1, arp monitoring with arp_validate=3 set
  • vlan tagging done by the network switch

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