IP and Optical Convergence: Rationale and Requirements

Transcription

1 IP and Optical Convergence: Rationale and Requirements Juan Pedro Fernandez-Palacios ECOC 2014 Sept 2014 Telefónica GCTO

2 03 What is Multilayer convergence? Multilayer planning Multilayer control plane integration Multilayer data integration (colored interfaces) All of these pieces are not necessarily put in place at once. 2

3 Different scenarios for IP and Optical convergence Control Plane Integration Separation Integration Optimized scenario Monovendor solutions available Multivendor could be technically feasible: pluggable optics + multilayer control plane Metro/backhaul: PtP metro/backhaul links (no optical control plane) Core: Current approach for multivendor core networks. Optical restoration was not supported in multivendor networks. Potential overinvestments in IP back up resources. Data Plane Separation Multilayer resilience, network provisioning Multivendor solutions available Current situation 3

4 01 Use cases for multilayer coordination 4

5 L2 Aggregation 02 Current Multilayer Coordination IP/MPLS Access IP/MPLS Transit IP/MPLS IX IP/MPLS IX IP/MPLS Transit IP/MPLS Access Access Network IP/MPLS Residential IP services, L3 VPN,... L2 VPN,.. Metro Core ISPs Core Metro Inter/ction Load balancing is triggered by the Network Management System according to off-line multilayer optimization algorithms WSON Carrier A Carrier B Load balancing between IP/MPLS and WSON. High capacity flows (e.g between IP access and IP interconnection) are directly transported over WSON 5

6 02 Current multi-layer provisioning Hours Hours/Days Hours/Days Very costly Time Money Human dependent Hours 6

7 Pending standardization work NOW!! 02 What do we want of a multi-layer network? Router is configured IP link 1-3 IP node 1 IP node 2 IP node 3 In multivendor scenarios IP i/f 1 IP i/f 0 IP/MPLS network T i/f 1 ML link 1-3 T-node 1 λ 2 T-node 2 T i/f 0 T-node 3 Photonic Mesh Standard interface to configure the routers. NETCONF is standard (RFC 6241), but data models are vendor dependent. T-node 4 Openflow enables standard configuration of flow tables. Is it enough? Multilayer topology information Pending exchange. standardization work An element is required to configure VNT to the upper layer through a standard interface. Functional validation of the cooperation between Virtual Network Topology Manager (VNTM) and Path Computation Element (PCE), IPOP

8 02 Automated Multi-layer Provisioning < Seconds < Seconds Seconds/Minutes 8

9 03 Multi-layer Restoration Multi-layer restoration consist on using the increased DWDM layer connectivity and dynamicity to recover both layer failures. Multi-layer restoration allows to increase availability due to the higher number of resources to drive traffic available. Access Region 2 Transit R2 Interconnection Access R1 Transit R1 Transit Backup R3 Transit R3 Access R3 9

10 Control plane requirements The number of IP ports saved thanks to the addition of optical restoration in Telefonica s Spanish backbone is 37% in Control plane integration required to keep optical restoration - Savings IP Ports Cost (%) Incremental Gain (%) IP Ports Cost (%) Incremental Gain (%) FRR 100% 0% 100% 0% FRR+Multilayer optimization 92% 8% 82% 18% Multilayer optimization + Optical restoration 75% 17% 50% 37% 10

11 03 Multilayer restoration: Alternatives comparison 1+1 Protection and Multilayer Restoration 1+1 Protection, multilayer restoration (additional router) Multilayer restoration only OPEX Reduction Highest reduction No change CAPEX No change Increase Reduction Failure recovery time 1 st failure: 50 ms 2 nd failure: 1 minute (approx) without FRR 1 st failure: 50 ms 2 nd failure: 50 ms 1 st failure: 1 minute (approx) without FRR 2 nd failure: 1 minute (approx) without FRR 11

12 02 Control plane requirements 12

