3Com S7906E Command Reference Manual page 698

description description-text: Configures a description for the static route, which consists of 1 to 60
characters, including special characters like space, but excluding ?.
track track-entry-number: Associates the static route with a track entry. Use the track-entry-number
argument to specify a track entry number, in the range 1 to 1024.
Description
Use the ip route-static command to configure a unicast static route.
Use the undo ip route-static command to delete a unicast static route.
When configuring a unicast static route, note that:
1) If the destination IP address and the mask are both 0.0.0.0, the configured route is a default route.
If routing table searching fails, the router will use the default route for packet forwarding.
2) Different route management policies can be implemented for different route preference
configurations. For example, specifying the same preference for different routes to the same
destination address enables load sharing, while specifying different preferences for these routes
enables route backup.
Related commands: display ip routing-table, ip route-static default-preference.
The static route does not take effect if you specify its next hop address first and then configure the
address as the IP address of a local interface.
The next hop address must not be the IP address of the local interface; otherwise, the route
configuration will not take effect.
For a NULL0 interface, if the output interface has already been configured, there is no need to
configure the next hop address.
To configure track monitoring 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.
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.
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.
Examples
# Configure a static route, whose destination address is 1.1.1.1/24, next hop address is 2.2.2.2, tag
value is 45, and description information is for internet & intranet.
<Sysname> system-view
[Sysname] ip route-static 1.1.1.1 24 2.2.2.2 tag 45 description for internet & intranet
# Configure a static route for a VPN instance named vpn1: the destination address is 1.1.1.1/16 and the
next hop address is 1.1.1.2, which is the address of this VPN instance.
<Sysname> system-view
1-3