Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 3 Next »

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 statistics through gNMI.

AmpCon-Campus workflow

2.png
  1. The AmpCon-Campus server includes a component called the Configuration Manager. Your network team uses it to create a standard configuration to be deployed on all switches, along with any site region-specific variations. All configurations are tied to specific switches by the switch serial number (or Service Tag) and stored in a database.

  2. After registering with the AmpCon-Campus server, each switch then downloads its appropriate configuration. At the same time, the switch will access another AmpCon-Campus server component, the License Manager, which will access 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 script to automatically reboot, apply and validate the new configuration, update its status in the configuration database, and join the network. From your perspective, all of this switch configuration happens 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.

  • No labels