Re: [j-nsp] igmp snooping layer 2 querier breaks ospf in other devices
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 Donnerstag, 1. Februar 2024, 19:41:12 CET schrieb Aaron Gould via juniper- nsp: > 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 to route ssm multicast joins to > the multicast sender > - port ge-0/0/2 is mapped to an l2circuit over mpls to some remote location > --- i don't see ge-0/0/2 related at all to the vlan 100 where i run > multicast > > -Aaron > > On 2/1/2024 8:19 AM, Andrey Kostin wrote: > > 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 have a router with irb interface that > > should work as igmp querier by default. Not sure if it helps though. > > > > Kind regards, > > Andrey > > > > Aaron Gould via juniper-nsp писал(а) 2024-01-31 14:54: > >> 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 unrelated l2circuits that > >> carry traffic for devices in other vlans and inside this l2circuit is > >> ospf hellos that seem to be getting broken by this configuration > >> > >> set interfaces irb unit 100 family inet address 10.100.4.1/27 > >> set protocols ospf area 0.0.0.1 interface irb.100 passive > >> set protocols igmp interface irb.100 version 3 > >> set protocols pim interface irb.100 > >> set protocols igmp-snooping vlan vlan100 l2-querier source-address > >> 10.100.4.1 > >> > >> Model: acx5048 > >> Junos: 17.4R2-S11 ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] JunOS 18, ELS vs non-ELS QinQ native vlan handling.
--- Begin Message ---
Hi,
I haven't tested the behvaior, but to avoid the big surprises you should at
least check the tables in
the kb:
https://kb.juniper.net/InfoCenter/index?page=content=KB35261=RSS
As you're not writing the exact release, there was a change if you upgraded
from R1 or R2.
Kind regards
Karsten
Am Freitag, 9. April 2021, 10:02:21 schrieb Antti Ristimäki:
> Hi list,
>
> Returning to this old thread. It seems that the behaviour has again changed,
> because after upgrading QFX5110 to 18.4R3-S7 the switch does not add the
> native-vlan tag when forwarding the frame to QinQ uplink. Previously with
> version 17.3 the switch did add the native-vlan tag along with the S-tag.
> It seems that "input-native-vlan-push " is available as a
> hidden command in 18.4R3-S7, but it doesn't seem to have any impact on the
> behaviour.
>
> Any experience from others?
>
> Antti
>
> - On 22 Mar, 2019, at 19:03, Alexandre Snarskii s...@snar.spb.ru wrote:
> > Hi!
> >
> > Looks like JunOS 18.something introduced an incompatibility of native
> > vlan handling in QinQ scenario between ELS (qfx, ex2300) and non-ELS
> > switches: when ELS switch forwards untagged frame to QinQ, it now adds
> > two vlan tags (one specified as native for interface and S-vlan) instead
> > of just S-vlan as it is done by both non-ELS and 'older versions'.
> >
> > As a result, if the other end of tunnel is non-ELS (or third-party)
> > switch, it strips only S-vlan and originally untagged frame is passed
> > with vlan tag :(
> >
> > Are there any way to disable this additional tag insertion ?
> >
> > PS: when frames sent in reverse direction, non-ELS switch adds only
> > S-vlan and this frame correctly decapsulated and sent untagged.
> >
> > ELS-side configuration (ex2300, 18.3R1-S1.4. also tested with
> > qfx5100/5110):
> >
> > [edit interfaces ge-0/0/0]
> > flexible-vlan-tagging;
> > native-vlan-id 1;
> > mtu 9216;
> > encapsulation extended-vlan-bridge;
> > unit 0 {
> >
> >vlan-id-list 1-4094;
> >input-vlan-map push;
> >output-vlan-map pop;
> >
> > }
> >
> > (when native-vlan-id is not configured, untagged frames are not
> > accepted at all).
> >
> > ___
> > juniper-nsp mailing list juniper-nsp@puck.nether.net
> > https://puck.nether.net/mailman/listinfo/juniper-nsp
> >
> >
> > --
>
> ___
> juniper-nsp mailing list juniper-nsp@puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
--- End Message ---
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] If there's anyone from Juniper on the list.....
Hi, If it is on a Web page you can simply use the star rating and leave feedback with a comment. My response rate from the documentation team is still 100%. Originalnachricht Von: Chris Boyd Gesendet: Dienstag, 15. Mai 2018 19:08 An: juniper-nsp@puck.nether.net Betreff: [j-nsp] If there's anyone from Juniper on the list. Who can get a message over to the Documentation group, it would be great if you could update the doc on the “insert” command to note that you have to create the object first, and then move it with the insert. May be common knowledge to old hands, but I’m still learning the ins and outs of JunOS. Looking at the doc, it seems that the order of operations would be this: edit firewall family inet filter foo insert term bar before term xyzzy error: statement ‘bar' not found But it’s actually this: edit firewall family inet filter foo set term bar from source-prefix-list source set term bar from destination-prefix-list dest set term bar from protocol tcp set term bar from destination-port ssh insert term bar before term xyzzy —Chris ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
