Users Guide

226| BranchController Config for Controllers Dell Networking W-Series ArubaOS 6.5.x| User Guide
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.
Starting from ArubaOS 6.5, the ZTP feature is enhanced to support 16 VLANs per branch controller as against
just four in the earlier versions of ArubaOS. Except this VLAN enhancement, all the other configurations for the
ZTP feature remain the same as in previous ArubaOS versions.
The Bulk Edit template (in Excel sheet) on the branch controller allows you to specify the static IP assignment
for individual branch controller devices. The static IP configuration is maintained in this Bulk Edit CSV file, with
each line in the file representing the settings for a specific branch controller device. To support this
enhancement, the Bulk Edit Excel sheet (.CSV format) is now expanded to allow for addition of up to 16 VLANs
for each branch controller.
The DHCP pools for the VLANs will have settings for the following parameters: pool name, domain name,
domain name server, VLAN ID, IP address, mask, and the IP address exclude list.
To create a new branch config group:
1. Navigate to Configuration > Branch > Smart Config and select the Management tab.
2. Click the New button under the branch config group list. You are prompted to enter a name for the new
branch config group profile.
3. Click OK.
4. Next, click the Model drop-down list and select the model type of your branch controllers. Each profile can
support a single controllermodel .
5. Click the IP Address Management drop-down list and select the Static or Dynamic option.
6. If you select Dynamic, each branch office controller will get an IP address using DHCP.
7. If you select Static, the WebUI gives you the option to select export and download the static IP address
template export-RemoteNode.csv, or select import and upload a completed static IP address .csv file.
8. Click Apply to save your settings.
The export-RemoteNode.csv template defines the following settings for each branch controller in the branch
config group. Complete the template by adding information for up to 16 IP address pools for each branch
controller.