1-3
Configuration Procedure
Follow these steps to configure a static route:
To do…
Use the command…
Remarks
Enter system view
system-view
—
Configure a static
route
ip route-static dest-address
{
mask
|
mask-length
}
{
next-hop-address | interface-type interface-number
next-hop-address
} [
preference
preference-value
]
[
tag tag-value
] [
description description-text
]
Required
By default,
preference
for
static routes is 60,
tag
is 0, and no
description
information is
configured.
Configure the default
preference for static
routes
ip route-static default-preference
default-preference-value
Optional
60 by default
z
When configuring a static route, the static route does not take effect if you specify the next hop
address first and then configure it as the IP address of a local interface.
z
If you do not specify the preference when configuring a static route, the default preference will be
used. Reconfiguring the default preference applies only to newly created static routes.
z
You can flexibly control static routes by configuring tag values and using the tag values in the
routing policy.
z
If the destination IP address and mask are both configured as 0.0.0.0 with the
ip route-static
command, the route is the default route.
Detecting Reachability of the Static Route’s Nexthop
If a static route fails due to a topology change or a fault, the connection will be interrupted. To improve
network stability, the system needs to detect reachability of the static route’s next hop and switch to a
backup route once the next hop is unreachable.
Following method can be used to detect reachability of the static route’s next hop.
Detecting Nexthop Reachability Through Track
If you specify the nexthop but not outgoing interface when configuring a static route, you can associate
the static route with a track entry to check the static route validity:
z
When the track entry is positive, the static route's nexthop is reachable and the static route takes
effect.
z
When the track entry is negative, the static route's nexthop is unreachable and the static route is
invalid. For details about track, refer to
Track Configuration
in the
High Availability Volume
.
Summary of Contents for S5500-SI Series
Page 161: ...3 10 GigabitEthernet1 0 1 2 MANUAL...
Page 220: ...1 7 Clearing ARP entries from the ARP table may cause communication failures...
Page 331: ...1 7 1 1 ms 1 ms 1 ms 1 1 6 1 2 1 ms 1 ms 1 ms 1 1 4 1 3 1 ms 1 ms 1 ms 1 1 2 2 Trace complete...
Page 493: ...2 8...
Page 1111: ...1 10 Installing patches Installation completed and patches will continue to run after reboot...