They see the controller, it downloads the software but then on reboot I get these errors:
LWAPP_CLIENT_ERROR_DEBUG: spamHandleJoinTimer: Did not rec
ieve the Join response
*Mar 1 00:00:58.622: LWAPP_CLIENT_ERROR_DEBUG: No more AP manager IP addresses
*Mar 1 00:00:58.655: %SYS-5-RELOAD: Reload requested by LWAPP CLIENT. Reload Re
ason: DID NOT GET JOIN RESPONSE.
I cannot ping the ip address of the ap-management port, maybe I'm not supposed to. This is hooked into a 4506 core switch and I have it set to Dynamic Auto on the port. At one point I could get the AP's that were connected to the 4506 to stay associated but not the ones outside the switch.
What are you consoled into to configure the controller? What model controller do you have?
Well it looks like you have things setup wrong. This is what I would do first. Work on one controller at a time. Take off the second controller.
1) You need to have the management and ap-manager on the same subnet and vlan tagged as '0' not as what vlan they are on.
2) They will be 802.1q trunk on the switch with native vlan (whatever your management vlan is)
3) Configure the controller for layer 3
4) Configure DHCP on the switch so that the ap's get an IP
ip dhcp excluded-address 10.100.6.1 10.100.6.50
ip dhcp pool AP_Staging
network 10.100.6.0 255.255.255.0
option 60 ascii "Cisco AP c1130"
option 43 ascii "IP address of the management interface"
5) Configure the service port to an ip address that is not on any subnet and don't plug thi into your network. Use a 192.168.x.x or just 22.214.171.124. Service port has to be configured if you have a WiSM!
6) When ou create an ssid in the WLAN, make sure you identify which interface the ssid will be mapped to, or else it will be on the subnet your management interface is on.
7) On the interface you created for the ssid, that is where you specify the DHCP address for that interface.
Then let me know how things are after that, because there is more!