Software-defined branch (SD-Branch) is a technology shift toward solutions that are agile, open, and cloud-integrated. SD-Branch includes SD-WAN components that deliver a secure, service-provider-independent network with enterprise-level performance over disparate wide-area network (WAN) technologies. However, although SD-WAN solves a real IT problem, it addresses only part of the issue organizations face when dealing with distributed locations.
Organizations often roll out and operate distributed, heterogeneous networks with centralized teams. These distributed networks offer many services in addition to WAN connectivity. Branch networks require wired and wireless LANs, security and policy enforcement, and, of course, WAN interconnects. SD-Branch extends the concepts beyond SD-WAN to all elements in the branch, delivering a full-stack solution that includes SD-LAN and security that address all network connectivity needs.
When formulating the strategy for an SD-Branch rollout, Aruba recommends:
Purchase as much WAN bandwidth as possible to alleviate potential bottlenecks during the busiest times of the day.
Increase Internet bandwidth, instead of buying additional private bandwidth.
Use cloud-based tools to simplify the configuration, operation, and management of the WAN.
This deployment guide covers the Aruba SD-Branch in the Edge Services Platform (ESP) architecture. It contains an explanation of the requirements that shaped the design and the benefits it can provide to your organization. The guide describes a single unified infrastructure that integrates access points (APs), switches, gateways, and network management with access-control and traffic-control policies. Refer to volume one of this VSG for design guidance:
This guide assumes the reader has an equivalent knowledge of an Aruba Certified Mobility Associate or Aruba Certified Switching Associate.
The overall goal is to create a simple, scalable design that is easy to replicate across all sites in your network. The solution components are limited to a specific set of products to help with operations and maintenance. The key features addressed by Aruba SD-Branch include:
Simplicity with Zero Touch Provisioning (ZTP): SD-Branch devices can be factory-shipped directly to a remote site. By automatically matching orders to an Aruba customer account, the mobile Installer app is available for third-party systems integrators to quickly install equipment. Standardized group- and device-level configurations for APs, switches, and gateways enable fast network deploymnet.
Unified policy management: For Aruba and third-party network infrastructure, Aruba ClearPass delivers a common policy framework for multivendor wired and wireless networks. This software-defined approach makes it easy for the network administrator to distribute changes quickly based on corporate risk and compliance requirements. ClearPass Device Insight (CPDI) adds AI-powered device profiling to help automate discovery of the latest mobile and IoT endpoints.
Predictive analytics and assurance: Aruba Central’s artificial intelligence (AI), machine learning (ML), and automation capabilities identify issues and notify IT of problems with recommended changes. When shifting to a cloud-hosted model, data can be collected and crowdsourced from Aruba’s installed base to take advantage of Aruba’s extensive data science expertise.
Secure WAN connectivity: Enable SD-WAN technology to support the use of the Internet to replace or augment private WAN services. Elements of the solution include: path quality monitoring (PQM) to track the available paths, stateful firewall with application fingerprinting to identify traffic flows, dynamic path selection (DPS) to use the optimal path, and centralized routing to free branch gateways (BGWs) from participating in the routing decisions. End-user identity information refines the selection of available WAN paths.
LAN automation with dynamic segmentation: Most branch networks are needlessly complex because designs are based on a proliferation of VLANs, complex IP addressing schemes, access control lists (ACLs), and architectures tailored to the needs of automation software. The SD-Branch architecture flattens the branch into fewer subnets or even a single subnet, eliminating the dependence on static IP addressing schemes and hardwired ACLs across multiple devices. This is achieved by consolidating all policy enforcement into a single device in the branch.
Use this guide to design new networks or to optimize and upgrade existing networks. It is not intended as an exhaustive discussion of all options; it presents commonly recommended designs, features, and hardware.
This guide is written for IT professionals who need to design an Aruba SD-Branch network. These IT professionals serve in a variety of roles:
Systems engineers who need a standard set of procedures for implementing solutions
Project managers who create statements of work for Aruba implementations
Aruba partners who sell technology or create implementation documentation.
Branch networks are changing rapidly. The most pressing challenges include an increasing number of mobile and IoT devices, growing bandwidth requirements of the business, and modern users who expect connectivity for work and personal use from anywhere at any time. The teams that run these distributed networks are often shrinking while demands increase.
Organizations expect new network rollouts within shorter timeframes, and IT organizations are asked to improve service levels, reduce costs, and shift spending from capital expense to operating expense.
This guide discusses the following use cases:
Secure WAN communications using IPsec tunnels over an independent transport
ZTP for all networking components in the branch
Switch stacking for simplified management, high availability, and scalability
Link aggregation for high bandwidth, redundancy, and resiliency between switches and gateways
Wireless as the primary access method for branch employees
Wireless and wired guest access for customers, partners, and vendors
Consistent security for wired and wireless devices based on roles.
Table of contents
- Network Overview
- Preparing to Deploy
- Deploying VPNC
- Configuring Branch Gateway
- Configuring Branch Switch
- Configuring Wireless Access
- Verifying Hub Spoke Topology
- Validated Hardware