Brocade Multi-Service IronWare Multiprotocol Label Switch (MPLS) Configuration Guide (Supporting R05.6.00) User Manual
Page 117
Multi-Service IronWare Multiprotocol Label Switch (MPLS) Configuration Guide
93
53-1003031-02
Configuring MPLS
1
The number has a range of 0 – 31.
After the user associates an administrative group name with a number, the user can see it by name
when assigning interfaces to the group or including or excluding the group from LSP calculations.
Refer to
“Adding interfaces to administrative groups”
“Including or excluding administrative
Enabling OSPF-TE LSAs for MPLS interfaces
Information related to traffic engineering is carried in OSPF traffic engineering (OSPF-TE) LSAs.
OSPF-TE LSAs have special extensions that contain information about an interface’s traffic
engineering metric, bandwidth reservations, and administrative group memberships.
When an MPLS-enabled device receives an OSPF-TE LSA, it stores the traffic engineering
information in its Traffic Engineering database (TED). The device uses information in the TED when
performing calculations to determine a path for an LSP.
The user can configure the device to send out OSPF-TE LSAs for all of its MPLS-enabled interfaces.
To do this, enter the following commands.
Brocade(config)# router mpls
Brocade(config-mpls)# policy
Brocade(config-mpls-policy)# traffic-engineering ospf
Syntax: [no] traffic-engineering ospf [area area-id]
The user can use the area option to limit the CSPF calculations to the OSPF Area specified by the
area-id variable. The area-id variable can accept area-id in both Decimal and IP address formats.
By default, the device does not send out OSPF-TE LSAs for its MPLS-enabled interfaces. Because
information in the TED is used to make path selections using CSPF and information in the TED
comes from OSPF-TE LSAs or IS-IS TE LSP, the user must enable the device to send out OSPF-TE
LSAs or IS-IS LSPs with TE extensions when the user wants CSPF to perform constraint-based path
selection.
The [no] option removes an existing OSPF TE database. When the user employs the no option with
the area option, the OSPF TE database is removed for only the specified OSPF area.
Refer to
“Setting traffic engineering parameters for MPLS interfaces”
, for information on the traffic
engineering information carried in OSPF-TE LSAs.
Enabling IS-IS LSPs with TE extensions for MPLS interfaces
Information related to traffic engineering is carried in IS-IS traffic engineering LSPs. IS-IS TE LSPs
have special extensions that contain information about an interface’s administrative group
memberships, IPv4 interface address, IPv4 neighbor address, maximum link bandwidth,
reservable link bandwidth, unreserved bandwidth, and default traffic engineering metrics.
When an MPLS-enabled device receives an IS-IS TE LSP, it stores the traffic engineering
information in its Traffic Engineering database (TED). The device uses information in the TED when
performing calculations to determine a path for an LSP.
The user can configure the device to send out IS-IS TE LSPs for all of its MPLS-enabled interfaces.
To do this, enter the following commands.