Versions Compared

Version Old Version 1 New Version Current
Changes made by

Tracy Yang

Jennifer Xiao

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

AmpCon™AmpCon-DC Campus is built on Ubuntu Linux and incorporates a web GUI and a MySQL database with Python codes built on top of an Ansible engine. Switches and AmpCon-DC Campus communicate with the SSH protocol. AmpCon-DC Campus gets switch statistics through gNMI.

AmpCon-DC workflow

...

stats through gNMI.

Table of Contents
stylenone

Zero Touch Provisioning (ZTP) Workflow

White-Box Switches

Figure 1. ZTP Workflow of White-Box Switches

...

  1. 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.

  2. The switch sends a request to the DHCP server, and the DHCP server sends a response including the HTTP server address.

  3. 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.

  4. The switch executes the shell script to complete the ZTP deployment, including downloading a PicOS image, installing PicOS and its license, registering with the AmpCon-Campus server, updating switch configurations, and rebooting the switch.

Integrated Hardware and Software Switches

Figure 2. ZTP Workflow of Integrated Hardware and Software Switches

...

  1. 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.

  2. The switch sends a DHCP request to the DHCP server, and the DHCP server sends a DHCP response including the TFTP server address.

  3. 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.

  4. 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

  1. 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 be deployed on all switches, along with any site region-specific variationsconfigure switches. All configurations are tied to specific switches by the switch serial number (or Service Tag) and are stored in a the AmpCon-Campus database.

  2. After registering with you use the AmpCon-DC serverCampus UI to push configurations to switches, each switch then downloads its appropriate configurationconfigurations. At the same time, the switch will access accesses another AmpCon-DC Campus server component, the License Manager, which will access accesses the customer’s account on the Pica8 License Portal to generate a license key and install the license on the switch.

  3. The switch runs a shell script to automatically reboot, apply and validate the new configurationconfigurations, update its status in the configuration AmpCon-Campus database, and join the network. From your perspective, all of this switch configuration happens these switch configurations happen with the touch of a button – as close to “zero-touch provisioning”. AmpCon-DC can help you 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.

...