Driving Ethernet Deeper Ethernet Business Services over DOCSIS COX New Orleans (NOLA) Case Study Kashif Islam, Technical Leader – Cisco Carlos Sanchez, Systems Engineer – Cisco Edward Kerner, Network Engineering Supervisor – COX New Orleans 1 CESNA 3.1 SI&I Priorities and Deliverables
Agenda � Carrier Ethernet Business Services � COX New Orleans Telecommuter Service � Deployment Challenges and Service Evolution � Summary and Q&A 2 Driving Ethernet Deeper – COX NOLA Case Study
Carrier Ethernet Business Services 3 Driving Ethernet Deeper – COX NOLA Case Study
Business VPN Services � Mass scale Carrier Ethernet Services adoption � MPLS-based L3 VPN and L2 VPN services � Advantages of L2 VPN services over L3 VPN: –Protocol Agnostic –No protocol sharing between SP and Customer –More customer control over their network –Simpler to deploy � Standardized Carrier Ethernet L2VPN Services 4 Driving Ethernet Deeper – COX NOLA Case Study
Carrier Ethernet L2VPN Services E-LINE Services E-LAN Services Port-based Ethernet Private Line (EPL) Ethernet Private LAN (EP-LAN) Replaces a TDM private line Supports dedicated UNIs Dedicated UNIs for point-to-point connections Supports transparent LAN services Single Ethernet Virtual Connection (EVC) per UNI Supports multipoint Layer 2 VPNs The most popular Ethernet service due to its simplicity VLAN-based Ethernet Virtual Private Line (EVPL) Replaces Frame Relay or ATM services Supports service multiplexed UNIs (i.e., multiple Ethernet Virtual Private LAN (EVP-LAN) EVCs per UNI) Supports service-multiplexed UNIs Allows single physical connection (UNI) to customer Supports multipoint Layer 2 VPNs premise equipment for multiple virtual connections E-Tree Services not shown here * 5 Driving Ethernet Deeper – COX NOLA Case Study
Carrier Ethernet Components � User-to-Network Interface (UNI) – Physical demarcation between Subscriber and MSO � Network-to-Network Interface (NNI) – Physical demarcation between individual Carrier Ethernet networks � Ethernet Virtual Circuit (EVC) – Logical end-to-end service representation MSO/Service Provider A MSO/Service Provider B Subscriber Subscriber Site Site External-NNI UNI UNI Internal-NNI Internal-NNI CE CE 6 Driving Ethernet Deeper – COX NOLA Case Study
Business Services Over DOCSIS � Builds on standard defined by MEF � Competitive advantage for Cable SPs due to HFC reach � DOCSIS 3.0 offer new opportunities for BSOD –Higher speed with Channel bonding –Effective competition against T1, leased line and in some cases, fiber � Multiple Deployment Options – Transparent LAN Services over DOCSIS – 802.1Q (Dot1Q) Based BSoD – MPLS based BSoD 7 Driving Ethernet Deeper – COX NOLA Case Study
COX New Orleans Telecommuter Service 8 Driving Ethernet Deeper – COX NOLA Case Study
COX New Orleans Telecommuter Application Service Objectives and Requirements � To provide telecommuters with Layer 2 Access to Central Office � Use existing HFC access in Home Office � Each Home Office contains: � IP Phone for Voice over IP traffic � PC for Data traffic � VoIP and Data Traffic to use separate VLAN’s in CO Call Manager(s) Telecommuter (s) Data Center Enterprise CM Layer 2 Ethernet Service DHCP Servers Application Server Farm 9 Driving Ethernet Deeper – COX NOLA Case Study
COX New Orleans Telecommuter Application Service Architecture � H-VPLS to provide MAC learning and bridging at Central Location � Transparent LAN Services over DOCSIS used on CM and CMTS � CMTS encapsulate all traffic from CM in a 802.1Q VLAN Tag � Data traffic is untagged; VoIP is Tagged for service separation Telecommuter (s) Server Farm Enterprise Data VLAN VoIP Data Center VoIP VLAN VoIP Data VLAN Data IP/MPLS Metro VoIP Network MPLS Label (s) MPLS Label (s) Call Managers VLAN VoIP VLAN TLS VLAN VoIP HFC L2 802.1Q Handoff VoIP Data VoIP Fiber Carrier Data Ethernet Network EoMPLS VC for H-VPLS MPLS CMTS H-VPLS PE Agg 10 Driving Ethernet Deeper – COX NOLA Case Study
COX New Orleans Telecommuter Application Service Traffic Separation � CMTS adds a TLS over DOCSIS tag to all traffic � Data Traffic is single tagged � VoIP is double tagged, with same S-VLAN as Data � Flexible frame matching needed on upstream router VLAN 100 VoIP VLAN 100 Physical Loopback Data MPLS Label (s) MPLS Label (s) Intelligent Packet Classification VLAN VoIP VFI Data VoIP VLAN 100 EoMPLS VC for H-VPLS MPLS PE Data VLAN Data Data IP/MPLS Metro Server Farm Network VoIP VoIP VLAN Fiber Carrier Ethernet Network VoIP Call Manager(s) 11 Driving Ethernet Deeper – COX NOLA Case Study
Deployment Challenges and Service Evolution 12 Driving Ethernet Deeper – COX NOLA Case Study
Service Deployment Challenges � End-to-End Traffic Isolation � Centralized solution difficult to troubleshoot � Per Site CMTS Configuration � CMTS manually configured for each site � L2 Problem Detection and Isolation � End-to-end troubleshooting tools are mainly Layer 3 � Cable Modem down, but L2 circuit active � High Availability and Load Balancing � Only one forwarding interface per CMTS � Service Scale � 4000 services (VLANs) total 13 Driving Ethernet Deeper – COX NOLA Case Study
Service Evolution � Cable Labs compliant Business Services over DOCSIS (BSoD) � 1) Dot1Q-based BSoD � Similar to TLS over DOCSIS but supports: � Multiple VLAN’s for single CM � Provisioning through Cable Modem Config file � 2) MPLS-based BSoD � Enables MPLS PE functionality on CMTS � Provisioning through CM Config file � MPLS-based load balancing and High Availability 14 Driving Ethernet Deeper – COX NOLA Case Study
Dot1Q Based BSoD for Telecommuter Service Enterprise VLAN VoIP Data Center IP/MPLS Metro VoIP Fiber Carrier Network Ethernet Network Data Data Data VoIP Service EoMPLS VC for H-VPLS VoIP VoIP MPLS Label (s) Flow VoIP MPL PE CMTS H-VPLS Agg VoIP Data Data VoIP VLAN Data VLAN Telecommuter (s) � Changes from TLS over DOCSIS Design: Server Farm Call Managers Challenge Impact � Use multiple services flow with VLAN based Traffic Isolation Classification Per site Configuration � Assign per-traffic VLAN L2 Problem Detection Future � Use Cable modem Configuration file for CMTS CM Down Propagation side processing High Availability and Load Balancing Service Scale (CMTS) 4000 15 Driving Ethernet Deeper – COX NOLA Case Study
MPLS Based BSoD for Telecommuter Service Enterprise VLAN VoIP Data Center IP/MPLS Metro Telecommuter (s) Network Fiber Carrier VoIP Ethernet Network Data Data VoIP Service EoMPLS VC for H-VPLS VoIP MPLS Label (s) Flow VoIP CMTS H-VPLS MPLS PE Agg VoIP Data Data VoIP VLAN Data VLAN � Changes from TLS over DOCSIS Design: Server Farm Call Managers � CMTS as MPLS PE !!!! Challenge Impact � Use multiple services flow with VLAN based Traffic Isolation Classification Per site Configuration � Assign per-service flow EoMPLS PW L2 Problem Detection Future � Use Cable modem Configuration file for CMTS CM Down Propagation side processing High Availability and Load Balancing � Simplest End-to-End Design !! Service Scale (CMTS) upto16000 16 Driving Ethernet Deeper – COX NOLA Case Study
Summary 17 Driving Ethernet Deeper – COX NOLA Case Study
Summary � Business Services over DOCSIS picking steam � Leverage existing HFC infrastructure for MEF Services � Multiple deployment option for Business Services over DOCSIS � TLS over DOCSIS for COX Telecommuter application � Metro network key for end-to-end Layer 2 transport � Dot1Q- and MPLS-based BSoD offers enhanced functionality and flexibility 18 Driving Ethernet Deeper – COX NOLA Case Study
Q & A 19 Driving Ethernet Deeper – COX NOLA Case Study
Recommend
More recommend
