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

Multi-Service IronWare Multiprotocol Label Switch (MPLS) Configuration Guide 89
53-1003031-02
MPLS over virtual Ethernet interfaces
1
Protocol-based VLANs
When enabling MPLS on a VE interface associated with a protocol-based VLAN, consider the
following.
NOTE
MPLS is supported only on VE interfaces that are configured on port-based VLANs.
• The user cannot configure MPLS on a VE interface associated with a protocol based VLAN. The
command is rejected, and the following error message is displayed.
Brocade(config-mpls)# mpls-interface ve 1
Error: Cannot configure MPLS on VE built on protocol-based VLAN
VRF
When enabling MPLS on a VE interface for a VRF instance, consider the following.
NOTE
When configuring MPLS on a VE interface on a VLAN port, the user can also configure a VRF instance
on other VLANs of the same port.
• The user cannot configure a VRF instance on a MPLS VE enabled interface. The following error
message is displayed.
Brocade(config-vif-20)# vrf forwarding test
Error - cannot configure VRF on an MPLS VE enabled interface
Class of Service (CoS)
NOTE
On Brocade NetIron CES and Brocade NetIron CER devices, by default the internal priority of a packet
received on a tagged MPLS uplink is mapped only from EXP bits. The PCP bits are not used.
By default, the internal priority of a packet received on a tagged MPLS uplink is mapped from PCP
and EXP bits. When determining the internal priority, the first step is to merge the PCP and EXP bits.
In this step, when configuring the qos exp force command on an interface, the internal priority is
mapped only from EXP bits and PCP bits are ignored.The qos exp force command does not override
the port priority command. In the second step, the port priority is merged with the internal priority
so the qos exp force command has no effect on this step.
By default, the internal priority of a packet sent out on a tagged MPLS uplink is mapped into EXP
and PCP bits. When configuring the qos pcp-encode policy off command on an outgoing interface,
the PCP bits is zero.