Routing
Highlighted
Routing

VPLS MPLS-TE problem

‎10-04-2014 12:51 AM

Hello

I need help with finding the best solution for this topology:

 

topology.png

 

 

I need to route traffic from VPLS Black instance through S42 and Red instance through S43. Can you give me any ideas/clues how to achieve that? I have to use MPLS-TE. I am using Juniper MX80s.

In the core network I have already configured:
-ospf with TE
- LDP
- iBGP
- LSP between PEs (S40 and S41)

I was thinking about simple mpls path, rsvp and mpls-forwarding but I dont know how to use this in my example topology (how to route a traffic from speciffic instace).

Thank you for your help in advance

 

 

10 REPLIES 10
Highlighted
Routing

Re: VPLS MPLS-TE problem

‎10-04-2014 05:02 AM

Hi,

 

You started well.

 

 

First you need to create two distinct RSVP-signalled LSPs. With the help of EROs each of them will be able to follow the paths you intend for them. Also make sure those two LSPs have the same metric. They should have according your topology. Let's call these LSPS: LSP_1 and LSP_2.

 

Then comes the second part of the solution: you'll need to manipulate on the ingress PE the LFIB so that you select one specific LSP for forward.

When multiple equal-cost LSPs to a destination exist, you can use a policy to control which LSP is actually installed in the forwarding table.

A possible template on the ingress router for such a configuration:

 

routing-options {
  forwarding-table {
    export lsp-policy;
  }
}
policy-options {
  policy-statement lsp-policy {
    term p1 {
      from community p1;
      then {
        install-nexthop lsp LSP_1;
        accept;
      }
    }
    term p2 {
      from community p2;
      then {
        install-nexthop lsp LSP_2;
        accept;
      }
    }
    term last {
      then accept;
    } } }

 

Communities p1 would be associated with VPLS instance 1 whereas community p2 would be associated with VPLS instance 2.

 

 

 

 

--
Click the star for kudos if you think I earned it.
If this post solves your problem, please mark this post as "Accepted Solution".

 

 

 

Highlighted
Routing
Solution
Accepted by topic author anetilav
‎08-26-2015 01:27 AM

Re: VPLS MPLS-TE problem

[ Edited ]
‎10-04-2014 08:27 AM

Hi,

 

You need to set the comunity explicitly for vpls under the routing-instance to get this working.

 

show policy-options {

policy-statement VPLS-LSP-MAP {
    term vpls-black {
        from community BLACK;
        then {
            install-nexthop lsp LSP-VIA-S42;
            accept;
        }
    }
    term vpls-red {
        from community RED;
        then {
            install-nexthop lsp LSP-VIA-S43;
            accept;
        }
    }
}

community BLACK members 100:100;

community RED members 200:200;

}

 

 

 

show protocols mpls
label-switched-path LSP-VIA-S42 {
    to 10.10.10.41;
    primary path-via-S42;
}
label-switched-path LSP-VIA-S43 {
    to 10.10.10.41;
    primary path-via-S43;
}
path path-via-S42 {
    10.10.10.42;
}
path path-via-S43 {
    10.10.10.43;
}

 

 

show routing-instances

VPLS-BLACK {

<..>
    protocols {
        vpls {
            community BLACK;

        <...>
        }
    }
}
VPLS-RED {

<..>
    protocols {
        vpls {
            community RED;

        <...>
        }
    }
}

 

show routing-options
<..>
forwarding-table {
    export VPLS-LSP-MAP;
}

 

Regards

Surya

 

 

Highlighted
Routing

Re: VPLS MPLS-TE problem

[ Edited ]
‎10-05-2014 01:20 AM

Thank you very much for reply 🙂

 

There is one problem:

 

lab@S40> show route forwarding-table 

 

Routing table: default.mpls
MPLS:
Destination Type RtRef Next hop Type Index NhRef Netif
default          perm 0 dscd 50 1
0                    user 0 recv 49 4
1                    user 0 recv 49 4
2                    user 0 recv 49 4
13                  user 0 recv 49 4
262147         user 0 Pop 612 2 lsi.1050112   #
262156         user 0 Pop 615 2 lsi.1050113   # labels for instances
300016         user 0 10.100.10.10 Pop 604 2 ge-1/1/3.0
300016(S=0) user 0 10.100.10.10 Pop 605 2 ge-1/1/3.0  # this is S43
300032            user 0 10.100.10.2 Pop 606 2 ge-1/1/2.0
300032(S=0) user 0 10.100.10.2 Pop 607 2 ge-1/1/2.0   #S42
300048           user 0 10.100.10.6 Pop 610 2 ge-1/1/1.0
300048(S=0) user 0 10.100.10.6 Pop 609 2 ge-1/1/1.0
lsi.1050112 (VPLS) user 0 indr 1048574 4
10.100.10.6 Push 262145 608 2 ge-1/1/1.0
lsi.1050113 (VPLS) user 0 indr 1048575 4
10.100.10.6 Push 262154 613 2 ge-1/1/1.0

 

