Routing

Hi folks,

I had a question about MPLS LSP bypass feature.

So, here is the situation - I need to create a bypass LSP from the head-end router to the tail-end router. I am enabling link-protection on all links under RSVP, creating MPLS LSP with primary path, secondary path and "link-protection" options enabled under that LSP. In addition, under relevant interface under RSVP I am creating bypass itself with specific path and destination of tail-end router (using strict next-hops).

However, after configuration is commited, when I run "show mpls lsp bypass", the state of this LSP is displayed as "NotInService".

I've read about Bypass LSPs, but did not find where it is mentioned, how LSP can be forced to use this manually created bypass.

Any ideas, what could be wrong with it?

Thanks

Hello,

Please share LSP config and "show mpls lsp extensive" output. 

Hi folks,

I had a question about MPLS LSP bypass feature.

So, here is the situation - I need to create a bypass LSP from the head-end router to the tail-end router. I am enabling link-protection on all links under RSVP, creating MPLS LSP with primary path, secondary path and "link-protection" options enabled under that LSP. In addition, under relevant interface under RSVP I am creating bypass itself with specific path and destination of tail-end router (using strict next-hops).

However, after configuration is commited, when I run "show mpls lsp bypass", the state of this LSP is displayed as "NotInService".

I've read about Bypass LSPs, but did not find where it is mentioned, how LSP can be forced to use this manually created bypass.

Any ideas, what could be wrong with it?

Thanks

Hi,

I've attached the test topology.

Primary path for the LSP is in red, while desired bypass LSP path is in blue.  The idea is to protect primary path over PE6-PE5 with bypass LSP path over PE3-PE7-PE6 from link failure between PE2-PE6.

Note that load-balancing policy is applied to forwarding. 

label-switched-path pe2-pe5 {
    to 192.168.1.5;
    link-protection;
    primary primary1 {
        admin-group include-any blue;
    }
    secondary secondary1 {
        standby;
    }
}

interface ge-0/0/2.0 {
    link-protection {
        bypass pe3-pe7-bypass {
            to 192.168.1.6;
            bandwidth 100m;
            path {
                192.168.1.3 strict;
                192.168.1.7 strict;
                192.168.1.6 strict;
            }
        }
    }
}

192.168.1.5
  From: 192.168.1.2, State: Up, ActiveRoute: 0, LSPname: pe2-pe5, LSPid: 3
  ActivePath: primary1 (primary)
  Link protection desired
  LSPtype: Static Configured, Penultimate hop popping
  LoadBalance: Random
  Follow destination IGP metric
  Encoding type: Packet, Switching type: Packet, GPID: IPv4
  LSP Self-ping Status : Enabled
 *Primary   primary1         State: Up
    Priorities: 7 0
    SmartOptimizeTimer: 180
          Include Any: blue
    Flap Count: 3
    MBB Count: 0
    Computed ERO (S [L] denotes strict [loose] hops): (CSPF metric: 20)
 10.2.6.6 S 10.5.6.5 S 
    Received RRO (ProtectionFlag 1=Available 2=InUse 4=B/W 8=Node 10=SoftPreempt 20=Node-ID):
          192.168.1.6(flag=0x20) 10.2.6.6(Label=300416) 192.168.1.5(flag=0x20) 10.5.6.5(Label=3)
  Standby   secondary1       State: Up
    Priorities: 7 0
    SmartOptimizeTimer: 180
    Flap Count: 0
    MBB Count: 0
    Computed ERO (S [L] denotes strict [loose] hops): (CSPF metric: 40)
 10.2.3.3 S 10.3.7.7 S 10.6.7.6 S 10.5.6.5 S 
    Received RRO (ProtectionFlag 1=Available 2=InUse 4=B/W 8=Node 10=SoftPreempt 20=Node-ID):
          192.168.1.3(flag=0x21) 10.2.3.3(flag=1 Label=300640) 192.168.1.7(flag=0x21) 10.3.7.7(flag=1 Label=300112) 192.168.1.6(flag=0x20) 10.6.7.6(Label=300480) 192.168.1.5(flag=0x20) 10.5.6.5(Label=3)

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

