cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2570
Views
0
Helpful
2
Replies
lvpin Lv
Beginner

MPLS TE SRLG(Shared Risk Link Groups)

Hello everyone I am a for students from China, here is my problem, my English is not good, this is done by google translate.

No one has yet to answer it?

If you know the answer, please send to my mailbox 。550513723@qq.com

Highest respects to your

Lab Topology。

topology.png

Narrative

MPLS -TE auto-tunnel,will be the preferred R1-R2-R3-R4 this path

Now

Red part(R2-R5-R6-R3) Bandwidth 1000 Kbit/sec

Blue part(R2-R7-R8-R3)Bandwidth 100 Kbit/sec

If R2-R3 link fails,I hope that auto-tunnel select R1-R2-R7-R8-R3-R4 this route,Instead of Red Link

Lab requirements

①If R2-R3 link fails,I hope that auto-tunnel select R1-R2-R7-R8-R3-R4 this route,Instead of Red Link

Use only SRLG technology,Can not be used mpls traffi-eng attribute-flags,Or change weights method。

I queries cisco document,then I do not know how it should be either configured to complete the experiment.

Are here seek to you for your help, thank you.


        http://www.cisco.com/en/US/docs/ios/12_0s/feature/guide/fs29srlg.html

Supplementary

SRLG,To prevent auto-tunnel is automatically created at the time, primary tunnel and the backup tunnel to use same link as

So how to configure it to to prevent this situation?

Thank you very much

Supplementary again

I re-do the experiment,Differ And before。I created on R2 auto-tunnel primary and backup auto tunnel. Then use the SRLG, reached the experimental results. But there are a few commands do not understand, I hope to get help.

Configuration files can be downloaded below

Help

R2(config)#mpls traffic-eng auto-tunnel backup config unnumbered-interface 【interface】

Here is manually specify the backup tunnel it?


R2(config)#mpls traffic-eng auto-tunnel primary config unnumbered-interface  【interface】

Here are primary tunnel manually specify what?

But when I fill in here the tunnel interface when an error occurred cannot generate a backup tunnel

RSVP is always being given, how to solve?

*Aug 27 20:00:56.287: %RSVP-3-IP_HDR: 46C000F0 00540000 FE2EF1C3 0A010101 28010101 94040000 10010000 FF0000D8

*Aug 27 20:00:56.287: %RSVP-3-MSG_1:  10010000 FF0000D8 00100107 28010101 00000001 0A010101 000C0301 0C010101

*Aug 27 20:00:56.287: %RSVP-3-MSG_2:  02000405 00080501 00007530 00341401 01080C01 01022000 01081701 01022000

SRLG and auto-tunnel(auto-Template ) can be used in combination with it?

About the Experiment

I will, R2-R3 link and R2-R5 link configuration "mpls traffic-eng srlg 1"

SHOW

R2#show ip rsvp fast-reroute

Primary                   Protect BW         Backup      

Tunnel                    I/F     BPS:Type   Tunnel:Label  State  Level   Type 

------                    ------- --------   ------------- ------ -----   ------

R2_t203                   Fa0/0   0:G        None          None   None  

R2_t201                   Fa0/1   0:G        Tu2001:0      Ready  any-unl Nhop 

R2_t202                   Et1/0   0:G        Tu2002:0      Ready  any-unl Nhop 

R2_t200                   Et1/1   0:G        Tu2000:0      Ready  any-unl Nhop 

R2#show mpls traffic-eng tunnels tunnel 202Primary tunnel Use the red link】

Name: R2_t202                             (Tunnel202) Destination: 50.1.1.1

  Status:

    Admin: up         Oper: up     Path: valid       Signalling: connected

    path option 1, type explicit __dynamic_tunnel202 (Basis for Setup, path weight 10)

  Config Parameters:

    Bandwidth: 0        kbps (Global)  Priority: 7  7   Affinity: 0x0/0xFFFF

    Metric Type: TE (default)

    AutoRoute:  enabled   LockDown: disabled  Loadshare: 0        bw-based

    auto-bw: disabled

  Active Path Option Parameters:

    State: explicit path option 1 is active

    BandwidthOverride: disabled  LockDown: disabled  Verbatim: disabled

  InLabel  :  -

  OutLabel : Ethernet1/0, implicit-null

  FRR OutLabel : Tunnel2002, explicit-null

  RSVP Signalling Info:

       Src 20.1.1.1, Dst 50.1.1.1, Tun_Id 202, Tun_Instance 7177

    RSVP Path Info:

      My Address: 25.1.1.2  

      Explicit Route: 25.1.1.5 50.1.1.1

      Record   Route:   NONE

      Tspec: ave rate=0 kbits, burst=1000 bytes, peak rate=0 kbits

    RSVP Resv Info:

      Record   Route:  50.1.1.1(0)

      Fspec: ave rate=0 kbits, burst=1000 bytes, peak rate=0 kbits

  Shortest Unconstrained Path Info:

    Path Weight: 10 (TE)

   Explicit Route: 25.1.1.2 25.1.1.5 50.1.1.1

  History:

    Tunnel:

      Time since created: 13 minutes, 48 seconds

      Time since path change: 13 minutes, 47 seconds

      Number of LSP IDs (Tun_Instances) used: 1

    Current LSP:

      Uptime: 13 minutes, 47 seconds

