Download pdf - Cisco Live - Service Instance

BRKSPG-2204

Building Carrier Ethernet Services Using Cisco Ethernet Virtual Circuit (EVC) Framework

2009 Cisco Systems, Inc. All rights reserved. Cisco PublicBRKOPT-2204 2

Agenda

Introduction

Cisco EVC Fundamentals

Operation and Packet Flow

Configuration

Mapping to Metro Ethernet Forum (MEF) Services Attributes

Deployment Use CasesResidential / Business Services

Platform Support

Summary

2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKOPT-2204 3

Introduction


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, IEEE, IETF standards


Access Edge

BRAS

SR/PE

DPI

Core NetworkMPLS /IP

Content Farm

VOD TV SIP

DSLResidential

STB

Content Farm

VOD TV SIP

Mobile

ETTx

PON

MSPP

Cable

Business

Corporate

Residential

STB

Aggregation

L2 P-to-P nativeL2 P-to-P over PWL2 MP native bridgingL2 MP VPLSL3 routed

UntaggedSingle taggedDouble tagged802.1q802.1adetc

Flexible Ethernet Edge


Service Abstraction

FlexibleServiceMapping

Standards Alignment

MultiplexedForwarding

Services TechnologyEVC

Framework

Support mix of Layer 2 and Layer 3 services on same physical port

Concurrent support of different flavors of Layer 2 services: Pt-to-Pt and Mpt

Ethernet Service Instances Model Ethernet Service Layer Transport agnostic

Alignment with emerging standards: MEF 6, 10.1, 11 IEEE 802.1ad IEEE 802.1ah

Flexible definition of service delimiters based on Ethernet header fields

Selective EVC Mapping

Advanced VLAN tag manipulation

Introducing Cisco EVC Framework

AdvancedFrame

Manipulation

Functional Highlights


Cisco EVC Fundamentals


Cisco EVC Building Blocks

Cisco EVC uses the following new concepts:

Ethernet Service Instance (S-I)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


CE A1CE A2

CE A3

CE B1CE B2

EVC Blue

EVC Red

S-I

Service Instance

S-I

S-I

Interface


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

Ethernet Service Instance



Representation of a MEF EVC on the device

Management Plane container

Hosts global EVC attributes

One-to-many mapping from EVC to Service Instance

Ethernet Virtual Circuit

Management Plane

Service Instance

S-IS-I

S-I

Interface

EVCEVC


Cisco EVC Building BlocksBridge Domain

Management Plane

Service Instance

S-IS-I

S-I

Interface

EVCEVC

Bridge Domain

Broadcast Domain internal to the device

Allows decoupling broadcast domain from VLANPer port VLAN significance

One-to-many mapping from BD to Service Instances



VLAN bridge has 1:1 mapping between VLAN and internal Broadcast Domain

VLAN has global per-device significance

EVC bridge decouples VLAN from Broadcast DomainVLAN treated as encapsulation on a wire

VLAN on a wire mapped to internal Bridge Domain via Service Instances

Net result: per-port VLAN significance

VLAN Bridge EVC Bridge

Bridge Domain vs. VLAN Bridge

VLANVLAN

VLAN

Service InstanceBridge

Domain


FlexibleServiceMapping

Packet Flow Pipeline

Ingress Encapsulation

Adjustment

Input Features

Frame FilteringEgress

Encapsulation Adjustment

OutputFeatures

Ingress Interface

Inbound Service Instance (S-I)

Outbound S-I

Egress Interface

Forwarder



Flexible Service Mapping



Single Tagged VLAN Matching Untagged traffic

Single VLAN ID value

Single VLAN ID Range (contiguous)

Single VLAN ID List

Single VLAN ID Range and List

Overview

30 5

0

40

19

12

10

11

20 2

2

21

S-VLAN C-VLAN

70

Un-tagged

PORTGE / 10GE

Range List Rangeand List

Ethernet Service Instances



Double Tagged VLAN Matching Outer VLAN, Inner

VLAN

Outer VLAN and Range of Inner VLANs (contiguous)

Outer VLAN and List of Inner VLANs

Outer VLAN and Range and List of Inner VLANs

Overview

200

10 1

1

12

300

70 8

0

90

10

100

S-VLAN C-VLAN

PORTGE / 10GE

OuterInner Range

OuterInner List

OuterInner



Header Matching Single VLAN, single

802.1p (COS) value

Single VLAN, COS List/Range

Outer VLAN, outer COS and Inner VLAN

Outer VLAN, Inner VLAN and inner COS

Single VLAN, Ethertype value (PPPoE, IPv4, IPv6)

Outer VLAN, Inner VLAN and Ethertype value (PPPoE, IPv4, IPv6)

Overview

S-VLAN C-VLAN

PORTGE / 10GE

COS5

400COS2-5

500

PPPoE

600

COS PPPoECOS

Range



Industrys Most Comprehensive Matching

Capabilities Service Instance

construct classifies L2 flows on Ethernet interfaces

Single Tagged

Double Tagged

Header/Payload

70

Overview

200

10 1

1

12

300

70 8

0

90

10

100

30 5

0

40

19

12

10

11

20 2

2

21

PORTGE / 10GE

S-VLAN C-VLAN

Un-tagged

Ethernet Service Instances

COS5

400COS2-5

500

PPPoE

600



Advanced Frame Manipulation


2025SADA20SADA

3125SADASADA


PUSH Operations Add one VLAN tag

Add two VLAN tags

Overview



SADA2010SADA

20SADA2010SADA

2025SADA20SADA

3125SADASADA

OverviewAdvanced Frame Manipulation

POP Operations Remove one VLAN tag

Remove two VLAN tags


3125SADA2010SADA

31SADA2010SADA

3125SADA10SADA

25SADA10SADA

2025SADA20SADA

3125SADASADA

SADA2010SADA

20SADA2010SADA


Translation Operations 1:1 VLAN Translation

1:2 VLAN Translation




3125SADA2010SADA

31SADA2010SADA

3125SADA10SADA

2025SADA20SADA

3125SADASADA

25SADA10SADA

SADA2010SADA

20SADA2010SADA


VLAN Tag Manipulation PUSH operations

POP operations

TRANSLATION operations



Multiplexed Forwarding Services



