rsvp
Syntax
rsvp {
associated-bidirectional-lspsingle-sided-provisioning;
authentication-key (Protocols RSVP) authentication-key;
cross-credibility-cspf;
(disable | enable);
expand-flood-reflector-hop;
fast-rerouteoptimize-timer seconds;
graceful-deletion-timeout seconds;
graceful-restart (Protocols RSVP) <(disable | enable)> <helper-disable> <maximum-helper-recovery-time seconds> <maximum-helper-restart-time seconds>;
hello-acknowledgements;
interface (Protocols RSVP) name {
authentication-key authentication-key;
bandwidth (Protocols RSVP) bandwidth;
(disable | enable);
hello-interval (Protocols RSVP) seconds;
link-protection (RSVP) {
admin-groupinclude-any [include-any ...] include-all [include-all ...] exclude [exclude ...];
bandwidth <ct0 bps> <ct1 bps> <ct2 bps> <ct3 bps> <per-traffic-class-bandwidth>;
bypass (Signaled LSP) bypass name {
admin-groupinclude-any [include-any ...] include-all [include-all ...] exclude [exclude ...];
bandwidth <ct0 bps> <ct1 bps> <ct2 bps> <ct3 bps> <per-traffic-class-bandwidth>;
class-of-service (Protocols RSVP) class-of-service;
description description;
exclude-srlg;
hop-limit hop-limit;
no-cspf;
path (Protocols RSVP) name;
priority (Protocols RSVP) {
reservation-priority;
setup-priority;
}
subscription <subscription>;
to to;
}
class-of-service class-of-service;
(disable | enable);
exclude-srlg;
hop-limit hop-limit;
max-bypasses max-bypasses;
no-cspf (Protocols RSVP);
no-node-protection;
optimize-timer (Protocols RSVP) seconds;
path (Protocols RSVP) name;
priority (Protocols RSVP) {
reservation-priority;
setup-priority;
}
subscription subscription;
}
non-rsvp-bandwdith {
local-bw-override-threshold;
}
(reliable | no-reliable);
subscription <ct0 ct0> <ct1 ct1> <ct2 ct2> <ct3 ct3> <link-subscription> priority-value percent percent;
update-threshold <adaptive name threshold-percent percent threshold-value threshold-value> <threshold-percent> <threshold-value threshold-value>;
update-threshold-max-reservable {
bandwidth;
percent percent;
}
}
keep-multiplier keep-multiplier;
load-balancebandwidth;
local-reversion;
lsp-set name {
(disable | enable);
match-criteria(egress | ingress | transit);
traceoptions {
file filename <files files> <size size> <(world-readable | no-world-readable)>;
flag (all | enhanced-frr | error | event | io-event | io-packets | lmp | lsp-prefix | nsr-synchronization | packets | path | pathtear | resv | resvtear | route | state) {
detail;
disable;
receive;
send;
}
}
}
no-authentication-check (Protocols RSVP);
node-hello <hello-interval seconds>;
no-enhanced-frr-bypass (Protocols RSVP);
no-hello-acknowledgements;
no-interface-hello;
no-local-reversion;
no-node-hello;
no-node-hello-on-bypass;
no-node-id-subobject;
no-p2mp-re-merge;
no-p2mp-sublsp;
peer-interface (Protocols RSVP) name {
authentication-key authentication-key;
dynamic-bidirectional-transport <template template>;
(disable | enable);
hello-interval (Protocols RSVP) seconds;
(reliable | no-reliable);
}
pop-and-forward (Protocols RSVP) <application-labeldepth depth>;
preemption (aggressive | disabled | normal);
refresh-time refresh-time;
rfc6510-lsp-attributes;
setup-protection;
traceoptions (Protocols RSVP) {
file filename <files files> <size size> <(world-readable | no-world-readable)>;
flag (all | enhanced-frr | error | event | io-event | io-packets | lmp | lsp-prefix | nsr-synchronization | packets | path | pathtear | resv | resvtear | route | state) {
detail;
disable;
receive;
send;
}
}
tunnel-services (RSVP) {
devices [devices ...];
}
}Hierarchy Level
[edit logical-systems name protocols], [edit logical-systems name routing-instances name protocols], [edit logical-systems name tenants name routing-instances name protocols], [edit protocols], [edit routing-instances name protocols], [edit tenants name routing-instances name protocols]
Description
Enable Resource Reservation Protocol (RSVP) signaling.
You must include the rsvp statement in the configuration
to enable RSVP on the router.
The primary purpose of RSVP in Junos OS for EX Series switches is to support dynamic signaling within label switched paths (LSPs).
Options
cross-credibility-cspf—Enable path computation across credibility levels.
The constraint path computation is run across multi-protocol links and nodes, instead of a
credibility-by-credibility basis.
authentication key—Authentication key. Neighboring routers use the
password to verify the authenticity of packets sent from this interface or peer interface.
It is recommended to use the authentication-key configuration at the
[edit protocols rsvp] hierarchy level for the RSVP node-neighbor.
graceful deletion timeout—Specify the time, in seconds, before completing
graceful deletion of signaling.
graceful restart—Configure graceful restart on the
router. You must configure the graceful-restart statement at the
[edit routing-options] hierarchy level to enable graceful restart on the
router.
hello acknowledgements—Enable hello messages from nonsession neighbors to
be acknowledged with a hello acknowledgment message. Once hello
acknowledgments are enabled, the router continues to acknowledge hello messages
from any nonsession RSVP neighbors unless the interface itself goes down or the
configuration is changed by an administrator.
interface—Enable RSVP on one or more router interfaces.
bandwidth—Enables you to specify the actual available bandwidth.
hello interval—Enable the sending of hello packets on the interface.
link protection—Using link protection, you can configure a network to
reroute traffic quickly around broken links.
priority—Configure the setup priority and reservation priority for a
bypass LSP.
exclude-srlg—Exclude Shared Risk Link Group (SRLG) links for the secondary
path for critical links where it is imperative to keep the secondary and primary
label-switched paths completely disjoint from any common SRLG.
hop-limit—Specify the maximum number of routers that an LSP can traverse.
Maximum number of hops.
bypass—Enables you to configure specific bandwidth and path constraints
for a bypass LSP.
max bypasses—Specify the maximum number of dynamic bypass LSPs permitted
for protecting this interface.
no cspf—Disable CSPF computation on all bypass LSPs or on a specific
bypass LSP. You need to disable CSPF for link protection to function properly on interarea
paths.
optimize-timer—The optimize timer initiates a periodic optimization process
that reshuffles data LSPs among bypass LSPs to achieve the most efficient use of network
resources.
path—Configure an explicit path (a sequence of strict or loose routes) to
control where and how a bypass LSP is established.
update threshold—Adjust the threshold at which a change in bandwidth
triggers an interior gateway protocol (IGP) update.
keep multiplier—Indicates the number of messages that can be lost before a
particular state is declared stale and must be deleted. The keep multiplier directly affects
the lifetime of an RSVP state.
no authentication check—Skip authentication check for received
messages.
node hello—Enable node-ID based RSVP hellos globally on all of the RSVP
interfaces on the router to allow Juniper Networks routers to interoperate with the
equipment of other vendors.
peer interface—Configure the name of the LMP peer device.
no-enhanced-frr-bypass—Enable no-enhanced-frr-bypass to
turn off all Fast reroute (FRR) facility protection enhancements, which includes improved
LSP scaling and enhanced RSVP message handling, and reduce the default refresh time to 30
seconds.
no-interface-hello—Explicitly disable RSVP interface hellos globally on
the router.
no-local-reversion—Disable RSVP local revertive mode as specified in RFC
4090, Fast Reroute Extensions to RSVP-TE for LSP Tunnels.
no-node-hello-on-bypass—Starting with Junos release 16.1, Junos routers
send RSVP hello packets over a bypass LSP (when one is present), instead of the IGP next
hop. To return to the original behavior specify the no-node-hello-on-bypass
option.
no-node-id-subobject—Disable the record route object (RRO) node-ID
subobject for compatibility with earlier versions of Junos OS.
pop-and-forward—Specify RSVP pop-and-forward LSP tunnel-specific global
parameters.
refresh time—Periodical refresh timer expressed in seconds.
setup-protection—The facility-backup fast reroute mechanism can provide
setup protection for LSPs which are in the process of being signaled.
traceoptions—The default RSVP-level trace options are those inherited from
the routing protocols traceoptions statement included at the [edit
routing-options] hierarchy level.
tunnel services—The Junos OS selects one of the available virtual tunnel
(VT) interfaces to de-encapsulate the egress traffic.
Default
RSVP is disabled.
Required Privilege Level
routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Release Information
Statement introduced before Junos OS Release 7.4.