[j-nsp] MPLS Endpoint Discussion

[Alexander Arseniev]

Yes
Ato did not offer an explanation, I will fill the void for him -
in JUNOS, for L2VPN/L3VPN services to work, the MPLS tailend route in 
inet.3 must exactly match the L2VPN/L3VPN route' protocol nexthop.
JUNOS automatically populates the L2VPN/L3VPN route protocol nexthop 
with originating PE' lo0.0 primary IP.
So, if You feeling warm about nexthop rewriting via BGP policies, then 
You could use link addresses, otherwise use MPLS tailend' lo0.0 primary 
IP for RSVP LSP "to" parameter on headend.
HTH
Thanks
Alex


On 02/07/2015 15:28, Antonio Sanchez-Monge wrote:
> loopbacks
>
> On 7/2/15, 4:25 PM, "juniper-nsp on behalf of Levi Pederson"
> <juniper-nsp-bounces at puck.nether.net on behalf of
> levipederson at mankatonetworks.net> wrote:
>
>> All,
>>
>> I've created simpler MPLS ring between a total of 6 MPLS 4550s.  My
>> questions what IP do I use for the Label Switched Path Endpoints. I can't
>> seem to find a "best practice."
>>
>> Specifically this code
>>
>> Obfuscated as I'm a little to literal with my descriptions
>>
>> set protocols mpls label-switched-path PE2-to-PE1 to 10.254.1.1
>> set protocols mpls label-switched-path PE2-to-PE3 to 10.254.1.6
>> set protocols mpls label-switched-path PE2-to-PE4 to 10.254.0.4
>>
>>
>> Do I use the /30 that exists between the Legs?
>>
>> Or should I use the LoopBack0 ?
>>
>> My thought would be Leg itself as it creates the path.  But some documents
>> state LoopBack.
>>
>>
>> Thank you,
>>
>> *Levi Pederson*
>> Mankato Networks LLC
>> cell | 612.481.0769
>> work | 612.787.7392
>> levipederson at mankatonetworks.net
>> _______________________________________________
>> juniper-nsp mailing list juniper-nsp at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/juniper-nsp
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp