Bug 747853

Summary: Bonding over vlan with arp monitor does not work
Product: Red Hat Enterprise Linux 5 Reporter: Liang Zheng <lzheng>
Component: kernelAssignee: Andy Gospodarek <agospoda>
Status: CLOSED NOTABUG QA Contact: Red Hat Kernel QE team <kernel-qe>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 5.8CC: jfeeney, kzhang, peterm
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-10-24 17:22:52 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Liang Zheng 2011-10-21 06:55:43 UTC 
Description of problem:
When enslave vlan interfaces in a bonding interface with arp monitor,even the bonding receive the arp reply packets from arp_ip_target,MII status of the slave interfaces always came down.

Version-Release number of selected component (if applicable):
kernel-2.6.18-290.el5

How reproducible:
100%

Steps to Reproduce:
1.modprobe bonding mode=1 arp_interval=1000 arp_ip_target=192.168.10.4
2.ifconfig bond0 192.168.10.1/24 up
3.ifconfig eth4 up
4.vconfig add eth4 3
5.ifenslave bond0 eth4.3
6.tcpdump -i bond0 arp
7.cat /proc/net/bonding/bond0
  
Actual results:
[root@hp-dl580g7-01 ~]# cat /proc/net/bonding/bond0 
Ethernet Channel Bonding Driver: v3.4.0-1 (October 7, 2008)

Bonding Mode: fault-tolerance (active-backup)
Primary Slave: None
Currently Active Slave: eth4.3
MII Status: up
MII Polling Interval (ms): 0
Up Delay (ms): 0
Down Delay (ms): 0
ARP Polling Interval (ms): 1000
ARP IP target/s (n.n.n.n form): 192.168.10.4

Slave Interface: eth4.3
MII Status: up
Speed: 100 Mbps
Duplex: full
Link Failure Count: 275  <=================
Permanent HW addr: 00:1b:21:4a:fe:98

Slave Interface: eth5.3
MII Status: down
Speed: 100 Mbps
Duplex: full
Link Failure Count: 278 <==================
Permanent HW addr: 00:1b:21:4a:fe:99


Expected results:


Additional info:
Bonding can receive the arp reply from arp target which IP is 192.168.10.4.
[root@hp-dl580g7-01 ~]# tcpdump -i bond0 arp
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on bond0, link-type EN10MB (Ethernet), capture size 96 bytes
02:54:18.450776 arp reply 192.168.10.4 is-at 00:10:18:58:d0:48 (oui Unknown)
02:54:19.450895 arp reply 192.168.10.4 is-at 00:10:18:58:d0:48 (oui Unknown)
02:54:20.450852 arp reply 192.168.10.4 is-at 00:10:18:58:d0:48 (oui Unknown)
02:54:21.450956 arp reply 192.168.10.4 is-at 00:10:18:58:d0:48 (oui Unknown)
02:54:22.450884 arp reply 192.168.10.4 is-at 00:10:18:58:d0:48 (oui Unknown)
02:54:23.450949 arp reply 192.168.10.4 is-at 00:10:18:58:d0:48 (oui Unknown)
02:54:24.450923 arp reply 192.168.10.4 is-at 00:10:18:58:d0:48 (oui Unknown)
Comment 1 Andy Gospodarek 2011-10-24 17:22:52 UTC 
This is NOTABUG.  VLANs should be added on top of the bond.

You cannot reliably make a VLAN interface a slave of a bond.