Cox Business. L2 / L3 and Network Topology Overview. February 1, 2011

Transcription

1 Cox Business L2 / L3 and Network Topology Overview February 1, 2011

2 Layer 3 / Layer 2 Comparo Protocol Architecture Control Change: Adding sites Change: IP changes Faults: Management Faults: Calls Layer bis Limited to IP only, so special handling needed to make some applications available on the network Routed solution so customer s routers have to navigate service provider routers to connect with each other Customers lose control of IP routing Complex as all service provider routers connecting sites need routing changes Service provider needs to agree all IP address changes Very difficult to fix faults costing time and money for service provider No clear demarcation between customer and service provider network resulting in customer fault calls when the issue is on the customer network Layer 2 VPLS Multi-protocol Ethernet if the application can run on your LAN then it can run on the WAN Bridged solution so customer s routers only see routers of their own network transparent WAN to customer Customer retains control of IP routing Simple, only the service provider router the site connects to needs changing IP addressing is simpler. No need to involve service provider Service provider does not need to deal with customer routing issues fewer fault calls, quicker and cheaper fault fixing Clear demarcation of service provider and customer results in less stress for customer and less cost for service provider 2

3 Layer 3 and Layer 2 Benefits 3

4 Our Network

5 Cox DWDM Nationwide Backbone Infinera DWDM Carrier Class Fiber Backbone Scalable to 800 Gb+ Network & capacity expansion on-going Managed by Cox National NOC 10Gb Wavelength services Business-class Service Level Agreements 5

6 Cox IP/MPLS Nationwide Backbone Self-healing, IP/MPLS based multi-service National Backbone Multiple, redundant, diverse Tier 1 transit points, nationwide Network & capacity expansion on-going Managed by Cox National NOC Business-class Service Level Agreements Extensive national and international Peering partners Peering distributed nationwide Peering expansion ongoing 6

7 Cox Markets 7

8 Cox AZ Network Cox owned and managed fiber optic facilities Over $500M invested in the network in the last 5 years Dedicated Local Resources Multiple Cox Metropolitan Telecommunications Centers (MTC s) Next Generation, multi-service, self healing DWDM, Ethernet, SONET, and HFC transport networks Self-healing, IP/MPLS based multiservice Metro Network High performance, high capacity, low latency, scalable Carrier class reliability Business Class Service Level Agreements 8

9 Cox Business Ethernet Services Overview

10 Feature - Service Option (EPL) Ethernet Private Line (EPL) Replaces a TDM private line Dedicated s for Point-to-Point (P2P) connections Single Ethernet Virtual Connection (EVC) per The most popular Ethernet service due to its simplicity Point-to-Point EVCs Dedicated TDM circuits MEN SONET MAN EPL using E-Line Service Type Private Line Analogy 10

11 Service Option - EVPL Ethernet Virtual Private Line (EVPL) Replaces Frame Relay or ATM services s can be shared across multiple P2P connections Multiple EVCs per (Service Multiplexing) Enables a single Ethernet port () to support multiple virtual connections (EVCs) Popular service for those wanting hub & spoke connectivity Point-to-Point EVCs Point-to-Point FR PVCs Service Multiplexed MEN FR CPE FR FRS MAN FR Port FR CPE FR CPE FR Port EVPL using E-Line Service Type Frame Relay Service Analogy 11

12 Service Option - EP-LAN/EVP-LAN Ethernet Private LAN/Ethernet Virtual Private LAN Intra-company, any-to-any connectivity Private or virtual Makes the MEN look like a LAN Operates very similar to an Ethernet network deployed in the enterprise Metro only Multipoint-to-Multipoint EVC Multipoint-to-Multipoint EVC MEN MEN EP-LAN using E-LAN Service Type EVP-LAN using E-LAN Service Type 12

13 E-Line/E-LAN Private and Virtual E-Line (EVC Type = P2P) Point-to-Point EVC E-LAN (EVC type = MP2MP) Multipoint-to-Multipoint EVC SM = No (Private) MEN MEN EPL EP-LAN Point-to-Point EVCs Multipoint-to-Multipoint EVC SM = Yes (Virtual) Service Multiplexed MEN MEN EVPL EVP-LAN 13

14 BP Options - EPL/EP-LAN EVC EVC Profile Per Ingress Profile Per Ingress EPL E-Line Service type; P2P EVC Emulates a Private Line service 1, 1 EVC, 1 QoS (CIR = x) BP at the Customer should police their traffic up to CIR to avoid dropped frames BP port speed EP-LAN E-LAN Service type; MP2MP EVC Emulates a Transparent LAN Service (TLS; old terminology) 1, 1 EVC, 1 QoS (CIR = x) BP at the Customer should police their traffic up to CIR to avoid dropped frames BP port speed 14

15 BP Option #1 - EVPL/EVP-LAN EVPL (option 1) E-Line; P2P or P2MP topologies Emulates a FR or ATM service EVC 1 EVC 2 Profile Per Ingress 1, 3 EVCs, 1 QoS (CIR = x) BP at the All EVCs share bandwidth EVC 3 Customer responsible for traffic policing across EVCs BP port speed EVP-LAN (option 1) EVC 1 E-LAN; MP2MP topology EVC 2 Profile Per Ingress Emulates a TLS 1, 3 EVCs, 1 QoS (CIR = x) EVC 3 BP at the All EVCs share bandwidth Customer responsible for traffic policing across EVCs BP port speed 15

16 BP Option #2 - EVPL EVPL (option 2) E-Line; P2P or P2MP topologies Emulates a muxed PL service EVC 1 EVC 2 Profile Per EVC 1 Profile Per EVC 2 1, 3 EVCs, 1-3 QoS values CIR = x, y, z where x, y, z can be the same or different for each EVC EVC 3 Profile Per EVC 3 BP at the EVC Provider manages b/w per EVC Customer should still police their traffic to avoid dropped frames Sum of EVC BPs port speed 16

17 BP Option #2 - EVP-LAN EVP-LAN (option 2) E-LAN EVC type; MP2MP topology EVC 1 EVC 2 EVC 3 Profile Per EVC 1 Profile Per EVC 2 Profile Per EVC 3 Emulates a TLS 1, 3 EVCs, 1-3 QoS values CIR = x, y, z where x, y, z can be the same or different BP at the EVC Provider manages b/w per EVC Customer should still police their traffic to avoid dropped frames Sum of EVC BPs port speed 17