2-2
ip route-static
Syntax
ip
route-static
dest-address
{
mask
|
mask-length
} {
next-hop-address
[
track track-entry-number
] |
interface-type
interface-number next-hop-address
] } [
preference
preference-value
] [
tag
tag-value
]
[
description
description-text
]
undo
ip
route-static
dest-address
{
mask
|
mask-length
} [
next-hop-address
|
interface-type
interface-number
[
next-hop-address
] ] [
preference
preference-value
]
View
System view
Default Level
2: System level
Parameters
dest-address
: Destination IP address of the static route, in dotted decimal notation.
mask
: Mast of the IP address, in dotted decimal notation.
mask-length
: Mask length, in the range 0 to 32.
next-hop-address
: IP address of the next hop, in dotted decimal notation.
interface-type interface-number
: Specifies the output interface by its type and number.
preference
preference-value
: Specifies the preference of the static route, which is in the range of 1 to
255 and defaults to 60.
tag
tag-value
: Sets a tag value for the static route from 1 to 4294967295. The default is 0. Tags of
routes are used in routing policies to control routing.
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.
3) When configuring a static route, Note that the next hop address must not be the IP address of the
local interface; otherwise, the route configuration will not take effect. When specifying the output
interface, note that: for a Null 0 or loopback interface, if the output interface has already been
configured, there is no need to configure the next hop address.
Summary of Contents for E4510-48G
Page 109: ...2 18 Sysname interface bridge aggregation 1 Sysname Bridge Aggregation1 shutdown ...
Page 309: ...6 4 Sysname interface vlan interface 1 Sysname Vlan interface1 ip address dhcp alloc ...
Page 324: ...8 3 Sysname interface vlan interface 1 Sysname Vlan interface1 ip address bootp alloc ...
Page 530: ...2 5 Sysname mvlan 100 subvlan 10 to 15 ...
Page 739: ...8 15 Sysname system view Sysname port security trap addresslearned ...
Page 819: ...13 11 Sysname system view Sysname public key peer key2 import sshkey key pub ...
Page 914: ...5 17 Sysname reset oam ...
Page 1064: ...5 30 Slot 2 Set next configuration file successfully ...
Page 1325: ...21 13 Examples Redirect to member 2 Sysname irf switch to 2 Sysname Slave 2 ...
