Mailing List Archive: P2MP traffic loss over QFX and EX series

P2MP traffic loss over QFX and EX series

Sep 2, 2023, 4:07 PM

Post #1 of 5 (283 views)

Hi everyone,

I have multicast traffic through a P2MP LSP and when this traffic goes
through an EX or QFX series switch (spot EX4600 and QFX5110/5120) it is
lost. We use these switches as multilayer, they have MPLS suite protocols
(ISIS, LDP and RSVP).

*>show versionModel: ex4600-40fJunos: 21.4R3.15 (recommended version at
day)*

The switch see the transit LSP from IP 2.2.2.2 to 1.1.1.1:

*> show mpls lspTransit LSP: 2 sessionsTo From State Rt Style
Labelin Labelout LSPname2.2.2.2 1.1.1.1 Up 0 1 SE 6 2
lsp1Total 2 displayed, Up 2, Down 0*

Traffic from 1.1.1.1 come's via ae0:

*> show route 1.1.1.11.1.1.1/32 <http://1.1.1.1/32> *[IS-IS/18] via
ae0.01.1.1.1/32 <http://1.1.1.1/32> *[LDP/9] via ae0.0, Push 315471*

Traffic to 2.2.2.2 goes via ae3:

*> show route 2.2.2.22.2.2.2/32 <http://2.2.2.2/32> *[IS-IS/18] 20:36:26,
via ae3.02.2.2.2/32 <http://2.2.2.2/32> *[LDP/9] 20:36:25, via ae3.0*

The P2MP traffic see on input interface but they not replicate at the
output:

*Interface: ae0, Enabled, Link is UpInput bytes: 7282719382422 (785608168
bps) [207824323]Input packets: 5263502719 (70972 pps) [223103]Interface:
ae3, Enabled, Link is Up Output bytes: 186620844 (26760 bps) [7545]
Output packets: 1225967 (13 pps) [47]*
Has anyone ever had a similar problem? or are you certain that this type of
LSP will NOT work on these switches?

Thanks, Gonzalo.
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Re: P2MP traffic loss over QFX and EX series [ In reply to ]

juniper-nsp at puck

Sep 2, 2023, 10:23 PM

Post #2 of 5 (283 views)

Permalink

On 9/3/23 01:07, Gonzalo Caceres via juniper-nsp wrote:
> Hi everyone,
>
> I have multicast traffic through a P2MP LSP and when this traffic goes
> through an EX or QFX series switch (spot EX4600 and QFX5110/5120) it is
> lost. We use these switches as multilayer, they have MPLS suite protocols
> (ISIS, LDP and RSVP).
>
>
>
> *>show versionModel: ex4600-40fJunos: 21.4R3.15 (recommended version at
> day)*
>
> The switch see the transit LSP from IP 2.2.2.2 to 1.1.1.1:
>
>
>
>
> *> show mpls lspTransit LSP: 2 sessionsTo From State Rt Style
> Labelin Labelout LSPname2.2.2.2 1.1.1.1 Up 0 1 SE 6 2
> lsp1Total 2 displayed, Up 2, Down 0*
>
> Traffic from 1.1.1.1 come's via ae0:
>
>
> *> show route 1.1.1.11.1.1.1/32 <http://1.1.1.1/32> *[IS-IS/18] via
> ae0.01.1.1.1/32 <http://1.1.1.1/32> *[LDP/9] via ae0.0, Push 315471*
>
> Traffic to 2.2.2.2 goes via ae3:
>
>
> *> show route 2.2.2.22.2.2.2/32 <http://2.2.2.2/32> *[IS-IS/18] 20:36:26,
> via ae3.02.2.2.2/32 <http://2.2.2.2/32> *[LDP/9] 20:36:25, via ae3.0*
>
> The P2MP traffic see on input interface but they not replicate at the
> output:
>
>
>
>
>
>
>
>
> *Interface: ae0, Enabled, Link is UpInput bytes: 7282719382422 (785608168
> bps) [207824323]Input packets: 5263502719 (70972 pps) [223103]Interface:
> ae3, Enabled, Link is Up Output bytes: 186620844 (26760 bps) [7545]
> Output packets: 1225967 (13 pps) [47]*
> Has anyone ever had a similar problem? or are you certain that this type of
> LSP will NOT work on these switches?

