Using ZTP with DHCP to Provision a Managed Device

The auto-provisioning process begins when a factory-default controller boots up. The following section describes the provisioning workflow, and also details the process to prepare your network for ZTP Zero 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 DHCP Dynamic 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. .

In the absence of an Activate server, DHCP Dynamic 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.  servers aid the managed devices to get information about the Mobility Conductor. The information required for provisioning managed devices is obtained from a DHCPv4 or DHCPv6 server.

Option 43 of DHCPv4 contains information about the Mobility Conductor to the managed devices. Similarly, for DHCPv6 Option 16 provides vendor related information and Option 17 provides information such as conductor IPv6 address, VPNC information and so on.

Following are the list of supported topologies:

  • VMM with VPNC
  • HMM with VPNC
  • HMM without VPNC

This feature also supports L2 Mobility Conductor Redundancy scenarios, where the managed device gets information about the primary Mobility Conductor and standby Mobility Conductor.

In VPNC scenarios, the managed devices get information related to primary Mobility Conductor, standby Mobility Conductor, Primary VPNC, and standby VPNC.

Option 43 of DHCPv4 contains the following information required to provision a managed device:

  • conductorip, country-code, conductor-mac1 (No L2 redundant Conductor)
  • conductorip, country-code, conductor-mac1, conductor-mac2 (L2 Redundant Conductor)
  • conductorip, country-code, vpnc ip, vpnc-mac1 (No L2 , Redundant VPNC)
  • conductorip, country-code, vpnc ip, vpnc-mac1, vpnc-mac2 (L2 Redundant VPNC)
  • Enter the details using one of the formats given below:

    mip=10.9.186.001, mm1=aa:aa:aa:aa:aa:aa, cc=US

    mip = 10.9.195.111 , cc= US, vm2= 00:0C:20:C9:10:34 , vm1= 00:0C:29:B1:05:56A, vip=10.45.12.111

For DHCPv6, Option 16 contains Vendor Class Identifier (VCI), which is a text string that uniquely identifies a type of vendor device and Option 17 contains the following information required to provision a managed device:

Enter the details using the format given below:

mip=10.9.199.120,vip=10.9.199.100,vip6=2002:1:1:101::20,vm1=00:1a:1e:01:10:b0,mip6=2002:1:1:101::361,cc=US,mm1=00:1a:1e:01:7d:c0

Examples

Following is an example of a DHCPv4 configuration used for ISC DHCP Dynamic 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 software:

subnet 10.3.91.0 netmask 255.255.255.0 {

option vendor-class-identifier "ArubaMC";

option vendor-encapsulated-options "mip = 10.9.196.160 , cc= US, vm2= 00:0C:29:B9:20:64 , vm1= 00:0C:29:B9:20:5A, vip=10.45.34.187";

option domain-name-servers 10.1.10.10;

option routers 10.3.91.254;

range 10.3.91.2 10.3.91.253;

authoritative;

}

Following is an example of a DHCPv6 configuration used for ISC DHCP Dynamic 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 software:

subnet6 2500:abcd:1234:dead::/64 {

default-lease-time 43200;

max-lease-time 43200;

option vendor-class-identifier "ArubaMC";

option dhcp6.vendor-opts “mip=10.9.199.120,vip=10.9.199.100,vip6=2002:1:1:101::20,vm1=00:1a:1e:01:10:b0,mip6=2002:1:1:101::361,cc=US,mm1=00:1a:1e:01:7d:c0”

option dhcp6.name-servers 2111::1;