You are on page 1of 94

Using Cisco Ethernet Virtual Circuit (EVC) Framework

Concepts, Configuration and Verification

Agenda
 Introduction
 Cisco EVC Fundamentals  Operation and Packet Flow

 Configuration
 Platform Support

Presentation_ID

© 2010 Cisco and/or its affiliates. All rights reserved.

Cisco Public

2

Introduction

Presentation_ID

© 2010 Cisco and/or its affiliates. All rights reserved.

Cisco Public

3

What Is Cisco EVC Framework?  Cisco Ethernet Virtual Circuit (EVC) is the next-generation cross-platform Carrier Ethernet Software Infrastructure  Addresses Flexible Ethernet Edge requirements  Supports service convergence over Ethernet  Complies with MEF. All rights reserved. IEEE. IETF standards Presentation_ID © 2010 Cisco and/or its affiliates. Cisco Public 4 .

1.1ah Presentation_ID Standards Alignment © 2010 Cisco and/or its affiliates. All rights reserved.Introducing Cisco EVC Framework Functional Highlights Ethernet Service Instances  Model Ethernet Service Layer  Transport agnostic Support mix of Layer 2 and Layer 3 services on same physical port Concurrent support of different flavors of Layer 2 services: Ptto-Pt and Mpt Service Abstraction Multiplexed Forwarding Services EVC Framework Technology Flexible Service Mapping Advanced Frame Manipulation Flexible definition of service delimiters based on Ethernet header fields Selective EVC Mapping Advanced VLAN tag manipulation Alignment with emerging standards:  MEF 6.1ad  IEEE 802. Cisco Public 5 . 11  IEEE 802. 10.

All rights reserved. Cisco Public 6 .Cisco EVC Fundamentals Presentation_ID © 2010 Cisco and/or its affiliates.

Cisco Public 7 . All rights reserved.Cisco EVC Building Blocks Cisco EVC uses the following new concepts:  Ethernet Service Instance Transport-agnostic abstraction of an Ethernet service on an interface  Ethernet Virtual Circuit (EVC) Device local object (container) for network-wide service parameters  Bridge Domain (BD) Ethernet Broadcast Domain local to a device  Bridge Domain Interface (BDI) –Logical Layer 3 interface associated with a BD to perform integrated routing and bridging Presentation_ID © 2010 Cisco and/or its affiliates.

All rights reserved.Cisco EVC Building Blocks Ethernet Service Instance CE A2 CE A3 EVC Blue CE A1 CE B2 CE B1 Service Instance EFP EFP EFP Interface EVC Red  Instance of a MEF EVC on a port  Also defined as Ethernet Flow Point (EFP)  Classify frames belonging to a particular Ethernet Service  Apply features selectively to service frames  Define forwarding actions and behavior Presentation_ID © 2010 Cisco and/or its affiliates. Cisco Public 8 .

Cisco EVC Building Blocks Ethernet Virtual Circuit EVC EVC Service Instance Management Plane EFP EFP Interface EFP  Representation of a MEF EVC on the device  Management Plane container  Hosts global EVC attributes  One-to-many mapping from EVC to Service Instance Presentation_ID © 2010 Cisco and/or its affiliates. Cisco Public 9 . All rights reserved.

All rights reserved.Cisco EVC Building Blocks Bridge Domain EVC EVC Service Instance Management Plane EFP EFP EFP Bridge Domain Interface  Broadcast Domain internal to the device  Allows decoupling broadcast domain from VLAN  Per port VLAN significance  One-to-many mapping from BD to Service Instances Presentation_ID © 2010 Cisco and/or its affiliates. Cisco Public 10 .

VLAN Bridge VLAN VLAN Bridge Domain Service Instance VLAN VLAN Bridge EVC Bridge  VLAN bridge has 1:1 mapping between VLAN and internal Broadcast Domain –VLAN has global per-device significance  EVC bridge decouples VLAN from Broadcast Domain –VLAN treated as encapsulation on a wire  VLAN on a wire mapped to internal Bridge Domain via Service Instances –Net result: per-port VLAN significance Presentation_ID © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Public 11 .Cisco EVC Building Blocks Bridge Domain vs.

multiple access VLANs to a service  Forwarding services include: –L2 point-to-point local connect –L2 point-to-point xconnect –L2 multipoint bridging –L2 multipoint VPLS –L2 point-to-multipoint bridging –L3 termination Presentation_ID © 2010 Cisco and/or its affiliates.Multiplexed Forwarding Services  Cisco EVC supports flexible access VLAN to forwarding service mapping –1-to-1 access VLAN to a service –Same port. All rights reserved. Cisco Public 12 . multiple access VLANs to a service –Multiple ports.

Cisco Public .Multiplexed Forwarding Services  Layer 2 P2P local services –No MAC learning –Two Service Instances (EFP) on same interface (hair-pin) –Two EFPs on different interfaces Local Hair-Pin Layer 2 Point-to-Point BD Split Horizon  Layer 2 MP bridged services –MAC based fwd and learning –Local VLAN significance –Bridge Domain (BD)—different access VLANs in the same broadcast domain –Split-horizon—prevent communication between service instances Layer 2 Multipoint bridged VFI = Virtual Fwd Instance SVI = Switch Virtual Instance 13 Service BD = Bridge Domain Instances PW Local and Bridged P2P and MP Forwarding Services = Pseudowire Presentation_ID © 2010 Cisco and/or its affiliates. All rights reserved.

Multiplexed Forwarding Services  Layer 2 P2P services using Ethernet over MPLS –EFP to EoMPLS PW PW BD VFI PW PW  Layer 2 MP services using VPLS –Extends ethernet multipoint bridging over a full mesh of PWs –Split horizon support over attachment circuits (configurable) and PWs Layer 2 Multipoint VPLS Layer 2 Point-to-Point EoMPLS BD = Bridge Domain PW = Pseudowire Cisco Public MPLS-Based P2P and MP Forwarding Services Presentation_ID © 2010 Cisco and/or its affiliates. VFI = Virtual Fwd Instance SVI = Switch Virtual Instance 14 . All rights reserved.

All rights reserved. Cisco Public 15 .Multiplexed Forwarding Services Rooted-Multipoint Forwarding Services (E-TREE)  BD with Split Horizon Group can be used to implement rooted-multipoint forwarding service: –Place all Leaf EFPs in Split Horizon Group –Keep Root EFP outside the Split Horizon Group  Net effect: –Bidirectional connectivity between Root and all Leaf EFPs –Leaf EFPs cannot communicate to each other Root Service Instance Bridge Domain Leaf EFP BD Leaf EFP Interface Leaf EFP Split Horizon Group Presentation_ID © 2010 Cisco and/or its affiliates.

