Cisco Wireless :: AP 1310 Not Able To Join Controller
May 20, 2013
i converted the C1310 to LAP using upgrade tool. but the AP is not able to join the controller i was not able to view SHA Key in upgrade tool, so i ran the "debug pm pki enable " on the controler to get it. i'm still not able to view SHA key.
here is the output of debug command
*spamApTask0: May 21 15:07:43.527: 88:43:e1:d1:fc:9e Received LWAPP JOIN REQUEST from AP 88:43:e1:d1:fc:9e to cc:ef:48:b3:23:ef on port '13'
*spamApTask0: May 21 15:07:43.549: sshpmGetIssuerHandles: locking ca cert table
I have an (AIR-LAP1310G-E-K9R) and I tried to join it to WLC 5508 but I'm facing an error, I get this error from the LAP 1310 console as below:
Compiled Mon 17-Jul-06 11:45 by alnguyen *Mar 1 00:00:05.289: %LINK-3-UPDOWN: Interface FastEthernet0, changed state to up *Mar 1 00:00:06.289: %LINEPROTO-5-UPDOWN: Line protocol on Interface
I have Cisco 5508 WLAN controller v7.4 and i have lap 1310 and it is not joining to this lan controller. What to do? How to join this lap to this lan controller? or how to convert it to autonomous because i dont find mode button on this access point?
I have 2 campuses. I have my 5508 wireless controller working beautifully on my main campus using LDAP. (YAY!!) Now for my problem. My remote campus has 1310 bridges. I was able to successfully upgrade one of them to work with the controller, however, I can't get the other two bridges to talk to the one that I upgraded and I can't get them to upgrade, it indicates that they need to be the root. I have several small buildings on that remote campus, than need that remote bridging in order to be able to have network access.
When we were installing some new APs, were plugged in to ports that were not configured on the WLC management VLAN.
This is the illustration
WLC management VLAN is VLAN 80 Management VLAN of infrastructure (Switches routers) is VLAN 10
The APs were plugged in to VLAN 10 and they were not able to associate themselves with the controllers.
Through research, those APs were getting a wrong IP address,
I did the Mode button, pressed for 30 secs, but this did not fix the problem, i thought it was going to clean the flash and bring the AP back to factory default I do not believe this happened.
We also added the cisco-capwap-controller.localdomain to our DNS servers, and then I rebotted the APs and still no luck.
What fixed the issue is we had to go to the DHCP server, release the IP addresses and we found those based on the macs of the APs. What is we do not have the mac addresses?
Now that I have the DNS entry created, if I plug in an AP on the wrong VLAN port will I be able to see it?
I am trying to get one AP to join the 2106 controller, it did join once then never again!! Now all I get is: *Jan 22 11:16:22.088: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to administratively down
When I check the AP join statistics I see the following: Reason For Last Unsuccessful Attempt RADIUS authorization is pending for the AP, I don't run a radius server and don't know how to get around this so that the device can join.
This is a new setup and has not worked yet. I have multiple 3602 APs and one 2504 Controller. I thought initially I could plug-in an AP into one of two POE Ports on the 2504. During debug mode I see that it has low power, was suprised that the 2504 switch can't fully power the AP? Is this correct?Anyways I have another POE switch that I am using with ample power. The configuration for my wireless is that it will be completely segmented off of my internal network as this is for guest access. So DNS servers are external so I cannot create host entries for the AP to discover the controller. With that being said I believe that is just one way for the discovery process to happen. I have my controller management interface and DHCP scope on the controller on the same subnet plugged into the same POE switch. The AP does seem to get a DHCP address and I can ping the controller from the AP. I cannot get any further then that. I will not join the controller and the radios get disabled. I get messages such as "discovery response from MWAR is rejected. I will post a debug log of the AP and its bootup process. This is new equipment so I would assume the firmware is somewhat up-to-date and the 3602 AP is somewhat the latest model.
1) AP was originally running a standalone image. I booted it into a so-called ROMMON or AP mode (ESC is the right key to make it boot into this mode).
I found a recovery image in its flash - c1140-rcvk9w8-mx. I made the AP boot from it by using "set" command and I see that it start booting using this recovery image. Here goes the question. Do all AP settings matter ? E.g. when I run "set" command from AP I see the following:
ap: set ?= DEFAULT_ROUTER=10.0.0.1 Default_router=10.9.99.1 ENABLE_BREAK=yes
my access point 1230 fail to join the controller. The image is C1200-k9w7-mx.123-8.JA2. I tried to reboot it but it does not join to controller. How do I initiate the discovery process again to make this AP to join? Should I convert it back to autonomous AP and then LWAPP process again? I can ping the AP from the controller and the AP is in the same VLAN with controller.
Iam having trouble to conect my 1121-AG AP`s to my 4404 WLC.
My WLC version is 7.0.116.0.
I can see he AP is getting an IP address from the controller(internal DHCP). But from some reason they can`t connect to the WLC. I have tried many things such as:
1)reset to default settings
2) move the AP to Autonumos mode and back to LWAPP mode -- didnt work.
I try to configure an AP1131 as OfficeExtend but unfortunately I receive the following message from the debug command on the WLC5508: (Cisco Controller)
*spamApTask4: Oct 04 17:19:18.043: 00:1b:90:74:37:e0 Discovery Request from XX.XX.XX.XX:14847 *spamApTask4: Oct 04 17:19:18.043: 00:1b:90:74:37:e0 Join Priority Processing status =
we have WLC 4400, we have 40 APs with model no. AIR-LAP1131AG-N-K9 but we recenlty got an AP with model no. AIR-LAP1131AG-E-K9 which is unable to join WLC.
we are running 5500-series WLC and AIR-LAP1131 and AIR-CAP3502 APs. Now we are trying to have new 1600-series AP's working with 5500WLCs. How to get this combo working.
WLC is running 7.4.100 sw version, and AP will join to controller but it won´t work.[code] I can´t find any kinf off document about invalid event 10 & state 5 combination erros message.
I'm trying to use 1142 APs with a 2504 Wireless Controller through a D-Link 48PT GBIT XSTACK SWITCH (DLI-DGS-3120-48PC/SI).At any rate, the 1142 AP joins with the wireless controller ONLY when I attach it directly to the controller. When connected directly to the controller the AP functions normally and all is well. When I attach it through the D-Link switch, the AP flashs green several times, indicating that it can't find the controller. I suspect that there's some setting on the D-Link switch that's preventing the AP from seeing the controller.
I am not able to join 1042 wireless AP with 2106 controller, even i mention that controller ip is 192.168.200.5 it try to join with controller on 192.168.200.6 ip address always. following are the error logs i can see on console.
*Nov 30 19:50:20.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 192.168.200.6 peer_port: 5246 *Nov 30 19:50:20.001: %CAPWAP-5-CHANGED: CAPWAP changed state to *Nov 30 19:50:21.435: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 192.168.200.6 peer_port: 5246 *Nov 30 19:50:21.436: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.200.6 *Nov 30 19:50:21.436: %CAPWAP-5-CHANGED: CAPWAP changed state to JOIN
We have two controllers 7510 with the same config (SSID, Mobility Groups, etc)... All APs now was joined in wlc01... If we try to one o more APs join to another controller.. it's is not possible and debug show this . [code]
i have configured cisco LAP1240 in H-Reap Mode for multiple branch offices with Local switching and central authentication. one of the branch's AP does not join the controller in HQ while the others are all ok. i have firewall only in HQ, i did priming first for all APs like let them join the controller and configure controller IP in high availbility, and H-Reap config and assign SSID to map with the branch local vlan. when i faced this issue first time i brought back ap and configure a static IP address for AP than recheck them again but the problem still same. since i have only one firewall in the network and also other branches joined the controller through that firewall and no issues.
*Mar 1 01:28:21.018: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY *Mar 1 01:28:21.022: %LWAPP-3-CLIENTERRORLOG: bsnSetCurrentBHRate : fail to set radio control and data rate
*Mar 1 01:28:21.179: %CDP_PD-2-POWER_LOW: All radios disabled - AC_ADAPTOR (00 00.0000.0000) *Mar 1 01:28:21.984: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEth ernet0, changed state to up *Mar 1 01:28:34.341: %DHCP-6-ADDRESS_ASSIGN: Interface GigabitEthernet0 assigne d DHCP address 192.168.10.244, mask 255.255.255.0, hostname AP2c54.2d0d.c3c4
I try to join an ACS v. 5.3 to the domain. For my acs in Location A, I can join without problems using my account. When I try to join the ACS in location B to the same domain with the same account, it doesnt work.I looked at the debug log files for the ad client, and noticed, that the ACS in location B goes to a certain Domain Controller. However, I would have expected the ACS to contact another DC, which is located on the same location as the ACS ... this doesnt happen.
My question: How does the ACS determine what DC to contact ? Is it possible to force the AC to join by connecting a certain DC ?
I am trying to setup a wireless link between two locations, and be able to pass VLANs through the Wireless link.Currently I have two 1310 bridges.I followed the information at url..., but it is only passing VLAN 1 across the link. I cannot figure what the problem is.Both Bridges are running c1310-k9w7-mx.123-8.JEA3. [code]
Is it possible to make a bridge using a 1242 and a 1310? I have been able to get them to associate together and it appears it will function as a bridge. I have the 12(4) 253 JA IOS for both devices. I would like to use the g antenna on the 1242 for the bridge and the a antenna for wireless clients. The configuration on the web management appears to support bridge root and non root for both devices.
I have an access point 1310. I want to add to the WLC as an access point. It have been configured with IP address correctly and the radio interface is up. I need to add it to the WLC as CAPWAP.
I've got a Cisco Aironet LAP1310AG-A-K9 that I can't access through Internet Explorer or Firefox (multiple versions). I set a static IP in DHCP, I can ping the unit, but I can't browse to the GUI.
I know that the 3600 series APs are not supported on the 4404 WLC. However, would the following scenario be supported? I would like to use the 4404 (software rel. 7.0) as a guest anchor with a 5508 (software release 7.2) as the foreign controller supporting series 3600 APs. I ask because the APs do not need to join the guest anchor.
We have a customer that have 2 5508 as primary and backup controller and a 4400 as an anchor controller. We plan to upgrade the 5508 to 7.3.112.0 and the 4400 is already 7.0.116.0. Will there be any issue if the anchor controller is not the same code as the foreign controller? Do I also have to upgrade the acnhor controller to 7.0.240.0?
