Routing

last person joined: 21 hours ago 

Ask questions and share experiences about ACX Series, CTP Series, MX Series, PTX Series, SSR Series, JRR Series, and all things routing, including portfolios and protocols.
Expand all | Collapse all

automatically clear RSVP session in certain period of time?

  • 1.  automatically clear RSVP session in certain period of time?

    Posted 08-14-2014 19:40

    Hi All,

     

     

    Is there any way how to clear rsvp session clear the bypass lsp's or a way to set a timer to clear those bypass lsp's that does not carry traffic.

     

     

    Thanks and aapreciate someone feedback



  • 2.  RE: automatically clear RSVP session in certain period of time?

    Posted 08-21-2014 09:58

    Bypass LSPs do exist to locally protect your LSP from a link or node failure as quick as possible. And this protection is expected to be temporary. Hence it is your interest that those RSVP sessions are up and available all allong your LSP life.

    If bypass LSPs were to be signalled after the failure were detected then probably within the same amount of time the ingress LSR would already have been notified of the failure and might already have rerouted the traffic to a pre-signalled standby secondary path. In that case the bypass LSP would have been totally useless.

     

    If your concern is ressources consumption on the local router then you should know that bypass LSPs can be shared by all LSPs exiting the router through the protected link.



  • 3.  RE: automatically clear RSVP session in certain period of time?

     
    Posted 08-21-2014 19:25

    There is no mechanism to clear the bypass lsp if it doesn't carry traffic. The bypass lsp is created and destroyed only with link or node-link protection knob. However if a bypass lsp is not associated or used by any primary lsp, it will timeout after certain duration.



  • 4.  RE: automatically clear RSVP session in certain period of time?

    Posted 08-24-2014 03:52

    Hi Surya / All,

     

     

     

    thanks for your explanation.



  • 5.  RE: automatically clear RSVP session in certain period of time?

    Posted 08-24-2014 20:20

    Hi Surya / All,

     

     

    Is there anyone know  "However if a bypass lsp is not associated or used by any primary lsp, it will timeout after certain duration" the period time the bypass lsp will be clear? Can u guide the doc for that info?

     

     

    thanks and appreciate someone feedback.



  • 6.  RE: automatically clear RSVP session in certain period of time?

    Posted 08-25-2014 02:57

    It means that if no LSP is transiting through the protected link for which the bypass LSP was created then that bypass LSP would timeout.

     

    If you do not want pre-signaled LSPs in your network then you should consider using secondary paths. But this will increase your repair time.



  • 7.  RE: automatically clear RSVP session in certain period of time?

     
    Posted 08-25-2014 12:44
    Hi,

    The timeout duration for non-used bypass-lsp is 180 seconds.

    You would see a syslog message like below for these cases:

    RPD_RSVP_BYPASS_DOWN: RSVP bypass Bypass->10.8.1.2 for protecting interface xe-2/2/1.0 went down, reason: inactivity timeout


  • 8.  RE: automatically clear RSVP session in certain period of time?

    Posted 08-25-2014 19:20

    Hi pantunes,

     

    When u said  "It means that if no LSP is transiting through the protected link for which the bypass LSP was created then that bypass LSP would timeout"  it referring the bypass LSP will still appear until no traffic use that bypass LSP even as a transit /egress right? Please correct if i misunderstanding what u said.

     

     

    Hi Surya,

     

    180 second is default right. Can we force to clear that bypass LSP if that LSP not carried any traffic when i do command "show mpls mpls_name statistic".

     

    Thanks and appreciate your feedback

     

     

     



  • 9.  RE: automatically clear RSVP session in certain period of time?
    Best Answer

     
    Posted 08-25-2014 20:03

    Hi,


    kronicklez wrote:

     

    Hi Surya,

     

    180 second is default right. Can we force to clear that bypass LSP if that LSP not carried any traffic when i do command "show mpls mpls_name statistic".


     

    Yes, that's correct. 180sec timeout for non-used bypass LSP is by default. I don't think there is command to clear bypass lsp. Of course we do have "clear mpls lsp <name>" which can be used only for primary LSP and not for bypass lsp. Again this command will only re-optimize the primary LSP.

     

    Regards

    Surya



  • 10.  RE: automatically clear RSVP session in certain period of time?

    Posted 08-28-2014 02:52

    Hi Surya,

     

     

    Many thanks for your kindness explanation.



  • 11.  RE: automatically clear RSVP session in certain period of time?

    Posted 09-02-2014 18:59

    Hi Surya,

     

     

    We already check the entire router in our network that bypass lsp not carried any traffic even that bypass lsp act as transit or egrees.

     

    Kindly need your expertise how to solve it.

     

     

    thanks



  • 12.  RE: automatically clear RSVP session in certain period of time?

     
    Posted 09-03-2014 04:04
    Hi,

    Did you check if any of the bypass lsp was not associated with any primary lsp? The bypass lsp would be cleared by system if and only if it is not associated with any primary lsp.

    Regards
    Surya


  • 13.  RE: automatically clear RSVP session in certain period of time?

    Posted 09-04-2014 17:18

    Hi Surya,

     

     

    How to check if any of the bypass lsp was not associated with any primary lsp? What command need to excute?

     

     

    Thanks and apreciate your feedback



  • 14.  RE: automatically clear RSVP session in certain period of time?

     
    Posted 09-09-2014 18:01

    Hi ,

     

    Sorry for getting back late on this.

    You can use "show rsvp session bypass extensive" and check "Number of data route tunnel through". If the cout is 0, then it is not used by any primary LSP.

     

    Example: Below is the capture, where there are 2 byapss LSP, one protecting 100 primary LSP, when other is not associated with any primary LSP

     

    show rsvp session bypass extensive | match "name|Number"
      LSPname: Bypass->20.8.1.1
      Port number: sender 1 receiver 33622 protocol 0
        Number of data route tunnel through: 100
        Number of RSVP session tunnel through: 0
      LSPname: Bypass->10.8.2.2
      Port number: sender 1 receiver 33621 protocol 0
        Number of data route tunnel through: 0
        Number of RSVP session tunnel through: 0

     

     

    Regards

    Surya



  • 15.  RE: automatically clear RSVP session in certain period of time?

    Posted 09-16-2014 07:31

    Hi Surya,

     

     

    Sorry disturb you again. Just want to know how i can check the bypass lsp is associated with which primary lsp? For example whether it associates with another lsp name.

     

    Thanks and appreciates your feedback



  • 16.  RE: automatically clear RSVP session in certain period of time?

     
    Posted 09-16-2014 10:29

    Hi kronicklez,

     

    Please don't be sorry, I would be very glad to help and answer your queries at any time. Smiley Happy

     

    In oder to get that information you need to fallback to retrieve the primary LSP rsvp session details as below, where highlighted portion whill indicate which Bypass LSP is being used by this primary LSP.

     

    egress@prussia> show rsvp session lsp extensive 
    Ingress RSVP: 1032 sessions
    
    10.255.5.43
      From: 10.255.14.110, LSPstate: Up, ActiveRoute: 0
      LSPname: R1_R2_LSP_1, LSPpath: Primary
      Suggested label received: -, Suggested label sent: -
      Recovery label received: -, Recovery label sent: 429296
      Resv style: 1 SE, Label in: -, Label out: 429296
      Time left:    -, Since: Mon Nov  2 15:29:19 2009
      Tspec: rate 0bps size 0bps peak Infbps m 20 M 1500
      Port number: sender 1 receiver 37394 protocol 0
      Link protection desired
      Type: Link protected LSP, using Bypass->11.1.1.1
         35 Nov  2 16:57:46 Link protection up, using Bypass->11.1.1.1

     

    AFAIK there isn't a single command to get all primary LSPs associated with Bypass LSP, but you can play around with "match" criteria like below

     

    show rsvp session extensive | match "LSPname|Type: Link protected LSP"

     

    Regards

    Surya



  • 17.  RE: automatically clear RSVP session in certain period of time?

    Posted 09-16-2014 19:50

    Hi Surya,

     

     

    Do i need to do that command to entire router in the network or just on the router ingress only?

     

    Thanks and appreciate your feedback

     

    egress@prussia> show rsvp session lsp extensive 
    Ingress RSVP: 1032 sessions
    
    10.255.5.43
      From: 10.255.14.110, LSPstate: Up, ActiveRoute: 0
      LSPname: R1_R2_LSP_1, LSPpath: Primary
      Suggested label received: -, Suggested label sent: -
      Recovery label received: -, Recovery label sent: 429296
      Resv style: 1 SE, Label in: -, Label out: 429296
      Time left:    -, Since: Mon Nov  2 15:29:19 2009
      Tspec: rate 0bps size 0bps peak Infbps m 20 M 1500
      Port number: sender 1 receiver 37394 protocol 0
      Link protection desired
      Type: Link protected LSP, using Bypass->11.1.1.1
         35 Nov  2 16:57:46 Link protection up, using Bypass->11.1.1.1


  • 18.  RE: automatically clear RSVP session in certain period of time?

     
    Posted 09-17-2014 09:43

    Hi,

     

    Bypass-LSP is local to the PLR(Point of local Repair) router and when the same trasvers other routers it would be similar to a transit LSP.

    Hence you would have to run this command on each of the PLR routers, if you have to see which primary LSP is using which bypass LSP.

     

    Regards

    Surya



  • 19.  RE: automatically clear RSVP session in certain period of time?

    Posted 09-18-2014 08:56

    Hi Surya,

     

     

    many thanks for your explanation. Now i understand how to verify it.

     

    Thanks again.