H3C LS-3100-52P-OVS-H3 Operation Manual - page 508
1-5
Configuration procedure
Follow these steps to detect the reachability of a static route's nexthop through Track:
To do…
Use the command…
Remarks
Enter system view
system-view
—
ip route-static dest-address { mask | mask-length}
{next-hop-address | vpn-instance d-vpn-instance-name
next-hop-address } track track-entry-number
[ preference preference-value ] [ tag tag-value ]
[ description description-text]
Associate the static
route with a track entry
ip route-staticvpn-instance
s-vpn-instance-name&<1-6> dest-address { mask |
mask-length } { next-hop-address track
track-entry-number[ public ] | vpn-instance
d-vpn-instance-namenext-hop-address track
track-entry-number} [ preference preference-value ]
[ tag tag-value ] [ description description-text]
Required
Not
configured by
default
z
To configure this feature for an existing static route, simply associate the static route with a track
entry. For a non-existent static route, configure it and associate it with a Track entry.
z
If the track module uses NQA to detect the reachability of the private network static route's nexthop,
the VPN instance number of the static route's nexthop must be identical to that configured in the
NQA test group.
z
If a static route needs route recursion, the associated track entry must monitor the nexthop of the
recursive route instead of that of the static route; otherwise, a valid route may be mistakenly
considered invalid.
Displaying and Maintaining Static Routes
To do…
Use the command…
Remarks
Display the current
configuration information
display current-configuration
Display the brief information of
the IP routing table
display ip routing-table
Display the detailed
information of the IP routing
table
display ip routing-table verbose
View information of static
routes
display ip routing-table protocol static
[ inactive | verbose ]
Available in any
view
Delete all the static routes
delete [ vpn-instance vpn-instance-name ]
static-routes all
Available In
system view