Brocade Multi-Service IronWare Multiprotocol Label Switch (MPLS) Configuration Guide (Supporting R05.6.00) - Manual (Page 132)

108 Multi-Service IronWare Multiprotocol Label Switch (MPLS) Configuration Guide
53-1003031-02
RSVP reliable messaging
1
Brocade(config)# router mpls
Brocade(config-mpls)# mpls-interface ethernet 1/1
Brocade(config-mpls-if-e100-1/1)# rsvp-authentication key administrator
Syntax: [no] rsvp-authentication key string
The string variable specifies a text string of up to 64 characters that is encrypted and used for
RSVP message authentication.
By default, the authentication key is encrypted. When the user wants the authentication key to be
in clear text, insert a 0 between key and string.
Example
Brocade(config-mpls-if-e100-1/1)# rsvp-authentication key 0 administrator
The software adds a prefix to the authentication key in the configuration. For example, the following
portion of the code has the encrypted code “2”.
rsvp-authentication 2 key $IUA2PWc9LW9VIW9zVQ=="
The prefix can be one of the following:
• 0 = the key string is not encrypted and is in clear text
• 1 = the key string uses proprietary simple cryptographic 2-way algorithm (only for Brocade
NetIron CES and Brocade NetIron CER devices)
• 2 = the key string uses proprietary base64 cryptographic 2-way algorithm (only for Brocade
NetIron XMR and Brocade MLX series devices)
RSVP reliable messaging
The standard RSVP periodically resends Resv and Path refresh messages to maintain the state of
the path, but many trigger messages signaling a new or changed state (such as PathTear and
ResvTear messages) are sent only once. The loss of such a message can cause delays in the
reservation or release of resources.
RFC 2961 provides extensions to the RSVP to make the transmission of RSVP trigger messages
more reliable by creating an ID for each new RSVP message and allowing the sender to request an
acknowledgement of the receipt of trigger messages.
Configuring RSVP reliable messaging
When RSVP reliable messaging is enabled on an interface of the Brocade device, RSVP trigger
messages sent out on that interface includes a message ID and a request for acknowledgement
from the RSVP neighbor. When acknowledgement is not received, the trigger message is
retransmitted using the retransmission parameters configured on the interface.
NOTE
RSVP refresh messages never require acknowledgement, even when reliable messaging is enabled.
To enable RSVP reliable messaging on an interface, use commands such as the following.
Brocade(config)# router mpls
Brocade(config-mpls)# mpls-interface ethernet 3/13