Cisco EVC supports flexible access VLAN to forwarding service mapping

1-to-1 access VLAN to a service

Same port, multiple access VLANs to a service

Multiple ports, 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



Layer 2 P2P local services

No MAC learning

Two Service Instances (S-I) on same interface (hair-pin)

Two SIs on different interfaces

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-horizonprevent communication between service instances

BD

BD = Bridge Domain VFI = Virtual Fwd InstancePW = Pseudowire SVI = Switch Virtual Instance

Layer 2 Multipointbridged

Layer 2 Point-to-PointLocal Hair-pin

Split

Horizon

Service Instances

Local and Bridged P2P and MP Forwarding Services



Layer 2 P2P services using Ethernet over MPLS

S-I to EoMPLS 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

BD VFI

MPLS-Based P2P and MP Forwarding Services

PW

PW


PW

Layer 2 MultipointVPLS

Layer 2 Point-to-PointEoMPLS



BD with Split Horizon Group can be used to implement rooted-multipoint forwarding service:

Place all Leaf S-Is in Split Horizon Group

Keep Root S-I outside the Split Horizon Group

Net effect: Bidirectional connectivity between Root and all Leaf S-Is

Leaf S-Is cannot communicate to each other Leaf S-I

Interface

BD

Bridge Domain

Split Horizon Group

Root Service Instance

LeafS-I

LeafS-I

Rooted-Multipoint Forwarding Services



Co-existence with Routed sub-interfaces

Layer 3 termination through SVI interface (interface vlan)

Layer 3 termination through Routed sub-interfaces

Layer 3 Forwarding Services


BD SVI

Layer 3IP / L3VPN via sub-int

BD

BD

Layer 3IP / L3VPN via SVI



Multiplexed Service Interface

Mix of L2 and L3 services on same port

Different types of L2 services

Point-to-Point

Multipoint

Service Instances

BD

BD VFI

BD SVI

Putting It All Together

PW

PW

PW




Features


Service-Instance/Bridge Domain Features

Security

MAC limit on EVC Bridge Domain

MAC security on Service Instance

MAC ACL on Service Instance

L3 / L4 ACL on Service Instance

Storm Control on Service Instance

IP Source Guard on Service Instance

DHCP snooping with Option-82 on Service Instance

Dynamic ARP Inspection (DAI)

Sample of Supported Features



Resiliency

MST on EVC Bridge Domain

EVC static Etherchannel

EVC LACP Etherchannel

EVC Etherchannel Manual Load Balancing

EVC and FlexLink (backup interface) integration

Resilient Ethernet Protocol (REP) on EVC

Multi-Chassis LACP (mLACP)

MST Access Gateway

Pseudowire Redundancy

Sample of Supported Features (Cont.)



OAM

IEEE 802.1ag (CFM) on Service Instance with Bridge Domain

CFM on Service Instance with Xconnect

CFM on L2 VFI

CFM to Ethernet LMI (E-LMI) Interworking

PW OAM to E-LMI Interworking

Link OAM to CFM Interworking

IP SLA for Metro Ethernet




MiscellaneousIEEE 802.1ah (Provider Backbone Bridging PBB)

IGMP Snooping

UDLD on Service Instance

Custom ether-type on Service Instance

Static unicast / multicast MAC on Service Instance and VFI PW

InstrumentationCISCO-EVC-MIB

IF-MIB (extensions to support Service Instances)

CISCO-BRIDGE-DOMAIN-MIB



Configuration


interface

Cisco EVC Configuration Anatomy

Per Port Per EVC Features

Per Port Per EVC Features Per Sub-interface

Features (L3)

Layer 2 ServicesBridging (VPLS via SVI)

xconnect (EoMPLS)Local Connect

L3 VRF

Global

ethernet evc

service instance ethernet service instance ethernet sub-interface

EFP

EVC


Configuring Flexible Service Mapping

Single-Tagged Frame encapsulation dot1q {any | [,[-]]}

VLAN tag can be single, multiple or range or any (1-4094)

Double-Tagged Frameencapsulation dot1q second-dot1q {any | [,[-]]}

First vlan tag must be unique, second vlan tag can be any, unique, range or multiple

Untagged Frameencapsulation untagged

Match un-tagged frames, for example control traffic

Default encapsulation default

Match all frames (tagged/untagged) not matched by more specific service instances

interface GigabitEthernet 2/1service instance 1 ethernetencapsulation ?default catch-all unconfigured encapsulationdot1q IEEE 802.1Q Virtual LAN or S-VLANuntagged Untagged encapsulation


Configuring Flexible Service Mapping (cont.)

Single-Tagged Frame and payload Ether-Typeencapsulation dot1q {[,[-]] | etype [IPv4|IPv6|pppoe-all]}

Double-Tagged Frame and payload Ether-Typeencapsulation dot1q second-dot1q {[,[-]] | etype [IPv4|IPv6|pppoe-all]}

Single-Tagged Frame and COSencapsulation dot1q {[,[-]] | cos [,[-]]}

Double-Tagged Frame and Inner COSencapsulation dot1q second-dot1q {[,[-]] | cos [,[-]]}

Double-Tagged Frame and Outer COSencapsulation dot1q {cos [,[-]]} second-dot1q {[,[-]]}

interface GigabitEthernet 2/1service instance 1 ethernetencapsulation ?default catch-all unconfigured encapsulationdot1q IEEE 802.1Q Virtual LAN or S-VLANuntagged Untagged encapsulation



Cisco EVC follows a Loose Match classification model: Unspecified fields are treated as wildcard encap dot1q 10 matches any frame with outer tag equal to 10:

encap dot1q 10 sec 50 matches any frame with outer-most tag as 10 and second tag as 50

10

5010

50

450

10

10

Loose Match Classification Rule



Cisco EVC follows the Longest Match classification model:

Frames are mapped to Service Instance with longest matching set of classification fields

Inte

rfac

e

10

20010

10010

13010

VLAN 10

S-VLAN 10

C-VLAN 100

S-VLAN 10

C-VLAN 128-133

Service Instance

Longest Match Classification Rule



Service Instance with Default encapsulation matches all frames otherwise unmatched by any other S-I on the same port

If default Service Instance is the only one configured on a port, it matches all traffic on the port (tagged and untagged)

Service Instance with Default Encapsulation

