11 steps to network transformation with SD-WAN

Organizations are increasingly using the Internet alongside or instead of private MPLS access technologies to access cloud-based services and reduce connectivity costs. SD-WAN provides a way to gain control, visibility and the flexibility to quickly bring connectivity online in new locations. But what steps do you need to take to define your network transformation strategy and ensure it meets your digital business objectives?

1. Consult the right stakeholders

It is very important to consult the right internal stakeholders at the start of the network transformation to ensure that your strategy supports the overall digital business objectives of the organization. This means understanding the expectations and needs of the CEO and business application owners. The concerns of end users, network, IT and security management teams also need to be considered. Only when all stakeholders are on board and rowing in the same direction can you successfully implement your strategy.

2. Define your SD-WAN transformation goals

According to recent industry surveys, the most important reasons for companies to introduce SD-WAN are as follows:

• Ensuring 24/7 availability and business continuity of network and applications
• Enforcement of security policies for applications and users
• Achieving outstanding application and WAN performance
• Greater flexibility, especially in the provision of connectivity
• Greater flexibility when adapting security controls

It is important that you are clear from the outset about the problems you want to solve and the business goals you want to achieve.

3. Define the scope of your SD-WAN solution

The next step is to define the scope of your SD-WAN solution. After the network transformation, most organizations want to be able to:

• Create and automate the setup of site-to-site VPNs that connect branch offices to the cloud or the company’s data center
• Use cost-effective broadband access connections
• Enable dynamic path selection to balance traffic loads across the various access technologies
• Access a self-care portal

4. Decide on delivery model and provider

You need to be able to rely on the providers on your shortlist to deliver robust, business-grade services and be able to meet end-to-end service level agreements (SLAs) to securely execute your network transformation.

SD-WAN deployment models range from self-operated, where the organization procures and deploys the solution and manages ISPs directly, to fully managed services with various forms of co-management in between. The decision depends on whether the organization has the staff and expertise to operate in-house.

5. Define your network topology

You must decide whether each function should be provided on a universal CPE (uCPE) on site. Alternatively, functions can run on a virtualized CPE, in the corporate data center or in the data centers of communication service providers (cloud SD-WAN). For example, a company may choose to scan all its internet traffic in the cloud, avoiding the need for an on-site device to slow down employee browsing.

6. Define your access types

SD-WAN is inherently access agnostic and supports any type of local access technology (copper, fiber, cable coaxial, wireless and even satellite). Using existing connections can make sense, especially in some exotic regions of the world, if you are happy with the service provided and don’t want to switch.

7. Evaluate your application landscape and QoS prioritization

It makes sense to use tools to monitor the applications before the network transformation. This will allow you to determine which applications are consuming which bandwidth and what quality of service (QoS) issues exist. At this stage, it is also worth identifying the most business-critical applications that need to be prioritized in your new SD-WAN network.

8. Define your location profiles

The company must check each location to determine the number of employees, user profiles and applications used. Investigate the bandwidth requirements of specific locations, such as production sites.

9. Security requirements

From the outset, the network and security teams need to work together to consider the security policies and future requirements of the business. The security elements of an SD-WAN service can drastically change the design of your entire network.

10. Requirements for virtual network functions

Your service provider should be able to support a wide range of virtual network functions (VNFs). This allows you to remotely set up and manage communication services such as VPNs, WAN optimization, VoIP and next-generation firewalls.

11. Requirements for service management

There is little doubt that organizations increasingly need to be able to manage SD-WAN functions and policies, as well as other virtualized network functions for security and acceleration. Your SD-WAN management console must be easy to use and provide a sufficient level of monitoring and visibility to provide a means of control. The best portals have an intuitive graphical user interface (GUI) that allows you, or your managed service provider, to configure the devices in your branch offices and set policies. The portal should also produce highly visual, easy-to-understand reports.