Routing

Hi all

 

I have one question for backup path via RSVP over MPLS

As below diagram, I hope KOREA01 to KOREA03 directly is set as primary path.

And KOREA01 to KOREA03 via KOREA02 is set as backup path.

 

After I set it, second path is still down and shown "wrong delivery".

Should I modify anything as follow what I did ? Like set loose, not strict  or wrong next-hop IP ?

 

BTW, if second path is working , do it will be shown when I show route 192.168. .145.2 ? 

 

Appreciate for your reply

Cloud

=====================================

label-switched-path KOREA01-->KOREA03 {
to 192.168.145.2;
primary KOREA01-->KOREA03;
secondary KOREA01->KOREA02->KOREA03;
}
path KOREA01-->KOREA02 {
10.5.100.61 strict;
}
path KOREA01->KOREA02->KOREA03 {
10.3.100.41 strict;
}

 

> show mpls lsp
Ingress LSP: 1 sessions
To From State Rt P ActivePath LSPname
192.168.145.2 172.16.131.2 Up 0 *KOREA01-->KOREA03 KOREA01-->KOREA03

 

>show mpls lsp extensive103.198.145.2

From: 172.16.131.2, State: Up, ActiveRoute: 0, LSPname:KOREA01-->KOREA03
ActivePath:KOREA01-->KOREA03 (primary)
FastReroute desired
LSPtype: Static Configured, Penultimate hop popping
LoadBalance: Random
Encoding type: Packet, Switching type: Packet, GPID: IPv4
*PrimaryKOREA01-->KOREA03 State: Up
Priorities: 7 0
OptimizeTimer: 3600
SmartOptimizeTimer: 180
Received RRO (ProtectionFlag 1=Available 2=InUse 4=B/W 8=Node 10=SoftPreempt 20=Node-ID):

10.5.100.61
17 May 11 08:49:39.649 Selected as active path
16 May 11 08:49:39.648 Record Route: 10.5.100.61
15 May 11 08:49:39.648 Up
14 May 11 08:49:39.648 Self-ping started
13 May 11 08:49:39.648 Self-ping enqueued
12 May 11 08:49:39.648 Stats related identifier changed
11 May 10 16:48:24.992 Deselected as active
10 May 10 16:48:24.991 192.168.145.62: Session preempted
SecondaryKOREA03 KOREA01-->KOREA03 State: Dn
Priorities: 7 0
OptimizeTimer: 3600
SmartOptimizeTimer: 180
5 May 11 08:49:40.901 Clear Call
4 May 10 16:48:24.992 Originate Call
3 May 10 16:45:21.030 Clear Call
2 May 10 16:45:04.727

10.5.100.61: Explicit Route: wrong delivery[9 times]
1 May 10 16:32:06.509 Originate Call
Created: Thu May 10 16:31:36 2018

#MPLS

can you share your configs?

Hi Kingsman

 

Nice to meet you again and very thanks for your help many times.

 

As attachment is my configuration.

 

I think I have some problem about an explicit mpls path what maybe I haven't enough know-how.

1. Why my second path is not working ? Does I set wrong way.

2. When I enable RSVP on three routers, how I control routes of RSVP using direct route as first chicoe 

 

Thanks again

Cloud  

Please delete no-cspf from the KOREA1 and check.

 

delete protocols mpls no-cspf

 

You have configured no-cspf which is causing KOREA1 to not use TED database and  signal LSP hop by hop using IGP best path.

 

 

Hi 

 

I think it is still failed and got a error message "No computed ERO."

Also, I found nothing about this via google.

 

Cloud

 

=======================================================

192.168.145.2

  From: 182.54.131.2, State: Up, ActiveRoute: 0, LSPname: KOREA01—>KOREA03

  ActivePath: KOREA01—>KOREA03 (primary)

  FastReroute desired

  LSPtype: Static Configured, Penultimate hop popping

  LoadBalance: Random

  Encoding type: Packet, Switching type: Packet, GPID: IPv4

*Primary   KOREA01—>KOREA03    State: Up

    Priorities: 7 0

    OptimizeTimer: 3600

    SmartOptimizeTimer: 180

    Reoptimization in 2291 second(s).

    Computed ERO (S [L] denotes strict [loose] hops): (CSPF metric: 5)

