| The AP did not receive a valid IP address via the DHCP. |
Be sure that the DHCP server is on and available on the VLAN/subnet connected to the AP. If the AP fails to get a valid IP address, you can reboot it to see if that resolves the problem. |
| Unable to connect to the server. |
- Be sure you have an active server and reachable from the network connected to the AP. If a firewall or a router has Access Control Lists (ACLs) enabled between the AP and the server, allow traffic on UDP port 3851.
- Use the IP-based server discovery method and be sure you have correctly entered the DNS name, wifi-security-server , on the DNS server.
- Be sure the DNS server has correctly configured IP addressesor provided by the DHCP server.
- The AP might fail to authenticate with the server. In this case, an 'Authentication failed ' event logs to the server. Refer to the event for recommended action.
|
| The AP has encountered a problem. |
- If using Arista Cloud Services, then open the TCP port 443 (SSL). If you have an on-premises installation, then open UDP port 3851 and TCP 443.
- If using a Proxy, Web Accelerator, or URL Content Filter between the AP and the Internet, ensure that the settings allow communication between the AP and Arista Cloud Services. For more information, see Wi-Fi Access Points Server Communication Workflow.
- If your configuration requires you to specify an exact IP address or IP range for Arista Cloud Services, please contact This email address is being protected from spambots. You need JavaScript enabled to view it.
|
