[j-nsp] Juniper MVPN and tunnel interfaces.
Ivan Ivanov
ivanov.ivan at gmail.com
Sat May 17 07:23:29 EDT 2014
Hi,
This is quote from "Understanding Junos Next-generation multicast VPN"
"If a PE is a bud router, meaning it has local receivers and also forwards
MPLS packets received over a P2MP LSP
downstream to other P and PE routers, then there is a difference in how
vrf-table-label and vt work. With
vrf-table-label configuration, the bud PE receives two copies of the packet
from the penultimate router: one to
be forwarded to local receivers and the other to be forwarded to downstream
P and PE routers. With vt configuration,
the PE receives a single copy of the packet."
Which means that it should work only with 'vrf-table-label'
Can you send the output from 'show route table mpls label 340240'?
And when you remove the vt- interface from routing-instance to send again
the output form 'show ldp database p2mp'
Ivan,
On Fri, May 16, 2014 at 7:01 PM, Misak Khachatryan <m.khachatryan at gnc.am>wrote:
> Here it is:
>
> misak at MX80-HRAZDAN> show ldp database p2mp
> Input label database, 10.255.255.25:0--10.255.255.1:0
>
> Output label database, 10.255.255.25:0--10.255.255.1:0
>
> Input label database, 10.255.255.25:0--10.255.255.6:0
>
> Output label database, 10.255.255.25:0--10.255.255.6:0
> Label Prefix
> 343248 P2MP root-addr 10.255.255.1, lsp-id 16777218
> 336720 P2MP root-addr 10.255.255.1, lsp-id 16777237
> 341584 P2MP root-addr 10.255.255.1, lsp-id 16777244
> 339488 P2MP root-addr 10.255.255.1, lsp-id 16777271
> 319376 P2MP root-addr 10.255.255.1, lsp-id 16777506
> 319392 P2MP root-addr 10.255.255.1, lsp-id 16777507
> 319408 P2MP root-addr 10.255.255.1, lsp-id 16777508
> 319424 P2MP root-addr 10.255.255.1, lsp-id 16777509
> 319440 P2MP root-addr 10.255.255.1, lsp-id 16777510
> 351104 P2MP root-addr 10.255.255.1, lsp-id 16777511
> 320112 P2MP root-addr 10.255.255.1, lsp-id 16777512
> 342352 P2MP root-addr 10.255.255.1, lsp-id 16777513
> 326112 P2MP root-addr 10.255.255.1, lsp-id 16777514
> 349088 P2MP root-addr 10.255.255.1, lsp-id 16777516
> 319536 P2MP root-addr 10.255.255.6, lsp-id 16777218
> 319552 P2MP root-addr 10.255.255.6, lsp-id 16777223
> 319568 P2MP root-addr 10.255.255.6, lsp-id 16777225
> 319584 P2MP root-addr 10.255.255.6, lsp-id 16777226
> 351024 P2MP root-addr 10.255.255.6, lsp-id 16777228
> 338192 P2MP root-addr 10.255.255.6, lsp-id 16777230
> 320752 P2MP root-addr 10.255.255.6, lsp-id 16777235
> 350752 P2MP root-addr 10.255.255.6, lsp-id 16777259
> 344112 P2MP root-addr 10.255.255.6, lsp-id 16778445
> 319632 P2MP root-addr 10.255.255.6, lsp-id 16778702
> 339552 P2MP root-addr 10.255.255.6, lsp-id 16790511
> 349856 P2MP root-addr 10.255.255.6, lsp-id 16794063
> 333424 P2MP root-addr 10.255.255.6, lsp-id 16802330
> 319936 P2MP root-addr 10.255.255.6, lsp-id 16806929
> 352144 P2MP root-addr 10.255.255.6, lsp-id 16834686
> 352960 P2MP root-addr 10.255.255.6, lsp-id 16838480
> 349296 P2MP root-addr 10.255.255.6, lsp-id 16847033
> 352016 P2MP root-addr 10.255.255.6, lsp-id 16852285
> 339648 P2MP root-addr 10.255.255.6, lsp-id 16852501
> 339696 P2MP root-addr 10.255.255.6, lsp-id 16852914
> 339712 P2MP root-addr 10.255.255.6, lsp-id 16853013
> 339728 P2MP root-addr 10.255.255.6, lsp-id 16853014
> 339744 P2MP root-addr 10.255.255.6, lsp-id 16853015
> 351152 P2MP root-addr 10.255.255.6, lsp-id 16853020
> 333248 P2MP root-addr 10.255.255.6, lsp-id 16853606
> 347760 P2MP root-addr 10.255.255.6, lsp-id 16856317
> 339808 P2MP root-addr 10.255.255.6, lsp-id 16856670
> 351184 P2MP root-addr 10.255.255.6, lsp-id 16857676
> 339888 P2MP root-addr 10.255.255.6, lsp-id 16857837
> 340000 P2MP root-addr 10.255.255.6, lsp-id 16858422
> 340080 P2MP root-addr 10.255.255.6, lsp-id 16859121
> 347440 P2MP root-addr 10.255.255.6, lsp-id 16859279
> 351216 P2MP root-addr 10.255.255.6, lsp-id 16859347
> 344960 P2MP root-addr 10.255.255.6, lsp-id 16859573
> 342288 P2MP root-addr 10.255.255.6, lsp-id 16859585
> 342816 P2MP root-addr 10.255.255.6, lsp-id 16859627
> 349264 P2MP root-addr 10.255.255.6, lsp-id 16859694
> 351248 P2MP root-addr 10.255.255.6, lsp-id 16859725
> 346128 P2MP root-addr 10.255.255.6, lsp-id 16859903
> 351264 P2MP root-addr 10.255.255.6, lsp-id 16859908
> 351296 P2MP root-addr 10.255.255.6, lsp-id 16860084
> 351328 P2MP root-addr 10.255.255.6, lsp-id 16860228
> 351776 P2MP root-addr 10.255.255.6, lsp-id 16860311
> 351920 P2MP root-addr 10.255.255.6, lsp-id 16860397
> 352544 P2MP root-addr 10.255.255.6, lsp-id 16860520
> 352896 P2MP root-addr 10.255.255.6, lsp-id 16860563
>
> Input label database, 10.255.255.25:0--10.255.255.20:0
>
> Output label database, 10.255.255.25:0--10.255.255.20:0
>
> Input label database, 10.255.255.25:0--10.255.255.28:0
> Label Prefix
> 635746 P2MP root-addr 10.255.255.1, lsp-id 16777218
> 630690 P2MP root-addr 10.255.255.1, lsp-id 16777237
> 634914 P2MP root-addr 10.255.255.1, lsp-id 16777244
> 641074 P2MP root-addr 10.255.255.1, lsp-id 16777271
> 635970 P2MP root-addr 10.255.255.1, lsp-id 16777506
> 621906 P2MP root-addr 10.255.255.1, lsp-id 16777507
> 621922 P2MP root-addr 10.255.255.1, lsp-id 16777508
> 621938 P2MP root-addr 10.255.255.1, lsp-id 16777509
> 640642 P2MP root-addr 10.255.255.1, lsp-id 16777510
> 641106 P2MP root-addr 10.255.255.1, lsp-id 16777512
> 635474 P2MP root-addr 10.255.255.1, lsp-id 16777513
> 643330 P2MP root-addr 10.255.255.1, lsp-id 16777514
> 639602 P2MP root-addr 10.255.255.1, lsp-id 16777516
> 624354 P2MP root-addr 10.255.255.6, lsp-id 16777218
> 622050 P2MP root-addr 10.255.255.6, lsp-id 16777223
> 622066 P2MP root-addr 10.255.255.6, lsp-id 16777225
> 622082 P2MP root-addr 10.255.255.6, lsp-id 16777226
> 641138 P2MP root-addr 10.255.255.6, lsp-id 16777228
> 631890 P2MP root-addr 10.255.255.6, lsp-id 16777230
> 640834 P2MP root-addr 10.255.255.6, lsp-id 16777235
> 640866 P2MP root-addr 10.255.255.6, lsp-id 16777259
> 637506 P2MP root-addr 10.255.255.6, lsp-id 16778445
> 642162 P2MP root-addr 10.255.255.6, lsp-id 16778702
> 641186 P2MP root-addr 10.255.255.6, lsp-id 16790511
> 640402 P2MP root-addr 10.255.255.6, lsp-id 16794063
> 641218 P2MP root-addr 10.255.255.6, lsp-id 16806929
> 643394 P2MP root-addr 10.255.255.6, lsp-id 16834686
> 640930 P2MP root-addr 10.255.255.6, lsp-id 16847033
> 642530 P2MP root-addr 10.255.255.6, lsp-id 16852285
> 641314 P2MP root-addr 10.255.255.6, lsp-id 16852501
> 641330 P2MP root-addr 10.255.255.6, lsp-id 16852914
> 641362 P2MP root-addr 10.255.255.6, lsp-id 16853013
> 641378 P2MP root-addr 10.255.255.6, lsp-id 16853014
> 641394 P2MP root-addr 10.255.255.6, lsp-id 16853015
> 641410 P2MP root-addr 10.255.255.6, lsp-id 16853020
> 638482 P2MP root-addr 10.255.255.6, lsp-id 16853606
> 641426 P2MP root-addr 10.255.255.6, lsp-id 16856317
> 641458 P2MP root-addr 10.255.255.6, lsp-id 16856670
> 641474 P2MP root-addr 10.255.255.6, lsp-id 16857676
> 641490 P2MP root-addr 10.255.255.6, lsp-id 16857837
> 641522 P2MP root-addr 10.255.255.6, lsp-id 16859121
> 643586 P2MP root-addr 10.255.255.6, lsp-id 16859279
> 641570 P2MP root-addr 10.255.255.6, lsp-id 16859347
> 636770 P2MP root-addr 10.255.255.6, lsp-id 16859573
> 640802 P2MP root-addr 10.255.255.6, lsp-id 16859585
> 635506 P2MP root-addr 10.255.255.6, lsp-id 16859627
> 641586 P2MP root-addr 10.255.255.6, lsp-id 16859694
> 641618 P2MP root-addr 10.255.255.6, lsp-id 16859725
> 637490 P2MP root-addr 10.255.255.6, lsp-id 16859903
> 641650 P2MP root-addr 10.255.255.6, lsp-id 16859908
> 641682 P2MP root-addr 10.255.255.6, lsp-id 16860084
> 641746 P2MP root-addr 10.255.255.6, lsp-id 16860228
> 642402 P2MP root-addr 10.255.255.6, lsp-id 16860311
> 642386 P2MP root-addr 10.255.255.6, lsp-id 16860397
>
> Output label database, 10.255.255.25:0--10.255.255.28:0
> Label Prefix
> 340240 P2MP root-addr 10.255.255.15, lsp-id 16777242
>
> Input label database, 10.255.255.25:0--10.255.255.33:0
> Label Prefix
> 17 P2MP root-addr 10.255.255.1, lsp-id 16777237
> 17 P2MP root-addr 10.255.255.1, lsp-id 16777506
> 17 P2MP root-addr 10.255.255.1, lsp-id 16777508
> 17 P2MP root-addr 10.255.255.1, lsp-id 16777510
> 17 P2MP root-addr 10.255.255.1, lsp-id 16777512
> 17 P2MP root-addr 10.255.255.1, lsp-id 16777514
> 17 P2MP root-addr 10.255.255.6, lsp-id 16777218
> 17 P2MP root-addr 10.255.255.6, lsp-id 16777223
> 17 P2MP root-addr 10.255.255.6, lsp-id 16777225
> 17 P2MP root-addr 10.255.255.6, lsp-id 16777226
> 17 P2MP root-addr 10.255.255.6, lsp-id 16777228
> 17 P2MP root-addr 10.255.255.6, lsp-id 16777230
> 17 P2MP root-addr 10.255.255.6, lsp-id 16777235
> 17 P2MP root-addr 10.255.255.6, lsp-id 16778445
> 17 P2MP root-addr 10.255.255.6, lsp-id 16778702
> 17 P2MP root-addr 10.255.255.6, lsp-id 16802330
> 17 P2MP root-addr 10.255.255.6, lsp-id 16834686
> 17 P2MP root-addr 10.255.255.6, lsp-id 16838480
> 17 P2MP root-addr 10.255.255.6, lsp-id 16853606
> 17 P2MP root-addr 10.255.255.6, lsp-id 16857676
> 17 P2MP root-addr 10.255.255.6, lsp-id 16859121
> 17 P2MP root-addr 10.255.255.6, lsp-id 16859585
> 17 P2MP root-addr 10.255.255.6, lsp-id 16859908
> 17 P2MP root-addr 10.255.255.6, lsp-id 16860311
> 17 P2MP root-addr 10.255.255.6, lsp-id 16860520
> 17 P2MP root-addr 10.255.255.6, lsp-id 16860563
>
> Output label database, 10.255.255.25:0--10.255.255.33:0
>
> misak at MX80-HRAZDAN>
>
> Best regards,
> Misak Khachatryan,
> Network Administration and Monitoring Manager,
> GNC-Alfa CJSC.
>
>
> ----- Original Message -----
> From: "Bikram Singh" <sbikram at live.com>
> To: "Misak Khachatryan" <m.khachatryan at gnc.am>, "juniper-nsp" <
> juniper-nsp at puck.nether.net>
> Sent: Friday, May 16, 2014 7:57:33 PM
> Subject: RE: [j-nsp] Juniper MVPN and tunnel interfaces.
>
> ok . Can you share below output from both the PEs
> show ldp database p2mp .
>
>
> > Date: Fri, 16 May 2014 18:57:04 +0400
> > From: m.khachatryan at gnc.am
> > To: sbikram at live.com; juniper-nsp at puck.nether.net
> > Subject: Re: [j-nsp] Juniper MVPN and tunnel interfaces.
> >
> > Hi Bikram,
> >
> > Yes, it's transit, but others too. I use LDP P2MP.
> >
> > misak at MX80-HRAZDAN> show mpls lsp p2mp
> > Ingress LSP: 0 sessions
> > Total 0 displayed, Up 0, Down 0
> >
> > Egress LSP: 0 sessions
> > Total 0 displayed, Up 0, Down 0
> >
> > Transit LSP: 0 sessions
> > Total 0 displayed, Up 0, Down 0
> >
> > misak at MX80-HRAZDAN>
> >
> >
> >
> > Bikram Singh wrote:
> > >
> > >
> > >
> > > > Date: Fri, 16 May 2014 16:28:56 +0400
> > > > From: m.khachatryan at gnc.am
> > > > To: juniper-nsp at puck.nether.net
> > > > Subject: [j-nsp] Juniper MVPN and tunnel interfaces.
> > > >
> > >
> > >
> > > Is this PE also acting as a transit to other PE for Multicast traffic ?
> > >
> > > can u share below
> > >
> > > show mpls lsp p2mp ?
> > >
> > >
> > >
> > >
> > > -bs
> > >
> > >
> > >
> >
> > --
> > Best regards,
> > Misak Khachatryan,
> > Network Administration and Monitoring Manager,
> > GNC-Alfa CJSC.
>
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>
--
Best Regards!
Ivan Ivanov
More information about the juniper-nsp
mailing list