VLAN 10VLAN 20

Default

VLAN 10VLAN 20

VLAN 50Untagged

Interface S-I

Default

VLAN 10VLAN 20

VLAN 50Untagged

Interface

S-I


Configuring Advanced Frame Manipulationinterface GigabitEthernet 2/1service instance 1 ethernetencapsulation dot1q 10rewrite ingress tag ?pop Pop the tagpush Rewrite Operation of pushtranslate Translate Tag

POP Operationsrewrite ingress tag pop 1 symmetric

rewrite ingress tag pop 2 symmetric

PUSH Operationsrewrite ingress tag push dot1q 10 symmetric

rewrite ingress tag push dot1q 10 second-dot1q 20 symmetric

TRANSLATION Operationsrewrite 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

Automatic mirror egress operation


Configuring Point-to-Point Services

Point-to-point local connectconnect

Point-to-point xconnectxconnect encapsulation mpls

interface GigabitEthernet4/1/0service instance 3 ethernetencapsulation dot1q 51rewrite ingress tag translate 1-to-2 dot1q 52 second-dot1q 52 symmetric

interface GigabitEthernet4/1/1service instance 4 ethernetencapsulation dot1q 52 second-dot1q 52

connect eline-sample GigabitEthernet4/1/0 3 GigabitEthernet4/1/1 4

interface GigabitEthernet4/1/1service instance 11 ethernetencapsulation dot1q 101 second-dot1q 60-70xconnect 10.0.0.3 101 encapsulation mpls


VC label imposition and service delimiter tag are independent from EVC VLAN tag operations

Any VLAN tag, if retained, will appear as payload to the VC

VLAN tags can be added, removed or translated prior to VC label imposition or after disposition

VC Service Delimiter VLAN-ID is removed before passing packet to Attachment Circuit processing

AC PW

REWRITE Imposition

Add tag

5

4

VC

PW

Disposition

Pop 1 Tag

5

4

VC

AC

REWRITE

Imposition

Disposition

Encapsulation Adjustment ConsiderationsPW VC Type and EVC VLAN rewrites


IP/MPLS

PE-1 PE-2

VLAN ModeInterface GigabitEthernet 1/1.1encap dot1q 20xconnect 1.1.1.1 100 encap mpls

service instance 3 ethernetencapsulation dot1q 10xconnect 1.1.1.2 100 encap mpls

20

PW Type 4

20

10 10tag 10 20

PROBLEM - VLAN tag mismatch on attachment circuits !!!

In most cases, EVC device must be configured to POP EVCs context service delimiter VLAN

Encapsulation Adjustment ConsiderationsPW VC Type and EVC VLAN rewrites (cont.)

Dummy VLAN

service instance 3 ethernetencapsulation dot1q 10rewrite ingress tag pop 1 symmetricxconnect 1.1.1.2 100 encap mpls

Correct Configuration

Incorrect Configuration


Configuring Multipoint Services

Multipoint Native Ethernet Bridging and VPLSbridge-domain [split-horizon]

Split-horizon to disable L2 communication between two Service Instances (optional)

Local Bridging

interface GigabitEthernet4/1/0service instance 2 ethernetencapsulation dot1q 101-1000bridge-domain 100



VPLS

interface GigabitEthernet4/1/0service instance 2 ethernetencapsulation dot1q 60bridge-domain 20

interface GigabitEthernet4/1/1service instance 3 ethernetencapsulation dot1q 61bridge-domain 20

interface Vlan20xconnect vfi vpls-sample


Configuring Point-to-Multipoint Services

Multipoint Native Ethernet Bridging and VPLSbridge-domain [split-horizon]

Disables communication between leaf Service Instances in Split Horizon Group

Local Bridging

interface GigabitEthernet4/1/0service instance 2 ethernetencapsulation dot1q 101-1000bridge-domain 100 split-horizon

interface GigabitEthernet4/1/1service instance 3 ethernetencapsulation dot1q 101-1000bridge-domain 100 split-horizon


Leaf

Leaf

Root

Gig3/1/2

BD

Bridge Domain

Split Horizon Group

Root

Leaf

Leaf

X

Gig4/1/1

Gig4/1/0


Single tag termination

Option 1

interface GigabitEthernet4/1/1service instance 666 ethernetencapsulation dot1q 200rewrite ingress tag pop 1 symmetricbridge-domain 100

interface Vlan100ip address 100.1.100.1 255.255.255.0

Option 2

interface GigabitEthernet4/1/1.200encapsulation dot1q 200 ip address 100.1.100.1 255.255.255.0

Double tag termination

Option 1

interface GigabitEthernet4/1/1service instance 666 ethernetencapsulation dot1q 200 second 300rewrite ingress tag pop 2 symmetricbridge-domain 100

interface Vlan100ip address 100.1.100.1 255.255.255.0

Option 2

interface GigabitEthernet4/1/1.200encapsulation dot1q 200 second 300ip address 100.1.100.1 255.255.255.0

Configuring Layer 3 Services

POP mandatory for IP termination


Mapping to Metro Ethernet Forum (MEF) Services Attributes


MEF Service Attributes at a Glance

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

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

Multicast Service Frame Delivery

Broadcast Service Frame Delivery


EVC Performance

UNI AttributesEVC AttributesUNI 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

EVC Per UNI Attributes

MEF 10.1Ethernet Services Attributes


Mapping MEF Services to Cisco EVCSupport for Bundling and Service Multiplexing

CE

CEUNI

UNI

UNI


CE

CEUNI

UNI

UNI

All-to-One Bundling

All

CE-VLANs

CE

CEUNI

UNI

UNI

Bundling

CE-VLAN subset

PE PE PE

S-I match multiple CE-VLANs

S-I match all CE-VLANs

Different S-Is match different CE-VLANs


Configuring MEF Attributes

Configuring EVC IdentifierPE(config)# ethernet evc

CE-VLAN ID/EVC MapPE(config-if-srv)# ethernet lmi ce-vlan map {[,[-]] | any | default | untagged}

UNI CountPE(config-evc)# uni count {2 [multipoint] to 1024}

UNI TypePE(config-if)# ethernet uni {bundle [all-to-one] | multiplex}

UNI NamePE(config-if)# ethernet uni id


Configuring MEF UNI Variants

