R2511-HP MSR Router Series Layer 3 - IP Routing Command Reference(V5)

31
description description-text: Configures a description for the static route, which consists of 1 to 60
characters, including special characters like space, but excluding the question mark (?).
bfd: Enables the bidirectional forwarding detection (BFD) function to detect reachability of the static
route's next hop. Once the next hop is unreachable, the system will switch to a backup route.
control-packet: Implements BFD in the control packet mode.
echo-packet: Implements BFD in the echo packet mode.
bfd-source ip-address: Specifies the source address of BFD packets. HP recommends configuring
loopback interface address.
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 of 1 to 1024. For more information about Track,
see High Availability Configuration Guide.
Usage guidelines
When you configure a unicast static route, follow these 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 packets that match no specific entry in the routing
table.
• Implement different routing policies by tuning route preference. For example, to enable multiple
routes to the same destination address to share load, assign the same preference to the routes. To
enable them to back up one another, assign different preferences to them.
• Specify the outgoing interface or the next hop address of the static route as needed. The next hop
address cannot be the IP address of a local interface.
{ If the outgoing interface is a Null 0 interface, no next hop address is required.
{ If the outgoing interface is a point-to-point interface, a PPP serial interface for example, you can
specify only the outgoing interface. You do not need to change the configuration of the route
even if the peer address is changed.
{ If the outgoing interface is an NBMA interface or point-to-multipoint (P2MP) interface, an X.25
or Frame Relay interface for example, HP recommends specifying both the outgoing interface
and the next hop address for the route. This is because such interfaces need IP address-to-link
layer address mappings for successful packet delivery.
{ If the outgoing interface is a broadcast interface, an Ethernet interface or a VLAN interface for
example, specify the corresponding next hop of the interface at the same time. This is because
such interfaces can have multiple next hops.
The next hop address of a static route cannot be the IP address of a local interface.
Enabling BFD for a flapping route could worsen the situation. Be cautious when using BFD. 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 number of the static route's next hop must be identical to that configured in the NQA test
group.
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.