For some reason some AP will not join the WLC. (WISMII)I have several hundrede AP online, but still a few offline
This fails:
FRH-R06-L226-UX-G#sh cdp nei gi2/0/41 detail
-------------------------
Device ID: AP5057.a8a1.c632
Entry address(es):
[Code]...
a Customer ask me to configure a etherchannel between two Switches C3500 XL Version IOS 12.0 follow the first configuration what I done and the output error show me by switch:
Sw01(conf)# interface port-channel 1 % invalid input detected at '^' marker.
I have to do something before add an new port-channel interface ?? why the Sw01 does not accept my configuration ?
Customer has got a 2 x 1552AP that wont join a WLC.
This is the debugs from the WLC. Customer cant console to AP to capture as its up in the roof so not easily accessible. why the AP wont join? Date/Time are fine on the WLC as is the region.
*spamReceiveTask: Jun 28 13:45:26.612: 2c:3f:38:be:23:c0 DTLS connection not found, creating new connection for 172:16:2:1 (57918) 172:16:0:1 (5246)
*spamReceiveTask: Jun 28 13:45:27.243: 2c:3f:38:be:23:c0 DTLS Session established server (172.16.0.1:5246), client (172.16.2.1:57918)
[Code]....
There are a total of 25 Cisco 3502 APs installed. 24 APs were discovered except for 1 AP. I run SH CDP NE on the switch and the AP was discovered by the switch but it does not have an IP address. On the output of the SH CDP NE DE, I noticed that on the AP that is not joining, the Platform is "cisco AIR-SAP3502E-E-K9" while the APs that joined the WLC, the Platform is "cisco AIR-CAP3502E-E-K9". The software versions are also different but this could be because the WLC already upgraded the IOS when the APs joined.Why is the Platform "SAP3502E" for the AP that did not join.
View 9 Replies View RelatedI had problems joining a 1131AG AP to a "new" 5508 WLC with 7.4.100.0 running. This AP has been connected to a, for me unknown controller for years. Now the customer wants to move this AP to a newer 5508 controller with 7.4.100.0 We [URL] could not get this AP to the controller connected. Now I have this AP on my desk. I have a 5508 (7.4.100.0) as well. I connected the AP to the same network as the WLC Management -> AP did not connect, tried to download the "new" IOS but didn't seem to work, same as already in the old tread. So I tried to login to the AP, but it seemed to have a for me unknown Account / Password.
-> I did a reset of the AP by pressing the mode button (about 2-3 sec.) during Power on (not connected to the network). Now I could log on to the AP. I deleted six crashinfos and connected the AP back to the network.
Now the AP joined the controller.
Does a "unknown" Password prevent the AP to join to a other WLC?
The AP hat 15740928 bytes total (6409728 bytes free) space on the Flash: was this enough for the new image? 15740928 bytes total (7798272 bytes free) after deleting the crashinfos
The customer has more AP's that has to join the new controller, would be nice that we don't have to reset all APs.
After a wireless network interruption, one of MAP 1522 it's not joining to WLC .
(Cisco Controller) >show ap join stats detailed 00:08:30:bb:53:20
Discovery phase statistics
- Discovery requests received.............................. 7
- Successful discovery responses sent...................... 5
[Code]....
We've just replaced some 1240 LAPs with 20 x 3502i.
Seem to have a problem, most of the 14 * 3502i have regersted on the network and working, 6 arent connecting and log below. I've replaced one of the AP with a differnt one, same model and batch and this works.
WISMs on 7.0.98.0
Scirpt
*Mar 1 00:15:16.015: %CAPWAP-5-CHANGED: CAPWAP changed state to
[Code].....
My customer has an 1131AG AP, andhas Problems with joining to the controller. I did a debug and have the following output. The WLC (5508) shows the AP with Primary SW version as 3.0.51.0. this Release does not showup in any compat matrix! It seems to start downloading the software. after a while it stops with the bolded output, twice the same Bytecount!?
*spamApTask0: Apr 03 09:55:59.998: 68:ef:bd:94:e7:9c 5179392 Bytes Transferred to AP 68:ef:bd:94:e7:9c
*spamApTask0: Apr 03 09:56:00.097: 68:ef:bd:94:e7:9c Received LWAPP
[Code].....
i have 1240 series access points which is not joining controller 5500 series. [code]
View 12 Replies View Relatedinfo regarding my LAP521 access points that are refusing to join the WLC4402-12.This is my first lightweight access point implementation and I have 3 LAP521's and 1 AIR-CAP3502I-E-K9 access points on my network.They are meant to pick up ip address from external dhcp server and then join the WLC but only the 3502i joins successfuly while the 521's get dhcp address but do not join the WLC. From the logs, I can see that the WLC is discovered by the 521's and even get a response message from the controller but they are still unable to join as shown in the screenshot below.My WLC is running software version 7.0.230.0 and the 521's are running an lwapp image version 4.2.61.8. [code]
View 3 Replies View RelatedI am trying to join my 1130AG-E-K9 AP to my 2016 WLC, but it is stuck in a boot loop and will not connect to the controller. [code] I found some details here: url... but I'm not sure what it means that I have a 'SSC AP'. I am not local to this AP, though I do have a console connection to it-what do I need to do to get it working again? It just continually goes through this error and reboots every 30 seconds or so, so it's useless at the moment.
View 3 Replies View RelatedI am performing a new install of a WLC 5760 and 3602i APs. I have limited experience in setting up WLCs. I am hitting a brick wall in getting the AP to join my WLC. My primary document has been this deployment guide:url...I have also sifted through many of the relevant portions of these guides: url...
I went through the setup wizard and followed the instructions in Ch. 2 to the letter (or at least I think I did). I have DHCP options 43 and 60 configured per the 3600 series Getting Started Guide.I believe my AP discovery process is sound because I see activity when I power on the AP and perform debug capwap ap all from the WLC. I have highlighted lines that I think are relevant. I have attempted to find the answer on my own by searching the Internet for these phrases. [code]
I upgraded a controller yesterday 5508 it went from a low code version 6.x to 6.0.196.0 then to 7.0.116.0. However although all the access points joined code 6.0.196.0 they refused to join 7.0.116.0. The aps are all 1242s.
The country codes etc were all fine so I do not understand what was going on.
*spamApTask0: Jun 26 16:07:44.734: 00:3a:99:db:f3:20 Discovery Request from 10.0.0.183:55065
*spamApTask0: Jun 26 16:07:44.734: 00:3a:99:db:f3:20 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 25, joined Aps =0*spamApTask0: Jun 26 16:07:44.735: 00:3a:99:db:f3:20 Discovery Response sent to 10.0.0.183:55065
[code] ......
A customer of mine has a centralized 2504 WLC with 7.2 code running. They have 1142N APs deployed locally as well as in remote sites (3) in FlexConnect mode. For no apparent reason last Thursday all the remote APs disassociated with the controller and could not rejoin. All the local APs remained up and unaffected.No changes to the WLAN, LAN, Firewall or MPLS WAN occured to cause this.The customer opened a TAC case and their determination was that ports 5246-5247 were not getting thru. When the customer engaged me this morning I had him run a packet capture on the Sonicwall firewall to prove out if the CAPWAP signals were leaving and returning across the WAN. Sure enough we can see this bi-directional traffic (pic attached). Also, I had the MPLS provider run a trace at the far end and they see the same traffic leave the remote site. And then an odd thing happened; one of the APs at one of the remote sites all of a sudden Joined the controller. So I tried rebooting the AP that is located in the same office, and it fails to Join. When I look on the controller under AP Join statistics, the last activity shows the controller receiving a Discovery Request and response is sent, but no further Config Request and response or Join Request and response.
View 8 Replies View RelatedWe have 3 5508 WLCs (A, B, & C) and several LAPs (1140, 3500, 3600). The APs learn the controllers IP addresses through DHCP Option 43. When we setup a new site we put the IP address of the controller we want the AP to join first. Lately, I've noticed that regardless of which WLC IP I put first when I setup Option 43 the LAPs are always joining a particular controller.
View 6 Replies View RelatedI am trying to deploy several AIR-CAP3502E-E-K9 access points from a cisco 5508 wire lan contoller running ver 7 code. However iam having difficulty registering the access points with the WLC. The wlc is connect to a 3650 switch, and each access point is connected to a 2960 switch. A bad update was not allowing the access points to get their correct firmware.
View 7 Replies View RelatedLAP join process: 70:ca:9b:25:5b:9d -> AP MAC10.10.1.30 -> DNS
View 8 Replies View RelatedI have some remote 1142s that I converted to LAP last night. They are not joing a WLC, but I they are online and I can ping them. Telnet or SSH is disabled by default (WHY???). What can I do to figure out why these access points are not joining the controller?
View 17 Replies View RelatedI am trying to configure new 5508wireless controller, AP 1042N model access points are able to receive DHCP IP address from Controller, but not able to join them.
View 11 Replies View RelatedI am tryign to join my first AP to the 5508 and am gettign this error int he logs.
*Dec 07 10:42:31.067: %DTL-3-NPUARP_ADD_FAILED: dtl_arp.c:2280 Unable to add an ARP entry for 0:0.0.0 to the network processor. entry does not exist
The management Interface is on the the same vlan as the AP , both untagged ports. the AP gets an ip address from my dhcp server.
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?
View 6 Replies View RelatedI have new 1600 series Access Points. I am trying to join those APs on controller but unable to join.
After doing config reset using mode button, I was able to join only. Please find the logs or error messages below:
*Mar 4 18:53:13.999: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 10.2.241.50:5246
*Mar 4 18:53:14.063: %LWAPP-3-CLIENTERRORLOG: LWAPP LED Init: incorrect led state 255
*Mar 4 18:53:14.079: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to administratively down
*Mar 4 18:53:14.123: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
[Code] ....
I am facing problem with an outdoor access point AIR-1522-K-E series which is unable to join a wirless lan controller 5508. The wireless AP is able to get IP address from dhcp server and discover the Wireless controller IP address. After this i see following status messeges on the console of AP.
*Aug 27 11:04:19.767: %CAPWAP-3-ERRORLOG: Go join a capwap controller
*Aug 27 11:04:21.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.2.64.50 peer_port: 5246
*Aug 27 11:04:21.000: %CAPWAP-5-CHANGED: CAPWAP changed state to
*Aug 27 11:04:21.707: %CAPWAP-5-DTLSREQSUCC: DTLS connection created successfully peer_ip: 10.2.64.50 peer_port: 5246
[Code]...
i have a problem with our new 5508 wireless controller (7.0.116.0).
Port 1 is the system default "management" (Port 2 is backup). Dynamic AP Management is disabled. Port 3 is a new dynamic interface "ap-manager 2" with Dynamic AP Management enabled and has a ip in a seperated VLAN which is not routed.
When i am connecting the AP (1260 series) to the "ap-manager 2" interface, then it will not join and i get an error message on the WLC:
*spamApTask1: Mar 05 14:52:12.783: %CAPWAP- -DISC_INTF_ERR1:capwap_ac_sm.c:1453 Ignoring discovery request received on non-managementinterface (3) from AP
When i am connecting the AP to the "management2 interface, then it is working fine. But i don't want the APs in the Management LAN. I want them in the separated no routed LAN explicit for the APs.
Got a bit of a quandary with joining new access points to our 5500 series W LAN Controller. It looks like the LAP is initially able to see the W LAN controller, but after that things go sideways. The LAP is pulling a valid IP address from DHCP, and the W LAN Controller is able to ping it.
In the controller's AP Join Statistics we get this:
Last AP Message Decryption Failure
Last AP Connection Failure -Timed out while waiting for ECHO repsonse from the AP
Last AP Disconnect Reason
[code]...
I have Cisco AIR-LAP1310G-E-K9 access point and 5508 wlan controller with version 7.0.220 and it is joining to the WLAN controller. I have enabled dhcp in the lan controller and i dont have external dns server. How to fix this issue? Can this LAN controller version will support this access point? My Lan Controller Management IP Address is 10.10.10.5 find the below configuration of 1300 access point.
AP001d.4513.dd68#reloadProceed with reload? [confirm]
%SYS-5-RELOAD: Reload requested by console. Reload Reason: Reload Command.%LWAPP-5-CHANGED: LWAPP changed state to DOWNXmodem file system is available.flashfs[0]: 4 files, 2 directoriesflashfs[0]: 0 orphaned files, 0 orphaned directoriesflashfs[0]: Total bytes: 7741440flashfs[0]: Bytes used: 2052608flashfs[0]: Bytes available: 5688832flashfs[0]: flashfs fsck took 14 seconds.Base ethernet MAC Address: 00:1d:45:13:dd:68Initializing ethernet port 0...Reset ethernet port 0...Reset done!ethernet link up, 100 mbps,
[code].....
I'm having problem joining a AP802 access-point in a Cisco 887VAM-W router to a WLC2125 running 7.0.116.0. I get the following messages pasted below from the AP console. The AP connects to the WLC over a EZVpn tunnel with a ASA on the other end, and can't see any error messages there. [code]
View 5 Replies View Relatedrecently migrated APs from a 4400 to 5508 which had the 7.4 code and encountered an issue that I haven't see before, in short the APs would never join the 5508 even when the selction rules said it should.The AP would get a discovery response from both controllers and even though the 4400 had 98 APs attached and the 5508 just 1 and a factory reset was made on the AP, it would always join the 4400.
A packet capture showed that the first CAPWAP address from the 5508 was always an IPv6 whilst the 4400 always sent IPv4 CAPWAP control adressess, disabling the global IPv6 option on the 5508 ensured that the the first CAPWAP control address was now an IPv4 and the AP then happily joined the controller, IPv6 addresses were still showing up in the discovery responses but since it was no longer the first one in the packet the AP didn't mind.
I cannot join domain it saying that "Computer name changes", A domain controller for the domain MyDomain could not be contacted.”. We have domain and workgroup, Actually first its already joined the domain, but I want to map the sharedrive inside the workgroup but I cannot map. Then I change to join workgroup. After I boot up I cannot log in with that user, I log in with administrator and the user is dissappear in the "User Account", but the profile inside document and setting still left surprise. I don't know why Now I create one more user, it can map to share drive also share folder. also can see all other network computer. But only left one is I cannot join the domain. I need this one because of we don't let our user using as administrator account. Before I testing this one I should backup, but now the time
View 2 Replies View Relatedthis is what happens when I try to join an acs 5.3 to the domain. On two other acs appliances, it works.
View 1 Replies View RelatedI have been having some issues with an ACS express joining a domain. This device previously had joined and after a weekend we received a notice that users were not authenticating to the domain. This in turn let us to find out the the device was unable to join the domain. Further research led us to find that the account the device was using to join the domain had been disabled. However, after re-enabling the account we would only recieve domain timeouts when tried to join. I opened a case with cisco and we have tried everything under the sun to no avail. I can ping the AD server (name & ip) from the ACS express. Cisco apply a root patch that allowed us to create hosts file entries on the device. I checked the system time and made sure it was within 5 minutes of the Domain controller time. In the logs of the ACS express the only thing I can really find is:
-"Checking remote join status: SMB connectivity failed"
-"Timeout reached in getting AD Diag info"
"acsxp/server Warning Server 0 is DisconnectedMode, IOException for reason, ipc socket connect; No such file or directory:
Recently we re-imaged the ACS and tried to join the domain without the old config on it and just received the same error. I reloaded the backup after that which also resulted in no change. I am starting to think that there is more of a domain issue rather than networking but am having issues finding a way to prove this via the logs. The are other ACS's configured in the network and the settings on this device match the settings on the other device in the network which are working correctly.
I have a couple 3600s that don't want to join. One i and one e that are both doing the something. It is able to find the controller via layer 3 discovery but it is acting like it is a mesh AP when it tries to join the controller.
From the 2500 controller (running 7.2)
*spamApTask2: May 13 12:03:05.272: f0:f7:55:ae:xx:xx Mesh AP username f0f755aexx xx.
*spamApTask2: May 13 12:03:10.739: f0:f7:55:ae:xx:xx spamProcessJoinRequest : RA
P, Check MAC filter
From the 3602i
flash:/mesh_start_cfg.txt: No such file or directory. The filesystem containing the variables may not be initialized yet.
I should note that 3500 APs are able to join this controller. The field guy is going to try to add the MAC address to the filter list when he gets back out on site to see if it allows it to join.
I've just installed two ACS 5.2 appliances and I'm trying to get them to join my domain, I've setup an account that has the relevant permissions (tested the account on a laptop and it can join the machine to the domain).
The ACS keeps coming back with an invalid credentials to join the domain error despite the fact that I know the user in question has the correct permissions.
I have a suspicion that the problem is related to how the ACS handles the Active Directory Domain, we have a large domain that spans several domain controllers. The DNS server uses round robin DNS to serve a different DC's IP each time, however a typical windows laptop is aware of what controllers it's allowed to use whereas the ACS box doesn't appear to be.
The ACS servers are located in a network in the UK that is only allowed to talk to 2/6 DC's and I have no way of controlling what IP appears when the ACS tries to join the domain due to the round robin DNS.
Is there any way to get around this? Or any way to hard code a specific DC for the server to connect to? Even being able to add the DNS manually to a hosts file would work.