13 Control Plane Requirements Basic UNI (set up tear down, no wavelength) Select service type (restoration) Basic automated network provisioning Use cases (Data plane Separation) Differentiated resilience (FRR+GMPLS) Multilayer Shared Restoration Alien Wavelength Restoration UNI with wavelength (in ERO or Label Sets) Collect SRLG information Collect TE metrics UNI with route exclusions UNI with service constraints Automated network provisioning PCEP from router 13

14 Recommendations and call for action Automated Operation Adaptation to Traffic evolution Low cost Disaster recovery BW adjustment for BoD Data Plane Integration Bus/ring (Metro) Bus wo CP (Core) Multilayer Management Problems to be solved Basic UNI is not enough Extended reach Multivendor interoperability Operational complexity Multivendor interoperability Technology enablers Recommendations Basic UNI (set up tear down, no wavelength) Select service type (restoration) UNI with wavelength Collect SRLG information Collect TE metrics UNI with route exclusions UNI with service constraints PCEP from router Pluggable optics including OTN and FEC Black Link Standard solutions to enable a converged management/sdn Multilayer planning Single vendor solutions Multilayer optimization in multivendor networks Multilayer Resilience Differentiated resilience (FRR+GMPLS) Multilayer shared resilience Alien wavelength restoration Basic UNI is not enough Basic UNI and Select service type (restoration) UNI with wavelength 14

15 03 Multilayer SDN 15

16 02 Which architecture fits in a Network Service Provider? SDN CONTROLLER Big black box controlling the network Centralize functionalities to enable automation Define simple standard interfaces 16

17 02 SDN orchestration approach Current SDN solutions are mainly focused on single domain and monovendor scenarios (e.g data center) SDN architectures for heterogeneous networks with different technologies (IP, MPLS, Ethernet, optical ) and equipment providers are still under definition. We propose a SDN orchestrator architecture based on the ABNO (Application Based Network Operation) architecture because: ABNO is not a monolithic controller. ABNO is based on existing standard blocks defined within the IETF (PCE, ALTO, VNTM ) which could be implemented either in a centralized or distributed way according to network operator requirements. ABNO is specially adapted to multidomain and multivendor networks enabling interoperability between traditional control plane (e.g IP/MPLS, GMPLS) and OpenFlow domains (e.g Data Center). The SDN orchestrator defined in ABNO is not substituting the distributed control plane but interworking with it. 17

18 02 SDN orchestration approach SDN orchestrator: It takes decisions on E2E network configuration and resources allocation according to service and network optimization criteria Abstracted information about network status Control plane triggering Multilayer and multidomain control plane: It executes network configuration according to SDN orchestrator request 18

19 02 SDN controller based on IETF building blocks Applications (Internet, CDN, cloud ) 4-ALTO 3- ABNO controller 5-OAM Handler 1- TED 6-VNTM 2-PCE 7-Provisioning Manager SDN Controller OPENFLOW OPENFLOW NETCONF PCEP OPENFLOW CLI OpenFLow Data Center OpenFlow MAN Domain IP/MPLS core GMPLS Optical Domains OpenFlow Optical Domain MPLS MAN 19

20 Multi-layer provisioning Workflow IP link provisioning (no path SDN controller requests L3-PCE (stateless) a path between routers. If L3-PCE can not find a path in L3 topology, it asks VNTM for a new link in the VNTM. After checking for policy rules, VNTM asks for a path to L0/L1 PCE between two transport nodes. ALTO Server Databases TED LSP-DB OSS/NMS / Application Service Orchestrator Policy 2 Agent 5 VNTM SDN Controller 7 L1/L0 PCE 3 L3 PCE Provisioning Manager Client Network Layer Server Network Layer 9 10 Response is returned to the SDN controller. SDN controller checks if the establishment of a transport path is needed. If new transport bandwidth is required, the SDN controller would first configure the transport nodes using PCEP, UNI or OpenFlow. Once the transport layer is configured, routers must be updated (e.g OpenFlow, NetConf, CLI ) I2RS Client OAM Handler 20 20

21 04 Conclusions 21

22 04 Conclusions Main challenge for IP and Optical convergence is multivendor interoperability Multivendor control plane coordination is feasible SDN and control plane could be complementary pieces of work in e2e transport networks 22

23 23