R2#show mpls traffic-eng tunnels tunnel 2002Your can see the backup tunnel, use the blue link】

Name: R2_t2002                            (Tunnel2002) Destination: 50.1.1.1

  Status:

    Admin: up         Oper: up     Path: valid       Signalling: connected

    path option 1, type explicit __dynamic_tunnel2002 (Basis for Setup, path weight 50)

  Config Parameters:

    Bandwidth: 0        kbps (Global)  Priority: 7  7   Affinity: 0x0/0xFFFF

    Metric Type: TE (default)

    AutoRoute:  disabled  LockDown: disabled  Loadshare: 0        bw-based

    auto-bw: disabled

  Active Path Option Parameters:

    State: explicit path option 1 is active

    BandwidthOverride: disabled  LockDown: disabled  Verbatim: disabled

  InLabel  :  -

  OutLabel : Ethernet1/1, 17

  RSVP Signalling Info:

       Src 20.1.1.1, Dst 50.1.1.1, Tun_Id 2002, Tun_Instance 7

    RSVP Path Info:

      My Address: 27.1.1.2  

      Explicit Route: 27.1.1.7 78.1.1.7 78.1.1.8 38.1.1.8

                      38.1.1.3 36.1.1.3 36.1.1.6 56.1.1.6

                      56.1.1.5 50.1.1.1

      Record   Route:   NONE

      Tspec: ave rate=0 kbits, burst=1000 bytes, peak rate=0 kbits

    RSVP Resv Info:

      Record   Route:   NONE

      Fspec: ave rate=0 kbits, burst=1000 bytes, peak rate=0 kbits

  Shortest Unconstrained Path Info:

    Path Weight: 10 (TE)

    Explicit Route: 25.1.1.2 25.1.1.5 50.1.1.1

  History:

    Tunnel:

      Time since created: 16 minutes, 12 seconds

      Time since path change: 16 minutes, 8 seconds

      Number of LSP IDs (Tun_Instances) used: 7

    Current LSP:

      Uptime: 16 minutes, 8 seconds



1 ACCEPTED SOLUTION

Accepted Solutions
Marwan ALshawi
Advisor

try this

in R2 e1/0 ( red path ) configure the below command:

interface e1/0 mpls traffic-engineering srlg 1

On each router, configure the following for automatic SRLG-diverse backup  tunnel path computation and provisioning:

mpls traffic-engineering auto-tunnel backup srlg exclude preferred

OSPF extensions allow each router to automatically learn about the SRLG membership

hope this helps

View solution in original post

2 REPLIES 2
Marwan ALshawi
Advisor

try this

in R2 e1/0 ( red path ) configure the below command:

interface e1/0 mpls traffic-engineering srlg 1

On each router, configure the following for automatic SRLG-diverse backup  tunnel path computation and provisioning:

mpls traffic-engineering auto-tunnel backup srlg exclude preferred

OSPF extensions allow each router to automatically learn about the SRLG membership

hope this helps

View solution in original post

Waiting so long,Finally have the answers,

First, you want to make thank marwanshami

I configured before Collect

mpls traffic-eng auto-tunnel backup srlg exclude force

interface FastEthernet0/1      (R2 Ordinary path)

ip address 23.1.1.2 255.255.255.0

mpls traffic-eng srlg 1

..............

!

interface Ethernet1/0            (R2 red path)

ip address 25.1.1.2 255.255.255.0

mpls traffic-eng srlg 1

.........

Experimental results seem to meet needs

However, I do not know,My configuration is not the correct

So come here, confirmation

Also want to know there is no room for improvement

Anyway thanks for your help

Regards

Content for Community-Ad