[no] rsvp
config>router
This command creates the RSVP-TE protocol instance and enables RSVP-TE configuration.
RSVP-TE is enabled by default.
RSVP-TE is used to set up LSPs. RSVP-TE should be enabled on all router interfaces that participate in signaled LSPs.
The no form of this command deletes this RSVP-TE protocol instance and removes all configuration parameters for this RSVP-TE instance. To suspend the execution and maintain the existing configuration, use the shutdown command. RSVP-TE must be shut down before the RSVP-TE instance can be deleted. If RSVP-TE is not shut down, the no rsvp command does nothing except issue a warning message on the console indicating that RSVP-TE is still administratively enabled.
no shutdown
[no] entropy-label-capability
config>router>rsvp
This command enables or disables the entropy label capability for an RSVP-TE LSP. When enabled, the egress LER (eLER) signals to the ingress LER (iLER) that the LSP is capable of using entropy labels.
The no form of the command disables entropy label capability.
no entropy-label-capability
[no] graceful-shutdown
config>router>rsvp
config>router>rsvp>interface
This command initiates a graceful shutdown of the specified RSVP interface (referred to as a maintenance interface) or all RSVP interfaces on the node (referred to as a maintenance node). When this command is executed, the node performs the following operations in no specific order.
A PathErr message with an error sub-code of ‟Local Maintenance on TE Link required” is generated for each LSP that is in transit at this node and is using a maintenance interface as its outgoing interface. A PathErr message with the error code ‟Local node maintenance required” is generated if all interfaces are affected.
A single make-before-break attempt is performed for all adaptive CSPF LSPs that originate on the node and whose paths make use of the maintenance interfaces listed in the PathErr message. If an alternative path for an affected LSP is not found, the LSP is maintained on its current path. The maintenance node also tears down and resignals any bypass or detour LSP that uses the maintenance interfaces as soon as they are not active. The maintenance node floods an IGP TE LSA/LSP containing a Link TLV for the links under graceful shutdown with the Traffic Engineering metric set to 0xffffffff and the Unreserved Bandwidth parameter set to zero (0).
Upon receipt of the PathErr message, an intermediate LSR tears down and resignals any bypass LSP whose path makes use of the listed maintenance interfaces as soon as no associations with a protected LSP are active. The node does not take any action on a detour LSP whose path makes use of the listed maintenance interfaces.
Upon receipt of the PathErr message, a head-end LER performs a single make-before-break attempt on the affected adaptive CSPF LSP. If an alternative path is not found, the LSP is maintained on its current path.
A node does not take any action on the paths of the following originating LSPs after receiving the PathErr message:
an adaptive CSPF LSP for which the PathErr indicates a node address in the address list and the node corresponds to the destination of the LSP. In this case, there are no alternative paths that can be found.
an adaptive CSPF LSP whose path has explicit hops defined using the listed maintenance interfaces or node
a CSPF LSP that has the adaptive option disabled and whose current path is over the listed maintenance interfaces in the PathErr message. These are not subject to make-before-break.
a non-CSPF LSP whose current path is over the listed maintenance interfaces in the PathErr message
Upon receipt of the updated IPG TE LSA/LSP for the maintenance interfaces, the head-end LER updates the TE database. This information will be used at the next scheduled CSPF computation for any LSP whose path might traverse any of the maintenance interfaces.
The no form of the command disables the graceful shutdown operation at the RSVP interface level or at the RSVP level. The configured TE parameters of the maintenance links are restored and the maintenance node floods the links.
n/a
[no] implicit-null-label
config>router>rsvp
This command enables the implicit null label to be included in RESV messages sent by the egress LER (eLER) to the previous-hop LSR. The implicit null label is enabled for all LSPs for which the router is the eLER.
When the implicit null label is signaled to the LSR, it pops the outer label before sending the MPLS packet to the eLER; this is known as penultimate hop popping.
RSVP-TE must be shut down before this command can be used.
The no form of this command disables the signaling of the implicit null label.
no implicit-null-label
[no] keep-multiplier number
no keep-multiplier
config>router>rsvp
This command is used by RSVP-TE to declare that a reservation is down or the neighbor is down. The keep-multiplier number is used with the refresh-time command to determine when RSVP-TE will declare the session down.
The no form of this command reverts to the default value.
3
specifies the keep-multiplier value
node-id-in-rro {include | exclude}
config>router>rsvp
This command enables the option to include the node-id sub-object in the RRO. Propagation of the node-id sub-object is required to provide fast reroute protection for an LSP that spans multiple area domains.
exclude
the node-id sub-object is included in the RRO
the node-id sub-object is not included in the RRO
rapid-retransmit-time hundred-milliseconds
no rapid-retransmit-time
config>router>rsvp
This command is used to define the value of the rapid retransmission interval. This is used in the retransmission mechanism based on an exponential backoff timer in order to handle unacknowledged message-_id objects. The RSVP-TE message with the same message-id is retransmitted every 2 ✕ rapid-retransmit-time interval. The node will stop retransmission of unacknowledged RSVP-TE messages whenever the updated backoff interval exceeds the value of the regular refresh interval or the number of retransmissions reaches the value of the rapid-retry-limit parameter, whichever comes first.
The rapid retransmission interval must be smaller than the regular refresh interval configured in config>router>rsvp>refresh-time.
The no form of this command reverts to the default value.
5 (which represents 500 msec)
1 to 100, in units of 100 msec
rapid-retry-limit number
no rapid-retry-limit
config>router>rsvp
This command is used to define the value of the rapid retry limit. This is used in the retransmission mechanism based on an exponential backoff timer in order to handle unacknowledged message_id objects. The RSVP-TE message with the same message_id is retransmitted every 2 ✕ rapid-retransmit-time interval. The node will stop retransmission of unacknowledged RSVP-TE messages whenever the updated backoff interval exceeds the value of the regular refresh interval or the number of retransmissions reaches the value of the rapid-retry-limit parameter, whichever comes first.
The no form of this command reverts to the default value.
3
1 to 6, integer values
refresh-reduction-over-bypass [enable | disable]
config>router>rsvp
This command enables the refresh reduction capabilities over all bypass tunnels originating on this 7705 SAR PLR node or terminating on this 7705 SAR Merge Point (MP) node.
By default, this is disabled. Since a bypass tunnel may merge with the primary LSP path in a node downstream of the next hop, there is no direct interface between the PLR and the MP node and it is possible that the latter will not accept summary refresh messages received over the bypass. When disabled, the node as a PLR or MP will not set the ‟Refresh-Reduction-Capable” bit on RSVP-TE messages pertaining to LSP paths tunneled over the bypass. It will also not send message-id in RSVP-TE messages. This effectively disables summary refresh.
disable
refresh-time seconds
no refresh-time
config>router>rsvp
This command controls the interval, in seconds, between the successive PATH and RESV refresh messages. RSVP-TE declares the session down after it misses keep-multiplier number consecutive refresh messages.
The no form of this command reverts to the default value.
30
specifies the refresh time in seconds