While I see the messages even with no VMs running, I don't see any messages before installing oVirt. Additionally, is there any reason that the school network would selectively affect some nodes but not others?
Thanks On Aug 22, 2013, at 2:49 AM, Assaf Muller <[email protected]> wrote: > I'd enable STP on all ports, including the port connecting your switch to the > school switch. > > VSDSM configures the ovirtmgmt bridge on installation. The reason I'm > suggesting that it's not VDSM at fault but rather the school network having a > loop is that you mentioned > that you get these messages even with no VMs running. > > ----- Original Message ----- > From: "H. Haven Liu" <[email protected]> > To: "Assaf Muller" <[email protected]> > Cc: [email protected] > Sent: Wednesday, August 21, 2013 11:26:57 PM > Subject: Re: [Users] received packet with own address as source address > > The switch is connected to the internet via the school's switch. Currently > (as well as when I received the error messages last time) portfast is > disabled for all ports, and STP enabled for all ports except for the port > connecting my switch to the school's. > > On Aug 20, 2013, at 11:50 PM, Assaf Muller <[email protected]> wrote: > >>> The problem was also present when I just had one interface connected to the >>> switch, connected to the Internet. >> >> How was the switch connected to the internet? Is it connected to other >> switches? >> >> To solve the loop you can make sure that STP is enabled on all switches and >> to disable portfast. >> >> ----- Original Message ----- >> From: "H. Haven Liu" <[email protected]> >> To: "Assaf Muller" <[email protected]> >> Cc: [email protected] >> Sent: Tuesday, August 20, 2013 6:09:09 PM >> Subject: Re: [Users] received packet with own address as source address >> >> 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 <[email protected]> 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" <[email protected]> >>> To: [email protected] >>> 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@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@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@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@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@vhost1 ~]# >>> >>> Any help is appreciated. >>> _______________________________________________ >>> Users mailing list >>> [email protected] >>> http://lists.ovirt.org/mailman/listinfo/users > _______________________________________________ Users mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/users
