By increased overhead I meant increased wi-fi system administration time if you are not using a controller. But this certainly doesn't apply in your case where you only have 2 access points so I consider option 1 is the best for you.    Even a Cisco reseller needs a valid smartnet/service contract to download the software from cisco.com. Your best work around is to get a smartnet contract for one of your devices then follow the procedure that Scott gave you. A Cisco TAC engineer can also walk you through the process once you have the service contract either by phone or using webex. You can get the service contract for like 25 bucks.     ... View more

Warrior if i get you correctly, you are saying you want to broadcast same SSID across multiple access points. You can achieve that goal using any of the 2 scenarios below:   You can run your access points as standalone devices - notable advantage is to cut costs by not including the controller - notable disadvantage is increased overhead since you have to replicate configs across all APs whenever there is change   You can run your access points as light weight devices in a controller based architecture - notable advantage is central management of the system, everything is done on the controller. - I wouldn't see controller cost as a disadvantage because in some cases controllers costs just the same as one AP depending on the number of APs you want to deploy.   To download software from Cisco.com you need a valid Smartnet contract. The Smartnet contract also gives you access to 24hr technical assistance centre who can also help resolve your issue.   Please rate useful posts ... View more

Hi Leo, I have tried this specific AP on different switches including switch ports where other APs are working fine. It's just this specific one that is misbehaving. With that I would like to believe this has nothing to do with the switch. Tell me if I am right ... View more

Hi Guys, AP:                     2602i Controller:                     2504 APs using DHCP to acquire addresses APs using power adapters (no PoE) AP in same LAN as controller In the event that there has been Flash system file failure what is the possible remedy? Also what is and how do we check TDR? I haven't managed to get console output but will post it as soon as I get it. \\Kelvin ... View more

Hi Scott, I figured out what the real course of my problems where? My WLC was running software version 7.0.x.x which doesn't support the newer 2600 LAPs. On upgrading to 7.4 the problem was fixed. Now my LAPs can easily join the WLC. ... View more

At the time of the debug the ip address of the AP was 10.131.201.115. However this keeps changing not to sure why (thinking it keeps getting new addresses from the DHCP). My setup is simple as shown in network diagram in my previous reply. WLC and LAP connected to the same switch and there are no vlans configured. Router being used as a DHCP server. No firewall or ACLs configured. Any more debugs I need to run? From the debugs I can see that the AP is sending 'discovery requests' to the WLC and the WLC is responding with the 'discovery response'. Instead of going back to the next level the the process recycles with the AP sending another 'discovery request' again. Any reason why we wont go past this stage? ... View more

My setup is as shown in the figure below. From the results below would you be able to tell where the problem is? I have run 3 debugs which are given below: (1). debug capwap event enable Aug 29 10:38:23.205: 44:03:a7:a0:f6:80 Discovery Request from 10.131.201.115:3946 Aug 29 10:38:23.205: 44:03:a7:a0:f6:80 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 5, joined Aps =0 Aug 29 10:38:23.205: 44:03:a7:a0:f6:80 Discovery Response sent to 10.131.201.115:3946 Aug 29 10:38:39.202: 44:03:a7:a0:f6:80 Discovery Request from 10.131.201.115:3946 Aug 29 10:38:39.203: 44:03:a7:a0:f6:80 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 5, joined Aps =0 Aug 29 10:38:39.203: 44:03:a7:a0:f6:80 Discovery Response sent to 10.131.201.115:3946 Aug 29 10:38:39.203: 44:03:a7:a0:f6:80 Discovery Request from 10.131.201.115:3946 Aug 29 10:38:39.203: 44:03:a7:a0:f6:80 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 5, joined Aps =0 Aug 29 10:38:39.203: 44:03:a7:a0:f6:80 Discovery Response sent to 10.131.201.115:3946 Aug 29 10:38:39.203: 44:03:a7:a0:f6:83 Received LWAPP DISCOVERY REQUEST to f0:29:29:89:99:e0 on port '1' Aug 29 10:38:39.203: 44:03:a7:a0:f6:83 Discarding discovery request in LWAPP from AP supporting CAPWAP (2). debug pm pki enable (Cisco Controller) >debug pm pki enable (Cisco Controller) >*sshpmLscTask: Aug 28 11:20:09.116: sshpmLscTask: LSC Task received a message 4 *sshpmLscTask: Aug 28 11:22:09.116: sshpmLscTask: LSC Task received a message 4 *** IDLE TIMEOUT *** (3). test capwap controller ip 10.131.201.162 AP4403.a7a0.f683#test capwap controller ip 10.131.201.162 AP4403.a7a0.f683# Not in Bound state. *Mar  1 00:25:25.103: %CAPWAP-3-DHCP_RENEW: Could not discover WLC using DHCP IP. Renewing DHCP IP. *Mar  1 00:25:30.223: %DHCP-6-ADDRESS_ASSIGN: Interface BVI1 assigned DHCP address 10.131.201.20, mask 255.255.255.0, hostname AP4403.a7a0.f683 Translating "CISCO-CAPWAP-CONTROLLER"...domain server (255.255.255.255) Not in Bound state. *Mar  1 00:26:56.603: %CAPWAP-3-DHCP_RENEW: Could not discover WLC using DHCP IP. Renewing DHCP IP. *Mar  1 00:27:01.723: %DHCP-6-ADDRESS_ASSIGN: Interface BVI1 assigned DHCP address 10.131.201.21, mask 255.255.255.0, hostname AP4403.a7a0.f683 Translating "CISCO-CAPWAP-CONTROLLER"...domain server (255.255.255.255) ... View more