: jeudi 26 juin 2008 16:26
À : Gay,S,Samuel,JPECS R; juniper-nsp@puck.nether.net
Objet : Re: [j-nsp] Next Gen MVPN and signalling protocol
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
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
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
Of course, you may also need to do some filtering or modify protocol
preferences to ensure that the RSVP routes are not populated into your
unicast routing tables or if they are, that they should be less
preferred than your LDP routes.
--
Stefan Fouant
Principal Network Engineer
NeuStar, Inc. -
routes together with using no-install-to with
install prefix/mask LSP knobs.
Rgds
Alex
- Original Message -
From: [EMAIL PROTECTED]
To: juniper-nsp@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
PROTECTED] On Behalf Of [EMAIL PROTECTED]
Sent: Thursday, June 26, 2008 4:35 PM
To: juniper-nsp@puck.nether.net
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
6 matches
Mail list logo