The thing is, when I enable link protection under relevant LSP, it automatically calculates bypass LSP and does not use manually configured bypass LSP under protocols > rsvp > interface 

Ingress LSP: 2 sessions
To              From            State   Rt Style Labelin Labelout LSPname 
192.168.1.6     192.168.1.2     Up       0  1 SE       -   299936 Bypass->10.2.6.6
192.168.1.6     192.168.1.2     NotInService  0 0  -       -        - pe3-pe7-bypass

Hello,

Please share LSP config and "show mpls lsp extensive" output. 

Hi folks,

I had a question about MPLS LSP bypass feature.

So, here is the situation - I need to create a bypass LSP from the head-end router to the tail-end router. I am enabling link-protection on all links under RSVP, creating MPLS LSP with primary path, secondary path and "link-protection" options enabled under that LSP. In addition, under relevant interface under RSVP I am creating bypass itself with specific path and destination of tail-end router (using strict next-hops).

However, after configuration is commited, when I run "show mpls lsp bypass", the state of this LSP is displayed as "NotInService".

I've read about Bypass LSPs, but did not find where it is mentioned, how LSP can be forced to use this manually created bypass.

Any ideas, what could be wrong with it?

Thanks

Hi,

If the primary goal is to protect the path you can use the following configuration.

        label-switched-path pe2-pe5 {
            to 192.168.1.5;
            link-protection;
            primary primary1 {  ### PE2-PE6-PE5
                admin-group include-any red; 
            }
            secondary secondary1 { ### PE2-PE3-PE7-PE6-PE5
                standby;

            }
        }

        path secondary1 {
            192.168.1.3 strict;
            192.168.1.7 strict;
            192.168.1.6 strict;
            192.168.1.5 strict;
        }

If you want to test bypass configuration under rsvp please share full config. I will lab it and let you know.

Hi,

I've attached the test topology.

Primary path for the LSP is in red, while desired bypass LSP path is in blue.  The idea is to protect primary path over PE6-PE5 with bypass LSP path over PE3-PE7-PE6 from link failure between PE2-PE6.

Note that load-balancing policy is applied to forwarding. 

label-switched-path pe2-pe5 {
    to 192.168.1.5;
    link-protection;
    primary primary1 {
        admin-group include-any blue;
    }
    secondary secondary1 {
        standby;
    }
}

interface ge-0/0/2.0 {
    link-protection {
        bypass pe3-pe7-bypass {
            to 192.168.1.6;
            bandwidth 100m;
            path {
                192.168.1.3 strict;
                192.168.1.7 strict;
                192.168.1.6 strict;
            }
        }
    }
}

192.168.1.5
  From: 192.168.1.2, State: Up, ActiveRoute: 0, LSPname: pe2-pe5, LSPid: 3
  ActivePath: primary1 (primary)
  Link protection desired
  LSPtype: Static Configured, Penultimate hop popping
  LoadBalance: Random
  Follow destination IGP metric
  Encoding type: Packet, Switching type: Packet, GPID: IPv4
  LSP Self-ping Status : Enabled
 *Primary   primary1         State: Up
    Priorities: 7 0
    SmartOptimizeTimer: 180
          Include Any: blue
    Flap Count: 3
    MBB Count: 0
    Computed ERO (S [L] denotes strict [loose] hops): (CSPF metric: 20)
 10.2.6.6 S 10.5.6.5 S 
    Received RRO (ProtectionFlag 1=Available 2=InUse 4=B/W 8=Node 10=SoftPreempt 20=Node-ID):
          192.168.1.6(flag=0x20) 10.2.6.6(Label=300416) 192.168.1.5(flag=0x20) 10.5.6.5(Label=3)
  Standby   secondary1       State: Up
    Priorities: 7 0
    SmartOptimizeTimer: 180
    Flap Count: 0
    MBB Count: 0
    Computed ERO (S [L] denotes strict [loose] hops): (CSPF metric: 40)
 10.2.3.3 S 10.3.7.7 S 10.6.7.6 S 10.5.6.5 S 
    Received RRO (ProtectionFlag 1=Available 2=InUse 4=B/W 8=Node 10=SoftPreempt 20=Node-ID):
          192.168.1.3(flag=0x21) 10.2.3.3(flag=1 Label=300640) 192.168.1.7(flag=0x21) 10.3.7.7(flag=1 Label=300112) 192.168.1.6(flag=0x20) 10.6.7.6(Label=300480) 192.168.1.5(flag=0x20) 10.5.6.5(Label=3)

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

