olly - Fotolia
If you're looking to upgrade your legacy WAN with software-defined WAN technology, you should consider several...
things during network infrastructure planning to help with the migration process.
The first step in network infrastructure planning for SD-WAN is to evaluate which WAN connectivity options are available at each local and remote location. Whether the connectivity is dark fiber, MPLS, Metro Ethernet, broadband, wireless or satellite, it must be considered in terms of cost, as well as the throughput and latency requirements of each remote office.
Your goal should be to meet each location's current minimum data requirements by using two or more intelligently managed WAN links. That will help keep costs down, which will help speed up return on investment. That said, network infrastructure planning should also include research into rapid scalability steps, such as increasing throughput on existing links or adding additional WAN links into the SD-WAN mix.
Decide how to implement the SD-WAN technology
Next, you must consider how to best implement the SD-WAN intelligence at both the corporate or headquarters side and the remote location side of the WAN. The lowest-cost option is to use existing WAN hardware that can be upgraded to support software-defined functionality. If that's not possible, you'll need to determine if hardware-based appliances or virtual server software is best for each location.
For smaller remote sites that likely don't have virtualized servers, hardware-based appliances are best. If your corporate office or remote site already has virtual machines hosted locally on the LAN, however, using a virtual SD-WAN appliance would lower costs and be one less hardware device that IT needs to support.
Verify the best routing protocol
Lastly, during network infrastructure planning for an SD-WAN upgrade, you must consider which routing protocol is best for your business. Your corporate office -- and possibly WAN -- is likely already running a dynamic routing protocol. For consistency purposes, it's usually best to use the same routing protocol for the SD-WAN as is being used on the corporate LAN.
Because some dynamic routing protocols are proprietary in nature, take care to verify the SD-WAN option you choose is compatible. If not, you'll have to redistribute one routing protocol into another, which can add unnecessary complexity.
Dig Deeper on Software-defined WAN (SD-WAN)
Related Q&A from Andrew Froehlich
While VLANs are a type of subnet, they have their own unique capabilities and characteristics that differentiate them from subnets. However, the OSI ... Continue Reading
Broadband and Wi-Fi are common technical terms often used interchangeably -- although they shouldn't be. Both provide connectivity, but they do so in... Continue Reading
Migrating to UCaaS doesn't always mean an organization can keep its PSTN or SIP carrier. But some providers are taking a 'bring you own carrier' ... Continue Reading