Presentation is loading. Please wait.

Presentation is loading. Please wait.

SPARC: use-cases and results Requirements and Controller Architecture Wolfgang John November 23th 2012.

Similar presentations


Presentation on theme: "SPARC: use-cases and results Requirements and Controller Architecture Wolfgang John November 23th 2012."— Presentation transcript:

1 SPARC: use-cases and results Requirements and Controller Architecture Wolfgang John November 23th 2012

2 Split Architecture for Carrier-Grade Networks.  EU FP7 Project  Start date: July 2010; End date: November 2012 (1 week ago …)  6 Partners: ER Kista ER Budapest = ACREO

3  Mission: Applying Software Defined Networking (SDN) to operator networks  Results  23 publications, presentations and demos (GENI engineering conference, World Telecommunication Congress, Globecom, etc.)  Standardization impact in ONF and IRTF  Key Project Deliverables  D2.2: Use cases, requirements, techno-economic study (CAPEX and OPEX), business environment  D3.3: Main technical document, study of architecture and required extensions  D4.2: Documentation of specific OpenFlow extensions  D4.3: Technical documentation of implementation and prototyping activities  D5.2: Results of validation and performance evaluation  Movie: Summarizing the most important demo’s  (Soon) all to find on: Split Architecture for Carrier-Grade Networks. ACREO

4 SPARC. Project Team. ACREO

5 LSR Optical transport BRAS Backbone LERAGS2 GPON OLT AGS1 Outdoor DSLAM DSLAM Business RGW Switch / Router Data Centre Other Service Platforms (mobile, business, IPTV, VoIP,...) Access/Aggregation AAA Auto- configuration Network Management Service Management OAM subsystem Use Case Areas. Focus on Access/Aggregation. ACREO

6  The vision of SPARC is to define, implement & evaluate a scalable carrier class Split Architecture.  Seven objectives of SPARC, with the three main objectives highlighted:  Definition of typical use cases for Split Architecture (D2.2)  Analysis and description of business potential (D2.2)  Definition of Split Architecture blueprint (D3.3)  Extension of the OpenFlow protocol (D3.3 and D4.2)  Development of SPARC prototype (D4.3)  Validation of SPARC prototype (D5.2)  Exploitation of results (papers, demos, presentations, videos) SPARC. Main Objectives. ACREO

7  What is carrier-grade?  Scalability  Support large-scale deployments for carrier-grade networks. E.g. a controller shall be able to control forwarding devices that could count in the order of hundreds.  Availability and Reliability  The availability of networking services shall be equivalent to that of traditional technologies.  Network and service management  The ability to monitor, diagnose and centrally manage the network  Quality of Service  Allowing the assurance of SLAs using QoS guarantees for service attributes (e.g. rate, loss, delay) and service isolation  Support for legacy technology  allowing deployment of new services in parallel to existing legacy protocol stacks SPARC Objectives. Carrier-grade. ACREO

8 SPARC Requirements and Study Topics. Overview. Requirements (study topics) from WP2 WP3: Problem and Solution Description WP4: OF ExtensionsWP4: Prototype Integration /Implementation WP5: Validation / Performance Evaluation Controller Architecture Yes Network Management YesNo Service Creation Yes Virtualization & Isolation Yes OAM Yes Openness & Extensibility Yes Control Channel Bootstrapping & Topology Discovery YesN/AYes Network Resiliency YesN/AYes Energy-Efficient Networking Yes No Quality of Service YesNo Multilayer Aspects YesNo Scalability Yes (numerical validation) N/A Yes 1 2 ACREO

9 Intro to SplitArchitecture. Evolution of SDN. ACREO

10 OpenFlow-based SDN model, defined by the ONF Intro to SplitArchitecture. Software-Defined Networking. data SDN control software network services business applications ACREO

11 OpenFlow-based SDN model, including a network hypervisor – Virtualization and abstraction layer – Position of hypervisor (below or above NOS) debatable Intro to SplitArchitecture. Software-Defined Networking. data SDN control software network services business applications control program data hypervisor network operating system business applications ACREO

12 SPARC SplitArchitecture – Again a split between data and control plane – Forwarding and processing in data plane considered separately Intro to SplitArchitecture. The SplitArchitecture concept. control program data hypervisor network operating system business applications ACREO

13 SPARC SplitArchitecture – Again a split between data and control plane – Forwarding and processing in data plane considered separately Intro to SplitArchitecture. The SplitArchitecture concept. OpenFlow hierarchical controller concept forwarding processing ACREO

14 SPARC SplitArchitecture – Initial considerations on the role of network management Intro to SplitArchitecture. The SplitArchitecture concept. network management system OpenFlow hierarchical controller concept forwarding processing ACREO

