[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] bfd-enable
config>router>rsvp>interface
Supported on all 7210 SAS platforms as described in this document
This command enables the use of bidirectional forwarding (BFD) to control the state of the associated RSVP interface. This causes RSVP to register the interface with the BFD session on that interface.
Configure the BFD session parameters, such as transmit-interval, receive-interval, and multiplier, under the IP interface in the config>router>interface>bfd context.
It is possible that the BFD session on the interface was started because of a prior registration with another protocol, for example, OSPF or IS-IS.
The registration of an RSVP interface with BFD is performed at the time the neighbor gets its first session, which is when this node sends or receives a new Path message over the interface. However, if the session does not come up, because of not receiving a Resv for a new path message sent after the maximum number of retries, the LSP is shut down and the node deregisters with BFD. In general, the registration of RSVP with BFD is removed as soon as the last RSVP session is cleared.
The registration of an RSVP interface with BFD is performed independent of whether an RSVP hello is enabled on the interface. However, hello timeout clears all sessions toward the neighbor and RSVP deregisters with BFD at the clearing of the last session.
An RSVP session is associated with a neighbor based on the interface address the path message is sent to. If multiple interfaces exist to the same node, each interface is treated as a separate RSVP neighbor. The user must enable BFD on each interface, and RSVP registers with the BFD session running with each of those neighbors independently.
Similarly, the disabling of BFD on the interface results in removing registration of the interface with BFD.
When a BFD session transitions to the down state, the following actions are triggered:
for RSVP signaled LSPs, activation of FRR bypass/detour backup (PLR role), global revertive (head-end role), and switchover to secondary, if any (head-end role), for affected LSPs with FRR enabled
switchover to secondary, if any, and scheduling of retries for signaling the primary path of the non-FRR-affected LSPs (head-end role).
For more information about the list of protocols that support BFD, see the 7210 SAS-D, Dxp, K 2F1C2T, K 2F6C4T, K 3SFP+ 8C Router Configuration Guide.
The no form of this command removes BFD from the associated RSVP protocol adjacency.
no bfd-enable
[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 (maintenance interface) or all RSVP interfaces on the node (maintenance node), if applied at the RSVP level.
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 MBB 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 resignals 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 TE metric set to 0xffffffff and the unreserved bandwidth parameter set to zero.
A head-end LER node, upon receipt of the PathErr message, performs a single MBB 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 nodes.
a CSPF LSP with the adaptive option disabled and where the current path is over the listed maintenance interfaces in the PathErr message. These are not subject to MBB.
a non-CSPF LSP where the current path is over the listed maintenance interfaces in the PathErr message
The head-end LER node, upon receipt of the updates IPG TE LSA/LSP for the maintenance interfaces, updates the TE database. This information is used at the next scheduled CSPF computation for any LSP with a path that traverses any of the maintenance interfaces.
The no form of this command disables the graceful shutdown operation at the RSVP interface level or 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 specifies 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.
3
Specifies the keep-multiplier value.
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 command 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. The node will also not send Message-ID in RSVP messages. This effectively disables summary refresh.
disable
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 configures the value of the rapid retransmission interval. This is used in the retransmission mechanism based on an exponential backoff timer 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 stops the retransmission of unacknowledged RSVP messages in the following cases when the updated backoff interval exceeds the value of the regular refresh interval or when 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 using the config router rsvp refresh-time command.
The no form of this command reverts to the default value.
5
Specifies the rapid retransmission interval.
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.
The node stops the 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 command, whichever comes first.
The no form of this command reverts to the default value.
3
Specifies the value of the rapid retry limit.
refresh-time seconds
no refresh-time
config>router>rsvp
Supported on all 7210 SAS platforms as described in this document
This command configures the interval between the successive Path and Resv refresh messages. RSVP declares the session down after it misses the consecutive refresh messages value configured in the keep-multiplier command.
The no form of this command reverts to the default value.
30 seconds
Specifies the refresh time, in seconds.