I'll test the patch to see if it's working fine.
I have unmanaged (cheep) switches, so I guess they do not send IGMP querier
messages.
So if I disable that on linux bridges it will break multicast in my cluster?
___
pve-devel mailing list
-devel@pve.proxmox.com
Envoyé: Lundi 11 Mars 2013 09:33:17
Objet: RE: [pve-devel] corosync, multicast problem because of vmbr
multicast_snooping enabled
I'll test the patch to see if it's working fine.
I have unmanaged (cheep) switches, so I guess they do not send IGMP querier
messages.
So
On Sun, 10 Mar 2013 10:41:53 +0100 (CET)
Alexandre DERUMIER aderum...@odiso.com wrote:
So, I don't known for HP switchs, but for Cisco switches it seem to break the
election of igmp.
Some thoughts:
1) You have an aggregation spanning over two switches, I only use one
2) The switch is up
here another bug with igmp report from bridge and bonding, if failover occur
in
bonding, igmp report are not send anymore :/
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=1c3ac42
89a0e4d60cbd4787b4a91de4a0c785df1
If you find a bug including a patch we can try to
Maurer diet...@proxmox.com
À: Alexandre DERUMIER aderum...@odiso.com, Michael Rasmussen
m...@datanom.net
Cc: pve-devel@pve.proxmox.com
Envoyé: Dimanche 10 Mars 2013 11:18:29
Objet: RE: [pve-devel] corosync, multicast problem because of vmbr
multicast_snooping enabled
here another bug with igmp
to patch author, maybe can he give us more informations
about the problem.
I'll continue tests this week.
- Mail original -
De: Michael Rasmussen m...@datanom.net
À: pve-devel@pve.proxmox.com
Envoyé: Dimanche 10 Mars 2013 11:05:49
Objet: Re: [pve-devel] corosync, multicast problem
Envoyé: Vendredi 8 Mars 2013 19:45:33
Objet: Re: [pve-devel] corosync, multicast problem because of vmbr
multicast_snooping enabled
On Fri, 08 Mar 2013 19:34:56 +0100 (CET)
Alexandre DERUMIER aderum...@odiso.com wrote:
So, how can do you multicast with linux without bridge ?
Like simply
aderum...@odiso.com, Michael Rasmussen
m...@datanom.net
Cc: pve-devel@pve.proxmox.com
Envoyé: Samedi 9 Mars 2013 09:31:26
Objet: RE: [pve-devel] corosync, multicast problem because of vmbr
multicast_snooping enabled
@Dietmar
Maybe the upgrade should be done like this:
- disable igmp
Some more infos about igmp queries.
We can have only 1 igmp quierier on a vlan. If multiple quierier exist, an
election
mecanism exist, and the querier with lowest ip should win.
So it's possible that a proxmox host, is the igmp quierier for your whole
network.
(including physical
On Sat, 9 Mar 2013 15:30:44 +0100
Michael Rasmussen m...@datanom.net wrote:
Attached are my configuration on a HP V1910 switch.
Missed one screen dump.
--
Hilsen/Regards
Michael Rasmussen
Get my public GnuPG keys:
michael at rasmussen dot cc
From what I have read about the IGMP implementation in Linux then igmp
quierier is optional and disabled by default since the task of acting as
quierier is
normally an infrastructure task in which case you expect the network
components like switch or router to take care of this. This is
comming from the bridge.
- Mail original -
De: Dietmar Maurer diet...@proxmox.com
À: Michael Rasmussen m...@datanom.net, pve-devel@pve.proxmox.com
Envoyé: Samedi 9 Mars 2013 16:44:43
Objet: Re: [pve-devel] corosync, multicast problem because of vmbr
multicast_snooping enabled
igmp querier in linux bridge is on disabled in newer kernel since the commit I
have pointed, but it's enabled by default is current redhat kernel.
With tcpdump on bridge you should see igmp queries comming from the bridge.
Did you already test applying the patch (seem possible). Does that
igmp querier in linux bridge is on disabled in newer kernel since the
commit I have pointed, but it's enabled by default is current redhat kernel.
With tcpdump on bridge you should see igmp queries comming from the
bridge.
Did you already test applying the patch (seem possible). Does
On Sat, 09 Mar 2013 16:53:27 +0100 (CET)
Alexandre DERUMIER aderum...@odiso.com wrote:
Are you sure about that? How can we test that (looking at the sources it
seems to be enabled)?
igmp querier in linux bridge is on disabled in newer kernel since the commit
I have pointed,
but it's
On Sat, 9 Mar 2013 17:31:54 +0100
Michael Rasmussen m...@datanom.net wrote:
tcpdump -i vmbr20 -vv net 224.0.0.0/4
tcpdump: listening on vmbr20, link-type EN10MB (Ethernet), capture size
65535 bytes 17:20:45.093219 IP (tos 0xc0, ttl 1, id 0, offset 0, flags
[DF], proto IGMP
After making some investigation the above request can be interpreted this way:
ttl 1: Restricted to the local subnet, no router hops
0.0.0.0 (group address): for Host Membership Query
The patch to disable sending multicast queries includes the following hint:
Unfortunately these packets
On Sat, 9 Mar 2013 18:33:58 +
Dietmar Maurer diet...@proxmox.com wrote:
So I think we talk about switch bugs here, not normal behavior.
I am leaning towards the same conclusion since I have never seen
those queries cause any problems here.
@alexandre: What precise Cisco switch do you
So maybe disabling it is the better choice.
I have talked again with my network engineer, he say it's really shouldn't be
break anything.
Our production servers don't have anymore multicast errors since the change.
OK, just uploaded a new kernel to pvetest (disabled
Thanks !
I'll test it today
- Mail original -
De: Dietmar Maurer diet...@proxmox.com
À: Alexandre DERUMIER aderum...@odiso.com
Cc: pve-devel@pve.proxmox.com
Envoyé: Vendredi 8 Mars 2013 11:46:18
Objet: RE: [pve-devel] corosync, multicast problem because of vmbr
multicast_snooping
@pve.proxmox.com
Envoyé: Vendredi 8 Mars 2013 11:46:18
Objet: RE: [pve-devel] corosync, multicast problem because of vmbr
multicast_snooping enabled
So maybe disabling it is the better choice.
I have talked again with my network engineer, he say it's really
shouldn't be break anything.
Our
, multicast problem because of vmbr
multicast_snooping enabled
What is your problem exactly ?
Martin updated 2 clusters, and now I get strange TOTEM error - corosync does
not work.
Mar 8 14:30:23 hp1 corosync[1588]: [TOTEM ] Totem is unable to form a cluster
because of an operating system
original -
De: Michael Rasmussen m...@datanom.net
À: pve-devel@pve.proxmox.com
Envoyé: Vendredi 8 Mars 2013 17:31:24
Objet: Re: [pve-devel] corosync, multicast problem because of vmbr
multicast_snooping enabled
On Fri, 08 Mar 2013 17:20:53 +0100 (CET)
Alexandre DERUMIER aderum...@odiso.com
But Indeed, that's not an easy update,i'm not sure it's possible to push it
by
default to next kernel.
You are certain that it is not your switch which is causing problems?
@alexandre: what switch model do you use?
___
pve-devel mailing list
Maurer diet...@proxmox.com
À: Michael Rasmussen m...@datanom.net, pve-devel@pve.proxmox.com
Envoyé: Vendredi 8 Mars 2013 18:51:33
Objet: Re: [pve-devel] corosync, multicast problem because of vmbr
multicast_snooping enabled
But Indeed, that's not an easy update,i'm not sure it's possible
)
- Mail original -
De: Dietmar Maurer diet...@proxmox.com
À: Alexandre DERUMIER aderum...@odiso.com
Cc: pve-devel@pve.proxmox.com
Envoyé: Vendredi 8 Mars 2013 18:39:40
Objet: RE: [pve-devel] corosync, multicast problem because of vmbr
multicast_snooping enabled
multicast also does
...@proxmox.com
À: Alexandre DERUMIER aderum...@odiso.com
Cc: pve-devel@pve.proxmox.com
Envoyé: Jeudi 7 Mars 2013 08:32:08
Objet: RE: [pve-devel] corosync, multicast problem because of vmbr
multicast_snooping enabled
Currently to disable snooping, 2 possibility:
/etc/network/interfaces
auto vmbr1
Do you think we should disable it in the kernel?
Yes, I think, but maybe some user want to have choice activate it or not ?
Maybe is it possible to create a patch to kernel to disable it by default?
sysfs
multicast_snooping=0
Already tried that, but found not way so far.
multicast errors since the change.
- Mail original -
De: Dietmar Maurer diet...@proxmox.com
À: Alexandre DERUMIER aderum...@odiso.com
Cc: pve-devel@pve.proxmox.com
Envoyé: Jeudi 7 Mars 2013 09:54:48
Objet: RE: [pve-devel] corosync, multicast problem because of vmbr
multicast_snooping
À: Alexandre DERUMIER aderum...@odiso.com
Cc: pve-devel@pve.proxmox.com
Envoyé: Lundi 4 Mars 2013 06:59:31
Objet: RE: [pve-devel] corosync, multicast problem because of vmbr
multicast_snooping enabled
The question is if that can have bad side effects?
I'll investigate this week with my
Hi,
I had worked on a problem this week,
Since some month, I have corosync random failures.
Thanks to omping, I had check the multicast layer, and it seem that sometime
it's hanging.
Also, I have had a strange thing, shutdown down a node had killed multicast
between all my others nodes
-devel@pve.proxmox.com
Envoyé: Dimanche 3 Mars 2013 18:02:15
Objet: [pve-devel] corosync, multicast problem because of vmbr
multicast_snooping enabled
Hi,
I had worked on a problem this week,
Since some month, I have corosync random failures.
Thanks to omping, I had check the multicast layer
I don't known how exactly it's works with linux bridge, But as my proxmox host
ip is on vmbr0 (the default proxmox setup),
echo 0 /sys/class/net/vmbr0/bridge/multicast_snooping
has resolved all my problems.
I'm not sure, but I think we should disable multicast_snooping by default.
: Lundi 4 Mars 2013 06:40:04
Objet: RE: [pve-devel] corosync, multicast problem because of vmbr
multicast_snooping enabled
I don't known how exactly it's works with linux bridge, But as my proxmox
host
ip is on vmbr0 (the default proxmox setup),
echo 0 /sys/class/net/vmbr0/bridge
34 matches
Mail list logo
