Configure a DHCP Relay for ZTP
To use ZTP for onboarding devices that are present on a subnet that is different from the subnet in which Paragon Automation is installed, you must configure a DHCP relay, as shown in Figure 1.
The DHCP relay can be an MX Series device or a Linux-based (CentOS) Virtual Machine (VM). For information about using an MX Series device as a DHCP relay, see DHCP Relay Agent.
To configure a DHCP relay in a CentOS-based VM:
-
Log in to the VM as a root user.
-
Install the DHCP relay package on the VM.
root@host# yum install dhcp
Note:The DHCP relay package is usually available by default in a CentOS-based VM. However, if the package is not available, the
yum install dhcpcommand fetches the package and installs it. -
Execute the following command to run the DHCP relay service.
root@host# dhcrelay -4 -d -i <interface-name> <dhcp-service-external-ip>
where:
interface-name is the interface on the VM that is connected to the device to be onboarded to Paragon Automation.
dhcp-service-external-ip is the Paragon Insights services virtual IP (VIP) address that was provided during the installation.
You can also obtain the Paragon Insights services VIP address by running the following command on the Paragon Automation primary node:
root@device# kubectl get svc -n ems | grep -i ztpservicedhcp NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE ztpservicedhcp LoadBalancer 10.102.3.100 192.168.15.155 67:30241/UDP 37h
The IP address listed under EXTERNAL-IP is the Paragon Insights services VIP address.
You can now use the VM as a DHCP relay to connect Paragon Automation and the devices to be onboarded to Paragon Automation.