Challenges and Opportunities for SD-WAN in China

Recently, SD-WAN market have seen significant growth in the US and other countries, but there're several challenges in China market. The first challenge is the communication quality of inter service providers, this makes endpoint to endpoint internet overlay tunnel communication unreliable (e.g. China Telecom endpoint to China Mobile endpoint), also missing public IP at endpoint puts additional difficulty on creating end to end overlay tunnel. Secondly, China service provider expects seamless integration between traditional MPLS and internet based solution, i.e. branches may have both MPLS and internet access, or only one of them. SDWAN solution has to exchange routing information between traditional MPLS and internet based network.

1.Challenges and Practice for SDWAN in China Jerry Ziyi Lu CTO, Tethrnet Technology

2.What’s SDWAN

3.SDWAN? Software Defined Wide Area Network v DCI? v VPN? v Overlay on Internet? v Auto configuration? v Quick deployment? v Low cost? v Simple operation?

4.WAN Envolving

5.WAN Requirement

6.SDWAN! v Meet WAN requirement via SDN v Strict (openflow, control/data plane separation) to more generic v Generic SDN v Programmable (overlay, virtualization) v Data Analytics v Intelligent Control (more than routing protocol)

7.SDWAN Challenges

8.C1: internet end to end VPN v Internet Overlay end to end VPN,NOT good for China vinter-SP vLack of public IP


10.C2: SaaS access v SaaS or public cloud access, not covered by traditional WAN solution

11.C3: Backbone Network v Do we need backbone network? v Backbone network can be pure built upon Internet? v Can leverage the existing backbone network, such as MPLS VPN network? v Can current MPLS VPN user seamlessly adopt to SDWAN? v Hybrid network: SDWAN + MPLS VPN backbone

12.C4: Traffic Engineering v Access vInternet/MPLS performance monitoring, auto switching v Backbone vDynamic load balancing, route optimization

13.C5: Centralized vs Distributed v Centralized Controller vGood for Global view/control vNot good for fast failover v Distributed Controller vRouting Protocol?

14.SDWAN Practice

15.Access Network

16. Traditional Solution v MPLS/MSTP v Good: Security, SLA v Bad: Flexibility, Cost v Internet VPN v Good: Flexibility, Cost v Bad: SLA, Operation v CloudVPN v Internet + MPLS !

17.Internet as Last Mile

18.Backbone Network

19. Traditional Solution v MPLS-VPN vGood: Stable, Fast Failover vBad: Traffic Engineering, Complex Configuration and Operation(LDP, RSVP)

20.Backbone Re-Arch v Web v Google: B4 v Facebook: EBB v SP v ATT: domain 2.0 v Key Points: v Stability (control plane and data plane) v Failure detection and fast failover (<50ms) v Traffic engineering, dynamic route optimization v Segment Routing !

21. SR-TE v SR-TE + SDN Controller v SR-TE: vData Plane: MPLS vControl Plane:SR or Controller (No LDP/RSVP) v SDN Controller: vGlobal Resource Management vDynamic Path Computation

22.SDWAN Solution

23.SDWAN Modules System deployment Infrastr HA/Cluster ucture Traffic Engineering QoS, Fast Failover, Path Back Multiple Access Access computation, L2/L3 VPN bone Internet/MPLS access, auto switching, SD-WAN L2/L3 access End to end service Equipm Northbound API, portal per Orchest ent different role users ration Manage ment Multiple Vendor Monitor Southbound API, Zero touch Topology, Network Status deployment Traffic per Tenant/flow/tunnel/Equipment, real time and history, Alarm