Associating Track with static routing

A static route is a manually configured route to route packets. For more information about static route configuration, see Layer 3—IP Routing Configuration Guide.

Static routes cannot adapt to network topology changes. Link failures or network topological changes can make the routes unreachable and cause communication interruption.

To resolve this problem, configure another route to back up the static route. When the static route is reachable, packets are forwarded through the static route. When the static route is unreachable, packets are forwarded through the backup route.

To check the accessibility of a static route in real time, associate the Track module with the static route.

If you specify the next hop but not the output interface when configuring a static route, you can configure the static routing-Track-detection module collaboration. This collaboration enables you to verify the accessibility of the static route based on the track entry state.

When you associate Track with static routing, follow these restrictions and guidelines:

To associate Track with static routing:

Step

Command

Remarks

1. Enter system view.

system-view

N/A

2. Associate a static route with a track entry to check the accessibility of the next hop.

  • Method 1:ip route-static { dest-address { mask-length | mask } | group group-name } { next-hop-address track track-entry-number | vpn-instance d-vpn-instance-name next-hop-address track track-entry-number } [ preference preference-value ] [ tag tag-value ] [ description description-text ]

  • Method 2:ip route-static vpn-instance s-vpn-instance-name { dest-address { mask-length | mask } | group group-name } { next-hop-address [ public ] track track-entry-number | vpn-instance d-vpn-instance-name next-hop-address track track-entry-number } [ preference preference-value ] [ tag tag-value ] [ description description-text ]

By default, Track is not associated with static routing.