ZTP with Aruba Central

Aruba Central does not require any options to be configured in the DHCP server, but requires a DHCP server in the network to provide IP address, default gateway, DNS parameters, and an internet connectivity to reach Central.

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.

  • 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 Aruba Central.

  3. The switches check-in with Aruba 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 management interfaces on the switch are read-only or disabled.

The following management interfaces on the switch are read-only:

  • Web UI

  • SNMP

  • REST


These interfaces are opened for READ operation after the switch is connected to Aruba Central. For the 2920 switches, only SNMP is read-only, REST and Web UI are disabled.

The following management interfaces on the switch are disabled:

  • 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