...
After a switch is powered on, the switch sends DHCP Discover to get an IP address, and the DHCP server provides the switch with an IP address.
The switch sends a DHCP request to the DHCP server, and the DHCP server sends a DHCP response including the TFTP server address.
The switch sends a TFTP request to the TFTP server to get the shell script, and the TFTP server sends a TFTP response with the shell script.
The switch executes the shell script to complete the ZTP deployment, including registering with the AmpCon-DC server, installing a PicOS license on the switch, updating switch configurations, and rebooting the switch.
...
The AmpCon-DC server includes a component called the Configuration Manager, which is used to create a standard configuration to configure switches. All configurations are tied to specific switches by the switch serial number (or Service Tag) and are stored in a the AmpCon-DC database.
After you use the AmpCon-DC UI to push configurations to switches, each switch then downloads its appropriate configurations. At the same time, the switch accesses another AmpCon-DC server component, the License Manager, which accesses the customer’s account on the License Portal to generate a license key and install the license on the switch.
The switch runs a shell script to automatically reboot, apply and validate the new configurations, update its status in the AmpCon-DC database, and join the network. From your perspective, all these switch configurations happen with the touch of a button in the AmpCon-DC UI. You can use the AmpCon-DC UI to deploy dozens or hundreds of switches to far-flung sites while your network team stays at home and monitors the process centrally.
...