•
You can use bridge domain routing with only native packets.
Bridge domain routing only works if proper tag popping is configured on the corresponding EFP BD.
For example, if an EFP is configured with a single tag then
rewrite
should be
pop 1 symmetric
. If the
EFP is configured with double tag then
rewrite
should be
pop 2 symmetric
. For double tag EFP,
pop
1 symmetric
and routing on the BDI is not supported.
Traffic engineering is not supported for BDI Routing.
Note
This is an example of configuring bridge-domain routing with a single tag EFP:
Router (config)#
interface gigabitethernet0/2
Router (config-if)#
service instance 1 Ethernet
Router (config-if-srv)#
encapsulation dot1q 10
Router (config-if-srv)#
rewrite ingress tag pop 1 symmetric
Router (config-if-srv)#
bridge-domain 100
Router (config)#
interface bdi 100
Router (config-if)#
ip address 20.1.1.1 255.255.255.255
This is an example of configuring bridge-domain routing with two tags:
Router (config)#
interface gigabitethernet0/2
Router (config-if)#
service instance 1 Ethernet
Router (config-if-srv)#
encapsulation dot1q 10 second-dot1q 20
Router (config-if-srv)#
rewrite ingress tag pop 2 symmetric
Router (config-if-srv)#
bridge-domain 100
Router (config)#
interface bdi 100
Router (config-if)#
ip address 20.1.1.1 255.255.255.255
EFPs and Trunk Port MAC Addresses
Because forwarding can occur between EFPs and trunk ports, MAC address movement can occur on learned
addresses. Addresses learned on EFPs will have the format of int EFP ID, for example gigabitethernet
0/0/1 + EFP 1. When an address moves between a non-secured EFP and a trunk port, the behavior is similar
to that of moving between trunk ports.
To see MAC address information for bridge domains, use the
show mac-address-table bdomain domain
command.
When an EFP property changes (bridge domain, rewrite, encapsulation, split-horizon, secured or unsecured,
or a state change), the old dynamic MAC addresses are flushed from their existing tables. This is to prevent
old invalid entries from lingering.
EFPs and MSTP
EFP bridge domains are supported by the Multiple Spanning Tree Protocol (MSTP). These restrictions apply
when running STP with bridge domains.
•
EVC supports only MSTP.
•
All incoming VLANs (outer-most or single) mapped to a bridge domain must belong to the same MST
instance or loops could occur.
Carrier Ethernet Configuration Guide (Cisco ASR 920 Series)
39
Ethernet Virtual Connections Configuration
Configuring IEEE 802.1Q Tunneling and Layer 2 Protocol Tunneling Using EFPs
Содержание ASR 920 series
Страница 2: ... 2014 Cisco Systems Inc All rights reserved ...
Страница 273: ...Carrier Ethernet Configuration Guide Cisco ASR 920 Series 255 Configuring Ethernet CFM Designing CFM Domains ...
Страница 302: ...Carrier Ethernet Configuration Guide Cisco ASR 920 Series 284 Configuring Ethernet CFM Glossary ...