seems that they are still going through S40-S41 .

 

Routing table: VPLS-BLACK.vpls
VPLS:
Destination Type RtRef Next hop Type Index NhRef Netif
default perm 0 dscd 551 1
lsi.1050112 intf 0 indr 1048574 4
10.100.10.6 Push 262145 608 2 ge-1/1/1.0
0x30005/51 user 0 comp 623 2
ge-1/0/5.0 intf 0 ucst 581 4 ge-1/0/5.0
0x30003/51 user 0 comp 589 2
0x30001/51 user 0 comp 586 2

 

Routing table: VPLS-RED.vpls
VPLS:
Destination Type RtRef Next hop Type Index NhRef Netif
default perm 0 dscd 555 1
lsi.1050113 intf 0 indr 1048575 4
10.100.10.6 Push 262154 613 2 ge-1/1/1.0
0x30006/51 user 0 comp 633 2
ge-1/0/6.0 intf 0 ucst 582 4 ge-1/0/6.0
0x30004/51 user 0 comp 598 2
0x30002/51 user 0 comp 595 2

 

 

Or I am using wrong command to trace traffic from vpls instances.

Highlighted
Routing

Re: VPLS MPLS-TE problem

‎10-05-2014 05:52 AM

Hi,

 

From below captures it looks like it is taking directly connected path between S40-S41 for both VPLS as I don't see second label push.

 

lsi.1050112 (VPLS) user 0 indr 1048574 4
              10.100.10.6 Push 262145 608 2 ge-1/1/1.0
lsi.1050113 (VPLS) user 0 indr 1048575 4
              10.100.10.6 Push 262154 613 2 ge-1/1/1.0

 

Also can you confirm if you have applied below config?

 

set routing-options forwarding-table export VPLS-LSP-MAP

 

Please provide the capture for "show route 10.10.10.41 extensive from S40"

 

Regards

Surya

 

Highlighted
Routing

Re: VPLS MPLS-TE problem

‎10-05-2014 09:15 AM

I have apllied: set routing-options forwarding-table export VPLS-LSP-MAP

 

lab@S40# run show route 10.10.10.41 extensive

 

inet.0: 15 destinations, 15 routes (15 active, 0 holddown, 0 hidden)
10.10.10.41/32 (1 entry, 1 announced)
State: <FlashAll>
TSI:
KRT in-kernel 10.10.10.41/32 -> {10.100.10.6}
*OSPF Preference: 10
Next hop type: Router, Next hop index: 603
Address: 0x27410b0
Next-hop reference count: 4
Next hop: 10.100.10.6 via ge-1/1/1.0, selected
Session Id: 0x2803
State: <Active Int>
Local AS: 65546
Age: 3:51 Metric: 1
Validation State: unverified
Area: 0.0.0.0
Task: OSPF
Announcement bits (2): 0-KRT 3-LDP
AS path: I

inet.3: 3 destinations, 3 routes (3 active, 0 holddown, 0 hidden)

10.10.10.41/32 (1 entry, 1 announced)
State: <FlashAll>
*LDP Preference: 9
Next hop type: Router
Address: 0x274148c
Next-hop reference count: 4
Next hop: 10.100.10.6 via ge-1/1/1.0, selected
Session Id: 0x2803
State: <Active Int>
Local AS: 65546
Age: 3:51 Metric: 1
Validation State: unverified
Task: LDP
Announcement bits (1): 2-Resolve tree 1
AS path: I

Highlighted
Routing

Re: VPLS MPLS-TE problem

‎10-05-2014 09:50 AM

Hi,

 

In inet.3 table, I see only LDP route towards the other PE S41.

With the suggested config, there should have been 2 RSVP routes. Can you please confirm if the RSVP LSPs are up?

 

 

lab@S40# run show route 10.10.10.41 extensive

<..>

inet.3: 3 destinations, 3 routes (3 active, 0 holddown, 0 hidden)

10.10.10.41/32 (1 entry, 1 announced)

*LDP Preference: 9
Next hop type: Router
Address: 0x274148c
Next-hop reference count: 4
Next hop: 10.100.10.6 via ge-1/1/1.0, selected

 

 

Regards

Surya

Highlighted
Routing

Re: VPLS MPLS-TE problem

[ Edited ]
‎10-05-2014 10:36 AM

lab@S40# run show rsvp session
Ingress RSVP: 0 sessions
Total 0 displayed, Up 0, Down 0

Egress RSVP: 0 sessions
Total 0 displayed, Up 0, Down 0

Transit RSVP: 0 sessions
Total 0 displayed, Up 0, Down 0

 

In attachment there is configuration of S40. 

 

 

 

-----------------------------

edit:

 

I have set 'no-cspf' in mpls. Effect:

 

lab@S40# run show rsvp session
Ingress RSVP: 2 sessions
To From State Rt Style Labelin Labelout LSPname
10.10.10.41 10.10.10.40 Dn 0 0 - - - LSP-VIA-S42
10.10.10.41 10.10.10.40 Dn 0 0 - - - LSP-VIA-S43
Total 2 displayed, Up 0, Down 2