Configuring All-to-One Bundling

interface GigabitEthernet 1/0/2service instance 1 ethernet ServiceXYZ Instantiate an EVC on this portencapsulation default Maps all traffic on interface to single EVCbridge-domain 3

Configuring Bundling

interface GigabitEthernet 1/0/2service instance 1 ethernet ServiceXYZ Instantiate an EVC on this portencapsulation dot1q 30-50, 83, 100 Map multiple C-VLANs to single EVCbridge-domain 3


Configuring MEF UNI Variants (cont.)

Configuring Service Multiplexing

interface GigabitEthernet 1/0/2service instance 1 ethernet ServiceABC Instantiate first EVC on this portencapsulation dot1q 20-50 This service has bundling as wellbridge-domain 3!service instance 2 ethernet ServiceXYZ Instantiate second EVC on this port

encapsulation dot1q 100 No bundling for this servicebridge-domain 40


Deployment Use Cases

Residential Access Models Implementation



Access Node UNI Type Characteristics

Trunk UNI N:1 Service VLANs for Voice, Video and Data

Trunk UNI 1:1 Dedicated VLAN for Data and N:1 Service VLANs for Voice and Video

Residential use cases presented in the section:




Trunk UNI, N:1 Service VLAN


Residential UNI Standards

DSL Forum 101 for residential services

UNI exists between the access node and the CPE

Trunk UNI means a different VLAN or VC per service

Non-Trunk UNI means no VLANs to CPE

1:1 means one VLAN per customer

N:1 means multiple customers share a VLAN

Prevalent Residential service options

Non-Trunk UNI, N:1 VLAN

Trunk (Multi-VC) UNI, N:1 Service VLAN

Trunk (Multi-VC) UNI, 1:1 Internet Access (HSI) VLAN


Trunk UNI, N:1 Service VLAN Residential Service Connectivity Overview

Split Horizon Forwarding, locally significant VLAN ids combined into a per service Bridge Domains (N:1)

Video routed (unnumbered) in Aggregation, other transported to Distribution

Bridged DSL RG

Routed DSL RG

Emulated Bridge Domain

BNGInternet Service

Router

Default Gateway for the Routed CPEs or Appliances Connected in the Bridged RGs PPPoE Server DHCP Relay

Voice Service Router Function

Bridge Domain

Function

Aggregation Node

802.1Q

802.1Q

Video Service Router Function

ADSL, ADSL2+, 802.3Multi VC or Trunk UNI

N:1 Service VLAN

N:1 Service VLAN

Trunk or Multi VC UNI

Ethernet/WiMAX or DSL Access Node

Gateways for the Specific Video/Voice Application Subnets IP Unnumbered Interface DHCP Relay


Trunk UNI, N:1 Service VLAN Residential Service Aggregation Model

Port-significant VLAN ids removed on ingress

Some VLANs routed, other bridged

Common Bridge Domain allows to use single MPLS PW per Aggregation Node

VLAN id added on egress towards BNG

802.1Q [10]

802.1Q [10]

IPoE TV, VoD

HSI IP/PPPoE

IPoE TV, VoD

HSI IP/PPPoE

802.1Q [310]

Bridge Domain 310

Ingress POP TAG 10 Symmetric

Ingress POP TAG 10 Symmetric

IngressPOP TAG 310 Symmetric

VFI

IPoE Voice

IPoE Voice

802.1Q [11]

802.1Q [12]

802.1Q [11]

802.1Q [12]

Aggregation BNGAccess Distribution

20xGE 2x10GE 2x10GE 20xGE


Residential Service Use CaseTrunk UNI, N:1 Data Service VLAN (PW per AGG Node)

DSLAM Aggregation Distribution BNGEoMPLS PW

BD

Ingress direction: Match traffic from BNG based

on AGG VID (e.g. 310) POP AGG vlan Send traffic to PW

Single EoMPLS PW carries traffic from all DSLAMs in a given AGG node

Ingress direction: Match traffic from DSLAM based

on single VID (e.g. 10) POP the service vlan Send traffic to DATA bridge

domain (BD)

DATA Service Instance

Egress direction: PUSH service vlan (e.g. 10) on

traffic received from DATA BD

310310310310

Egress direction: PUSH vlan representing AGG

node (e.g. 310) on traffic received from PW


1010

1010

DSLAM assigns a single VLAN for Data service (e.g. 10). This vlan is shared for all subscribers (N:1)


interface GigabitEthernet4/0/4service instance 1 ethernetencapsulation dot1q 10rewrite ingress tag pop 1 symmetricbridge-domain 310 split-horizon

!service instance 2 ethernetencapsulation dot1q 11rewrite ingress tag pop 1 symmetricbridge-domain 311 split-horizon

!interface GigabitEthernet4/0/5service instance 1 ethernet

encapsulation dot1q 10rewrite ingress tag pop 1 symmetricbridge-domain 310 split-horizon


Trunk UNISingle Attached DSL Access Node

One common bridge domain for HSI (VLAN 310)

Per DSLAM SVI for video (VLAN 311 and VLAN 312)

Active/Active example using VPLS

Aggregation SVI

vlan 310vlan 311vlan 312!interface Loopback1ip address 130.173.1.1 255.255.255.255

!interface Vlan310xconnect vfi v310

!interface Vlan311ip dhcp relay information trustedip unnumbered Loopback1ip helper-address 10.20.61.3ip pim sparse-mode


Aggregation EVCAggregation Distribution

Aggregation Node EVC/SVI Configuration


Distribution #1vlan 310!pseudowire-class F1701encapsulation mplspreferred-path interface Tunnel1

!pseudowire-class F1601encapsulation mplspreferred-path interface Tunnel3

!l2 vfi v310 manualvpn id 310

neighbor 10.30.30.16 pw-class F1601 no-split-horizonneighbor 10.30.30.17 pw-class F1701 no-split-horizon!interface Loopback0ip address 10.30.30.172 255.255.255.255


Distribution #2

Trunk UNISingle Attached DSL Access Node

Aggregation

interface Loopback0ip address 10.30.30.16 255.255.255.255

!interface GigabitEthernet3/0/3service instance 310 ethernetencapsulation dot1q 310rewrite ingress tag pop 1 symmetricxconnect 10.30.30.173 310 pw-class F1703


