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

124 Multi-Service IronWare Multiprotocol Label Switch (MPLS) Configuration Guide
53-1003031-02
Setting up signaled LSPs
1
Configuring RSVP message authentication on an MPLS VE interface
NOTE
For more information on configuring RSVP message authentication on physical interfaces, refer to
“Configuring RSVP message authentication” .
RSVP Message Authentication is disabled by default. This authentication method uses MD5 for an
MPLS VE interface. The following example configures RSVP message authentication for MPLS
interface ve 100.
Brocade(config)# router mpls
Brocade(config-mpls)# mpls-interface ve 100
Brocade(config-mpls-if-ve-100)# rsvp-authentication key private
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.
Specifying a bypass LSP for an MPLS VE interface
The user can create a bypass LSP by using the bypass-lsp command. This is used for facility backup
FRR. In the context of bypass LSP, the user can configure an MPLS interface as an exclude
(protected) interface against resource failures using a bypass LSP. The user can specify a VE
interface as exclude-interface. When a protected LSP egress interface is a VE interface, then any
fault on a VE interface could trigger FastReroute. The following example configures protection for
MPLS interface ve 100 using facility backup FRR.
Brocade(config)# router mpls
Brocade(config-mpls)# bypass-lsp to4
Brocade(config-mpls-bypasslsp-to4)# exclude-interface ve 10
Syntax: [no] exclude-interface ethernet slot/port [ethernet slot/port | to slot/port] | pos slot/port
[pos slot/port | to slot/port] | ve vid]
By default, a VE interface is not protected. The ve parameter allows the user to configure a ve
interface as exclude-interface specified by vid.
Setting up signaled LSPs
An LSP consists of an actual path of MPLS routers through a network, as well as the characteristics
of the path, including bandwidth allocations and routing metrics. There are two kinds of LSPs:
signaled and static. Signaled LSPs are configured at the ingress LER. When the user enables a
signaled LSP, RSVP causes resources to be allocated on the other routers in the LSP.
Configuring a signaled LSP consists of the following tasks:
• Specifying a path for the LSP to follow (optional)
• Setting parameters for the signaled LSP