All rights reserved.Multiplexed Forwarding Services  Co-existence with Routed sub-interfaces  Layer 3 termination through SVI/BDI interface BD Layer 3 IP / L3VPN via SVI or BDI BD BD SVI/BDI Layer 3 IP / L3VPN via sub-int  Layer 3 termination through Routed sub-interfaces Layer 3 Forwarding Services Presentation_ID © 2010 Cisco and/or its affiliates. Cisco Public BD = Bridge Domain VFI = Virtual Fwd Instance PW = PseudowireSVI = Switch Virtual Instance BDI = Bridge Domain Interface 16 .

All rights reserved. 17 .Multiplexed Forwarding Services  Multiplexed Service Interface  Mix of L2 and L3 services on same port  Different types of L2 services –Point-to-Point –Multipoint BD Service Instances PW BD BD VFI PW PW SVI/BDI Putting It All Together Presentation_ID BD = Bridge Domain VFI = Virtual Fwd Instance PW = PseudowireSVI = Switch Virtual Instance BDI = Bridge Domain Interface Cisco Public © 2010 Cisco and/or its affiliates.

Operation and Packet Flow Presentation_ID © 2010 Cisco and/or its affiliates. Cisco Public 18 . All rights reserved.

All rights reserved. Output Features Frame Filtering Cisco Public 19 .Packet Flow Pipeline Flexible Service Mapping Inbound EFP Forwarder Egress Interface Outbound EFP Ingress Encapsulation Adjustment Input Features Ingress Interface Egress Encapsulation Adjustment Presentation_ID © 2010 Cisco and/or its affiliates.

80 600 PPPoE S-VLAN C-VLAN 400 COS 5 500 COS 2-5 Cisco Public 20 . All rights reserved.Flexible Service Mapping Comprehensive Matching  Service Instance construct classifies L2 flows on Ethernet interfaces  Single Tagged PORT CapabilitiesGE / 10GE Untagged 70 40 10 11 19 12 300 70 90 20 21 30 22 50  Double Tagged  Header/Payload 100 10 10 200 12 11 Ethernet Service Instances Presentation_ID © 2010 Cisco and/or its affiliates.

All rights reserved. 21 .Flexible Service Mapping Loose Match Classification Rule  Cisco EVC follows a Loose Match classification model  Unspecified fields are treated as wildcard  encapdot1q 10 matches any frame with outer tag equal to 10 10 10 50  encapdot1q 10 sec 50 matches any frame with outer-most tag as 10 and second tag as 50 10 50 10 Presentation_ID 50 4 Cisco Public © 2010 Cisco and/or its affiliates.

All rights reserved. Cisco Public .Flexible Service Mapping Longest Match Classification Rule  Cisco EVC follows a Longest Match classification model  Frames are mapped to Service Instance with longest matching set of classification fields EFP 10 VLAN 10 S-VLAN 10 10 100 C-VLAN 100 S-VLAN 10 C-VLAN 128-133 10 130 Interface 22 10 200 Presentation_ID © 2010 Cisco and/or its affiliates.

Cisco Public Default EFP 23 .Flexible Service Mapping Service Instance with ‗Default‘ Encapsulation  Matches all frames unmatched by any other EFP on a port VLAN 10 VLAN 20 VLAN 10 VLAN 20 VLAN 50 Untagged Interface EFP Default  If default Service Instance is the only one configured on a port. All rights reserved. it matches all traffic on the port (tagged and untagged) VLAN 10 VLAN 20 VLAN 50 Untagged Interface Presentation_ID © 2010 Cisco and/or its affiliates.

1 400.11 400. inner VLAN range: 1-3 Match outer 400. 210 Match VLAN: 300.17 400.34 300. All rights reserved.100 Match outer VLAN 400. Cisco Public 24 .17. inner VLAN list: 11.2 400.Flexible Frame Matching Examples Ethernet Flow Points  Provide classification of L2 flows on Ethernet interfaces  Are also referred to as EVC service-instances  Support dot1q and Q-in-Q EFPs on Interface Match VLAN: 14 100 101 102 Physical Ethernet interface (GE/10GE) 14 Match VLAN range: 100-102  Support VLAN lists  Support VLAN ranges  Support VLAN Lists and Ranges combined  Coexist with routed subinterfaces 200 203 210 Match VLAN list: 200.34 Presentation_ID © 2010 Cisco and/or its affiliates.3 400. 203.10 0 400.

All rights reserved. Cisco Public 25 .Operation and Packet Flow Advanced Frame Manipulation Presentation_ID © 2010 Cisco and/or its affiliates.

Advanced Frame Manipulation PUSH Operations  Add one VLAN tag DA SA 20 DA SA 25 20  Add two VLAN tags DA SA DA SA 25 31 Presentation_ID © 2010 Cisco and/or its affiliates. Cisco Public 26 . All rights reserved.

All rights reserved. Cisco Public 27 .Advanced Frame Manipulation POP Operations  Remove one VLAN tag DA SA 20 DA SA 25 20  Remove two VLAN tags DA SA DA SA 25 31 DA SA 10 20 DA SA 20 DA SA 10 20 DA SA Presentation_ID © 2010 Cisco and/or its affiliates.

Advanced Frame Manipulation Translation Operations  1:1 VLAN Translation DA SA 20 DA SA 25 20  1:2 VLAN Translation  2:1 VLAN Translation  2:2 VLAN Translation DA SA DA SA 25 31 DA SA 10 20 DA SA 20 DA SA 10 20 DA SA DA SA 10 DA SA 25 DA SA 10 DA SA 25 31 DA SA 10 20 DA SA 31 DA SA 10 20 DA SA 25 31 Presentation_ID © 2010 Cisco and/or its affiliates. Cisco Public 28 . All rights reserved.

Advanced Frame Manipulation VLAN Tag Manipulation  PUSH operations DA SA 20 DA SA 25 20  POP operations  TRANSLATION operations DA SA DA SA 25 31 DA SA 10 20 DA SA 20 DA SA 10 20 DA SA DA SA 10 DA SA 25 DA SA 10 DA SA 25 31 DA SA 10 20 DA SA 31 DA SA 10 20 DA SA 25 31 Presentation_ID © 2010 Cisco and/or its affiliates. Cisco Public 29 . All rights reserved.

Configuration Presentation_ID © 2010 Cisco and/or its affiliates. Cisco Public 30 . All rights reserved.

All rights reserved. Cisco Public L3 VRF 31 .Cisco EVC Configuration Anatomy Global EVC ethernet evc <evc-name> EFP service instance <id> ethernet <evc-name> Per Port Per EVC Features interface service instance <id> ethernet <evc-name> Per Port Per EVC Features sub-interface Per Sub-interface Features (L3) Layer 2 Services Bridging (VPLS via SVI) xconnect (EoMPLS) Local Connect Presentation_ID © 2010 Cisco and/or its affiliates.

 ―On the wire‖ is defined as packets ingressing the switch prior to any rewrites. does not match any of the Encapsulations on that port. This ―filtering‖ happens both on Ingress and Egress. then that packet is dropped. All rights reserved.  If a packet entering a port. and packets egressing the switch after all rewrites. Cisco Public 32 .  The Encapsulation matches the packet on the wire to determine filtering criteria.Encapsulation  Encapsulation matching is done on a most to least specific basis. Presentation_ID © 2010 Cisco and/or its affiliates.

