no-local-reversion
Syntax
local-reversion; no-local-reversion;
Hierarchy Level
[edit logical-systems logical-system-name protocols rsvp], [edit protocols rsvp]
Description
Disable RSVP local revertive mode as specified in RFC 4090, Fast Reroute Extensions to RSVP-TE for LSP Tunnels.
For Junos OS Release 16.1 running on MX Series or PTX
Series routers, no-local-reversion is enabled by default,
that is, local reversion is not running, and the statement has been
deprecated. To enable local reversion, use the local-reversion statement.
RSVP local revertive mode is supported on all Juniper Networks routers running Junos OS. It is the default behavior. If you include this statement, the Juniper Networks router uses global revertive mode instead. You might need to disable RSVP local revertive mode on Juniper Networks routers if your network includes equipment that does not support this mode.
The following information can also be found in RFC 4090. Refer to the RFC for additional information. When an LSP fails, the connection can be repaired locally using a traffic protection mechanism such as fast reroute. To restore the LSP to a full working path, RFC 4090 specifies the following strategies:
Local revertive mode—Upon detecting that the path is restored, the point of local repair (PLR) resignals each of the LSPs that were formerly routed over the restored path. Every LSP successfully resignaled along the restored path is switched back.
Global revertive mode—The ingress router of each tunnel is responsible for reoptimizing the LSPs that used the failed path. There are several potential reoptimization triggers: RSVP error messages, inspection of OSPF LSAs or IS-IS LSPs, and timers. This re-optimization process can proceed as soon as the failure is detected. It is not tied to the restoration of the failed path.
Required Privilege Level
routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Release Information
Statement introduced in Junos OS Release 10.4.