Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

CRS-8 IOS-XR 4.3.2 not showing up FRR information in "sh mpls traffic-eng fast-reroute database " output

Hi,

The topology looks like below. The four routers are connected in the below said fashion. Note 186 and 195 are connected. The IGP is ISIS.

              7600 185

                    |

                    |

               CRS-8 80

                    /\

                  /     \

   7600 186----ASR9K 195

I have configured the p2mp tunnel on the router 185(head) tunnel765(185->80->186 and 195). 185 headend router ios ver is 15.3.3.

If the interface Gig 0/3/0/7(connected to 186) on .80(mid) is bought down the traffic is fast rerouted towards backup tunnel 387 (80->195->186). But this is not shown in the output of “sh mpls traffic-eng fast-reroute database”.

Please find the other outputs that show the FRR ready and active highlighted below when the int Gig 0/3/0/7 is up and when it is bought down. Any idea what could be the problem?

If we have a p2p MPLS te tunnel from 185->80->195 instead of p2mp, the CRS shows the FRR information as READY and when the interface is bought down trasitions to ACTIVE state.

RP/0/RP1/CPU0:CRS-2-P2-80#sh mpls traffic-eng tunnels backup       

RP/0/RP1/CPU0:CRS-2-P2-80#sh mpls traffic-eng tunnels backup                     

Tue Feb 25 06:45:08.819 UTC

Tue Feb 25 06:47:22.213 UTC

tunnel-te387

tunnel-te387

Admin: up, Oper: up

Admin: up, Oper: up

Src: 192.168.169.80, Dest: 192.168.169.186, Instance: 2

Src: 192.168.169.80, Dest: 192.168.169.186, Instance: 2

Fast Reroute Backup Provided:

Fast Reroute Backup Provided:

  Protected LSPs: 1 (0 active)

  Protected LSPs: 1 (1 active)

  Protected S2L Sharing Families: 1

  Protected S2L Sharing Families: 1

  Protected S2Ls: 1

  Protected S2Ls: 1

Backup BW: any-class (no limit specified), Inuse: 0 kbps

  Backup BW: any-class (no limit specified), Inuse: 0 kbps

  Protected i/fs: Gi0/3/0/7

  Protected i/fs: Gi0/3/0/7

RP/0/RP1/CPU0:CRS-2-P2-80#

RP/0/RP1/CPU0:CRS-2-P2-80#

RP/0/RP1/CPU0:CRS-2-P2-80#sh mpls traffic-eng tunnels protection frr tunnel-id 765

RP/0/RP1/CPU0:CRS-2-P2-80#sh mpls traffic-eng tunnels protection frr tunnel-id 765

Tue Feb 25 06:46:11.067 UTC

Tue Feb 25 06:48:00.279 UTC

p2mp P2MP S2L Tunnel Id: 765

p2mp P2MP S2L Tunnel Id: 765

  Role Midpoint, signaled, connection up

  Role Midpoint, signaled, connection up

  Src: 192.168.169.185, ExtId: 192.168.169.185, Instance: 486

  Src: 192.168.169.185, ExtId: 192.168.169.185, Instance: 486

  Dest: 192.168.169.186, P2MP Id: 765, OrigId: 192.168.169.185, SGId: 1

  Dest: 192.168.169.186, P2MP Id: 765, OrigId: 192.168.169.185, SGId: 1

  Fast Reroute Protection: Requested

  Fast Reroute Protection: Requested

    Inbound: FRR Inactive

    Inbound: FRR Inactive

     S2L signalling info:

     S2L signalling info:

      Original: in i/f: GigabitEthernet0/3/0/9, label:  1048568, phop: 192.168.169.10

      Original: in i/f: GigabitEthernet0/3/0/9, label:  1048568, phop: 192.168.169.10

    Outbound: FRR Ready

    Outbound: FRR Active

     Backup tunnel-te387 to S2L nhop

     Backup tunnel-te387 to S2L nhop

      tunnel-te387: out i/f: GigabitEthernet0/3/0/8, next hop: 192.168.169.2

      tunnel-te387: out i/f: GigabitEthernet0/3/0/8, next hop: 192.168.169.2

     S2L signalling info:

     S2L signalling info:

      Original: out i/f: GigabitEthernet0/3/0/7, label:  1007, next hop: 192.168.169.6

      Original: out i/f: GigabitEthernet0/3/0/7, label:  1007, next hop: 192.168.169.6

      With FRR: out i/f: tunnel-te387, label:  1007

      With FRR: out i/f: tunnel-te387, label:  1007

     Sub-LSP bw: 0 kbps, Backup level: any-class unlimited, type: CT0

     Sub-LSP bw: 0 kbps, Backup level: any-class unlimited, type: CT0

p2mp P2MP S2L Tunnel Id: 765

p2mp P2MP S2L Tunnel Id: 765

  Role Midpoint, signaled, connection up

  Role Midpoint, signaled, connection up

  Src: 192.168.169.185, ExtId: 192.168.169.185, Instance: 486

  Src: 192.168.169.185, ExtId: 192.168.169.185, Instance: 486

  Dest: 192.168.169.195, P2MP Id: 765, OrigId: 192.168.169.185, SGId: 2

  Dest: 192.168.169.195, P2MP Id: 765, OrigId: 192.168.169.185, SGId: 2

  Fast Reroute Protection: Requested

  Fast Reroute Protection: Requested

    Inbound: FRR Inactive

    Inbound: FRR Inactive

     S2L signalling info:

     S2L signalling info:

      Original: in i/f: GigabitEthernet0/3/0/9, label:  1048568, phop: 192.168.169.10

      Original: in i/f: GigabitEthernet0/3/0/9, label:  1048568, phop: 192.168.169.10

    Outbound: FRR Inactive

    Outbound: FRR Inactive

     S2L signalling info:

     S2L signalling info:

      Original: out i/f: GigabitEthernet0/3/0/8, label:  160009, next hop: 192.168.169.2

      Original: out i/f: GigabitEthernet0/3/0/8, label:  160009, next hop: 192.168.169.2

1 REPLY
New Member

finally found the answer.....

finally found the answer......"show mpls traffic-eng fast-reroute database displays only P2P FRR state. For P2MP tunnels, use show mrib mpls traffic-eng fast-reroute database"

162
Views
0
Helpful
1
Replies
CreatePlease to create content