[j-nsp] track-igp-metric in LDP

[aaron1 at gvtc.com]

I had to do this with my cgnat deployment.  I had an unforeseen and
undesirable result of all my customer facing mpls pe's using one and only
one of my cgnat boundary mx960's. (this was via an mpls l3vpn)  not good, I
need the pe's to flow towards the igp-closest mx960 towards the internet.
Thus load balancing via multiple mx960's and using separate and unique
public ipv4 pools.  This track-igp-metric did the trick.  It allowed my
cgnat boundary nodes to be seen as more or less attractive from the customer
facing mpls pe perspective.

As someone stated, i think it's rsvp, mp-ibgp for vpns and perhaps other
things that make use of inet.3 in it's best path calculations

-Aaron

-----Original Message-----
From: juniper-nsp <juniper-nsp-bounces at puck.nether.net> On Behalf Of Chen
Jiang
Sent: Sunday, August 2, 2020 5:11 AM
To: Juniper List <juniper-nsp at puck.nether.net>
Subject: [j-nsp] track-igp-metric in LDP

Hi! Experts

Sorry for disturbing, I am curious about track-igp-metric knob under LDP, is
there any scenarios it will be useful? I think ldp is just a label
distribution protocol, the forwarding path always follows the IGP shortest
path, is there any benefit for using track-igp-metric?

Thanks for your help!

--
BR!



           James Chen
_______________________________________________
juniper-nsp mailing list juniper-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp