[Users] received packet with own address as source address
H. Haven Liu
haven.liu at ucla.edu
Tue Aug 20 11:09:09 EDT 2013
Hello,
After I reinstalled the host, the problem seems to have disappeared. This is not to say it's not going to come back, as it has done before.
I know the nodes were not receiving the error message *before* I installed VDSM (which configured the bridge?), but I haven't tried uninstalling to see if the problem would go away. The problem was also present when I just had one interface connected to the switch, connected to the Internet.
If the problem is indeed a classic L2 loop, how do I go about resolving it? Is it due to bridge (mis)configuration, or is it in the network switch settings? I have tried enabling and disabling STP and portfast, which didn't seem to have any effect.
Thanks,
Haven
On Aug 20, 2013, at 12:26 AM, Assaf Muller <amuller at redhat.com> wrote:
> Hello Mr. Liu,
>
> Sounds like a classic L2 loop. Hosts getting their own packets then losing connectivity for a few minutes while the switches restart.
>
> Can you try to rule out this possibility?
> For example:
> If you uninstall the engine and VDSM from all hosts does this still happen?
> Can you simplify the network topology and see if the issue persists?
>
>
> ----- Original Message -----
> From: "H. Haven Liu" <haven.liu at ucla.edu>
> To: Users at ovirt.org
> Sent: Saturday, August 17, 2013 10:06:07 PM
> Subject: [Users] received packet with own address as source address
>
> Hello,
>
> I have a oVirt installation with 6 CentOS 6.4 hosts. Some (not all) hosts are receiving these error messages, at a frequency of once every other minute:
>
> [root at vhost1 ~]# grep "source address" /var/log/messages | tail
> Aug 17 11:19:20 vhost1 kernel: em1: received packet with own address as source address
> Aug 17 11:21:24 vhost1 kernel: em1: received packet with own address as source address
> Aug 17 11:23:29 vhost1 kernel: em1: received packet with own address as source address
> Aug 17 11:25:34 vhost1 kernel: em1: received packet with own address as source address
> Aug 17 11:27:39 vhost1 kernel: em1: received packet with own address as source address
> Aug 17 11:29:44 vhost1 kernel: em1: received packet with own address as source address
> Aug 17 11:31:49 vhost1 kernel: em1: received packet with own address as source address
> Aug 17 11:33:54 vhost1 kernel: em1: received packet with own address as source address
> Aug 17 11:35:59 vhost1 kernel: em1: received packet with own address as source address
> Aug 17 11:38:04 vhost1 kernel: em1: received packet with own address as source address
>
> These error messages are accompanied with loss of connectivity, with duration varies between a few seconds to minutes. The loss of connectivity would start just before the above error message.
>
> I don't *think* it's hardware because the "received packet with own address" error message would disappear from one of the hosts after a while. These error messages are also present whether or not any VM is running on the particular host.
>
> Here are some configurations:
>
> [root at vhost1 ~]# ifconfig
> em1 Link encap:Ethernet HWaddr aa:bb:cc:dd:ee:f1
> inet6 addr: aaaa::bbbb:cccc:dddd:eee1/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:37413202 errors:0 dropped:0 overruns:0 frame:0
> TX packets:17822315 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:32444347931 (30.2 GiB) TX bytes:13715272213 (12.7 GiB)
> Interrupt:16
>
> em2 Link encap:Ethernet HWaddr aa:bb:cc:dd:ee:f2
> inet6 addr: aaaa::bbbb:cccc:dddd:eee2/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:21878 errors:0 dropped:0 overruns:0 frame:0
> TX packets:526 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:1598070 (1.5 MiB) TX bytes:40526 (39.5 KiB)
> Interrupt:17
>
> 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:49 errors:0 dropped:0 overruns:0 frame:0
> TX packets:49 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:9236 (9.0 KiB) TX bytes:9236 (9.0 KiB)
>
> ovirtmgmt Link encap:Ethernet HWaddr aa:bb:cc:dd:ee:f1
> inet addr:xxx.xxx.xxx.xxx Bcast:xxx.xxx.xxx.yyy Mask:255.255.255.0
> inet6 addr: aaaa::bbbb:cccc:dddd:eeee/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:22623881 errors:0 dropped:0 overruns:0 frame:0
> TX packets:9990988 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:28427312067 (26.4 GiB) TX bytes:13112553784 (12.2 GiB)
>
> private_lan Link encap:Ethernet HWaddr aa:bb:cc:dd:ee:f2
> inet addr:10.0.1.12 Bcast:10.0.1.255 Mask:255.255.255.0
> inet6 addr: aaaa::bbbb:cccc:dddd:eee2/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:19771 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:1080512 (1.0 MiB) TX bytes:468 (468.0 b)
> [root at vhost1 ~]# cat /etc/sysconfig/network-scripts/ifcfg-em1
> DEVICE=em1
> ONBOOT=yes
> HWADDR=aa:bb:cc:dd:ee:f2
> BRIDGE=ovirtmgmt
> NM_CONTROLLED=no
> UUID=c25b1ad1-9646-4126-9149-be5f68bae36c
> DNS2=www.www.www.www
> DNS1=www.www.www.www
> HOSTNAME=vhost1.mydomain.com
> MTU=1500
> IPV6INIT=no
> [root at vhost1 ~]# cat /etc/sysconfig/network-scripts/ifcfg-ovirtmgmt
> DEVICE=ovirtmgmt
> ONBOOT=yes
> TYPE=Bridge
> DELAY=0
> IPADDR=xxx.xxx.xxx.xxx
> NETMASK=255.255.255.0
> GATEWAY=xxx.xxx.xxx.1
> BOOTPROTO=none
> NM_CONTROLLED=no
> UUID=c25b1ad1-9646-4126-9149-be5f68bae36c
> DNS2=www.www.www.www
> DNS1=www.www.www.www
> HOSTNAME=vhost1.mydomain.com
> MTU=1500
> IPV6INIT=no
> [root at vhost1 ~]#
>
> Any help is appreciated.
> _______________________________________________
> Users mailing list
> Users at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
More information about the Users
mailing list