10.5.100.61 S

    Received RRO (ProtectionFlag 1=Available 2=InUse 4=B/W 8=Node 10=SoftPreempt 20=Node-ID):

          192.168.145.61

   45 May 11 16:09:58.230 Record Route:  192.168.145.61

   44 May 11 16:09:58.230 Up

   43 May 11 16:09:58.230 Self-ping started

   42 May 11 16:09:58.230 Self-ping enqueued

   41 May 11 16:09:58.125 Originate Call

   40 May 11 16:09:58.125 CSPF: computation result accepted  10.5.100.61

   39 May 11 16:09:58.125 Self-ping ended due to LSP tear-down

   38 May 11 16:09:58.124 Clear Call    

   37 May 11 16:06:57.708 Record Route:  192.168.145.61

   36 May 11 16:06:57.708 Up

   35 May 11 16:06:57.708 Self-ping started

   34 May 11 16:06:57.708 Self-ping enqueued

   33 May 11 16:06:57.501 Originate Call

   32 May 11 16:06:57.501 CSPF: computation result accepted  192.168.145.61

   31 May 11 16:06:57.501 Self-ping ended due to LSP tear-down

   30 May 11 16:06:57.500 Clear Call

   29 May 11 13:13:16.449 Record Route:  192.168.145.61

   28 May 11 13:13:16.449 Up

   27 May 11 13:13:16.449 Self-ping started

   26 May 11 13:13:16.449 Self-ping enqueued

   25 May 11 13:13:16.347 Originate Call

   24 May 11 13:13:16.346 Self-ping ended due to LSP tear-down[2 times]

   23 May 11 13:13:16.346 Clear Call

   22 May 11 13:00:40.751 Record Route:  192.168.145.61

   21 May 11 13:00:40.751 Up

   20 May 11 13:00:40.751 Self-ping started

   19 May 11 13:00:40.751 Self-ping enqueued

   18 May 11 13:00:40.547 Originate make-before-break call

   17 May 11 08:49:39.649 Selected as active path

   16 May 11 08:49:39.648 Record Route:  192.168.145.61

   15 May 11 08:49:39.648 Up

   14 May 11 08:49:39.648 Self-ping started

   13 May 11 08:49:39.648 Self-ping enqueued

   12 May 11 08:49:39.648 Stats related identifier changed

   11 May 10 16:48:24.992 Deselected as active

   10 May 10 16:48:24.991 192.168.145.62: Session preempted

    9 May 10 16:48:24.991 Self-ping ended due to LSP tear-down

    8 May 10 16:48:24.991 192.168.145.62: Down

    7 May 10 16:44:57.506 Selected as active path

    6 May 10 16:44:57.505 Record Route:  192.168.145.61

    5 May 10 16:44:57.505 Up

    4 May 10 16:44:57.505 Self-ping started

    3 May 10 16:44:57.505 Self-ping enqueued

    2 May 10 16:44:15.396 192.168.145.61: MPLS label allocation failure[8 times]

    1 May 10 16:31:36.587 Originate Call

  Secondary KOREA01->KOREA02->KOREA03 State: Dn

    Priorities: 7 0

    OptimizeTimer: 3600

    SmartOptimizeTimer: 180

    Reoptimization in 1420 second(s).

        No computed ERO.

  Created: Thu May 10 16:31:36 2018

Total 5 displayed, Up 3, Down 2

Remove the below line from the config and check. 

 

set protocols mpls path KOREA01->KOREA02->KOREA03 10.3.100.41 strict

Hi Kingsman

 

Sorry to relpy so late.

 

After removed "stric and kept "set protocols mpls path KOREA01->KOREA02->KOREA03 10.3.100.41"

I also got the samw result . Do I miss what you mean ?

 

===============================================

Secondary KOREA01->KOREA02->KOREA03 State: Dn
Priorities: 7 0
OptimizeTimer: 3600
SmartOptimizeTimer: 180
Reoptimization in 0 second(s).
No computed ERO.
Created: Thu May 10 16:31:36 2018
Total 3 displayed, Up 3, Down 0 

Can you share your changed config and share show ted database extensive output form the box?

 

Also, kindly share the complete output of "show mpls lsp name <lsp name> extensive"

Hi Kingsman

 

I modified my second path and set it as standy. Then it is working.

Please refer it as below informaiton.

 

Configuration :

set protocols mpls path KOREA01->KOREA02->KOREA03 10.3.100.41 strict
set protocols mpls path KOREA01->KOREA02->KOREA03 10.5.100.33 strict

 

set protocols mpls label-switched-path KMH01-->SIN01 primary KOREA01->KOREA03
set protocols mpls label-switched-path KMH01-->SIN01 secondary KOREA01->KOREA02->KOREA03 standby

 

Routing table:

> show route 103.198.145.2

inet.0: 692581 destinations, 1382338 routes (692581 active, 4 holddown, 859 hidden)
+ = Active Route, - = Last Active, * = Both

103.198.145.2/32 *[RSVP/7/1] 00:07:30, metric 5
> to 10.5.100.61 via xe-1/3/3.0, label-switched-path KOREA01-->KOREA03
to 10.3.100.41 via xe-0/3/3.0, label-switched-path KOREA01-->KOREA03
[LDP/9] 1d 07:04:55, metric 5
> to 10.5.100.61 via xe-1/3/3.0
to 10.3.100.41 via xe-0/3/3.0, Push 299856
[OSPF/10] 1d 07:04:55, metric 5
> to 10.5.100.61 via xe-1/3/3.0
to 10.3.100.41 via xe-0/3/3.0

 

> show mpls lsp extensive  

(omitted)

Standby KOREA01->KOREA02->KOREA03 State: Up
Priorities: 7 0
OptimizeTimer: 3600
SmartOptimizeTimer: 180
Reoptimization in 2734 second(s).
Computed ERO (S [L] denotes strict [loose] hops): (CSPF metric: 10)

 

Best regards,

Cloud

Yeah, that’s expected.

Standby cause the router to create additional state by bringing up the secondary LSP in advance. It improved the failover in case primary goes down.

IF you don’t use standby, the secondary LSP will be signaled once the primary goes down.