Your SlideShare is downloading. ×
0
© 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco PublicEnhancing IP/MPLS based CarrierServices to...
© 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco PublicAttending Cisco Live Orlando?We are offeri...
© 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco PublicSpeaker & Panelist IntroductionPanelistSpe...
© 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco PublicHousekeeping•  Submit questions in Q&A pan...
© 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco PublicAgenda•  Data Center Interconnect Requirem...
© 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco PublicData Center Interconnect Requirements6
© 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco PublicData Center Interconnect (DCI) Concept•  D...
© 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco Public!"#$%&()(&!*+)*,&!"#$%&()(&!*+)*,&Workload...
© 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco PublicSP Managed DCI Solutions•  Standalone DCI ...
© 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco PublicSP Managed DCI•  Data Centre Interconnecti...
© 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco PublicVM Mobility•  Drivers for VM mobility!  Ma...
© 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco PublicLocal loadbalancingServer Clustering•  Glo...
© 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco PublicSP Multitenant DCI:Baseline Requirements• ...
© 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco PublicSP Multitenant DCI Scaling•  The scaling o...
© 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco PublicData Center Interconnect: Layer 2 Extensio...
© 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco PublicTowards a common DCI Handoff ?•  Is DCI a ...
© 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco PublicData Center Interconnect Using VPLS17
© 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco Public./01&2&!$3)#4*,&15$674*+)&!1&!1&!1&1)8*,+*...
© 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco PublicVPLS constraints•  Not optimal with multic...
© 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco PublicScaling VPLS : PBB-VPLS•  VPLS current cha...
© 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco PublicMulti-Homing DC’s and Loadbalancing/Resili...
© 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco PublicQ%FU%_J$Cisco A-VPLS : VPLS w/ MC-LAG & Fa...
© 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco PublicSummary Scaling VPLSVPLS/LDP VPLS/BGPMAC-A...
© 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco PublicDCI Using E-VPN / PBB-EVPN24
© 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco PublicEvolving Requirements for L2VPN251.  All-a...
© 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco PublicWhat is Ethernet-VPN (E-VPN)•  Treat MAC a...
© 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco PublicEthernet Segment ID (ESI) and E-VPN Instan...
© 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco PublicEVPN RoutesE-VPN Routes PurposeEthernet Au...
© 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco PublicE-VPN Operations Example!  Host M1 sends a...
© 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco PublicE-VPN Operations Example – Cont.!  Host M2...
© 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco PublicIt looks easy but not so fast !•  In the s...
© 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco PublicSplit Horizon for Ethernet Segment•  PE1 a...
© 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco PublicDesignated Forwarder (DF) Election•  Only ...
© 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco PublicAliasing•  In order for PE3 to be able to ...
© 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco PublicReducing ARP Flooding in E-VPN•  PE/MESes ...
© 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco PublicProvider Backbone Bridging E-VPN (PBB-EVPN...
© 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco PublicPBB-EVPN Main Principles•  DF Election wit...
© 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco PublicOperation: Dual Homed Device•  Each PE adv...
© 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco PublicOperation: Dual Homed Network•  Each PE ad...
© 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco PublicAdvantages: MAC Address Scalability1.  BGP...
© 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco PublicAdvantage: Avoiding C-MAC Address Flushing...
© 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco PublicAdvantage: IntraDC Interworking•  End-to-e...
© 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco PublicAdditional Advantages•  C-MAC Mobility wit...
© 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco PublicBGP Routes Comparison44Route E-VPN PBB-EVP...
© 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco PublicComparison of Solutions45Requirement E-VPN...
© 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco PublicVPLS and EVPN Scaling•  Actual requirement...
© 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco PublicVPLS and EVPN Scaling•  Parameters!  n DCs...
© 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco PublicComparison DCI MPLS solutions48Characteris...
© 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco PublicSummary• Data Center InterconnectRequireme...
© 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco PublicKey Take Aways•  Data Center Interconnect ...
© 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco PublicPoll Question #1How many Datacenters does ...
© 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco PublicPoll Question #2Which platform are you con...
© 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco PublicPoll Question #3Are you considering VPLS/P...
© 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco PublicPoll Question #4Which features are most cr...
© 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco PublicGlossary55(G)SLB (Global) Server Load Bala...
© 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco Public•  A8(+B&C#$D&$•  %#(&*($-./0#(+($+1($0.*+...
Enhancing IP/MPLS based Carrier Services to Address the Data Center Interconnect Market
Upcoming SlideShare
Loading in...5
×

Enhancing IP/MPLS based Carrier Services to Address the Data Center Interconnect Market

1,991

Published on

This webinar describes the motivation for using IP/MPLS technologies as a Data Center inter-connect technology. Data Center Interconnect is a service that Service Providers (SP) can offer to interconnect Enterprise Data Centers, interconnect SP Data Centers, or allow Enterprise to connect to SP-owned compute and storage resources.

Watch the replay at: https://cisco.webex.com/ciscosales/lsr.php?AT=pb&SP=EC&rID=67897237&rKey=f7260083ab1d593f

Published in: Technology, Education
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
1,991
On Slideshare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
144
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide

Transcript of "Enhancing IP/MPLS based Carrier Services to Address the Data Center Interconnect Market"

  1. 1. © 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco PublicEnhancing IP/MPLS based CarrierServices to address the Data CenterInterconnect MarketPatrick Warichet: Technical Marketing Engineer NOSTGVipul Shah: Engineering Product Manager NOSTG•  Cisco TechAdvantage Webinars – May 1, 2013
  2. 2. © 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco PublicAttending Cisco Live Orlando?We are offering various Ethernet Services and Ethernet OAM learningopportunities at Cisco Live Orlando.Learn more and register at: http://www.ciscolive.com/us/attendees/education/Technical Session Session NumberBuilding Carrier Ethernet Services Using Cisco Ethernet VirtualCircuit FrameworkBRKSPG-2204Ethernet OAM: Technical Overview and Deployment Scenarios BRKNMS-2202Redundancy Mechanisms for Carrier Ethernet and Layer 2VPN ServicesBRKSPG-2207Towards Massively Scalable Ethernet: Technologies andStandardsBRKSPG-2206
  3. 3. © 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco PublicSpeaker & Panelist IntroductionPanelistSpeakersPatrick WarichetTechnical MarketingEngineerpwariche@cisco.comTina LamEngineering ProductManagertinalam@cisco.comVipul ShahEngineering ProductManagervipshah@cisco.com
  4. 4. © 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco PublicHousekeeping•  Submit questions in Q&A panel and send to !"##$%&(#)*+*,$Avoid CHAT window for better access to panelists•  Please -./0#(+($+1($0.*+2(3(+$*453(6$•  For 7(89:$&4;)., select COMMUNICATE > Join AudioBroadcast•  Where can I get the presentation?Or send email to: &*<=+(-1&;3&+&>(?-)*-.@-./$•  A.)$4*$B.5$.45$40-./)>$C(-1";3&+&>($7(8)&5*D$$EEE@-)*-.@-./F>.F+(-1&;3&+&>($$•  For 7(89:$-&##$8&-<, click ALLOW phone buttonat the bottom of participants side panel
  5. 5. © 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco PublicAgenda•  Data Center Interconnect Requirements•  Data Center Interconnect Using Virtual Private LAN Service•  Data Center Interconnect Using Ethernet -VPN•  Summary5
  6. 6. © 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco PublicData Center Interconnect Requirements6
  7. 7. © 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco PublicData Center Interconnect (DCI) Concept•  Data Centers are extending beyondtraditional boundaries due to:!  Extending Operating System, FileSystem clusters, Database clusters!  Virtual/Physical machine mobilitydue to load sharing, disasterprevention!  Legacy devices/applications withembedded IP addressing!  Time to deployment and operationalreasons!  Extend DC to solve power/heat/space limitationsBusiness Drivers7BusinessDriversIT SolutionsDisasterPreventionActive/Standby MigrationBusinessContinuanceServer HA clusters, “Geo-clustering”WorkloadMobilityMove, consolidate servers,“Vmotion”ConnectivityflavorPurpose Business BenefitSANextensionsStoring/replicatingdatabusiness continuity, disasterrecovery, regulatory complianceL3 extensions(L3VPNs)Routed L3ConnectivitySegmentation, Virtualization, fileserver backup applicationsL2 extensions Layer 2 across datacentersHigh-Availability Clusters, Geo-clustering, Virtual machinemobilityEthernet EmulationServiceL2 L2Main DataCenterBackup Data CenterStorage StorageIP RoutedServiceDWDM/CWDML3L3SAN SANL2L2FC FC
  8. 8. © 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco Public!"#$%&()(&!*+)*,&!"#$%&()(&!*+)*,&WorkloadincreaseCoreCloud VPN!"#$%&()(&!*+)*,&RequestresourcesWorkloadDeployedAdditional CapacityNeeds – RequestCloud Resources1Check Availability,Performance,Determine OptimalLocation2Self-provision NetworkTenant, VirtualCompute, Storage,VPN3vDC Active41234A DCI use Case : Cloud Centric NetworkingG%&62&*26.42>.H$B.5$-./04+(I$*+.5&>(I$(+E.5<$-+)*,+("&()(&!*+)*,&DCI8
  9. 9. © 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco PublicSP Managed DCI Solutions•  Standalone DCI network providesinterconnection between main SP DCs!  Owned by SP DC team!  Addresses SP2SP only!  Very high bandwidth – packet / optical solutionlikely the most cost effective•  DCI Requires Technology Evolution inData Center and SP NGN for:!  Multihoming!  Scale (MAC-addresses, Number of ServiceInstances!  Loadbalancing!  Optimal Forwarding!  Multicast optimization!  Multitenancy•  NGN Based DCI Interconnectionmodels:!  Enterprise to Enterprise (E2E)!  Enterprise to Service Provider (E2SP)!  Service Provider to Service Provider(SP2SP)J%$KLM$ J%$KLN$9+$KLM$ 9+$KLN$J%$OPO$KL%9$KL%9$KL9$KL9$%9$ %9$L9$ L9$9+(505)*($KLQ$!8&-<$;..5,$J+&;&#.($KLQ$(+E.5<$9
  10. 10. © 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco PublicSP Managed DCI•  Data Centre Interconnection (DCI) refers to interconnection of datacentres primarily in support of two use cases:•  Workload mobility! Moving workloads across Enterprise DCs! Moving workloads from Ent to SP – “cloud bursting”! Moving workloads from SP to SP – resilience and maintenance! Needs mobility of the IP address – can be achieved at L2 and L3•  Business Continuance - Server clustering and related transaction andstorage replication! Often requires L2 extension – but increasingly support for L3Use Cases10
  11. 11. © 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco PublicVM Mobility•  Drivers for VM mobility!  Maintenance withoutdowntime!  Workload balancing across sites!  Data centre migration, consolidation orexpansion!  Disaster avoidance•  Example: VMware Vmotion!  Enables live migration of VMs!  Active memory and execution state of a VM is transmittedfrom one physical server to another and access to the VMsdisk storage is switched to the new physical host!  VM retains its IP address and network connections,helping to ensure transparent migration11•  R(S4)5(/(+*$B.5$TU.V.D$U)$WNNU80*$8&;E);+1$)*$5(S4)5(;$8(+E(($;&+&$-(+5(*$&;$&+$#(&*+$MP80*$E)+1)$;&+&$-(+5(*$U&:$X/*$RCCI$)@(@$/&:$YZZ</$[((0$U"L$&;$Q%$&;;5(**$4-1&>(;$&(5$/.3($•  J.45-($&;$;(*V&V.$*(53(5*$;.$.+$((;$+.$8($.$*&/($*48(+$)$05&-V*(]$^4+$+1(6$;.$((;$+.$8($&8#($+.$/&)+&)$Q%$-.(-V3)+6$_N$(:+(*).$)*$.($E&6$.B$&-1)(3)>$+1)*$
  12. 12. © 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco PublicLocal loadbalancingServer Clustering•  Global server load balancing (GSLB) distributesclient traffic to servers across remote data centers!  e.g. using DNS, L3, route health injection, HTTPredirection•  GSLB commonly deployed with local Server LoadBalancing (SLB) to Server Clusters•  Server clustering technologies and storage sync /replication often require L2 extension – butincreasingly support L3 also!  Active/Standby ; Heartbeat based!  Potentially out of span of control SPExamples Microsoft MSCS*, Veritas Cluster Server*, Solaris Sun ClusterEnterprise, VMware Cluster, Oracle RAC (Real Appl.Cluster), HP MC/ServiceGuard, HP NonStop, HP Open VMS/TruCluster, IBM HACMP, EMS/Legato Automated Availability MgrStorageArrayStorageArrayServerClusterServerClusterLocal loadbalancingGloballoadbalancingK&+&$L(+5($`M$K&+&$L(+5($`N$12
  13. 13. © 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco PublicSP Multitenant DCI:Baseline Requirements•  Scales to the level required for SP virtualprivate cloud!  100s of thousands of MAC addresses per datacentre!  Thousands of tenants ; potentially more than 4Kservice instances!  10s of data centres•  Optimally forward unicast and multicast!  Shortest path!  Loop free!  Avoiding duplicates•  Is resilient to all single element failures, i.e. inboth NGN and DC•  Provides control plane isolation between DCs•  Fast to converge•  Uses network resources efficiently!  All connections active with load balancing!  Flood minimisation•  Easy to manage and operate•  Open standards based or clear track tostandardisation•  Integrates with SP NGN, whilst honouring anyadministrative boundaries between DC and NGN,including DC connectivity across multiple AS’es•  Supports geo-redundant PEs, i.e Enterprise DCI“back door”•  Is DC transparent!  works for plain old spanning tree 802,1Q environment(Normalized DCI Handoff)!  interworks with other DC technologies (Seamless DCIHandoff)13
  14. 14. © 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco PublicSP Multitenant DCI Scaling•  The scaling of a solution that uses L2 extension may be impacted by 4concerns! MAC address scalabilityMAC address scalability is an issue on the DC WAN edge for solutions that use L2 extensionExample: 250k CMAC addresses in a single SP data centreThis is multiplied across interconnected SP data centres and Enterprise data centres! PW scale – (if PWs are used)! Control plane scale – i.e. whether an L2 control plane domain is extendedbetween data centres! Broadcast, Unknown unicast, and multicast traffic handling14
  15. 15. © 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco PublicData Center Interconnect: Layer 2 Extension Technology•  Virtual Private LAN Service (VPLS)! The best available option in shipping code! Does not meet some of the data center interconnect requirements for large SPMultitenant Deployment options•  Ethernet-VPN (E-VPN) / Provider Backbone Bridging Ethernet VPN(PBB-EVPN)! New technologies to meet all of the large SP multitenant data center interconnectrequirements! http://tools.ietf.org/html/draft-ietf-l2vpn-evpn! http://tools.ietf.org/html/draft-ietf-l2vpn-pbb-evpn15
  16. 16. © 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco PublicTowards a common DCI Handoff ?•  Is DCI a UNI or NNI ?! All Service Instancesremapped to 802.1q VLANs! or end to end (assumesother encapsulation insideDC)•  Is there a Control Planeinside the Data Center?! Control Plane interworkingconsiderations! IGP in DC ; BGP acrossDCs ?802.1Q/ad DC802.1ahDCOther IntraDCtechnologies :TRILL /802.1Qaq/bpDCI16
  17. 17. © 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco PublicData Center Interconnect Using VPLS17
  18. 18. © 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco Public./01&2&!$3)#4*,&15$674*+)&!1&!1&!1&1)8*,+*)&.9-& 1)8*,+*)&.9-&9/01&:&9/01&;&9/01&<&9/01&=&0>&./01&2&!$3)#4*,&15$674*+)&!1&!1&!1&1)8*,+*)&.9-& 1)8*,+*)&.9-&9/01&:&9/01&;&9/01&<&9/01&=&0>&Virtual Private LAN Services (VPLS)•  Flooding (Broadcast, Multicast, UnknownUnicast)•  Dynamic learning of MAC addresses on PHYand VCsVirtual Forwarding Instance (VFI)•  ForwardingPhysical PortVirtual Circuit•  VPLS uses Split-Horizon and Full-Mesh ofPWs for loop-avoidancein coreSP does not run STP in the core•  RFC 4761 (BGP-Based VPLS); RFC 4762(LDP-Based VPLS)•  BGP Autodiscovery for LDP-Based VPLSRFC6074•  Hierarchical VPLS option for LDP based VPLS!  802.1ad based!  MPLS PW based"00#)(*$$J0#)+2$a.5)b.$"00#)(*$$J0#)+2$a.5)b.$"00#)(*$$J0#)+2$a.5)b.$T%_J$K(c(*$&$"5-1)+(-+45($+.$%5.3);($L.(-V3)+6$^(+E(($P(.>5&01)-&##6$K)*0(5*(;$L4*+./(5$J)+(*$"-5.**$U"O*$&;$7"O*I$&*$QB$C1(6$7(5($L.(-+(;$d*)>$&$_"O@$18
  19. 19. © 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco PublicVPLS constraints•  Not optimal with multicast! Enhancements are maturing (using Label Switched Multicast with VPLS instead ofingress resplication)•  No active/active dual-homing per flow! Per VLAN is possible•  Does not hide customer mac-addresses•  PW scaling•  Handoff scaling and Service Instance Scaling! 4k services per physical interface! 000’s of VSI’s (hardware limitations)19
  20. 20. © 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco PublicScaling VPLS : PBB-VPLS•  VPLS current challenges! MAC-Address Scalability at the PE! Service Instance Scaling! Limits DCI handoff to 4K services per interface•  Approach:! Use Provider Backbone Bridging (PBB)/802.1ah withVPLS! Hides Customer MAC-Addresses!  Described inhttp://tools.ietf.org/html/draft-ietf-l2vpn-pbb-vpls-pe-model andhttp://tools.ietf.org/html/draft-ietf-l2vpn-pbb-vpls-interop20
  21. 21. © 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco PublicMulti-Homing DC’s and Loadbalancing/Resilience across VPLSSP DC1 SP DC2Ent DC1 Ent DC2SP NGNSignalling Active PE : InterChassis Control Protocol(ICCP,) or BGPOr PE Clustering (VSS, nV,VPC)Multi Chassis LinkAggregation (MC-LAG)Multi Chassis AutomaticProtection Switching (MC-APS)Selecting correct Pseudo-Wire: PseudowireRedundancyOr BGPFlow Aware Transport:FAT-PW21
  22. 22. © 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco PublicQ%FU%_J$Cisco A-VPLS : VPLS w/ MC-LAG & Fat-PWs•  Flow Aware Transport (FAT) Pseudo-wires as in RFC6391•  A: Aggregation switch performs EtherChannel flow-based hashing (on L2/L3/L4) & elects a linktowards VSS switch (e.g. Cat6000).•  B: VSS performs flow-based hashing (L2/L3/L4) to select outbound ECMP link. Optionallyinserts FAT-PW Flow Label (to be used in C).•  C: P nodes in MPLS core perform Loadbalaningover ECMP using Flow Label.Note: Load-balancing decisions in A, B & C are independent.Advanced 3-stage Load-BalancingUL2_"P$UL2_"P$">>M$">>N$UM$ UN$UL2_"P$UL2_"P$"$ ^$ L$TJJ$TJJ$
  23. 23. © 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco PublicSummary Scaling VPLSVPLS/LDP VPLS/BGPMAC-Address Scaling Needs PBB-VPLS Needs PBB-VPLSFlexible ServiceInstance ScalingNeeds PBB-VPLS Needs PBB-VPLSOptimal Unicast(ECMP)Needs Fat PWs Needs Fat PWsOptimal Multicast Needs VPLS-LSM Needs VPLS-LSMControl Plane isolationbetween DC and DCINone (Transparent toDC control planeexcept MST)None (Transparent toDC control planeexcept MST)Active Active per VLAN Needs ICCP andPseudowireredundancyBGPActive Active per Flow Not achievable Not achievableGeoredundancy Needs ICCP (active/standby)BGP (active/standby)
  24. 24. © 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco PublicDCI Using E-VPN / PBB-EVPN24
  25. 25. © 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco PublicEvolving Requirements for L2VPN251.  All-active Redundancy•  Flow Based Load Balancing•  Flow Based Multi-pathing•  Geo-redundancy and FlexibleRedundancy Grouping2.  Simplified Provisioning and Operation•  Core Auto-Discovery•  Access Multi-homing Auto-Discovery•  New Service Interfaces3.  Optimal Multicast with LSM•  P2MP Trees•  MP2MP Trees4.  Fast Convergence•  Link/Port/Node Failure•  MAC Mobility5.  Scalable for SP virtual privatecloud service:•  Support O(10 Million) MAC Addresses per DC•  Confinement of C-MAC Learning6.  Seamless interworking betweenTRILL / 802.1aq / 802.1Qbp andMST / RSTP•  Guarantee C-MAC Transparency on PE7.  Fast Convergence•  Avoiding C-MAC Flushing";;5(**(;$86$$92T%O$e$%^^29T%O$Addressed byPBB-EVPNUnderline: Addressed byVPLS
  26. 26. © 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco PublicWhat is Ethernet-VPN (E-VPN)•  Treat MAC addresses as routable addresses and distribute them in BGP•  When multiple PE nodes advertise same MAC, create multiple adjacencies in forwarding table•  When forwarding traffic for a given unicast MAC DA, use hashing (L2/L3/L4) to pick one of the adjacencies•  MP2MP or P2MP LSPs for Multicast Traffic Distribution•  MP2P (like L3VPN) LSPs for Unicast Distribution•  NO FULL MESH of PW’s !!!At a glance26PE1/MES1PE4/MES4PE3MES3MPLS CorePE2/MES2From PE1iBGP L3-NLRI:•  next-hop: n-PE1•  <C-IP1, L1>iBGP L2-NLRI•  next-hop: n-PE1•  <C-MAC1, L2>From PE3iBGP L3-NLRI:•  next-hop: n-PE3•  <C-IP5, L1>iBGP L2-NLRI•  next-hop: n-PE3•  <C-MAC3, L2>
  27. 27. © 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco PublicEthernet Segment ID (ESI) and E-VPN Instance•  MPLS Edge Switch (MES) is an E-VPN PE•  ESI Used when CE is multi-homed to two MES•  Allows remote MESes to load-balance to a multihomed CE•  10 octet value created by:!  Configuration!  Snooping of LACP (Multi-Homed Device)!  Snooping of STP BPDUs (Multi-Homed Network)!  (LLDP , although currently out of scope of the draft)•  ESI has a new associated MPLS Label extended BGP Community (used forsplit-horizon procedures in multi-homing)•  EVI = E-VPN Instance ID27
  28. 28. © 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco PublicEVPN RoutesE-VPN Routes PurposeEthernet Auto-Discovery (AD)RouteMulti-purpose route for• Auto-discovery of sites, vlans, VPNs, and site/vlan• Load Balancing• Split Horizon filtering on an Ethernet segmentMAC Route • Advertisement of Client/Provider MACsInclusive Multicast Route • Auto-discovery of MESes belonging to a VPN for setting upmulticast treeSelective Multicast Route • Auto-discovery of MESes belonging to a given c-(S,G) of aVPN for setting up a multicast treeEthernet Segment Route • DF election on an Ethernet segment• MC-LAG state synch on an Ethernet segment• Loop prevention on an ES during transient stateLeaf Auto-Discovery (AD) Route • Multicast Tree Auto-discovery28
  29. 29. © 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco PublicE-VPN Operations Example!  Host M1 sends a message with MAC SA = M1and MAC DA=bcast!  PE1 learns M1 over its Agg2-PE1 AC and distributes it viaBGP to other PE devices!  All other PE devices learn that M1 sits behind PE1M1 communicates with M2 (e.g. ARP) - Broadcast29PE1PE2 PE4PE3AGG1AGG2AGG3AGG4AGG5AGG6ESI=1ESI=3ESI=2C-MAC1C-MAC2iBGP L2-NLRI•  next-hop: n-PE1•  <C-MAC1, Label 100>BGPM1M2
  30. 30. © 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco PublicE-VPN Operations Example – Cont.!  Host M2 sends response with MAC SA = M2 and MAC DA = M1!  PE4 learns M2 over its Agg5-PE4 AC and distributes it via BGP to other PE devices!  PE 4 forwards the frame to PE1 since it has learned previously that M1 sits behind PE1!  All other PE devices learn that M2 sits behind PE4Reply from M2 to M1 (Unicast)PE1PE2 PE4PE3AGG1AGG2AGG3AGG4AGG5AGG6ESI=1ESI=3ESI=2M1M2iBGP L2-NLRI•  next-hop: n-PE1•  <C-MAC2, Label 200>10030BGP
  31. 31. © 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco PublicIt looks easy but not so fast !•  In the shown example, how do weensure that!  ARP broadcast packet doesn’t get loopback to theoriginating Agg device (Agg-1) :Split Horizon for ESI!  Either PE3 or PE4 forward the broadcast frame tothe far-end dual-homed device (Agg-2)Designated Forwarder Selection!  When PE3 wants to forward a packet withdestination address MAC1, it needs to send it toboth PE1 and PE2 even though it only learnedMAC1 from PE1Aliasing31?@!=& ?@!<&?@!=& ?@!<&?@!=& ?@!<&%9M$%9N$%9f$%9Y$%9M$%9N$%9f$%9Y$">>M$ ">>N$">>M$ ">>N$">>M$ ">>N$%9M$%9N$%9f$%9Y$
  32. 32. © 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco PublicSplit Horizon for Ethernet Segment•  PE1 advertises in BGP a split-horizon labelassociated with the ESI-1 (in the EthernetAD route)•  Split-horizon label is only used for multi-destination frames (unknown unicast,mcast, bcast)•  When PE1 wants to forward a multi-destination frame, it appends this SH labelto the packet•  PE2 uses this label to perform split-horizonfiltering for frames destined to ESI-1! A frame originated by a segment must not bereceived by the same segment32MAC1 MAC2PE1PE2PE3PE4Agg1 Agg2ESI-1 ESI-2
  33. 33. © 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco PublicDesignated Forwarder (DF) Election•  Only the PE that is the DF shallforward the multi-destination frame toan ESI•  DF election is performed by each PEadvertising the ESI in BGP (EthernetAD route) for a given VLAN•  PE with highest (or lowest) IP addressis selected ad the DF for that segment•  Non-DF PEs block that port for thatsegment – e.g., do not transmit anymulti-destination frames to thatsegment33MAC1 MAC2PE1PE2PE3PE4Agg1 Agg2ESI-1 ESI-2
  34. 34. © 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco PublicAliasing•  In order for PE3 to be able to perform loadbalancing among the flows destined to MAC1on ESI-1, it needs to know that:a)  ESI-1 sits behind both PE1 and PE2b)  MAC-1 is associated with ESI-1•  PE1 and PE2 use Ethernet AD route toadvertise ESI-1•  PE1 uses MAC route to advertise MAC1•  All the remote PEs (PE3 and PE4) use thesetwo routes in combination to associatea)  MAC1 to ESI-1b)  subsequently MAC-1 to [PE1 and PE2]34MAC1MAC2PE1PE2PE3PE4Agg1 Agg2ESI-1 ESI-2
  35. 35. © 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco PublicReducing ARP Flooding in E-VPN•  PE/MESes perform Proxy ARP wthe destination is in the same subnet asthe sender of the ARP request•  The ARP request is not forwarded to other PE/MESes•  How does the PE/MES learn the IP address bound to the MAC addresswhen the MAC address is remote?! A PE/MES advertises the local IP to MAC bindings in the BGP MAC routes•  How does a PE/MES learn the IP to MAC binding when the MAC addressis local?! Control or management plane between MES and CEs or data plane snooping(DHCP, etc)35
  36. 36. © 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco PublicProvider Backbone Bridging E-VPN (PBB-EVPN)•  Advertise local B-MAC addresses in BGP to all other PEs that have at least one VPN incommon just like E-VPN•  Build a forwarding table from remote BGP advertisements just like E-VPN (e.g., associationof B-MAC to MPLS labels)•  PEs perform PBB functionality just like PBB-VPLSC-MAC learning for traffic received from ACs and C-MAC/B-MAC association for traffic received from core36PE2PE1PE3LACPCE1MPLSBE BBE B<- E-VPN |PBB -><- PBB|E-VPN ->• $J)>#($^2U"L$+.$5(05(*(+$*)+($QK$• $-&$;(5)3($+1($^2U"L$&4+./&V-&##6$B5./$*6*+(/$U"L$&;;5(**$.B$_"L%$B-MAC =Site IDTRILLB-MAC BGPRoutes
  37. 37. © 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco PublicPBB-EVPN Main Principles•  DF Election with VLAN Carving!  Prevent duplicate delivery of flooded frames.!  Uses BGP Ethernet Segment Route.!  Performed per Segment rather than per (VLAN,Segment).!  Non-DF ports are blocked for flooded traffic (multicast,broadcast, unknown unicast).•  Split Horizon for Ethernet Segment!  Prevent looping of traffic originated from a multi-homedsegment.!  Performed based on B-MAC source address rather thanESI MPLS Label.•  Aliasing!  PEs connected to the same multi-homed EthernetSegment advertise the same B-MAC address.!  Remote PEs use these MAC Route advertisements foraliasing load-balancing traffic destined to C-MACsreachable via a given B-MAC.37%9$ %9$%9$ %9$%9$ %9$%9$ %9$%9$ %9$%9$^2U"LM$^2U"LM$
  38. 38. © 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco PublicOperation: Dual Homed Device•  Each PE advertises a MAC route per Ethernet Segment (carries B-MAC associated with Ethernet Segment).!  Both PEs advertise the same B-MAC for the same Ethernet Segment.•  Remote PE installs both next hops into FIB for associated B-MAC.!  Hashing used to load-balance traffic among next hops.•  PE1 MAC Routes:!  Route: RD11, B-MAC1, RT2, RT3•  PE2 MAC Routes:!  Route: RD22, B-MAC1, RT2, RT338PE1PE2VLAN 2, 3VLAN 2,3B-MAC1PE3VPN B-MAC NHRT3 B-MAC1 PE1RT3 B-MAC1 PE2RT2 B-MAC1 PE1RT2 B-MAC1 PE2RIBVPN B-MAC NHRT3 B-MAC1 PE1,PE2RT2 B-MAC1 PE1,PE2FIBMPLS/ IP
  39. 39. © 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco PublicOperation: Dual Homed Network•  Each PE advertises two MAC routes per Ethernet Segment: one with high Local Pref for active VLANs,and another with low Local Pref for standby VLANs.•  Remote PE installs the route with higher local pref into FIB for associated B-MAC.•  PE1 MAC Routes:!  Route 1: RD11, B-MAC1, RT3, Local Pref = High!  Route 2: RD12, B-MAC1, RT2, Local Pref = Low•  PE2 MAC Routes:!  Route 1: RD22, B-MAC2, RT3, Local Pref = Low!  Route 2: RD21, B-MAC2, RT2, Local Pref = High39PE1PE2VLAN 3VLAN 2PE3VPN B-MAC NH PrefRT3 B-MAC1 PE1 HighRT3 B-MAC2 PE2 LowRT2 B-MAC1 PE1 LowRT2 B-MAC2 PE2 HighRIBVPN B-MAC NHRT3 B-MAC1 PE1RT2 B-MAC2 PE2FIBMPLS/ IPEthernetB-MAC1B-MAC2
  40. 40. © 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco PublicAdvantages: MAC Address Scalability1.  BGP MAC Advertisement Route Scalability!  Multiple orders of magnitude difference between C-MAC & B-MAC addresses2.  C-MAC Address Confinement!  With data plane C-MAC learning, C-MACs are never in RIB and are only present in FIB for active flows!  Whereas, with control plane C-MAC learning, C-MACs are always in RIB and maybe also in FIB407"O$KL$J)+($M$KL$J)+($N$KL$J)+($O$ghMUi$L2U"L*$ghMZZi$^2U"L*$
  41. 41. © 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco PublicAdvantage: Avoiding C-MAC Address Flushing•  B-MAC represents a site (Ethernet Segment)•  Link, port, or node failure doesn’t change the B-MAC address to C-MAC address bindings –only changes the next hop for that B-MAC41PE1PE2VLAN 3VLAN 2B-MAC1PE3 RIBC-MAC VPN B-MAC NHCM1 RT3 B-MAC1 PE1 PE2CM2 RT2 B-MAC1 PE2FIBMPLS/ IPVPN B-MAC NH PrefRT3 B-MAC1 PE1 HighRT3 B-MAC1 PE2 LowRT2 B-MAC1 PE1 LowRT2 B-MAC1 PE2 High12Withdraw B-MAC13 Remove4 Update
  42. 42. © 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco PublicAdvantage: IntraDC Interworking•  End-to-end tunneling of C-MAC addresses thus avoiding data-planetermination and C-MAC learning by PE.•  Control plane isolation between different TRILL / IEEE 802.1aq/ 802.1Qbpislands.TRILL / IEEE 802.1aq / 802.1Qbp42PBB-EVPNTRILL /802.1aq/802.1QbpIS-IS IS-ISBGPTRILL/PBB EncapsulationControlPlaneData PlanePEPEMPLSTRILL /802.1aq/802.1Qbp
  43. 43. © 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco PublicAdditional Advantages•  C-MAC Mobility with MAC sub-netting! Typically C-MACs are not managed and thus can not be sub-netted! B-MACs on the other hand are always managed and can easily be sub-netted! Even when C-MACs are sub-netted, VM mobility contradicts the effect of sub-netting•  Avoid transient loop for known unicast when doing egress MAC lookup! Since B-MAC SA is always transmitted with every frame, checking of every frameagainst its source MAC SA for known unicast frame is already provided by PBB43
  44. 44. © 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco PublicBGP Routes Comparison44Route E-VPN PBB-EVPNMAC Advertisement Route Distribute C-MAC • Distribute B-MAC• Aliasing• Fast WithdrawEthernet A-D Route • Aliasing• Split-Horizon Label• Fast Withdraw• DF ElectionNot UsedEthernet Segment Route DF Election DF ElectionInclusive Multicast Route Multicast Tree Discovery Multicast Tree DiscoverySelective Multicast Route Multicast Tree Discovery Multicast Tree DiscoveryLeaf Discovery Route Multicast Tree Discovery Multicast Tree Discovery
  45. 45. © 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco PublicComparison of Solutions45Requirement E-VPN PBB-EVPNAll-Active Redundancy with Flow Based Load-balancing ! !Flow Based Multi-pathing ! !Geo-redundancy and Flexible Redundancy Grouping ! !Core Auto-Discovery ! !Access Multi-homing Auto-Discovery ! !New Service Interfaces ! !LSM with P2MP Tree ! !LSM with MP2MP Tree ! !Fast Convergence on Failure ! !Fast Convergence on MAC Mobility ! !Fast Convergence: Avoiding C-MAC Flushing !Scale to Millions of MAC Addresses !Confinement of C-MAC Learning !Seamless interworking between TRILL /802.1Qaq/802.1Qbp ! (C-MAC Transparency issue) !
  46. 46. © 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco PublicVPLS and EVPN Scaling•  Actual requirements from a large SP:!  n DCs = 20!  d cmacs per DC = 500k!  2 PEs per DC!  c customers (with bridge domain per customer) = 8k!  l linecards per PE = 8!  e edge switches per DC on average = 8SP DCI Case Study46# Model Mac scale reqs per PE PW / LSP scale reqs per PE1a VPLS 500k*20 = 10M 8k*(2*20-1) = 312k1b VPLS + Cluster 500k*20 = 10M 8k*(20-1) = 152k2 EVPN 500k*20 = 10M 2*20-1 = 393 PBB-VPLS (PE linecard is I component) 500k*20/8 = 1.25M 2*20-1 = 394 PBB-EVPN (PE linecard is I component) 500k*20/8 = 1.25M 2*20-1 = 395 EVPN + TRILL/FP 20*8 = 160 2*20-1 = 39
  47. 47. © 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco PublicVPLS and EVPN Scaling•  Parameters!  n DCs!  d cmacs per DC!  2 PEs per DC!  c customers (with bridgedomain per customer)!  l linecards per PE!  e edge switches per DCon averageRequirements47# Model Mac scalereqs per PEPW / LSP scale reqsper PE1a VPLS d*n c*(2n-1)1b VPLS + cluster d*n c*(n-1)2 EVPN d*n 2n-13a PBB-VPLS (PE is I-component) d*n 2n-13b PBB-VPLS (PE linecard is I-component)d*n/l 2n-14a PBB-EVPN (PE is I-component) d*n 2n-14b PBB-EVPN (PE linecard is I-component)d*n/l 2n-15 EVPN + TRILL/FP n*e 2n-1
  48. 48. © 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco PublicComparison DCI MPLS solutions48Characteristics Legacy VPLS Cisco’s A-VPLS E-VPN PBB-EVPNFlow-based Load Balancing No Yes Yes YesFlow-based multi-pathing No Yes Yes YesGeo redundant group & opt. unicast No No Yes YesFlexible redundancy grouping No No Yes YesMAC Scaling No No No YesMP2MP MDT support No No Yes YesP2MP MDT support No No Yes YesFast convergence upon AC failure No Yes Yes YesFlow-based or VLAN-based LB for MHN No Yes Yes YesMinimal configuration No Yes Yes YesAuto detect of MHN/MHD for flow-based LB No No Yes YesScaling MPLS Core – full-mesh No No Yes Yes
  49. 49. © 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco PublicSummary• Data Center InterconnectRequirements• Data Center Interconnect Using VirtualPrivate LAN Service• Data Center Interconnect UsingEthernet -VPN49
  50. 50. © 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco PublicKey Take Aways•  Data Center Interconnect is a new Service that can be offered by SP’s byenhancing their IP/MPLS Services!  L2 Ethernet Service!  L3 Service•  VPLS with enhancement can be leveraged to offer L2 Ethernet Service•  E-VPN solves some of the VPLS Scaling issues!  Active, Active!  Better Multicast support!  Pseudo Wire Scaling!  Autoconfiguration•  PBB-EVPN solves all of the Scaling issues associated with multi-tenant, high-capacity DCI!  Service Instance Scaling!  MAC Address Scaling!  Interworking with next gen IntraDC Technologies50
  51. 51. © 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco PublicPoll Question #1How many Datacenters does your company have?A.  1-2B.  2-3C.  4-5D.  6+51
  52. 52. © 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco PublicPoll Question #2Which platform are you considering or currently have at the DCIedge? (select multiple choices, as applicable)A.  ASR 9KB.  Nexus 7KC. ASR 1KD. Catalyst 6KE.  Another vendor equipment52
  53. 53. © 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco PublicPoll Question #3Are you considering VPLS/PBB-EVPN/EVPN for your Data CenterInterconnect technology?A.  I would consider deployment in the next 12 monthsB.  I would consider deployment in the next 12-24 monthsC. Undecided. Need further evaluation / understanding of the technologyD. No plans to deploy / Not applicable to my environmentE.  I am considering another DCI technology at this time53
  54. 54. © 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco PublicPoll Question #4Which features are most critical for your company when considering a DCItechnology? (select multiple choices, as applicable)A.  Route scaling associated with Multi-tenant networksB.  Seamless interworking between intra-DC and DCI protocolsC. Resiliency and load balancingD. MulticastE.  Other54
  55. 55. © 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco PublicGlossary55(G)SLB (Global) Server Load Balancing(V)LAN (Virtual) Local Area NetworkAD Auto-DiscoveryARP Address Resolution ProtocolAS Autonomous SystemBGP Border Gateway ProtocolB-MAC Backbone MACBPDU Bridge Protocol Data UnitCE Customer EdgeC-MAC Customer MACCWDM Coarse Wave Division MultiplexingDC Data CenterDCI Data Center InterconnectDF Designated ForwarderDHD Dual Homed DeviceDHN Dual Homed NetworkDWDM Dense Wave Division MultiplexingECMP Equal Cost Multi PathESI Ethernet Segment IDEVI Ethernet VPN InstanceE-VPN Ethernet VPNFAT Flow Aware TransportFC Fiber ChannelFIB Forwarding Information BaseICCP Inter Chassis Control ProtocolIGP Interior Gateway ProtocolIP Internet ProtocolL2-VPN Layer 2 VPNLACP Link Aggregation Control ProtocolLDP Label Distribution ProtocolLLDP Link Layer Discovery ProtocolLSM Label Switched MulticastMAC Media AccessMC-APS Multi-Chassis Automatic Protection SwitchingMC-LAG Multi-Chassis Link AggregationMES MPLS Edge SwitchMHN Multi Homed NetworkMP2MP Multipoint to MultipointMP2P Multipoint to PointMPLS Multi Protocol Label SwitchingMST Multiple Spanning Tree ProtocolNGN Next Generation NetworkNLRI Network Layer Reachability InformationNNI Network to Network InterfacenV Network VirtualizationP2MP Point to MultipointP2P Point to PointPBB-EVPN Provider backbone Bridging Ethernet VPNPE Provider EdgePW Pseudo WireRD Route DistinguisherRIB Routing Information BaseRSTP Rapid Spanning Tree ProtocolRTT Round Trip TimeSAN Storage Area NetworkTRILL Transparent INterconnection of a Lot of LinksUNI User to Netwok InterfaceVPLS Virtual Private LAN ServiceVPN Virtual Private NetworkVSI Virtual Switch InstanceVSS Virtual SwitchWAN Wide Area Network
  56. 56. © 2013 Cisco and/or its affiliates. All rights reserved.BRKSPG-2024 Cisco Public•  A8(+B&C#$D&$•  %#(&*($-./0#(+($+1($0.*+2(3(+$*453(6$•  A.)$4*$B.5$40-./)>$E(8)&5*D$R(>)*+(5D$EEE@-)*-.@-./F>.F+(-1&;3&+&>($$j.##.E$4*$$$$$$$?P(+k.45^4)#;g$$
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×