| the AP did not receive a valid IP address via the DHCP. |
Be sure you have an active DHCP server on the VLAN/subnet with the connected AP. If the AP fails to get a valid IP address, reboot it to see if that resolves the problem. |
| Unable to connect to the server. |
- Be sure you have an active server reachable from the network with the connected AP. If a firewall or a router has access Control Lists (ACLs) enabled between the AP and the server, be sure to 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 that the DNS server has correctly configured IP addresses or the DHCP server provides the IP addresses.
- 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 you use Arista Cloud Services, open the TCP port 443 (SSL). If you have an on-premises installation, then open UDP port 3851 and port 80.
- If you use 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.
- 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..
|