Cisco Public 33 . for example control traffic  Default encapsulation default Match all frames (tagged/untagged) not matched by more specific service instances Presentation_ID © 2010 Cisco and/or its affiliates. range or multiple  Untagged Frame encapsulation untagged Match un-tagged frames.<vlan-id>[-<vlan-id>]]”} VLAN tag can be single. All rights reserved.<vlan-id>[-<vlan-id>]]”} First vlan tag must be unique. unique. multiple or range or any (1-4094)  Double-Tagged Frame encapsulation dot1q <vlan-id> second-dot1q {any | “<vlan-id>[. second vlan tag can be any.1Q Virtual LAN or S-VLAN untagged Untagged encapsulation  Single-Tagged Frame encapsulation dot1q {any | “<vlan-id>[.Configuring Flexible Service Mapping interface GigabitEthernet 2/1 service instance 1 ethernet encapsulation ? default catch-all unconfigured encapsulation dot1q IEEE 802.

<vlan-id>[-<vlan-id>]]” | etype [IPv4|IPv6|pppoe-all]}  Double-Tagged Frame and payload Ether-Type encapsulation dot1q<vlan-id> second-dot1q {“<vlan-id>[.1Q Virtual LAN or S-VLAN untagged Untagged encapsulation  Single-Tagged Frame and payload Ether-Type encapsulation dot1q {“<vlan-id>[.<vlan-id>[-<vlan-id>]]” | cos<cos-id>[. Cisco Public 34 .<vlan-id>[-<vlan-id>]]” | etype [IPv4|IPv6|pppoe-all]}  Single-Tagged Frame and COS encapsulation dot1q {“<vlan-id>[.) interface GigabitEthernet 2/1 service instance 1 ethernet encapsulation ? default catch-all unconfigured encapsulation dot1q IEEE 802.<cos-id>[-<cos-id>]]}  Double-Tagged Frame and Outer COS encapsulation dot1q<vlan-id>{cos<cos-id>[.<vlan-id>[-<vlain-id>]]” | cos<cos-id>[.<cos-id>[<cos-id>]]}  Double-Tagged Frame and Inner COS encapsulation dot1q<vlan-id> second-dot1q {“<vlan-id>[.Configuring Flexible Service Mapping (cont.<vlan-id>[-<vlan-id>]]”} Presentation_ID © 2010 Cisco and/or its affiliates.<cos-id>[-<cos-id>]]} second-dot1q {“<vlan-id>[. All rights reserved.

Presentation_ID © 2010 Cisco and/or its affiliates.Rewrite  The “Rewrite” command allows for packet vlan tag modifications. and vlan tagging properties are added on egress. where packets going into a switch travel native.  This command can be used to emulate traditional dot1q tagging.  This can also be used to facilitate vlan translation. Cisco Public 35 . All rights reserved. and Q-in-Q.

Cisco Public 36 .Configuring Advanced Frame Manipulation  POP Operations rewrite ingress tag pop 1 symmetric rewrite ingress tag pop 2 symmetric interface GigabitEthernet 2/1 service instance 1 ethernet encapsulation dot1q 10 rewrite ingress tag ? pop Pop the tag push Rewrite Operation of push translate Translate Tag  PUSH Operations rewrite ingress tag push dot1q 10 symmetric Automatic mirror egress operation rewrite ingress tag push dot1q 10 second-dot1q 20 symmetric  TRANSLATION Operations rewrite ingress tag translate 1-to-1 dot1q 100 symmetric rewrite ingress tag translate 1-to-2 dot1q 100 second-dot1q 200 symmetric rewrite ingress tag translate 2-to-1 dot1q 100 symmetric rewrite ingress tag translate 2-to-2 dot1q 100 second-dot1q 200 symmetric Presentation_ID © 2010 Cisco and/or its affiliates. All rights reserved.

EVC Configuration Example interface GigabitEthernet0/2 switchport trunk allowed vlan none switchport mode trunk service instance 10 ethernet encapsulation dot1q 10 rewrite ingress tag pop 1 symmetric bridge-domain 10 Service Instance Frame Matching Required for EFP Configuration Required for EFP Configuration Rewrite Operation Forwarding Presentation_ID © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Public 37 .

Cisco Public 38 . All rights reserved.0.0.3 101 encapsulation mpls Presentation_ID © 2010 Cisco and/or its affiliates.Configuring Point-to-Point Services Point-to-point local connect connect <name><interface-type/slot/port><EFP-id><ethernet-type/slot/port><EFPid> interface GigabitEthernet4/1/0 service instance 3 ethernet encapsulation dot1q 51 rewrite ingress tag translate 1-to-2 dot1q 52 second-dot1q 52 symmetric interface GigabitEthernet4/1/1 service instance 4 ethernet encapsulation dot1q 52 second-dot1q 52 connect eline-sample GigabitEthernet4/1/0 3 GigabitEthernet4/1/1 4 Point-to-point xconnect xconnect<peer-add><VC-ID> encapsulation mpls interface GigabitEthernet4/1/1 service instance 11 ethernet encapsulation dot1q 101 second-dot1q 60-70 xconnect 10.

1.1.1 encap dot1q 20 xconnect 1.2 100 encap mpls Correct Configuration service instance 3 ethernet encapsulation dot1q 10 rewrite ingress tag pop 1 symmetric xconnect 1.2 100 encap mpls 10 Dummy VLAN PW Type 4 tag 10 20 10 20 20 PROBLEM .1 100 encap mpls Incorrect Configuration service instance 3 ethernet encapsulation dot1q 10 xconnect 1.1.1. Cisco Public 39 .1.Encapsulation Adjustment Considerations PW VC Type and EVC VLAN rewrites (cont. EVC device must be configured to POP EVC’s context service delimiter VLAN Presentation_ID © 2010 Cisco and/or its affiliates. All rights reserved.VLAN tag mismatch on attachment circuits !!! In most cases.) IP/MPLS PE-1 PE-2 VLAN Mode Interface GigabitEthernet 1/1.1.

Configuring Multipoint Services Multipoint Native Ethernet Bridging and VPLS bridge-domain <global-vlan-id> [split-horizon]  Split-horizon to disable L2 communication between two Service Instances (optional) Local Bridging interface GigabitEthernet4/1/0 service instance 2 ethernet encapsulation dot1q 101-1000 bridge-domain 100 interface GigabitEthernet4/1/1 service instance 3 ethernet encapsulation dot1q 101-1000 bridge-domain 100 interface GigabitEthernet4/1/2 service instance 1 ethernet encapsulation dot1q 101-1000 bridge-domain 100 VPLS interface GigabitEthernet4/1/0 service instance 2 ethernet encapsulation dot1q 60 bridge-domain 20 interface GigabitEthernet4/1/1 service instance 3 ethernet encapsulation dot1q 61 bridge-domain 20 interface Vlan20 xconnect vfi vpls-sample Presentation_ID © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Public 40 .

All rights reserved.Configuring Point-to-Multipoint Services Multipoint Native Ethernet Bridging and VPLS bridge-domain <global-vlan-id> [split-horizon]  Disables communication between leaf Service Instances in Split Horizon Group Local Bridging interface GigabitEthernet4/1/0 service instance 2 ethernet encapsulation dot1q 101-1000 bridge-domain 100 split-horizon interface GigabitEthernet4/1/1 service instance 3 ethernet encapsulation dot1q 101-1000 bridge-domain 100 split-horizon interface GigabitEthernet3/1/2 service instance 1 ethernet encapsulation dot1q 101-1000 bridge-domain 100 Leaf Gig3/1/2 Root Bridge Domain Gig4/1/1 Leaf Leaf BD X Leaf Gig4/1/0 41 Root Split Horizon Group Presentation_ID © 2010 Cisco and/or its affiliates. Cisco Public .

0 POP mandatory for IP termination Presentation_ID © 2010 Cisco and/or its affiliates.1.0 Option 2 interface GigabitEthernet4/1/1.255.100.1.1. Cisco Public 42 .255.255.255.0 Option 2 interface GigabitEthernet4/1/1.100.100.1 255.0 Double tag termination Option 1 interface GigabitEthernet4/1/1 service instance 666 ethernet encapsulation dot1q 200 second 300 rewrite ingress tag pop 2 symmetric bridge-domain 100 interface Vlan100 ip address 100.1.1 255. All rights reserved.100.Configuring Layer 3 Services Single tag termination Option 1 interface GigabitEthernet4/1/1 service instance 666 ethernet encapsulation dot1q 200 rewrite ingress tag pop 1 symmetric bridge-domain 100 interface Vlan100 ip address 100.255.1 255.255.1 255.200 encapsulation dot1q 200 ip address 100.200 encapsulation dot1q 200 second 300 ip address 100.255.255.

the frame is flooded to all the ports within the bridge domain. source MAC addresses. Cisco Public 43 . and EFP is known.  MAC address learning is based on bridge domain ID.  The frame is forwarded to an EFP if the binding between the bridge domain.  If there is no matching entry in the Layer 2 forwarding table for the ingress frame. All rights reserved. and logical port number. Presentation_ID © 2010 Cisco and/or its affiliates. Learning and Aging on EFPs  Layer 2 forwarding is based on the bridge domain ID and the destination MAC address. destination MAC address.Forwarding.

Presentation_ID © 2010 Cisco and/or its affiliates.  The default for aging dynamic addresses is 5 minutes.Forwarding. Learning and Aging on EFPs (cont.)  You can disable learning on a bridge domain by entering the global configuration command –―no mac address-table learning bridge-domain <bridge-id>‖  Dynamic addresses are aged out if there is no frame from the host with the MAC address. Cisco Public 44 . All rights reserved.

The range is in seconds. Cisco Public 45 .)  You can configure dynamic address aging time per VLAN by entering the command. Learning and Aging on EFPs (cont. Presentation_ID © 2010 Cisco and/or its affiliates. All rights reserved.Forwarding. – mac address-table aging time [0 | 10-1000000] bridgedomain bridge-id  An aging time of 0 means that the address aging is disabled.  MAC address movement is detected when the host moves from one port to another.

All rights reserved. Presentation_ID © 2010 Cisco and/or its affiliates. Cisco Public 46 . –Load-balancing is performed based on MAC address or IP address of the traffic flow on the bundle interface.Etherchannel/L2 Protocols  EVC on etherchannels –EVC can be configured under bundle interface.

lacp. dtp. then it is dropped at the interface. the command to do this is: ―l2protocol tunnel ― interface GigabitEthernet0/4 service instance 20 ethernet encapsulation untagged. stp. 47 . pagp.  CSCtf72829 L2PT Presentation_ID UDLD & LLDP tunneling option is missing for Cisco Public © 2010 Cisco and/or its affiliates. vtp  If a protocol is not listed in <protocols>. All rights reserved.Etherchannel/L2 Protocols  To enable L2PT. dot1q 200 second-dot1q 300 l2protocol tunnel cdp stp vtp dtp page lacp bridge-domain 10  Valid <protocols> include: cdp.

but in different splithorizon group  If a service instance does not belong to a group.  Service instances in the same bridge domain and split-horizon group –They cannot forward data between each other –They can forward data between other service instances that are in the same bridge domain. All rights reserved.Split-Horizon  The split-horizon feature allows service instances in a bridge domain to join groups. it can send and receive from all ports within the bridge domain.  A service instance cannot join more than one splithorizon group Presentation_ID © 2010 Cisco and/or its affiliates. Cisco Public 48 .

Cisco Public 49 . Service Instances 1 and 2 cannot forward and receive packets from each other. Interface Gi0/1 Service Instance 1 Ethernet Encapsulation dot1q 10 Rewrite ingress pop 1 symmetric Bridge-Domain 8000 Split-Horizon Group 1 Service Instance 2 Ethernet Encapsulation dot1q 99 Rewrite ingress pop 1 symmetric Bridge-Domain 8000 Split-Horizon Group 1 Interface Gi0/2 Service Instance 3 Ethernet Encapsulation dot1q 10 Rewrite ingress pop 1 symmetric Bridge-Domain 8000 Split-Horizon Group 2 Service Instance 4 Ethernet Encapsulation dot1q 99 Rewrite ingress pop 1 symmetric Bridge-Domain 8000    In this example. Service Instance 4 can talk to everyone in Bridge-Domain 8000 since it has not joined any Split-Horizon Groups.. Presentation_ID © 2010 Cisco and/or its affiliates.Split-Horizon contd. All rights reserved. Service Instance 3 can talk to everyone in Bridge-Domain 8000 since no one is in Split-Horizon Group 2.

Presentation_ID © 2010 Cisco and/or its affiliates. Layer 2 protocol tunneling is supported on EFPs.  ME3800X and ME3600X switches. All rights reserved. but not on switchports.CDD0) upon network entry and exit  Cisco‘s Layer 2 protocol tunneling address is treated as unknown multicast data. Cisco Public 50 .L2 Protocol Tunneling  Layer 2 protocol tunneling converts the customer BPDU to a Cisco-known MAC destination address (0100.0CCD.

. vtp  If a protocol is not listed in <protocols>. then it is dropped at the interface. lacp. All rights reserved.L2 Protocol Tunneling contd. dtp. Cisco Public 51 . stp. Presentation_ID © 2010 Cisco and/or its affiliates.. dot1q 200 second-dot1q 300 l2protocol tunnel cdp stp vtp dtp page lacp bridge-domain 10  Valid <protocols> include: cdp. the command to do this is: ―l2protocol tunnel ― interface GigabitEthernet0/4 service instance 20 ethernet encapsulation untagged.  To enable L2PT. pagp.

EFP information is not passed to the protocol. Presentation_ID © 2010 Cisco and/or its affiliates.  When STP mode is PVST+ or PVRST.EFPs and MSTP  EFP bridge domains are supported by MSTP. All rights reserved. you must configure backup EFPs on every redundant path to prevent loss of connectivity due to STP blocking a port. Cisco Public 52 .  All incoming VLANs (outer-most or single) mapped to a bridge domain must belong to the same MST instance or loops could occur.  For all EFPs that are mapped to the same MST instance.  These restrictions apply when running STP with bridge domains.

All rights reserved.Operation and Packet Flow EVC Interaction with Switchport Presentation_ID © 2010 Cisco and/or its affiliates. Cisco Public 53 .

Untagged to Tagged Packet INGRESS UNI interface GigabitEthernet0/1 port-type nni switchport access vlan 10 interface GigabitEthernet0/1 port-type nni switchport trunk native vlan 10 switchport mode trunk *By defalult untagged goes to vlan 1. Cisco Public 54 . to change the behavior use the command “native vlan 10” under trunk EGRESS NNI interface GigabitEthernet0/2 switchport mode trunk Bridged to VLAN 10 Untagged Packet Ingress Switchport Gig 0/1 PUSH TAG 10 Egress Switchport Gig 0/2 VLAN 10 (CTAG) Traffic Direction Switchport: Implicit push on egress & implicit pop on ingress Presentation_ID © 2010 Cisco and/or its affiliates. All rights reserved.

All rights reserved. Cisco Public 55 .Untagged to Tagged Packet INGRESS UNI interface GigabitEthernet0/1 switchport trunk allowed vlan none switchport mode trunk service instance 10 ethernet encapsulation untagged bridge-domain 10 EGRESS NNI interface GigabitEthernet0/2 switchport mode trunk Untagged Packet INGRESS EFP Gig 0/1 Switch Under Test Egress Switchport PUSH Gig 0/2 VLAN 10 (CTAG) Traffic Direction Switchport: Implicit push on egress & implicit pop on ingress Presentation_ID © 2010 Cisco and/or its affiliates.

Cisco Public 56 .QinQ Configuration (EFP to Switchport) INGRESS UNI interface GigabitEthernet0/1 switchport trunk allowed vlan none switchport mode trunk service instance 10 ethernet encapsulation dot1q 10 bridge-domain 100 EGRESS NNI interface GigabitEthernet0/2 switchport mode trunk TAG 10 VLAN 10 (C-TAG) INGRESS EFP Gig 0/1 Switch Under Test Egress Switchport VLAN 100 (S-TAG) PUSH VLAN 10 (C-TAG) Gig 0/2 Traffic Direction Switchport: Implicit push on egress & implicit pop on ingress Presentation_ID © 2010 Cisco and/or its affiliates. All rights reserved.

All rights reserved.Selective QinQ Configuration INGRESS UNI interface GigabitEthernet0/1 switchport trunk allowed vlan none switchport mode trunk service instance 10 ethernet encapsulation dot1q 10-20 bridge-domain 100 service instance 20 ethernet encapsulation dot1q 20-30 bridge-domain 200 EGRESS NNI interface GigabitEthernet0/2 switchport mode trunk TAG 10-20 TAG 20-30 VLAN 10-20 (C-TAG) VLAN 20-30 (C-TAG) INGRESS EFP Gig 0/1 Switch Under Test Egress Switchport PUSH Gig 0/2 VLAN 100. Cisco Public 57 . 10-20 VLAN 200. 20-30 Traffic Direction Switchport: Implicit push on egress & implicit pop on ingress Presentation_ID © 2010 Cisco and/or its affiliates.

Cisco Public 58 . All rights reserved.QinQ Configuration (EFP to EFP) INGRESS UNI interface GigabitEthernet0/1 switchport trunk allowed vlan none switchport mode trunk service instance 10 ethernet encapsulation dot1q 1-50 bridge-domain 5000 EGRESS UNI interface GigabitEthernet0/2 switchport trunk allowed vlan none switchport mode trunk service instance 10 ethernet encapsulation dot1q 100 rewrite ingress tag pop 1 symmetric bridge-domain 5000 BD 5000 VLAN 1-50 (C-TAG) INGRESS EFP Gig 0/1 Switch Under Test Egress EFP Gig 0/2 VLAN 100 (S-TAG) VLAN 1-50 (CTAG) Traffic Direction Presentation_ID © 2010 Cisco and/or its affiliates.

Why is it Important: This removes the need for coordinate the CVLANs with customers.1:1 VLAN Mapping Layer 2 VPN Service Offering Multi-Tenant Unit Customer A Headquarters Customer CPE Customer-A VLAN . Allowing more Flexible Service Delivery Presentation_ID © 2010 Cisco and/or its affiliates.10 Customer CPE Customer CPE UNI Problem: Customer-A and Customer-B have the overlapping VLANs configured on their networks and the service provider does NOT want to deploy QinQ. All rights reserved. Cisco Public 59 .10 Customer CPE UNI Service Provider Network MPLS Core with dot1Q Ethernet Access Domain UNI 0/1 Customer B Headquarters UNI 0/2 Customer-B VLAN .

All rights reserved. Cisco Public 60 .UNI with 1:1 Translation (EFP to EFP) INGRESS UNI interface GigabitEthernet0/1 switchport trunk allowed vlan none switchport mode trunk service instance 10 ethernet encapsulation dot1q 10 rewrite ingress tag pop 1 symmetric bridge-domain 10 EGRESS UNI interface GigabitEthernet0/2 switchport trunk allowed vlan none switchport mode trunk service instance 10 ethernet encapsulation dot1q 20 rewrite ingress tag pop 1 symmetric bridge-domain 10 VLAN 10 INGRESS EFP POP Gig 0/1 UNTAG Switch Under Test Traffic Direction EGRESS EFP PUSH Gig 0/2 VLAN 20 Presentation_ID © 2010 Cisco and/or its affiliates.

1:2 VLAN Mapping / Selective QinQ Layer 2 VPN Service Offering: MEF. Ethernet Virtual Private Line Service •Leverages Selective QinQ (1:2 VLAN Mapping) on ME ME3800X/ME3600X with multiplexed UNI •Uses EVC (Flexible UNI) infrastructure •Adds / Removes Service Provider VLAN (S-VLAN) based upon the Customer (CE-VLAN) mapping •EVPL serves as a replacement for lower speed Frame Relay service offerings •The New ME3800X/ME3600X ASIC allows the user full flexibility of marking the SVLAN Tag COS marking based on the Customer CoS / DSCP / IP Prec marking Cisco Public 61 .EVPL Customer A Remote Branch # 1 Push QinQ Tag Customer A Headquarters Customer CPE UNI Customer CPE UNI Service Provider Network Pop QinQ Tag Customer A Remote Branch # 2 MPLS Core with QinQ Ethernet Access Domain UNI Customer CPE Pop QinQ Tag Presentation_ID © 2010 Cisco and/or its affiliates. All rights reserved.

VLAN 30 (C-VLAN) Traffic Direction Presentation_ID © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Public 62 .UNI with 1:2 Translation (EFP to EFP) INGRESS UNI interface GigabitEthernet0/1 switchport trunk allowed vlan none switchport mode trunk service instance 10 ethernet encapsulation dot1q 10 rewrite ingress tag pop 1 symmetric bridge-domain 10 EGRESS UNI interface GigabitEthernet0/2 switchport trunk allowed vlan none switchport mode trunk service instance 10 ethernet encapsulation dot1q 20 second-dot1q 30 rewrite ingress tag pop 2 symmetric bridge-domain 10 UNTAG VLAN 10 INGRESS POP Gig 0/1 Switch Under EGRESS PUSH Gig 0/2 VLAN 20.

L2 VPN

QinQ with 2:1 Translation
• Provides Port Isolation allowing multiple customers single switch to have same internal Vlans • Flexibility for Service Provider to choose Vlans to pass over Core • Does NOT require mixing of Customer and Provider Vlans

Customer A Dot1Q Tunnel Dot1Q Tunnel

Customer B Customer A Customer B

Presentation_ID

© 2010 Cisco and/or its affiliates. All rights reserved.

Cisco Public

63

UNI with 2:1 Translation (EFP to EFP)
INGRESS UNI interface GigabitEthernet0/1 switchport trunk allowed vlan none switchport mode trunk service instance 10 ethernet encapsulation dot1q 10 second-dot1q 20 rewrite ingress tag pop 2 symmetric bridge-domain 10 EGRESS UNI interface GigabitEthernet0/2 switchport trunk allowed vlan none switchport mode trunk service instance 10 ethernet encapsulation dot1q 30 rewrite ingress tag pop 1 symmetric bridge-domain 10

UNTAG

VLAN 10, VLAN 20 (C-VLAN)

INGRESS POP
Gig 0/1

EGRESS PUSH
Gig 0/2

VLAN 30

Traffic Direction
Presentation_ID © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Public

64

UNI with 2:2 Translation (EFP to EFP)
INGRESS UNI interface GigabitEthernet0/1 switchport trunk allowed vlan none switchport mode trunk service instance 10 ethernet encapsulation dot1q 10 second-dot1q 20 rewrite ingress tag pop 2 symmetric bridge-domain 10 EGRESS UNI interface GigabitEthernet0/2 switchport trunk allowed vlan none switchport mode trunk service instance 10 ethernet encapsulation dot1q 30 second-dot1q 40 rewrite ingress tag pop 2 symmetric bridge-domain 10

UNTAG

VLAN 10, VLAN 20 (C-VLAN)

INGRESS POP
Gig 0/1

Switch Under

EGRESS PUSH
Gig 0/2

VLAN 30, VLAN 40 (C-VLAN)

Traffic Direction
Presentation_ID © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Public

65

Bridge Domain Routing  The bridge-domain can only be between 1-4K range since SVI interfaces can be configured in that range only.  We need SVI interfaces for bridge-domain routing  There can only be one EFP in the bridge-domain. MPLS is not supported.  The EFP must make the packet native for Bridge-domain routing to work.  L3VPN/L2VPN configuration is supported Presentation_ID © 2010 Cisco and/or its affiliates. All rights reserved.  There can not be any switchport as well in the same VLAN/bridge-domain. Cisco Public 66 .  This is fundamental for IP routing purposes since IP router routes a IP datagram  Only IP is supported.

255. Cisco Public 67 .1.255. All rights reserved.255 Presentation_ID © 2010 Cisco and/or its affiliates.One/ Two Tag EFP int gi0/1 switchport trunk allowed vlan none switchport mode trunk service instance 1 ethernet encapsulation dot1q 10 second-dot1q 20 rewrite ingress tag pop 1 symmetric bridge-domain 100 int vlan 100 ip address 20.1.1 255.

All rights reserved. Cisco Public 68 .Operation and Packet Flow Monitoring EFP Presentation_ID © 2010 Cisco and/or its affiliates.

All rights reserved. Cisco Public •show mac address-table bridge-domain bridgedomain id •show mac address-table count bridge-domain bridge-domain id •show mac address-table learning bridge-domain bridge-domain id Presentation_ID © 2010 Cisco and/or its affiliates. 69 .Monitoring EFP show ethernet service [id evc-id | interface interface-id] [detail] show bridge-domain [n] show bridge-domain n split-horizon [group {group_id | all}] show mac address-table Displays information about EVC Displays all the members of the specified bridge-domain Displays all the members of bridgedomain n that belong to split horizon group Displays dynamically learned or statically configured MAC security addresses Displays MAC address table information for the specified bridge domain.

All rights reserved. Cisco Public 70 .Monitoring EFP 3600-HL-1#sh ethernet service instance id 10 interface gigabitEthernet 0/7 detail Service Instance ID: 10 Associated Interface: GigabitEthernet0/7 Associated EVC: L2protocol drop CE-Vlans: Encapsulation: dot1q 10 vlan protocol type 0x8100 Rewrite: ingress tag pop 1 symmetric Interface Dot1q Tunnel Ethertype: 0x8100 State: Down EFP Statistics: Pkts In Bytes In 0 0 EFP Microblocks: **************** Microblock type: Bridge-domain Bridge-domain: 10 Pkts Out 0 Bytes Out 0 Presentation_ID © 2010 Cisco and/or its affiliates.

Cisco Public 71 .Monitoring EFP 3600-HL-1#sh bridge-domain 10 Bridge-domain 10 (1 ports in all) State: UP GigabitEthernet0/7 service instance 10 3600-HL-1#show mac address-table bridge-domain 10 Mac Address Table ------------------------------------------BD Mac Address Type Ports ------------------------All 0100.cccc STATIC CPU All 0100.0000.cccd STATIC CPU All 0100.ccce STATIC CPU Presentation_ID © 2010 Cisco and/or its affiliates.0ccc.0000 STATIC CPU All 0100.0ccc. All rights reserved.0ccc.

Cisco Public 72 . All rights reserved.Operation and Packet Flow Service Migration Presentation_ID © 2010 Cisco and/or its affiliates.

Cisco Public  Split-horizon needs to be configured per bridge-domain instead of per port 73 . * Service Instance 4 can talk to everyone in Bridge-Domain 8000 since it has not joined any Split-Horizon Groups. Presentation_ID © 2010 Cisco and/or its affiliates. All rights reserved. we would need a way to drop protocol packets and also a way to create traffic isolation across UNI ports in same bridge domain/VLAN. * Service Instance 3 can talk to everyone in Bridge-Domain 8000 since no one is in Split-Horizon Group 2. Interface Gi0/1 Service Instance 1 Ethernet Encapsulation dot1q 10 Rewrite ingress pop 1 symmetric Bridge-Domain 8000 Split-Horizon Group 1 Service Instance 2 Ethernet Encapsulation dot1q 99 Rewrite ingress pop 1 symmetric Bridge-Domain 8000 Split-Horizon Group 1 Interface Gi0/2 Service Instance 3 Ethernet Encapsulation dot1q 10 Rewrite ingress pop 1 symmetric Bridge-Domain 8000 Split-Horizon Group 2 Service Instance 4 Ethernet Encapsulation dot1q 99 Rewrite ingress pop 1 symmetric Bridge-Domain 8000 * In this example.UNI Service  In order to do UNI functionality. Service Instances 1 and 2 cannot forward and receive packets from each other.

All rights reserved.ENI Service  The ENI service is similar to UNI except that it provides flexibility of understanding customer protocol packets instead of dropping them. Cisco Public 74 . Presentation_ID © 2010 Cisco and/or its affiliates.

Cisco Public 75 . All rights reserved. int gi0/3  NNI (EVC model) switchport trunk allowed vlan none switchport mode trunk service instance 1 ethernet encapsulation 100 bridge-domain 100 int gi0/4  NNI (switchport model) switchport mode trunk Presentation_ID © 2010 Cisco and/or its affiliates.NNI Service  The NNI service is standard dot1q trunking.  The NNI interface can communicate with any other NNI and also any UNI ports (split-horizon enabled).

All rights reserved. Cisco Public 76 .Private VLAN Service  The private VLAN service is typically deployed using two VLANs where one VLAN is used for down interfaces (UNI) and other VLAN is used for uplink interface (NNI). Presentation_ID © 2010 Cisco and/or its affiliates.  This service can be deployed using EVC configuration model in conjunction with split-horizon and we would need only one VLAN/bridge-domain.

 This service can be deployed using EVC configuration model in conjunction with splithorizon. Cisco Public 77 .  The only drawback is that split-horizon need to be enabled per bridge-domain instead of per port but because of this reason it is more flexible. All rights reserved. Presentation_ID © 2010 Cisco and/or its affiliates.Protected port Service  The protected port feature allows UNI kind of functionality.

All rights reserved.Platform Support Presentation_ID © 2010 Cisco and/or its affiliates. Cisco Public 78 .

Cisco Public 79 .Cisco EVC Framework Platform Support Aggregation Access Cisco ASR 9000 Cisco 7600 Cisco ME3600X Cisco ME3800X Cisco ONS 15454 ML-MR linecard Cisco ASR 1000 SIP-400 ES-20 and ES+ linecards Catalyst 6500 Supervisor 2T Presentation_ID © 2010 Cisco and/or its affiliates. All rights reserved.

1 pw-id 22 p2p service3  PW stitching neighbor 2.3.101 l2transport encapsulation dot1q 101 second 10 rewrite ingress tag pop 2 Symmetric Interface gig 0/0/0/2. Qo/ACL features. Cisco Public 80 .3. etc Interface gig 0/0/0/1.2.3 pw-id 101 Presentation_ID © 2010 Cisco and/or its affiliates.101 l2transport encapsulation dot1q 101 rewrite ingress tag pop 1 Symmetric ME3800X/ME3600X interface GigabitEthernet4/1/1 service instance 11 ethernet encapsulation dot1q 101 second-dot1q 60-70 xconnect 10.1.2.101 neighbor 1.0. tag rewrite.EVC Configuration Comparison (IOS XR & IOS) – L2VPN P2P service ASR 9000 EoMPLS EFP configuration under interface Including VLAN tag encapsulation.101 p2p service2  EoMPLS interface gig 0/0/0/3.2 pw-id 100 neighbor 3.3 101 encapsulation mpls Service configuration under “l2vpn” l2vpn xconnect group cisco p2p service1  local connect interface gig 0/0/0/1. All rights reserved.101 interface gig 0/0/0/2.1.0.

0.1 pw-id 100 Presentation_ID © 2010 Cisco and/or its affiliates. etc Same as L2VPN P2P services Service configuration under “l2vpn” 7600 interface GigabitEthernet4/1/0 service instance 101 ethernet encapsulation dot1q 101-1000 bridge-domain 100 split-horizon interface GigabitEthernet4/1/1 service instance 101 ethernet encapsulation dot1q 101-1000 bridge-domain 100 split-horizon interface GigabitEthernet4/1/0 service instance 2 ethernet encapsulation dot1q 20 bridge-domain 20 split-horizon interface GigabitEthernet4/1/1 service instance 2 ethernet encapsulation dot1q 20 bridge-domain 20 split-horizon l2 vfi vpls-20 manual  VPLS vpn id 120 neighbor 10.0.0.0.0.101 Interface gig 0/0/0/2.0. All rights reserved.101 split-horizon group Interface gig 0/0/0/2. tag rewrite. Qo/ACL features.0. bridge-domain domain3  vpls & h-vpls Interface gig 0/0/0/1.1 pw-id 100 interface Vlan20  SVI EoMPLS neighbor 192.1 encapsulation mpls  core PW neighbor 10.0.2 encapsulation mpls no-splithorizon  spoke PW neighbor 10.0.1 101 encap mpls Cisco Public 81 .0.0.101 neighbor 192.4 encapsulation mpls (H-)VPLS & SVI based EoMPLS l2vpn bridge group cisco bridge-domain domain1  local bridging Interface gig 0/0/0/1.0.0.0.0.101 split-horizon group bridge-domain domain2  SVI EoMPLS Interface gig 0/0/0/1.101 neighbor 192.3 pw-id 100  spoke PW interface Vlan20  (H-)VPLS xconnect vfi vpls-20 vfi cisco  core PWs under VFI config neighbor 192.2 pw-id 100 xconnect 10.0.EVC Configuration Comparison (IOS XR & IOS) – L2VPN MP bridging ASR 9000 Local Bridging EFP configuration under interface Including VLAN tag encapsulation.

Acronyms Acronym ACL BD BRAS CE C-VLAN / CE-VLAN CoS Access Control List Bridge Domain Broadband Access Server Customer Equipment (Edge) Customer VLAN Class of Service Acronym IPoETV IPTV MEF MEN MPLS TV on IP over Ethernet Television over IP Metro Ethernet Forum Metro Ethernet Network Multi-protocol Label Switching Operations. All rights reserved. PW Q-in-Q QoS SVI S-VLAN UNI VLAN VoD VoIP VPLS Pseudowire VLAN tunneling using two 802.1Q tags Quality of Service Switch Virtual Interface (interface vlan) Service VLAN (Provider VLAN) User to Network Interface Virtual LAN Video on Demand Voice over IP Virtual Private LAN Service Cisco Public 82 . Administration and Maintenance Provider Edge device OAM PE DSLAM E-LAN E-Line E-Tree EFP EoMPLS EPL EVC EVPL IEEE IETF Presentation_ID DSL Access Modulator Ethernet LAN service (multipoint) Ethernet Line service (point-to-point) Ethernet Tree service (rooted multipoint) Ethernet Flow Point Ethernet over MPLS Ethernet Private Line Ethernet Virtual Connection Ethernet Virtual Private Line Institute of Electrical and Electronics Engineers Internet Engineering Task Force © 2010 Cisco and/or its affiliates.

Presentation_ID © 2010 Cisco and/or its affiliates. Cisco Public 83 .Thank you. All rights reserved.

Introduction to Metro Ethernet Forum (MEF) Ethernet Services Appendix Presentation_ID © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Public 84 .

All rights reserved.MEF Concepts and Terminology CE.3 PHY/MAC Presentation_ID © 2010 Cisco and/or its affiliates.1 bridge/switch CE UNI MEN CE  MEN: –Metro Ethernet Network –Provide Ethernet service to CE –May employ various transports/media UNI UNI CE  UNI: –User-Network Interface –Demarcation between Customer and Provider –IEEE 802. MEN and UNI  CE: –Customer Equipment (Edge) –Router or IEEE 802. Cisco Public 85 .

MEF Service Attributes at a Glance
EVC Attributes
EVC Type
EVC ID UNI List Maximum Number of UNIs EVC Maximum Transmission Unit Size CE-VLAN ID Preservation CE-VLAN CoS Preservation Unicast Service Frame Delivery

UNI Attributes
UNI Identifier Physical Medium Speed Mode MAC Layer UNI MTU Service Multiplexing CE-VLAN for untagged/priority tagged Service Frames Maximum Number of EVCs Bundling All to One Bundling Ingress Bandwidth Profile Per Ingress UNI Egress Bandwidth Profile Per Egress UNI Layer 2 Control Protocols Processing
Cisco Public

EVC Per UNI Attributes
UNI EVC ID CE-VLAN ID/EVC Map Ingress Bandwidth Profile Per EVC Ingress Bandwidth Profile Per COS ID Egress Bandwidth Profile Per EVC Egress Bandwidth Profile Per COS ID

Multicast Service Frame Delivery
Broadcast Service Frame Delivery Layer 2 Control Protocols Processing EVC Performance
Presentation_ID

MEF 10.1 Ethernet Services Attributes
86

© 2010 Cisco and/or its affiliates. All rights reserved.

MEF Concepts and Terminology
Ethernet Virtual Connection (EVC)
CE UNI CE UNI CE UNI

Point-to-Point
UNI CE UNI CE

Multipoint-to-Multipoint

Rooted-Multipoint

UNI CE

UNI CE

UNI CE

UNI CE

 Ethernet Virtual Connection (or Circuit)  Conceptual visualization of an Ethernet Service  ―An association of two or more UNIs‖  Three types:
–Point-to-Point EVC (E-Line)

–Multipoint-to-Multipoint EVC (E-LAN)
–Rooted-Multipoint EVC (E-Tree)
Presentation_ID © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Public

87

MEF Concepts and Terminology
Service Visualization
E-LINE: Ethernet Private Line (EPL) E-LAN: Ethernet Private LAN

E-LINE: Ethernet Virtual Private Line (EVPL)

E-LAN: Ethernet Virtual Private LAN

Presentation_ID

© 2010 Cisco and/or its affiliates. All rights reserved.

Cisco Public

88

All rights reserved.MEF Concepts and Terminology Highlight of UNI Attributes CE CE CE-VLAN subset All UNI CE-VLANs UNI CE UNI UNI UNI CE UNI UNI CE UNI UNI CE Bundling All-to-One Bundling Service Multiplexing  Bundling: More than one CE-VLAN on a UNI mapped to an EVC  All-to-one Bundling: All CE-VLANs on a UNI mapped to a single EVC  Service Multiplexing: Support multiple EVCs over a UNI. EVC selection is based on CE-VLAN value Presentation_ID © 2010 Cisco and/or its affiliates. Cisco Public 89 .

Mapping MEF Services to Cisco EVC Support for Various EVC Types  E-Line: –Associate a point-to-point forwarding service to a Service Instance –Native Transport: Ethernet to Ethernet Local Switching (connect) –MPLS Transport: EoMPLS (xconnect)  E-LAN: –Associate a multipoint forwarding service (Bridge Domain) with EFPs –Native Transport: Ethernet multipoint bridging –MPLS Transport: VPLS  E-Tree: –Associate a rooted-multipoint forwarding service (Bridge Domain with Split Horizon) with Service Instances –Native Transport: Service Instances –MPLS Transport: Service Instances and Pseudowires Presentation_ID © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Public 90 .

Mapping MEF Services to Cisco EVC Support for Bundling and Service Multiplexing CE CE CE-VLAN subset All UNI CE-VLANs UNI CE UNI UNI UNI UNI UNI CE UNI CE UNI Bundling All-to-One Bundling Service Multiplexing CE EFPmatch multiple CE-VLANs EFPmatch all CE-VLANs Different EFPsmatch different CE-VLANs PE Presentation_ID © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Public PE PE 91 .

<vlan-id>[-<vlain-id>]] | any | default | untagged}  UNI Count –PE(config-evc)# uni count {2 [multipoint] to 1024}  UNI Type –PE(config-if)# ethernet uni {bundle [all-to-one] | multiplex}  UNI Name –PE(config-if)# ethernet uni id <uni-name> Presentation_ID © 2010 Cisco and/or its affiliates. All rights reserved.Configuring MEF Attributes  Configuring EVC Identifier –PE(config)# ethernet evc <evc-name>  CE-VLAN ID/EVC Map –PE(config-if-srv)# ethernet lmi ce-vlan map {<vlanid>[. Cisco Public 92 .

All rights reserved. 83. 100 Map multiple C-VLANs to single EVC bridge-domain 3 Presentation_ID © 2010 Cisco and/or its affiliates. Cisco Public 93 .Configuring MEF UNI Variants  Configuring All-to-One Bundling interface GigabitEthernet 1/0/2 service instance 1 ethernet ServiceXYZ  Instantiate an EVC on this port encapsulation default Maps all traffic on interface to single EVC bridge-domain 3  Configuring Bundling interface GigabitEthernet 1/0/2 service instance 1 ethernet ServiceXYZ  Instantiate an EVC on this port encapsulation dot1q 30-50.

All rights reserved.)  Configuring Service Multiplexing interface GigabitEthernet 1/0/2 service instance 1 ethernet ServiceABC  Instantiate first EVC on this port encapsulation dot1q 20-50  This service has bundling as well bridge-domain 3 ! service instance 2 ethernet ServiceXYZ Instantiate second EVC on this port encapsulation dot1q 100  No bundling for this service bridge-domain 40 Presentation_ID © 2010 Cisco and/or its affiliates. Cisco Public 94 .Configuring MEF UNI Variants (cont.