FS Singapore FREE SHIPPING on Orders Over SGD99 GST excl.

FREE SHIPPING on Orders Over SGD99 GST excl.

Singapore



Document Center





FS GPT

Search result for "344499"

Types

Sort by

AmpCon-Campus Installation and Upgrade Guide

Feb 12, 2026 - AmpCon-Campus Installation and Upgrade Guide Supported Deployments The following AmpCon-Campus deployments are supported: Table 1. Supported Deployment Information Indicator Support information Deployment method VMware ESXi 6.7, 7.0, 8.0, QEMU / KVM for Ubuntu 22.04 LTS, Oracle VirtualBox for lab only, physical machine based on Ubuntu 22.04 LTS with Docker Maximum number of switches supported 1000 Maximum number of registered users 1000 Maximum number of online users 100 Storage duration of system logs 2 months Storage duration of operation logs 2 months Maximum storage of current alerts Unlimited Maximum storage of historical alerts 2 months Installation Requirements Before you install the AmpCon-Campus server, ensure that the following requirements are met. Server Requirements If you want to install the AmpCon-Campus server on a physical machine, ensure that the physical machine meets the following requirements: NOTE To install the AmpCon-Campus server on a virtual machine, ensure that the hypervisor has the following resources (CPU, memory, and hard disk) to be allocated when you import the AmpCon-Campus server image. Table 2. Server Requirement Details Indicators Requirements CPU Clock speed 2.0 GHz or faster Number of cores At least 4 CPU cores Memory At least 16 GB Hard disk At least 512 GB Operating systems Ubuntu 22.04 LTS (X86 architecture) with Docker Network Requirements Before you install AmpCon-Campus, set the firewall and proxy properly to allow the following network access: Table 3. Network Requirement for the AmpCon-Campus Server Machine TCP/UDP Port Protocol TCP 80 HTTP TCP 443 HTTPS UDP 69 TFTP UDP 80 OpenVPN NOTE On AmpCon-Campus, each managed switch has two IP addresses: Mgmt IP and VPN IP. Mgmt IP is the management IP address of a switch. Mgmt IP is used to connect to the AmpCon-Campus server during the switch onboarding process. However, Mgmt IP might be changed. To ensure uninterrupted connection between the AmpCon-Campus server and a switch after Mgmt IP is changed, OpenVPN is introduced to AmpCon-Campus. OpenVPN is an open-source virtual private network (VPN) solution designed to create secure, encrypted communication tunnels over networks. After a switch is onboarded to AmpCon-Campus successfully, a VPN tunnel between the AmpCon-Campus server and the switch is established, and a VPN IP, the IP address of the VPN tunnel, is assigned to the switch. Later, the AmpCon-Campus server and the switch will communicate through the VPN tunnel. The AmpCon-Campus server also functions as the OpenVPN server, and its OpenVPN IP address is 10.8.0.1. The default subnet for OpenVPN is 10.8.0.0/20. If the default subnet has conflicts with your network, AmpCon-Campus can’t work well. Contact the FS support team to resolve this issue. License Requirements Obtain an AmpCon-Campus license from the FS sale team. The following AmpCon-Campus license types are supported: Trial license: The trial period lasts for 90 days and an additional 14 days. After the trial license is expired, you must install a standard license to continue using AmpCon-Campus. Standard license: After a standard license is installed, you cannot install a trial license. Installing the AmpCon-Campus Server You can install the AmpCon-Campus server on a virtual machine or a physical machine by using one of the following methods: Installing on VMware ESXi Installing on QEMU or KVM Installing on VirtualBox for Lab Only Installing on Physical Machines (Ubuntu Docker) If multiple NICs are added to the virtual machine or physical machine, you must specify the NIC IP address used by the AmpCon-Campus server to establish connections with managed switches, in the configuration file (/usr/share/automation/server/.env). Otherwise, the connections between the AmpCon-Campus server and managed switches might fail. For more information, see Multi-NIC Deployment for Switch Connectivity. NOTE On AmpCon-Campus, each managed switch has two IP addresses: Mgmt IP and VPN IP. Mgmt IP is the management IP address of a switch. Mgmt IP is used to connect to the AmpCon-Campus server during the switch onboarding process. However, Mgmt IP might be changed. To ensure uninterrupted connection between the AmpCon-Campus server and a switch after Mgmt IP is changed, OpenVPN is introduced to AmpCon-Campus. OpenVPN is an open-source virtual private network (VPN) solution designed to create secure, encrypted communication tunnels over networks. After a switch is onboarded to AmpCon-Campus successfully, a VPN tunnel between the AmpCon-Campus server and the switch is established, and a VPN IP, the IP address of the VPN tunnel, is assigned to the switch. Later, the AmpCon-Campus server and the switch will communicate through the VPN tunnel. The AmpCon-Campus server also functions as the OpenVPN server, and its OpenVPN IP address is 10.8.0.1. The default subnet for OpenVPN is 10.8.0.0/20. If the default subnet has conflicts with your network, AmpCon-Campus can’t work well. Contact the FS support team to resolve this issue. Installing on VirtualBox for Lab Only You can install the AmpCon-Campus server on VirtualBox for lab purposes only. Production environments require a proper enterprise-scale virtualization solution as described in Supported Deployments. For how to use VirtualBox in general, see the Oracle VirtualBox documentation. Prerequisites Ensure that the installation requirements are met. Download the compressed AmpCon-Campus server image file by going to the FS AmpCon-Campus website and then clicking AmpCon-Campus for VirtualBox 2.3.x Software in the Resources section. Put the compressed AmpCon-Campus server image file to the machine where the hypervisor exists, and unzip the file. Installation Procedure 1. Open the VirtualBox console, and then click File > Import Appliance. image.png 2. Select Local File System, import the AmpCon-Campus server .ova image file, and then click Next. image.png 3. Confirm the settings for the .ova file, and then click Finish. image.png Wait for the importing process to finish. Once completed, the virtual machine is successfully imported, and the AmpCon-Campus server is installed. NOTE The AmpCon-Campus server is installed in the /usr/share/automation/server directory. Currently, you can’t customize the installation directory. image.png 4. Click Settings, and then check the settings of the imported virtual machine. image.png NOTE In the Network column, the default value of the Promiscuous Mode is Deny. You must change it to Allow All. image.png 5. Start the imported virtual machine by clicking the virtual machine and then clicking Start. image.png 6. Modify the network interface configuration. a. Log in to the virtual machine with the default username (pica8) and password (pica8). b. Modify the IP address with the real IP address of the virtual machine. sudo vi /etc/netplan/00-installer-config.yaml c. In the 00-installer-config.yaml file, modify the IP address with the real IP address of the virtual machine as follows: NOTE The Network Interface Card (NIC) name in the 00-installer-config.yaml file might not match the real NIC name of the virtual machine. Therefore, you must check the real NIC name of the virtual machine first by using the command ip addr show and then update the NIC name in the 00-installer-config.yaml file. image.png d. Apply the network interface configuration by running the following command: sudo netplan apply 7. Start the AmpCon-Campus server: a. Go to the AmpCon-Campus installation directory by running the following command: cd /usr/share/automation/server b. Start the AmpCon-Campus server by running the following command: sudo ./start.sh Now the AmpCon-Campus server is installed and started. What to Do Next If multiple NICs are added to the virtual machine or physical machine, you must specify the NIC IP address used by the AmpCon-Campus server to establish connections with managed switches, in the configuration file (/usr/share/automation/server/.env). Otherwise, the connections between the AmpCon-Campus server and managed switches might fail. For more information, see Multi-NIC Deployment for Switch Connectivity. To stop the AmpCon-Campus server, follow the steps: 1. Go to the AmpCon-Campus installation directory by running the cd /usr/share/automation/server command. 2. Stop the AmpCon-Campus server by running the sudo ./stop.sh command. To start the the AmpCon-Campus server after it is stopped, follow the steps: 1. Go to the AmpCon-Campus installation directory by running the cd /usr/share/automation/server command. 2. Start the AmpCon-Campus server by running the sudo ./start.sh command. Installing on VMware ESXi You can install the AmpCon-Campus server on VMware ESXi 6.7, 7.0, 8.0. For how to use VMware ESXi in general, see the VMware ESXi documentation. Prerequisites Ensure that the installation requirements are met. Download the compressed AmpCon-Campus server image file by going to the FS AmpCon-Campus website and then clicking AmpCon-Campus for VMWare ESXi 2.3.x Software in the Resources section. Put the compressed AmpCon-Campus server image file to the machine where the hypervisor exists, and unzip the file. Installation Procedure 1. Open the VMware ESXi console, and then click Create / Register VM. image.png 2. Select Deploy a virtual machine from an OVF or OVA file, and then click Next. image.png 3. Enter the virtual machine name, upload the AmpCon-Campus server .ovf and .vmdk files, and then click Next. image.png 4. Confirm the storage type and datastore, and then click Next. image.png 5. In the Network mappings drop-down list of the Deployment Options window, select the network adapter to which the virtual machine is connected, and then click Next. 6. Click Finish. image.png Wait for the importing process to finish. Once completed, the virtual machine is successfully imported, and the AmpCon-Campus server is installed. NOTE The AmpCon-Campus server is installed in the /usr/share/automation/server directory. Currently, you can’t customize the installation directory. 7. On the VMware ESXi console, click the new virtual machine name that you specified in step 3. image.png 8. Click Console to open the virtual machine console. image.png 9. Modify the network interface configuration. a. Log in to the virtual machine with the default username (pica8) and password (pica8). b. Modify the IP address with the real IP address of the virtual machine. sudo vi /etc/netplan/00-installer-config.yaml c. In the 00-installer-config.yaml file, modify the IP address with the real IP address of the virtual machine as follows: image.png d. Apply the network interface configuration by running the following command: sudo netplan apply 10. Start the AmpCon-Campus server: a. Go to the AmpCon-Campus installation directory by running the following command: cd /usr/share/automation/server b. Start the AmpCon-Campus server by running the following command: sudo ./start.sh Now the AmpCon-Campus server is installed and started. What to Do Next If multiple NICs are added to the virtual machine or physical machine, you must specify the NIC IP address used by the AmpCon-Campus server to establish connections with managed switches, in the configuration file (/usr/share/automation/server/.env). Otherwise, the connections between the AmpCon-Campus server and managed switches might fail. For more information, see Multi-NIC Deployment for Switch Connectivity. To stop the AmpCon-Campus server, follow the steps: 1. Go to the AmpCon-Campus installation directory by running the cd /usr/share/automation/server command. 2. Stop the AmpCon-Campus server by running the sudo ./stop.sh command. To start the the AmpCon-Campus server after it is stopped, follow the steps: 1. Go to the AmpCon-Campus installation directory by running the cd /usr/share/automation/server command. 2. Start the AmpCon-Campus server by running the sudo ./start.sh command. Installing on QEMU or KVM You can install the AmpCon-Campus server on QEMU or KVM. For how to use QEMU or KVM in general, see the KVM documentation and QEMU documentation. In this topic, KVM virt-manager is used to demonstrate the AmpCon-Campus server installation steps. Prerequisites Ensure that the installation requirements are met. Download the compressed AmpCon-Campus server image file by going to the FS AmpCon-Campus website and then clicking AmpCon-Campus for QEMU/KVM 2.3.x Software in the Resources section. Put the compressed AmpCon-Campus server image file to the machine where the hypervisor exists, and unzip the file. Installation Procedure 1. Open the virt-manager console by running the following command: virt-manager 2. Click the following button to start the importing process. image.png 3. Select Import existing disk image, and then click Forward. image.png 4. Click Browse to select the AmpCon-Campus server .qcow2 image file. image.png 5. Click Browse Local to add a local location. image.png 6. Find the location of the AmpCon-Campus server .qcow2 image file, and then click Open. image.png 7. Select Ubuntu 22.04 LTS, and then click Forward. NOTE Do not select other operating systems because AmpCon-Campus supports only Ubuntu 22.04 currently. image.png 8. Adjust the memory and CPU settings as needed, and then click Forward. NOTE The memory and CPU settings need to meet the Server Requirements. image.png 9. In the Network selection section, select Macvtap device, and enter the device name. Then, click Finish. image.png Wait for the importing process to finish. Once completed, the virtual machine is successfully imported, and the AmpCon-Campus server is installed. NOTE The AmpCon-Campus server is installed in the /usr/share/automation/server directory. Currently, you can’t customize the installation directory. image.png 10. Modify the network interface configuration. a. Log in to the virtual machine with the default username (pica8) and password (pica8). b. Modify the IP address with the real IP address of the virtual machine. sudo vi /etc/netplan/00-installer-config.yaml c. In the 00-installer-config.yaml file, modify the IP address with the real IP address of the virtual machine as follows:. image.png d. Apply the network interface configuration by running the following command: sudo netplan apply 11. Start the AmpCon-Campus server: a. Go to the AmpCon-Campus installation directory by running the following command: cd /usr/share/automation/server b. Start the AmpCon-Campus server by running the following command: sudo ./start.sh Now the AmpCon-Campus server is started. What to Do Next If multiple NICs are added to the virtual machine or physical machine, you must specify the NIC IP address used by the AmpCon-Campus server to establish connections with managed switches, in the configuration file (/usr/share/automation/server/.env). Otherwise, the connections between the AmpCon-Campus server and managed switches might fail. For more information, see Multi-NIC Deployment for Switch Connectivity. To stop the AmpCon-Campus server, follow the steps: 1. Go to the AmpCon-Campus installation directory by running the cd /usr/share/automation/server command. 2. Stop the AmpCon-Campus server by running the sudo ./stop.sh command. To start the the AmpCon-Campus server after it is stopped, follow the steps: 1. Go to the AmpCon-Campus installation directory by running the cd /usr/share/automation/server command. 2. Start the AmpCon-Campus server by running the sudo ./start.sh command. Installing on Physical Machines (Ubuntu Docker) You can install the AmpCon-Campus server on a physical machine based on Ubuntu 22.04 LTS with Docker installed. Prerequisites Prepare a physical machine based on Ubuntu 22.04 LTS with Docker installed. Ensure that the installation requirements are met. Download the compressed AmpCon-Campus server installation package AmpCon-Campus for Ubuntu Docker V2.3.x Software from the FS AmpCon-Campus website. Installation Procedure 1. Put the AmpCon-Campus server installation package to the prepared physical machine, and then extract the package by running the unzip .zip command. A .tar.gz file is generated in the current directory. Extract the generated .tar.gz file by running the tar -zxvf .tar.gz command. A directory is generated with AmpCon-Campus server installation files. NOTE Replace in the command with the name of the AmpCon-Campus server installation package. Replace in the command with the extracted .tar.gz file name. 2. On the physical machine, modify the network interface configuration as follows: a. Open the file named 00-installer-config.yaml by running the following command: sudo vi /etc/netplan/00-installer-config.yaml b. In the 00-installer-config.yaml file, modify the IP address with the real IP address of the physical machine. image.png c. Apply the network interface configuration by running the following command: sudo netplan apply 3. Go to the directory where the unzipped AmpCon-Campus server installation files exist. cd Replace with the name of the directory containing the unzipped AmpCon-Campus server installation files. 4. Install the AmpCon-Campus server by running the following command: sudo ./install_or_upgrade.sh Wait for the installation process to finish. Once completed, the AmpCon-Campus server is installed and started. NOTE The AmpCon-Campus server is installed in the /usr/share/automation/server directory. Currently, you can’t customize the installation directory. What to Do Next If multiple NICs are added to the virtual machine or physical machine, you must specify one NIC IP address, which is used by AmpCon-Campus server to establish connections with the switches to be managed, in the configuration file (/usr/share/automation/server/.env). Otherwise, the connections between the AmpCon-Campus server and the switches to be managed might fail. For more information, see Multi-NIC Deployment for Switch Connectivity. To stop the AmpCon-Campus server, follow the steps: a. Go to the AmpCon-Campus installation directory by running the cd /usr/share/automation/server command. b. Stop the AmpCon-Campus server by running the sudo ./stop.sh command. To start the the AmpCon-Campus server after it is stopped, follow the steps: a. Go to the AmpCon-Campus installation directory by running the cd /usr/share/automation/server command. b. Start the AmpCon-Campus server by running the sudo ./start.sh command. Multi-NIC Deployment for Switch Connectivity As described in Installing the AmpCon-Campus Server, you need to import the AmpCon-Campus image file to a virtual machine or unzip the AmpCon-Campus installation packet file on a physical machine to install the AmpCon-Campus server. If multiple NICs are added to the virtual machine or physical machine, you must specify one NIC IP address, which is used by the AmpCon-Campus server to establish connections with the switches to be managed, in the configuration file (/usr/share/automation/server/.env). Otherwise, the connections between the AmpCon-Campus server and the switches to be managed might fail. NOTE When you install the AmpCon-Campus server on a virtual machine, the imported AmpCon-Campus image file contains only one Network Interface Card (NIC). But you can manually add more NICs. When you install the AmpCon-Campus server on a physical machine, the AmpCon-Campus installation package file is not an image file, and thus no NIC is contained in the file. But you can manually add one or multiple NICs to the physical machine. Prerequisite Ensure that the AmpCon-Campus server is installed on a virtual machine or a physical machine. Procedure 1. Log in to the virtual machine or the physical machine, and then open the /usr/share/automation/server/.env file. sudo vim /usr/share/automation/server/.env 2. Locate the line containing PROD_IP= in the file, and add the NIC IP address of the AmpCon-Campus server machine, which is used to connect to the switches to be managed. image.png 3. Restart the AmpCon-Campus server by the following commands: cd /usr/share/automation/server/ sudo ./start.sh Upgrading the AmpCon-Campus Server To upgrade the AmpCon-Campus server to 2.3.0, see the following upgrading path and procedure. Upgrading Path If the AmpCon-Campus server that you are using is 2.1.0, 2.1.1, 2.2.0, 2.2.1, or 2.3.0E, you can upgrade it to 2.3.0. Upgrading Procedure 1. Download the AmpCon-Campus server upgrade package Software Upgrade Package for AmpCon-Campus V2.3.0 from the FS AmpCon-Campus website. Then, the upgrade package will be downloaded to your local machine. 2. Copy the upgrade package to the AmpCon-Campus server machine, and then extract the package by running the following command: unzip .zip Replace with the real upgrade package name. Then, a .tar.gz file is generated in the current directory. Run the following command to extract the .tar.gz file: tar -zxvf .tar.gz Replace with the real extracted .tar.gz file name. 3. After extracting the upgrade package, go to the extracted upgrade package directory, and then run the following upgrade command: image.png 4. Wait for the upgrade process to complete. Once you see a success message, the upgrade is finished. image.png 5. Log in to the AmpCon-Campus UI, and then click admin > Version to check the current AmpCon-Campus version. image.png Uninstalling the AmpCon-Campus Server To uninstall the AmpCon-Campus server, follow these steps: Procedure 1. Go to the root directory of the AmpCon-Campus server, and run the stop script with sudo privileges: cd /usr/share/automation/server sudo ./stop.sh 2. Clear the files in the server directory with sudo privileges: sudo rm -rf /usr/share/automation/server

