Specifying the Next Hop of the Static Route

When you configure an individual static route in the route part of the static statement, specify how to reach the destination (in next-hop) in one of the following ways:

• next-hop address—IPv4 or IPv6 address of the next hop to the destination, specified as:
  • IPv4 or IPv6 address of the next hop
  • Interface name (for point-to-point interfaces only)
  • address or interface-name to specify an IP address of a multipoint interface or an interface name of a point-to-point interface.

    Note: If an interface becomes unavailable, all configured static routes on that interface are withdrawn from the routing table.

• next-table routing-table-name—Name of the next routing table to the destination.

  Note: Within a routing instance, you cannot configure a static route with the next-table inet.0 statement if any static route in the main routing instance is already configured with the next-table statement to point to the inet.0 routing table of the routing instance. For example, if you configure on the main routing instance a static route 192.168.88.88/32 with next-table test.inet.0 and the routing instance test is also configured with a static route 192.168.88.88/32 next-table inet.0, the configuration commit fails. Instead, you must configure a rib group both on the main instance and on the routing instance, which enables you to install the static route into both routing tables. For more information, see Installing a Static Route into More than One Routing Table.

• reject—Do not forward packets addressed to this destination. Instead, drop the packets, send ICMP (or ICMPv6) unreachable messages to the packets’ originators, and install a reject route for this destination into the routing table.
• discard—Do not forward packets addressed to this destination. Instead, drop the packets, do not send ICMP (or ICMPv6) unreachable messages to the packets’ originators, and install a reject route for this destination into the routing table.
• receive—Cause packets to the destination to be received by the local router.

Copyright © 2008, Juniper Networks, Inc. All rights reserved. Trademark Notice.