I remember several late-night calls with Juniper, nearly a decade ago,
when we were evaluating their Broadcom-based platforms for deployments
where NG-MVPN had been anticipated, both via p2mp RSVP-TE as well as mLDP.

They were not comfortable committing to supporting NG-MVPN on their
Broadcom boxes then. I'm not sure how far that has come in 2023, but
probably worth reaching out to your SE and asking about whether what you
are trying to do is supported on the Broadcom chips your boxes are running.

Mark.
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Re: P2MP traffic loss over QFX and EX series [ In reply to ]

juniper-nsp at puck

Sep 5, 2023, 8:05 AM

Post #3 of 5 (282 views)

Permalink

Hi Mark, thanks for the quick reply!

It is a problem that we have been having for some time, and we have not
received concrete answers from our SE. That's why I checked here, as I
haven't seen colleagues expressing this flaw in other posts either. Thanks
again.

Regards. Gonzalo.
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Re: P2MP traffic loss over QFX and EX series [ In reply to ]

juniper-nsp at puck

Sep 5, 2023, 8:10 PM

Post #4 of 5 (277 views)

Permalink

On 9/5/23 17:05, Gonzalo Caceres via juniper-nsp wrote:

> Hi Mark, thanks for the quick reply!
>
> It is a problem that we have been having for some time, and we have not
> received concrete answers from our SE. That's why I checked here, as I
> haven't seen colleagues expressing this flaw in other posts either. Thanks
> again.

I suspect it could be an issue related to Broadcom, which I understand
Juniper may have been able to workaround through code (with some
limitations on performance). But your SE will be your best bet.

Mark.
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Re: P2MP traffic loss over QFX and EX series [ In reply to ]

juniper-nsp at puck

Sep 11, 2023, 10:53 AM

Post #5 of 5 (263 views)

Permalink

This PR may be worth asking about.

https://prsearch.juniper.net/problemreport/PR1693424

On Sat, Sep 2, 2023 at 7:08?PM Gonzalo Caceres via juniper-nsp <
juniper-nsp@puck.nether.net> wrote:

> Hi everyone,
>
> I have multicast traffic through a P2MP LSP and when this traffic goes
> through an EX or QFX series switch (spot EX4600 and QFX5110/5120) it is
> lost. We use these switches as multilayer, they have MPLS suite protocols
> (ISIS, LDP and RSVP).
>
>
>
> *>show versionModel: ex4600-40fJunos: 21.4R3.15 (recommended version at
> day)*
>
> The switch see the transit LSP from IP 2.2.2.2 to 1.1.1.1:
>
>
>
>
> *> show mpls lspTransit LSP: 2 sessionsTo From State Rt Style
> Labelin Labelout LSPname2.2.2.2 1.1.1.1 Up 0 1 SE 6 2
> lsp1Total 2 displayed, Up 2, Down 0*
>
> Traffic from 1.1.1.1 come's via ae0:
>
>
> *> show route 1.1.1.11.1.1.1/32 <http://1.1.1.1/32> *[IS-IS/18] via
> ae0.01.1.1.1/32 <http://1.1.1.1/32> *[LDP/9] via ae0.0, Push 315471*
>
> Traffic to 2.2.2.2 goes via ae3:
>
>
> *> show route 2.2.2.22.2.2.2/32 <http://2.2.2.2/32> *[IS-IS/18] 20:36:26,
> via ae3.02.2.2.2/32 <http://2.2.2.2/32> *[LDP/9] 20:36:25, via ae3.0*
>
> The P2MP traffic see on input interface but they not replicate at the
> output:
>
>
>
>
>
>
>
>
> *Interface: ae0, Enabled, Link is UpInput bytes: 7282719382422 (785608168
> bps) [207824323]Input packets: 5263502719 (70972 pps) [223103]Interface:
> ae3, Enabled, Link is Up Output bytes: 186620844 (26760 bps) [7545]
> Output packets: 1225967 (13 pps) [47]*
> Has anyone ever had a similar problem? or are you certain that this type of
> LSP will NOT work on these switches?
>
> Thanks, Gonzalo.
> _______________________________________________
> 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