ZTP with Aruba Central

Aruba Central does not require any configuration of local DHCP server or other network components but requires a switch with Internet access.

Users with access to Aruba Central cloud portal must provision their switches and assign licenses accordingly. Once complete, Aruba Central will automatically program the Activate portal with the required switch details and the group to which the switch must check in.

NOTE:

  • Aruba Central does not support IPv6 connectivity.

  • Aruba Central is not applicable for connection through OOBM interface.

The following diagram illustrates the working of Aruba Central ZTP:

The workflow is as follows:

  1. The switches being provisioned in branches boot and connect to the Activate on the cloud.

  2. Based on administrator’s provisioning (such as folder, rule), the device is placed in the appropriate folder before being redirected to the Aruba Central.

  3. The switches check-in with Central and the server pushes the configuration to the switches based on the group, switch model, and branch location.

For more information on Aruba Central configuration, refer to the Aruba Central Configuration Guide.

After the switch successfully checks-in with Aruba Central, the following management interfaces on the switch are disabled:

  • WebUI

  • REST

  • SNMP

  • TR-69

  • Menu

There is a restriction on executing the following commands over CLI:

  • boot

  • recopy

  • erase

  • reload

  • startup-default

  • upgrade-software

  • setup

  • delete

  • reboot

  • restore

  • menu

  • write memory

  • amp-server