Peering as a Cloud enabler for Enterprises Lionel MARIE Network architect Schneider Electric Advisor Self employed Former Board Member France-IX (2013-2015)
Schneider Electric at a Glance We are the global specialist in energy Management and efficiency technologies Balanced geographies billion revenue (FY 2015) of sales devoted to R&D North America 25% Rest of World 20% Western Europe 28% Asia Pacific 27% of revenue in IoT people in 100+ countries Balanced end markets Industrial & Machines 28% Utilities & infrastructure 21% Data centres & networks 15% Non-residential and Residential buildings 36% 2
The Big Picture SSL VPN mobile users Data Center Nordic zone 1400+ remote sites 4 global data centers + several data rooms EMEA WAN 2 MPLS / MAN telcos + domestic networks France Full control USA on Network CoS / QoS (MPLS / MAN) Global WAN Full WAN acceleration, end to end India China Singapore Full network visibility using NPM & APM UK Ireland Japan 2 centralized Internet break-outs, 140+ local break-outs Austalia 3
And then came the 4
Schneider Electric and the Cloud 5
and then came the troubles Network guy (me ) 6
Internet usage in large companies Before: Internet was a commodity access to reach non-businness critical content. Now: Non business traffic is increasing: social networks, video Internet is used to access business critical applications SaaS: Salesforce, Office 365, SFB, Webex, Box.net, IaaS: Amazon Web Services, Microsoft Azure, Softlayer,, à Internet access becomes as critical as MPLS Gentle reminder: Internet = Public network with no SLA, poor (no?) control on routing, no CoS, no network visibity, no 7
AWS as a trigger of our peering policy 8
A powerful IaaS offer for Virtual Private Clouds Seen as virtual rooms connected to our data centers 1200+ VMs in 3 AWS regions, and counting (21 VPCs) in 2012, IPsec tunnels were used to connect to AWS VPC à Challenge: how to provide MPLS-like connectivity? 9
The challenge of moving applications into a Virtual Private Cloud ISP1 Direct connectivity Internet ISP3 IPsec ISP2 ISP4 10
Amazon as a first trigger for our Cloud Access Policy in Europe Mb/s Transit traffic vs. peering traffic Internet VPC??? Direct Connect 48 months with 100% uptime??? ISP #1 ISP #2 Data Center France 2014 2015 2016 2017 11
AWS traffic 12
O365 traffic 13
Webex 14
Google 15
Current peering policy in St Louis DC Mb/s Transit traffic vs. peering traffic Internet AT&T IXP (Chi) IXP (NY) Level3 Data Center St Louis 2014 2015 Schneider Electric US 2016 2017 16
Global Cloud Access policy 17
Global Peering Policy Other dest. Direct connectivity IXP1 IXP2 Internet / Cloud Hub Private Zen node MPLS 18
Cloud / Internet Hubs Transit Transit IXP #1 IXP #2 #1 #2 Cloud Access Provider Cloud Access Provider Legacy DC Carrier neutral data center MPLS Internet / Cloud hub 19
Putting all together: - Internet / Cloud hubs - Peering policy - SDWAN 20
Private peering Direct Connect Public Internet peering VPCs Network hub ISP 4G / 5G SDWAN Overlay Network Legacy data center Legacy $ $ $ MPLS Branch Broadband Internet Access $ 21
The next steps Replicate our peering policy, worldwide à Create 15 Internet / Cloud connectivity Hubs Adapt our network transport toward the hubs (SDWAN) Deal more peering agreements with cloud providers Orchestrate the network: SDN / SDWAN / SDDC to better connect to the Cloud and to better connect Internet to our Cloud. 22
Main takeaways Peering adds quality and better control on network paths Public peering is not expensive and easily scalable Win / Win solution for Enterprises and Content providers A better solution to get Cloud content over SDWAN 23
Thank you! 24