Rsvp-Te Global Tasks - Juniper JUNOSE SOFTWARE FOR E SERIES 11.0.X - BGP AND MPLS CONFIGURATION GUIDE 2009-12-30 Configuration Manual

JUNOSe 11.0.x BGP and MPLS Configuration Guide

RSVP-TE Global Tasks

Typically, you do not configure anything for RSVP-TE at the global level, but you can
perform the following optional tasks.
1.
2.
3.
4.
5.
6.
NOTE: Low timer values lead to frequent reoptimization of LSPs, which is undesirable
for the following reasons:
268
RSVP-TE Global Tasks
(Optional) Enable RSVP-TE. Any RSVP-TE–related command creates RSVP-TE
implicitly, negating the need to issue this command.
host1(config)#mpls rsvp
(Optional) Configure a global RSVP-TE profile that specifies the timeout period
in milliseconds between generation of RSVP refresh messages, the number of
refresh messages that can be lost before the PATH or RESV state is ended, or
both.
host1(config)#mpls rsvp interface profile rsvp4
host1(config-rsvp)#refresh-period 60000
host1(config-rsvp)#cleanup-timeout-factor 9
(Optional) Configure retry timer options globally (to apply to all tunnels) to set
up an LSP after a setup failure (a failure other than one due to no available route).
Specify the number of attempts to be made to set up an RSVP-TE tunnel or the
interval in seconds between attempts.
host1(config)#mpls lsp retries 35
host1(config)#mpls lsp retry-time 55
(Optional) Configure retry timer options globally (to apply to all tunnels) to set
up an LSP after a failure due to no available route. Specify the number of attempts
to be made to set up an RSVP-TE tunnel or the interval in seconds between
attempts.
host1(config)#mpls lsp no-route retries 3200
host1(config)#mpls lsp no-route retry-time 45
(Optional) Configure the interval at which the bandwidth values are flooded.
host1(config)#mpls traffic-eng link-management timers periodic-flooding 10
(Optional) Configure reoptimization the frequency at which MPLS searches for
better paths for existing tunnels.
Frequent changes to the LSPs increases packet loss.
Frequent reoptimization increases the load on the router, especially when the
router acts as the LSP head end. The load is particularly noticeable in a scaled
network, resulting in high CPU utilization on the router.
host1(config)#mpls reoptimize timers frequency 180