H3C S5120-EI Series - Displaying and Maintaining Track Entries; Track Configuration Examples; Static Routing-Track-NQA Collaboration Configuration Example

128
• The Invalid state of the track entry shows that the accessibility of the next hop of the static route is
unknown and that the static route is valid.
If a static route needs route recursion, the associated track entry must monitor the next hop of the recursive
route instead of that of the static route; otherwise, a valid route may be considered invalid.
For more information about static route configuration, see Layer 3—IP Routing Configuration Guide.
To associate track with static routing:
Ste
p
Command Remarks
1. Enter system view.
system-view N/A
2. Associate the static route
with a track entry to
check the accessibility of
the next hop.
ip route-static dest-address { mask | mask-length }
next-hop-address track track-entry-number
[ preference preference-value ] [ description
description-text ]
Not configured by
default.
NOTE:
You can associate a nonexistent track entry with a static route. The association takes effect only after you
use the track command to create the track entry.
Displaying and maintaining track entries
Task Command Remarks
Display information about the
specified or all track entries.
display track { track-entry-number |
all } [ | { begin | exclude |
include } regular-expression ]
Available in any view
Track configuration examples
Static routing-track-NQA collaboration configuration example
Network requirements
As shown in Figure 29, Switch A, Switch B, Switch C, and Switch D are connected to two segments
20.1.1.0/24 and 30.1.1.0/24. Configure static routes on these switches so that the two segments can
communicate with each other, and configure route backup to improve reliability of the network.
Switch A is the default gateway of the hosts in segment 20.1.1.0/24. Two static routes to 30.1.1.0/24 exist
on Switch A, with the next hop being Switch B and Switch C, respectively. These two static routes back
up each other as follows:
• The static route with Switch B as the next hop has a higher priority, and is the master route. If this
route is available, Switch A forwards packets to 30.1.1.0/24 through Switch B.
• The static route with Switch C as the next hop acts as the backup route.
• Configure static routing-track-NQA collaboration to determine whether the master route is available
in real time. If the master route is unavailable, the backup route takes effect, and Switch A forwards
packets to 30.1.1.0/24 through Switch C.