28
track track-entry-number: Associates the static route with a track entry specified by its number in the
range of 1 to 1024. For more information about track, see High Availability Configuration Guide.
echo-packet: Specifies the BFD echo mode.
public: Indicates that the specified next hop address is on the public network.
interface-type interface-number: Specifies an output interface by its type and number. If the output
interface is an NBMA interface or broadcast interface (such as a VLAN interface), rather than a P2P
interface, the next hop address must be specified.
preference preference-value: Specifies a preference for the static route, in the range of 1 to 255. The
default is 60.
tag tag-value: Sets a tag value for marking the static route, in the range of 1 to 4294967295. The default
is 0. Tags of routes are used for route control in routing policies. For more information about routing
policies, see Layer 3—IP Routing Configuration Guide.
description description-text: Configures a description for the static route, which comprises 1 to 60
characters, including special characters like the space, but excluding the question mark (?).
Usage guidelines
If the destination IP address and the mask are both 0.0.0.0 (or 0), the configured route is a default route.
The default route is used for forwarding a packet matching no entry in the routing table.
Implement different routing policies to configure different route preferences. For example, to enable load
sharing for multiple routes to the same destination, assign the same preference to the routes; to enable
them to back up one another, assign different preferences to them.
Follow these guidelines when you specify the output interface or the next hop address of the static route:
• If the output interface is a Null 0 interface, no next hop address is required.
• If the output interface is a point-to-point interface (such as a PPP serial interface), you can specify
only the output interface. You do not need to change the configuration of the route even if the peer
address is changed.
• If the output interface is a broadcast interface (such as a VLAN interface) that might have multiple
next hops, you must specify the output interface and the next hop address at the same time.
Follow these guidelines when you configure a static route:
• Enabling BFD for a flapping route could worsen the situation. Therefore, use it with caution. For
more information about BFD, see High Availability Configuration Guide.
• If the track module uses NQA to detect the reachability of the private network static route's next hop,
the VPN instance ID of the static route's next hop must be identical to that configured for the NQA
operation.
• If a static route needs route recursion, the associated track entry must monitor the next hop of the
recursive route instead of that of the static route. Otherwise, a valid route might be mistakenly
considered invalid.
• Do not specify the permanent keyword together with the bfd or track keyword.
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.
<Sysname> system-view
[Sysname] ip route-static 1.1.1.1 24 2.2.2.2 tag 45 description for internet
To Next Page
Loading...
