15
# Display route 4.4.4.4/32 on Switch S to view the backup next hop information.
[SwitchS] display ip routing-table 4.4.4.4 verbose
Routing Table : Public
Summary Count : 1
Destination: 4.4.4.4/32
Protocol: Static Process ID: 0
Preference: 60 Cost: 0
IpPrecedence: QosLcId:
NextHop: 13.13.13.2 Interface: vlan 200
BkNextHop: 12.12.12.2 BkInterface: vlan 100
RelyNextHop: 0.0.0.0 Neighbor : 0.0.0.0
Tunnel ID: 0x0 Label: NULL
BKTunnel ID: 0x0 BKLabel: NULL
State: Active Adv Age: 00h01m27s
Tag: 0
# Display route 1.1.1.1/32 on Switch D to view the backup next hop information.
[SwitchD] display ip routing-table 1.1.1.1 verbose
Routing Table : Public
Summary Count : 1
Destination: 1.1.1.1/32
Protocol: Static Process ID: 0
Preference: 60 Cost: 0
IpPrecedence: QosLcId:
NextHop: 13.13.13.1 Interface: vlan 200
BkNextHop: 24.24.24.2 BkInterface: vlan 101
RelyNextHop: 0.0.0.0 Neighbor : 0.0.0.0
Tunnel ID: 0x0 Label: NULL
BKTunnel ID: 0x0 BKLabel: NULL
State: Active Adv Age: 00h01m27s
Tag: 0
BFD for static routes configuration example (direct next hop)
Network requirements
As shown in
, configure static routes to subnet 120.1.1.0/24 on Switch A, static routes to subnet
121.1.1.0/24 on Switch B, and static routes to subnets 120.1.1.0/24 and 121.1.1.0/24 on Switch C.
Enable BFD so that when the link between Switch A and Switch B through the Layer 2 switch fails, BFD
can detect the failure immediately and Switch A and Switch B can communicate through Switch C.