!interface GigabitEthernet3/0/3service instance 310 ethernetencapsulation dot1q 310rewrite ingress tag pop 1 symmetricxconnect 10.30.30.173 310 pw-class F1703

BNG

Aggregation Distribution

Distribution Node/VPLS Configuration

* These configurations reflect only the VPLS CLI required for HSI transport toward the redundant BNGs on the Aggregation Node; for complete Aggregation Node configuration, please refer to the previous slide


Residential Service Use CaseTrunk UNI, N:1 Data Service VLAN (PW per DSLAM)



on DSLAM VID (e.g. 310, 410) POP DSLAM vlan Send traffic to PW

Single EoMPLS PW carries traffic from all subscribers in a given DSLAM


on single VID (e.g. 10) POP the service vlan Send traffic to PW


Egress direction: PUSH service vlan (e.g. 10) on

traffic received from PW

310310410410

Egress direction: PUSH vlan representing

DSLAM (e.g. 310, 410) on traffic received from PW


1010

1010

DSLAM assigns a single VLAN for Data service (e.g. 10). This vlan is shared for all subscribers (N:1)




Trunk UNI, 1:1 Internet Access VLAN


Trunk UNI, 1:1 Internet Access VLAN Residential Service Connectivity Overview

This models allows to migrate from a single/dual-play 1:1 scenario to a triple play one with video optimisation

Different Bridge Domains:N:1 VLAN for TV/VoD with Split Horizon forwarding in Access and Aggregation

1:1 VLAN for Internet Access/Voice

QinQ/802.1ad Interface

BNGInternet Service

Router

Default Gateway for the Routed CPEs or Appliances Connected in the Bridged RGs DHCP Relay PPPoE Server

Video ServiceRouter

Function

VLAN Rewrite/Tag Function

Aggregation Node

802.1Q

TV/VoD VC/VLAN

HIS/Voice VC/VLAN

N:1 VLAN

1:1 VLAN

1:1 VLAN

Ethernet or DSL Access Node

Bridged DSL RG

Routed DSL RGTrunk or Multi VC UNI

ADSL, ADSL2+, 802.3Multi VC or Trunk UNI

Gateway for the Specific Video Application Subnets DHCP Relay IP Unnumbered Interface


Trunk UNI, 1:1 Internet Access VLAN Residential Service Aggregation Model

Internet Access 1:1 VLANs are selectively double-tagged, added to a Bridge Domain, and tunnelled across a single PW

TV/VoD N:1 VLAN routed in Aggregation

802.1Q Range [100,499]

802.1Q Range [100,499]

802.1Q 10

802.1Q 10

Bridge Domain 310 QinQ [[100, 200,], any]

HSI IP/PPPoE

IPoE TV, VoD

HSI IP/PPPoE

IPoE TV, VoD

Aggregation BNGAccess Distribution

20xGE 2x10GE 2x10GE 20xGE

Ingress PUSH TAG 100 Symmetric

IngressPUSH TAG 200 Symmetric


Residential Service Use CaseTrunk UNI, 1:1 Data Service VLAN (PW per AGG Node)


Single EoMPLS PW carries traffic from all DSLAMs in a given AGG node


on DSLAM VID list (e.g. 100,200)

Send traffic to PW

100

101

100

101

100

100

200

200


on VID range (e.g. 100-499) PUSH vlan representing DSLAM

(e.g. 100, 200) Send traffic to DATA BD


Egress direction: POP DSLAM vlan (e.g. 100) on


100

101

100

101

100

100

200

200

Egress direction: Forward traffic received from

PW


100101

100101

DSLAM assigns a dedicated VLAN (1:1) for Data service per subscriber (e.g. range 100-499 for 400 subscribers)

BD


interface GigabitEthernet4/0/4service instance 1 ethernetencapsulation dot1q 100-499rewrite ingress tag push dot1q 100 symmetricbridge-domain 310 split-horizon


!interface GigabitEthernet4/0/5service instance 1 ethernetencapsulation dot1q 100-499rewrite ingress tag push dot1q 200 symmetricbridge-domain 310 split-horizon


Trunk UNI 1:1Single Attached DSL Access Node

One common bridge domain for HSI (VLAN 310)

Per DSLAM SVI for video (VLAN 311 and VLAN 312)

Active/Active example using VPLS

Aggregation SVI

vlan 310Vlan 311Vlan 312!interface Loopback1ip address 130.173.1.1 255.255.255.255




Aggregation EVCAggregation Distribution

Aggregation Node EVC/SVI Configuration


Distribution #1Vlan 310!pseudowire-class F1701encapsulation mplspreferred-path interface Tunnel1

!pseudowire-class F1601encapsulation mplspreferred-path interface Tunnel3

!l2 vfi v310 manualvpn id 310

neighbor 10.30.30.16 pw-class F1601 no-split-horizonneighbor 10.30.30.17 pw-class F1701 no-split-horizon!interface Loopback0ip address 10.30.30.172 255.255.255.255


Distribution #2

Trunk UNI 1:1Single Attached DSL Access Node

Aggregationinterface Loopback0ip address 10.30.30.16 255.255.255.255

!interface GigabitEthernet3/0/3service instance 310 ethernetencapsulation dot1q 100,200xconnect 10.30.30.173 310 pw-class F1703


!interface GigabitEthernet3/0/3service instance 310 ethernetencapsulation dot1q 100,200xconnect 10.30.30.173 310 pw-class F1703

BNGAggregation Distribution

Distribution Node/VPLS Configuration

* These configurations reflect only the VPLS CLI required for HSI transport toward the redundant BNGs on the Aggregation Node; for complete Aggregation Node configuration, please refer to the previous slide


Residential Service Use CaseTrunk UNI, 1:1 Data Service VLAN (PW per DSLAM)


Single EoMPLS PW carries traffic from all subscribers in a given DSLAM


on DSLAM VID (e.g. 100, 200) Send traffic to PW

100

101

100

101

100

100

200

200


on VID range (e.g. 100-499) PUSH vlan representing DSLAM

(e.g. 100, 200) Send traffic to PW


Egress direction: POP DSLAM vlan (e.g. 100) on


100

101

100

101

100

100

200

200

Egress direction: Forward traffic received from

PW


100101

100101

