Users Guide

224| BranchController Config for Controllers Dell Networking W-Series ArubaOS 6.5.x| User Guide
l mini-setup: In this mode, the branch controller:
n has its role set to branch when mini-setup is initiated
n obtains its IP address from DHCP
n is configured through the console with its country code and the IP address of the primary master
controller and (optionally) the secondary master controller IP.
n retrieves its branch config group from the primary master controller
l full-setup: In this mode, the branch controller:
n is configured with its role set to branch through the console
n is configured to obtain its IP address through manual configuration of a static IP, DHCP, or PPPoE
n is configured through the console with its country code and the IP address of the primary master
controller and (optionally) the secondary master controller IP
n retrieves its branch config group from the primary master controller
Automatically Provisioning a Branch Controller
When a factory-default branch controller boots, it starts the auto-provisioning process.
First it will obtain its IP address through DHCP by sending a DHCP discover on the default uplink port. The
default uplink port is configured as an access port in VLAN 4094.
To interrupt the auto provisioning process, enter the string mini-setup or full-setup at the initial setup dialog
prompt shown below.
Auto-provisioning is in progress. Choose one of the following options to override or debug...
'enable-debug' : Enable auto-provisioning debug logs
'disable-debug': Disable auto-provisioning debug logs
'mini-setup' : Stop auto-provisioning and start mini setup dialog for smart-branch role
'full-setup' : Stop auto-provisioning and start full setup dialog for any role
Enter Option (partial string is acceptable):_
DHCP Options
When the branch controller sends the DHCP discover message to obtain its IP address, it adds a DHCP option
60 b Vendor Class Identifier to that DHCP discover message, where DHCP Option 60 is set to “ArubaMC”.
If the DHCP Offer does have DHCP Option 60 = ArubaMC, the branch controller will accept the DHCP lease and
send a DHCP request. It will also look for DHCP Option 43 – Vendor Specific Information in the DHCP Lease. If
DHCP Option 43 is present in the Offer, the branch controller will parse it to learn the provisioning parameters.
The role is not explicitly specified in DHCP Option 43. However, the controller will set its Role to branch if the other
provisioning parameters are present in DHCP Option 43.
If the DHCP Offer does not have DHCP Option 60 = ArubaMC, the branch controller will still accept the DHCP
lease and send a DHCP request. However, once it is bound to the IP address, it will initiate the next mode of
auto-provisioning and query for a provisioning rule.
DHCP Server Provisioning
The branch controller adds ArubaMC as a DHCP option-60 vendor class identifier in its DHCP discovery
messages, so the DHCP offer from the server must include ArubaMC as a DHCP option-60 vendor class
identifier. The controller gets the master information and country code from the DHCP server, which is
configured with the master information corresponding to that identifier. The server may also send vendor-
specific information (VSI - option 43) in its response to the controller.
Before you deploy a branch controller using ZTP, configure the DHCP server with the following information:
l The option-60 vendor class identifier ArubaMC