Supported Platforms
Related Documentation
- ACX, J, M, MX, PTX, QFX, SRX, T Series
- Examples: Controlling Traffic with Metrics in a RIP Network50
metric-out (Protocols RIP)
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.
Description
Specify the metric value to add to routes transmitted to the neighbor. Use this statement to control how other routing devices prefer RIP routes sent from this neighbor.
If you have included the export statement, RIP exports routes it has learned to the neighbors configured by including the neighbor statement.
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 metric for a route can 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.
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, J, M, MX, PTX, QFX, SRX, T Series
- Examples: Controlling Traffic with Metrics in a RIP Network50
Published: 2013-08-15
Supported Platforms
Related Documentation
- ACX, J, M, MX, PTX, QFX, SRX, T Series
- Examples: Controlling Traffic with Metrics in a RIP Network50
