•
For all EFPs that are mapped to the same MST instance, you must configure backup EFPs on every
redundant path to prevent loss of connectivity due to STP blocking a port.
L3 Unicast and Multicast Routing on a Bridge Domain with Multiple EFPs
L3 unicast routing and L3 multicast routing are supported on bridge domains with multiple EFPs. This feature
provides the following functionality:
•
Broadcast domains are determined through bridge-domains rather than VLANs
•
Multiple EFPs on a single bridge domain and physical interface with L3 multicast routing enabled is
supported
•
Each EFP has its own match criteria and its own ingress and egress rewrite operations
Figure below shows an access-facing port with multiple EFPs configured to the route or bridge.
Example for Configuring L3 Multicast Routing on a Bridge Domain
The following example shows how to configure L3 multicast routing on a bridge domain using existing IOS
commands.
ip routing
Ip multicast-routing
!
!
interface bdi 100
ip address 1.1.1.1 255.255.255.0
ip pim sparse-mode
Igmp version v3
!
interface GigabitEthernet0/1
service instance 1 ethernet
encapsulation dot1q 33
rewrite ingress tag pop 1 symmetric
bridge-domain 100
!
service instance 2 ethernet
encapsulation dot1q 55
rewrite ingress tag pop 1 symmetric
bridge-domain 100
Cross-Connect on EFP Interfaces
Cross-connect provides the ability to match the encapsulation of received packets on the ingress side of an
EFP interface and send them out with the same encapsulation through the egress side of the EFP interface.
Cross-connect bridge-domain entries are provided, and encapsulation matching is achieved by matching
bridge-domain entries for the EFPs on which cross-connect is configured.
The following types of encapsulation tags are supported:
•
untagged
•
rewrite tags with pop1
Carrier Ethernet Configuration Guide (Cisco ASR 920 Series)
40
Ethernet Virtual Connections Configuration
Configuring IEEE 802.1Q Tunneling and Layer 2 Protocol Tunneling Using EFPs
To Next Page
Loading...
Need help?
General
