You are here: Home > Configuring ArubaOS Features > Managed Devices > Provisioning a Managed Node

Using ZTP to Provision a Managed Device

When a factory-default controller boots, it starts the auto-provisioning process. The following sections describe the provisioning workflow, and the process to prepare your network for ZTPZero Touch Provisioning. ZTP is a device provisioning mechanism that allows automatic and quick provisioning of devices with a minimal or at times no manual intervention. for a managed device.

When a managed device establishes an HTTPSHypertext Transfer Protocol Secure. HTTPS is a variant of the HTTP that adds a layer of security on the data in transit through a secure socket layer or transport layer security protocol connection. connection to the Activate server and requests provisioning information, the Activate server authenticates the managed device and provides that device with provisioning information, including the IP address of its Mobility Master and secondary Mobility Master, and its country code.

If the managed device is unsuccessful in retrieving the provisioning parameters from Activate, it will retry in 30 seconds. The managed device will keep trying to retrieve the provisioning parameters from Activate until it is successful, or the administrator initiates Mini-Setup or Full-Setup provisioning.

Before you can use Activate to associate a managed device to Mobility Master, you must configure Activate with additional device settings for each managed device and Mobility Master, create a folder for those local devices, then assign a provisioning rule to the folder that associates the managed devices to a specified master and configuration node. Use the following procedures to configure device details for the Mobility Master and managed devices, create folders, and define the provisioning rule.

/*]]>*/