rpm-tracking

Syntax

Hierarchy Level

Release Information

Support introduced in Junos OS Release 18.4 R1.

Support for multiple next hops added in Junos OS Release 19.1 R1.

Description

RPM static route tracking routes are coupled with a given RPM test instance. Routes can be installed or removed according to the results of the given RPM test. When installed, routes are automatically given a preference of 1, and so are preferred over static routes that may already exist with the same prefix.

If the RPM test result is “success,” then all the RPM-tracked routes that match the probe owner and test name of the successful test are added to the routing table. If the test result is “failure,” then all the RPM-tracked routes that match the probe owner and test name of the failed test are removed, if present, from the routing table.

RPM route tracking supports both IPv4 and IPv6 routes. RPM-tracked routes are configured individually; wildcards, ranges, and regular expressions are not supported.

Options

route—(Required) Must be a IPv4 or IPv6 destination prefix.

next-hop—(Required) Must be a IPv4 or IPv6 address. You can configure up to 16 multiple paths (next-hops) for any given RPM static route (RPM static routes with multiple next-hops can also be configured inside a routing instance).

metric—(Optional) The route with the lowest metric is active in routing table.

Default: 1

Range: 1 through 16.

rpm-probe—(Required) Must be a valid RPM probe owner from services rpm.

rpm-test—(Required) Must be a valid RPM test name from services rpm.

Required Privilege Level

interface—To view this statement in the configuration.

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