HP VPN Firewall Appliances Network Management Command Reference

273
permanent: Specifies the route as a permanent static route. If the output interface is down, the permanent
static route is still active.
description description-text: Configures a description for the static route, which comprises 1 to 60
characters, including special characters like space, but excluding question marks (?).
bfd: Enables BFD to detect reachability of the static route's next hop. Once the next hop is unreachable,
the system immediately switches to a backup route. Support for this keyword varies by device model.
control-packet: Implements BFD control mode.
echo-packet: Implements BFD echo mode.
bfd-source ip-address: Specifies the source address of BFD packets. HP recommends that you configure
loopback interface address.
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.
multiple-topology topology-name: Specifies a topology by its name, a case-sensitive string of 1 to 31
characters.
The following matrix shows the keywords bfd, control-packet, bfd-source, and echo-packet and
hardware compatibility:
Hardware Com
p
atibilit
y
F1000-A-EI/F1000-S-EI No
F1000-E No
F5000 Yes
F5000-S/F5000-C No
VPN firewall modules No
20-Gbps VPN firewall modules No
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 to tune 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.
• Specify the output interface or the next hop address of the static route as needed:
{ 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 an Ethernet interface or a VLAN interface)
that might have multiple next hops, you must specify both the output interface and the next hop
address at the same time.
• The next hop address of a static route cannot be the IP address of a local interface. Otherwise, the
static does not take effect.