[j-nsp] BGP/MPLS Question MX Platform

[Dean Bolton]

I'm not opposed to using RSVP if necessary.  All links are MPLS
capable...just trying to find a way to not let BGP use the A-C link for IP
transit traffic and only use it for protection of the MPLS traffic.  A-C is
a smaller capacity link than the others which is why I don't want to
saturate it with IP traffic that can just come from A or C directly.


On Tue, Aug 2, 2016 at 3:22 PM, Mark Tinka <mark.tinka at seacom.mu> wrote:

>
>
> On 2/Aug/16 22:14, Dean Bolton wrote:
>
> Hi,
>
> I have a small network with 3 nodes that are connected in a "ring", ie A to
> B, B to C, C to A.  I'm running MPLS w/LDP for l2circuits and ISIS as the
> IGP.  MPLS is working fine including if one of the links fails.  Nodes A
> and C also have IP transit connections to upstream carriers and all three
> nodes have BGP setup.  What I would like to do is prevent BGP from using
> the A to C link for any traffic or only traffic that I specify and the A to
> C link only be used for MPLS.  I haven't quite been able to figure out how
> one could accomplish that since the loopbacks are reachable via MPLS and/or
> IGP and they will use that link during a failure of A-B or B-C.
>
>
> If you use LDP as your label distribution protocol, this will be difficult.
>
> I could see you solving this by using RSVP, but I'm only theorizing this,
> as I'd be wary of having a partitioned MPLS network within the same IGP
> domain. Strange things could happen if MPLS-switched traffic ends up on a
> link that has no MPLS capabilities.
>
> Mark.
>
>