3Com SuperStack 4 Configuration Manual page 104

116 C 6: IP R
HAPTER OUTING
Configuring Static
Routes
P O
ROTOCOL PERATION
Static route configuration tasks are described in the following sections:
Configuring a Static Route
■
Configuring a Default Route
■
Deleting All The Static Routes
■
Displaying and Debugging Static Routes
■
Configuring a Static Route
Perform the following configurations in System View.
Table 108 Configuring a static route
Operation Command
Add a static route
ip route-static
interface_type interface_number
[ preference
Delete a static
undo ip route-static
route
} [
gateway_address
blackhole ]
The parameters are explained as follows:
IP address and mask
■
The IP address and mask use a decimal format. Because the 1s in the 32-bit
mask must be consecutive, the dotted decimal mask can also be replaced by
the mask-length which refers to the digits of the consecutive 1s in the mask.
Next hop address and NULL interface
■
When configuring a static route, you can specify the
decide the next hop address, depending on the actual conditions.
For all the routing items, the next hop address must be specified. When the IP
layer transmits a packet, it first searches the matching route in the routing
table, depending on the destination address of the packet. Only when the next
hop address of the route is specified can the link layer find the corresponding
link layer address, and then forward the packet.
The packets sent to the NULL interface, which is a virtual interface, are
discarded at once. This can decrease system load.
You cannot specify an interface address of the local Switch as the next hop
address of an static route.
Preference
■
For different configurations of
routing management policy.
Other parameters
■
The attributes
reject
blackhole route, respectively.
ip_address
value
] [ reject | blackhole ]
ip_address
interface_type interface_number
] [ preference
preference_value
and indicate the unreachable route and the
blackhole
mask mask_length
{ |
gateway_address
|
mask mask_length
{ |
|
value
] [ reject |
gateway_address
, you can flexibly apply the
} {
}
to