You are here: Home > Configuring ArubaOS Features > Managed Devices > Using ZTP with DHCP to Provision a Managed Node

Using ZTP with DHCP 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. using DHCPDynamic Host Configuration Protocol. A network protocol that enables a server to automatically assign an IP address to an IP-enabled device from a defined range of numbers configured for a given network.  for a managed device.

The managed device can get the information required for provisioning from a DHCPDynamic Host Configuration Protocol. A network protocol that enables a server to automatically assign an IP address to an IP-enabled device from a defined range of numbers configured for a given network.  server instead of Activate. Using DHCPDynamic Host Configuration Protocol. A network protocol that enables a server to automatically assign an IP address to an IP-enabled device from a defined range of numbers configured for a given network.  helps the 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. controllers get master information when the users are unable to use Activate. Option 43 of DHCPDynamic Host Configuration Protocol. A network protocol that enables a server to automatically assign an IP address to an IP-enabled device from a defined range of numbers configured for a given network.  can be used for broadcasting the master information to the managed devices.

This feature supports the following topologies:

VMM with VPNC

HMM with VPNC

HMM without VPNC

 

VPNC must be a hardware controller and not a virtual machine.

This feature also supports L2 and L3 Mobility Master redundancy scenarios, where the managed device can get primary Mobility Master and standby Mobility Master (L2 or L3 standby master) information.

In VPNC scenarios, the managed devices can get primary Mobility Master information, standby Mobility Master, Primary VPNC and standby VPNC information.

Option 43 contains the following information to help provision a managed device:

Master IP

VPNC IP

Primary Master MACMedia Access Control. A MAC address is a unique identifier assigned to network interfaces for communications on a network.

Redundant Master MACMedia Access Control. A MAC address is a unique identifier assigned to network interfaces for communications on a network.

Primary VPNC MACMedia Access Control. A MAC address is a unique identifier assigned to network interfaces for communications on a network.

Redundant VPNC MACMedia Access Control. A MAC address is a unique identifier assigned to network interfaces for communications on a network.

Country Code

Option 43 contains the following information:

masterip, country-code, master-mac1 (No L2 redundant Master)

masterip, country-code, master-mac1, master-mac2 (L2 Redundant Master)

masterip, country-code, vpnc ip, vpnc-mac1 (No L2 Redundant VPNC)

masterip, country-code, vpnc ip, vpnc-mac1, vpnc-mac2 (L2 Redundant VPNC)

/*]]>*/