...
| Table of Contents | ||
|---|---|---|
|
Switch Deployment Workflow
...
Zero Touch Provisioning (ZTP)
...
Workflow
White-Box Switches
Figure 1. ZTP Workflow of White-Box Switches
...
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 request to the DHCP server, and the DHCP server sends a script address that is obtained from AmpCon-Campus serverresponse including the HTTP server address.
The switch sends an HTTP request to the HTTP server to get the shell script, and the HTTP server sends an HTTP response with the shell script.
The switch automatically runs executes the shell script to find complete the ZTP deployment, including downloading a PicOS image, installing PicOS and its license, registering with the AmpCon-Campus server, register with itupdating switch configurations, and then complete rebooting the PicOS installationswitch.
...
Integrated Hardware and Software Switches
Figure 1. Configuring Switches with AmpCon-Campus
...
2. ZTP Workflow of Integrated Hardware and Software Switches
...
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-Campus server, installing a PicOS license on the switch, updating switch configurations, and rebooting the switch.
Switch Configuration Workflow
The AmpCon-Campus server includes a component called the Configuration Manager. Your network team uses it , which is used to create a standard configuration to configure switches, along with any region-specific variations. All configurations are tied to specific switches by the switch serial number (or Service Tag) and are stored in a the AmpCon-Campus database.
After registering with you use the AmpCon-Campus serverUI to push configurations to switches, each switch then downloads its appropriate configurations. At the same time, the switch accesses another AmpCon-Campus 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 configuration AmpCon-Campus database, and join the network. From your perspective, all these switch configurations happen with the touch of a button in the AmpCon-Campus UI. You can use the AmpCon-Campus UI to deploy dozens or hundreds of switches to far-flung sites while your network team stays at home and monitors the process centrally.
...