Specifying Static Route Options

In the defaults and route parts of the static statement, you can specify static-options, which define additional information about static routes that is included with the route when it is installed in the routing table. All static options are optional. Static options that you specify in the defaults part of the static statement are treated as global defaults and apply to all the static routes you configure in the static statement. Static options that you specify in the route part of the static statement override any global static options and apply to that destination only.

To configure static route options for IPv4 static routes, include one or more options in 
the defaults or route part of the static statement. Each of these options is explained in 
the sections that follow.

[edit]

routing-options {

    static {

        defaults {

            (active | passive); 

            as-path <as-path> <origin (egp | igp | incomplete)> <atomic-aggregate> 

                <aggregator as-number in-address>; 

            community [ community-ids ]; 

            (install | no-install); 

            metric metric <type type>; 

            (preference | preference2 | color | color2) preference <type type>; 

            (readvertise | no-readvertise); 

            (retain | no-retain); 

            tag string; 

        }

        rib-group group-name;

        route destination-prefix {

            (active | passive); 

            as-path <as-path> <origin (egp | igp | incomplete)> <atomic-aggregate> 

                <aggregator as-number in-address>; 

            community [ community-ids ]; 

            (install | no-install); 

            metric metric <type type>; 

            (preference | preference2 | color | color2) preference <type type>; 

            (readvertise | no-readvertise); 

            resolve;

            (retain | no-retain); 

            tag string; 

        }

    }

}

For a list of hierarchy levels at which you can configure this statement, see the statement summary section for this statement.

To configure static route options for IPv6 static routes, include one or more options in the defaults or route part of the static statement. Each of these options is explained in the sections that follow.

[edit routing-options]

rib inet6.0 {

    static {

        defaults {

            (active | passive); 

            as-path <as-path> <origin (egp | igp | incomplete)> <atomic-aggregate> 

                <aggregator as-number in-address>; 

            community [ community-ids ]; 

            (install | no-install); 

            metric metric <type type>; 

            (preference | preference2 | color | color2) preference <type type>; 

            (readvertise | no-readvertise); 

            resolve;

            (no-retain | retain); 

        }

        rib-group group-name;

        route destination-prefix {

            (active | passive); 

            as-path <as-path> <origin (egp | igp | incomplete)> <atomic-aggregate> 

                <aggregator as-number in-address>; 

            community [ community-ids ]; 

            (install | no-install); 

            metric metric <type type>; 

            (preference | preference2 | color | color2) preference <type type>; 

            (readvertise | no-readvertise); 

            resolve; 

            (retain | no-retain); 

        }

    }

}

For a list of hierarchy levels at which you can configure this statement, see the statement summary section for this statement.

The following sections explain how to specify static route options:

• Specifying the Route Metric
• Specifying the Route Preference
• Specifying Community Information
• Specifying the AS Path
• Specifying the OSPF Tag
• Specifying Whether a Route Is Installed in the Forwarding Table
• Specifying Whether the Route Is Permanently Installed in the Forwarding Table
• Specifying Whether Inactive Routes Are Removed from the Routing or Forwarding Table
• Specifying When the Route Can Be Readvertised
• Specifying When the Route Can Be Resolved to a Prefix That Is Not Directly Connected
• Configuring Bidirectional Forwarding Detection