Junos OS

Expand all | Collapse all

Question about MPLS Path LSP

Jump to Best Answer

thomas.block10-20-2017 01:20

  • 1.  Question about MPLS Path LSP

    Posted 10-19-2017 22:03

    Hi everybody,

     

    I have a question about some of my MPLS LSPs in my backbone.

    In the log file I can see every 15 minutes this message from one MX.

     

    Oct 20 06:36:38 rpd[1484]: RPD_MPLS_LSP_DOWN: MPLS LSP 10.55.0.63:dt-rsvp-R43 down on dynamic()
    Oct 20 06:36:38 rpd[1484]: RPD_MPLS_PATH_DOWN: MPLS path down on LSP 10.55.0.63:dt-rsvp-R43
    Oct 20 06:36:39  rpd[1484]: RPD_MPLS_PATH_UP: MPLS path up on LSP 10.55.0.63:dt-rsvp-R43 path bandwidth 0 bps
    Oct 20 06:36:39  rpd[1484]: RPD_MPLS_LSP_UP: MPLS LSP 10.55.0.63:dt-rsvp-R43 up on dynamic() Route  lsp bandwidth 0 bps

     

    The rsvp neighbours are on and the MPLS LSP are up

     

     show rsvp neighbor

    10.55.250.81          0  1/0  22w0d 2:39:28        9 1471599/1471599 71835917
    10.55.250.162         0  1/0  22w0d 2:39:08        9 1471649/1471649 73034481

     

    show mpls lsp

    10.55.0.63      10.55.0.43      Up     0 *                      10.55.0.63:dt-rsvp-R43

     

    I can see no packest on the LSP.

    Is this an error or is it  normal when a LSP not needed.

    I hope you can understand and I am sorry about my bad englisch.

     

    THX

    Thomas

     

     

     

     

     



  • 2.  RE: Question about MPLS Path LSP

     
    Posted 10-19-2017 22:27

    Hi Thomas,

    Based on above logs we do find the LSP path down and LSP itself is going down and coming up,

     

    Oct 20 06:36:38 rpd[1484]: RPD_MPLS_LSP_DOWN: MPLS LSP 10.55.0.63:dt-rsvp-R43 down on dynamic() <<<< LSP Going down

    Oct 20 06:36:38 rpd[1484]: RPD_MPLS_PATH_DOWN: MPLS path down on LSP 10.55.0.63:dt-rsvp-R43 <<< path going down

    Oct 20 06:36:39  rpd[1484]: RPD_MPLS_PATH_UP: MPLS path up on LSP 10.55.0.63:dt-rsvp-R43 path bandwidth 0 bps <<<< Path coming up

    Oct 20 06:36:39  rpd[1484]: RPD_MPLS_LSP_UP: MPLS LSP 10.55.0.63:dt-rsvp-R43 up on dynamic() Route  lsp bandwidth 0 bps <<< LSP coming up

     

    Can we get, ‘show mpls lsp name 10.55.0.63:dt-rsvp-R43 extensive’ this will give us more idea.

     

    To add, check the inet.3 table for any route pointing to the LSP. In the absence of any prefix pointing to LSP we don’t expect any traffic on it.

     



  • 3.  RE: Question about MPLS Path LSP

    Posted 10-19-2017 23:14

    THX for the quickly help.l

    Here the output from the cli

     

    show mpls lsp name 10.55.0.63:dt-rsvp-R43 extensive
    Ingress LSP: 40 sessions

    10.55.0.63
    From: 10.55.0.43, State: Up, ActiveRoute: 0, LSPname: 10.55.0.63:dt-rsvp-R43
    ActivePath: (primary)
    FastReroute desired
    LSPtype: Dynamic Configured, Penultimate hop popping
    LoadBalance: Random
    Encoding type: Packet, Switching type: Packet, GPID: IPv4
    *Primary State: Up
    Priorities: 7 0
    OptimizeTimer: 65535
    SmartOptimizeTimer: 180
    Reoptimization in 65500 second(s).
    Computed ERO (S [L] denotes strict [loose] hops): (CSPF metric: 40)
    10.55.250.162 S 10.55.250.169 S 10.55.250.125 S 10.55.250.230 S
    Received RRO (ProtectionFlag 1=Available 2=InUse 4=B/W 8=Node 10=SoftPreempt 20=Node-ID):
    10.55.250.162(flag=9) 10.55.250.169(flag=1) 10.55.250.125(flag=1) 10.55.250.230
    9 Oct 20 08:06:43.378 Record Route: 10.55.250.162(flag=9) 10.55.250.169(flag=1) 10.55.250.125(flag=1) 10.55.250.230
    8 Oct 20 08:06:42.556 Record Route: 10.55.250.162(flag=9) 10.55.250.169(flag=1) 10.55.250.125 10.55.250.230
    7 Oct 20 08:06:42.353 Record Route: 10.55.250.162(flag=9) 10.55.250.169 10.55.250.125 10.55.250.230
    6 Oct 20 08:06:42.147 Fast-reroute Detour Up
    5 Oct 20 08:06:39.475 Selected as active path
    4 Oct 20 08:06:39.473 Record Route: 10.55.250.162 10.55.250.169 10.55.250.125 10.55.250.230
    3 Oct 20 08:06:39.473 Up
    2 Oct 20 08:06:38.660 Originate Call
    1 Oct 20 08:06:38.660 CSPF: computation result accepted 10.55.250.162 10.55.250.169 10.55.250.125 10.55.250.230
    Created: Fri Oct 20 08:06:38 2017
    Total 1 displayed, Up 1, Down 0

     

    Every 15 minutes  goes the path down and up, my first idea was a timer to rebuildt the path automaticly



  • 4.  RE: Question about MPLS Path LSP

    Posted 10-19-2017 23:28

    Hi,

     

    You may be hitting below PR.

     

    https://prsearch.juniper.net/InfoCenter/index?page=prcontent&id=PR1272223

     

    Althpough PR is related to p2mp RSVP LSP but error seen in the PR is matching what you see on your box.

     

    Can you share your protocol configuration and try the workarund provided in the above PR?

     

    HTH



  • 5.  RE: Question about MPLS Path LSP

    Posted 10-20-2017 00:28

    Ok,

    I have rsvp agregate disabled, no changes in the log.

     

    To share my configuraten ( protocol) I must copy the text in the box called article feedback and submit?

    Is this right?

    who gives me then an answer?

     



  • 6.  RE: Question about MPLS Path LSP

    Posted 10-20-2017 00:48

    Well, You can just  directly paste your protocol cofniguration here



  • 7.  RE: Question about MPLS Path LSP

    Posted 10-20-2017 01:00

    Ok.

    I think the problem is a other router in my Backbone.

     

    rsvp {
        interface int-mplscore {
            aggregate;
        }
        interface lo0.0;
    }
    mpls {
        path-mtu {
            rsvp mtu-signaling;
        }
        optimize-timer 65535;
        label-switched-path lsp-template {
            template;
            standby;
            adaptive;
            fast-reroute;
        }
        interface int-mplscore;
    }
    bgp {
        group INTERNAL {
            type internal;
            local-address 10.55.0.43;
            family inet-vpn {
                unicast;
            }
            family l2vpn {
                signaling;
            }
            family route-target;
            bfd-liveness-detection {
                minimum-interval 300;
            }
            neighbor 10.55.0.11;
            neighbor 10.55.0.16;
        }
    }
    isis {
        level 1 disable;
        interface fxp0.0 {
            disable;
        }
        interface int-mplscore {
            point-to-point;
            bfd-liveness-detection {
                minimum-interval 300;
            }
            level 1 disable;
        }
        interface lo0.0 {
            level 1 disable;
            level 2 passive;
        }
    }
    lldp {
        interface all;
    }

     



  • 8.  RE: Question about MPLS Path LSP

    Posted 10-20-2017 01:11

    Yes, it could be.

     

    You can check the other device in the network and if it still doesn't solve, we can try enabling traceoptions for rsvp and mpls and check whats happening.

     

     



  • 9.  RE: Question about MPLS Path LSP

    Posted 10-20-2017 01:20

    OK, that is right way.

     



  • 10.  RE: Question about MPLS Path LSP

    Posted 10-20-2017 02:26

    I have MPLS tracelogs from two neigbohboured MX Router.

    There is only one 10  GIG LINK between these routers and the LSP Flip down and up.

    Can I post the tracelog here in clear test as a  file?



  • 11.  RE: Question about MPLS Path LSP

    Posted 10-20-2017 03:12

    Hi,

     

    Did you check other router's in your network as you suspected?

    You can also attach traceoption file here.



  • 12.  RE: Question about MPLS Path LSP

    Posted 10-20-2017 03:23

    I do post the trace log´s next week.

    The LSP from  router A goes directly t Router B

     

    10.55.0.63
      From: 10.55.0.42, State: Up, ActiveRoute: 0, LSPname: 10.55.0.63:dt-rsvp-R42
      ActivePath:  (primary)
      FastReroute desired
      LSPtype: Dynamic Configured, Penultimate hop popping
      LoadBalance: Random
      Encoding type: Packet, Switching type: Packet, GPID: IPv4
     *Primary                    State: Up
        Priorities: 7 0
        OptimizeTimer: 65535
        SmartOptimizeTimer: 180
        Reoptimization in 63620 second(s).
        Computed ERO (S [L] denotes strict [loose] hops): (CSPF metric: 10)
     10.55.250.234 S
        Received RRO (ProtectionFlag 1=Available 2=InUse 4=B/W 8=Node 10=SoftPreempt 20=Node-ID):
              10.55.250.234
        6 Oct 20 11:52:34.164 Fast-reroute Detour Up
        5 Oct 20 11:52:30.244 Selected as active path
        4 Oct 20 11:52:30.243 Record Route:  10.55.250.234
        3 Oct 20 11:52:30.240 Up
        2 Oct 20 11:52:30.060 Originate Call
        1 Oct 20 11:52:30.060 CSPF: computation result accepted  10.55.250.234
      Created: Fri Oct 20 11:52:30 2017

     

    The LSP from router B goes an other way over 4 routers

     

    10.55.0.42
      From: 10.55.0.63, State: Up, ActiveRoute: 0, LSPname: 10.55.0.42:dt-rsvp-R63
      ActivePath:  (primary)
      FastReroute desired
      LSPtype: Dynamic Configured, Penultimate hop popping
      LoadBalance: Random
      Encoding type: Packet, Switching type: Packet, GPID: IPv4
     *Primary                    State: Up
        Priorities: 7 0
        OptimizeTimer: 65535
        SmartOptimizeTimer: 180
        Reoptimization in 26830 second(s).
        Computed ERO (S [L] denotes strict [loose] hops): (CSPF metric: 10)
     10.55.250.233 S
        Received RRO (ProtectionFlag 1=Available 2=InUse 4=B/W 8=Node 10=SoftPreempt 20=Node-ID):
              10.55.250.233
       74 Oct 20 01:15:50.007 CSPF: computation result ignored, new path no benefit
       73 Oct 19 09:04:38.751 Fast-reroute Detour Up
       72 Oct 19 09:04:35.542 Make-before-break: Switched to new instance
       71 Oct 19 09:04:35.542 Fast-reroute Detour Down
       70 Oct 19 09:04:34.541 Record Route:  10.55.250.233
       69 Oct 19 09:04:34.541 Up
       68 Oct 19 09:04:34.420 Originate make-before-break call
       67 Oct 19 09:04:34.420 CSPF: computation result accepted  10.55.250.233
       66 Oct 19 09:04:34.419 CSPF: Reroute due to re-optimization
       65 Oct 19 09:01:50.065 Record Route:  10.55.250.229(flag=1) 10.55.250.37(flag=9) 10.55.250.114(flag=9) 10.55.250.166(flag=1) 10.55.250.153
       64 Oct 19 09:01:47.249 Fast-reroute Detour Up
       63 Oct 19 09:01:35.633 Record Route:  10.55.250.229(flag=1) 10.55.250.37 10.55.250.114(flag=9) 10.55.250.166(flag=1) 10.55.250.153
       62 Oct 19 09:01:35.034 Record Route:  10.55.250.229(flag=1) 10.55.250.37 10.55.250.114(flag=9) 10.55.250.166 10.55.250.153
       61 Oct 19 09:01:18.489 Record Route:  10.55.250.229(flag=1) 10.55.250.37 10.55.250.114 10.55.250.166 10.55.250.153
       60 Oct 19 09:01:17.549 Make-before-break: Switched to new instance
       59 Oct 19 09:01:16.546 Record Route:  10.55.250.229 10.55.250.37 10.55.250.114 10.55.250.166 10.55.250.153
       58 Oct 19 09:01:16.546 Up
       57 Oct 19 09:01:14.413 Pending path switchover, skip CSPF run
       56 Oct 19 09:01:14.413 CSPF: link down/deleted: 10.55.250.234(10.55.0.63:336)(R63_SAP_RWE.00/10.55.0.63)->10.55.250.233(10.55.0.42:427)(R42-bfz.00/10.55.0.42)
       55 Oct 19 09:01:14.016 Originate make-before-break call
       54 Oct 19 09:01:14.016 CSPF: computation result accepted  10.55.250.229 10.55.250.37 10.55.250.114 10.55.250.166 10.55.250.153
       53 Oct 19 09:01:13.833 10.55.250.234: Tunnel local repaired
       52 Oct 19 09:01:13.830 Record Route:  10.55.250.229 10.55.250.37 10.55.250.114 10.55.250.166 10.55.250.153
       51 Oct 19 09:01:13.830 10.55.250.234: Tunnel local repaired
       50 Oct 19 09:01:13.830 10.55.250.234: Down
       49 Oct 19 00:49:05.863 CSPF: computation result ignored, new path no benefit
       48 Oct 18 06:36:54.865 Fast-reroute Detour Up

     

     

    I think to need the weekend to understand why and to think about the problem.

     



  • 13.  RE: Question about MPLS Path LSP

    Posted 10-20-2017 03:57

    Ahh, I didn't notice.

     

    Are these dynamic tunnels? Can you share your full configuration if possible?

     

    Usually If no traffic passed through the dynamic tunnel after 15 minutes then the dynamic tunnel get deleted.

     

     

     

     



  • 14.  RE: Question about MPLS Path LSP

    Posted 10-20-2017 04:07

    We have dynamic LSP

     

    Yes , I can share my config with you.

    Which part do you need?

     

    I do not understand why ..

    1. The LSP from Router A goes directly Router B   

    2.The LSP from rourer B goes to router A over 4 other hops......?

     



  • 15.  RE: Question about MPLS Path LSP

    Posted 10-20-2017 04:16

    Hi,

     

    I need all the config related to RSVP/MPLS and dynamic tunnels, routing-options, and interface config between A & B

     

    Also, can you draw a rough topology here?

     

    we will need to look at the config of B as well.

     

    One more thing, As i said in my last post. If there's no traffic for 15 mins, the LSP will go down. Kindly check that as well



  • 16.  RE: Question about MPLS Path LSP

    Posted 10-20-2017 04:21

    Ok, next week i will post all you need.

     

    I know yet why the other router have another way for th lsp.

    Yesterday we changed the optic betwenn the two router and the link was down.

    Thats the reason, easy and simple..  🙂



  • 17.  RE: Question about MPLS Path LSP

    Posted 10-25-2017 04:33

    Hi, i want to gives a feedback of my problem with the LSP.

    We have deleted all Services on the router which were did not need now

    And a look on the systemshow us tha all works fine..

    All the dynamic rsvp and mpls lsp which not needed are down after 15 minutes.

     

    THX for your help

     

     

     



  • 18.  RE: Question about MPLS Path LSP

    Posted 10-25-2017 04:54

    yep. That's the expected behaviour of dynamic tunnels.

     

     



  • 19.  RE: Question about MPLS Path LSP

    Posted 10-25-2017 21:34

    THX for your help.

    i have lerned so much about RSVP and MPLS LSP.

    Do you know what this means, it is in my log since two days.( MX 104 14.2R7.5)

     

    ct 26 06:32:31 R73_Gymnasium_Ueberruhr afeb0 PQ3_IIC(WR): no target ack on byte 0 (wait spins 3)
    Oct 26 06:32:31 R73_Gymnasium_Ueberruhr afeb0 PQ3_IIC(WR): I/O error (i2c_stat=0xa3, i2c_ctl[1]=0xb0, bus_addr=0x51)
    Oct 26 06:32:34 R73_Gymnasium_Ueberruhr afeb0 PQ3_IIC(WR): no target ack on byte 0 (wait spins 3)
    Oct 26 06:32:34 R73_Gymnasium_Ueberruhr afeb0 PQ3_IIC(WR): I/O error (i2c_stat=0xa3, i2c_ctl[1]=0xb0, bus_addr=0x51)
    Oct 26 06:32:37 R73_Gymnasium_Ueberruhr afeb0 PQ3_IIC(WR): no target ack on byte 0 (wait spins 3)
    Oct 26 06:32:37 R73_Gymnasium_Ueberruhr afeb0 PQ3_IIC(WR): I/O error (i2c_stat=0xa3, i2c_ctl[1]=0xb0, bus_addr=0x51)
    Oct 26 06:32:40 R73_Gymnasium_Ueberruhr afeb0 PQ3_IIC(WR): no target ack on byte 0 (wait spins 3)
    Oct 26 06:32:40 R73_Gymnasium_Ueberruhr afeb0 PQ3_IIC(WR): I/O error (i2c_stat=0xa3, i2c_ctl[1]=0xb0, bus_addr=0x51)

     

    I think thi is a problen with my forwarding engine...

     

     

     



  • 20.  RE: Question about MPLS Path LSP

    Posted 10-25-2017 23:57

    Do you have any unsupported SFP installed in the box?

    I would suggest you open a ticket with the JTAC to check this further.



  • 21.  RE: Question about MPLS Path LSP

    Posted 10-26-2017 00:04

    Hi Thomas,

    Check the below KB for more information regarding the error logs

    https://kb.juniper.net/InfoCenter/index?page=content&id=KB31238&act=login

     

    Hope this helps



  • 22.  RE: Question about MPLS Path LSP

    Posted 10-26-2017 05:28
    you may share couple of commands output for having the reason clear.. show chassis hardware show chassis alarms start shell pfe networks feb0 show nvram show syslog messages ************************ You may also refer the following link however it is of older JUNOS.. https://www.juniper.net/documentation/en_US/junos9.6/information-products/topic-collections/release-notes/9.6/topic-32552.html Mark this as accepted solution if it resolved your problem. Kudos will be appreciated if you think i have earned them.


  • 23.  RE: Question about MPLS Path LSP

    Posted 11-06-2017 03:49

    Hi,

     

    last week we found an unsupported GBIC in the router.

    Tha was the problem of my log file.....

     

     

    THX



  • 24.  RE: Question about MPLS Path LSP
    Best Answer

    Posted 11-06-2017 06:43

    Yeah, that was one of the reasons for those log error messages.

     

    I would suggest you to close this thread and start a new thread for any new query. This will help other community members in case they see the similar issue.

     

    Regards

     

     



  • 25.  RE: Question about MPLS Path LSP

    Posted 11-08-2017 22:08

    Hi,

     

    who can I close this threat.

    I can not find where iI can do that



  • 26.  RE: Question about MPLS Path LSP

     
    Posted 10-20-2017 01:31

    Hi Folks,

    The RSVP LSP has only primary path and the path has the following ERO,

     

    10.55.250.162 S 10.55.250.169 S 10.55.250.125 S 10.55.250.230 S

     

    The sample output from your box shows that the FastReroute desired object was included in the Path messages for the LSP, allowing your box to select the active path for the LSP and establish a detour path to avoid the other routers.

     

    Can you login to these boxes along the path and look for any link flap?

     

    10.55.250.162 S

    10.55.250.169 S

    10.55.250.125 S

    10.55.250.230 S

     

    The output for the show mpls lsp extensive command does not show the actual path of the detour. To see the actual links used by the detour paths, you must use the show rsvp session ingress detail command.