The thing is, when I enable link protection under relevant LSP, it automatically calculates bypass LSP and does not use manually configured bypass LSP under protocols > rsvp > interface 

Ingress LSP: 2 sessions
To              From            State   Rt Style Labelin Labelout LSPname 
192.168.1.6     192.168.1.2     Up       0  1 SE       -   299936 Bypass->10.2.6.6
192.168.1.6     192.168.1.2     NotInService  0 0  -       -        - pe3-pe7-bypass

Hello,

Please share LSP config and "show mpls lsp extensive" output. 

Hi folks,

I had a question about MPLS LSP bypass feature.

So, here is the situation - I need to create a bypass LSP from the head-end router to the tail-end router. I am enabling link-protection on all links under RSVP, creating MPLS LSP with primary path, secondary path and "link-protection" options enabled under that LSP. In addition, under relevant interface under RSVP I am creating bypass itself with specific path and destination of tail-end router (using strict next-hops).

However, after configuration is commited, when I run "show mpls lsp bypass", the state of this LSP is displayed as "NotInService".

I've read about Bypass LSPs, but did not find where it is mentioned, how LSP can be forced to use this manually created bypass.

Any ideas, what could be wrong with it?

Thanks

Hi,

As you mentioned, the idea is to test the bypass feature under RSVP. 

I already shared RSVP configuration section from the router. Interface ge-0/0/2 is the interface between PE2 and PE3, over which I am trying to build bypass to protect LSP from the link failure between PE2-PE6. Full configuration would be too long, I guess. But if it is still needed, then I can add it as a separate file.

Hi,

If the primary goal is to protect the path you can use the following configuration.

        label-switched-path pe2-pe5 {
            to 192.168.1.5;
            link-protection;
            primary primary1 {  ### PE2-PE6-PE5
                admin-group include-any red; 
            }
            secondary secondary1 { ### PE2-PE3-PE7-PE6-PE5
                standby;

            }
        }

        path secondary1 {
            192.168.1.3 strict;
            192.168.1.7 strict;
            192.168.1.6 strict;
            192.168.1.5 strict;
        }

If you want to test bypass configuration under rsvp please share full config. I will lab it and let you know.

Hi,

I've attached the test topology.

Primary path for the LSP is in red, while desired bypass LSP path is in blue.  The idea is to protect primary path over PE6-PE5 with bypass LSP path over PE3-PE7-PE6 from link failure between PE2-PE6.

Note that load-balancing policy is applied to forwarding. 

label-switched-path pe2-pe5 {
    to 192.168.1.5;
    link-protection;
    primary primary1 {
        admin-group include-any blue;
    }
    secondary secondary1 {
        standby;
    }
}

interface ge-0/0/2.0 {
    link-protection {
        bypass pe3-pe7-bypass {
            to 192.168.1.6;
            bandwidth 100m;
            path {
                192.168.1.3 strict;
                192.168.1.7 strict;
                192.168.1.6 strict;
            }
        }
    }
}

