I have a Cisco WAP321 with 2 SSID's (Called SSID A and SSID B) on the same VLAN (vlan id 1)
The Cisco Wap is connected to a Cisco SG-300 SBS switch with a Linksys N300 as Router device and DHCP server
When i boot up the WAP and a device is connected to the SSID A the device retrieves an ip adres from the N300. Another device creates a connection with SSID B and retrieves also a DHCP adres from the N300.
After a few days, all the devices which has a connection width SSID B, hung on Waiting for IP. The same devices will able to connect with SSID A, but when the same device wil setup a connection with SSID B, the same message appeas: Waiting for IP.
When i give the WAP a soft reset, all the devices are able to setup a connection with SSID B and retrieves an IP from the DHCP server (N300). But after af few days the same problem returns.
Special thanks to Alex McDonald for sharing his favorite tip:My favorite
tip is the ‘write default’ command on autonomous wireless access points,
it simplifies manual conversion of a WAP with a static ip address to a
LAP with a DHCP address.This saved a l...
With the latest release of firmware for the WAP 561, 551, 371, 351 a new
feature was added that would allow customers to upgrade the firmware for
their clustered access points from the main access point.The basic steps
to accomplish this is:1) Download th...