Concept for zero-touch provisioning for distribution switch in CNaaS NMS. Target release cnaas-nms ZTP for CORE and DIST type devices is supported from NMS v1.2.

The first switch might always have to be configured manually, unless some other network element can be configured to forward DHCP requests.

...

New device is not directly connected so LLDP information is not seen, in this case peer hostnames list can be set as an empty list and all interfaces and BGP peers have to be configured manually? Also manual reconfig of peer devices might be needed at step 4f

Caveats:

It might not be able to fully ZTP devices that should go in the "evpn_peers" list (CORE devices), since it's probably not possible to populate "evpn_peers" list before the devices exist, and routing connectivity to the management loopback will not work until after the evpn_peers has been established. Solved by using all CORE type devices as evpn_peers if no peers are explicitly set?

Troubleshooting

If the subtask push_base_management fails (for example because a bad template) the neighbor devices might already have had their linknets reconfigured to fabric linknets. In this case the device that failed ZTP will not be reachable via DHCP IP nor MGMT IP until the device is deleted from the database and the neighbor devices are re-synchronized so the ZTP device can reaquire a DHCP lease.