Voice of the Customer First American Title SD-WAN Transformation

Transcription

1 Voice of the Customer First American Title SD-WAN Transformation CJ Metz First American - Senior IT Manager, Network Eng Archish Dalal Viptela Senior Systems Engineer #FutureWAN

2 First American Financial Corporation This presentation and the related remarks reflect the views of the presenter and do not necessarily represent the views of First American. 2

3 Project Background Branch Connectivity Today: MPLS (Single or Dual T1) as our primary circuit for all connectivity (Interoffice/DC/INET) This connectivity architecture was first introduced in 2002 Problem Statement: Bandwidth Constraints: Richer applications, multimedia traffic and a growth in cloud/saas application consumption Cost: Demand for bandwidth cannot keep up with the existing TDM-based MPLS architecture Uptime: Single Circuit could potentially result in office network/phones down Scope: Beginning in 2013, the Network Engineering team sought out various carrier and technology solutions to address bandwidth consumption needs Goal: Provide a more productive user experience to our remote offices without increasing cost to the business 3

4 Evaluation Criteria for SD-WAN App-Aware Routing on based on network health & App requirements Integration with existing infrastructure (BGP, Monitoring Tools, etc) Regional Specific Routing Topologies (Hub-n-Spoke, Full Mesh, Internet POPs) Centralized device management & Policy administration Built in HA provides Automatic Failovers Easy Encryption on all transports Zero Touch Provisioning QoS and Config Parity with current branch design 4

5 Hybrid WAN Design DC-1 DC-2 1. Router advertises /30 into MPLS provider 2. Viptela establishes data tunnels on MPLS and Internet to other Viptela endpoints 3. MPLS RTRouter and Viptela head-ends peer using ebgp 4. Viptela has another link that will terminate Internet tunnels 5. Another ebgp peering session with core network to learn DC routes and advertise remote routes 5

6 Viptela Pilot Test Plan (High Level) 1. Overlay WAN Network Functionality ü Build Viptela WAN overlay across all transport (Internet + MPLS) ü Establish redundant paths and validate failovers (DC failovers + local circuit failovers) ü Establish full mesh for voice traffic and Hub-and-Spoke for rest 2. Local L3 Routing ü Peer with local L3 next-hops using static or dynamic routing (BGP) ü Determine which routes will need to be carried to other end-points 3. Routing, Performance & Control Policies ü Validate routing policies to establish dynamic routing topologies (Full Mesh, Hub-n-Spoke) ü Validate Policy based routing preferences and performance based metrics to influence next hop decisions on WAN 4. QoS/Configuration Parity + Other Data Policies ü Validate data policy components of Viptela solution (ACLs, QoS, NAT) ü Match existing ISR branch configuration 5. Secure Bring-Up + Segmentation ü Validate Segmentation of traffic into different VPNs (Application Level, Organization Level) ü ZTP for secure branch bring-up 6. VoIP Call Quality/Delay Testing ü Measure delay while performing failovers 6

7 Additional Hybrid WAN Benefits In addition to the management and performance benefits that a Hybrid-WAN solution yields, it also provides the following additional benefits: 1. Inherent Redundancy: If either MPLS or Broadband connection is lost, all traffic will re-route to the available connection 2. Dashboard Management: Baseline Templates, Monitoring, Configuration/Upgrade/Change management of all SD-WAN devices 3. Zero-Touch Provisioning 4. Transport Independence: Flexibility to provision and de-provision the physical transport without disrupting network service 5. Increased Network Capacity: The Hybrid-WAN solution will provide increased network capacity but not increase office circuit cost 7

8 New Circuit Standards 1. Hybrid MPLS w/ Viptela (Small/Medium Offices): Augmenting MPLS with Internet gives 4x-20x bandwidth boost at same cost Meets QoS requirements for Voice over IP Addresses bandwidth requirement for SaaS, Video and Internet applications 2. Ethernet MPLS Solution (Medium/Large Offices): Converting large office locations from 4xT1 to Ethernet circuits gives higher bandwidth at Lloyd will reduced cost For critical location, still aiming for dual MPLS plus maybe one broadband We were able to significantly increase bandwidth at most offices But, getting circuits is sometimes a challenge 8

9 Huge Difference in Application Resiliency During Circuit Outages (See 30-day chart) One site down for 2.5 mins in last 30 days because both links failed simultaneously All others sites faced ~2 hours circuit outage in last 30 days but no App downtime 9

10 Real World Example of Carrier Performances Viptela Analytics provides data (loss, latency and jitter) across all circuit providers Following is a snapshot of the various carriers in our network and their performance for a quarter 10

11 Conclusion: What did we learn? SD-WAN has met business goals of bandwidth and resiliency Network-wide visibility on circuit and applications is very useful Flexibility of deploying different circuit types at different locations on the same WAN Operational simple to deploy and manage But, Focus on performance and total bandwidth, not cost Upload speeds on broadband are usually low and comparable to MPLS Price delta of MPLS v Broadband may not be as big as expected Circuit challenges hard to get broadband everywhere Ethernet based circuits are not always readily available, but workarounds exist Operational Integration Challenges (SNMP/Syslog/API) These features need continuous development with technology partners Every vendor has their own way of deploying monitoring and its tough to just switch from SNMP one day to all APIs overnight 11

12 Recommended FutureWAN 17 Sessions u Analyst Keynote: Building the SD-WAN Business Case (Nemertes Research) u Network Engineer Roundtable on Deploying SD-WAN (Tech Field Day) u Enabling AWS and Azure Migration using SD-WAN u What To Ask Your Vendor on Enterprise SD-WAN Capabilities Access All Summit Sessions 12