Extreme Networks BlackDiamond 6800 MPLS, Installation And User Manual

Page: 96 / 176

5-22 MPLS Module Installation and User Guide
Configuring RSVP-TE
The valid metric values range from 1 to 65535. Specifying the
igp-tracking
keyword
forces the route metric to track the underlying IGP metrics. If no IGP metric exists for
the LSP (for example, the LSP traverses a RIP network), the metric is ignored. Tracking
IGP metrics is the default behavior.
The
record
keyword is used to enable hop-by-hop path recording. The enabled
keyword causes the record route object (RRO) to be inserted into the path message. The
RRO is returned in the reserve message and contains a list of IPv4 subobjects that
describe the RSVP-TE path. Path recording by default is disabled. When disabled, no
RRO is inserted into the path message.
To delete an RSVP-TE path profile, use the following command:
config mpls rsvp-te delete profile [<profile_name> | all]
This command deletes a configured RSVP-TE profile with the specified profile name.
The default profile cannot be deleted. If a profile is associated with a configured LSP,
the profile cannot be deleted. If you specify the
all
keyword, all profiles not associated
with an LSP are deleted (except for the default profile).
Configuring an Existing RSVP-TE Profile
To configure an existing RSVP-TE profile, use the following command:
config mpls rsvp-te profile <profile_name> {bandwidth <bps>} {hop-count
<number>} {setup-priority <priority>} {hold-priority <priority>}
{retry-timeout <seconds>} {ping-interval <seconds>} {metric [<metric> |
igp-tracking]} {record [enabled | disabled]}
This command configures RSVP-TE attributes for the specified profile. The
<profile_name>
must have been previously added. All of the LSP profile values are
updated dynamically. For LSPs configured with this profile, the LSP parameters are
updated automatically with the sending of the next refresh path message. If the metric
is changed, all LSPs using this profile are rechecked against the calculated IGP metric.
In some cases, the LSP may be torn down because of a profile configuration change. For
example, if the bandwidth value is increased, the LSRs along the existing path may not
be able to accommodate the additional reserved bandwidth. In this scenario, the LSP is
torn down and resignaled.