3Com 3031 Command Reference Manual page 544

544 C 6: R P
HAPTER OUTING ROTOCOL
View
System view
Parameter
ip-address: Destination IP address, in dotted decimal notation.
mask: Mask.
mask-length: Mask length. Since "1" s in the 32-bit mask are required to be
consecutive, the mask in dotted decimal notation can be replaced by
mask-length, which is the number of the consecutive "1" s in the mask.
interface-name: Specifies the outbound interface name of the static route. The
interfaces of the public network or under other vpn-instances can be taken as
the outbound interface of the static route.
vpn-instance-name: Indicates a name of VPN instance. It can take a maximum
of 6 values.
vpn-nexthop-name: Specifies the vpn-instance of the static route next hop.
nexthop-address: Specifies the next hop IP address (in dotted decimal notation)
of the static route.
preference-value: Preference level of the static route in the range from 1 to
255.
reject: Indicates an unreachable route.
blackhole: Indicates a blackhole route.
Description
Using the ip route-static command, you can configure a static route. Using the
undo ip route-static command, you can cancel the configured static route.
Using the ip route-static vpn-instance command, you can configure a static route.
In the application of multi-role host, you can configure a static route on a private
network to specify the interface of another private network or public network as
its outbound interface. Using the undo ip route-static vpn-instance command, you
can remove the static route configuration.
By default, the system can obtain the sub-net route directly connected with the
router. When configuring a static route, the default preference is 60 if it is not
specified. If it is not specified as reject or blackhole, the route will be reachable by
default.
Precautions when configuring static route:
When the destination IP address and the mask are both 0.0.0.0, it is the default
route. If it is failed to detect the routing table, a packet will be forwarded along
the default route.
For different configuration of preference level, flexible routing management
policy can be adopted. For example, configure multiple routes to the same
destination. Load sharing can be fulfilled by specifying the same preference for
the routes. Route backup can be realized by specifying different preferences.
To configure static route, either transmission interface or next hop address can
be specified, which one is adopted in practice depends on actual condition. For
the interfaces supporting the resolution from network address to link layer
address or point-to-point interface, transmission interface or next hop address