Cisco WS-SUP32-GE-3B - Supervisor Engine 32 Software Configuration Manual page 321

Chapter 21 Configuring Multiprotocol Label Switching
Note
Note
• EoMPLS is not supported with private VLANs.
• The following restrictions apply to using trunks with EoMPLS:
–
–
All protocols (for example, CDP, VTP, BPDUs) are tunneled across the MPLS cloud without
•
conditions.
ISL encapsulation is not supported for the interface that receives EoMPLS packets.
•
Unique VLANs are required across interfaces. You cannot use the same VLAN ID on different
•
interfaces.
EoMPLS tunnel destination route in the routing table and the CEF table must be a /32 address (host
•
address where the mask is 255.255.255.255) to ensure that there is a label-switched path (LSP) from
PE to PE.
For a particular EoMPLS connection, both the ingress EoMPLS interface on the ingress PE and the
•
egress EoMPLS interface on the egress PE have to be subinterfaces with dot1Q encapsulation or
neither is a subinterface.
• 802.1Q in 802.1Q over EoMPLS is supported if the outgoing interface connecting to MPLS network
is a port on an Layer 2 card.
Shaping EoMPLS traffic is not supported if the egress interface connecting to an MPLS network is
•
a Layer 2 LAN port (a mode known as PFC3B-based EoMPLS).
EoMPLS does not perform any Layer 2 lookup to determine if the destination MAC address resides
•
on the local or remote segment and does not perform any Layer 2 address learning (as traditional
LAN bridging does). This functionality (local switching) is available only when using OSM and
FlexWAN modules as uplinks.
In previous releases of AToM, the command used to configure AToM circuits was mpls l2 transport
•
route. This command has been replaced with the xconnect command. You can use the xconnect
command to configure EoMPLS circuits.
• The AToM control word is not supported.
• EoMPLS is not supported on Layer 3 VLAN interfaces.
• Point-to-point EoMPLS works with a physical interface and subinterfaces.
OL-11439-03
The no mls qos rewrite ip dscp command is not compatible with the MPLS and MPLS VPN
features. See Chapter 38, "Configuring PFC QoS."
Do not use the no mls qos rewrite ip dscp command if you have PFC3B-based EoMPLS and
PXF-based EoMPLS services in the same system.
To support Ethernet spanning tree bridge protocol data units (BPDUs) across an EoMPLS cloud,
you must disable the supervisor engine spanning tree for the Ethernet-over-MPLS VLAN. This
ensures that the EoMPLS VLANs are carried only on the trunk to the customer switch.
Otherwise, the BPDUs are directed to the supervisor engine and not to the EoMPLS cloud.
The native VLAN of a trunk must not be configured as an EoMPLS VLAN.
Catalyst Supervisor Engine 32 PISA Cisco IOS Software Configuration Guide, Release 12.2ZY
Any Transport over MPLS
21-15