[Xen-users] Trouble with bonding + arp_ip_target + vlan + trunked netdev + network-bridge script

[Rolf Arne Larsen <rolf@xxxxxxxxxxxxx>]

Running debian lenny with 3.2.1 + 2.6.26.
Even tried 2.6.35 suse kernel and xen 4.0.0 but still the same problems.

Running bonding on eth0,1 as bond0 with arp_ip_target as check to see if 
interfaces really are online.

Problems start when i run:

/etc/xen/scripts/network-bridge start netdev=bond0.120

Then the arp_ip_target in the bonding driver completely freaks out:

Jul 22 16:34:21 kernel: [  709.844231] bonding: bond0: no path to arp_ip_target 
77.xxxxxxx via rt.dev bond0.120
Jul 22 16:34:23 kernel: [  711.848233] bonding: bond0: no path to arp_ip_target 
77.xxxxxxx via rt.dev bond0.120
Jul 22 16:34:25 kernel: [  713.852232] bonding: bond0: no path to arp_ip_target 
77.xxxxxxx via rt.dev bond0.120
Jul 22 16:34:27 kernel: [  715.856350] bonding: bond0: no path to arp_ip_target 
77.xxxxxxx via rt.dev bond0.120
Jul 22 16:34:29 kernel: [  717.860232] bonding: bond0: no path to arp_ip_target 
77.xxxxxxx via rt.dev bond0.120

It then starts to jump back and forth between eth0 and eth1 because both doesnt 
seem to get arping reply through rt.dev bond0.120.

Whats strange is that arping works:

# arping -i bond0.120 77.xxxxxx
ARPING 77.xxxxxxxx
56 bytes from 00:10:db:ff:20:50 (77.xxxxxxxxx): index=0 time=535.011 usec
56 bytes from 00:10:db:ff:20:50 (77.xxxxxxxxx): index=1 time=4.130 msec

Anyone else seen these problems?

This only happens after network-bridge creates the bond0.120 bridge which 
pbond0.120 is attached to. (bond0.120 has ip, pbond0.120 does not)

---
Mvh
Rolf Arne Larsen
System Administrator
rolf@xxxxxxxxxxxxx

ABC Startsiden AS
Sagveien 21A, 0459 Oslo

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users