15 SPARC SplitArchitecture – Recursively stacked control planes – Abstracted network view ot higher planes via OpenFlow Interface Intro to SplitArchitecture. The SplitArchitecture concept. OpenFlow hier.controlplanen+1 hier.controlplanen hier.controlplanen-1 app OpenFlow hierarchical controller concept filtered, abstract network view forwarding processing network management system ACREO

16 Intro to SplitArchitecture. The SplitArchitecture concept. SPARC SplitArchitecture – Recursively stacked control planes – Abstracted network view ot higher planes via OpenFlow Interface ACREO

17 Goals for a carrier-grade control layer: – Increase flexibility Adapt control architecture to use-cases and business models Distribute the control layer to adapt to network capabilities Allowing both cross-layering and strict layering of control logic – Increase scalability Operator networks are complex -> divide and conquer the problem space – Allow smooth migration Supporting control protocol operations with legacy domains Hierarchical controller. Design goals. ACREO

18 CP DP CP peers talk OSPF, IS-IS, STP, etc. FWD engine (DP) and control logic (CP) sit jointly on a single network element Hierarchical controller. Current situation: monolithic network elements ACREO

19 DP CP OpenFlow But still the old situation  the CP peers control a single network element and use the old protocol for sharing state as before (OSPF, IS-IS, LDP, STP, …) Hierarchical controller. Splitting Ccontrol and forwarding. Step 1 of SDN: Splitting control from data plane ACREO

20 Step 2 of SDN: Centralize control plane Hierarchical controller. Centralizing control. Benefit: no complex protocols for sharing state among CP peers required any more. Centralized control logic DP OpenFlow ACREO

21 Centralized control logic DP Domain acts like a backplane within the emulated data path element. OpenFlow Mgmt API SPARC Idea #1: Exposing services via OpenFlow again! Hierarchical controller. OpenFlow as northbound interface. OpenFlow ACREO

22 Flowspace Mgmt Hierarchical controller. Flow space registration. Centralized control logic DP Higher layer controllers subscribe to parts of the flowspace (i.e. slices) Replace the pub/sub interface (as in NOX) with flowspace reservation OpenFlow Mgmt API OpenFlow SPARC Idea #2: Integrate FlowVisor functionality into controller ACREO

23 Requires OpenFlow protocol extensions for management of: * Flowspaces: allow plane (n) to register a slice of the flowspace on (n-1) * Transport endpoints: allow plane (n) to control (CRUD) logical ports on (n-1) Result: Hierarchical structuring of control planes! Hierarchical controller. Stacked control planes. ACREO

24 IP ETH 4/14/2015 PHY SMTP IPv4 IPv6 ETH PHY An IP router  use case: build an IPv4/IPv6 router An SMTP router  use case: build a Mail Transport Agent (MTA) DP SMTP ETH IPv4 OpenFlow PHY-CTL ETH-CTL APP-CTL IP-CTL = IP-CTL  emulates a single IP layer ETH-CTL  emulates Ethernet host stacks PHY-CTL  is a data path element The northbound interface is OPENFLOW! Hierarchical controller. Example: protocol stack. Example: Modular layering of a controller ACREO

25 SPARC SplitArchitecture – Initial considerations on the role of network management Considerations on network management. The SplitArchitecture concept. ACREO

26 Considerations on network management. Control vs. management. Boundary between management and control is blurred – Management functions are important in SplitArchitecture Today’s Network Management SplitArch/ SDN Functionality (Increased control granularity) Automation (Program driven, automatic adjustment of the network) Speed (Beyond human time-scale) ACREO

27 Which NM functions to embed in a controller? – Q1: Already an essential part of SplitArchitecture/SDN control? If not, – Q2: Facilitates timely and automated configuration and flow steering? If so, – Q3: Possible with open and standardized extensions to the OF / OF- Config protocols? (no bloating with vendor or device specific models) Apply this question to NM function according the TMN/FCAPS definitions of network management Considerations on network management. Assessment of functions. ACREO

28 Considerations on network management. SPARC assessment example. ACREO

29 Control and management architecture. Summary. Result: A recursive and modular control plane architecture control plane A control plane B e.g. optical devices network management system OpenFlow hierarchical controller concept forwarding processing ACREO

30 SPARC: use-cases and results SPARC prototype implementations Wolfgang John November 23th 2012

31 Seamless MPLS aka carrier grade packet transport Seamless MPLS “…architecture which can be used to extend MPLS networks to integrate access and aggregation networks into a single MPLS domain…” draft-leymann-mpls-seamless-mpls-03 Forklifting access/aggregation to MPLS may be too expensive  apply SDN principles for Seamless MPLS ACREO

