Carrier Ethernet Exchange Robert J Huey Equinix, Inc. <rhuey@equinix.com> 1
Overview Multi-Segmented Ethernet Virtual Connection (EVC) UNI ENNI ENNI UNI Ethernet Service Carrier Ethernet Ethernet Network Provider Exchange Operator OVC OVC E- NNI = External Network Network Interface UNI = User Network Interface OVC = Operator Virtual Circuit 2
CEE: Key Objectives Facilitate mulk- segmented Ethernet services Accelerate Ethernet service delivery Increase geographic distribukon & reach If it makes sense to do this anywhere, it makes sense to do it everywhere 3
CEE: Key Components Ethernet Exchange switch fabric(s) Alcatel- Lucent 7450 (SR/ESS Pla^orm) Metro- Area/Redundant Topologies Exchange Portal Features The Marketplace (match buyers & sellers) Alcatel- Lucent 5620SAM (SAM- 0) Automate Service Provisioning SLA Monitoring (stakskcs distribukon) TroubleshooKng 4
Portal Architecture London On-Net Buildings Disk DB Paris Service Provider Primary EMS Frankfurt New York Service Provider PORTAL Network Tools Chicago Service Provider Backup EMS Los Angeles Tokyo Customer Disk DB Hong Kong Singapore 5
Physical Interconnect Types Port Types 1. 1GbE 2. 10GE ConnecKon Methods A. Single Circuit B. Link AggregaKon C. MulK- Chassis LAG D. MulK- Chassis w/ Redundant IBX Carrier B IBX-B Carrier A Switch IBX-A Metro Network IBX-C Switch Switch Switch Carrier C Carrier D 6
Exchange Service Topologies E-NNI Aggregation Switch Fabric A E-NNI E-NNI B C E-NNI E-NNI D Point- to- Point Topology (E- Line) MulK- Point Topology (E- LAN) 7
Exchange Fabric Behavior Exchange Switch E-NNI Preserve Translate Adapt Client Data Preserve the original end user data Carrier Frame VLAN Frame Type Translation VLAN ID Translation TPID Translation CoS Bits QoS Marking & Queue Adaptation Preserve Translate Adapt E-NNI Preserve: Data & Protocol Transparency Translate: Frame Handling Adapt: QoS Behaviors 8
Quality of Service The Bad News It s wrijen into the service provider product descripkon The Good News It s wrijen into the service provider product descripkon We have to support whatever comes our way Requires Good Network Queuing and Mapping ModificaKon from default behavior MPLS switching = MPLS EXP bit mapping to Queues Strict Priority Order Drop!"#"# $%&'()*% +,,, -,,. /,., 0,.. 1.,, 2.,.,..,.... 3456678(94:;(<#=5>7:4 Congestion 9
Ingress QoS Adaptation Default Ingress CoS TranslaKon Table Carriers need only create the policy once to match product descripkon Side AgnosKc All marking policies can be customized if desired Can only use a 802.1p bit once Can use more than one 802.1p bit to idenkfy traffic on ingress only )*+,-../0,12,134/5-6-7/32/89-9- :9;<-,/2=/89-9-.! " # $ % & ' (!!!!! " " "!!/ " # # # " # $ $ $!/ " # $ % % % 89-9-. 802.1p Bits " # $ % & & & ' ' ( Traffic Direction 10
Egress QoS Adaptation Default Egress CoS TranslaKon Table Carriers need only create the policy once to match product descripkon Side AgnosKc All marking policies can be customized if desired Only one 802.1p bit (mark) per egress queue -./+,,0)*+*+,01203/42/41506+7+8 9*:;+/02<0)*+*+,! " # $ % & ' ( ( ( ( ( ' ' ' ( ( & & & ' (0 )*+*+, 802.1p Bits % % % $ $ $ % & ' & ' (0 # " # # $ % & '! " Traffic Direction 11
Ingress Scheduling Weighted Queues (priority order drop) Per Queue Parameters (opkonal) Commijed InformaKon Rate (CIR) Peak InformaKon Rate (PIR) Maximum Rate CIR, PIR, MAX Service Rate (opkonal) Typically match the carrier product descripkon Example: 100M Service Rate 1GbE Service Rate EVC #1 CIR, PIR, MAX CIR, PIR, MAX CIR, PIR, MAX To Network EVC #2 CIR, PIR, MAX CIR, PIR, MAX Service Rate Scheduler Port Scheduler 12
Egress Scheduling Mirrors of Ingress QoS Policy Number of Queues Class maps Weighted Queues (priority order drop) All eight (8) MPLS EXP or 802.1p Bits expressed in class map policy Per Queue Parameters (opkonal) 111 110 101 100 011 010 001 000 Queue #4 Queue #3 Queue #2 Queue #1 To Port Egress Class Map Port Scheduler 13
Ethernet OAM IEEE 802.1ag Hierarchal Maintenance Domain Maintenance AssociaKon, MIPs & MEP ConnecKvity Fault Management ITU- T Y.1731 All that (plus) Frame loss measurement Frame delay measurement 14
Lessons Field VerificaKon & TesKng DifficulKes RFC2544 TesKng Throughput Burst Rate Frame loss Latency Not MulK- Service Aware The Stacked NIDs Problem Ethernet OAM (to much to expect?) What s next? 15
References The Metro Ethernet Forum. Technical Specifica.on MEF 26, External Network Network Interface (ENNI) Phase 1. January 2010. hjp://metroetherne^orum.org/pdf_documents/technical- specificakons/mef26.pdf Balakrishnan, R. (May 2008). Advanced QoS for Mul.- Service IP/MPLS Networks. (Wiley) ITU- T RecommendaKon Y.1731 - OAM funckons and mechanisms for Ethernet based networks ITU- T RecommendaKon Y.156 - OAM funckons and mechanisms for Ethernet based networks 16
QuesKons? Thank You 17