Users Guide
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 to obtain its IP address, it adds DHCP option 60 – Vendor
Class Identifier to the DHCP discover. 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 - 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
l Option-43 Vendor Specific Information (VSI) with the master IP address, or the master IP and country code,
of the branch controller . This VSI must be in one of the following formats, where <master-ip-address)
contains the IP address of the master controller in dotted-decimal notation (a.b.c.d) format, and the
country code contains a valid ISO 3166 country codes,such as, US, AU, or IN
n <Master-IP-address>,
n <Master-ip-address>,<Country-code>
Using Smart Config to create a Branch Config Group
Before you begin to configure a branch config group for individual branch controllers, you must select a master
controller to serve as the master for a group of branch controllers on a network. A controller can act either as a
master or a branch controller, but not both.
Any change to an active branch controller’s DHCP pool configuration causes the branch controller to reboot.
Only W-7200 Series controllers can server as a master controller for a group of branch controllers on a network.
Dell Networking W-Series ArubaOS 6.4.x | User Guide BranchController Config for Controllers | 298