Internet
WAN Router
WAN Router
Switch being
provisioned
Switch being
provisioned
DHCP
Server
Router/
Firewall
AirWave
Server
Corporate Network
Corporate
HQ
Branch 2
Branch 1
DHCP
Server
In the preceding illustration, the workflow is as follows:
1.
The switches being provisioned in the branches are booted obtaining the IP address from the DHCP server.
2.
The DHCP servers provide information about the AirWave server in the Corporate Head Quarters.
3.
The switches connect to the AirWave server through the Corporate Network (MPLS VPN or equivalent).
4.
The AirWave server pushes the configuration to the switches based on the AirWave folder, switch model, and
branch location.
5.
An optional IPsec tunnel can be established between the branches and the Corporate HQ to secure the
management traffic. For more information, refer the
Activate-based ZTP with AirWave
.
NOTE:
If IPsec tunnel is required for AirWave, the switch requires Aruba Mobility Controller IP
address, which is provided through ZTP with DHCP Option 138 (CAPWAP).
DHCP server configuration for DHCP based ZTP
You can configure the DHCP server for AirWave using Windows DHCP server, Linux DHCP server, and ArubaOS
DHCP server.
Preferred Methods
The following methods are preferred to configure DHCP server for AirWave:
Configure AirWave details in Windows DHCP server for IPv4
NOTE:
AirWave provisioning using IPv6 on Windows based DHCP server is not supported.
To configure the AirWave details in Windows DHCP server for IPv4, do the following steps:
Procedure
1.
From the
Start
menu, select
Server Manager
.
Chapter 10 Zero Touch Provisioning with AirWave and Central
295