DSLAM assigns a dedicated VLAN (1:1) for Data service per subscriber (e.g. range 100-499 for 400 subscribers)



Business Services Implementation


Carrier Ethernet Business ServicesMEF Service Visualization

E-LINE: Ethernet Private Line (EPL) E-LAN: Ethernet Private LAN (EP-LAN)

E-LINE: Ethernet Virtual Private Line (EVPL) E-LAN: Ethernet Virtual Private LAN (EVP-LAN)



Service Type Service

E-LINE Ethernet Virtual Private Line

E-LINE Ethernet Private Line

E-LAN Ethernet Virtual Private LAN

E-LAN Ethernet Private LAN

Business use cases presented in the section:




Point-to-Point (EVPL and EPL)


Ethernet Virtual Private Line (EVPL)Logical View

DistributionAggregation

Localconnect

Core


Ethernet Virtual Private Line (EVPL)Details

Port-level C-VLAN significance

Local connect for services on same aggregation

Point-to-point EoMPLS for services to remote aggregations

C-Vlan tag is popped on UNI ingress

New C-Vlan tag pushed on egress

Most scalable option:

No global VLAN used

No MAC learning required


Ethernet Virtual Private Line (EVPL)Sample Configurations

EVPL Service Between Aggregations *

interface GigabitEthernet3/0/15no cdp enableservice instance 100 ethernetencapsulation dot1q 2593rewrite ingress tag pop 1 symmetricxconnect 10.40.40.26 11111 pw-class AS40

pseudowire-class AS40encapsulation mplspreferred-path interface Tunnel1040

EVPL Service on Same Aggregation

interface GigabitEthernet3/0/15mls qos trust cosno cdp enableservice instance 100 ethernetencapsulation dot1q 2595rewrite ingress tag pop 1 symmetric

interface GigabitEthernet3/0/16mls qos trust cosno cdp enableservice instance 200 ethernetencapsulation dot1q 2595rewrite ingress tag pop 1 symmetric

connect EVPL_local GigabitEthernet3/0/15 100 GigabitEthernet3/0/16 200

Aggregation CoreDistribution

1 GE 10GE 10 GE

* Configuration sample for remote EVPL reflects only one end of the connection


Localconnect


Core

Ethernet Private Line (EPL)Logical View


Ethernet Private Line (EPL)Details

Catch-all encapsulation default used for port-based service

Local connect for services on same aggregation

Point-to-point EoMPLS for services to remote aggregations

Scalability considerations:

No global VLAN used

No MAC learning required

One port = One service


Ethernet Private Line (EPL)Sample Configurations

EPL Service Between Aggregations *

interface GigabitEthernet3/0/4description Sample EPLmtu 9216no cdp enableservice instance 30 ethernetencapsulation defaultxconnect 10.40.40.26 1111 pw-class AS40

pseudowire-class AS40encapsulation mplspreferred-path interface Tunnel1040

EPL Service on Same Aggregation

interface GigabitEthernet3/0/11mtu 9216no cdp enableservice instance 100 ethernetencapsulation default

interface GigabitEthernet3/0/12mtu 9216no cdp enableservice instance 200 ethernetencapsulation default

connect EPL-sample GigabitEthernet3/0/11 100 GigabitEthernet3/0/12 200


1 GE 10GE 10 GE

(*) Configuration sample for remote EPL reflects only one end of the connection




Multipoint (EVP-LAN and EP-LAN)


VFI

Bridge Domain


Bridge Domain

Ethernet Virtual Private LAN (EVP-LAN)Logical View


Ethernet Virtual Private LAN (EVP-LAN)Details

C-Vlans are popped on ingress at aggregation

All traffic is mapped to a bridge-domain on aggregation

Bridge-domain tied to an SVI with Xconnect to distribution

Distribution node implements full-mesh VPLS

Distribution VPLS establishes a PW with aggregation

No split-horizon on distribution-aggregation PW


Ethernet Virtual Private LAN (EVP-LAN)Sample Configurations


1 GE 10GE 10 GE

Aggregation Node

interface GigabitEthernet3/0/15mtu 9216service instance 100 ethernetencapsulation dot1q 2504rewrite ingress tag pop 1 symmetricbridge-domain 2511

interface GigabitEthernet3/0/16mtu 9216service instance 200 ethernetencapsulation dot1q 2514rewrite ingress tag pop 1 symmetricbridge-domain 2511

interface Vlan2511mtu 9216xconnect 10.10.10.25 1111 pw-class F2501

pseudowire-class F2501encapsulation mplspreferred-path interface Tunnel11

Distribution Node *

l2 vfi EVPLAN-sample manualvpn id 1111

!Neighbor aggregation nodeneighbor 10.10.10.26 pw-class F2601 no-split-horizon

!Neighbor Distribution nodeneighbor 10.10.10.24 pw-class F2401

!Remote Distribution nodeneighbor 10.40.40.63 encapsulation mpls

interface Vlan2511mtu 9216xconnect vfi EVPLAN-sample

pseudowire-class F2401encapsulation mplspreferred-path interface Tunnel11 pseudowire-class F2601encapsulation mplspreferred-path interface Tunnel13

(*) Distribution SVI will stay up even if not associated to a Service Instance


VFI

Bridge Domain


Bridge Domain

Ethernet Private LAN (EP-LAN)Logical View


Ethernet Private LAN (EP-LAN)Details

Catch-all encapsulation default used for port-based service on aggregation

L2-protocol forward implements BPDU forwarding

All EPLAN interfaces mapped to a bridge-domain

SVI attached to bridge domain implement EoMPLS xconnect to distribution

Distribution node implements VPLS VFI with:

Full mesh to PW to remote distribution

PW to active aggregation with no split-horizon

Service uses a global VLAN


Ethernet Private LAN (EP-LAN)Sample Configurations

Aggregation Node

interface GigabitEthernet4/0/2mtu 9216no cdp enableservice instance 200 ethernetencapsulation defaultl2protocol forwardbridge-domain 2711

interface Vlan2711mtu 9216xconnect 10.10.10.25 1111 pw-class F2501

pseudowire-class F2501encapsulation mplspreferred-path interface Tunnel11

Distribution Node *

l2 vfi EPLAN-sample manualvpn id 1111!Neighbor aggregation node

