Users Guide

Provisioning a controller includes completing the following:
l setting the role
l setting the country code
l configuring the local configuration
The local configuration is the configuration that is specific to a controller. That is, not the global configuration shared
by a network of controllers. This includes, but is not limited to, IP addresses and VLANs.
Once the controller is provisioned, it is ready to obtain its global configuration either by:
l The administrator entering the global configuration directly from the WebUI or CLI of a master controller
l The controller retrieving the global configuration from a master controller
Previously the steps of setting the role, setting the country code, and configuring the local configuration could
only be performed manually by an administrator. With ZTP, these steps can be automatically completed.
The local configuration that a branch controller retrieves through ZTP is called as branch config group.
A controller that is deployed using ZTP is called as branch controller.
Only the W-7000 Series controllers may be deployed as branch controllers.
Before you Begin
Before you deploy a W-7000 Seriesbranch controller, use the smart config feature on the master controller to
a create branch config group. The master controller can push a branch config group configuration to a branch
controller when the branch becomes active on the network. The smart config feature is enabled by default. For
more information on branch config group settings, refer to
Using Smart Config to create a Branch Config
Group on page 225.
The parameters of role, country code, and IP address of the master controller are collectively known as the
provisioning parameters.
Provisioning Modes for Branch Deployments
The administrator has the choice of several provisioning modes that alter how the branch controller is supplied
with its own IP address, role, country code, and branch config group.
During the various provisioning modes, the branch controller is supplied with the IP address of the primary
master controller, or, for deployments requiring Layer-3 redundancy, the IP addresses of the primary and
backup master controllers. Once the branch controller learns the IP address of the primary master controller,
the branch controller contacts the master controller and retrieves its branch config group.
Provisioning a controller means defining the following values for that device:
l the role of the controller (master or branch)
l the country code
l local configuration settings
ArubaOS supports the following provisioning modes for branch controllers:
l auto: In this mode, branch controller:
n obtains its IPaddress from DHCP
n obtains its role, country code, and the IP addresses of the primary controller and any defined secondary
controller from DHCP Options
n retrieves its branch config group from the primary master controller
Dell Networking W-Series ArubaOS 6.5.x | User Guide BranchController Config for Controllers | 223