Hi all,
I''ve a feeling this has been covered many times but my research
hasn''t
showed anything applicable to me.
/var/log/messages;
pbond0: received packet with own address as source address
Repeats many many times;
I noticed that after a large transfer to domU (5GB scp''d) that is on
dom0 having the bond, load average takes about 2 minutes to drop from
2.5 to .7
I''ve a simple mode 0 (round robin) bond, no special network switch
config for this one.
Any guidance is greatly appreciated.
Configs below;
/etc/xend/xend-config.sxp;
(network-script ''network-bridge bridge=bond0'')
/etc/modprode.conf
alias eth0 tg3
alias eth1 tg3
alias eth2 forcedeth
alias eth3 forcedeth
alias scsi_hostadapter2 mptsas
alias scsi_hostadapter mptspi
alias scsi_hostadapter1 mptfc
alias scsi_hostadapter2 mptsas
alias bond0 bonding
options bond0 miimon=80 mode=0
alias peth0 tg3
/etc/sysconfig/network-scripts/ifcfg-eth0
# Broadcom Corporation NetXtreme BCM5715 Gigabit Ethernet
DEVICE=eth0
BOOTPROTO=none
USERCTL=no
HWADDR=00:23:8B:CE:9C:5C
ONBOOT=yes
MASTER=bond0
SLAVE=yes
TYPE=Ethernet
/etc/sysconfig/network-scripts/ifcfg-eth1
# Broadcom Corporation NetXtreme BCM5715 Gigabit Ethernet
DEVICE=eth1
BOOTPROTO=none
USERCTL=no
HWADDR=00:23:8B:CE:9C:5D
ONBOOT=yes
MASTER=bond0
SLAVE=yes
TYPE=Ethernet
/etc/sysconfig/network-scripts/ifcfg-bond0
DEVICE=bond0
IPADDR=10.0.70.11
NETMASK=255.255.0.0
NETWORK=10.0.0.0
BROADCAST=10.0.255.255
GATEWAY=10.0.10.1
ONBOOT=yes
BOOTPROTO=none
USERCTL=no
TYPE=Ethernet
ifconfig output;
bond0 Link encap:Ethernet HWaddr 00:23:8B:CE:9C:5C
inet addr:10.0.70.11 Bcast:10.0.255.255 Mask:255.255.0.0
inet6 addr: fe80::223:8bff:fece:9c5c/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:10714 errors:0 dropped:0 overruns:0 frame:0
TX packets:386 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1157674 (1.1 MiB) TX bytes:37307 (36.4 KiB)
eth0 Link encap:Ethernet HWaddr 00:23:8B:CE:9C:5C
UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1
RX packets:5618 errors:0 dropped:0 overruns:0 frame:0
TX packets:192 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:694966 (678.6 KiB) TX bytes:20541 (20.0 KiB)
Interrupt:21
eth1 Link encap:Ethernet HWaddr 00:23:8B:CE:9C:5C
UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1
RX packets:5570 errors:0 dropped:0 overruns:0 frame:0
TX packets:191 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:685771 (669.6 KiB) TX bytes:19584 (19.1 KiB)
Interrupt:22
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:2111 errors:0 dropped:0 overruns:0 frame:0
TX packets:2111 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:5464730 (5.2 MiB) TX bytes:5464730 (5.2 MiB)
pbond0 Link encap:Ethernet HWaddr 00:23:8B:CE:9C:5C
inet6 addr: fe80::223:8bff:fece:9c5c/64 Scope:Link
UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1
RX packets:11188 errors:0 dropped:0 overruns:0 frame:0
TX packets:383 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1380737 (1.3 MiB) TX bytes:40125 (39.1 KiB)
virbr0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:
255.255.255.0
inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:468 (468.0 b)
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Hi Brian Am Dienstag, den 06.10.2009, 13:41 -0700 schrieb Brian Krusic:> Hi all, > > I''ve a feeling this has been covered many times but my research hasn''t > showed anything applicable to me. > > /var/log/messages; > > pbond0: received packet with own address as source address > > Repeats many many times;.... This is an arp-problem. There is an option ARP_ANNOUNCE in /proc-FS or sysctl that allows you to control which source address is put in to ARP headers /proc/sys/net/ipv4/conf/$INTERACE/arp_announce is the place your searching for... hth, thomas> _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi Thomas, Thanks for the info. I do need arp and assume the value of 0 in those various files means yes. I''ll set bond0 to 1 and se what happens. Thanks again. - Brian On Oct 6, 2009, at 2:40 PM, Thomas Halinka wrote:> Hi Brian > > Am Dienstag, den 06.10.2009, 13:41 -0700 schrieb Brian Krusic: >> Hi all, >> >> I''ve a feeling this has been covered many times but my research >> hasn''t >> showed anything applicable to me. >> >> /var/log/messages; >> >> pbond0: received packet with own address as source address >> >> Repeats many many times; > .... > > This is an arp-problem. There is an option ARP_ANNOUNCE in /proc-FS or > sysctl that allows you to control which source address is put in to > ARP > headers > > /proc/sys/net/ipv4/conf/$INTERACE/arp_announce > > is the place your searching for... > > hth, > > thomas > >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xensource.com >> http://lists.xensource.com/xen-users > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi Thomas, I''m pretty confused as to what I need to do. In /etc/sysctl.conf, I set a few values, being either 0,1 or 2 on pbond0 as well as bond0 but to no avail for both arp_announce and arp_ignore. I also do; ip link set pbond0 down ip link set pbond0 arp off ip link set pbond0 up But still get many lines of; pbond0: received packet with own address as source address - Brian On Oct 6, 2009, at 2:40 PM, Thomas Halinka wrote:> Hi Brian > > Am Dienstag, den 06.10.2009, 13:41 -0700 schrieb Brian Krusic: >> Hi all, >> >> I''ve a feeling this has been covered many times but my research >> hasn''t >> showed anything applicable to me. >> >> /var/log/messages; >> >> pbond0: received packet with own address as source address >> >> Repeats many many times; > .... > > This is an arp-problem. There is an option ARP_ANNOUNCE in /proc-FS or > sysctl that allows you to control which source address is put in to > ARP > headers > > /proc/sys/net/ipv4/conf/$INTERACE/arp_announce > > is the place your searching for... > > hth, > > thomas > >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xensource.com >> http://lists.xensource.com/xen-users > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users