neighbor 10.10.10.26 pw-class F2601 no-split-horizon!Neighbor Distribution node

neighbor 10.10.10.24 pw-class F2401!Remote Distribution node

neighbor 10.40.40.63 encapsulation mpls

interface Vlan2711mtu 9216xconnect vfi EPLAN-sample

pseudowire-class F2401encapsulation mplspreferred-path interface Tunnel11 pseudowire-class F2601encapsulation mplspreferred-path interface Tunnel13


1 GE 10GE 10 GE

(*) Distribution SVI will stay up even if not associated to a Service Instance


Platform Support


Cisco EVC FrameworkPlatform Support

Scalable Edge Services

Cisco 7600SIP-400ES-20 andES+ linecards

CiscoASR 9000


Summary


Cisco EVC FrameworkKey Takeaways

Next-generation cross-platform Carrier Ethernet Software Infrastructure

Addresses Flexible Ethernet Edge requirements





For More Information

Cisco 7600Ethernet Services + (ES+) Configuration GuideLayer 2 Features

Cisco 7600Ethernet Services (ES) Configuration GuideLayer 2 Features

Cisco 7600SPA Interface Processor-400 (SIP-400) Configuration Guide

Cisco ASR 9000 Series Aggregation Services Router Ethernet Services Application Guide

http://cisco.com/en/US/partner/docs/routers/7600/install_config/ES40_config_guide/es40_chap4.htmlhttp://cisco.com/en/US/partner/docs/routers/7600/install_config/ES40_config_guide/es40_chap4.htmlhttp://cisco.com/en/US/partner/docs/routers/7600/install_config/ES20_config_guide/SRD/baldcfg.htmlhttp://cisco.com/en/US/partner/docs/routers/7600/install_config/ES20_config_guide/SRD/baldcfg.htmlhttp://cisco.com/en/US/partner/docs/interfaces_modules/shared_port_adapters/configuration/7600series/76cfgeth.htmlhttp://cisco.com/en/US/partner/docs/interfaces_modules/shared_port_adapters/configuration/7600series/76cfgeth.htmlhttp://www.cisco.com/en/US/docs/routers/asr9000/applications/ethernet/services/application/guide/esasr9k.htmlhttp://www.cisco.com/en/US/docs/routers/asr9000/applications/ethernet/services/application/guide/esasr9k.html

2009 Cisco Systems, Inc. All rights reserved. Cisco PublicTECIPM-3001 96

AcronymsAcronymACL Access Control List

BD Bridge Domain

BRAS Broadband Access Server

CE Customer Equipment (Edge)

C-VLAN / CE-VLAN Customer VLAN

CoS Class of Service

DSLAM DSL Access Modulator

E-LAN Ethernet LAN service (multipoint)

E-Line Ethernet Line service (point-to-point)

E-Tree Ethernet Tree service (rooted multipoint)

EFP Ethernet Flow Point

EoMPLS Ethernet over MPLS

EPL Ethernet Private Line

EVC Ethernet Virtual Connection

EVPL Ethernet Virtual Private Line

IEEE Institute of Electrical and Electronics Engineers

IETF Internet Engineering Task Force

AcronymIPoETV TV on IP over Ethernet

IPTV Television over IP

MEF Metro Ethernet Forum

MEN Metro Ethernet Network

MPLS Multi-protocol Label Switching

OAM Operations, Administration and Maintenance

PE Provider Edge device

PW Pseudowire

Q-in-Q VLAN tunneling using two 802.1Q tags

QoS Quality of Service

SVI Switch Virtual Interface (interface vlan)

S-VLAN Service VLAN (Provider VLAN)

UNI User to Network Interface

VLAN Virtual LAN

VoD Video on Demand

VoIP Voice over IP

VPLS Virtual Private LAN Service


Complete Your Online Session Evaluation

Give us your feedback and you could win fabulous prizes. Winners announced daily.

Receive 20 Cisco Preferred Access points for each session evaluation you complete.

Complete your session evaluation online now (open a browser through our wireless network to access our portal) or visit one of the Internet stations throughout the Convention Center.

Dont forget to activate your Cisco Live and Networkers Virtual account for access to all session materials, communities, and on-demand and live activities throughout the year. Activate your account at any internet station or visit www.ciscolivevirtual.com.

http://www.ciscolivevirtual.com/


Check the Recommended Reading brochure for suggested products available at the Cisco Store

Enter to Win a 12-Book Libraryof Your Choice from Cisco Press

Visit the Cisco Store in the World of Solutions, where you will be asked to enter this Session ID code


EVC Framework coexistence with Switchport modelAppendix


Example Description

LAN

Card (67xx )

ES

20 / ES

+

5

50PF

C/D

FC

DBUS VLAN

= 50

Service instance (EFP)

Physical port PFC/DFC Forwarding engine

Frame on wire ( tag and data)

Frame on wire (tag and data)

DBUS VLAN is used for VLAN tag rewrite on the catalyst LAN cards, but not for VLAN tag rewrite on the service instance

Frame on data plane BUS or Fabric

interface gig 2/1service instance 11 ethernet

encapsulation dot1q 5rewrite tag ingress pop 1 symmetricbridge-domain 50

interface gig 3/1switchport mode trunkswitchport trunk encap dot1q


Example MP local bridging 802.1Q Trunk ports on LAN card, single tag frames

service instance 10 ethernetencapsulation dot1q 6rewrite ingress tag pop 1 symmetricbridge-domain 50

LAN

Card (67xx )

ES

20 / ES

+

5

6


50

service instance 10 ethernetencapsulation dot1q 5rewrite ingress tag pop 1 symmetricbridge-domain 50

ES

20 / ES

+

PF

C/D

FC

DBUS VLAN

= 50


Example MP local bridging 802.1Q Trunk ports on LAN card, double tag frames

service instance 10 Ethernetencapsulation dot1q 52 second 5-100rewrite ingress tag pop 1 symmetricbridge-domain 50 split-horizon

LAN

Card (67xx )

ES

20 / ES

+

5-100

5-100

5-100

service instance 10 Ethernetencapsulation dot1q 51, second 5-100rewrite ingress tag pop 1 symmetricbridge-domain 50 split-horizon

ES

20 / ES

+

50

5-100

PF

C/D

FC

DBUS VLAN

