[no] interface ip-int-name
config>router>rsvp
Supported on all 7210 SAS platforms as described in this document
This command enables RSVP protocol support on an IP interface. No RSVP commands are executed on an IP interface where RSVP is not enabled.
The no form of this command deletes all RSVP commands, such as hello-interval and subscription, that are defined for the interface. The RSVP interface must be shutdown before it can be deleted. If the interface is not shut down, the no interface ip-int-name command does nothing except issue a warning message on the console indicating that the interface is administratively up.
shutdown
Specifies the name of the network IP interface. An interface name cannot be in the form of an IP address. If the string contains special characters (#, $, spaces, and so on), the entire string must be enclosed within double quotes.
authentication-key [authentication-key | hash-key] [hash | hash2]
no authentication-key
config>router>rsvp>interface
Supported on all 7210 SAS platforms as described in this document
This command configures the authentication key used between RSVP neighbors to authenticate RSVP messages. Authentication uses the MD-5 message-based digest.
When enabled on an RSVP interface, authentication of RSVP messages operates in both directions of the interface.
A node maintains a security association using one authentication key for each interface to a neighbor. The following items are stored in the context of this security association:
HMAC-MD5 authentication algorithm
key used with the authentication algorithm
lifetime of the key; the user-entered key is valid until the user deletes it from the interface
source address of the sending system
latest sending sequence number used with this key identifier
An RSVP sender transmits an authenticating digest of the RSVP message, computed using the shared authentication key and a keyed-hash algorithm. The message digest is included in an integrity object that also contains a flags field, a key identifier field, and a sequence number field. The RSVP sender complies with the procedures for RSVP message generation in RFC 2747, RSVP Cryptographic Authentication.
An RSVP receiver uses the key together with the authentication algorithm to process received RSVP messages.
The MD5 implementation does not support the authentication challenge procedures in RFC 2747.
The no form of this command disables authentication.
no authentication-key
Specifies the authentication key. The key can be any combination of ASCII characters up to 16 characters in length (unencrypted). If the string contains special characters (#, $, spaces, and so on), the entire string must be enclosed within double quotes.
Specifies the hash key. The key can be any combination of up 33 alphanumeric characters. If spaces are used in the string, enclose the entire string in quotation marks (‟ ”).
This is useful when a user must configure the parameter, but for security purposes the actual unencrypted key value is not provided.
Keyword to specify the key is entered in an encrypted form. If the hash parameter is not used, the key is assumed to be in a non-encrypted, clear text form. For security, all keys are stored in encrypted form in the configuration file with the hash parameter specified.
Keyword to specify the key is entered in a more complex encrypted form. If the hash2 parameter is not used, the less encrypted hash form is assumed.
hello-interval milli-seconds
no hello-interval
config>router>rsvp>interface
Supported on all 7210 SAS platforms as described in this document
This command configures the time interval between RSVP hello messages.
RSVP hello packets detect loss of RSVP connectivity with the neighboring node. Hello packets detect the loss of the neighbor more quickly than it would take for the RSVP session to time out based on the refresh interval. After the loss of the of keep-multiplier number consecutive hello packets, the neighbor is declared to be in a down state.
The no form of this command reverts to the default value. To disable sending hello messages, set the value to zero.
3000 milliseconds
Specifies the RSVP hello interval in milliseconds, in multiples of 1000. A 0 (zero) value disables the sending of RSVP hello messages.
implicit-null-label [enable | disable]
no implicit-null-label
config>router>rsvp
Supported on all 7210 SAS platforms as described in this document
This command enables the use of the implicit null label for all LSPs signaled by RSVP on the node.
All LSPs for which this node is the egress LER and for which the path message is received from the previous hop node over this RSVP interface signals the implicit null label. If the egress LER is also the merge-point (MP) node, the incoming interface for the path refresh message over the bypass dictates whether the packet uses the implicit null label. The same is true for a 1-to-1 detour LSP.
The RSVP interface must be shut down before changing the implicit-null-label command.
The no form of this command reverts the RSVP interface to using the RSVP level configuration value.
disable
Keyword to enable the implicit null label.
Keyword to disable the implicit null label.
[no] refresh-reduction
config>router>rsvp>interface
Supported on all 7210 SAS platforms as described in this document
This command enables the use of the RSVP overhead refresh reduction capabilities on this RSVP interface.
The no form of this command reverts to the default value.
no refresh-reduction
[no] reliable-delivery
config>router>rsvp>interface>refresh-reduction
Supported on all 7210 SAS platforms as described in this document
This command configures reliable delivery of RSVP messages over the RSVP interface. When the refresh-reduction command is enabled on an interface and the reliable-delivery command is disabled, the router sends a message_id and not set ACK desired in the RSVP messages over the interface. The router does not expect an ACK but accepts it if received. The node also accepts message IDs and replies with an ACK when requested. In this case, if the neighbor set the "refresh-reduction-capable" bit in the flags field of the common RSVP header, the node enters summary refresh for a specific message_id it sent regardless of whether it received an ACK to this message from the neighbor.
Finally, when the reliable-delivery command is enabled on any interface, RSVP message pacing is disabled on all RSVP interfaces on the system; for example, the user cannot enable the msg-pacing option in the config>router>rsvp context, and an error message is returned in the CLI. When the msg-pacing option is enabled, the user cannot enable the reliable delivery option on any interface on this system. An error message is also generated in the CLI after such an attempt.
The no form of this command reverts to the default value.
no reliable-delivery
subscription percentage
no subscription
config>router>rsvp>interface
Supported on all 7210 SAS platforms as described in this document
This command configures the percentage of the link bandwidth that RSVP can use for reservation and sets a limit for the amount of over-subscription or under-subscription allowed on the interface.
When the subscription is set to zero, no new sessions are permitted on this interface. If the percentage value is exceeded, the reservation is rejected and a log message is generated.
The no form of this command reverts to the default value.
100
Specifies the percentage of the interface bandwidth that RSVP allows to be used for reservations.