[no] rsvp
config>router
Supported on all 7210 SAS platforms as described in this document.
Commands in this context configure RSVP protocol parameters. RSVP is not enabled by default and must be explicitly enabled (no shutdown).
RSVP is used to set up LSPs. RSVP should be enabled on all router interfaces that participate in signaled LSPs.
The no form of this command deletes this RSVP protocol instance and removes all configuration parameters for this RSVP instance. To suspend the execution and maintain the existing configuration, use the shutdown command. RSVP must be shut down before the RSVP instance can be deleted. If RSVP is not shut down, the no rsvp command does nothing except issue a warning message on the console indicating that RSVP is still administratively enabled.
no shutdown
[no] graceful-shutdown
config>router>rsvp
config>router>rsvp>interface
Supported on all 7210 SAS platforms as described in this document.
This command initiates a graceful shutdown of the specified RSVP interface or all RSVP interfaces on the node if applied at the RSVP level. These are referred to as maintenance interface and maintenance node, respectively.
To initiate a graceful shutdown the maintenance node generates a PathErr message with a specific error sub-code of Local Maintenance on TE Link required for each LSP that is exiting the maintenance interface.
The node performs a single make-before-break attempt for all adaptive CSPF LSPs it originates and LSP paths using the maintenance interfaces. 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 re-signals any detour LSP path using listed maintenance interfaces as soon as they are not active.
The maintenance node floods an IGP TE LSA/LSP containing Link TLV for the links under graceful shutdown with the traffic engineering metric set to 0xffffffff and unreserved bandwidth parameter set to zero (0).
After receiving the PathErr message, ahead-end LER node 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, no alternative paths can be found
an adaptive CSPF LSP for which the path has explicit hops defined using the listed maintenance interfaces or nodes
a CSPF LSP with the adaptive option disabled and for which the current path is over the listed maintenance interfaces in the PathErr message; these are not subject to make-before-break
a non-CSPF LSP for which the current path is over the listed maintenance interfaces in the PathErr message
After receiving the updated IPG TE LSA/LSP for the maintenance interfaces, the head-end LER node updates the TE database. This information is used at the next scheduled CSPF computation for any LSP for which the path may traverse any of the maintenance interfaces.
The no form of this 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.
keep-multiplier number
no keep-multiplier
config>router>rsvp
Supported on all 7210 SAS platforms as described in this document.
This command configures the keep multiplier number. The keep-multiplier number is an integer used by RSVP to declare that a reservation is down or the neighbor is down.
The no form of this command reverts to the default value.
keep-multiplier 3
Specifies the keep multiplier value.
node-id-in-rro [include | exclude]
config>router>rsvp
7210 SAS-Mxp
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.
If this option is disabled, the node ID is not included in the RRO object.
node-id-in-rro exclude
Keyword to include the node ID sub-object in the RRO.
Keyword to exclude the node ID sub-object in the RRO.
refresh-reduction-over-bypass [enable | disable]
config>router>rsvp
Supported on all 7210 SAS platforms as described in this document.
This command enables the refresh reduction capabilities over all bypass tunnels originating on this 7210 SAS PLR node or terminating on this 7210 SAS Merge Point (MP) node.
By default, this is disabled. Because 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 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 messages pertaining to LSP paths tunneled over the bypass. It will also not send the Message-ID in RSVP messages. This disables summary refresh.
disable
Keyword to enable refresh reduction capabilities.
Keyword to disable refresh reduction capabilities.
rapid-retransmit-time hundred-milliseconds
no rapid-retransmit-time
config>router>rsvp
Supported on all 7210 SAS platforms as described in this document.
This command is used to define the value of the rapid retransmission interval. This is used in the retransmission mechanism based on the exponential back-off timer to handle unacknowledged message_id objects.
The RSVP message with the same message ID is retransmitted every 2 ✕ rapid-retransmit-interval.
The node stops re transmission of unacknowledged RSVP messages whenever the updated back-off 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.
rapid-retransmit-time 5
Specifies the rapid retransmission interval, in units of 100 milliseconds.
rapid-retry-limit limit
no rapid-retry-limit
config>router>rsvp
Supported on all 7210 SAS platforms as described in this document.
This command configures the value of the rapid retry limit. This is used in the retransmission mechanism based on an exponential backoff timer to handle unacknowledged message_id objects. The RSVP message with the same message_id is retransmitted every 2 ✕ rapid-retransmit-time interval of time. The node stops retransmission of unacknowledged RSVP 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.
rapid-retry-limit 3
Specifies the value of the rapid retry limit, expressed as an integer value.
refresh-time seconds
no refresh-time
config>router>rsvp
Supported on all 7210 SAS platforms as described in this document.
This command controls the interval, in seconds, between the successive Path and Resv refresh messages. RSVP declares the session down after it misses keep-multiplier number consecutive refresh messages.
The no form of this command reverts to the default value.
refresh-time 30
Specifies the refresh time in seconds.