cox business l2 / l3 and network topology overview relay service analogy men uni uni point-to-point...

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

Upload: truongdang

Post on 07-May-2018

216 views

Category:

Documents


3 download

TRANSCRIPT

Cox Business

L2 / L3 and Network Topology OverviewFebruary 1, 2011

2

Layer 3 / Layer 2 Comparo

Clear demarcation of service provider and customer results in less stress for customer and less cost 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

Faults: Calls

Service provider does not need to deal with customer routing issues – fewer fault calls, quicker and cheaper fault fixing

Very difficult to fix faults – costing time and money

for service provider Faults: Management

IP addressing is simpler. No need to involve service provider

Service provider needs to agree all IP address changes

Change:IP changes

Simple, only the service provider router the site connects to needs changing

Complex as all service provider routers connecting sites need routing changes

Change: Adding sites

Customer retains control of IP routing Customers lose control of IP routing Control

Bridged solution so customer’s routers only see routers of their own network – transparent WAN to customer

Routed solution so customer’s routers have to navigate service provider routers to connect with

each other

Architecture

Multi-protocol Ethernet – if the application can run on your LAN then it can run on the WAN

Limited to IP only, so special handling needed to

make some applications available on the network

Protocol

Layer 2 VPLSLayer 3 2547bis

3

Layer 3 and Layer 2 Benefits

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

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

7

Cox Markets

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 multi-service Metro Network

• High performance, high capacity, low latency, scalable

•Carrier class reliability

•Business Class Service Level Agreements

Cox Business Ethernet Services Overview

10

MEN

UNI

UNI

UNI

Point-to-Point EVCs

EPL using E-Line Service Type Private Line Analogy

UNI

SONETMAN

Dedicated TDM circuits

CE

CE CE

CE

Feature - Service Option (EPL)

• Ethernet Private Line (EPL)– Replaces a TDM private line– Dedicated UNIs for Point-to-Point (P2P) connections– Single Ethernet Virtual Connection (EVC) per UNI– The most popular Ethernet service due to its simplicity

CE CE

11

FR CPE

FR CPE

FRSMAN

FR Port

FR Port

FR UNI

Point-to-Point FR PVCs

Frame Relay Service Analogy

MEN

UNI

UNI

Point-to-Point EVCs

EVPL using E-Line Service Type

CE

Service Multiplexed

UNI

FR CPECE

Service Option - EVPL

• Ethernet Virtual Private Line (EVPL)– Replaces Frame Relay or ATM services– UNIs can be shared across multiple P2P connections– Multiple EVCs per UNI (Service Multiplexing)

• Enables a single Ethernet port (UNI) to support multiple virtualconnections (EVCs)

– Popular service for those wanting hub & spoke connectivity

CE

12

Service Option - EP-LAN/EVP-LAN

MEN

Multipoint-to-Multipoint EVC

UNI

UNI

UNI

UNI

EP-LAN using E-LAN Service Type

• 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

MEN

Multipoint-to-Multipoint EVC

UNI

UNI

UNI

UNI

EVP-LAN using E-LAN Service Type

CE

CECE

CE CE CE

CECE

13

E-Line/E-LAN – Private and Virtual

E-Line (EVC Type = P2P) E-LAN (EVC type = MP2MP)

SM = No

(Private)

SM = Yes

(Virtual)

CE

CE

CE

MEN CE

Multipoint-to-Multipoint EVC

UNI

UNI

UNI

UNI

EVP-LAN

Point-to-Point EVC

MENUNI

UNI

EPL

CE CE

CE

CE

CE

MEN CE

Multipoint-to-Multipoint EVC

UNI

UNI

UNI

UNI

EP-LAN

MEN

UNI

UNI

Point-to-Point EVCs

EVPL

CE

CE

Service Multiplexed

UNI

CE

14

BP Options - EPL/EP-LAN

• EPL– E-Line Service type; P2P EVC– Emulates a Private Line service– 1 UNI, 1 EVC, 1 QoS (CIR = x)– BP at the UNI

• Customer should police their traffic up to CIR to avoid dropped frames

– BP port speed

UNI EVC Ingress Bandwidth Profile Per Ingress UNI

• EP-LAN– E-LAN Service type; MP2MP EVC– Emulates a Transparent LAN Service (TLS;

old terminology)– 1 UNI, 1 EVC, 1 QoS (CIR = x)– BP at the UNI

• Customer should police their traffic up to CIR to avoid dropped frames

– BP port speed

UNI EVC Ingress Bandwidth Profile Per Ingress UNI

15

BP Option #1 - EVPL/EVP-LAN

• EVPL (option 1)– E-Line; P2P or P2MP topologies– Emulates a FR or ATM service– 1 UNI, 3 EVCs, 1 QoS (CIR = x)– BP at the UNI

• All EVCs share bandwidth• Customer responsible for traffic policing

across EVCs– BP port speed

UNIEVC1

EVC2

EVC3

Ingress Bandwidth Profile Per Ingress UNI

UNIEVC1

EVC2

EVC3

Ingress Bandwidth Profile Per Ingress UNI

• EVP-LAN (option 1)– E-LAN; MP2MP topology– Emulates a TLS– 1 UNI, 3 EVCs, 1 QoS (CIR = x)– BP at the UNI

• All EVCs share bandwidth• Customer responsible for traffic policing

across EVCs– BP port speed

16

BP Option #2 - EVPL

UNIEVC1

EVC2

EVC3

Ingress Bandwidth Profile Per EVC1

Ingress Bandwidth Profile Per EVC2

Ingress Bandwidth Profile Per EVC3

• EVPL (option 2)– E-Line; P2P or P2MP topologies– Emulates a muxed PL service– 1 UNI, 3 EVCs, 1-3 QoS values

• CIR = x, y, z where x, y, z can be the same or different for each EVC

– 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

BP Option #2 - EVP-LAN

UNIEVC1

EVC2

EVC3

Ingress Bandwidth Profile Per EVC1

Ingress Bandwidth Profile Per EVC2

Ingress Bandwidth Profile Per EVC3

• EVP-LAN (option 2)– E-LAN EVC type; MP2MP

topology– Emulates a TLS– 1 UNI, 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