[j-nsp] Next Gen MVPN and signalling protocol

[Alex]

Samuel,
p2mp RSVP LSP egress LSR lo0.0 IP@ are not present in inet.0/inet.3 and 
therefore unicast traffic cannot use NGEN MVPN p2mp LSP.
If you have p2p RSVP LSP and you stll want to use LDP (cannot imagine why 
but let's assume so) then consider changing next-hops of IPv4 
unicast/L3VPN/L2VPN routes together with using "no-install-to"  with 
"install <prefix/mask>" LSP knobs.
Rgds
Alex

----- Original Message ----- 
From: <samuel.gay at bt.com>
To: <juniper-nsp at puck.nether.net>
Sent: Thursday, June 26, 2008 2:34 PM
Subject: [j-nsp] Next Gen MVPN and signalling protocol


> Hi group,
>
> This is my "problem":
>
> We have an MPLS backbone using LDP. We are configuring Next Gen MVPN.
> For that we have to configure RSVP on all the core router. The problem
> is that we would like to keep LDP for the data and RSVP for the
> multicast, but like RSVP has a preference of 7 and LDP has a preference
> of 9, all the traffic use now the LSPs created with RSVP.
> The easiest way will be to increase RSVP preference to 10, but I can't
> do it.
>
> I am studying some advanced options like "install-nexthop lsp lsp-name",
> "traffic-engineering bgp-igp", "traffic-engineering mpls-forwarding",
> but it seems not to be the good way. May be an other idea will be to use
> an other routing-table just for multicast for each L3-VPN.
>
> Do you have some advices?
>
> Thanks !
> Samuel
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp