This document focuses on the basic prerequisites and minimum configuration required for configuring an Arista device as an AP.
- Administrative access to the Wireless Manager UI.
- Access Point should be connected to the network and also active on the Wireless Manger.
If you do not see the Access Point active on the server, please refer to Troubleshoot AP Server connectivity.
The Arista AP does not have a UI of its own, so it must be configured via Wireless Manager.
There are two aspects that control the configuration of an AP via Wireless Manager.
- SSID Profile
- Device Template
Setting up Location and Device Presence
Configuration is also dependent on the location of the device within Wireless Manager. Location can be configured and managed through the Location Tree. For this example, we will create a new location.
Note: You can choose to configure the SSID profile and Device Template at the Root location as well.
All new devices will be tagged to the Staging Area (or “Unknown”) location, and you can move the device from there to the preferred location.
Note: Changing the location (if you do not retain the template) or Device Template always reboots the device.
Setting up an SSID Profile
We choose to set up an SSID profile as a device usually has a default Device Template assigned, so we can consider it as the next step.
SSID profile will control all aspects of the SSID that is shown to the end user or device like , Name of the SSID, Security Type, Captive portal settings, VLANs and network settings, etc.
Navigate to Configuration → Device Configuration → SSID Profiles to create an SSID profile using “Add New WiFi Profile”.
A window is displayed which allows the admin to configure the required settings. In this example, we will add minimal settings for an operational corporate SSID, as seen in the screenshot.
The result would look like this:
Setting up the Device Template
By default, the System template is applied to the device, which does not have any specific configuration assigned to it. This can be modified, but it is a better practice to create a new Device Template for use.
Navigate to Configuration → Device Configuration → Device Templates and click “Add Device Template”.
Note: In this example , we are using a new location so an option to break inheritance and customize is displayed. If you perform the same configuration at the root or parent location, this will not be shown.
Device Template controls all configuration assigned to the device. Besides the SSID profiles applied to the radio, it also controls management features like device password, syslog, NTP, etc. While creating the template, remember to select the correct “Operating Region”. We will use minimal settings to complete the Device Template, as shown in the screenshot below:
While this configuration is enough to Save the template, we intend to add an SSID, so an additional configuration is to apply the SSID profile previously created to the template as shown in the next screenshots. You can choose to apply it to one radio or both.
Click Save to complete the configuration.
Unless this new template is marked as the Default for the location, it will not be applied to devices at this location. We will set the new Device Template to be the default so that we can use it for all devices at this location in the future.
From Monitoring → Managed Devices, we can verify if the template was applied correctly.
Click on the device name to view its properties in the first widget.
Other Important Configuration
Within the SSID profile settings, the VLAN specifies the VLAN to which the end user traffic will be bridged. VLAN ID zero means it is Untagged.
Captive portal can be used to authenticate users or engage with users who access your WiFi. It is especially useful for guest WiFi access and can also be used to gather user analytics. On the cloud, Captive Portals can be created via the Guest Manager service.
Refer to the Wireless Manager user guide or access the Help section to know more about the captive portal configuration.