Re: [j-nsp] Proxmox with Multicast & Juniper EX
Hi Everybody, just wanted to let you know that enabling an IGMP querier on the router solved the issue. Best, Jeff ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] Proxmox with Multicast & Juniper EX
Hi Tore, However these intial IGMP membership reports are not forwarded to the EX4550, as it is not a multicast-router interface (from the EX4200s' points of view, at least). So the EX4550 won't be able to learn of the existence of the multicast group at all. Also, since the uplink to the EX4550 isn't a multicast-router interface, nor a regular host interface that's a member of the multicast group, packets destined for the multicast group won't be forwarded to the EX4550 either. You really need a multicast querier in the network for this to work... I will give that a shot, thanks for the help! Regards, Jeff ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] Proxmox with Multicast & Juniper EX
* Tore Anderson > * Jeff Meyers > > > I am mostly confused why the packets passing the core makes a > > difference at all. For my understanding, igmp-snooping inspects the > > communication and passes multicast traffic to exactly those who shall > > receive it. Why isn't this working? I read that this requires an icmp > > querier. Would it help to configure that querier on one of the > > routers (it's two routers because of VRRP)? Can anyone explain why it > > is working on a local switch but not anymore as soon as a 2nd switch > > is involved in the path? > > You'll need a querier in your network if you want IGMP snooping to > work, otherwise the switch will remove the host interfaces from their > subscribed multicast groups after a while. The querier can be one of > the switches (you must configure a l3-interface on the VLAN), it > doesn't have to be the upstream routers. > > Other than that there's too little information in your message for me > to say exactly what your problem is. After thinking a bit more about it I think the behaviour you're observing makes perfect sense. When you connect your hosts to one of the EX4200s, they'll send an IGMP membership report to join the multicast group in question. The EX4200's IGMP snooping picks up on this, and multicast communication the two hosts then works (but probably just for a limited amount of time, as there's no querier that would normally cause the hosts to renew their membership in the group, so their membership will likely just timeout eventually). However these intial IGMP membership reports are not forwarded to the EX4550, as it is not a multicast-router interface (from the EX4200s' points of view, at least). So the EX4550 won't be able to learn of the existence of the multicast group at all. Also, since the uplink to the EX4550 isn't a multicast-router interface, nor a regular host interface that's a member of the multicast group, packets destined for the multicast group won't be forwarded to the EX4550 either. You really need a multicast querier in the network for this to work... Tore ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] Proxmox with Multicast & Juniper EX
* Jeff Meyers > I am mostly confused why the packets passing the core makes a > difference at all. For my understanding, igmp-snooping inspects the > communication and passes multicast traffic to exactly those who shall > receive it. Why isn't this working? I read that this requires an icmp > querier. Would it help to configure that querier on one of the > routers (it's two routers because of VRRP)? Can anyone explain why it > is working on a local switch but not anymore as soon as a 2nd switch > is involved in the path? You'll need a querier in your network if you want IGMP snooping to work, otherwise the switch will remove the host interfaces from their subscribed multicast groups after a while. The querier can be one of the switches (you must configure a l3-interface on the VLAN), it doesn't have to be the upstream routers. Other than that there's too little information in your message for me to say exactly what your problem is. I suggest you play around with the "show igmp-snooping ... detail" commands on your switches to find out exactly where the packets gets dropped. Also note that multicast packets destined for 224.0.0.0/24 are treated differently from other multicast destinations, so this is important information as well. https://www.juniper.net/techpubs/en_US/junos12.3/topics/concept/igmp-snooping-ex-series-overview.html Tore ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
[j-nsp] Proxmox with Multicast & Juniper EX
Hi list, I hope to get some experience and tips from you regarding the usage of a Proxmox cluster using Multicast in a (juniper-based) network. Since our multicast experience is quite low and was never required before Proxmox became quickly popular and is meanwhile widely used by our customer, we are a little stuck here. The situation is as follows: Proxmox cluster communicates using multicast between the nodes being a member of the cluster. This works so far with the default configuration (igmp-snooping enabled on Juniper EX for all vlans, nothing further configured) if the nodes are on the same device. It is not working in the following setup: MX480MX80 | | +---+ | EX4550-VC | +---+ || || +---+ +---+ | EX4200-VC | | EX4200-VC | +---+ +---+ | | | Node 1 | Node 3 Node 2 Node 1 & Node 2 see each other but they don't see Node 3. It doesn't matter on which EX4200 Node 1 & 2 are placed, it always works locally but doesn't as soon as data has to travel through the EX4550 core-switch. Most likely a solution would be to simply disable igmp-snooping on the EX4550 for the vlans, where I have to have a working multicast communication. I'd really like to avoid that since we are using vlan-range configurations instead of explicitly configuration each vlan but the latter is required, in order to disable igmp-snooping for just this specific vlan. I am mostly confused why the packets passing the core makes a difference at all. For my understanding, igmp-snooping inspects the communication and passes multicast traffic to exactly those who shall receive it. Why isn't this working? I read that this requires an icmp querier. Would it help to configure that querier on one of the routers (it's two routers because of VRRP)? Can anyone explain why it is working on a local switch but not anymore as soon as a 2nd switch is involved in the path? Hopefully some of you guys are working with setups like this as well and can help to solve our issue. Thanks in advance! Jeff ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
