At this point I opted for a different design. I no longer have the
mcast clients gathered into a vlan, which requires igmp snooping. I
changed the mcast client ports to be L3. I just assign a /30 to each
mcast client interface on the ACX5048. This way there is no need for
igmp snooping. A
Hi Aaron,
since ACX series is based on Broadcom PFE , and based on your description of
the issue..
=> When you enable igmp-snooping (in Broadcom based PFE devices like
EX3400/QFX5100s) there are some associated dynamic filters / IFP/VFP gets
created in PFE , and if there are some
thanks for this... i think i misunderstood the use of l2-querier from a
previous project i worked on, and put it here where i really didn't need
it. moving forward i will only use igmp snooping in the vlan, and not
the l2-querier option. but with all that said, i still don't understand
why
Thanks Aditya, here's my re-creation of this scenario in my lab... but
it works with the pim/igmp config that i have, and the ospf neighboring
over the l2circuit continues to work. isn't ospf 224 packets "hidden"
inside encapsulation over l2circuit? how would pfe in 5048 use 224
routes seen
I thought this was asked, but don’t recall an answer, what’s the point of
turning on a querier if the switch is already a PIM router? You don’t need
an IGMP snooping querier if it’s a multicast router.
On Fri, Feb 2, 2024 at 8:21 AM Aaron Gould via juniper-nsp <
juniper-nsp@puck.nether.net>
When you enabled pim multicast routes are added to the pfe, this is mostly
breaking ospf over l2 ckt because these packets are mostly now matching the
default 224 routes added to pfe . Without having any show commands or
rtsockmon it’s difficult to debug anything
-Aditya
Google
On Fri, Feb 2,
I tried to recreate the scenario in my lab with no success
21.2R3-S4.8 - in lab - problem not seen
20.2R3-S7.3 - in lab - problem not seen
19.2R3-S6.1 - in lab - problem not seen
18.3R3-S6.1 - in lab - problem not seen
17.4R2-S11 - in lab - problem not seen
17.4R2-S11 - in field - problem
thanks and yes, working on it
i've done my best to recreate this scenario in my lab...
21.2R3-S4.8 - in lab - problem not seen
20.2R3-S7.3 - in lab - downgraded an hour ago - problem not seen
19.2R3-S6.1 - in lab - downgrading now... will let you know... if good,
will continue
18.3R3-S6.1
Hi Aaron,
as you're using a 3,5 years old junos, is it possible to upgrade and check if
the problem is fixed in a newer version?
The latest is from March 2022, but I would still expect some bug fixing.
Maybe there is something wrong in the programming of the hardware...
Kind regards
Karsten
Am
does this help?
ACX5048
- port ge-0/0/4 - vlan 100 - multicast listener/client
- port ge-0/0/5 - vlan 100 - multicast listener/client
- port ge-0/0/6 - vlan 100 - multicast listener/client
- irb.100 routes that vlan - runs pim/igmp/igmp-snooping l2-querier
- xe-0/0/0 - an uplink port running pim
Hi Aaron,
It's not clear from your explanation where l2circuits with ospf are
connected and how they are related to this irb/vlan.
Do you really need a querier in this case? IIRC, querier is needed when
only hosts are present on LAN and a switch has to send igmp queries. In
your case, you
I'm having an issue where igmp snooping layer 2 querier breaks ospf in other
devices which are in l2circuits
Has anyone ever come across this issue, and have a work-around for it?
I have the following configured and devices in vlan 100 can join multicast just
fine. But there are other
12 matches
Mail list logo
