Filter
Top Products
8-8
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
Chapter 8 Configuring Ethernet Virtual Connections
Configuring EFPs
• All licenses support a maximum of 16 EFPs per bridge domain.
• You must configure encapsulation on a service instance before configuring bridge domain.
• When you configure a bridge domain between 1 and 4094, IGMP snooping is automatically disabled
on the VLAN.
• ISL trunk encapsulation is not supported.
• When an EFP encapsulation is the default (matching or allowing all ingress frames), you cannot
configure any other encapsulation on an EFP on the same port and bridge-domain as the default
encapsulation. There can be only one default encapsulation per port.
• The router does not support overlapping configurations on the same interface and same bridge
domain. If you have configured a VLAN range encapsulation, or encapsulation default on service
instance 1, you cannot configure any other encapsulations that also match previous encapsulations
in the same interface and bridge domain. See the “Configuration Examples of Unsupported
Features” section on page 8-12.
• Default encapsulation is supported only on the physical interface and port channel interface.
• The default encapsulation command is accepted only for untagged EFP.
• If default encapsulation EVC is configured on the interface, only the untagged encapsulation is
accepted and all other encapsulation commands are rejected.
• Default EFP under xconnect and untagged EFP under bridge-domain on the same interface is not
supported.
• The rewrite command on encapsulation default EVC is rejected.
• Supports encapsulation only on bridge-domain and Xconnect.
• Supports only untagged EFPs on the port with default encapsulation.
• Egress filtering is not supported. All unlearned traffic ingresses on the default encapsulation
interface is flooded to other interfaces that are part of the same bridge-domain.
• Layer 3 routing is not supported. Layer 2 VPN is supported on the default encapsulation EFP.
• QinQ configuration for Layer3 is not possible with pop1 rewrite. However pop2 configured routed
QinQ is supported.
• Default xconnect MTU is 9216.
• For interoperability with other routers for an xconnect session, ensure that the MTU on both PE
routers is same before the xconnect session is established.
• MPLS is not supported over routed QinQ.
• VLAN IDs 4093, 4094, and 4095 are reserved for internal usage.
Creating Service Instances
Complete the following steps to create an EFP service instance:
Note The dot1q and dot1ad range configuration is not supported on the port channel interface on
Cisco IOS Release 15.2(2)SNI.