--- title: "Adaptive bandwidth management" canonical: "https://docs.aryaka.com/space/KNOW/1284702276/Adaptive%20bandwidth%20management" format: markdown --- Adaptive Bandwidth Management is the ability for an ANAP deployed in edge routed mode or inline routed mode to reserve bandwidth for, or limit bandwidth to, a participating network that shares the site's internet links. A site's ANAP that is deployed using edge routed mode or inline routed mode can use one or both of its ISPs for the following purposes: Connect to a remote site using an Aryaka's POP (VPN Path Aryaka). Connect to a remote site using an IPSec tunnel over the internet to a remote ANAP(VPN Path Internet). Connect to an IaaS vendor like Azure Virtual WAN using IPSec tunnels (Cloud Transport Network). Connect to a cloud security vendor like Zscaler or Palo Alto Networks Prisma to route internet traffic (Cloud Security Network). Access internet resources directly (Direct Internet). The following graphic shows Site A connecting to various networks using these connection types: The following MyAryaka SD-WAN > Monitor graphic shows how WAN traffic is distributed across various networks: A site's WAN bandwidth is distributed among these networks using Adaptive Bandwidth Management. The following networks participate in Adaptive Bandwidth Management: VPN Path Aryaka VPN Path Internet Cloud Transport Network Direct Internet Each network is allocated a reserve and a limit. The reserve guarantees a configured throughput for the network and the limit ensures that a network never exceeds a configured throughput. Each network is also assigned a network priority, which determines how the networks are allocated bandwidth. For example, if the network with priority 1 is currently not using the ISP link, then the network with priority 2 can exceed its reserved throughput and use the available bandwidth provided that all other reserves are honored and the limit of the network is not exceeded.  The network priority mentioned in this document is different from routing priorities. The network that traffic uses is decided based on routing priorities and the bandwidth allocated to a network is decided based on bandwidth management priority . VPN Path Aryaka Bandwidth Management VPN Path Aryaka Bandwidth, also known as Subscribed Bandwidth (SBW) is the bandwidth commit of a site that the customer contracted from Aryaka. This is the guaranteed bandwidth a site can achieve when connecting to a remote site or SD-WAN resource using Aryaka's POPs. Additionally, customers can purchase the Bursting option. This enables a site's bandwidth to achieve up to 1.5 times the site's Subscribed Bandwidth. This value is known as Total Site Bandwidth (TSB). When the customer has not purchased Bursting, the Total Site Bandwidth is equal to Subscribed Bandwidth. Adaptive Bandwidth Management guarantees that VPN Path Aryaka network traffic has reserved bandwidth of SBW and that VPN Path Aryaka Network traffic is limited to the TSB. VPN Path Aryaka may be established from a site using one or two tunnels, and using one or two ISPs at a site. The two tunnel/two ISP approach is to achieve redundancy . Redundancy allows the tunnel or ISP to fail over to the second option in the case of failure to the first. In addition to redundancy, dual tunnels can be configured to perform load balancing or to replicate select traffic. They can also be configured to have a specific preference for certain types of traffic. Some of these configuration options require VPN Path Aryaka to utilize both ISPs at a site simultaneously. The following graphic shows a two tunnel/two ISP VPN Path Aryaka configuration: Other Networks' Bandwidth Management VPN Path Aryaka has the highest priority of all networks that use a site's WAN capacity. Other participating networks can be configured to have relative priority to each other as per the customer's requirements. The remaining bandwidth after VPN Path Aryaka has utilized what it needs is what is available to be shared by the participating networks. This bandwidth can now be divided and shared by the other networks. The configuration is performed per site and each network can be configured as follows: Reserved bandwidth for the network on each internet interface. Maximum bandwidth available for the network on each internet interface. This allows the networks to have different reserve bandwidth and limit configuration in either direction (inbound and outbound). The following sections describe each network's configuration options for using a site's WAN bandwidth. VPN Path Internet VPN Path Internet uses tunnels to connect to remote sites that have ANAPs. These tunnels are configured to take one of two possible paths between the two sites. These two sites can both have two ISPs. The ANAP's Internet Link Assure engine selects the traffic's path. This engine can be configured to use a specified preferred path between ANAPs or to perform load balancing on the two paths. This requires the ability for the network to use both ISPs when sending traffic to a remote site. The traffic on each ISP can be limited for use by this network. Similarly, a specific amount of bandwidth may be reserved for this network's use on each ISP. The following graphic shows a two tunnel/two ISP VPN Path Internet configuration: Cloud Transport Network An ANAP can connect to several IaaS hubs or gateways using redundant tunnels. Only one of the two tunnels to a hub or gateway is active at any time. Different hubs can have primary tunnels that use different internet-facing interfaces. For example, an Azure Virtual WAN cloud transport network can use both of a site's ISPs at any point of time to connect to several hubs or gateways. Like with VPN Path Internet, the traffic on each ISP can be limited for use by this network. Similarly, a specific amount of bandwidth can be reserved for this network's use on each ISP. The following graphic shows a two tunnel per hub Cloud Transport Network configuration: Direct Internet The ANAP routes internet traffic over the interface selected by the Internet Traffic Controller . This controller pings a known public IP address from each internet-facing interface to determine the healthiest ISP at that time. This internet-facing interface is used for default internet routing. Additionally, the site can be configured to implement Internet Overflow . Internet Overflow is a subset of the Internet Traffic Controller service . It enables the ANAP to route traffic over the second interface when the preferred internet interface has reached its throughput limit. The traffic on each ISP can be limited for use by this Direct Internet network. Similarly, a specific amount of bandwidth can be reserved for this network's use on each ISP. When the primary or preferred internet-facing interface's throughput reaches the limit configured for the interface and network, the traffic overflows over to the next preferred interface. The overflow is achieved by routing new flows to the new interface. Existing flows remain in the interface that was selected when the flow was established. The following graphic shows a two interface Direct Internet network configuration: Network Priority Management A site's networks can be reordered to adjust their priorities so that unreserved available bandwidth can be allocated to the networks in a specific order. All of the networks types can have reserves allocated to them. This total allocation must be equal to or less than the site's ISPs link size. Unallocated bandwidth is distributed among the configured networks in the order specified by the network priority, such that the bandwidth never exceeds the limit configured for the network. The following graphic shows the network and bandwidth management configuration of Site A's primary ISP link: Note the following in the graphic: VPN Path Aryaka always has the highest priority. Its bandwidth reserve and limit are determined by the subscribed bandwidth and bursting configuration of the site. The other relevant networks can have user-defined priorities, reserves, and limits. The remaining bandwidth in the example (820 Mbps) is what is left over from the ISP link size after the reserves of the individual networks are honored. This bandwidth can now be distributed among the participating networks in the order of their priorities. Contact Aryaka Customer Support   to discuss your bandwidth management needs. In this topic Related topics Internet Traffic Controller Configure site information