= 50

51

5-100

52

5-100



Example MP local bridging802.1Q Tunnel ports on LAN card, split-horizon enable

PF

C/D

FC

service instance 10 Ethernetencapsulation dot1q 5-100bridge-domain 50 split-horizon

LAN

Card (67xx )

ES

20 / ES

+

5-1005-100

5-100

interface gig 3/1switchportswitchport mode dot1q-tunnelswitchport access vlan 50

5-100

5-1005-100

service instance 10 Ethernetencapsulation dot1q 5-100bridge-domain 50 split-horizon

ES

20 / ES

+

DBUS VLAN

= 50


EVC Framework L2VPN considerations

Appendix


VC label imposition and service delimiter tag are independent from EVC VLAN tag operations

Any VLAN tag, if retained, will appear as payload to the VC

VLAN tags can be added, removed or translated prior to VC label imposition or after disposition

VC Service Delimiter VLAN-ID is removed before passing packet to Attachment Circuit processing

PW VC Type and EVC VLAN rewrites

AC PW

REWRITE Imposition

Add tag

5

4

VC

PW

Disposition

Pop 1 Tag

5

4

VC

AC

REWRITE

Imposition

Disposition


IP/MPLS

PE-1 PE-2

10 10

PW Type 5



tag10 tag tag

Single-tagged frame

Double-tagged frame

10

Encapsulation Adjustment Considerations

If peer PE uses EVC based configuration, then it will negotiate and use Type 5 pseudowire

MPLS labels

VLAN Tags and Pseudowires: EVC to EVC Example 1


IP/MPLS

PE-1 PE-2


10 10

PW Type 5

10


tag10 tag tag10 10

Service delimiter VLAN tag is transmitted unnecessarily. Wastes

bandwidth.


If peer PE uses EVC based configuration, then it will negotiate and use Type 5 pseudowire

Single-tagged frame

Double-tagged frame

VLAN Tags and Pseudowires: EVC to EVC Example 2


IP/MPLS

PE-1 PE-2

PW Type 4

VLAN ModeInterface gig 1/1.1encap dot1q 10xconnect 1.1.1.1 100 encap mpls

10 10tag


tag10 tag tagtag 10

tag10 tag tag1010

10 1010


Single-tagged frame

Double-tagged frame

Dummy VLAN

VLAN Tags and Pseudowires: EVC to Non-EVC Example 1


IP/MPLS

PE-1 PE-2

VLAN ModeInterface GigabitEthernet 1/1.1encap dot1q 20xconnect 1.1.1.1 100 encap mpls


20

PW Type 4

20

10 10tag 10 20

PROBLEM - VLAN tag mismatch on attachment circuits !!!

In most cases, EVC device must be configured to POP EVCs context service delimiter VLAN

Encapsulation Adjustment ConsiderationsVLAN Tags and Pseudowires: EVC to Non-EVC Example 2

Dummy VLAN


Correct Configuration

Incorrect Configuration


Introduction to Metro Ethernet Forum (MEF) Ethernet Services Appendix


MEF Concepts and TerminologyCE, MEN and UNI

CE:

Customer Equipment (Edge)

Router or IEEE 802.1 bridge/switch

MEN:

Metro Ethernet Network

Provide Ethernet service to CE

May employ various transports/media

UNI:

User-Network Interface

Demarcation between Customer and Provider

IEEE 802.3 PHY/MAC

CE

CECE

UNI

UNI

UNI

MEN


MEF Service Attributes at a Glance

UNI Identifier

Physical Medium

Speed

Mode

MAC Layer

UNI MTU


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


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

Multicast Service Frame Delivery

Broadcast Service Frame Delivery


EVC Performance

UNI AttributesEVC AttributesUNI 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

EVC Per UNI Attributes

MEF 10.1Ethernet Services Attributes


MEF Concepts and TerminologyEthernet Virtual Connection (EVC)

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)

CE

CE

CEUNI

UNI

UNI

CE

CE

CEUNI

UNI

UNI

CE

CE

CEUNI

UNI

UNI

Point-to-PointMultipoint-to-Multipoint Rooted-Multipoint


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


MEF Concepts and TerminologyHighlight of UNI Attributes

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

CE

CEUNI

UNI

UNI


CE

CEUNI

UNI

UNI

All-to-One Bundling

All

CE-VLANs

CE

CEUNI

UNI

UNI

Bundling

CE-VLAN subset


Mapping MEF Services to Cisco EVCSupport 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 S-Is

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


Mapping MEF Services to Cisco EVCSupport for Bundling and Service Multiplexing

CE

CEUNI

UNI

UNI


CE

CEUNI

UNI

UNI

All-to-One Bundling

All

CE-VLANs

CE

CEUNI

UNI

UNI

Bundling

CE-VLAN subset

PE PE PE

S-I match multiple CE-VLANs

S-I match all CE-VLANs

Different S-Is match different CE-VLANs


Configuring MEF Attributes

Configuring EVC IdentifierPE(config)# ethernet evc

CE-VLAN ID/EVC MapPE(config-if-srv)# ethernet lmi ce-vlan map {[,[-]] | any | default | untagged}

UNI CountPE(config-evc)# uni count {2 [multipoint] to 1024}

UNI TypePE(config-if)# ethernet uni {bundle [all-to-one] | multiplex}

UNI NamePE(config-if)# ethernet uni id


Configuring MEF UNI Variants

Configuring All-to-One Bundling

interface GigabitEthernet 1/0/2service instance 1 ethernet ServiceXYZ Instantiate an EVC on this portencapsulation default Maps all traffic on interface to single EVCbridge-domain 3

Configuring Bundling

interface GigabitEthernet 1/0/2service instance 1 ethernet ServiceXYZ Instantiate an EVC on this portencapsulation dot1q 30-50, 83, 100 Map multiple C-VLANs to single EVCbridge-domain 3


Configuring MEF UNI Variants (cont.)

Configuring Service Multiplexing

interface GigabitEthernet 1/0/2service instance 1 ethernet ServiceABC Instantiate first EVC on this portencapsulation dot1q 20-50 This service has bundling as wellbridge-domain 3!service instance 2 ethernet ServiceXYZ Instantiate second EVC on this port

encapsulation dot1q 100 No bundling for this servicebridge-domain 40