Static route FRR configuration example

As shown in Figure 5, configure static routes on Switch A, Switch B, and Switch C, and configure static route FRR. When Link A becomes unidirectional, traffic can be switched to Link B immediately.

1. Configure IP addresses for interfaces. (Details not shown.)

2. Configure static route FRR on link A by using one of the following methods:

   • (Method 1.) Specify a backup next hop for static route FRR:

     # Configure a static route on Switch A, and specify VLAN-interface 100 as the backup output interface and 12.12.12.2 as the backup next hop.

     <SwitchA> system-view
     [SwitchA] ip route-static 4.4.4.4 32 vlan-interface 200 13.13.13.2 backup-interface vlan-interface 100 backup-nexthop 12.12.12.2
     

     # Configure a static route on Switch B, and specify VLAN-interface 101 as the backup output interface and 24.24.24.2 as the backup next hop.

     <SwitchB> system-view
     [SwitchB] ip route-static 1.1.1.1 32 vlan-interface 200 13.13.13.1 backup-interface vlan-interface 101 backup-nexthop 24.24.24.2
     

   • (Method 2.) Configure static route FRR to automatically select a backup next hop:

     # Configure static routes on Switch A, and enable static route FRR.

     <SwitchA> system-view
     [SwitchA] ip route-static 4.4.4.4 32 vlan-interface 200 13.13.13.2
     [SwitchA] ip route-static 4.4.4.4 32 vlan-interface 100 12.12.12.2 preference 70
     [SwitchA] ip route-static fast-reroute auto
     

     # Configure static routes on Switch B, and enable static route FRR.

     <SwitchB> system-view
     [SwitchB] ip route-static 1.1.1.1 32 vlan-interface 200 13.13.13.1
     [SwitchB] ip route-static 1.1.1.1 32 vlan-interface 101 24.24.24.2 preference 70
     [SwitchB] ip route-static fast-reroute auto
     

3. Configure static routes on Switch C.

   <SwitchC> system-view
   [SwitchC] ip route-static 4.4.4.4 32 vlan-interface 101 24.24.24.4
   [SwitchC] ip route-static 1.1.1.1 32 vlan-interface 100 12.12.12.1
   

# Display route 4.4.4.4/32 on Switch A to view the backup next hop information.

[SwitchA] display ip routing-table 4.4.4.4 verbose

Summary Count : 1

Destination: 4.4.4.4/32
   Protocol: Static          
 Process ID: 0
  SubProtID: 0x0                     Age: 04h20m37s
       Cost: 0                Preference: 60
      IpPre: N/A              QosLocalID: N/A
        Tag: 0                     State: Active Adv
  OrigTblID: 0x0                 OrigVrf: default-vrf
    TableID: 0x2                  OrigAs: 0
      NibID: 0x26000002           LastAs: 0
     AttrID: 0xffffffff         Neighbor: 0.0.0.0
      Flags: 0x1008c         OrigNextHop: 13.13.13.2
      Label: NULL            RealNextHop: 13.13.13.2
    BkLabel: NULL              BkNextHop: 12.12.12.2
  Tunnel ID: Invalid           Interface: Vlan-interface200
BkTunnel ID: Invalid         BkInterface: Vlan-interface100
   FtnIndex: 0x0            TrafficIndex: N/A
  Connector: N/A

# Display route 1.1.1.1/32 on Switch B to view the backup next hop information.

[SwitchB] display ip routing-table 1.1.1.1 verbose

Summary Count : 1

Destination: 1.1.1.1/32
   Protocol: Static          
 Process ID: 0
  SubProtID: 0x0                     Age: 04h20m37s
       Cost: 0                Preference: 60
      IpPre: N/A              QosLocalID: N/A
        Tag: 0                     State: Active Adv
  OrigTblID: 0x0                 OrigVrf: default-vrf
    TableID: 0x2                  OrigAs: 0
      NibID: 0x26000002           LastAs: 0
     AttrID: 0xffffffff         Neighbor: 0.0.0.0
      Flags: 0x1008c         OrigNextHop: 13.13.13.1
      Label: NULL            RealNextHop: 13.13.13.1
    BkLabel: NULL              BkNextHop: 24.24.24.2
  Tunnel ID: Invalid           Interface: Vlan-interface200
BkTunnel ID: Invalid         BkInterface: Vlan-interface101
   FtnIndex: 0x0            TrafficIndex: N/A
  Connector: N/A