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

Multi-Service IronWare Multiprotocol Label Switch (MPLS) Configuration Guide 91
53-1003031-02
Configuring MPLS
1
Brocade(config-mpls)# mpls-interface e 3/1
Syntax: [no] mpls-interface all-ethernet | ethernet slot/port | pos slot/port |ve vid
The all-ethernet option specifies all Layer-3 Ethernet interfaces.
The ethernet option specifies the individual Ethernet interface described by the slot/port variable.
The pos option specifies the individual POS interface described by the slot/port variable.
The ve option specifies the individual virtual ethernet (VE) interface described by the vid variable.
Configuration Considerations for enabling MPLS on a LAG interface
When MPLS is globally enabled on the device, a port that is configured in a LAG can be enabled as
an MPLS interface port to create an MPLS LAG. The user can do this through either of the following
approaches:
• Include a primary LAG port that has already been MPLS -enabled in a new LAG.
• MPLS-enable a primary LAG port of a previously configured LAG.
The user must consider the following points when configuring MPLS on a LAG
• MPLS configuration on dynamic lag interfaces are supported.
• Switch and LACP LAGs are not supported.
• MPLS is enabled on the primary port of the LAG and this enables MPLS on the entire LAG.
Secondary ports of the LAG cannot be individually configured for MPLS.
Setting global MPLS policy parameters
The user can optionally set the following global MPLS policy parameters (they apply to all
MPLS-enabled interfaces on the device):
• Retry time
• Retry limit
• Administrative group names
• Whether the device sends out OSPF-TE LSAs for its MPLS-enabled interfaces
• Whether the device sends out IS-IS LSPs with TE extensions for its MPLS-enabled interfaces
• Configuring IP-over-MPLS TTL Propagation Control
• LSP Accounting
Setting the retry time
When a signaled LSP is enabled, the ingress LER attempts to connect to the egress LER over the
primary path specified in the LSPs configuration. When the connection is not successful, by default
the ingress LER waits 30 seconds before attempting the connection again. the user can configure
the amount of time the ingress LER waits between connection attempts.
For example, to specify a retry time of 45 seconds.