192.168.1.5
  From: 192.168.1.2, State: Up, ActiveRoute: 0, LSPname: pe2-pe5, LSPid: 3
  ActivePath: primary1 (primary)
  Link protection desired
  LSPtype: Static Configured, Penultimate hop popping
  LoadBalance: Random
  Follow destination IGP metric
  Encoding type: Packet, Switching type: Packet, GPID: IPv4
  LSP Self-ping Status : Enabled
 *Primary   primary1         State: Up
    Priorities: 7 0
    SmartOptimizeTimer: 180
          Include Any: blue
    Flap Count: 3
    MBB Count: 0
    Computed ERO (S [L] denotes strict [loose] hops): (CSPF metric: 20)
 10.2.6.6 S 10.5.6.5 S 
    Received RRO (ProtectionFlag 1=Available 2=InUse 4=B/W 8=Node 10=SoftPreempt 20=Node-ID):
          192.168.1.6(flag=0x20) 10.2.6.6(Label=300416) 192.168.1.5(flag=0x20) 10.5.6.5(Label=3)
  Standby   secondary1       State: Up
    Priorities: 7 0
    SmartOptimizeTimer: 180
    Flap Count: 0
    MBB Count: 0
    Computed ERO (S [L] denotes strict [loose] hops): (CSPF metric: 40)
 10.2.3.3 S 10.3.7.7 S 10.6.7.6 S 10.5.6.5 S 
    Received RRO (ProtectionFlag 1=Available 2=InUse 4=B/W 8=Node 10=SoftPreempt 20=Node-ID):
          192.168.1.3(flag=0x21) 10.2.3.3(flag=1 Label=300640) 192.168.1.7(flag=0x21) 10.3.7.7(flag=1 Label=300112) 192.168.1.6(flag=0x20) 10.6.7.6(Label=300480) 192.168.1.5(flag=0x20) 10.5.6.5(Label=3)

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

The thing is, when I enable link protection under relevant LSP, it automatically calculates bypass LSP and does not use manually configured bypass LSP under protocols > rsvp > interface 

Ingress LSP: 2 sessions
To              From            State   Rt Style Labelin Labelout LSPname 
192.168.1.6     192.168.1.2     Up       0  1 SE       -   299936 Bypass->10.2.6.6
192.168.1.6     192.168.1.2     NotInService  0 0  -       -        - pe3-pe7-bypass

Hello,

Please share LSP config and "show mpls lsp extensive" output. 

Hi folks,

I had a question about MPLS LSP bypass feature.

So, here is the situation - I need to create a bypass LSP from the head-end router to the tail-end router. I am enabling link-protection on all links under RSVP, creating MPLS LSP with primary path, secondary path and "link-protection" options enabled under that LSP. In addition, under relevant interface under RSVP I am creating bypass itself with specific path and destination of tail-end router (using strict next-hops).

However, after configuration is commited, when I run "show mpls lsp bypass", the state of this LSP is displayed as "NotInService".

I've read about Bypass LSPs, but did not find where it is mentioned, how LSP can be forced to use this manually created bypass.

Any ideas, what could be wrong with it?

Thanks

Hi Farid,

As I know you should change configuration  rsvp>interface ge-0/0/2 (PE2-PE3) to interface between PE2-PE6. In your case you are trying to protect link between PE2 and PE3 .

interface ge-0/0/X.0 {   ### (PE2-PE6)
    link-protection {
        bypass pe3-pe7-bypass {
            to 192.168.1.6;
            bandwidth 100m;
            path {
                192.168.1.3 strict;
                192.168.1.7 strict;
                192.168.1.6 strict;
            }
        }
    }
}

Hi,

As you mentioned, the idea is to test the bypass feature under RSVP. 

I already shared RSVP configuration section from the router. Interface ge-0/0/2 is the interface between PE2 and PE3, over which I am trying to build bypass to protect LSP from the link failure between PE2-PE6. Full configuration would be too long, I guess. But if it is still needed, then I can add it as a separate file.

Hi,

If the primary goal is to protect the path you can use the following configuration.

        label-switched-path pe2-pe5 {
            to 192.168.1.5;
            link-protection;
            primary primary1 {  ### PE2-PE6-PE5
                admin-group include-any red; 
            }
            secondary secondary1 { ### PE2-PE3-PE7-PE6-PE5
                standby;

            }
        }

        path secondary1 {
            192.168.1.3 strict;
            192.168.1.7 strict;
            192.168.1.6 strict;
            192.168.1.5 strict;
        }

