Description

When a static bypass LSP and a dynamic bypass LSP both exists for protecting an LSP, the dynamic LSP is torn-down for optimization (as long as static bypass LSP is up) and the following syslog message appears for the event of bypass LSP tear-down:

DAEMON-4-RPD_RSVP_BYPASS_DOWN: RSVP bypass Bypass->x.x.x.x for protecting interface <interface name> went down, reason: reshuffling data LSP to reduce no of bypasses

Symptoms

The following syslog message is seen:

DAEMON-4-RPD_RSVP_BYPASS_DOWN: RSVP bypass Bypass->x.x.x.x for protecting interface <interface name> went down, reason: reshuffling data LSP to reduce no of bypasses

Additionally, the dynamic bypass LSP does not show up in the output of ' show mpls lsp bypass ':

labroot@DUT> show mpls lsp bypass    
Dec 25 20:23:04
Ingress LSP: 1 sessions
To              From            State   Rt Style Labelin Labelout LSPname 
2.0.0.2         1.0.0.1  Up       0  1 SE       -        0 BYPASS_DUT-to-R2_AE6 
<--- This is static bypass LSP

Topology:
  1. RSVP LSP from DUT to R2 is up:

    labroot@DUT> show mpls lsp 
    Dec 25 20:51:09
    Ingress LSP: 1 sessions
    To              From            State Rt P     ActivePath       LSPname
    2.0.0.2         1.0.0.1  Up     0 *                      DUT-to-R2
  2. Below is the configuration for Static Bypass, protecting interface AE5. The bypass LSP is a strict LSP traversing AE6 only:

    set protocols rsvp interface ae5.0 link-protection bandwidth 150m
    set protocols rsvp interface ae5.0 link-protection subscription 65000
    set protocols rsvp interface ae5.0 link-protection optimize-timer 60
    set protocols rsvp interface ae5.0 link-protection bypass BYPASS_DUT-to-R2_AE6 path 20.1.1.1 strict
    set protocols rsvp interface ae5.0 link-protection bypass BYPASS_DUT-to-R2_AE6 bandwidth 150m
    set protocols rsvp interface ae5.0 link-protection bypass BYPASS_DUT-to-R2_AE6 subscription 65k
    set protocols rsvp interface ae5.0 link-protection bypass BYPASS_DUT-to-R2_AE6 admin-group exclude AVOID-LINK
    set protocols rsvp interface ae5.0 link-protection bypass BYPASS_DUT-to-R2_AE6 admin-group exclude ALL-AVOID
  3. In a normal situation, only Static Bypass LSP will be up:

    labroot@DUT> show mpls lsp bypass 
    Dec 25 20:54:27
    Ingress LSP: 1 sessions
    To              From            State   Rt Style Labelin Labelout LSPname 
    2.0.0.2         1.0.0.1  Up       0  1 SE       -        0 BYPASS_DUT-to-R2_AE6
  4. Lets cost out AE6 by setting COLOR 'AVOID-LINK' on the AE6 bundle. Since the static bypass is configured to avoid this link, the static bypass LSP will go down due to unavailable path:

    labroot@DUT# show | compare 
    Dec 25 20:59:42
    [edit protocols mpls interface ae6.0]
    +    admin-group 'AVOID-LINK ;

    This will lead to dynamic bypass for this LSP to get established since the static bypass has gone down:

    labroot@DUT> show mpls lsp bypass 
    Dec 25 21:00:57
    Ingress LSP: 2 sessions
    To              From            State   Rt Style Labelin Labelout LSPname 
    2.0.0.2         1.0.0.1  Up       0  1 SE       -        0 Bypass->10.1.1.1
    10.1.1.1        1.0.0.1  Down     0  0  -       -        - BYPASS_DUT-to-R2_AE6
  5. Bring back static bypass LSP path-AE6 in service again by removing the COLOR 'AVOID-LINK'. This will help Static bypass LSP to come up again.

    labroot@DUT0# show |compare 
    Dec 25 21:03:27
    [edit protocols mpls interface ae6.0]
    -    admin-group 'AVOID-LINK ;
    labroot@DUT> show mpls lsp bypass 
    Dec 25 21:04:17
    Ingress LSP: 2 sessions
    To              From            State   Rt Style Labelin Labelout LSPname 
    2.0.0.2         1.0.0.1  Up       0  1 SE       -        0 Bypass->10.1.1.1
    2.0.0.2         1.0.0.1  Up       0  1 SE       -        0 BYPASS_DUT-to-R2_AE6
  6. However, on the next 'optimize-timer' expiry, which is configured as 60 seconds here, the dynamic bypass LSP will be torn down. Since the static LSP is already up for it:

    Dec 25 21:04:30.782  DUT rpd[27801]: %DAEMON-4-RPD_RSVP_BYPASS_DOWN: RSVP bypass Bypass->10.1.1.1 for protecting interface ae5.0 went down, reason: reshuffling data LSP to reduce no of bypasses

Solution

This is a day one expected behavior.

  1. This behavior is by design. The optimize timer initiates a periodic optimization process that reshuffles data LSPs among bypass LSPs to achieve the most efficient use of network resources. The optimization process attempts to either minimize the number of bypasses currently in use, minimize the total amount of bandwidth reserved for all bypasses, or both
  2. When the periodic re-optimization timer finds a static (more preferred) bypass configured LSP with non-zero bandwidth, then the code deletes the running dynamic bypass instance.