Supported Platforms
Related Documentation
- ACX, M, MX, PTX, T Series
- Example: Configuring the Metric Value Added to Imported RIPng Routes
metric-out (Protocols RIPng)
Syntax
Hierarchy Level
Release Information
Statement introduced before Junos OS Release 7.4.
Statement introduced in Junos OS Release 9.0 for EX Series switches.
Support for routing instances introduced in Junos OS Release 9.0.
Description
Specify the metric value to add to routes transmitted to the neighbor. Use this statement to control how other routing devices prefer RIPng routes sent from this neighbor.
When an export policy is configured, RIPng exports all learned routes to neighbors configured with the neighbor statement.
If a route being exported was learned from a member of the same RIPng group, the metric associated with that route (unless modified by an export policy) is the normal RIPng metric. For example, a RIPng 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 RIPng neighbors in the same group. However, if this route was learned from a RIPng 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 metric-out is 1.
To modify the metric for routes advertised outside a group, include the metric-out statement.
Options
metric—Metric value.
Range: 1 through 16
Default: 1
Required Privilege Level
routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related Documentation
- ACX, M, MX, PTX, T Series
- Example: Configuring the Metric Value Added to Imported RIPng Routes
Published: 2012-12-08
Supported Platforms
Related Documentation
- ACX, M, MX, PTX, T Series
- Example: Configuring the Metric Value Added to Imported RIPng Routes
