Configuring Group-Specific RIP Properties

You can group together neighbors that share the same export policy and export metric defaults. You configure group-specific RIP properties by including the group statement at the [edit protocols rip] hierarchy level. Each group must contain at least one neighbor. You should create a group for every export policy you have. To configure neighbors, see Overview of RIP Neighbor Properties.

This section discusses the following tasks:

• Applying Policies to Routes Exported by RIP
• Configuring the Default Preference Value for RIP
• Configuring the Metric for Routes Exported by RIP

Applying Policies to Routes Exported by RIP

By default, RIP does not export routes it has learned to its neighbors. To enable RIP to export routes, apply one or more export policies. To apply export policies and to filter routes being exported from the local routing device to its neighbors, include the export statement and list the name of the policy to be evaluated:

To configure export policy globally for all RIP neighbors, include the export statement.

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

You can define one or more export policies. If no routes match the policies, the local routing device does not export any routes to its neighbors. Export policies override any metric values determined through calculations involving the values configured with the metric-in and metric-out statements (discussed in Configuring the Metric Value Added to Imported RIP Routes and Configuring Group-Specific RIP Properties, respectively).

Note: The export policy on RIP does not support manipulating routing information of the next hop.

For more information about creating policies, see the Junos Policy Framework Configuration Guide.

Configuring the Default Preference Value for RIP

By default, the Junos OS assigns a preference of 100 to routes that originate from RIP. When the Junos OS determines a route’s preference to become the active route, the software selects the route with the lowest preference and installs this route into the forwarding table. (For more information about preferences, see Route Preferences Overview.)

To modify the default RIP preference value, include the preference statement:

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

preference can be a value from 0 through 4,294,967,295 (2³² – 1).

Configuring the Metric for Routes Exported by RIP

If you have included the export statement, RIP exports routes it has learned to the neighbors configured by including the neighbor statement. For more information about those statements, seeConfiguring Group-Specific RIP Properties.

The metric associated with a RIP route (unless modified by an export policy) is the normal RIP metric. For example, a RIP route with a metric of 5 learned from a neighbor configured with a metric-in value of 2 is advertised with a combined metric of 7 when advertised to RIP neighbors in the same group. However, if this route was learned from a RIP neighbor in a different group or from a different protocol, the route is advertised with the metric value configured for that group with the metric-out statement. The default value for the metric-out statement is 1.

The metric for a route may be modified with an export policy. That metric is seen when the route is exported to the next hop.

To increase the metric for routes advertised outside a group, include the metric-out statement:

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