Reserving bandwidth for RSVP-TE LSPs
Specify the bandwidth for the RSVP-TE LSP to ensure the LSP meets desired traffic requirements.
Procedure steps
Step Action
1 To enter the configuration mode, enter:
configure terminal 2 To select the LSP, enter:
mpls traffic-eng-lsp <LSP-name>
3 To specify RSVP-TE LSP bandwidth, enter:
[no] [primary|secondary] {bandwidth <bandwidth>
[k|m|g]}
--End--Table 52
Variable definitions
Variable Value
[no] Removes the specified configuration.
primary Specifies the primary LSP.
Configuring constrained path LSP properties 93
Table 52
Variable definitions (cont’d.)
Variable Value
secondary Specifies the secondary LSP.
{bandwidth
<bandwidth> [k|m|g]}
1000 - 10000000000 bits. You can also specify the bandwidth in terms of kilobits (k) megabits (m) or gigabits (g). For example, for 1 megabit, enter 1m
Configuring the filter style for RSVP-TE LSP
Configure the filter to fixed or shared filter style for RSVP-TE LSP. Use the fixed filter style to prevent rerouting of an LSP and to prevent other LSPs from using the bandwidth reserved for this LSP.
Procedure steps
Step Action
1 To enter the configuration mode, enter:
configure terminal 2 To select the LSP, enter:
mpls traffic-eng-lsp <LSP-name>
3 To configure the filter style, enter:
[no] {primary | secondary}
filter {fixed | shared-explicit}
--End--Table 53
Variable definitions
Variable Value
primary Specifies the primary LSP.
secondary Specifies the secondary LSP.
fixed Specifies a distinct reservation. A distinct reservation request is created for data packets from this LSP.
shared-explicit Specifies a shared reservation environment. It creates a single reservation into which flows from all LSPs are combined.
Configuring retry limit for RSVP-TE LSP
If a session is in a nonexistent state due to the receipt of a Path Error message, it tries to recreate the LSP for the number of times specified by
94 RSVP-TE LSP configuration
Although the same retry command controls both the MPLS traffic engineering tunnel and the session, the retry-limit value affects only the session and not the traffic-engineering tunnel. If the traffic tunnel is in an incomplete state, the code keeps trying forever to bring it to a complete state, irrespective of the retry-limit value.
Procedure steps
Step Action
1 To enter the configuration mode, enter:
configure terminal 2 To select the LSP, enter:
mpls traffic-eng-lsp <LSP-name>
3 To configure retry limit, enter:
[no] {primary | secondary} retry-limit <1-65535>
--End--Table 54
Variable definitions
Variable Value
primary Specifies the primary LSP.
secondary Specifies the secondary LSP.
<1-65535> The number of times the system tries to set up the LSP. Default is 0 (indefinite).
Configuring retry timer for RSVP-TE LSP
Specify a retry interval for an RSVP-TE LSP. Use the no parameter to revert to the default.
Procedure steps
Step Action
1 To enter the configuration mode, enter:
configure terminal 2 To select the LSP, enter:
mpls traffic-eng-lsp <LSP-name>
3 To configure the retry timer, enter:
Configuring constrained path LSP properties 95
[no] {primary | secondary} retry-timer <1-600>
--End--Table 55
Variable definitions
Variable Value
[no] Reverts to the default value (30 seconds).
primary Specifies the primary LSP.
secondary Specifies the secondary LSP.
<1-600> Time, in seconds, that the system waits before retrying LSP setup.
Configuring setup priority for RSVP-TE LSP
Configure the setup priority to determine whether a new LSP can preempt an existing LSP. The setup priority of the new LSP must be higher than the hold priority of an existing LSP for the existing LSP to be preempted.
For RSVP-TE LSP, do not configure the setup priority to be higher than the hold priority.
Procedure steps
Step Action
1 To enter the configuration mode, enter:
configure terminal 2 To select the LSP, enter:
mpls traffic-eng-lsp <LSP-name>
3 To configure the setup priority for RSVP-TE LSP, enter:
[no] {primary | secondary} setup-priority <0-7>
--End--Table 56
Variable definitions
Variable Value
[no] Sets the setup priority to the default value:
7 (lowest).
primary Specifies the primary LSP.
96 RSVP-TE LSP configuration
Table 56
Variable definitions (cont’d.)
Variable Value
secondary Specifies the secondary LSP.
<0-7> Specifies the setup priority, from highest priority (0) to lowest priority (7)
Configuring the hold priority for RSVP-TE LSP
Configure the hold priority value for the selected RSVP-TE LSP. The hold priority determines the degree to which an LSP holds onto its reservation for a session after the LSP has been set up successfully. When the hold priority is high, the existing LSP is less likely to give up its reservation.
Procedure steps
Step Action
1 To enter the configuration mode, enter:
configure terminal 2 To select the LSP, enter:
mpls traffic-eng-lsp <LSP-name>
3 To configure the hold priority, enter:
[no] {primary | secondary} hold-priority <0-7>
--End--Table 57
Variable definitions
Variable Value
[no] Sets the hold priority to the default value:
0 (highest).
primary Specifies the primary LSP.
secondary Specifies the secondary LSP.
<0-7> Specifies the hold priority, from highest priority (0) to lowest priority (7)
Configuring CSPF retry limit
Specify the number of retries that CSPF performs for a request received from RSVP.
Configuring constrained path LSP properties 97
Procedure steps
Step Action
1 To enter the configuration mode, enter:
configure terminal 2 To select the LSP, enter:
mpls traffic-eng-lsp <LSP-name>
3 To configure the CSPF retry limit, enter:
[no] {primary | secondary} cspf-retry-limit <1-65535>
--End--Table 58
Variable definitions
Variable Value
[no] Sets the retry limit to the default value:
0 (indefinite).
primary Specifies the primary LSP.
secondary Specifies the secondary LSP.
<1-65535> Specifies the number of times CSPF tries to perform a request received from RSVP.
Configuring CSPF retry timer
Use this command to specify the time between each retry that CSPF performs for a request received from RSVP.
Procedure steps
Step Action
1 To enter the configuration mode, enter:
configure terminal 2 To select the LSP, enter:
mpls traffic-eng-lsp <LSP-name>
3 To configure CSPF retry timer, enter:
[no] {primary | secondary} cspf-retry-timer <1-600>
--End--98 RSVP-TE LSP configuration
Table 59
Variable definitions
Variable Value
[no] Sets the retry timer to the default value: 0 (indefinite).
primary Specifies the primary LSP.
secondary Specifies the secondary LSP.
<1-600> Timeout between successive retries, in seconds.
Configuring the hop limit for RSVP-TE LSP
Specify the hop limit for an RSVP-TE LSP to place a limit on the number of hops in the LSP.
If a primary path exists when you configure a hop limit, the hop limit is compared with the current number of hops in the primary path. If the number of hops in the primary path exceeds the configure hop limit, the existing session is torn down and no Path messages are sent out.
The hop limit data is sent to the CSPF server, if CSPF is being used.
Procedure steps
Step Action
1 To enter the configuration mode, enter:
configure terminal 2 To select the LSP, enter:
mpls traffic-eng-lsp <LSP-name>
3 To configure the hop limit, enter:
[no] {primary | secondary} hop-limit <1-255>
--End--Table 60
Variable definitions
Variable Value
[no] Sets the hop limit to the default value (255).
primary Specifies the primary LSP.
secondary Specifies the secondary LSP.
<1-255> Specifies the acceptable number of hops.
Configuring constrained path LSP properties 99
Configuring label recording
Configure label record to set whether to record all labels exchanged between RSVP enabled routers during the reservation setup process.
Label recording can help in debugging problems.
Procedure steps
Step Action
1 To enter the configuration mode, enter:
configure terminal 2 To select the LSP, enter:
mpls traffic-eng-lsp <LSP-name>
3 To configure label recording, enter:
[no] {primary | secondary} label-record
--End--Table 61
Variable definitions
Variable Value
[no] Disables label recording.
primary Specifies the primary LSP.
secondary Specifies the secondary LSP.
label-record Specifies to record all the labels exchanged for an LSP from the ingress to the egress.
Configuring route recording
You can disable recording of the route taken by PATH and RESV messages, which confirm the establishment of reservations and identify errors. Route recording is enabled by default.
Procedure steps
Step Action
1 To enter the configuration mode, enter:
configure terminal 2 To select the LSP, enter:
mpls traffic-eng-lsp <LSP-name>
3 To configure route recording, enter:
100 RSVP-TE LSP configuration
{primary|secondary} {no-record-route | record-route}
--End--Table 62
Variable definitions
Variable Value
primary Specifies the primary LSP.
secondary Specifies the secondary LSP.
no-record-route Disables route recording.
record-route Enables route recording.
Creating an MPLS administrative group
Create administrative groups to classify links or interfaces. Administrative groups are meaningful only when CSPF is enabled. You can use these groups to implement different policy-based LSP setups. Each interface can be a member of one or more, or no, administrative groups.
Procedure steps
Step Action
1 To enter the configuration mode, enter:
configure terminal
2 To create an administrative group, enter:
[no] mpls admin-group <admin-group-name> <0-31>
--End--Table 63
Variable definitions
Variable Value
[no] Deletes the specified administrative group.
<admin-group-name> Specifies the name or color of the administrative group.
<0-31> Specifies the value of the administrative group to be added (0-31).
Adding an interface to an administrative group
Assign an interface to an administrative group to classify the interfaces.
Configuring constrained path LSP properties 101
Procedure steps
Step Action
1 To enter the configuration mode, enter:
configure terminal
2 To select an MPLS interface, enter:
interface [bundle <bundle-name> | ethernet <0/1-0/4> | vlan <vid>]
3 To assign the interface to an administrative group, enter:
[no] mpls admin-group <admin-group-name>
--End--Table 64
Variable definitions
Variable Value
[no] Removes the interface from the specified administrative group.
<admin-group-name> Specifies the name of the administrative group.
Including administrative groups in an RSVP-TE LSP
Configure the include-any parameter to set the administrative groups to include in an LSP. To be added to the LSP, links must belong to at least one of the administrative groups listed in the include-any list.
Procedure steps
Step Action
1 To enter the configuration mode, enter:
configure terminal 2 To select the LSP, enter:
mpls traffic-eng-lsp <LSP-name>
3 To configure the administrative groups to include in the LSP, enter:
[no] {primary | secondary} include-any <admin-group-na me>
--End--102 RSVP-TE LSP configuration
Table 65
Variable definitions
Variable Value
[no] Removes a previously configured group from the specified list.
primary Specifies the primary LSP.
secondary Specifies the secondary LSP.
<admin-group-name> Specifies the administrative group name.
Excluding administrative groups from an RSVP-TE LSP Specify the administrative groups to be excluded from an LSP.
If you specify an exclude-any list, any link that belongs to even one of the groups specified in the exclude list cannot be chosen for the LSP.
Procedure steps
Step Action
1 To enter the configuration mode, enter:
configure terminal 2 To select the LSP, enter:
mpls traffic-eng-lsp <LSP-name>
3 To configure the administrative groups to exclude, enter:
[no] {primary | secondary} exclude-any <admin-group-na me>
--End--Table 66
Variable definitions
Variable Value
[no] Removes the specified group from the exclude-any list.
primary Specifies the primary LSP.
secondary Specifies the secondary LSP.
<admin-group-name> Specifies the name of the administrative group to exclude from the LSP.