R3721-F3210-F3171-HP High-End Firewalls Network Management Command Reference-6PW101

248
control-packet: Implements BFD in the control packet mode.
bfd-source ip-address: Specifies the source address of BFD packets. HP recommends that you configure
loopback interface address.
echo-packet: Implements BFD in the echo packet mode.
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.
Description
Use ip route-static to configure a unicast static route.
Use undo ip route-static to delete a unicast static route.
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 will be used for forwarding a packet if no route is available for the packet
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 for the routes; to
enable them to back up one another, assign different preferences for 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; otherwise, the route configuration will not
take effect. If the outgoing interface supports network address-to-link layer address resolution or is
a point-to-point interface, you may specify only the interface or the next hop address.
{ 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 interface for example, you may
specify only the outgoing interface rather than the peer address or both the outgoing interface
and peer address. As only the outgoing interface is specified, there is no need to change the
configuration of the route even if the peer address is changed.
{ If the outgoing interface is an NBMA and P2MP interface, HP recommends specifying both the
interface and the next hop address for the route. This is because such interfaces support
point-to-multipoint networks; for them the router must establish IP address-to-link layer address
mappings for successful packet delivery.
{ HP does not recommend specifying a broadcast interface (such as an Ethernet interface or a
VLAN interface) as the outgoing interface for a static route, because a broadcast interface may
have multiple next hops. If you have to do so, you must specify the corresponding next hop of
the interface at the same time.
{ To implement BFD with the control-packet mode, the remote end must create a BFD session;
otherwise the BFD function cannot work. To implement BFD with the echo-packet mode, the
BFD function can work even if the remote end does not create any BFD session.
{ To configure a static route and enable BFD control packet mode for it, specify an outbound
interface and a direct next hop, or specify an indirect next hop and a specific BFD packet
source address for the static route.
Related commands: ip route-static default-preference and display ip routing-table.
The next hop address of a static route cannot be the IP address of a local interface (such as an Ethernet
interface and VLAN interface). Otherwise, the static route does not take effect.
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.