Configuring an RSVP-TE Profile

To configure an RSVP-TE profile, use the following command:
configure mpls rsvp-te profile profile_name {bandwidth [best-effort | [{committed-rate committed_bps [Kbps | Mbps | Gbps]} {max-burst-size burst_size [Kb | Mb]} {peak-rate peak_bps [Kbps | Mbps | Gbps]}]} {hold-priority hold_priority} {mtu [number | use-local-interface]} {path-computation [full | partial]} {record [enabled {route-only} | disabled]} {setup-priority setup_priority}

A profile is a set of attributes that are applied to the LSP when the LSP is configured using the create mpls rsvp-te lsp command. A default profile is provided which cannot be deleted, but can be applied to any configured LSP. The profile name for the default profile is default. The default profile parameter values are initially set to their respective default values. The maximum number of configurable profiles is 1000 (one of which is reserved for the default profile).

The bandwidth parameter specifies the desired reserved bandwidth for the LSP. Any positive integer value is valid. You must append the characters k for kilobits, m for megabits, or g for gigabits, to the bps value to specify the unit of measure. The default bandwidth bps value is zero, which indicates that the QoS (Quality of Service) for the LSP is best effort.

The max-burst-size and peak-rate parameters are signaled in the sender Tspec object and add further definition of the expected traffic. The mtu parameter is also signaled in the sender Tspec object and defines the expected maximum packet size that is sent over the LSP.

The setup-priority and hold-priority are optional parameters indicating the LSP priority. During path set up, if the requested bandwidth cannot be reserved through the LSR, the setup-priority parameter is compared to the hold-priority of existing LSPs to determine if any of the existing LSPs need to be preempted to allow a higher priority LSP to be established. Lower numerical values represent higher priorities. The setup-priority range is 0 to 7 and the default value is 7. The hold-priority range is also 0 to 7 and the default value is 0.

The path-computation keyword specifies computation strategy for calculating a path to the LSP destination. "full" requires the ingress node to full calculate a path to the LSP destination. "partial" allows the ingress node to calculate only part of the path to the LSP destination.
Note
Inter area RSVP fast reroute (FRR) is not supported.

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:
delete mpls rsvp-te 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).

Published March 2020prev | next

Email this topic

Print this page Print this page

Leave feedback Feedback