AmpCon™-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-Campus communicate with the SSH protocol. AmpCon-Campus gets switch stats through gNMI.
Switch Deployment Workflow
AmpCon-Campus supports deploying switches with Zero Touch Provisioning (ZTP):
After you plug in the switch, DHCP automatically provides the switch with an IP address and a script address that is obtained from AmpCon-Campus server.
The switch runs the script to find the AmpCon-Campus server, register with it, and then complete the PicOS® installation.
Switch Configuration Workflow
Figure 1. Configuring Switches with AmpCon-Campus
The AmpCon-Campus server includes a component called the Configuration Manager. Your network team uses it 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 stored in a database.
After registering with the AmpCon-Campus server, 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 script to automatically reboot, apply and validate the new configurations, update its status in the configuration 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 AmpCon-Campus to deploy dozens or hundreds of switches to far-flung sites while your network team stays at home and monitors the process centrally.