Egress RSVP: 0 sessions
Total 0 displayed, Up 0, Down 0

Transit RSVP: 0 sessions
Total 0 displayed, Up 0, Down 0

 

 

--------------------------

 

lab@S40# run show mpls lsp extensive
Ingress LSP: 2 sessions

10.10.10.41
From: 10.10.10.40, State: Dn, ActiveRoute: 0, LSPname: LSP-VIA-S42
ActivePath: (none)
LSPtype: Static Configured, Penultimate hop popping
LoadBalance: Random
Metric: 10
Encoding type: Packet, Switching type: Packet, GPID: IPv4
Primary path-via-S42 State: Dn
Priorities: 7 0
SmartOptimizeTimer: 180
3 Oct 5 17:51:08.228 Explicit Route: bad strict route[11 times]
2 Oct 5 17:45:44.216 Originate Call
1 Oct 5 17:45:31.080 CSPF failed: no route toward 10.10.10.42[62 times]
Created: Sun Oct 5 17:15:45 2014

10.10.10.41
From: 10.10.10.40, State: Dn, ActiveRoute: 0, LSPname: LSP-VIA-S43
ActivePath: (none)
LSPtype: Static Configured, Penultimate hop popping
LoadBalance: Random
Metric: 10
Encoding type: Packet, Switching type: Packet, GPID: IPv4
Primary path-via-S43 State: Dn
Priorities: 7 0
SmartOptimizeTimer: 180
3 Oct 5 17:51:08.228 Explicit Route: bad strict route[11 times]
2 Oct 5 17:45:44.218 Originate Call
1 Oct 5 17:45:25.527 CSPF failed: no route toward 10.10.10.43[62 times]
Created: Sun Oct 5 17:15:45 2014
Total 2 displayed, Up 0, Down 2

Egress LSP: 0 sessions
Total 0 displayed, Up 0, Down 0

Transit LSP: 0 sessions
Total 0 displayed, Up 0, Down 0

 

Attachments

Highlighted
Routing

Re: VPLS MPLS-TE problem

‎10-05-2014 11:00 AM

Hi,

 

I see only lo0.0 interface is configured under "protocol mpls". Can you please add all interfaces under "protocol mpls"?

May be you need to add this on all the routers as well.

 

   mpls {

<..>

       interface lo0.0;

   }

 

Regards

Surya

Highlighted
Routing

Re: VPLS MPLS-TE problem

‎10-05-2014 11:07 AM

So that was my mistake. 

 

Now everything is as it should be:

 

lab@S40# run show rsvp session
Ingress RSVP: 2 sessions
To From State Rt Style Labelin Labelout LSPname
10.10.10.41 10.10.10.40 Up 0 1 FF - 302800 LSP-VIA-S42
10.10.10.41 10.10.10.40 Up 0 1 FF - 300208 LSP-VIA-S43
Total 2 displayed, Up 2, Down 0

Egress RSVP: 2 sessions
To From State Rt Style Labelin Labelout LSPname
10.10.10.40 10.10.10.41 Up 0 1 FF 3 - LSP-VIA-S42
10.10.10.40 10.10.10.41 Up 0 1 FF 3 - LSP-VIA-S43
Total 2 displayed, Up 2, Down 0

Transit RSVP: 0 sessions
Total 0 displayed, Up 0, Down 0

 

 

lab@S40# run show route forwarding-table

Routing table: default.mpls
MPLS:
Destination Type RtRef Next hop Type Index NhRef Netif
default perm 0 dscd 50 1
0 user 0 recv 49 4
1 user 0 recv 49 4
2 user 0 recv 49 4
13 user 0 recv 49 4
262147 user 0 Pop 615 2 lsi.1050881
262156 user 0 Pop 612 2 lsi.1050880
300112 user 0 10.100.10.10 Pop 604 2 ge-1/1/3.0
300112(S=0) user 0 10.100.10.10 Pop 605 2 ge-1/1/3.0
300144 user 0 10.100.10.2 Pop 611 2 ge-1/1/2.0
300144(S=0) user 0 10.100.10.2 Pop 610 2 ge-1/1/2.0
300160 user 0 10.100.10.6 Pop 606 2 ge-1/1/1.0
300160(S=0) user 0 10.100.10.6 Pop 607 2 ge-1/1/1.0
lsi.1050880 (VPLS) user 0 indr 1048574 5
10.100.10.10 Push 262154, Push 300208(top) 590 2 ge-1/1/3.0
lsi.1050881 (VPLS) user 0 indr 1048575 5
10.100.10.2 Push 262145, Push 302800(top) 587 2 ge-1/1/2.0

 

 

Thank you very much for help! 🙂

Highlighted
Routing

Re: VPLS MPLS-TE problem

‎10-05-2014 11:16 AM

Wow.. So glad to hear it out. Smiley Happy

 

Please don't forget to accept the post as a "Solution".

 

Regards

Surya

Feedback