Junos OS

Expand all | Collapse all

Pro-active Loss and Delay Measurements for Bidirectional MPLS LSPs

Jump to Best Answer
  • 1.  Pro-active Loss and Delay Measurements for Bidirectional MPLS LSPs

    Posted 10-14-2020 08:05

    Hello,

     

    I need a bit of help to clarify the troubleshooting/configuration issues related to the Pro-Active Loss/Delay measurements.

    The reference I was using is: 

    https://www.juniper.net/documentation/en_US/junos/topics/topic-map/mpls-statistics.html#jd0e248

     

    The configuration example looks very straight forward, however, I do not see any results after issuing "show performance-monitoring mpls lsp"

     

    The main difference between the example and my test environment is: 

    ______________________________________

    user@R1# show chassis
    network-services enhanced-ip;
    ______________________________________
     
    In my case I have enhanced-ethernet.
     
    I am looking for your support to understand:
    - if this is a correct approach/directions if I am interesting to have Loss/Delay information about my LSPs (the network itself will have more then 1000 LSPs, so the performance is really a challenge)
    - Was anybody able to reproduce this in the live environment?
    - Is the enhanced-ip - is critical in this case?
    - Any "how to debug this" advises?
     
    Thank you and all the best.
    Andrei 


  • 2.  Re: Pro-active Loss and Delay Measurements for Bidirectional MPLS LSPs

    Posted 10-15-2020 03:18

    Hello,

    "enhanced-ip" is pretty much a must for any advanced JUNOS MPLS feature, so the answer is You need "enhanced-ip" for this feature.

    I reckon You might even not be able to get some services running over 1000 RSVP LSP with "enhanced-ethernet" mode

    https://www.juniper.net/documentation/en_US/junos/topics/topic-map/chassis-guide-tm-config-ntwrk-srvics-mode.html#id-feature-restrictions-on-mx-series-routers-running-in-ethernet-network-services-mode-or

    HTH

    Thx

    Alex 



  • 3.  Re: Pro-active Loss and Delay Measurements for Bidirectional MPLS LSPs

    Posted 10-15-2020 03:35

    Thank you so much!
    I will try the enhanced-ip.

     

    Can you pls point me to the document that will describe (in a bit more detailed way) the difference between enhanced Ethernet and IP mode?

     

    It looks to be very critical to understand.

     

    BR



  • 4.  Re: Pro-active Loss and Delay Measurements for Bidirectional MPLS LSPs

    Posted 10-15-2020 03:37


  • 5.  Re: Pro-active Loss and Delay Measurements for Bidirectional MPLS LSPs

    Posted 10-15-2020 04:11

    Thank you one more time.

     

    The enhanced-ip looks not the root cause (or I am missing something else).

     

    My LAB setup is

    MX104

    set chassis fpc 0 pic 0 tunnel-services bandwidth 1g

    set chassis network-services enhanced-ip

    set protocols mpls statistics traffic-class-statistics

    set protocols mpls label-switched-path R9 to IP
    set protocols mpls label-switched-path R9 oam mpls-tp-mode
    set protocols mpls label-switched-path R9 oam performance-monitoring querier loss traffic-class none query-interval 1000
    set protocols mpls label-switched-path R9 oam performance-monitoring querier delay traffic-class tc-0 query-interval 1000
    set protocols mpls label-switched-path R9 oam performance-monitoring querier loss-delay traffic-class tc-0 query-interval 1000
    set protocols mpls label-switched-path R9 oam performance-monitoring responder loss min-query-interval 1000
    set protocols mpls label-switched-path R9 oam performance-monitoring responder delay min-query-interval 1000
    set protocols mpls label-switched-path R9 ultimate-hop-popping
    set protocols mpls label-switched-path R9 associate-lsp R9-R6

     

    However the result is the same 😞

     

    R6 > monitor mpls delay rsvp R9
    Performance monitoring is not supported on this LSP

     

    R6> monitor mpls loss rsvp R9
    Performance monitoring is not supported on this LSP

     

    R6> show performance-monitoring mpls lsp

     

    Anyhow - Thanks for your support! I will dig further 🙂

     

    BR

    Andrei 



  • 6.  Re: Pro-active Loss and Delay Measurements for Bidirectional MPLS LSPs

    Posted 10-15-2020 05:12

    Hello,

    1/ You need to reboot the node after changing "chassis network-services".

    2/ I suggest You remove extra knobs such as "ultimate-hop-popping" and "associate-lsp", then try again.

    HTH

    Thx

    Alex



  • 7.  Re: Pro-active Loss and Delay Measurements for Bidirectional MPLS LSPs

    Posted 10-15-2020 07:13

    Hi Alex,

    Thank you for your support on this.

    The "simple" version of config is also not working for me.

    I need to admit my LAB setup is a bit of "zoo"

     

    A-End MX104 JunOS 16.1R6-S6

    Z-End MX240 (DPC line cards) 15.1F7-S2.1 (no enhanced mode possible)

     

    As this feature is "forcing" me to use bidirectional/associate-lsp stanza, could it be that "Z-End limitation" is impacting the functionality? 

     

    Is there any way to "trace" this feature to see what is the issue?

     

    BR

    Andrei

     

     



  • 8.  Re: Pro-active Loss and Delay Measurements for Bidirectional MPLS LSPs
    Best Answer

    Posted 10-15-2020 09:52

    Hello,

     

    I labbed up Your scenario using MX2020 in enhanced-ip mode and it works just fine:

     

    set protocols rsvp interface all
    set protocols rsvp interface fxp0.0 disable
    set protocols mpls statistics traffic-class-statistics
    set protocols mpls icmp-tunneling
    set protocols mpls label-switched-path R3-R2 to 198.51.100.2
    set protocols mpls label-switched-path R3-R2 oam mpls-tp-mode
    set protocols mpls label-switched-path R3-R2 oam performance-monitoring querier loss traffic-class none query-interval 1000
    set protocols mpls label-switched-path R3-R2 oam performance-monitoring querier delay traffic-class tc-0 query-interval 1000
    set protocols mpls label-switched-path R3-R2 oam performance-monitoring querier loss-delay traffic-class tc-0 query-interval 1000
    set protocols mpls label-switched-path R3-R2 oam performance-monitoring responder loss min-query-interval 1000
    set protocols mpls label-switched-path R3-R2 oam performance-monitoring responder delay min-query-interval 1000
    set protocols mpls label-switched-path R3-R2 ultimate-hop-popping
    set protocols mpls label-switched-path R3-R2 associate-lsp R2-R3
    set protocols mpls interface all
    set protocols mpls interface fxp0.0 disable

     

    Verification:

     

    regress@R3> show performance-monitoring mpls lsp                      
    Oct 15 09:38:45
    Session Total: 3 Up: 3 Down: 0
      LSP name:R3-R2, PM State:Up
        Loss measurement Data:
          Duration: 00:01:59
          Traffic-class: None
          Queries sent: 120
          Responses received: 120
          Responses dropped due to errors: 0
          Queries timeout: 0
          Forward loss measurement:
            Average packet loss: 0
            Average packet throughput: 0
          Reverse loss measurement:
            Average packet loss: 0
            Average packet throughput: 0
      LSP name:R3-R2, PM State:Up
        Delay measurement Data:
          Duration: 00:01:59
          Traffic-class: 0
          Queries sent: 120
          Responses received: 120
          Responses dropped due to errors: 0
          Queries timeout: 0
          Best 2-way channel delay: 1754 usecs
          Worst 2-way channel delay: 6885 usecs
          Best round trip time: 2971 usecs
          Worst round trip time: 106082 usecs
          Avg absolute fw delay variation: 8833 usecs
          Avg absolute rv delay variation: 5726 usecs
      LSP name:R3-R2, PM State:Up
        Loss measurement Data:
          Duration: 00:02:00                
          Traffic-class: 0
          Queries sent: 120
          Responses received: 120
          Responses dropped due to errors: 0
          Queries timeout: 0
          Forward loss measurement:
            Average packet loss: 0
            Average packet throughput: 0
          Reverse loss measurement:
            Average packet loss: 0
            Average packet throughput: 0
        Delay measurement Data:
          Best 2-way channel delay: 1781 usecs
          Worst 2-way channel delay: 7954 usecs
          Best round trip time: 2981 usecs
          Worst round trip time: 106639 usecs
          Avg absolute fw delay variation: 6326 usecs
          Avg absolute rv delay variation: 4938 usecs

     

    Since You have DPC cards in Z-node, did You enable ultimate-hop-popping with VT interface?

    https://www.juniper.net/documentation/en_US/junos/topics/reference/configuration-statement/ultimate-hop-popping-edit-protocols-mpls.html

     

    AFAIK, to do that, You need to configure "tunnel-services" under "protocols rsvp" 

    https://www.juniper.net/documentation/en_US/junos/topics/reference/configuration-statement/tunnel-services-edit-protocols-rsvp.html 

    I don't have DPC cards in my lab to try.

    HTH

    Thx

    Alex

     



  • 9.  Re: Pro-active Loss and Delay Measurements for Bidirectional MPLS LSPs

    Posted 10-15-2020 10:31

    Thank you so much!


    I found other 2xMX480 (MPC based) and followed the instructions - all is crystal clear!

     

    Thank you so much!