32 Central element IP/MPLS core Aggregation IP Edge Access GW Service Switch CP OpenFlow IP MPLS OSPF, LDP, RSVP-TE, BGP … CP SPARC Controller Protocol Proxy CP APP (CP) Seamless MPLS implementation. Basic concept. ACREO

33 1.Topology discovery of MPLS aggregation & core 2.Management of MPLS LSPs in aggregation 3.Signal end-to-end MPLS LSPs 4.Provision MPLS transport services (e.g. Pseudowire) Video WEB Client MPLS CP OF Switch OF Edge OF Edge IP/MPLS core OPENFLOW MPLS Aggregation NNI OSPF, LDP OF Switch Core MPLS ServicesClients Client SPARC Controller NOX Kernel OpenFlow MPLS CTRL Protocol Proxy OSPF LDP End-to-end MPLS CTRL Discovery Seamless MPLS implementation. Essential Functionalities. ACREO

34 IP/MPLS core OPENFLOW MPLS Aggregation Services Clients MPLS CP Core MPLS MPLS CP OF Switch OF Access OF Access OF Switch Video WEB Client NOX Kernel Discovery Protocol Proxy OSPF Combine OpenFlow and legacy topology discovery information Seamless MPLS implementation. 1. Topology disovery of MPLS aggegation & core. ACREO

35 IP/MPLS core OPENFLOW MPLS Aggregation Services Clients MPLS CP Core MPLS MPLS CP OF Switch OF Access OF Access OF Switch Video WEB Client SPARC Controller NOX Kernel OpenFlow MPLS CTRL Discovery Installs PtP, MPtP and PtMP tunnels Reconfigures them upon topology changes Seamless MPLS implementation. 2. Management of MPLS LSPs in aggregation. ACREO

36 IP/MPLS core OPENFLOW MPLS Aggregation Services Clients MPLS CP Core MPLS MPLS CP OF Switch OF Access OF Access OF Switch Video WEB Client Topology synchronization with OSPF Spans end-to-end MPLS with LDP Nests them in MPtP tunnels in aggregation SPARC Controller NOX Kernel OpenFlow MPLS CTRL Protocol Proxy OSPF LDP End-to-end MPLS CTRL Discovery MPLS Tunnel Seamless MPLS implementation. 3. Signaling end-to-end MPLS LSPs. ACREO

37 Split-BRAS BRAS is complex and expensive integrated node since it must handle all subscriber traffic, hence it must cope with continuously increasing capacity need, this means increasing cost Traditional way of deploying BRAS will not scale  apply SDN principles to distribute BRAS functionality ACREO

38 RAW BRAS AN AGS 1AGS 2 BRAS RADIUS Client (RGW) PPPoE tunnel AN AGS 1 AGS 2 RADIUS Client (RGW) PPPoE tunnel Control session AN AGS 1 AGS 2 Client (RGW) PPPoE tunnel IP Edge RADIUS Control session Aggregation specific tunnel Common residential model today with PPPoE Split Control and raw forwarding Roll raw BRAS toward Access Node RAW BRAS Split BRAS. Basic concept. Control session ACREO

39 Applying a recursive control plane data path element control plane A control plane B L2 fwd engine (disabled) EoPhy L3 fwd engine IPoE PPP & PPPoE EoPhy Split BRAS. Architecture Blueprint. ACREO

40 Central element IP/MPLS core Aggregation IP Edge Access GW SPARC Controller Split BRAS. Concept. RAW BRAS Relay PPP Request Ethernet IP/MPLS ACREO

41 Central element IP/MPLS core Aggregation IP Edge Access GW SPARC Controller Split BRAS. Flexible placement. RAW BRAS Switch PPPoE (over PWE) ACREO

42 Central element IP/MPLS core Aggregation IP Edge Access GW SPARC Controller Split BRAS. Increased scalability. Switch PPPoE (over PWE) RAW BRAS IP/MPLS ACREO

43 Summary of SPARC OpenFlow Protocol Extensions implemented. MPLS – Parsing MPLS headers – Basic MPLS actions: push/pop header, change TTL, … PPP & PPPoE – Terminate PPP & PPPoE tunnels Connectivity Check – Pro-active monitoring of contuity with probe packets of MPLS-TP BFD format – Used for monitoring adjacency and flow pairs (bidirectional path) OAM & Protection Notification – About state changes of monitoring entities – About protection events Pseudo Wire – Support for Ethernet Pseudo Wire over MPLS PSN – Not full implementation (i.e., no sequence numbers) ACREO


Download ppt "SPARC: use-cases and results Requirements and Controller Architecture Wolfgang John November 23th 2012."

Similar presentations


Ads by Google