If you want to test bypass configuration under rsvp please share full config. I will lab it and let you know.

Hi,

I've attached the test topology.

Primary path for the LSP is in red, while desired bypass LSP path is in blue.  The idea is to protect primary path over PE6-PE5 with bypass LSP path over PE3-PE7-PE6 from link failure between PE2-PE6.

Note that load-balancing policy is applied to forwarding. 

label-switched-path pe2-pe5 {
    to 192.168.1.5;
    link-protection;
    primary primary1 {
        admin-group include-any blue;
    }
    secondary secondary1 {
        standby;
    }
}

interface ge-0/0/2.0 {
    link-protection {
        bypass pe3-pe7-bypass {
            to 192.168.1.6;
            bandwidth 100m;
            path {
                192.168.1.3 strict;
                192.168.1.7 strict;
                192.168.1.6 strict;
            }
        }
    }
}

192.168.1.5
  From: 192.168.1.2, State: Up, ActiveRoute: 0, LSPname: pe2-pe5, LSPid: 3
  ActivePath: primary1 (primary)
  Link protection desired
  LSPtype: Static Configured, Penultimate hop popping
  LoadBalance: Random
  Follow destination IGP metric
  Encoding type: Packet, Switching type: Packet, GPID: IPv4
  LSP Self-ping Status : Enabled
 *Primary   primary1         State: Up
    Priorities: 7 0
    SmartOptimizeTimer: 180
          Include Any: blue
    Flap Count: 3
    MBB Count: 0
    Computed ERO (S [L] denotes strict [loose] hops): (CSPF metric: 20)
 10.2.6.6 S 10.5.6.5 S 
    Received RRO (ProtectionFlag 1=Available 2=InUse 4=B/W 8=Node 10=SoftPreempt 20=Node-ID):
          192.168.1.6(flag=0x20) 10.2.6.6(Label=300416) 192.168.1.5(flag=0x20) 10.5.6.5(Label=3)
  Standby   secondary1       State: Up
    Priorities: 7 0
    SmartOptimizeTimer: 180
    Flap Count: 0
    MBB Count: 0
    Computed ERO (S [L] denotes strict [loose] hops): (CSPF metric: 40)
 10.2.3.3 S 10.3.7.7 S 10.6.7.6 S 10.5.6.5 S 
    Received RRO (ProtectionFlag 1=Available 2=InUse 4=B/W 8=Node 10=SoftPreempt 20=Node-ID):
          192.168.1.3(flag=0x21) 10.2.3.3(flag=1 Label=300640) 192.168.1.7(flag=0x21) 10.3.7.7(flag=1 Label=300112) 192.168.1.6(flag=0x20) 10.6.7.6(Label=300480) 192.168.1.5(flag=0x20) 10.5.6.5(Label=3)

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

The thing is, when I enable link protection under relevant LSP, it automatically calculates bypass LSP and does not use manually configured bypass LSP under protocols > rsvp > interface 

Ingress LSP: 2 sessions
To              From            State   Rt Style Labelin Labelout LSPname 
192.168.1.6     192.168.1.2     Up       0  1 SE       -   299936 Bypass->10.2.6.6
192.168.1.6     192.168.1.2     NotInService  0 0  -       -        - pe3-pe7-bypass

Hello,

Please share LSP config and "show mpls lsp extensive" output. 

Hi folks,

I had a question about MPLS LSP bypass feature.

So, here is the situation - I need to create a bypass LSP from the head-end router to the tail-end router. I am enabling link-protection on all links under RSVP, creating MPLS LSP with primary path, secondary path and "link-protection" options enabled under that LSP. In addition, under relevant interface under RSVP I am creating bypass itself with specific path and destination of tail-end router (using strict next-hops).

However, after configuration is commited, when I run "show mpls lsp bypass", the state of this LSP is displayed as "NotInService".

I've read about Bypass LSPs, but did not find where it is mentioned, how LSP can be forced to use this manually created bypass.

Any ideas, what could be wrong with it?

Thanks