Users Guide

299 | BranchController Config for Controllers Dell Networking W-Series ArubaOS 6.4.x| User Guide
Create and configure a branch config group on a master controller by navigating to the Configuration >
BRANCH > Smart Config section of the master controller WebUI. The Smart Config page contains eight tabs
for configuring the branch config group settings.
The BRANCH >Smart Config section of the master controller WebUI is available on the W-7200 Series controllers
only.
The configuration parameter on each of these tabs are described in the following pages:
l Config Group Management Settings on page 299
l System Configuration on page 305
l Networking Configuration on page 307
l Routing Configuration on page 309
l VPN Configuration on page 314
l WAN Configuration on page 317
l Branch ConfigGroup Summary on page 319
l Whitelist Configuration on page 320
Config Group Management Settings
Use this tab to create a new branch config group, select the model of branch controller to which this config
group will be applied, and choose either the Static or Dynamic IP address management option for your
deployment.
Address Pools
Each branch controller must have a pool of addresses it can dynamically assign to APs or users on each of its
VLANs, and a separate IP address that branch controller uses to create a GRE tunnel to the master controller.
Branch controller VLAN pools and the tunnel pool are defined on the master controller. Branch controller
address pools are pushed out to each branch controller when it comes up on the network. If a branch
controller is removed from the master, the IP addresses allocated to that branch controller can be reused and
reassigned to a new branch controller .
A master controller must have a separate VLAN pool defined for each VLAN used by its branch controller. A
VLAN pool allocates a static, continuous block of multiple IP addresses to each branch controller. The branch
controller acts as a DNS proxy server and dynamically assign IP addresses from its allocated pool to each AP or
client on the VLAN.
The tunnel pool on a branch controller defines a range of IP addresses that the branch controller uses to create
a GRE tunnel within the IPsec tunnel back to the master controller. Unlike VLAN pools, which allocates multiple
addresses to each branch controller VLAN, the tunnel DHCP pool assigns a single tunnel IP address to each
branch controller.
Static vs Dynamic IPManagement
If you choose the dynamic IP management option, you must define one or more IP address pools with a range
of sharable addresses. The master controller then divides each IP address pool into unique subnets that can
support the required number of clients per branch, and assigns one of these subnet to each branch controller.
If a branch deployment has existing IP addressing that needs to be preserved (for example, the printers at a
branch office have static IP addresses), then the branch config group should use static IP addressing. When
you create a branch config group that uses static IP addressing, you must export the ArubaOS static IP
addressing template from the master controller, define the IP settings for the devices that need a static IP
address within that template, then import the template file back into a branch config group.