AmpCon-Campus Quick Deployment Guide

Feb 12, 2026 - AmpCon-Campus Quick Deployment Guide The following topics provide quick start guides for AmpCon-Campus, detailing the workflows of AmpCon-Campus server installation, FSOS switch importing, PicOS switch onboarding, template-based switch configuration, campus network deployment (wireless and wired), and Ansible Automation. Platform Installation Workflow To use powerful features of AmpCon-Campus, you need to install the AmpCon-Campus server on a virtual machine or physical machine. This guide provides a comprehensive overview of AmpCon-Campus server installation procedures. Prerequisites If you want to install the AmpCon-Campus server on a physical machine, ensure that the physical machine meets the following requirements: NOTE: To install the AmpCon-Campus server on a virtual machine, ensure that the hypervisor has the following resources (CPU, memory, and hard disk) to be allocated when you import the AmpCon-Campus server image to the hypervisor. Table 1. Machine Requirements Resource Requirement CPU Clock speed: 2.0 GHz or faster Number of cores: At least 4 CPU cores Memory At least 16 GB Hard Disk At least 512 GB Operating System Ubuntu 22.04 LTS (X86 architecture) with Docker Whether you want to install the AmpCon-Campus server on a physical machine or virtual machine, if a firewall is used, configure the firewall properly to allow the following network access: Table 2. Network Requirements TCP/UDP Port Protocol TCP 80 HTTP TCP 443 HTTPS UDP 69 TFTP UDP 80 OpenVPN NOTE: On AmpCon-Campus, each managed switch has two IP addresses: Mgmt IP and VPN IP. Mgmt IP is the management IP address of a switch. Mgmt IP is used to connect to the AmpCon-Campus server during the switch onboarding process. However, Mgmt IP might be changed. To ensure uninterrupted connection between the AmpCon-Campus server and a switch after Mgmt IP is changed, OpenVPN is introduced to AmpCon-Campus. OpenVPN is an open-source virtual private network (VPN) solution designed to create secure, encrypted communication tunnels over networks. After a switch is onboarded to AmpCon-Campus successfully, a VPN tunnel between the AmpCon-Campus server and the switch is established, and a VPN IP, the IP address of the VPN tunnel, is assigned to the switch. Later, the AmpCon-Campus server and the switch will communicate through the VPN tunnel. The AmpCon-Campus server also functions as the OpenVPN server, and its OpenVPN IP address is 10.8.0.1. The default subnet for OpenVPN is 10.8.0.0/20. If the default subnet has conflicts with your network, AmpCon-Campus can’t work well. Contact the FS support team to resolve this issue. Installing on a Virtual Machine To install the AmpCon-Campus server on a virtual machine, complete the following tasks: Table 3. Tasks for Installation on Virtual Machines Task Description Preparing a Hypervisor Prepare the hypervisor used to create the virtual machine. The following hypervisors are supported: VMware ESXi 6.7, 7.0, or 8.0 QEMU for Ubuntu 22.04 LTS KVM for Ubuntu 22.04 LTS Oracle VirtualBox NOTE: The AmpCon-Campus server installed on Oracle VirtualBox can be used for lab purposes only. Downloading the AmpCon-Campus Server Image Download the compressed AmpCon-Campus server image by going to the FS AmpCon-Campus website and locating the image related to the hypervisor and the AmpCon-Campus version. Put the compressed AmpCon-Campus server image to the machine where the hypervisor exists, and then unzip the image. Importing the AmpCon-Campus Server Image Import the unzipped AmpCon-Campus server image to the hypervisor. For different hypervisors, the steps of importing the AmpCon-Campus server image are different. To check detailed importing steps on each hypervisor, see Installing on VMware ESXi, Installing on QEMU or KVM, and Installing on VirtualBox for Lab Only. Wait for the importing process to finish. Once completed, the virtual machine is successfully created, and the AmpCon-Campus server is installed. The AmpCon-Campus server is installed in the /usr/share/automation/server directory. Currently, you can’t customize the installation directory. Modifying the Network Interface Configuration Start the virtual machine. Log in to the virtual machine with the default username (pica8) and password (pica8). Open the file named 00-installer-config.yaml by running the sudo vi /etc/netplan/00-installer-config.yaml command. In the 00-installer-config.yaml file, modify the IP address with the real IP address of the virtual machine as follows: image.png The Network Interface Card (NIC) name in the 00-installer-config.yaml file might not match the real NIC name of the virtual machine. Therefore, you must check the real NIC name of the virtual machine first by using the command ip addr show and then update the NIC name in the 00-installer-config.yaml file. Apply the network interface configuration by running the sudo netplan apply command. Starting the AmpCon-Campus Server Go to the AmpCon-Campus installation directory by running the cd /usr/share/automation/server command. Start the AmpCon-Campus server by running the sudo ./start.sh command. Installing on a Physical Machine To install the AmpCon-Campus server on a physical machine (Ubuntu 22.04 LTS with Docker installed), complete the following tasks: Table 4. Tasks for Installation on Physical Machines Task Description Preparing a Physical Machine Prepare a physical machine based on Ubuntu 22.04 LTS with Docker installed. Downloading and Unzipping the AmpCon-Campus Server Installation Package Download the compressed AmpCon-Campus server installation package by going to the FS AmpCon-Campus website and locating the package related to the AmpCon-Campus version. Put the AmpCon-Campus server installation package to the prepared physical machine, and then extract the package by running the unzip .zip command. A .tar.gz file is generated in the current directory. Extract the generated .tar.gz file by running the tar -zxvf .tar.gz command. A directory is generated with AmpCon-Campus server installation files. NOTE: Replace in the command with the name of the AmpCon-Campus server installation package. Replace in the command with the extracted .tar.gz file name. Modifying the Network Interface Configuration On the physical machine, open the file named 00-installer-config.yaml by running the sudo vi /etc/netplan/00-installer-config.yaml command. In the 00-installer-config.yaml file, modify the IP address with the real IP address of the physical machine. image.png Apply the network interface configuration by running the sudo netplan apply command. Starting the AmpCon-Campus Server Go to the directory where the unzipped AmpCon-Campus server installation files exist. Install the AmpCon-Campus server by running the sudo ./install_or_upgrade.sh command. Wait for the installation process to finish. Once completed, the AmpCon-Campus server is installed and started. The AmpCon-Campus server is installed in the /usr/share/automation/server directory. Currently, you can’t customize the installation directory. What to Do Next After you install the AmpCon-Campus server, check the following tasks. These tasks are not mandatory and can be used only when needed. Table 5. Post-Installation Tasks Task Description Configuring for Multi-NIC Deployment If multiple NICs are added to the virtual machine or physical machine, you must specify the NIC IP address used by the AmpCon-Campus server to establish connections with managed switches, in the configuration file (/usr/share/automation/server/.env). Otherwise, the connections between the AmpCon-Campus server and managed switches might fail. For more information, see Multi-NIC Deployment for Switch Connectivity Stopping the AmpCon-Campus Server To stop the AmpCon-Campus server, follow the steps: Go to the AmpCon-Campus installation directory by running the cd /usr/share/automation/server command. Stop the AmpCon-Campus server by running the sudo ./stop.sh command. Uninstalling the AmpCon-Campus Server To uninstall the AmpCon-Campus server, follow the steps: Go to the AmpCon-Campus installation directory by running the cd /usr/share/automation/server command. Stop the AmpCon-Campus server by running the sudo ./stop.sh command. Clear the files in the server directory by running the sudo rm -rf /usr/share/automation/server command. Logging In to the AmpCon-Campus UI The first time you log in to the AmpCon-Campus UI, use the default username admin and password admin. For more information, see Working with the User Interface. NOTE: The user admin is a built-in account of the SuperAdmin role. It has all operation permissions on AmpCon-Campus. For security purposes, change the password upon the first login, update it periodically, and keep it secure. For how to update the password, see User Self-Management. You can add other user accounts and enable limited access for the personnel who are working with you. For more information, see Managing User Access. FSOS Switch Importing Workflow AmpCon-Campus supports monitoring FSOS switches and doesn’t support managing FSOS switches. To monitor FSOS switches with AmpCon-Campus, you need to import these switches to AmpCon-Campus through Simple Network Management Protocol (SNMP). This guide provides a comprehensive overview of FSOS switch import procedures. Prerequisites Before you import FSOS switches, ensure that the following prerequisite tasks have been completed: Table 6. Prerequisite Tasks and Links Category Task Reference Link Platform Requirement Install the AmpCon-Campus server successfully. Platform Installation Workflow Log in to the AmpCon-Campus UI with the SuperAdmin, Admin, or Operator role. Working with the User Interface Switch Requirement Ensure that the FSOS switches are supported to be managed by AmpCon-Campus. Supported FSOS Switches for 2.3.0 Ensure that you have enabled SNMP and configured SNMP authentication on the FSOS switches. No Reference Link Ensure that the OIDs (Sysname, Serial Number, Model, and Version) are not blocked on the switch side. These OIDs must be accessible for the SNMP View feature. Network Requirement Ensure that the AmpCon-Campus server can connect with the FSOS switches and no network timeout issues exist due to reasons like unreachable IP, disabled SNMP, firewall blockage, or Access Control List (ACL) restrictions. No Reference Link Procedure Click Wired > Switches from the navigation bar, and then click the FSOS tab. In this tab, you can import a single FSOS switch or import multiple FSOS switches in batches. Table 7. FSOS Switch Import Tasks and Links Category Task Reference Link Importing a Single FSOS Switch To import a single FSOS switch, hover your mouse over Import Actions, and then click Single Import. image.png Importing a Switch Importing Multiple FSOS Switches in Batches To import multiple FSOS switches in batches, hover your mouse over Import Actions, and then click Batch Import. image.png Importing Switches in Batches Checking Import Status In the FSOS tab, click View Import Details. In the pop-up window, check the Import Status column. image.png Checking Importing Results What to Do Next After you import FSOS switches, you can monitor these switches in the AmpCon-Campus UI. Category Task Reference Link Monitoring FSOS Switches Click Wired > Switches from the navigation bar. Click the FSOS tab, and then you can see the list of imported FSOS switches. image.png Viewing the Switch List In the FSOS tab, locate an FSOS switch, and click the SN or service tag of the switch. Then, you can see detailed metrics of the switch. image.png Viewing FSOS Switch Details Click Monitor > SNMP Management > SNMP Visualization from the navigation bar. On the “SNMP Visualization” page, you can add and view item-based trend graphs for imported FSOS switches. image.png Viewing SNMP Trend Graphs Click Monitor > SNMP Management > SNMP Data Filtering from the navigation bar. On the “SNMP Data Filtering” page, you can filter SNMP data of all the imported FSOS switches. image.png Filtering SNMP Data PicOS Switch Onboarding Workflow Onboard PicOS switches to bring them under AmpCon-Campus management. Once successfully onboarded, the PicOS switches are classified as managed devices and can be used to deploy wired networks. This guide provides a comprehensive overview of the procedures for onboarding PicOS switches to AmpCon-Campus. Guidelines To onboard PicOS switches, two options are provided: importing switches to AmpCon-Campus and deploying switches through Zero Touch Provisioning (ZTP). If the switches to be managed have PicOS installed, you can onboard these switches by importing them to AmpCon-Campus directly. If the switches to be managed don’t have PicOS installed, or though the switches have PicOS installed but you want to onboard these switches through ZTP, you can use AmpCon-Campus to deploy these switches through ZTP. NOTE: Importing switches is not a ZTP method, which means that you still need to connect to the switches and do some operations on the switch side, such as obtaining IP addresses from the switches. The importing switch process doesn’t push switch configurations. Deploying switches through ZTP is a ZTP method used for automated deployment of switches. After you reboot the switches, AmpCon-Campus will deploy the switches automatically. During the ZTP process, AmpCon-Campus will push pre-configured configurations to the switches. Integrated hardware and software switches have PicOS installed. To onboard these switches, you can import these switches to AmpCon-Campus directly, or you can deploy these switches through ZTP. Prerequisites Before you onboard PicOS switches, ensure that the following prerequisite tasks have been completed: Table 8. Prerequisite Tasks and Links Category Task Reference Link Platform Requirement Install the AmpCon-Campus server successfully. Platform Installation Workflow Log in to the AmpCon-Campus UI with an account of the SuperAdmin role. Working with the User Interface Switch Requirement Ensure that the switches to be onboarded are supported by AmpCon-Campus. Supported PicOS Switches for 2.3.0 For switches that have PicOS installed, ensure that the Secure Shell (SSH) protocol is enabled on these switches. SSH is enabled on PicOS switches by default. No Reference Link Network Requirement Ensure that the switches are able to connect to the AmpCon-Campus server. No Reference Link If a firewall is configured between the AmpCon-Campus server and the switches, allow outbound access on the following ports to the management port of each switch. TCP: 22 TCP: 9339 TCP: 830 No Reference Link Importing a PicOS Switch To onboard a PicOS switch by importing it to AmpCon-Campus, complete the following tasks: Table 9. Switch Importing Tasks and Links Category Task Reference Link Importing Licenses Obtain an AmpCon-Campus license (containing hardware IDs of the switches to be onboarded) from the FS sale team. Import the AmpCon-Campus license (containing hardware IDs of the switches to be imported) to AmpCon-Campus. Importing Licenses for Imported Switches Adding System Configurations Click Wired > Wired Profiles from the navigation bar of the AmpCon-Campus UI. Click the System Configuration tab. In this tab, configure the global system configuration. If the global system configuration doesn’t match with the switch, create a non-global system configuration. Adding System Configurations Importing PicOS Switches If you have obtained the IP address of the switch, you can use the automatic import method. Automatically Importing a Switch If you haven’t obtained the IP address of the switch, you can use the manual import method. Manually Importing a Switch Verifying Switch Status Click Wired > Switches from the navigation bar. In the PicOS tab, check whether the imported switch is displayed in Imported status. Checking Importing Results Deploying a Switch through ZTP Deploying a White-Box Switch To onboard a white-box switch by deploying it through ZTP, complete the following tasks: Table 10. White-Box Switch Deployment Tasks and Links Category Task Reference Link System Configuration Click Wired > Wired Profiles from the navigation bar of the AmpCon-Campus UI. Click the System Configuration tab. In this tab, configure the global system configuration. If the global system configuration doesn’t match with the switch, create a non-global system configuration. Adding System Configurations Switch Model Click the Switch Model tab. In this tab, configure the switch model related to the switch. Configuring Switch Models Global Configuration Click the Global Configuration tab. In this tab, prepare the global configuration to be pushed to the switch. Configuring Global Configurations Configuration Template Click Wired > Config Templates from the navigation bar. Click the Template List tab. In this tab, check whether an existing configuration template meets your need. If not, click the New Template tab, and then add a new configuration template. Managing Configuration Templates Adding Configuration Templates Switch Configuration Click Wired > Wired Profiles from the navigation bar. Click the Switch Configuration tab. In this tab, add a switch configuration for the switch. Adding Switch Configurations DHCP Server Configure a DHCP server. If the DHCP server is not configured correctly, the switch deployment will fail. Configuring a DHCP Server Switch Provisioning through ZTP Provision the switch through ZTP to complete the switch deployment. Provisioning a White-Box Switch NOTE: Pay attention to the following points. Or else, the switch will fail to be deployed. These points are also applicable to integrated hardware and software switch deployment. Be careful when you configure system configurations: Ensure that the entered Device Default Login User and Device Default Password are correct and can be used to log in to the switch. If the switch don’t use the Device Default Login User and Device Default Password in the global system configuration, create a non-global system configuration for the switch, and ensure the Device Default Login User and Device Default Password match with the switch. Ensure that the AmpCon-Campus server can connect with the License Portal through the entered License Portal URL, License Portal User, and License Portal Password. For more information, see Checking License Portal Connectivity. Ensure that the uploaded Security Config File and Parking Security Config File don’t contain wrong configurations or underlay/overlay related configurations. If you configure the DHCP server before adding a switch configuration, the switch will go to the AmpCon-Campus parking lot. For more information, see Managing the Parking Lot. To continue deploying the switches in the parking lot, follow these steps: a. In the AmpCon-Campus UI, click Device > Switches from the navigation bar. b. On the “Switches” page, click Parking Lot. c. Locate the switch to be deployed, and then click Create Config to add a switch configuration. After you add the switch configuration, the switch will be listed on the “Switches” page with the Configured status. d. Continue to provision the switch through ZTP to complete the switch deployment. Deploying an Integrated Hardware and Software Switch To onboard an integrated hardware and software switch by deploying it through ZTP, complete the following tasks: Table 11. Integrated Hardware and Software Switch Deployment Tasks and Links Category Task Reference Link System Configuration Click Wired > Wired Profiles from the navigation bar of the AmpCon-Campus UI. Click the System Configuration tab. In this tab, configure the global system configuration. If the global system configuration doesn’t match with the switch, create a non-global system configuration. Adding System Configurations Global Configuration Click the Global Configuration tab. In this tab, prepare the global configuration to be pushed to the switch. Configuring Global Configurations Configuration Template Click Wired > Config Templates from the navigation bar. Click the Template List tab. In this tab, check whether an existing configuration template meets your need. If not, click the New Template tab, and then add a new configuration template. Managing Configuration Templates Adding Configuration Templates Switch Configuration Click Wired > Wired Profiles from the navigation bar. Click the Switch Configuration tab. In this tab, add a switch configuration for the switch. Adding Switch Configurations DHCP Server Configure a DHCP server. If the DHCP server is not configured correctly, the switch deployment will fail. Configuring a DHCP Server Switch Provisioning through ZTP Provision the switch through ZTP to complete the switch deployment. Provisioning an Integrated Hardware and Software Switch What to Do Next After you onboard PicOS switches, check the following tasks. These tasks are not mandatory and can be used only when needed. Table 12. Post-Onboarding Tasks and Links Category Task Reference Link Deploying Wired Networks Deploy wired campus networks (fabrics) with PicOS switches. Wired Network Deployment Workflow Configuring PicOS Switches Use switch templates to satisfy general switch configuration through a full graphical interface. Switch Templates Use configuration templates to push specific configurations that can’t be pushed through switch templates. Configuration Templates Managing PicOS Switches Manage the lifecycle of PicOS switches to reduce the complexity and workload of switch management while improving efficiency: Check the switch inventory and telemetry data of each switch. Upgrade PicOS on a single switch or on multiple switches at scale. Use Returning Merchandise Authorization (RMA) to replace a switch with another switch of the same switch model. Decommission (DECOM) a deployed switch to clear the configurations pushed by AmpCon-Campus from the switch. Remove a switch from the AmpCon-Campus database and the AmpCon-Campus UI. Check or update PicOS licenses with the latest support entitlements. Managing Switches Managing PicOS Licenses Monitoring PicOS Switches Monitor PicOS switches as follows: Monitor metrics and topologies of PicOS switches. Monitor terminal devices connected to PicOS switches. Check alerts in the AmpCon-Campus UI. Receive real-time email notifications when alerts are triggered. Monitoring and Alerting Accessing Devices through SSH Sessions Connect to PicOS switches from the AmpCon-Campus UI by creating SSH sessions. Accessing Devices through SSH Sessions PicOS Switch Configuration Workflow AmpCon-Campus simplifies the whole switch configuration process through the template-based configuration model, and allows you to apply consistent and standardized configurations across switches in one or multiple sites, making the configuration process more efficient and streamlined. This guide provides a comprehensive overview of PicOS switch configuration procedures. Guidelines AmpCon-Campus supports two types of templates: switch templates and configuration templates. These two template types have different purposes: Table 13. Template Types Type Description Switch Template Used to satisfy general switch configurations through a full graphical interface. You can provide parameter values for each input field in a switch template and select the switches to be configured. The configurations mapping these parameters will be pushed to the selected PicOS switches automatically by AmpCon-Campus. Configuration Template Used to push specific configurations that can’t be pushed through switch templates. AmpCon-Campus provides pre-built CLI commands in a hierarchical way in the user interface. You can create configuration templates with different CLI commands. When pushing configurations to PicOS switches, select the configuration templates containing the required CLI commands, and select the switches to be configured. Then, these CLI commands will be run on the selected PicOS switches automatically. Prerequisites Before you configure PicOS switches, ensure that the following prerequisite tasks have been completed: Table 14. Prerequisite Tasks and Links Category Task Reference Link Platform Requirement Install the AmpCon-Campus server successfully. Platform Installation Workflow Log in to the AmpCon-Campus UI with an account of the SuperAdmin, Admin, or Operator role. Working with the User Interface Switch Requirement Onboard PicOS switches to bring them under AmpCon-Campus management. PicOS Switch Onboarding Workflow Ensure that the PicOS switches are up and connected to the AmpCon-Campus server. You can check the connectivity by clicking Wired > Switches from the navigation bar and viewing the VPN IP column of the PicOS tab: ✓: The switch is up and connected to the AmpCon-Campus server. x: The switch is down or not connected to the AmpCon-Campus server. No Reference Link Procedure To configure PicOS switches, check whether the required configurations can be pushed through switch templates first. If not, use configuration templates to achieve your goal. Table 15. Configuration Tasks and Links Category Task Reference Link Configuring through Switch Templates Click Network Design > Switch Templates from the navigation bar. On the “Switch Templates” page, configure switches through a full graphical interface. The workflow is as follows: Add a switch template. Specify the switches to be configured. Input configuration parameter values in the switch template as needed. Apply the switch template. Verify the template application result. Adding Switch Templates Configuring through Configuration Templates Click Wired > Config Templates from the navigation bar. In the New Template tab, create configuration templates with one or multiple required CLI commands. Click the Push Config tab. In this tab, create a configuration node, select the configuration templates containing the required CLI commands, enter variable values for the CLI commands, and select the switches to be configured. Verify the configuration pushing status and logs. Adding Configuration Templates Pushing Configurations to Switches Wireless Network Deployment Workflow AmpCon-Campus supports deploying and managing wireless networks and access points (APs), providing flexible and secure network deployment and management through enhanced wireless configuration, advanced radio frequency optimization, and robust management capabilities. This guide provides a comprehensive overview of wireless network deployment procedures. NOTE: The guide lists only the workflow of wireless network deployment. You need to check the reference links for detailed steps. Pay attention to the notes in each reference link. Or else, the deployment might fail. Prerequisites Before you configure a wireless network, ensure that the following prerequisite tasks have been completed: Table 16. Prerequisite Tasks and Links Category Task Reference Link Platform Requirement Install the AmpCon-Campus server successfully. Platform Installation Workflow Log in to the AmpCon-Campus UI with an account of the SuperAdmin role. Working with the User Interface Site Requirement Ensure that you have added the site where you will deploy the wireless network. Managing Sites AP Requirement Ensure that the APs to be added are supported by AmpCon-Campus. Supported APs for 2.3.0 IP Address Requirement Install a DHCP server, and configure the DHCP server to reserve an IP range for the APs to be added. No Reference Link Pre-configure the IP address of the AmpCon-Campus server by using one of the following ways: Configure DHCP Option 138 as the IP address of the AmpCon-Campus server. Add the IP address of the AmpCon-Campus server in the Redirector IP/URL field of each AP webpage. See the following DHCP Option 138 configuration example: image.png See the following AP webpage configuration example: image.png No Reference Link Network Requirement Ensure that the APs to be added are able to access the IP address of the AmpCon-Campus server. No Reference Link Procedure To deploy a wireless network, complete the following tasks: Table 17. Deployment Tasks and Links Category Task Reference Link Understanding Wireless Concepts and Highlights and AP ZTP Workflow Learn about wireless network related concepts, highlights of wireless network management, and the Zero-Touch Provisioning (ZTP) workflow of APs. Wireless Overview Concepts Adding APs to AmpCon-Campus Add APs to AmpCon-Campus one by one or import multiple APs in batches. Adding APs Adding SSID Configurations After adding APs to AmpCon-Campus, you must add SSID configurations for these APs. Adding SSID Configurations Optional Configurations On the “Wireless Profiles” page, configure some profiles, such as RADIUS servers, Multiple Pre-Shared Key (MPSK), Captive Portal, and the enabling time ranges for SSIDs or radio. Then, when you add SSID or radio configurations, you can use these pre-defined profiles. Adding Wireless Profiles AmpCon-Campus provides some default values for radio configurations. Check these default configuration values to see whether they meet your needs. If not, you must change the radio configurations as needed. NOTE Wireless regulatory requirements vary by country. Ensure that the country code in the radio configurations is consistent with the location of the AP. Adding Radio Configurations AmpCon-Campus provides some default values for advanced configurations. Check these default configuration values to see whether they meet your needs. If not, you must change the advanced configurations as needed. Adding Advanced Configurations Plugging In and Powering On APs Plug in and power on the added APs. Then, the ZTP process will start. Once completed, the wireless network is deployed, and the AP configurations will be pushed to the APs automatically. No Reference Link What to Do Next After you deploy a wireless network, check the following tasks for network monitoring and maintaining. These tasks are not mandatory and can be used only when needed. Table 18. Maintaining and Monitoring Tasks and Links Category Task Reference Link Maintaining Wireless Networks When an AP goes offline, has signal anomalies, or requires maintenance or replacement, you can remotely trigger its LED to blink, enabling quick on-site localization. Positioning APs You can reboot one AP or all the APs in a site. Rebooting APs After a wireless network is deployed, you can edit configurations of each AP in the wireless network. Editing Configurations of an AP After a wireless network is deployed, you might need to edit configurations of an AP or update SSID, radio, or advanced configurations of a site. In these cases, you must manually push configurations to APs. Pushing Configurations to APs You can upgrade AP firmware one by one or in batches. In addition, you can upgrade AP firmware immediately or at a scheduled date and time. Upgrading AP Firmware You can capture remote packets from target ports of APs for rapid troubleshooting. Capturing Remote Port Packets You can optimize wireless networks immediately or at a fixed time. You can also customize network optimization configurations. Optimizing Wireless Networks You can restore managed APs to factory settings. Restoring to Factory Settings You can export APs to a .csv file, delete APs, or move APs from one site to another. Exporting, Deleting, and Moving APs You can connect to an AP from the AmpCon-Campus UI through remote TTY shell (RTTY). Accessing APs If some issues can be resolved only through CLI configurations or some advanced functions can be achieved only through CLI configurations, you can contact FS support engineers to do AP debugging or configuration for you through this feature. Advanced CLI Configurations Monitoring Wireless Networks Click Dashboard > Wireless View from the navigation bar. On the “Wireless View” page, you can have a quick understanding of deployed wireless networks, such as managed APs, AP health status, and connected Stations (STAs). Wireless View Click Wireless > Access Points from the navigation bar. On the “Access Points” page, you can check detailed metrics of each managed AP. Monitoring APs Click Monitor > Wireless Clients from the navigation bar. On the “Wireless Clients” page, you can monitor STAs connected to each managed AP. Monitoring STAs Click Wireless > Manage from the navigation bar. In the Monitor tab, you can monitor the overall running status of each wireless site. Monitoring Wireless Sites Wired Network Deployment Workflow AmpCon-Campus offers flexible wired campus network (fabric) deployment to meet different networking requirements. You can design and deploy MLAG fabrics for small or mid-size campus networks or IP Clos fabrics for large-scale campus networks, eliminating complex networking configurations and enhancing deployment efficiency. This guide provides a comprehensive overview of wired network deployment procedures. NOTE: The guide lists only the workflow of wired network deployment. You need to check the reference links for detailed steps. Pay attention to the notes in each reference link. Or else, the deployment might fail. Prerequisites Before you deploy a wired campus network, ensure that the following prerequisite tasks have been completed: Table 19. Prerequisite Tasks and Links Category Task Reference Link Platform Requirement Install the AmpCon-Campus server successfully. Platform Installation Workflow Log in to the AmpCon-Campus UI with an account of the SuperAdmin role. Working with the User Interface Network Requirement Ensure that the PicOS switches are able to connect to the AmpCon-Campus server. No Reference Link If a firewall is configured between the AmpCon-Campus server and the PicOS switches, allow outbound access on the following ports to the management port of each switch. TCP: 22 TCP: 9339 TCP: 830 No Reference Link Switch Onboarding Ensure that the PicOS switches used for wired network deployment are supported for campus fabrics. Supported Switches for Campus Fabrics Ensure that the PicOS switches retain only basic routing configurations, without any other service configurations. No Reference Link For switches that have PicOS installed, ensure that the Secure Shell (SSH) protocol is enabled on these switches. SSH is enabled on PicOS switches by default. No Reference Link Create a site in the AmpCon-Campus UI, and add the PicOS switches to the site. Managing Sites Onboard PicOS switches to bring them under AmpCon-Campus management. Once successfully onboarded, the PicOS switches are classified as managed devices and can be used to deploy wired networks. PicOS Switch Onboarding Workflow Ensure that the PicOS switches are up and connected to the AmpCon-Campus server. You can check the connectivity by clicking Wired > Switches from the navigation bar and viewing the VPN IP column of the PicOS tab: ✓: The switch is up and connected to the AmpCon-Campus server. x: The switch is down or not connected to the AmpCon-Campus server. No Reference Link Procedure To design and deploy a wired campus network, complete the following tasks: Table 20. Fabric Deployment Tasks and Links Category Task Reference Link Understanding MLAG Fabrics and IP Clos Fabrics Understand the use cases, components, and architecture of MLAG fabrics and IP Clos fabrics. Fabric Overview Understanding Key Concepts Understand the concepts related to campus fabrics. Key Concepts Deploying MLAG Fabrics Design a two-layer MLAG fabric for small or mid-size campus networking. Designing MLAG Fabrics Deploying IP Clos Fabrics Design a 5-stage IP Clos fabric for large-scale campus networking. Designing IP Clos Fabrics Provisioning Overlay Services After you deploy an IP Clos fabric, if overlay configurations (VRF, VNI, and DHCP relay configurations) for the IP Clos fabric need to be changed, you can quickly modify these configurations on the “Overlay Service Activation” page. Provisioning Overlay Services Ansible Automation Workflow Ansible is an open-source tool to automate configuration management, application deployment, and task automation. Ansible uses the simple, declarative language written in YAML, which is called playbook, to automate your tasks. By using AmpCon-Campus, you can write, run, and schedule Ansible playbooks on managed PicOS switches and added Linux servers, reducing manual work, eliminating configuration errors, and improving network management efficiency. This guide provides a comprehensive overview of Ansible playbook running procedures. Prerequisites Before you run Ansible playbooks for automation, ensure that the following prerequisite tasks have been completed: Table 21. Prerequisite Tasks and Links Category Task Reference Link Platform Requirement Install the AmpCon-Campus server successfully. Platform Installation Workflow Log in to the AmpCon-Campus UI with an account of the SuperAdmin, Admin, or Operator role. Working with the User Interface Switch Requirement (Applicable only for running playbooks on PicOS switches) Ensure that each PicOS switch to run Ansible playbooks has been onboarded to AmpCon-Campus. PicOS Switch Onboarding Workflow Ensure that the Device Default Login User and Device Default Password in the global system configuration can be used to log in to the PicOS switches. NOTE: If the default username and password of a switch don’t match the Device Default Login User and Device Default Password specified in the global system configuration, the playbook will fail to be run on the switch. Adding a Global System Configuration Ensure that the PicOS switches are up and connected to the AmpCon-Campus server. You can check the connectivity by clicking Wired > Switches from the navigation bar and viewing the VPN IP column of the PicOS tab: ✓: The switch is up and connected to the AmpCon-Campus server. x: The switch is down or not connected to the AmpCon-Campus server. No Reference Link Linux Server Requirement (Applicable only for running playbooks on Linux servers) Ensure that the Linux servers have been added to AmpCon-Campus. Adding Other Devices Procedure To run an Ansible playbook with AmpCon-Campus, complete the following tasks: Table 22. Playbook Running Tasks and Links Category Task Reference Link Checking Pre-Built Playbooks AmpCon-Campus offers a series of pre-built Ansible playbooks. Click Maintain > Automation > Playbooks. On the “Playbooks” page, click the Show Pre-built Playbooks toggle. Check whether these pre-built Ansible playbooks meet your needs. If yes, click Save AS on the “Playbooks” page to create a copy playbook, and then run the playbook. No Reference Link Writing or Importing Playbooks If the pre-built Ansible playbooks don’t meet your needs, write or import a playbook on the “Playbooks” page as follows: Click + Playbook, and then write a playbook in the AmpCon-Campus UI. Click Import, and then import a local playbook to AmpCon-Campus. Examples for Ansible Playbooks Using Ansible playbooks Writing a Playbook on AmpCon-Campus Importing a Playbook Checking Playbook Syntax Before you run a playbook, check whether the playbook syntax is valid. On the “Playbooks” page, locate a playbook, and then click Check. No Reference Link Running Playbooks On the “Playbooks” page, locate the playbook, and then click Run to complete the automation operation. Running a Playbook Checking Ansible Job Results and Output An Ansible job is a single execution of an Ansible playbook. Click Maintain > Automation > Ansible Jobs from the navigation bar. On the “Ansible Jobs” page, check the playbook execution result and output. Managing Ansible Jobs What to Do Next After you run an Ansible playbook, check the following tasks. These tasks are not mandatory and can be used only when needed. Table 23. Post-Running Tasks and Links Category Task Reference Link Viewing Playbook Scheduling View executed playbooks based on months, weeks, or days. Viewing Playbook Scheduling Troubleshooting for Failed Ansible Jobs If a playbook fails to be run on PicOS switches or Linux servers, check the possible reasons and solutions for troubleshooting. Troubleshooting