[an error occurred while processing this directive][an error occurred while processing this directive]

static

Syntax

static {defaults {static-options;}rib-group group-name;route destination-prefix {bfd-liveness-detection {authentication {algorithm algorithm-name;key-chain key-chain-name;loose-check;}detection-time {threshold milliseconds;}local-address ip-address;minimum-interval milliseconds;minimum-receive-interval milliseconds;minimum-receive-ttl number;multiplier number;neighbor address;no-adaptation;transmit-interval {threshold milliseconds;minimum-interval milliseconds;}version (1 | automatic);}next-hop address;next-hop options;qualified-next-hop address {metric metric;preference preference;}static-options;}}

Hierarchy Level

[edit logical-systems logical-system-name routing-instances routing-instance-name routing-options],[edit logical-systems logical-system-name routing-options],[edit logical-systems logical-system-name routing-options rib routing-table-name],[edit routing-instances routing-instance-name routing-options],[edit routing-options],[edit routing-options rib routing-table-name]

Release Information

Statement introduced before JUNOS Release 7.4.

Statement introduced in JUNOS Release 9.0 for EX Series switches.

Support for BFD authentication introduced in JUNOS 9.6.

Support for BFD authentication introduced in JUNOS 9.6 for EX Series switches.

Description

Configure static routes to be installed in the routing table. You can specify any number of routes within a single static statement, and you can specify any number of static options in the configuration.

Options

defaults—Specify global static route options. These options only set default attributes inherited by all newly created static routes. These are treated as global defaults and apply to all the static routes you configure in the static statement. This part of the static statement is optional.

route destination-prefix—Destination of the static route.

  • defaults—For the default route to the destination. This is equivalent to specifying an IP address of 0.0.0.0/0.
  • destination-prefix/prefix-lengthdestination-prefix is the network portion of the IP address, and prefix-length is the destination prefix length.
  • next-hop address—Reach the next-hop routing device by specifying an IP address, an interface name, or an ISO network entity title (NET).
  • nsap-prefixnsap-prefix is the network service access point (NSAP) address for ISO.

next-hop options—Additional information for how to manage forwarding of packets to the next hop.

  • discard—Do not forward packets addressed to this destination. Instead, drop the packets, do not send ICMP unreachable messages to the packets’ originators, and install a reject route for this destination into the routing table.
  • iso-net—Reach the next-hop routing device by specifying an ISO NSAP.
  • next-table routing-table-name—Name of the next routing table to the destination.
  • receive—Install a receive route for this destination into the routing table.
  • reject—Do not forward packets addressed to this destination. Instead, drop the packets, send ICMP unreachable messages to the packets’ originators, and install a reject route for this destination into the routing table.

static-options—(Optional under route) Additional information about static routes, which is included with the route when it is installed in the routing table.

You can specify one or more of the following in static-options. Each of the options is explained separately.

  • as-path <as-path> <origin (egp | igp | incomplete)> <atomic-aggregate> <aggregator as-number in-address>;
  • community [ community-ids ];
  • (install | no-install);
  • (metric | metric2 | metric3 | metric4) value <type type>;
  • (preference | preference2 | color | color2) preference <type type>;
  • (readvertise | no-readvertise);
  • (resolve | no-resolve);
  • (no-retain | retain);
  • tag string;

The remaining statements are explained separately.

Required Privilege Level

routing—To view this statement in the configuration.

routing-control—To add this statement to the configuration.


Published: 2010-04-14

[an error occurred while processing this directive]