[j-nsp] Next Gen MVPN and signalling protocol

[Stefan Fouant]

You should be able to do this by configuring PIM/MSDP to use inet.2
for RPF, then use rib groups and policy to make sure you import your
direct routes, IGP routes, and RSVP routes (but not LDP routes) into inet.2.

-- 
Stefan Fouant
Principal Network Engineer
NeuStar, Inc. - http://www.neustar.biz
GPG Key ID: 0xB5E3803D

On Thu, Jun 26, 2008 at 9:34 AM,  <samuel.gay at bt.com> wrote:
> 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
>



-- 
Stefan Fouant
Principal Network Engineer
NeuStar, Inc. - http://www.neustar.biz
GPG Key ID: 0xB5E3803D